Re: A few observations about systemd
On Sat, Jul 23, 2011 at 12:47 PM, Marc Haber
> On Thu, 21 Jul 2011 18:12:13 -0300, Fernando Lemos
> <email@example.com> wrote:
>>A more realistic option would be launching a program (or script) which
>>would read a configuration file (containing whatever
>>/etc/default/exim4 contains nowadays) and launch the exim instance(s).
> So one would have some thing "like an" init script, which would
> probably have to stay around and monitor the daemon? That doesn't look
> like an easier way to do things.
The thing you don't seem to get is that systemd uses "init files"
which are not really scripts. If your daemon is so "unorthodox" (to
put it politely) that it needs to be started up from a script, you can
simple continue using an init script to start it up, just move it out
of /etc/init.d, which really was never a great place for it.
Unfortunately, there are other big "unorthodox" daemons out there.
Fortunately, systemd can live with them just fine.