journald: use argv0 for syslog identifier #3372
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The libsystemd code is documented to determine the syslog identifier by using https://man7.org/linux/man-pages/man3/program_invocation_short_name.3.html (a glibc thing). This code is parsing via looking at `/proc/self/exe`. Often, these things are the same, but in my case they're not because for unfortunate reasons I need to re-exec the current binary in a tempfile. It's actually simpler and more reliable for us anyways to match what libsystemd is doing by looking at argv[0]. Signed-off-by: Colin Walters <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The libsystemd code is documented to determine the syslog identifier by using
https://man7.org/linux/man-pages/man3/program_invocation_short_name.3.html (a glibc thing).
This code is parsing via looking at
/proc/self/exe.Often, these things are the same, but in my case they're not because for unfortunate reasons I need to re-exec the current binary in a tempfile.
It's actually simpler and more reliable for us anyways to match what libsystemd is doing by looking at argv[0].