Restarts of journald

[Jarek Kamiński]

Hello,

#771122 explains that journald can't be restarted, as all stdout and
stderr fds used by daemons to log would be lost. If I understand
correctly, that was fixed in v219[1] though:
>         * systemd now provides a way to store file descriptors
>           per-service in PID 1.This is useful for daemons to ensure
>           that fds they require are not lost during a daemon
>           restart. The fds are passed to the deamon on the next
>           invocation in the same way socket activation fds are
>           passed. This is now used by journald to ensure that the
>           various sockets connected to all the system's stdout/stderr
>           are not lost when journald is restarted. File descriptors
>           may be stored in PID 1 via the sd_pid_notify_with_fds() API,
>           an extension to sd_notify(). Note that a limit is enforced
>           on the number of fds a service can store in PID 1, and it
>           defaults to 0, so that no fds may be stored, unless this is
>           explicitly turned on.

Is it related, or am I mixing things? If yes, can #771122 be reverted?

[1]
https://lists.freedesktop.org/archives/systemd-devel/2015-February/028447.html


-- 
pozdr(); // Jarek