Sujet : Re: Faking a TTY on a pipe/socketpair
De : jj (at) *nospam* franjam.org.uk (Jim Jackson)
Groupes : comp.unix.programmerDate : 18. Dec 2024, 22:19:09
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <slrnvm6f2d.dr1.jj@iridium.wf32df>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13
User-Agent : slrn/1.0.3 (Linux)
On 2024-12-17, Lawrence D'Oliveiro <
ldo@nz.invalid> wrote:
On Mon, 16 Dec 2024 23:03:46 -0000 (UTC), Jim Jackson wrote:
>
Ok I've done specific network monitoring stuff from scratch - back in
the day, when SNMP was a new thing. But it was easier to control than
other stuff because I (and a couple of others) wrote it - we knew it -
so what's difficult? We even transitioned it from pre-SYS-V init to
SYS-V init, and I remember no difficulties.
>
Anything with this <https://www.phoronix.com/news/Facebook-systemd-2018>
level of complexity?
Of course not - what a silly question. And the interesting thing was
that their set up is SO complicated systemd is only a part of their
solutions, which is sort of obvious. I'd have been more interested in a
comparison of previous set up v. current with systemd.
Their process for non-stop upgrades was a fairly standard one of old
service handing over to new and having to notify and co-operate with
systemd because systemd handles new connections. Previously I suspect
their processes handled incoming connections directly and there would
have been process-process link to do the hand over. Which one works out
easier to program and manage I'm not sure. But given they'd gone for a
solution Centos which had systemd init they had to adapt to it.
Anyway it was interesting thanks for the pointer.