I'd like to let everyone know that there's a possible bug in
qscanq-0.43(scanning harness for qmail) after trying to use clamdscan
from
clamav-0.90.1 as the scanner. Downgrading to qscanq-0.42 resolved the issue.
This is the first time I've tried upgrading qscanq from 0.42.
___
Thanks for the help. The issue was the user which clamd
runs as. I now run qscanq as setuid 'clamav'.
- Steve Philson wrote:
> I believe the temporary files unpacked by qscanq
> (actually by whatever mime unpacker you use) are
> readable only by the owner, which is whatever owner
> is set up
Hi everyone
Anyone wishing to run clamd under daemontools
http://cr.yp.to/daemontools.html
can use the attached patch I hacked together, which is
almost identical to Len Budney's patch:
http://mysite.verizon.net/vze1ypud/software/qscanq/clamav-0.70-stderr.patch.gz
I didn't notice Len had updated h
#x27; config entry when using daemontools...
Dale Gallagher wrote
>Recommended /etc/clamav/clamav.conf entries:
>
> LogFile stderr
> LogFileMaxSize 0
> FixStaleSocket
Foreground
---
This SF.Net email is sponsor
Hi
> you can use /dev/fd/2?
> /proc/self/fd/2
None of the suggestions incl. the above work
Running Slack 9.1 boxes with Kernels 2.4.25 and others with
2.6.4
Errors reported are consistent:
ERROR: Can't open /dev/fd/2 in append mode.
ERROR: Problem with internal logger.
Please check
Dale Gallagher wrote
> I'm not using clamd, however I run Slackware 9.1 (kernel
> 2.4.25), so in case
> it helps, here are my ownerships/permissions on the
> relevant device files:
Antony Stone wrote
> $ ls -al /dev/fd
> lrwxrwxrwx1 root root
Hi
I appologise for the OT (though related) post. I'm having a
tough time getting qscanq running - the issue is related to
permissions. I'd appreciate a verbose listing of the
relevent dirs on a host where qscanq has been successfully
deployed. Thanks!
qmail-smtpd (when passing the mail to qscanq
> it works beautifully ti fails only in supervised mode.
>
> My run script is,
> # cat run
> #!/bin/sh
> exec 2>&1
> #exec /usr/local/bin/chpst -u clamav \
> #/usr/local/bin/chpst -m 4000 /usr/local/sbin/clamd
> #exec /usr/local/bin/chpst -m 8000
> /usr/local/sbin/clamd
> exec /usr/local/
> > Have you applied this patch? (for logging to stderr)
> > http://www.qscanq.org/clamav-0.70-stderr.patch.gz
>
> No. Is it necessary for my suitation?
Not unless you're piping stderr to a logging facility like
multilog.
> Do you have any more ideas on what might be wrong?
> Or shall I try it
Thanks for responding Frank.
Frank Rabitsch wrote
> with the exception that clamd is running as user qscanq
> and it logs to
> stderr using the qscanlog user and the std-err patch.
>
> Try to run clamd as qscanq and see what happens.
I tried this over the weekend without luck. This sho
Andrej Trobentar wrote
> Hello,
>
> I have aplied the appended patch and now I see all the
> output of clam in "ps axwww|grep readpro" insted of
> /var/log/clamd/current. Currently I'm using clamav 0.67-1
> with a patch that Tomasz Kojm send in
Hmmm...
Did you patch clamav-0.70, or cla
Sean Matheson <[EMAIL PROTECTED]>
> Is there perhaps a more effiecient way to san my
> incoming and outgoing qmail mail using clamd for
> instance?
The following is fast - scans and rejects infected
mail before it reaches the real queue...
clamav-0.71
run clamd as user clamav
ripmim
"kengheng" wrote:
> Hi All,
>How do I log the output from clamd using multilog?
> I've got the clamd supervised, but the log for
> infected emails was unable to be capture. Any Ideas?
A previous post of mine detailing how to do this:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg08827.html
13 matches
Mail list logo
