Re: [systemd-devel] systemd-networkd: keeping old routes when new dhcp lease was given

Probably related to this issue https://github.com/systemd/systemd/pull/12350 On Tue, Jun 11, 2019 at 02:25 Kaisrlík, Jan wrote: > Hello here, > > I am running Yocto-thud with systemd 239 on my SoC and I've found > interesting, when DHCP lease was prolonged, I observe the connection > to the

[systemd-devel] Q: Implementing logrotate's postrotate with systemd

Hi! I have a forking service (with a PID file) that can reopen the logfile after receiving SIGHUP. In the past I had implemented "rc{service} rotate" to send SIGHUP to the daemon as "postrotate" action. After converting (actually being converted ;-)) to systemd I dropped the LSB script, and

Re: [systemd-devel] Q: Implementing logrotate's postrotate with systemd

A separate oneshot service sounds like overkill. I would probably use something like `systemctl kill -s HUP ${service}.service` If your sevices spawns multiple processes and you only want to send SIGHUP to the main process, you should add a `--kill-who=main` All documented nicely in

[systemd-devel] systemd-networkd: keeping old routes when new dhcp lease was given

Hello here, I am running Yocto-thud with systemd 239 on my SoC and I've found interesting, when DHCP lease was prolonged, I observe the connection to the internet was completely stopped. Based on the logs in the system I strongly believe it is connected to moment when networkd renews a dhcp

Re: [systemd-devel] keyrings and dbus

On Tue, Jun 11, 2019 at 1:08 PM Josef Moellers wrote: > Hi, > > We have seen this problem: when you open a gnome-terminal, then the > shell in that terminal will not have the same keyring (created by > pam_keyinit.so) as the one eg in an xterm. This is due to the fact that > the xterm ist

[systemd-devel] Antw: Re: Q: Implementing logrotate's postrotate with systemd

>>> Michael Biebl schrieb am 11.06.2019 um 14:13 in Nachricht : > A separate oneshot service sounds like overkill. I would probably use > something like > `systemctl kill -s HUP ${service}.service` > If your sevices spawns multiple processes and you only want to send > SIGHUP to the main process,

Re: [systemd-devel] keyrings and dbus

On 11.06.19 12:45, Mantas Mikulėnas wrote: > On Tue, Jun 11, 2019 at 1:08 PM Josef Moellers > wrote: > > Hi, > > We have seen this problem: when you open a gnome-terminal, then the > shell in that terminal will not have the same keyring (created by >

Re: [systemd-devel] keyrings and dbus

On Tue, Jun 11, 2019 at 1:58 PM Josef Moellers wrote: > On 11.06.19 12:45, Mantas Mikulėnas wrote: > > On Tue, Jun 11, 2019 at 1:08 PM Josef Moellers > > wrote: > > > > Hi, > > > > We have seen this problem: when you open a gnome-terminal, then the > >

Re: [systemd-devel] Q: Implementing logrotate's postrotate with systemd

Am 11.06.19 um 13:34 schrieb Ulrich Windl: > I have a forking service (with a PID file) that can reopen the logfile after > receiving SIGHUP. In the past I had implemented "rc{service} rotate" to send > SIGHUP to the daemon as "postrotate" action. After converting (actually being > converted

[systemd-devel] keyrings and dbus

Hi, We have seen this problem: when you open a gnome-terminal, then the shell in that terminal will not have the same keyring (created by pam_keyinit.so) as the one eg in an xterm. This is due to the fact that the xterm ist started by the standard fork/exec mechanism which passes the keyring down

Re: [systemd-devel] keyrings and dbus

On 11.06.19 13:27, Mantas Mikulėnas wrote: > On Tue, Jun 11, 2019 at 1:58 PM Josef Moellers The point is that in the gnome-terminal case, pam_keyinit.so is not > involved. > > > It is. The systemd --user instance (from which dbus-daemon and > gnome-terminal-server descend) has its own

Re: [systemd-devel] keyrings and dbus

On 11.06.19 14:32, Josef Moellers wrote: > On 11.06.19 13:27, Mantas Mikulėnas wrote: >> On Tue, Jun 11, 2019 at 1:58 PM Josef Moellers >> The point is that in the gnome-terminal case, pam_keyinit.so is not >> involved. >> >> >> It is. The systemd --user instance (from which dbus-daemon

[systemd-devel] Antw: Re: Q: Implementing logrotate's postrotate with systemd

>>> Reindl Harald schrieb am 11.06.2019 um 14:30 in Nachricht <917331d8-845f-54d5-908c-e6c7d124a...@thelounge.net>: > > Am 11.06.19 um 13:34 schrieb Ulrich Windl: >> I have a forking service (with a PID file) that can reopen the logfile after > receiving SIGHUP. In the past I had implemented

Re: [systemd-devel] Antw: Re: Q: Implementing logrotate's postrotate with systemd

Am 11.06.19 um 15:00 schrieb Ulrich Windl: Reindl Harald schrieb am 11.06.2019 um 14:30 in > Nachricht <917331d8-845f-54d5-908c-e6c7d124a...@thelounge.net>: >> >> Am 11.06.19 um 13:34 schrieb Ulrich Windl: >>> I have a forking service (with a PID file) that can reopen the logfile >>>

Re: [systemd-devel] Antw: Re: Q: Implementing logrotate's postrotate with systemd

Am Di., 11. Juni 2019 um 15:00 Uhr schrieb Ulrich Windl : > > >>> Reindl Harald schrieb am 11.06.2019 um 14:30 in > Nachricht <917331d8-845f-54d5-908c-e6c7d124a...@thelounge.net>: > > > > > Am 11.06.19 um 13:34 schrieb Ulrich Windl: > >> I have a forking service (with a PID file) that can reopen

Re: [systemd-devel] coredump missing in systemd

Where are coredump now : systemctl status systemd-coredump.socket Failed to dump process list, ignoring: No such file or directory ● systemd-coredump.socket - Process Core Dump Socket Loaded: loaded (/lib/systemd/system/systemd-coredump.socket; static; vendor preset: enabled) Active:

[systemd-devel] dirsrv fails to start

Hi All, Everything has been working great until now. Suddonly one of our IDM servers is no longer able to start IPA services. We keep running into an issue with Dirsrv failing to start " see logs below" ( replaced domain name with for privacy ) Unit dirsrv@.service has failed. -- --

[systemd-devel] Anybody care to fix the list processor?

Hi! Does anybody running the list care to fix the list-processor. The welcome message says: You can also make such adjustments via email by sending a message to: systemd-devel-requ...@lists.freedesktop.org What you get is: The mail system : host

Re: [systemd-devel] Anybody care to fix the list processor?

On Tue, 11 Jun 2019 at 15:44:07 +0200, Ulrich Windl wrote: > Does anybody running the list care to fix the list-processor. I don't think the members of this list control its infrastructure, but I've opened . smcv

Re: [systemd-devel] Antw: Re: Q: Implementing logrotate's postrotate with systemd

Am Di., 11. Juni 2019 um 16:18 Uhr schrieb Reindl Harald : > > > > Am 11.06.19 um 15:00 schrieb Ulrich Windl: > Reindl Harald schrieb am 11.06.2019 um 14:30 in > > Nachricht <917331d8-845f-54d5-908c-e6c7d124a...@thelounge.net>: > >> > >> Am 11.06.19 um 13:34 schrieb Ulrich Windl: > >>> I