When gocryptfs was started on a terminal and later daemonized, the color codes stayed active in the syslog output. The codes are not visible in "journalctl -f", which is why I have not noticed it yet, but they do show up in normal syslog as the usual "#033[33m" crap.libgocryptfs
parent
4cdf6b9af9
commit
1ed08c7384
Loading…
Reference in new issue