On Tuesday 14 April 2009 10:31:15 Kai Schaetzl wrote: > > > Judgemental again - I had not changed the path, which is why I had the > > problem this time. The default did not work. > > Which is contrary to this: > > If I change > > that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd > > service won't start, saying the socket doesn't exist. > > Obviously, only one of your statements can be true. > Wrong again. Both are true. If the default had worked I would not have needed to try alternatives. Fortunately there are readers of this mailing list that are a good deal more helpful than you are. Anne -- New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos