Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 22  |
|  Paul Quinn to Kurt Weiske  |
|  log rotation?  |
|  28 Sep 11 09:25:00  |
 Hi! Kurt, In a message to All you wrote: KW> What do you folks do to rotate logs? I'm trying to find the best way KW> to manage my server HTTP logs, tosser logs and mailer logs, and would KW> love to find a good way to rotate Radius/Argus's logs. I use a daily pre-maint process BATch called by Radius, that shuts Radius down first using a semaphore and runs this... -----8<-----C-U-T--H-E-R-E----->8----- :: Massage the Radius logfiles for later maintenance, CD \LogFiles REN Zmh_pots.log Mailer0Z.log COPY /Y ip_?.log IP_Calls.Log FOR %%N IN (1 2 3 4 5 6 7 8 9) DO DEL ip_%%N.log COPY /Y polls.log+cronapps.log+IP_Calls.Log+traps.log Mailer0X.log FOR %%F IN (access_log agent_log binary_log cronapps.log) DO DEL %%F FOR %%F IN (ipdaemon.log IP_Calls.Log polls.log traps.log) DO DEL %%F -----8<-----C-U-T--H-E-R-E----->8----- The end result is that only two logfiles remain: Mailer0Z.log (analog modem... POTS) & Mailer0X.log (all of the IP logs) which can be further manipulated in later maintenance using a simple mask "mailer0?.log". The later maint routines post all logs (mailer, tosser & other tools') to a local echo and arcs them up to daily ARJs, and then to a monthly ARJ. I have logs dating back to Dec '98, encompassing software no longer even in use. After all maintenance tasks are completed, the daily pre-maint process BATch re-starts Radius. The whole thing, pre-processing & maint, takes between three & four minutes with the average at three and an half. Cheers, Paul. --- * Origin: For a good time call 86753099 (Jenny)... (3:640/384) |
[ << oldest | < older | list | newer > | newest >> ]