Hi there, On Fri, 16 Jan 2009 Rem P Roberti wrote:
> I'm back to square one here. I don't recall seeing your earlier posts about this, perhaps you can give us a pointer to the thread(s)? > I have installed clamav with milter, and have all of the appropriate > entries and flags in my rc.conf I entertain conjecture that the second part of that statement is false. > (freebsd), but I can't get the clmilter.sock to show up in > /var/run/clamav. However, if I start clmilter manually > > (clamav-milter --postmaster-only --local --outgoing \ > --max-children=50 --quarantine-dir=/var/mail/quarantine \ > --timeout=0 /var/run/clamav/clmilter.sock) > > clmilter comes right up and clmilter.sock appears in /var/run/clamav. You appear to have upgraded my conjecture to a theory. :) > Any ideas on why the I can't get clmilter.sock to come up at startup? More information is needed. The user running the milter when you start it from the command line clearly has permission to create the socket, but perhaps the user is different when clamav is started by the startup scripts. If that's the case, perhaps that user doesn't have the necessary permissions. Perhaps when the milter is started by the scripts it uses a different configuration file from when you start it manually. There could be other reasons for your trouble. Maybe someone with experience of ClamAV on FreeBSD (I have none) will have some other ideas. There might well be useful information output to logs or perhaps stdout (maybe the screen) under certain circumstances. Read the man pages to find out how to get this very useful information. Have you tried to put the command line that you gave above into one of your startup scripts (such as rc.local, or whatever passes for that on a FreeBSD system) and disabling the existing startup method? -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
