On 08-09-2011 12:58, Paul Ezvan wrote: > On Thu, 8 Sep 2011 12:08:30 +0200, Clemens Fruhwirth wrote: >> If you use Debian, you might have come across start-stop-daemon. It's >> part of the dpkg package and encapsulates all the knowledge, they >> learnt when dealing with starting and stopping daemons. > > Systemd may provide the same simplification of handling system deamons, > maybe we can look at it also. But it may be to bloated to be considered > as KISS :) > > Paul > The problem with systemd is that it is in community and I'd say that it still needs thorough testing and wiki documentation before it is adopted as arch's default init system. About the program that is suggested, it is c, if it really brings big improvements then go for it, if the problem is just handling programs that don't free a network port immediately when they are terminated, then I'm not sure if providing a c program that may be harder to understand and debug is a solution. Programs like deluge don't free the used ports immediately and users have to know how to deal with that, system daemons are not different, if anything a bug report/feature request/improvement request should be submitted upstream to tackle this problems. I may be wrong and imagining things but I think before I've seen arch keep bash scripts instead of replacing them with c programs because the speed improvement was not that substantial and bash was easier to understand and hack. However this is a good candidate to be maintained in [community] (or [extra]) as an alternative or maybe as a dependency of those misbehaving daemons that need special handling. -- Mauro Santos
