Received: by taz.hyperreal.com (8.6.12/8.6.5) id NAA15677; Thu, 14 Sep 1995 13:09:57 -0700 Received: from epprod.elsevier.co.uk by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id NAA15672; Thu, 14 Sep 1995 13:09:53 -0700 Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by epprod.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id VAA27995 for ; Thu, 14 Sep 1995 21:07:12 +0100 Received: from tees.elsevier.co.uk (actually host tees) by snowdon with SMTP (PP); Thu, 14 Sep 1995 21:05:52 +0100 Received: by tees.elsevier.co.uk (4.1/SMI-4.1) id AA09775; Thu, 14 Sep 95 21:05:23 BST Date: Thu, 14 Sep 95 21:05:23 BST From: Andrew Wilson Message-Id: <9509142005.AA09775@tees.elsevier.co.uk> To: new-httpd@hyperreal.com Subject: -d | !-d ? <- Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Ho, what do we all understand to be the meaning of the '-d' option? >From Usage we have: -d directory : specify an alternate initial ServerRoot which suggests that: ./httpd -d /foo/bar will start the ball rolling in the /foo/bar directory. If /foo/bar/httpd.conf contains a line like: ServerRoot /baz/boo then *this* will also override the '-d' setting, as seen under Apache 0.8.13. There seem to be two possibilities: 1) -d is behaving the way we mean it to, and we've just forgotten to mention in documentation that configuration files can overrule command line options - so if we're keen to use '-d' we should remove the ServerRoot line from the conf files. 2) we really meant '-d' to completely override all configuration file directives to the contrary and we never got round to coding it up to do just that. What do you think is meant by -d. Thoughts? Ay.