> qscanq: fatal: unable to chdir to > /var/qmail/qscanq/root/scanq: access denied > > clamd is running under daemontools as user clamav; this > shouldn't pose an issue, as qscanq connects to clamd using > the clamdscan client.
I'm running clamav supervised as described on http://www.clamav.net/doc/0.70/clamd_supervised/clamd-daemontools-guide.txt 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. > src/conf-scancmd: > /usr/bin/clamdscan --quiet ./ > > My permission listing: > > # ls -la /var/qmail/ | grep qscanq > drwxr-sr-t 5 root root 4096 May 1 12:49 qscanq/ > > # ls -la /var/qmail/qscanq/root/ | grep sc > drwx--S--- 2 qscan root 4096 May 1 12:49 scanq/ > Security settings on my box: /var/qmail/qscanq/: drwxr-sr-x 3 root root 4096 May 2 13:49 root /var/qmail/qscanq/root: drwx--S--- 2 qscanq root 4096 May 3 18:08 scanq > with qscanq user/group set as follows: > > qscanq user/group: qscan/qscan (src/conf-users line 1) > qscanq log user/group: qscanlog/qscan (src/conf-users line > 2) > qscanq user for /service: qclean (src/conf-groups line 1) > Don't have any groups in the user file. cat src/conf-users: qscanq qscanlog cat src/conf-groups qscanq Furthermore the website mentions that the users should not belong to the group: "Create users named Gqscanq and Gqscanlog (or whatever is in conf-users), and a group named Gqscanq (or whatever is in conf-groups). The users should NOT belong to the Gqscanq group". Hope this helps. regards Frank ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
