[EMAIL PROTECTED] wrote: > On Tue, 29 Jun 2004, Don Levey wrote: > >> I know the answer is out there somewhere, I just can't seem to find >> it. When my system restarts, clamd starts right up, just like it's >> supposed to. > > I'm sure it doesn't start up by magic -- you probably added a start-up > script for it -- something in /etc/init.d with a symlink from > /etc/rc3.d or whatever is appropriate for your system ? You need to > add a similar script for clamav-milter. > > Of course this will depend on what flavor of Unix, version, > run-level, etc. > Ah, I think this is what I was missing. In the appropriate rcX.d directory (3, 5) both the clamav-milter and the clamd are set at priority 80. Clamav-milter, perhaps because it comes first in alphabetical order, tries to start and fails because the clamd socket does not exist. Clamd starts without issue. I can then start the milter manually because clamd is already started. Looks like I'll change that from S80 to S85...
Thanks! -Don ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
