Quoting Ace Suares [EMAIL PROTECTED]:
Hi,
I installed clamav on Debian Woody with Qmail-Scanner. I used the debian
package from deb http://people.debian.org/~sgran/debian
So far so good, but since qmail-scanner runs as user qscand and clamd runs as
clamd, clam can not write files in the working
Hi,
qscanq (http://www.qscanq.org, http://www.qscanq.org/clamdscan.html) seems to
want to log to stderr, and provides a patch for it:
(http://www.qscanq.org/clamav-0.70-stderr.patch.gz)
Did this patch make it in the current release? Will it? Are there special
reasons not to incorporate that
On Sunday 27 June 2004 09:12 pm, Ace Suares wrote:
Hi,
qscanq (http://www.qscanq.org, http://www.qscanq.org/clamdscan.html) seems
to want to log to stderr, and provides a patch for it:
(http://www.qscanq.org/clamav-0.70-stderr.patch.gz)
no need to patch.
Did this patch make it in the
On Sunday 27 June 2004 22:24, Jeremy Kitchen wrote:
no need to patch.
{snip}
LogFile /dev/stdout should do the trick. I use it on many many many many
systems.
Thanks for the suggestion - I was thinking along those lines (honestly ;)
But in trying it out, I get this:
On Sun, Jun 27, 2004 at 09:22:19PM -0400, Ace Suares said:
It doesn't look like that: clamav.log is owned by qscand...
yet, the file is not appended to!
See my previous post - it seemed that I forgot to make the pid file owned by
qscand. Since I fixed that, the logfiles are rotated
On Sun, Jun 27, 2004 at 11:02:04PM -0400, Ace Suares said:
On Sunday 27 June 2004 22:24, Jeremy Kitchen wrote:
no need to patch.
{snip}
LogFile /dev/stdout should do the trick. I use it on many many many many
systems.
Thanks for the suggestion - I was thinking along those lines
Try using LogFileUnlock, and checking the permissions on the device.
I suppose you mean putting
LogFileUnlock
in clamav.conf...
but it didn't help. Same error.
Those do look like clam error messages. And no need to stick to stdout
- stderr should work the same.
permissions on
The patch located at qscanq.org for clamav-0.70 is working for 0.73 too.
Just change string 0.70 with 0.73 in patch file and patch works without
problem.
Ace Suares writes:
Try using LogFileUnlock, and checking the permissions on the device.
I suppose you mean putting
LogFileUnlock
