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 should not really make a difference anyway, as qscanq calls the clamdscan client - in fact any user can run the client which simply passes the file to clamd for scanning. Have I missed something here? ---- Frank Rabitsch wrote ---- > 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 If I look now, after installing yet again, the permissions are identical on my system. ---- Frank Rabitsch wrote ---- > 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". Yes, followed this. I created the group qscan purely for the my users qscan and qscanlog (ie. Gqscanq and Gqscanlog) as per conf-users. I then used qclean for the group in src/conf-groups to which my qscan and qscanlog users do _not_ belong. So, my setup follows the instructions, bar the name differences. Again, have I misinterpreted the setup? I'll set it up again carefully later today and report back. Thanks Dale ------------------------------------------------------- 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
