[PATCH] Make start-stop-daemon handle sending signals better

Rob Landley rob at landley.net
Wed Aug 30 00:18:05 UTC 2006


On Monday 28 August 2006 5:17 pm, Jason Schoon wrote:
> On 8/28/06, Natanael Copa <natanael.copa at gmail.com> wrote:
> >
> >
> > There is a bug about syslogd not starting (looks like the problem
> > affects any busybox applet)
> >
> > http://bugs.busybox.net/view.php?id=770
> >
> >
> On this one, I see the problem, but I don't know a clean, correct solution.

I don't use Debian-only stuff, so I dunno what start-stop-daemon is trying to 
do.  Not familiar with that command.

> The problem is that start-stop-daemon looks through the list of processes
> and checks if the new one is already running by comparing device and inode.

Which is a broken heuristic where busybox is involved.  I believe the second 
field of /proc/$pid/stat gives you the name the executable was originally 
called under (even if was called by path or rewrote its argv[0] or some 
such), and that's what "killall" goes based off of.  But that doesn't help if 
somebody calls "busybox httpd", does it?

Rob
-- 
Never bet against the cheap plastic solution.



More information about the busybox mailing list