You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously when running borg in a systemd service (and similar when piping to a file and co.),
these problems occurred:
- The carriage return both made it so that journald interpreted the output as
binary, therefore not printing the text, while also not buffering
correctly, so that log output was only available every once in a while
in the form [40k blob data]. This can partially be worked around by
using `journalctl -a` to view the logs, which at least prints the
text, though only sporadically
- The path was getting truncated to a short length, since the default
get_terminal_size returns a column width of 80, which isn't relevant
when printing to e.g. journald
This commit fixes this by introducing a new code path for when stderr is
a tty, which always prints the full paths and never ends with a carriage
return.
0 commit comments