[EMAIL PROTECTED] ([EMAIL PROTECTED]; Tuesday, January 28, 2003 2:28 PM):


>> > > Also, can anyone point me to some good background info on the
>> > > application of analog in a mass virtual hosting environment?  Some
>> > > standard approaches on the use of a single configfile or per host
>> > > config files would be really appreciated.
>> >
>> > There are some details in the HOW-TO's
>> > (http://analog.cx/how-to/index.html) that can get you started.
>> >
>> > When we setup mass virtual hosts, we always use a default
>> > configuration file (analog.cfg in the Analog directory) and then add
>> > per-host customizations. This makes it easy to quickly make global
>> > changes.

> I've just moved one of my servers to this system and get

> "Warning D: LOGFORMAT in configuration file analog.cfg with no subsequent
> LOGFILE"

> for each host in the batch file. docs/errors.html states that "Most likely
> you put the LOGFORMAT after the LOGFILE command. You must put the
> LOGFORMAT before the LOGFILE command"

> but docs/syntax.html states that "The first file which analog reads is the
> default configuration file, normally called analog.cfg"

> The default configuration file, which is being read, contains

> LOGFORMAT COMBINED
> LOGFORMAT COMMON

> The VirtualHost's file, which should presumably then be read (second)
> contains the LOGFILE command, which is also being read.

> Surely therefore, the LOGFORMAT is before the LOGFILE - so why the
> warning?

Use DEFAULTLOGFORMAT. LOGFORMAT only applies to LOGFILE statements in
the same config file (and the command-line counts as one, separate
config file).

-- 

Jeremy Wadsack
Wadsack-Allen Digital Group

+------------------------------------------------------------------------
|  TO UNSUBSCRIBE from this list:
|    http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
|  Digest version: http://lists.isite.net/listgate/analog-help-digest/
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------

Reply via email to