[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd and server use



 Hi.

On Fri, 26 Sep 2014 13:02:16 -0400
The Wanderer <wanderer@fastmail.fm> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> On 09/26/2014 at 12:26 PM, Steve Litt wrote:
> 
> > On Fri, 26 Sep 2014 12:03:57 +0200 Martin Steigerwald 
> > <Martin@lichtvoll.de> wrote:
> 
> >> Actually systemd has quite some features which benefits server 
> >> use.
> >> 
> >> For example:
> >> 
> >> 1) It groups services and shell sessions into process control 
> >> cgroups and shields them against each other CPU usage wise.
> 
> >> 2) It is really good at catching the PIDs of the services it
> >> runs, no matter what funny things they do like double forking. So
> >> it exactly stops these PIDs and no others.
> 
> >> 3) Compare systemctl service status with /etc/init.d/service 
> >> status. Its obvious that the systemctl output is way more useful 
> >> to administrators.
> >> 
> >> 
> >> Can these be implemented elsewhere? I´d say yet for 1. Yet 2 and 
> >> partly 3 I think is the core of an init system.
> 
> Agreed - definitely 2, maybe / maybe-not 3, and definitely not 1.

1 - libpam-cgroup

2 - daemontools, runit, many others.

3 - usability of 'systemctl status' feature is actually questionable, if
you count in troubleshooting-over-phone usecase. In that case less is
better than more.

Reco


Reply to: