On 3/15/04 10:35 AM, "Trog" <[EMAIL PROTECTED]> wrote: > It actually took 7 mins to reload the sig database - that is very > strange. > > All threads are stopped *before* the "Reading databases ..." message. > All that happens after that is to reset the database statistics > structure and reload the sig database. > > Anything strange in your setup? Like NFS? Odd disk setup? It's running > out of memory/disk/cpu resource?
Actually yes. We have the database on an NFS server. Neither the box or the NFS server are anywhere near capacity. Plenty of RAM, network speed and CPU cycles available. No warning or error messages in any of the kernel logs and the boxes seem to be performing properly. I can find no reason why the process would just take 7 minutes to read the file... Several other things lightly access the NFS server at that time and don't have any issues. Are there other problems using NFS? Should we not have clamd read the definitions off the NFS directly and maybe look at rsyncing them to the proper place on local disk? I can't imagine why we'd need to do this, especially if you have several other boxes that run clamd. Having to run freshclam on them all individually would seem like a waste. Suggestions? -- Robert Blayzor, BOFH INOC, LLC [EMAIL PROTECTED] PGP: http://www.inoc.net/~dev/ Key fingerprint = 1E02 DABE F989 BC03 3DF5 0E93 8D02 9D0B CB1A A7B0 A Life? Cool! Where can I download one of those from? ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
