Am Freitag, 26. September 2014, 22:41:04 schrieb Reco: > Hi. > > On Fri, 26 Sep 2014 13:02:16 -0400 > > The Wanderer <wande...@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 > > > > > > <mar...@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.
Then go and support these. Test them and help them to be available and tested in Debian. Help them so have sane defaults and so. If you don´t like systemd as a default in Debian that are at least some other options for acting on it. > 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. Oh, in that case I certainly prefer a this and this and this and prefer to listen for the phone partner to read it all out… instead of "oh it failed, but it doesn´t tell why". That said systemctl status also doesn´t always tell why as I learned already. Or at least not immediately so. -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2764642.jQ7QsSs4lO@merkaba
