> -----Original Message-----
> From: Support ePaxsys/FRWS [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 30, 2003 6:54 PM
> To: [EMAIL PROTECTED]
> Subject: [clamav-users] Semi-Newbie question about DB updating
> 
> 
> Hey Great Product....
> 
> Couple things keep me awake nights (sorta)
> 
> Using 0.60 on RH7.3 systems with upgraded Kernels/GLIBC
> Using clamav-milter
> Sendmail 8.12.9
> 
> 
> Have a cron job set up to grab the DBs using freshclam - it works fine
> Questions are this:
> 1. How do I get the clamd binary to know there are new DBs 
> and to use them
> Tried with the freshclam option --daemon-notify and it did 
> nothing as far 
> as I could tell.
> Mind you, freshclam was started as 'root' and "I assume" 
> changed to 'clamav'
> 

more of an addendum: is --daemon-notify necessary? or is it used with a
custom path for the clamav.conf?

--daemon-notify=/path/to/clamav.conf
              Notify  the  daemon  about  the  new  database.  By
              default  it  reads hardcoded directory, but you can
              specify another one  using  a  full  path  to  cla-
              mav.conf. Local and TCP sockets are supported.


> 2. Running clamav-milter - does the milter portion need to be 
> restarted if 
> I shut-down and restart clamd?
> If so...
> I need to:
> shutdown clamd
> shutdown clamav-milter
> kill sendmail
> and reverse the process to update the databases and restart 
> the system as 
> it is right now
> (scripting this correctly on a fast-ish server is a challenge)
> 
> If not - this obviously becomes easier.
> I tried also the clamd 'reload' option, however it rightfully 
> complained 
> that the 'socket was in use'.
> 
> 
> Any insights here would be very helpful, maybe how some of 
> you with similar 
> systems do this.
> 
> Thanks! Looks great otherwise!
> Jerome
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to