Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jim Jackson <jj@franjam.org.uk>
Newsgroups: comp.unix.programmer
Subject: Re: Faking a TTY on a pipe/socketpair
Date: Wed, 18 Dec 2024 21:19:09 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <slrnvm6f2d.dr1.jj@iridium.wf32df>
References: <vh9vgr$5bb$1@dont-email.me> <vj91a1$t8pn$1@dont-email.me>
 <vja9r8$14k6s$1@dont-email.me> <vjbiop$1f2e5$1@dont-email.me>
 <vjd3jg$1od5c$3@dont-email.me> <slrnvlk56u.2qa.jj@iridium.wf32df>
 <675a218f$0$12912$426a34cc@news.free.fr> <slrnvlp50u.29n.jj@iridium.wf32df>
 <vjib38$3kiac$2@dont-email.me> <slrnvlr8hp.49d.jj@iridium.wf32df>
 <vjl0m0$68i1$4@dont-email.me> <slrnvm1cei.adn.jj@iridium.wf32df>
 <vjqo9n$1dk7j$2@dont-email.me>
Injection-Date: Wed, 18 Dec 2024 22:19:10 +0100 (CET)
Injection-Info: dont-email.me; posting-host="dca54af08216e212df3f617cc09b91ac";
	logging-data="2604264"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+4Yb0+DiUeNlvP/ioarIh84mF4R7C5TPI="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:k119EMXn4wTcU0K0/EzARslo+Iw=
Bytes: 2628

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.