Mailinglist Archive: opensuse (1239 mails)

< Previous Next >
Re: [opensuse] systemd: What is the proper manner to print a message to the screen from a service file?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Mon, 17 Jun 2013 01:20:56 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.1306170110070.6527@Telcontar.valinor>
Hash: SHA1

Content-ID: <alpine.LNX.2.00.1306170112530.6527@Telcontar.valinor>

On Sunday, 2013-06-16 at 19:05 -0400, Cristian Rodríguez wrote:

nothing else is needed...

My idea is to have a small summary at the end of the boot process, printed in tty1, and I have it now. I boot in text mode, verbose, I like to see the messages, and the summary at the end just in case I missed some.

This command:

grep FAILED /var/log/boot.log

prduces exactly what I would like, but the file is not generated always, so it can not be relied uppon:

Telcontar:~ # grep FAILED /var/log/boot.log
[FAILED] Failed to start Load Kernel Modules.
[FAILED] Failed to start LSB: Console mouse support.
[FAILED] Failed to start Daemonized version of spamassassin.
[FAILED] Failed to start Network Manager Wait Online.

So instead I'm using this:

Telcontar:~ # systemctl --failed --no-pager
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Telcontar:~ # ·······································++-

but the format is not so nice. I would prefer it at least to print nothing if nothing failed.

- -- Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
Version: GnuPG v2.0.19 (GNU/Linux)

< Previous Next >