Hi, On Sun, 2007-03-25 at 16:17:32 +0200, Jeroen van Wolffelaar wrote: > Package: dpkg > Version: 1.13.25 > Severity: normal > > start-stop-daemon --background forks once, not twice. Because of this, > sometimes the ppid of the launched won't be properly set to 1.
That's not the problem, forking once should be enough (I've made s-s-d fork twice anyway, but not closed the bug as it does not fix your current problem). The problem here is that the parents are not reaped fast enough by the kernel, and when the exec gets started it's still linked to it's parents. Adding some delay fixes this, but I'm not sure what would be the cleanest way to implement that, maybe waiting until ppid == 1. Dunno, will have to think about it a bit. > This is unfortunate in my case, where I want to fix the init.d script > of imapproxy (which doesn't have pidfile support) using --background: > imapproxy will actually do the double-fork&setsid dance when ppid!=1, > and this will this way actually happen sometimes, causing the pidfile > written out by s-s-d to be wrong. Regardless of this bug report, you should consider adding pid file support to that daemon, it should be few lines of code anyway. regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
