Cristina Tanzi Tolenti wrote:
http://qmail-scanner.sourceforge.net/CHANGES
says:
Changed setuid to 6755 - ie it's now setuid and setgid. Forcing all
files to be group qscand will allow those who wish to do so to keep
their AV daemons running as other accounts. They just need to ensure
tho
Cristina Tanzi Tolenti wrote:
Hi,
I install qmail-scanner-2.01st + clamav 0.88.2 and I would like to use
CLAMDSCAN as scanner.
Clamd runs as clamav user so I add clamav to group qscand as I found in
the CHANGES file (
* Changed setuid to 6755 - ie it's now setuid and setgid. Forcin
Cristina Tanzi Tolenti wrote:
I understand!!!
my logrotate.conf is wrong
# qmail-scanner
/var/spool/qscan/qmail-queue.log {
daily
create 0600 qscand qscand
rotate 30
compress
I set create 0660 qscand qscand
thank you very much!!!
That will do it every t
Yeah, the solution is to have it correctly run as the clamav user. Did
you add clamav to the qscand group? Are the permissions of ALL
directories clamav uses owned by the clamav user (log files, database
directory, etc..)?
-Jim
Yes, I add clamav to qscand group (usermod -
Cristina Tanzi Tolenti wrote:
Yeah, the solution is to have it correctly run as the clamav user. Did you
add clamav to the qscand group? Are the permissions of ALL directories clamav
uses owned by the clamav user (log files, database directory, etc..)?
-Jim
Yes, I add clamav to qscand g
Hi,
I install qmail-scanner-2.01st + clamav 0.88.2 and I would like to use
CLAMDSCAN as scanner.
Clamd runs as clamav user so I add clamav to group qscand as I found in
the CHANGES file (
* Changed setuid to 6755 - ie it's now setuid and setgid. Forcing
all files to
be group
