The tsdfx service no longer log user relevant errors with file names etc to tsdfx-error.log, at least on Linux. The problem was introduced in commit 73806d42dbad27dc47b5c7f39f399b418fa459c7, when the log code was changed to no longer print to file descriptor 2 but instead open and write to /dev/stderr.
When executing a process under a different effective uid, the permissions to write to /dev/stderr are not available, causing log messages to disappear and make it to the parent process. The effect is that these messages do not make it into tsdfx-error.log.
The tsdfx service no longer log user relevant errors with file names etc to tsdfx-error.log, at least on Linux. The problem was introduced in commit 73806d42dbad27dc47b5c7f39f399b418fa459c7, when the log code was changed to no longer print to file descriptor 2 but instead open and write to /dev/stderr.
When executing a process under a different effective uid, the permissions to write to /dev/stderr are not available, causing log messages to disappear and make it to the parent process. The effect is that these messages do not make it into tsdfx-error.log.