On Thu, Nov 09, 2006 at 12:10:52PM +0100, Armin Berres wrote: > Pierre Habouzit wrote: > > do you run selinux or sth like that ? that should work because the > >file descriptor is kept open after a fork. I'm completely unable to > >reproduce that :| > > Sorry for the delay, I don't have reliable internet access these days... > > I'm trying to run whitelister on a vServer, but without selinux and stuff > like this. Should I try to run whitelister as non-privileged user?
hmmm, maybe that's related to the vserver then. whitelister already runs as a non-privileged user. it's launched as root to allow it to bind to priviledged ports, or to open a unix socket e.g. in /var/spoool/postfix/private and to write its pidfile in /var/run/. then it donwgrades its privileges (to nobody by default) and daemonizes itself. what fails for you is when as a non privileged user it tries to write its pidfile again (thing that it should be able to do because the pidfile is kept open during the fork). So I suppose there is sth rotten in the vserver kernel patch in that respect. I'll try to investigate on my end. -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpUJ6zD0jH6N.pgp
Description: PGP signature
