[systemd-devel] [PATCH] [RFC] umount: reduce verbosity

[Lennart Poettering]

On Mon, 13.04.15 13:13, Alban Crequy (alban.crequy at gmail.com) wrote:

> From: Alban Crequy <alban at endocode.com>
> 
> When a systemd-nspawn container terminates, systemd umounts all bind
> mounts that were mounted in the container and generates a log for each
> umount.
> 
> This additional log_info was added by
> bce93b7ac7642426039863493694d8c12812e2a7 for debugging shutdown. But
> surely log_debug is enough.
> 
> I don't want to see them when when systemd is started with --log-target=null.
> There are other log_info that I would like to mute on --log-target=null.
> Is changing log_info to log_debug the correct approach?

Hmm, I kinda like these messages I must say, because they actually
help users if the shutdown hangs.

Hmm, if you specify --log-target=null then then the messages should
go nowhere anyway.

We actually pass the log target setting from systemd to the shutdown
binary via a command line. Are you suggesting that this doesn't work
correctly? That#s something to debug first, I figure?

> This patch is useful for:
> https://github.com/coreos/rkt/issues/690
> 
> When rkt is started with --debug, the systemd logs are printed. When rkt
> is started without --debug, systemd is started with --log-target=null in
> order to mute the logs.

That generally sounds a bit extreme...

Lennart

-- 
Lennart Poettering, Red Hat