On Sun, Aug 21, 2005 at 02:48:55PM -0500, René Berber said: > Chris wrote: > > I have it set to "Run on selected schedule - when system boots" > > I've never seen cron used like this. So my comment before was apparently > wrong, > I'm not sure wich version of cron allows this "when system boots" option.
Many linux distros use vixie cron patched to allow @reboot syntax. I am not particularly surprised it is not portable :) > >>If you don't know what you are doing then start by reading the > >>documentation. > > > > > > I read the man pages, maybe I misinterpreted them! > > Perhaps I'm the one that has obsolete information, well what you describe > certainly doesn't work on Solaris 9, perhaps it works on Solaris 10 and/or new > Linux distributions (are you using Fedora Core 4?). > > Anyway, the problem you described is still there, something (perhaps that new > cron) ran freshclam at least twice. The idea, if you want freshclam as > daemon, > is to run it once with the -d option, or run it periodically (using cron) > without -d. > > HTH, sorry for my misunderstanding. Certainly the OP should run freshclam from a normal init script, if the idea is to start freshclam at boot. OP: locate the init script that starts freshclam, and set your options that way, and then skip the cron job. The init script method is the 'normal' way of doing things, and will be something that admins that come after you will quickly grok. Doing things in a non-standard way only raises the curve for others who have to follow you. -- -------------------------------------------------------------------------- | Stephen Gran | party, n.: A gathering where you meet | | [EMAIL PROTECTED] | people who drink so much you can't | | http://www.lobefin.net/~steve | even remember their names. | --------------------------------------------------------------------------
signature.asc
Description: Digital signature
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
