It seems tlog merges stderr and stdout output and dumps both on stdout instead. This breaks automated things as they expect the two channels to be distinct.
One such case is ThinLinc, which uses ssh as a transport layer. It will just hang, as it never sees the expected output on stderr as tlog has redirected that to stdout.
You can easily test this using this small command:
$ ssh user@server.example.com echo Foobar '>&2' 2>/dev/null
Without tlog, this prints nothing (CORRECT). With tlog, it prints "Foobar" (INCORRECT).
It seems tlog merges stderr and stdout output and dumps both on stdout instead. This breaks automated things as they expect the two channels to be distinct.
One such case is ThinLinc, which uses ssh as a transport layer. It will just hang, as it never sees the expected output on stderr as tlog has redirected that to stdout.
You can easily test this using this small command:
$ ssh user@server.example.com echo Foobar '>&2' 2>/dev/nullWithout tlog, this prints nothing (CORRECT). With tlog, it prints "Foobar" (INCORRECT).