Starting service daemons

[Natanael Copa]

On Tue, 2007-03-27 at 13:56 +0200, hinko.kocevar at cetrtapot.si wrote:
> Natanael Copa wrote:
> > On Tue, 2007-03-27 at 13:28 +0200, hinko.kocevar at cetrtapot.si wrote:
> >> Natanael Copa wrote:
> >>> On Tue, 2007-03-27 at 09:16 +0200, hinko.kocevar at cetrtapot.si wrote:
> >>>> Hello,
> >>>>
> >>> Use start-stop-daemon -n or with pidfiles.
> >>>
> >> Ok, thanx.
> >> I've tried -m -p /var/lock/pidfile and strange thing happens - actual 
> >> PID number recoreded in the pidfile doesn't belong to the daemon being 
> >> started. It belongs to the process that already finished. Eg.
> >>
> >> # start-stop-daemon --start -m -p /var/lock/crond.pid -x /sbin/crond -- 
> >> -c /etc/crontab/
> >>
> >> # ps
> >> ...
> >>   4274 root        192 S   /sbin/crond -c /etc/crontab/
> >>
> >> # cat /var/lock/crond.pid
> >> 4272
> >>
> >> Note: I observed that this doesn't happen with dropbear client but with 
> >> busybox applets - crond, httpd, ...
> > 
> > Its normal. process forks, child continues, parent exits and the pid of
> > parent get recorded.
> > 
> > try start-stop-daemon -n
> > 
> 
> It doesn't help or I don't know how to use it :/

Then drop the pidfile (-p) and use -n only.

alternatively you can drop start-stop-daemon:

DEAMON=httpd
start() {
	if pidof $DAEMON >/dev/null ; then
		echo "already running"
		return 1
	else
		$DEAMON $OPTS
		return $?
	fi
}

Natanael Copa