Hi!
We all know that using the journald native API it is possible to enrich the log
entry data w/ key/value pairs, although this facility is Linux only.
The set of key/value pairs which a message may log to the journal can
constitute an API with which a logging entity can communicate alerts to
I was advised on IRC to post this issue here after trying IRC, forums,
searches, man pages, wikis, etc.
During init, systemd asks for the passphrase of non-root LUKS drives when
they are added to crypttab even though a keyfile is specified. The keyfile
is the same one I'm using to open (old)
On Thu, 23.07.15 08:55, SF Markus Elfring (elfr...@users.sourceforge.net) wrote:
Heya,
I would like to continue the clarification of open issues
around a topic like Completion of error handling.
https://github.com/systemd/systemd/issues/644
I hope that the amount of unchecked return values
Hi
Following our ~2 week release plans, we intend to release v223 early
next week. If anyone has open issues that need to be resolved before a
release, please speak up.
Right now, the changes consist of mostly bugfixes and a few
configuration additions. I'll commit the full NEWS tomorrow.
On Thu, 23.07.15 09:17, Anne Mulhern (amulh...@redhat.com) wrote:
Hi!
We all know that using the journald native API it is possible to enrich the
log
entry data w/ key/value pairs, although this facility is Linux only.
The set of key/value pairs which a message may log to the journal can
Hello,
I would like to continue the clarification of open issues
around a topic like Completion of error handling.
https://github.com/systemd/systemd/issues/644
I hope that the amount of unchecked return values can be reduced
further in affected source files by the reuse of dedicated
software
