[systemd-devel] Systemd debugging option, documentation clarification

[Zbigniew Jędrzejewski-Szmek]

On Wed, May 15, 2013 at 10:28:54PM +0200, John Connor wrote:
> 1: It would be useful for debugging if systemctl had an option to show
> output on the screen (especially output from scripts run under
> systemd), rather than dumping it in a journal which you then have to
> search through.  This should be a command-line option, because you
> would normally use it only for debugging, not for a normal boot. I
> don't know how practicable this would be, but it would be useful.
This wouldn't be particularly useful because of parallelism. Output
from various services would be completely mixed. This wasn't a
problem when things were started sequentially or with just a bit
in parallel. You can try systemd.log_target=console.

> 2 :  the man page for systemd-journalctl  (at least on Open SUSE 12.2)
> mentions that you can filter journal contents using FIELD=value, but
> (except for one example) it
> doesn't indicate what the field identifiers are or where they are
> defined.  It would
> make the journal a lot more usable if it was clear where to find this
> information.
The fields are in the control of the application, so systemd documentation
can't really describe them. For some common ones see systemd.journal-fields(7).

Zbyszek