On Tue, 2004-05-25 at 15:41, Samuel Benzaquen wrote: > > Upgrade to 0.71. > > > > It was most likely waiting for a scanning thread to finish, which it has > > to do before it can reload the sig DB. If a scanning thread fails to > > finish, that indicates a bug in the scanner somewhere (which may have > > been fixed already). > > Is there any way I can reproduce this problem? > Just to see if the upgrade fixes it.
Only if you have positively identified a file that caused it. > > > > > You should try and recover the file that is has a problem scanning. > > How can I do that? > We have no quarantine directory configured. > If clamd still has a file descriptor open to a file you can recover it through the /proc filesystem (even if it's been deleted). cat /proc/<pid>/fd/<fd> > file.msg -trog
signature.asc
Description: This is a digitally signed message part
