Come on anyone.... any suggestions, documentation to read ... anything please...

----- Original Message ----- From: "Shaun Bugler" <[EMAIL PROTECTED]>
To: "ClamAV users ML" <clamav-users@lists.clamav.net>
Sent: Thursday, February 24, 2005 9:22 AM
Subject: [Clamav-users] Manual self check with clamd



Hi, I am busy implementing a new method for updating our clam database files (1 server uses freshclam, all other machines rsync the update to themselves). This works perfectly. Only problem now is, clam doesn't reload the database right away like with freshclam. I run clamd RELOAD, it reloads clamd, but also tries to start another process, which I don't want.

Feb 24 08:48:43 lfap1a clamd[20770]: Daemon started.
Feb 24 08:48:43 lfap1a clamd[20770]: clamd daemon 0.81 (OS: linux-gnu, ARCH:
i386, CPU: i386)
Feb 24 08:48:43 lfap1a clamd[20770]: Log file size limit disabled.
Feb 24 08:48:43 lfap1a clamd[20770]: Running as user qscand (UID 511, GID
511)
Feb 24 08:48:43 lfap1a clamd[20770]: Reading databases from /var/clamav
Feb 24 08:48:44 lfap1a clamd[20770]: Protecting against 31093 viruses.
Feb 24 08:48:44 lfap1a clamd[23932]: SelfCheck: Database modification
detected. Forcing reload.
Feb 24 08:48:44 lfap1a clamd[23932]: Reading databases from /var/clamav
Feb 24 08:48:44 lfap1a clamd[20770]: Socket file /var/run/clamav/clamd.sock
is in use by another process.
Feb 24 08:48:45 lfap1a clamd[23932]: Database correctly reloaded (31093
viruses)
All I want is the 23932 bits, not process 20770.

How do I manually recreate the reload process that freshclam executes on an
update?

Thanks
--
Shaun Bügler
 Hetzner Africa
 Tel: +27 21 970 2000
 Fax: +27 21 970 2001
 Email Disclaimer: http://www.hetzner.co.za/index.php?id=245

[ * Awarded Top 50 ICT Companies status in SA - 2003/4]
[ * Awarded Top 300 National Companies status - 2004/5/6]

_______________________________________________
http://lurker.clamav.net/list/clamav-users.html


_______________________________________________ http://lurker.clamav.net/list/clamav-users.html

Reply via email to