httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gil Dawson <...@GilDawson.com>
Subject [users@httpd] Apache & Unix
Date Mon, 29 Dec 2014 19:01:49 GMT
Hi--

Apache V2.2 is running fine on my machine (a Mac Mini with MacOS 10.6.8).  

I am reading the \private\etc\apache2\httpd,conf file to understand Apache.  

I'm having a little problem understanding the Unix terminology.  
Unix isn't my first language, so this is pretty sophisticated stuff for me.
Still, I thought I knew a little.  I didn't realize how little until...

At line 13, I came across this paragraph:

# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/private/var/log/apache2/foo_log"
# with ServerRoot set to "/usr" will be interpreted by the
# server as "/usr//private/var/log/apache2/foo_log".

This paragraph has me stumped.

'...if the filenames ... begin with "/"' 
--	I cannot imagine how a filename could begin with "/".  
Does the author possibly mean pathname?  
A pathname might begin with either a "/" or a "~", would it not?

"If the filenames do *not* begin with "/", ... "/private/var/log/apache2/foo_log"
--	This is an example of a filename that does not begin with "/", right?
I don't get it.  I see "/" at the beginning of everything.
What would be an example of a filename that does begin with "/"?

"/usr//private/..."
-- What is the meaning of "//" in this context?

I'd appreciate an explanation or possibly a link to where I can read about these constructs.
 
Googling "unix pathnames" didn't pay off right away.

--Gil
Mime
View raw message