[systemd-devel] How to figure out what's causing systemd to start printing messages partway through boot?

[McKay, Sean]

Hi Lennart,

I've had debug logging on for a while (it's mentioned in my first email, but I concede that was rather long). Unfortunately, I will admit to not being particularly familiar with dbus or the signals I should be looking for.

Is there a direction you could point me in (either documentation, or even in the code itself) that would help me familiarize myself with them so I can follow what's happening to try to figure out what could be changing that value?

The part that I really don't understand is that the only place that I can find where the value seems to be modified is in the manager_set_show_status function. That function has a debug log in it, but when I enable debug logging, it's nowhere to be found in the journal despite the value being toggled from auto to temporary.

Cheers!
-Sean

-----Original Message-----
From: Lennart Poettering <lennart at poettering.net> 
Sent: Wednesday, May 6, 2020 8:09 AM
To: McKay, Sean <sean.mckay at hpe.com>
Cc: systemd-devel at lists.freedesktop.org
Subject: Re: [systemd-devel] How to figure out what's causing systemd to start printing messages partway through boot?

On Mi, 29.04.20 23:26, McKay, Sean (sean.mckay at hpe.com) wrote:

> Do you have any guidance on what I should look at to determine what is 
> causing the show_status variable in systemd to get flipped to true 
> without any apparent unit failures? Is there an easy way to find that 
> information?

Maybe something asks systemd to? Consider enabling debug logging with "systemd.log_level=debug" on the kernel cmdline. It will then print information about incoming dbus msgs which might cause this, as well as signals it receives that might cause it.

Lennart

--
Lennart Poettering, Berlin