Re: Two line init.d scripts? Sure, that will work!
Matthias Urlichs <smurf@smurf.noris.de> writes:
> Oh except that some people didn't, which causes problems for the systemd
> transition -- because init skript that are not skeleton-based don't know
> how to redirect itself to systemd …
Err, no. I have plenty of sysvinit scripts that work just fine with
systemd, and are not at all based on skeleton.
> I'd much rather have something well-tested and upgradeable which takes the
> five lines you actually need for the common case(!) from a working systemd
> service file and produces a sensible init script from that.
I'd much rather support one init system that works instead of trying to
find workarounds for something that ended up being terrible.
Even if you generate an init script from systemd service files, the end
result will be terrible, on the same level as the current sysvinit
situation is. There's a reason it has not been done neither for upstart,
nor for systemd: it's not worth it.
--
|8]
Reply to: