Liste des Groupes | Revenir à cu programmer |
Jim Jackson <jj@franjam.org.uk> writes:>>
>
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.
Modern non-stop systems route new connections at a higher level (e.g. netscaler)
for both load balancing and resiliancy. systemd is not (thankfully)
involved in that at all.
Les messages affichés proviennent d'usenet.