On Wed, 2003-10-08 at 08:34, Graham Murray wrote: > Scott Deacon <[EMAIL PROTECTED]> writes: > > > No ... /usr/local/bin is NOT set as a path in the init but it is in the > > path of the user, > > > > When/How is clamdscan initiated? The error message suggested to me that > > it is called by milter as required so I assumed the PATH of the user > > would be the determining factor. > > clamdscan is called by the milter, but the milter is started by the > init script, so clamdscan must be in the path inherited by > clamav-milter. That is the explanation I came up with when adding > /usr/local/bin to the path in the init script cured that same > problem for me. > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Clamav-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/clamav-users
That fixed it. I created a .sh that loads clamav-milter with a path to clamdscan and it works fine. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
