Hi,
We have during boot received the "Supervising process..." warning from systemd
related to chronyd.service. This is not always happening, but when it happens
systemd receives SIGCHLD from grand-parent (22955) before the parent (22956).
See logs below:
Oct 25 10:34:55.104980 axis-accc8ed1c
On Mo, 31.10.22 08:04, Christopher Wong (christopher.w...@axis.com) wrote:
> Hi,
>
>
> We have during boot received the "Supervising process..." warning
> from systemd related to chronyd.service. This is not always
> happening, but when it happens systemd receives SIGCHLD from
> grand-parent (2295
On Mo, 31.10.22 11:40, Lennart Poettering (lenn...@poettering.net) wrote:
> This is almost certainly a bug in chrony. If you use Type=forking,
> then the process that systemd forks off (let's call it "P") should
> wait until all of the below holds:
>
> 1. The middle child P' has exited
> 2. The gr
On 10/26/22 20:44, Thomas HUMMEL wrote:
Hello,
I'm not sure if this is a systemd-resolved or NetworkManager question
but it involves both (I know Thomas HALLER is a member of this list too)
on
Fedora release 36 (Thirty Six) using the following kernel and packages
5.19.16-200.fc36.x86_64
I had my focus on the child (main daemon process), therefore the term went
backward parent and grand-parent. Sorry, if that caused confusion, but let's go
with your definitions.
Thank you for the explanation and pointing out the steps! Especially 1. makes
it much clearer than the list describe
🎆 A new, official systemd release has just 🎉 been 🎊 tagged 🍾. Please download
the tarball here:
https://github.com/systemd/systemd/archive/v252.tar.gz
Changes since the previous release:
Announcements of Future Feature Removals:
* We intend to remove cgroup v1 support f
