[Henrique de Moraes Holschuh]
> It is acceptable, however it is not optimal. Some daemons, such as apache,
> can be told to restart. It is best if we implement restart as restart, not
> as start-stop...
Sure, some do, but in my experience, most do not.
> OTOH, we already support a restart override, so it really isn't a
> big deal.
That was my idea too, that those with real restart support could add
an override.
> I really hate hackjobs of daemons that can't even support pidfiles
> properly. Bleh.
They are getting fewer, luckily. :)
> We could also avoid the need to override start/stop when no pidfile
> support is available, by doing the right thing when PIDFILE is not
> set, something like this:
>
> start-stop-daemon --start --quiet ${PIDFILE:+--pidfile ${PIDFILE}} --exec
> $DAEMON --test >/dev/null
Not really, as PIDFILE always is set, and can't be overriden at the
moment. I am open to suggestions on how to override it with the
current structure of the code.
--
Happy hacking
Petter Reinholdtsen
_______________________________________________
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
