Bug#764481: systemd: Verbosity in journalctl is lacking

Brian Potkin claremont102 at gmail.com
Wed Oct 8 18:56:58 BST 2014


On Wed 08 Oct 2014 at 16:37:11 +0200, Michael Biebl wrote:

> Am 08.10.2014 um 16:04 schrieb Brian Potkin:
> > 
> > The same command under systemd 215-5 produced:
> > 
> >   Oct 08 14:51:01 jessie-b2 sshd[375]: Received signal 15; terminating.
> >   Oct 08 14:51:01 jessie-b2 dnsmasq[392]: reading /etc/resolv.conf
> >   Oct 08 14:51:01 jessie-b2 dnsmasq[392]: using nameserver 192.168.7.1#53
> >   Oct 08 14:51:01 jessie-b2 dnsmasq[392]: exiting on receipt of SIGTERM
> >   Oct 08 14:51:01 jessie-b2 exim4[735]: Stopping MTA: exim4_listener.
> >   Oct 08 14:51:01 jessie-b2 gpm[749]: Stopping mouse interface server: gpm.
> > 
> > Apart from no "Stopping....." for the non-LSB services there is no record
> > at all cron or cups. Stopping, starting or restarting any of cups.service
> > cups.socket and cups.path leaves no trace in journalctl. There appears to
> > be nothing in the /etc configuration files to account for this.
> > 
> 
> If you always want the status message in the logs, you can use
> systemd.show_status=true
> This behaviour changed slightly with v215 [1]

Thank you.

I never thought of trying an option which is aimed at showing service
status updates when booting. The suggestion works (with "quiet" scrubbed
from the kernel command line) but it would be nice to have the previous
behaviour. And why some status messages are shown is still a mystery.

Please deal with this report as you see fit.

Regards,

Brian.




More information about the Pkg-systemd-maintainers mailing list