Update xenium.service to output to journal #4
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
Was having an issue with a headless version of raspbian OS where it was not logging phython3 output
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.
Was having an issue with a headless version of raspbian OS where it was not logging phython3 output
With that said, up until I swapped to a headless version of the OS I was seeing all the logs coming through to my
journalctl -u xenium.service -fwatch, but I started to only get service start/stop logs coming up for some reason.This change also doesn't resolve the issue that the downstream python scripts it launches (i.e. PromOS-programmer-smd) are also not outputing to the journal.
Would happily close this PR if it turns out I am just bad at linux (very likely) and there is a better way to get my logging working properly