david thompson wrote: > [EMAIL PROTECTED] wrote >> david wrote: >>> "--max-children must be given if --external is not given" ... >>> "timeout must be given if --external is not given". ... >>> Any clues?? >> >> Specify --external? >> >> Here's my personal rc.clamav:
snip > Thanks for your help. I do have a question or two though. > > When you write "here's my personal rc.clamav:" does this mean you are > running centos. I ask this as I have not seen this file. also in my > web searching for an answer I have not come across this file. It > looks as if it might go into /etc/rc.d. Is this true? I'm not running centos and I'm not familiar with it. I wrote rc.clamav from scratch with liberal copy/pasting from other startup files. Also there's stuff in the rc.clamav file that I didn't post. Yes, I did put it in /etc/rc.d and if you'd like I can send you a complete listing of the file offlist. What you should take from the partial listing I sent you though is there are no further than three separate clamav processes that each should have their own startup options... clamd freshclam clamav-milter However centos works, it should allow you to specify startup options for any or all of these separately. clamd is the running pool of threads that actually does the work of virus-scanning. So I start it up. All the options are set in /etc/clamd.conf so no command-line arguments are necessary freshclam is a command that checks for new virus definitions. I start it up in daemon mode with a -d option. This is only one of many methods for calling freshclam. Some people put it in their cron - if you do this, DON'T specify the -d option. If you start it up in daemon mode, the one process will check, sleep for a while, check again, sleep for a while, check again etc. ad infinitum. If you start it up in normal mode, it will check and exit. freshclam also uses /etc/clamd.conf clamav-milter is ironically the hardest of the three even though it doesn't do anything. It's just glue between sendmail and clamd. To be perfectly forthcoming, it doesn't really need clamd. You could run clamav-milter without clamd and have clamav-milter do the scanning itself. If you want it to use clamd to do the scanning, specify --external - if you want it to do the scanning itself, don't use --external. I personally like having a pool of clamd threads available for anyone to use, and I like clamav-milter to use the pre-existing pool rather than forming its own. clamav-milter uses /etc/clamd.conf to a certain extent, but has many other options that can only be specified at the command line. man clamav-milter for the gory details. -- Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902 Hispanic Business Inc./HireDiversity.com Software Engineer _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
