On Fri, 2007-03-02 at 07:32 +1000, Bill Maidment wrote: > On Thu, 1 Mar 2007 11:04:01 -0800 (PST), Zivago Lee wrote > > > On Thursday March 01, 2007 at 12:45:20 (PM) John W. Baxter wrote: > > > > > >> The way our system operates, we learned of the problem well after the > > >> 700 > > >> permissions were set up, when I restarted our mail processing system for > > >> another reason. (We run two processing systems per machine--handling > > >> submitted mail and handling incoming-from-the-world mail, each under its > > >> own > > >> user, so 700 is "difficult" for us.) > > > > > > You might be able to script something to check the permissions and > > > change them if they are not what you expected. Probably running it via > > > CRON would take care of the problem. > > > > I was looking at the freshclam.conf file and I see this: > > > > #OnUpdateExecute command > > > > Maybe we can put in 'chmod 755' on the directory once it runs an update... > > > > Any thoughts? > > > > That's what I have been doing. And it works if you remember to take out the > hash ;-)
Awesome.. thanks a lot. Of course I'll make sure to remove the hash ;-) -- Zivago Lee <[EMAIL PROTECTED]> _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
