Trog wrote to [EMAIL PROTECTED]: > On Fri, 2004-03-12 at 05:33, Odhiambo Washington wrote: > > I support the original poster. It would be a nice feature if it were > > done inside clamav itself, as he argued. > > Well, he's wrong :-) > > The UNIX philosophy is that each program should do all it needs to do > and do it well. So, it's clamds job to scan for viruses. It's logrotates > job to rotate log files.
Exactly. So why have the size limitation there at all? That should be a job of logrotate, too. The size limitation just causes grief, and, even if it worked correctly, it would interfere and do double-duty with logrotate. At the very least, I'd support an "unlimited" default size. Yes, I understand the risk of filling up one's log filesystem if it gets out of hand, but, again, it's the job of logrotate (or newsyslog, or similar) to limit log size. I've lost far more time (and important log detail!) to this LogFileMaxSize option than I would have from runaway log spam. And, besides, we have monitoring that'd alert someone long before that /var filesystem filled up... so that isn't really a concern, either. :-) I've since disabled the LogMaxFileSize option (=0), and would support that as default behaviour in future versions. Thanks, - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> SaskNow Technologies - http://www.sasknow.com 901-1st Avenue North - Saskatoon, SK - S7K 1Y4 Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
