Frank Tanner III wrote:
On Sun, 2007-02-25 at 16:38 -0800, Dennis Peterson wrote:
Frank Tanner III wrote:
Turned out there was a defective boolean in the default clamd.conf file
that I had to fix. The FixStaleSocket directive is a boolean and had
nothing after it. Putting a yes after it seems to have fixed the date
problem. It also appears to have fixed the segfault as well.
Thanks for the help. One of the devs should look into fixing the
default clamd.conf file.
What is wrong with it?
The line FixStaleSocket isn't commented out by default. It just says
FixStaleSocket. There is no true, yes, or 1 after it. That was giving
an abort on the clamd.conf file. I added a yes after FixStaleSocket and
the abort on the clamd.conf went away, and so did the "older than 7
days" error message.
Interesting - that's not the case in my built-from-scratch version. It
appears thusly in my unmodified sample:
# Remove stale socket after unclean shutdown.
# Default: no
#FixStaleSocket yes
And of course defaults to no.
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
