[GH-ISSUE #889] barriers does not write to log file without the -f flag. #710

New issue

Open

opened 2026-05-05 06:58:46 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 06:58:46 -06:00

Owner

Originally created by @viktorsmari on GitHub (Sep 28, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/889

Describe the bug

Start 2 terminals side by side
Start barriers in one:
barriers -f --enable-crypto --debug DEBUG --log ./barrier.log
Tail the log in the other terminal:
tail -f barrier.log

We should see activity in the tail, for example when we move the mouse to a client screen, which is expected.
Stop barriers in the first terminal, and start again without the -f flag
barriers --enable-crypto --debug DEBUG --log ./barrier.log

Everything works normally, except it has stopped logging to the logfile, why?

Expected behavior
It should always write to the log file when using the --log, or document that it does not output to a log file, if another specific flag is used.

OS: Linux
Barrier version 2.3.2

Originally created by @viktorsmari on GitHub (Sep 28, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/889 **Describe the bug** 1. Start 2 terminals side by side 2. Start `barriers` in one: `barriers -f --enable-crypto --debug DEBUG --log ./barrier.log` 3. Tail the log in the other terminal: `tail -f barrier.log` We should see activity in the `tail`, for example when we move the mouse to a client screen, which is expected. 4. Stop `barriers` in the first terminal, and start again **without the -f flag** `barriers --enable-crypto --debug DEBUG --log ./barrier.log` Everything works normally, **except** it has **stopped** logging to the logfile, why? **Expected behavior** It should **always** write to the log file when using the `--log`, or document that it does not output to a log file, if another specific flag is used. - OS: Linux - Barrier version 2.3.2