On Fri, Oct 27, 2006 at 08:00:26PM +0200, Armin Berres wrote: > Pierre Habouzit wrote: > > I would need a trace following forks then, yours is useless as it > >traces the father. please run > > strace -f -F -s 256 -o trace whitelister > >as root and send it as an attachement to the bug report please. > > Anything you say... > It is attached. :-)
> 28598 ftruncate64(3, 0 <unfinished ...> > 28596 --- SIGCHLD (Child exited) @ 0 (0) --- > 28598 <... ftruncate64 resumed> ) = -1 EACCES (Permission denied) > 28596 exit_group(0) = ? > 28598 write(2, "Fatal error: exception Unix.Unix_error(1, \"ftruncate\", > \"\")\n", 59) = 59 > 28598 exit_group(2) = ? okay I already answered to that, at least I thought so. it seems the forked daemon is unable to write its PID in the pidfile, whereas I keep the file open. what I do is: 1/ I open the pidfile when I'm started as root 2/ I downgrate the privileges, and keep the file open. 3/ I fork 4/ I truncate the file to write my new pid <--- crash 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 :| -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpDB6DmHgrTe.pgp
Description: PGP signature
