One would think that setting logroll to true in the
parameters section would cause the server log to be
rolled, as is the case with ns_log, but it doesn't work
that way. As Dossy says:
"while it's set up to roll the log on receipt of
SIGHUP, nothing actually sends it a SIGHUP. The nslog
module schedules a daily proc that initiates the access
log roll, but the main nsd doesn't do the same for the
server log."
It would be great to see this get fixed; it has been
this way for a long, long time.
Logged In: YES
user_id=143599
Fixing the title, which somehow got botched.