Am Fr., 7. Okt. 2022 um 09:24 Uhr schrieb Klaus Ebbe Grue <grue@xxxxxxxx>: > QUESTION: Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily? Unfortunately not. You'd need some kind of "maintenance" mode you could put a service in, where systemd would keep the socket open but just queues the requests until the service is put out of maintenance mode again. There is no such feature atm although I would have found that useful for Debian as well (during package upgrades). The best you can currently do is probably to stop the .socket to avoid accidental activation during the upgrade.
Re: Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily?
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Date: Fri, 7 Oct 2022 09:41:53 +0200
- Cc: "systemd-devel@xxxxxxxxxxxxxxxxxxxxx" <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <91a90e97f41a4da3b7f716727262de84@di.ku.dk>
- References: <91a90e97f41a4da3b7f716727262de84@di.ku.dk>
- Follow-Ups:
- References:
- Prev by Date: Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily?
- Next by Date: Re: Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily?
- Previous by thread: Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily?
- Next by thread: Re: Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily?
- Index(es):
 |