On Fri, Jan 28, 2022 at 10:50 AM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> Hi!
>
> When upgrading SLES15 to SP3, a newer version of systemd was installed
> (246.16+suse.191.g3850086c65).
> Since then I see new journal messages like these that I cannot associate
> with a unit:
>
>
On Fri, Jan 28, 2022, 11:59 Ulrich Windl
wrote:
> >>> Mantas Mikulenas schrieb am 28.01.2022 um 10:27 in
> Nachricht
> :
> > On Fri, Jan 28, 2022 at 10:50 AM Ulrich Windl <
> > ulrich.wi...@rz.uni-regensburg.de> wrote:
> >
> >> Hi!
> >>
> >> When upgrading SLES15 to SP3, a newer version of
Hi!
When upgrading SLES15 to SP3, a newer version of systemd was installed
(246.16+suse.191.g3850086c65).
Since then I see new journal messages like these that I cannot associate with a
unit:
Jan 27 09:29:30 h16 systemd[1]: var-tmp-AP_0xC5KDJP.mount: Succeeded.
Jan 27 09:29:30 h16
>>> Mantas Mikulenas schrieb am 28.01.2022 um 10:27 in
Nachricht
:
> On Fri, Jan 28, 2022 at 10:50 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> When upgrading SLES15 to SP3, a newer version of systemd was installed
>> (246.16+suse.191.g3850086c65).
>> Since then I
Try to set the systemd user instance's log level to 'debug'; I'm guessing
it's not that systemd kills processes directly but that something triggers
a 'systemctl stop' of the session .scope that they were in.
Can't think of any events directly related to monitor wakeup that systemd
would react to
On Sa, 22.01.22 14:08, www (ouyangxua...@163.com) wrote:
> Dear all,
>
>
> When using sd_bus_process() + sd_bus_wait() to implement the
> application(Service), call the methods function on the service can obtain the
> correct information. Run a certain number of times will lead to
>
> Try to set the systemd user instance's log level to 'debug'; I'm guessing
> it's not that systemd kills processes directly but that something triggers
> a 'systemctl stop' of the session .scope that they were in.
Here are the logs at debug level with some annotations inline:
**
Jan 28
