matthias, use the launchctl unload command, then remove the socket file, then restart the server. usually this should clean out the problems.
oliver Am 24.09.2007 um 12:10 schrieb Matthias Schmidt: > Am/On Sun, 23 Sep 2007 20:33:57 -0700 schrieb/wrote Dennis Peterson: > >> Matthias Schmidt wrote: >>> Hello, >>> >>> I have a little problem with clamd: >>> the process terminates, because: >>> Socket file /tmp/clamd is in use by another process. >>> >>> now I have no glue, which other process could use the socket file >>> from >> clamd. >>> I set the permissions to 777 on the end, but didn't help. >>> The original user and group is clamav. >>> So it seams to be not a permission problem. >>> >>> This all runs on a Mac OS 10.4.10 Server with clamav 0.91.2 >> >> Run lsof to see what processes have the socket open. >> >> Use ktrace and kdump to see what is happening when the process is >> started. Explain how clamd is started and how it is restarted. What >> other processes use /tmp/clamd? (see lsof). > > that's the strange thing, the socket is not open .... > when I start clamd by hand it works and the socket is owned by > clamav as > expected. > Looks like it's a problem with launchctl or the associated plist. > > Thanks and all the best > > Matthias > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http:// > wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
