github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #3749] Where to print debug messages (stdout or stderr)? #2365

New issue

Open

opened 2026-05-05 09:02:59 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 09:02:59 -06:00

Owner

Originally created by @smitsohu on GitHub (Nov 13, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3749

While the vast majority of Firejail's debug messages currently go to stdout, occasionally they are printed to stderr as well. I'm curious if there is desire to have a uniform behavior (one way or the other).

Background: When attempting a fix for #2301 I ran into the problem that I cannot print messages to stdout for a short period of time (otherwise Firejail would mix debug info and file content).

Originally created by @smitsohu on GitHub (Nov 13, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3749 While the vast majority of Firejail's debug messages currently go to `stdout`, occasionally they are printed to `stderr` as well. I'm curious if there is desire to have a uniform behavior (one way or the other). Background: When attempting a fix for #2301 I ran into the problem that I cannot print messages to `stdout` for a short period of time (otherwise Firejail would mix debug info and file content).

gitea-mirror added the

question_old

label 2026-05-05 09:02:59 -06:00

gitea-mirror commented

2026-05-05 09:03:01 -06:00

Author

Owner

@ghost commented on GitHub (Nov 13, 2020):

No personal desire in this context, besides avoiding such a mix obviously...

@ghost commented on GitHub (Nov 13, 2020): No personal desire in this context, besides avoiding such a mix obviously...

gitea-mirror commented

2026-05-05 09:03:02 -06:00

Author

Owner

@rusty-snake commented on GitHub (Nov 13, 2020):

Related: #3354

@rusty-snake commented on GitHub (Nov 13, 2020): Related: #3354

gitea-mirror commented

2026-05-05 09:03:03 -06:00

Author

Owner

@smitsohu commented on GitHub (Nov 14, 2020):

Personally no strong opinion either.

But having two different output destinations is somewhat inconvenient and error prone, as users might capture debug output by redirecting it to a file, potentially missing the important messages that are still going to stderr.

@smitsohu commented on GitHub (Nov 14, 2020): Personally no strong opinion either. But having two different output destinations is somewhat inconvenient and error prone, as users might capture debug output by redirecting it to a file, potentially missing the important messages that are still going to `stderr`.

gitea-mirror commented

2026-05-05 09:03:04 -06:00

Author

Owner

@ghost commented on GitHub (Nov 14, 2020):

@smitsohu That's indeed a very good point. I think I saw that kind of behaviour in the past and redirected both stdout and stderr to a file to avoid missing important info. Not sure if we can improve things in that regard.

@ghost commented on GitHub (Nov 14, 2020): @smitsohu That's indeed a very good point. I think I saw that kind of behaviour in the past and redirected both stdout and stderr to a file to avoid missing important info. Not sure if we can improve things in that regard.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2365

No description provided.

Rows
Columns