> > When I run qmail-scanner's ./configure it auto finds Clamuko and uses it. > > This is a stupid qmail-scanner naming "bug". You're not REALLY using clamuko. > They just say you are. Basically, they mistakenly named clamd or clamdscan > "clamuko". Silliness, I say.
That's what I was starting to think because best I can tell is that I'm using clamdscan. Not really sure how to tell qmail-scanner to use clamscan or clamd specifically. > > When I execute /usr/local/sbin/clamd it fires up the clamd daemon. How am > > I > > supposed to stop it etc.? > > If you're using linux, you'll have to do: > > ps auxwww | grep clamd > > then > > kill <clamd-pid> I am using Linux (sorry forgot to include that). That just didn't seem like a clean way to stop it. I tried kill -3 <clamd-pid> and nothing happens. So then I did kill -9 <clamd-pid> which kills it but I have to go and manually delete the socket /tmp/clamd > > I've read about the options it takes like PING > > etc. but I don't know how to execute them. I tried echo'ing them to the > > socket file /tmp/clamd but that fails (I was getting desperate for options > > :) > > Can't help there. I don't need to PING my clamd daemon, so I've never bothered. Yeah I don't really want to ping it either (not yet anyway). I'm mostly interested in sending the QUIT and RELOAD options to it (relating to my first question about killing clamd). Thanks Malcolm ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
