github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #96] Logging issues #71

New issue

Closed

opened 2026-05-05 04:56:56 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 04:56:56 -06:00

Owner

Originally created by @Every0ne on GitHub (Jul 16, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/96

I run barrierc with --log /dev/null option, however my log files still get littered with thousands of lines of

timestamp machine Barrier[3044]: 2.1.0-RELEASE: [2018-07-16T22:20:58] NOTE: connecting to 'servername': 172.16.0.X:24800
timestamp machine Barrier[3044]: 2.1.0-RELEASE: [2018-07-16T22:20:57] WARNING: failed to connect to server: Timed `out`

whenever the server is not running (and most often it isn't). Is there a way to truly disable logging or reduce verbocity to critical errors only?

Originally created by @Every0ne on GitHub (Jul 16, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/96 I run barrierc with `--log /dev/null` option, however my log files still get littered with thousands of lines of ``` timestamp machine Barrier[3044]: 2.1.0-RELEASE: [2018-07-16T22:20:58] NOTE: connecting to 'servername': 172.16.0.X:24800 timestamp machine Barrier[3044]: 2.1.0-RELEASE: [2018-07-16T22:20:57] WARNING: failed to connect to server: Timed `out` ``` whenever the server is not running (and most often it isn't). Is there a way to truly disable logging or reduce verbocity to critical errors only?

gitea-mirror closed this issue

2026-05-05 04:56:58 -06:00

gitea-mirror commented

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

Author

Owner

@AdrianKoshka commented on GitHub (Jul 16, 2018):

I think you're confusing logging to a file with the logging to (what I assume is) stderr.

@AdrianKoshka commented on GitHub (Jul 16, 2018): I think you're confusing logging to a file with the logging to (what I assume is) `stderr`.

gitea-mirror commented

2026-05-05 04:57:04 -06:00

Author

Owner

@Every0ne commented on GitHub (Jul 17, 2018):

I'm no *nix expert, but even when run with 2>/dev/null 1>/dev/null barrierc still outputs to system-owned log files. What's the reason for --log option then? What I see is that it doesn't do anything at all, no files are created nor written to.

@Every0ne commented on GitHub (Jul 17, 2018): I'm no *nix expert, but even when run with `2>/dev/null 1>/dev/null` barrierc still outputs to system-owned log files. What's the reason for `--log` option then? What I see is that it doesn't do anything at all, no files are created nor written to.

gitea-mirror commented

2026-05-05 04:57:06 -06:00

Author

Owner

@W4RH4WK commented on GitHub (Jul 18, 2018):

As I understand it, log output is always written to the console. The --log causes Barrier to also write the output to the given file.

@W4RH4WK commented on GitHub (Jul 18, 2018): As I understand it, log output is always written to the console. The `--log` causes Barrier to *also* write the output to the given file.

No labels

Rows
Columns