Voytek, > I just went to check and, guess what, errors stopped since Oct 29 at > 22:18, and, now all's well. > perhaps I didn't reload deamons after I altered to give group xrw...?
Good. The rx access should suffice, there is no need to give clamd write access to amavisd temporary directories or files. In fact protection from each other is the reason why it is desirable these two daemons run under different UIDs. > if there is anything you want me to try, let me know > > I'll try installing both amavisd and clam on another Centos system, and, > see what happens, is there a 'desired install order': install clam, then, > amavis ? The installation order doesn't matter. Even the startup order of Postfix/amavisd/clamd shouldn't matter much - worst case the first message in a queue after a startup gets delayed for another minute. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
