Bill Landry wrote: > > And this works even with the clamav and amavis users and groups > removed. I'll be updating and testing my script and will release an > updated version soon. Thanks everyone for the feedback, I think all of > this shows that the issue appears to be with access to /dev/null, for > some strange reason. > > Bill >> There used to be a problem with clam when started by root. Files were >> created and owned by root and when the clam process su'd to the run-as >> user it could no longer work with those startup files. That problem was >> corrected.
I must have been daydreaming through part of this thread - you've been using clamscan which doesn't change user id. So far as I know only clamav-milter and clamd do so and even then only when started as root. Clamscan always runs as the executing user. Someone correct me if I'm wrong here. Doesn't explain the tmp file issue though. I do wonder now if the tmp file is ever created. Clamscan is trying to create a file from stdin but since stdin is /dev/null, does the file ever get created? If not then it will certainly fail when it tries to delete it later. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
