clamd problem

[Daniel Maher]

It should, but in my case, it did not.  Using setgid solved the problem, no questions asked. :-)

 

--

  _
 °v°  Daniel Maher
/(_)\ Administrateur Système Unix
 ^ ^  Unix System Administrator

 

"The most incomprehensible thing about the world is that it is comprehensible." -- Albert Einstein.

________________________________

From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Koopmann, Jan-Peter
Sent: May 10, 2007 9:55 AM
To: MailScanner discussion
Subject: RE: clamd problem

 

Should the "Incoming Work Group" setting not take care of that?

 

 

	 

	
________________________________


	From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Daniel Maher
	Sent: Thursday, May 10, 2007 3:46 PM
	To: MailScanner discussion
	Subject: RE: clamd problem

	Hello,

	 

	I recently had exactly the same problem.  I had to setgid the incoming directory, so that the sub-directories underneath (i.e. "7529/") were created with the correct group at run-time.

	 

	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20070510/ad063f2b/attachment.html