Re: [systemd-devel] soft-reboot and surviving it

2024-05-31 Thread Luca Boccassi
On Wed, 8 May 2024 at 14:22, Thorsten Kukuk wrote: > > Hi, > > attached is a better reproducer for the "broken pipe" problem, if > applications write to stderr. This time without buffered glibc > streams. > If writing to stderr (fd 2) fails, the error get's logged via > sd_journal_print(). This h

Re: [systemd-devel] soft-reboot and surviving it

2024-05-08 Thread Thorsten Kukuk
Hi, attached is a better reproducer for the "broken pipe" problem, if applications write to stderr. This time without buffered glibc streams. If writing to stderr (fd 2) fails, the error get's logged via sd_journal_print(). Regards, Thorsten On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi wrote:

Re: [systemd-devel] soft-reboot and surviving it

2024-04-29 Thread Thorsten Kukuk
On Sat, Apr 20, 2024 at 8:21 PM Luca Boccassi wrote: > > On Sat, 20 Apr 2024 at 01:45, Cristian Rodríguez > wrote: > > > > On Fri, Apr 19, 2024 at 6:17 AM Thorsten Kukuk wrote: > > > > > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > > > wrote: > > > > > > > However, logging should work ou

Re: [systemd-devel] soft-reboot and surviving it

2024-04-29 Thread Thorsten Kukuk
Sorry for the late response, we had a conference last week. On Sat, Apr 20, 2024 at 8:18 PM Luca Boccassi wrote: > Having no dependency on the rootfs is a core requirement that we > cannot change, the filesystem used is irrelevant. It's not going to > work, it will break immediately if you are l

Re: [systemd-devel] soft-reboot and surviving it

2024-04-20 Thread Luca Boccassi
On Sat, 20 Apr 2024 at 01:45, Cristian Rodríguez wrote: > > On Fri, Apr 19, 2024 at 6:17 AM Thorsten Kukuk wrote: > > > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > > wrote: > > > > > However, logging should work out of the box as long as the journal is > > > used, what problem are you se

Re: [systemd-devel] soft-reboot and surviving it

2024-04-20 Thread Luca Boccassi
On Fri, 19 Apr 2024 at 12:50, Thorsten Kukuk wrote: > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > wrote: > > On Fri, 19 Apr 2024 at 10:30, Thorsten Kukuk wrote: > > > > And now I started looking into how services can survive the > > > soft-reboot. I know the FOSDEM talk from Luca about t

Re: [systemd-devel] soft-reboot and surviving it

2024-04-19 Thread Cristian Rodríguez
On Fri, Apr 19, 2024 at 6:17 AM Thorsten Kukuk wrote: > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > wrote: > > > However, logging should work out of the box as long as the journal is > > used, what problem are you seeing exactly? > > Starting around the shutdown and new start of systemd-j

Re: [systemd-devel] soft-reboot and surviving it

2024-04-19 Thread Thorsten Kukuk
On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi wrote: > On Fri, 19 Apr 2024 at 10:30, Thorsten Kukuk wrote: > > And now I started looking into how services can survive the > > soft-reboot. I know the FOSDEM talk from Luca about this topic, but I > > don't like to move the application into anothe

Re: [systemd-devel] soft-reboot and surviving it

2024-04-19 Thread Thorsten Kukuk
On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi wrote: > However, logging should work out of the box as long as the journal is > used, what problem are you seeing exactly? Starting around the shutdown and new start of systemd-journald during soft-reboot, all writes to stderr will result in an err

Re: [systemd-devel] soft-reboot and surviving it

2024-04-19 Thread Luca Boccassi
On Fri, 19 Apr 2024 at 10:30, Thorsten Kukuk wrote: > > Hi, > > we finished the integration of soft-reboot into openSUSE Tumbleweed > and MicroOS (transactional-update), and the major problems except > firewalld+podman are solved. Now we only need to do all the "fine > tuning". > Is there meanwhil

[systemd-devel] soft-reboot and surviving it

2024-04-19 Thread Thorsten Kukuk
Hi, we finished the integration of soft-reboot into openSUSE Tumbleweed and MicroOS (transactional-update), and the major problems except firewalld+podman are solved. Now we only need to do all the "fine tuning". Is there meanwhile any reliable/official way to detect that this was a soft-reboot? T