On 28. Februar 2007 20:12 Török Edvin wrote: > On 2/28/07, David Fröhlich <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > But unfortunately clamd crashed about five seconds after starting it. > > I tried both, using sockets and tcp communication. > > What did you do in those 5 seconds? Did you scan a file with clamdscan?
No, I did nothing. I just started the clamd daemon and waitet. I started 'ps aux' to see whether the daemon is still there or not. And after about 5 seconds of doing nothing it disappears with that error message. > If you have more details please open a bugreport on > http://bugs.clamav.net I opened a new bug report together with the output of clamconf and the whole error log message. > > So, what does that "fstat(): socket descriptor gone" and "Main socket > > gone" mean? > > gone means here "unaccessible, unexpectedly closed, deleted etc." Okay, but now it would be interesting which socket is meant. Since when I use the old behaviour (Listen on TCP-Port) there should not be any socket. > > I do not think that it has something to do with the socket used by > > clamdscan because this also happens if I use the old TCP connections > > instead of the new socket. > > Did you read clamd.conf(5): TCPSocket, LocalSocket ? Yes, and I would say that I have understood how clamd works. It is similiar to MySQL or SpamAssassin for instance where you can also connect to via TCP and via a local socket. But with clamd none of this both methods works for me. regards, David _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
