Busybox init doesn't even support the kill -HUP 1 to reload, I wrote a patch that is only in tomsrtbt-busybox-init for the addition but not yet for deletion of processes. Yes, that is how it is right now, you can add but not delete with kill -HUP 1, until I rewrite the init again some more. I know how to fix it, it is just a matter of applying time to it.
-TOm On Fri, 14 Jun 2002, Pete Scott wrote: > Date: Fri, 14 Jun 2002 14:17:52 +0000 > From: Pete Scott <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [tomsrtbt] > > Hi > > Thanks for the help with ftpd. > > I've got an ftpd from mulinux that I've got to work now. The problem was that when I >ran it by say: > > # ./ftpd > > it quits straight away. So I ran it with nc like this: > > nc -l -p 21 -e ./ftpd > > And once I'd added an ftp user to /etc/passwd it worked fine. But obviously for only >one connection. > > So I wanted to put the following line into /etc/inittab so it would respawn: > > c9:5:respawn:/bin/nc -l -p 21 -e /bin/ftpd > > Then I do: > > # kill -HUP 1 > > To get init to re-read /etc/inittab > > All this works fine though it would be less hassle with a binary that could run >stand alone. > > But what I noticed is that if I comment out a line such as the ftpd one in >/etc/inittab then did: > > # kill -HUP 1 > > Then ftpd/nc deamon would still be running/respawned. Even if I kill the nc process >it would get respawned by inittab. > > Is this usual or a oddity of busybox (?) init? > > Pete > >
