[systemd-devel] [PATCH 1/2] Report about syntax error in extended format

[Oleksii Shevchuk]

> The working assumption in systemd is that the journal is available,
> can can be used. So it storing messages in systemd (patch 2/2) goes against
> current design.

I thought about that, but that is not right I think. Journal is not the
place to store the state. It can be rotated, It can be disabled at all. For
example, we store ExitFailure status in unit state, not in journal. I
think that is important to store messages like these in objects itself.

> Also:
> why not use one MESSAGE_ID? The messages are in the same format with the
> same meaning, and their severity can be filtered separately.

Yes, now I think that MESSAGE_ID should be the same

> FILE,LINE are about the *origin* of the message, so something
> different should be used for the *object* (CONFIG_FILE,CONFIG_LINE?).
Agree