Re: [systemd-devel] [EXT] Re: Q: "systemd-journald: ... /system.journal: Journal file uses a different sequence number ID, rotating."

2025-02-06 Thread Windl, Ulrich
Andrei, you are right; it's just that there are so many bugs there 😉 Kind regards, Ulrich Windl > -Original Message- > From: Andrei Borzenkov > Sent: Friday, February 7, 2025 7:17 AM > To: Windl, Ulrich ; systemd-devel@lists.freedesktop.org > Subject: [EXT] Re: [systemd-devel] Q: "syste

Re: [systemd-devel] Q: "systemd-journald: ... /system.journal: Journal file uses a different sequence number ID, rotating."

2025-02-06 Thread Andrei Borzenkov
07.02.2025 08:57, Windl, Ulrich wrote: Hi! When upgrading SLES 15 from SP5 to SP6 also involved updating systemd (from 249 to 254): On first boot I noticed the message "systemd-journald[673]: /var/log/journal/aefe6ef1acb28655ef1a2fa8610cef2b/system.journal: Journal file uses a different seque

Re: [systemd-devel] Q: "systemd-journald: ... /system.journal: Journal file uses a different sequence number ID, rotating."

2025-02-06 Thread Windl, Ulrich
I noticed that systemd-journald has an option to "rotate" the journal, but I could not find a manpage that explains what "rotation" actually means. Kind regards, Ulrich Windl

[systemd-devel] Q: "systemd-journald: ... /system.journal: Journal file uses a different sequence number ID, rotating."

2025-02-06 Thread Windl, Ulrich
Hi! When upgrading SLES 15 from SP5 to SP6 also involved updating systemd (from 249 to 254): On first boot I noticed the message "systemd-journald[673]: /var/log/journal/aefe6ef1acb28655ef1a2fa8610cef2b/system.journal: Journal file uses a different sequence number ID, rotating." That was kind o

Re: [systemd-devel] How to stop child cgroup caused by PAMName=

2025-02-06 Thread Mantas MikulÄ—nas
On Thu, Feb 6, 2025 at 1:55 PM Dluhosch, Michael < michael.dluho...@airbus.com> wrote: > We use this service to control various sub-processes on a shared computer > and in the past without the PAMName we noticed that the processes behaved > differently than on our own computers where we are logged

Re: [systemd-devel] How to stop child cgroup caused by PAMName=

2025-02-06 Thread Lennart Poettering
On Do, 06.02.25 08:25, Dluhosch, Michael (michael.dluho...@airbus.com) wrote: > Hello, > > > I want a service which executes 'startFoo.sh' exactly like a user 'Foo' would > experience it. This is my current approach: > > [Service] > ExecStart=/usr/bin/startFoo.sh > > User=Foo > > PAMName=login >

Re: [systemd-devel] How to stop child cgroup caused by PAMName=

2025-02-06 Thread Dluhosch, Michael
We use this service to control various sub-processes on a shared computer and in the past without the PAMName we noticed that the processes behaved differently than on our own computers where we are logged in with our users. For example it was not aware of the settings in /etc/security/limits.d/

Re: [systemd-devel] How to stop child cgroup caused by PAMName=

2025-02-06 Thread Mantas MikulÄ—nas
On Thu, Feb 6, 2025 at 10:29 AM Dluhosch, Michael < michael.dluho...@airbus.com> wrote: > Hello, > > > I want a service which executes 'startFoo.sh' exactly like a user 'Foo' > would experience it. This is my current approach: > > [Service] > ExecStart=/usr/bin/startFoo.sh > > User=Foo > > PAMName

Re: [systemd-devel] How to stop child cgroup caused by PAMName=

2025-02-06 Thread Tomasz Pala
On Thu, Feb 06, 2025 at 08:25:06 +, Dluhosch, Michael wrote: > PAMName=login [...] > ExecStop=/usr/bin/stopFoo.sh > > to the main service which does that: > > #!/bin/bash Don't use bash for scripts. > systemctl stop $(systemctl status $(pidof > ) | grep user.*slice | grep -o > session.*s

[systemd-devel] How to stop child cgroup caused by PAMName=

2025-02-06 Thread Dluhosch, Michael
Hello, I want a service which executes 'startFoo.sh' exactly like a user 'Foo' would experience it. This is my current approach: [Service] ExecStart=/usr/bin/startFoo.sh User=Foo PAMName=login And it seems to work just fine. But I can't figure out how to stop this service and all of its ch