On Thu, 2022-08-04 at 16:01 +0200, karl@??? wrote:
> Steve Litt:
> > On Wed, 2022-08-03 at 09:36 +0200, marc wrote:
> > > Karl Hammar
> > > > Steve Litt:
> ...
> > > > 1) Does Busybox init require the daemon to background itself?
> > > So I seem no reason why "nohup daemon > /var/log/logfile &" isn't sufficient
> > > for this, or is there something I am not aware of ?
> >
> > The preceding involves PID files, which can get mixed up or stale. Also, the
> > nohup.out file can grow to a monstrosity, although that can be handled (no pun
> > intended) by redirection to /dev/null.
> ...
>
> There is no requirement of pid files in the above. The notion of pid
> files comes from some req. that you should be able to do
> ./some_script stop. 

I do sv stop daemonname all the time.


> If you don't care about scripts like thoose in
> /etc/init.d there is no need for pid files, and if you manage the
> startup and shutdown of single processes on your own then the ps
> output is sufficient.

What if there are two of them running, or two processes so close in text that it's
hard to grep between them? I've done stuff like looking at the ps output or
searching thru /proc, but I always felt a little insecure when doing so.

SteveT