fix: line-buffer stdout so print() reaches redirected logs#631
Merged
Conversation
rc.lua print() writes to stdout, which glibc block-buffers when stdout is not a TTY (somewm-client test, a pipe to tee, journald), so the output never flushed while the compositor ran. Set stdout line-buffered at startup; stderr is already unbuffered.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
print()writes to stdout, which glibc block-buffers when stdout isn't a TTY (somewm-client test, a pipe, journald), so it never flushes while the compositor runs. Line-buffer stdout at startup.Forward-port of #630 (release/1.4). Fixes #622.
Test Plan
main; C-only change, no Lua/spec touched.print()now reaches a| teelog immediately.Checklist
somewm.c)main