I'm not sure if this is new in nsd 4, but there are config parameters
in OpenACS's config.tcl under ns/parameters that seem to control
rolling the server log file -
ns_section ns/parameters
ns_param serverlog ${serverroot}/log/error.log
ns_param logroll on
ns_param maxbackup 5
looking in nsd/nsconf.c though, the maxbackup parameter looks like it
should be "logmaxbackup", and other relevant parameters are
logusec
logroll
logexpanded
debug
logdev
lognotice
logmaxbackup
logmaxlevel
logmaxbuffer
logflushinterval
serverlog
On 15/09/2004, at 11:26 PM, Janine A Sisk wrote:
In nsd 3.3 we have always had to use a script to get the logs to roll
properly. I had "assumed" this problem would be fixed by now, but it's
looking like it's not. I've got logroll set to true in my config file
but the error log just keeps on growing. Access logs OTOH do seem to
be rolling properly now.
Another reason for us to do our own rolling was because we don't ever
want access logs to be deleted, and it appears that there is no way to
specify that; you have to give some value for max backup or else a
default will be assumed. Is there a way around this?
This is not urgent for me; I will just disable log rolling and use my
script, as I've been doing for years, but I wanted to mention it in
case it turns out to be one of those bugs that's so easy to work around
that no-one bothers to mention it.
janine
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
