Depends on the impact of logrotation on the program for which the
rotation is occurring.
Also if there is low log activity, you may find a large number of
otherwise empty files will become troublesome to deal with.
Dean
david wrote:
Is there a good reason NOT to rotate logs hourly.. for example by moving
the logrotate cron to hourly instead of daily? This is a file created
hourly by cron for which I want to keep a history.
logrotate looks like a good way to do it. I'm assuming there is no
"hourly" option in logrotate, so I was going to force it to rotate by
specifying a very small file size.
Or is there "a better way" (tm).
--
http://fragfest.com.au
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
