From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1S9MDC-0001xx-VN for garchives@archives.gentoo.org; Sun, 18 Mar 2012 19:56:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A597BE096C; Sun, 18 Mar 2012 19:56:10 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by pigeon.gentoo.org (Postfix) with ESMTP id 6E42CE0898 for ; Sun, 18 Mar 2012 19:55:01 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so2639828wib.10 for ; Sun, 18 Mar 2012 12:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:x-mailer:mime-version:content-type :content-transfer-encoding; bh=2OMYRdGpvcResMIb6wDrQqXJm3a6jPDOAbKEFT15D80=; b=F4LezXBkX+Iyt2ek1InsEPMMPbloDssy+QpAY0nthts3M8Id4m7K2AyNAZYQ7cAbts g+lkohWHfKyxknlvmTa4fvH2FyimelsSX1svpiDLW7hNKSbqQU3fIN3FLTlef7l3G55N Jmj2PQvGRPHs926Y08/o5D0LnkTJ245sqpjJ1tIJ+BsG/B+JDgojBecQ8i3qj7m6o9J+ 4VXHAveToEVGmxY7u5bs+AC9jyb5rZroG/dh6UbHUJlsUSQd8zYyqFOOpTsk6BDQHL/S m0oLQQtwo9qQLsq1UcEnrxpDaLRGcIeQiTEeeg7tz5jn6JJUSigf2pEN/Vu6T3GQARui Pw7Q== Received: by 10.216.131.232 with SMTP id m82mr5620022wei.71.1332100500650; Sun, 18 Mar 2012 12:55:00 -0700 (PDT) Received: from khamul.example.com (196-215-69-205.dynamic.isadsl.co.za. [196.215.69.205]) by mx.google.com with ESMTPS id ff9sm19513573wib.2.2012.03.18.12.54.57 (version=SSLv3 cipher=OTHER); Sun, 18 Mar 2012 12:54:59 -0700 (PDT) Date: Sun, 18 Mar 2012 21:54:05 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Cc: caneko@gmail.com Subject: Re: [gentoo-user] Re: systemd? [ Was: The End Is Near ... ] Message-ID: <20120318215405.07aa89e6@khamul.example.com> In-Reply-To: References: <709768995.843751.1331957483491.JavaMail.open-xchange@email.1and1.com> <20120317115300.GB3615@acm.acm> <87obrugwvn.fsf@newton.gmurray.org.uk> Organization: Internet Solutions X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 485d7645-ea06-44ef-afac-2334a6c1bf9f X-Archives-Hash: 2a93e68721ab0dddf451e5e17b7c86a1 On Sun, 18 Mar 2012 13:25:32 -0600 Canek Pel=E1ez Vald=E9s wrote: > > Or, said configuration files might be corrupted; the OpenRC > > initscript -- if written defensively -- will be able to detect that > > and (perhaps) fallback to something sane. systemd can't do that, > > short of putting all required intelligence into a script which it > > executes on boot. =20 >=20 > That is a completely valid point, but I don't think that task belongs > into the init system. The init system starts and stops services, and > monitors them; checking for configuration files and creating hostkeys > is part of the installation process. If something got corrupted > between installation time and now, I would prefer my init system not > to start a service; just please tell me that something is wrong. I tend to agree. All most no daemons and services out there check that their config files are not corrupt. At most they do syntax checking, throw errors and leave it up to the caller to deal with it in some appropriate manner. Most often, the caller is a human with a shell. Same with sshd and all that checking that happens in the init script. That stuff correctly belongs in the ebuild config phase, or as an ad-hoc action done by the sysadmin whenever {,s}he feel like it. The major point being, if the software itself does not perform a certain check, then the launching script should also not concern itself with those checks. [There are exceptions of course, some stuff is brain-dead, like tac_plus. Nice software, but if it can't write to it's own log files, it silently stops working and doesn't tell you. To all intents it looks like it works fine, but doesn't. Presumably, openssh does not fall in that category of brain-dead software] --=20 Alan McKinnnon alan.mckinnon@gmail.com