diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-04-15 22:25:58 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2015-07-05 14:19:19 -0400 |
| commit | 0035bc19b18f0163f5d868debce185a912950cbc (patch) | |
| tree | 38edd37612630e2fa9c74aac087c862e245fa872 /systemd | |
| parent | 6238295ba705b0e2aba4326d33527c762328f79e (diff) | |
| download | python-systemd-0035bc19b18f0163f5d868debce185a912950cbc.tar.gz | |
Report about syntax errors with metadata
The information about the unit for which files are being parsed
is passed all the way down. This way messages land in the journal
with proper UNIT=... or USER_UNIT=... attribution.
'systemctl status' and 'journalctl -u' not displaying those messages
has been a source of confusion for users, since the journal entry for
a misspelt setting was often logged quite a bit earlier than the
failure to start a unit.
Based-on-a-patch-by: Oleksii Shevchuk <alxchk@gmail.com>
Diffstat (limited to 'systemd')
| -rw-r--r-- | systemd/docs/id128.rst | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/systemd/docs/id128.rst b/systemd/docs/id128.rst index 12c28f3..e43776a 100644 --- a/systemd/docs/id128.rst +++ b/systemd/docs/id128.rst @@ -36,3 +36,4 @@ .. autoattribute:: systemd.id128.SD_MESSAGE_UNIT_STARTING .. autoattribute:: systemd.id128.SD_MESSAGE_UNIT_STOPPED .. autoattribute:: systemd.id128.SD_MESSAGE_UNIT_STOPPING + .. autoattribute:: systemd.id128.SD_MESSAGE_CONFIG_ERROR |