On Sat, Jun 17, 2006 at 12:34:52AM +0200, Peter Eisentraut wrote:
> I wrote:
> > Here's a simple patch for this.  I had some unreproducible problems
> > that seem to be caused by the winbind_privileged directory not
> > existing by the time chgrp is run.  Could others test this?

> Tracing through the code shows that this can indeed happen because the 
> directory is created after the fork.  Perhaps the init script should 
> wait until the socket is created?

Why not pre-create the directory and set its permissions before calling
s-s-d?

I don't think 'winbind' is a very good name for this group, btw.  A
'winbind_priv' group would be clearer regarding the specific function of
this group, whereas 'winbind' could refer to anything at all in connection
with winbind (and who knows, we might need/want it for something else later).

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to