Riku Voipio, le Thu 22 Mar 2012 12:20:45 +0200, a écrit : > On Wed, Mar 21, 2012 at 11:06:22AM +0100, Bernd Zeimetz wrote: > > Common init scripts are short enough to make them easy to debug. Its > > more annoying when these shellscripts call other shellscripts which call > > other shellscripts - but that is a different issue which needs to be > > solved - but not necessarily in the init system. > > However debugging shell scripts is only easy if you already are a shell-script > and sysvinit expert already. When a non-expert opens say /etc/init.d/ssh, > figuring out what went wrong is not going to be easy. > > Sure systemd is unfamiliar and daunting now, but there is no reason to believe > the people who have learned howto handle sysvinit scripts wouldn't learn > systemd. In fact, if the systemd configuration files describe typical idioms > of services well enough, it will be easier to learn than the spagethi sysvinit > scripts sometimes end up being.
One big difference, however, is that when your system is screwed, you might however still have an editor. Rebuilding a systemd is a bit more involved, you probably don't even have a compiler on your production system... Samuel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120322103809.gi4...@type.bordeaux.inria.fr
