You wrote: > Is it actually 3.10 *pretending* to be 5.4 just to make it pass systemd's kernel version checks? Correct. The host machines runs 3.10 and via an OpenVZ configuration for the container you can overwrite the kernel version in the container that is reported via "uname -a". -- Erik Wasser
Re: systemctl daemon-reexec forgets running services and starts everything new
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: systemctl daemon-reexec forgets running services and starts everything new
- From: "Wasser, Erik" <ewasser@xxxxxxxxxxxxx>
- Date: Mon, 17 Apr 2023 16:17:23 +0200
- Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
- In-reply-to: <CAPWNY8VVUtHQSavt1pXA3_k83ZOHNpTuboE33vxt_ciRzkJN+Q@mail.gmail.com>
- References: <CAAVk8vysR5YZXC6UUjrNWCpRsCkWK1+TuQXC3RmfQ5n+_MaqaQ@mail.gmail.com> <CAPWNY8VVUtHQSavt1pXA3_k83ZOHNpTuboE33vxt_ciRzkJN+Q@mail.gmail.com>
- References:
- systemctl daemon-reexec forgets running services and starts everything new
- From: Wasser, Erik
- Re: systemctl daemon-reexec forgets running services and starts everything new
- From: Mantas Mikulėnas
- systemctl daemon-reexec forgets running services and starts everything new
- Prev by Date: Re: systemctl daemon-reexec forgets running services and starts everything new
- Next by Date: One shot service failure on Fedora 37
- Previous by thread: Re: systemctl daemon-reexec forgets running services and starts everything new
- Next by thread: creating device nodes
- Index(es):
 |