← Back to context Comment by post-it 1 day ago Multiple levels of logging, all of which you want to capture but not all in the same place. 3 comments post-it Reply skydhash 1 day ago Wasn't the idiomatic way the `-v` flag (repeated for verbosity). And then stderr for errors (maybe warning too). post-it 10 hours ago Yes, but sometimes you want just important non-error logs to go to the console or journal, and then those plus verbose logs to go to a file that gets rotated, and then also stderr on top of that. notpushkin 21 hours ago It is, and all logs should ideally go to stderr. But that doesn’t let you pipe them to different places.
skydhash 1 day ago Wasn't the idiomatic way the `-v` flag (repeated for verbosity). And then stderr for errors (maybe warning too). post-it 10 hours ago Yes, but sometimes you want just important non-error logs to go to the console or journal, and then those plus verbose logs to go to a file that gets rotated, and then also stderr on top of that. notpushkin 21 hours ago It is, and all logs should ideally go to stderr. But that doesn’t let you pipe them to different places.
post-it 10 hours ago Yes, but sometimes you want just important non-error logs to go to the console or journal, and then those plus verbose logs to go to a file that gets rotated, and then also stderr on top of that.
notpushkin 21 hours ago It is, and all logs should ideally go to stderr. But that doesn’t let you pipe them to different places.
Wasn't the idiomatic way the `-v` flag (repeated for verbosity). And then stderr for errors (maybe warning too).
Yes, but sometimes you want just important non-error logs to go to the console or journal, and then those plus verbose logs to go to a file that gets rotated, and then also stderr on top of that.
It is, and all logs should ideally go to stderr. But that doesn’t let you pipe them to different places.