Re: Init system deba{te|cle}
On Sun, Nov 3, 2013 at 9:23 AM, Marko Randjelovic <markoran@eunet.rs> wrote:
> On Sat, 02 Nov 2013 15:58:45 +0100
> berenger.morel@neutralite.org wrote:
>>
>> _ sysvinit scripts are scripts. Scripts needs programming skills, and
>> the sh language does not have an easy to read syntax. I would in fact
>> call it rather obscure compared to various other languages I used.
>> Systemd configuration files are, real configuration files. Plain-text,
>> no XML (this point is important for me), no script (this one too). Just
>> some key-value associations.
>
> I find shell scripts the most efficient way to automate system adin
> tasks. It could be because I am a programmer, but at least init scripts
> are already provided, and small modifications should not be a problem
> even for non-programmers. For new scripts you have 'skeleton' file that
> can be easily adjusted for a particular work.
System init scripts are not an "admin task", they're a system task.
Anyway, writing an upstart job or a systemd service is far simpler
than writing a dash init script.
Furthermore, if you want to do more than "/path/to/<executable>
<parameters>" using either upstart or systemd, you can.
Reply to: