Re: [AOLSERVER] 2Gb log file problem

2011-05-17 Thread Alexey Pechnikov
2011/5/17 Jeff Rogers dv...@diphi.com: Alexey Pechnikov wrote: 2011/5/17 Jeff Rogersdv...@diphi.com: Undocumented behaviour is bug, isn't it? I didn't suggest that it wasn't, I only offered a possible workaround for you to solve the immediate problem facing you. Thx, I use daemontools

Re: [AOLSERVER] 2Gb log file problem

2011-05-17 Thread Jeff Rogers
Alexey Pechnikov wrote: Thx, I use daemontools for starting AOL Server /usr/sbin/aolserver4-nsd -f ... and stdout may be logged by multilog (as example). Oh, the server log has the same issue. That one doesn't have automatic timed rolling, but it will still roll on a signal or an appropriate

[AOLSERVER] 2Gb log file problem

2011-05-16 Thread Alexey Pechnikov
With 2Gb size of log file all scripts don't work and the log file don't growing. Only static files are serves -- Best regards, Alexey Pechnikov. http://pechnikov.tel/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com

Re: [AOLSERVER] 2Gb log file problem

2011-05-16 Thread Jeff Rogers
The log module supports rolling. Normally it is done daily, but if your logs are growing too quickly and hitting 2G within a day you could set up a cronjob to send the server a signal to roll the logs, or a scheduled task within the server to roll the logs every hour, or when they reach a

Re: [AOLSERVER] 2Gb log file problem

2011-05-16 Thread Alexey Pechnikov
2011/5/17 Jeff Rogers dv...@diphi.com: Undocumented behaviour is bug, isn't it? -- Best regards, Alexey Pechnikov. http://pechnikov.tel/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF

Re: [AOLSERVER] 2Gb log file problem

2011-05-16 Thread Jeff Rogers
Alexey Pechnikov wrote: 2011/5/17 Jeff Rogersdv...@diphi.com: Undocumented behaviour is bug, isn't it? I didn't suggest that it wasn't, I only offered a possible workaround for you to solve the immediate problem facing you. There is a bugtracker for aolserver at sf where you can file