What is the reason behind logging unit's description? Consider the following
journal message (from `journalctl -b`):

  systemd[1]: Starting A secure, fast, compliant and very flexible web-server...

It shows some fancy stuff about the started unit, but does not point to any
particular unit as the description is ambiguous at best.

Adding the -x option to journalctl will also show the following message:

  -- Unit lighttpd.service has begun starting up.

OK, there is a way to identify the unit, but from journalctl(1):

  Note: when attaching journalctl output to bug reports, please do not use -x.

So, if the -x option is not-so-wanted, why is the unit not identified by its
name in the default output? This would also make the default journal output
unambiguous regardless of the units' descriptions.

Regards,
Jakub Klinkovský

Attachment: pgpU8sf5Dkc5o.pgp
Description: PGP signature

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to