Sujet : Re: Faking a TTY on a pipe/socketpair
De : Muttley (at) *nospam* DastardlyHQ.org
Groupes : comp.unix.programmerDate : 13. Dec 2024, 11:38:51
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vjh2rr$3c08v$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
On Thu, 12 Dec 2024 22:31:50 -0000 (UTC)
Lawrence D'Oliveiro <
ldo@nz.invalid> wibbled:
On Thu, 12 Dec 2024 08:39:07 -0000 (UTC), Muttley wrote:
The trouble is with any support scripts, not with init. I've written a
number of init scripts with a lot of surrounding logic.
>
I’m sure you have. Which means you are familiar with the wholesale copying
and pasting of boilerplate from one script to the next. “What does this
bit do?” “Don’t bother thinking too hard, just stick it in, just in
case.”
Its a few lines of code and usually one just copies a simple rc file and
starts from there.
God knows how I'd do that with systemd ...
>
Figure out what the directives do (they’re all documented), and which
Why TF would I want to have to leanr Yet Another Config Language when in
shell script I have a turing complete language that can do anything with the
system? You might as well say "Don't bother with that car, use this pushbike
instead."
Poettering created the wrong solution to the wrong problem.
>
Lots of sysadmins, and distro maintainers, and developers of service apps,
disagree.
Sheep exist even i open source. That other abortion poetrring wrote pulseaudio
was shoved into every distro until people realised that all it did was
remove the complexity of Alsa and add its own complexity in exchange. And
being built on alsa it simply added another layer and hence delay into the
sound system where you REALLY don't want delays.
Think of how simple it is to log error messages now: systemd automatically
captures stderr, and shows it in your service status and in the journal.
Oh wow, is there no end to its magical abilities!