[175555] in North American Network Operators' Group
Re: Linux: concerns over systemd adoption and Debian's decision to
daemon@ATHENA.MIT.EDU (Stephen Satchell)
Thu Oct 23 15:54:56 2014
X-Original-To: nanog@nanog.org
Date: Thu, 23 Oct 2014 12:54:47 -0700
From: Stephen Satchell <list@satchell.net>
To: Lamar Owen <lowen@pari.edu>
In-Reply-To: <54493E27.4040405@pari.edu>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On 10/23/2014 10:43 AM, Lamar Owen wrote:
> Wouldn't it be more 'do one thing well' if you had a 'super' inetd
> setup that can start services in a better way than with individually
> packaged (by different packagers in most cases) shell scripts that are
> going to run as root?
inetd versus xinetd -- I thought that was an excellent change. It was
closely targeted, well documented, and did indeed do one thing well:
accept connections and pass them off to a handler.
I'm not so sure about systemd yet. I've not tried to create a daemon of
my own to run under the setup. I have tried to use upstart, and found
the execution of upstart (CentOS 6) didn't match the documentation.
Further, there was no "here's how you go from sysvinit to upstart" that
made sense.
I did see that systemd *does* have a paper for people needing to move
from the old sysvinit to systemd, which is a plus on the surface. I'll
be trying that in the future.
