Re: Restarts of journald

2017-03-05 Thread Zbigniew Jędrzejewski-Szmek
On Sun, Mar 05, 2017 at 11:57:38PM +0100, Michael Biebl wrote:
> Am 17.01.2017 um 03:51 schrieb Zbigniew Jędrzejewski-Szmek:
> > On Sat, Jan 14, 2017 at 06:40:49PM +0100, Jarek Kamiński wrote:
> >> 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
> 
> [..]
> 
> > There were bugs, fixed only much later. See systemd pull request #4456.
> 
> Zbigniew, do you know if it is safe now to restart journald with v233?
Yes, ttbomk.

Zbyszek

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Restarts of journald

2017-03-05 Thread Michael Biebl
Am 17.01.2017 um 03:51 schrieb Zbigniew Jędrzejewski-Szmek:
> On Sat, Jan 14, 2017 at 06:40:49PM +0100, Jarek Kamiński wrote:
>> 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

[..]

> There were bugs, fixed only much later. See systemd pull request #4456.

Zbigniew, do you know if it is safe now to restart journald with v233?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Restarts of journald

2017-01-16 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Jan 14, 2017 at 06:40:49PM +0100, Jarek Kamiński wrote:
> 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

There were bugs, fixed only much later. See systemd pull request #4456.

Zbyszek



___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Restarts of journald

2017-01-14 Thread Michael Biebl
Hi Jarek

Am 14.01.2017 um 18:40 schrieb 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?

It should be possible now, I think. That said, I feel a bit uneasy doing
that so close to the freeze.
Doing it early in the buster release cycle seems safer.

Would you mind filing a bug report for that?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers