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
When installing this on HPC systems often the installation directory is not writable by the users running the software leading to errors. In the case that it is writable by users then there can be thrashing and race conditions in the logfile if multiple jobs are writing to it at once.
It might be better to distribute the version that logs to stdout instead of a logfile in the install directory.
The text was updated successfully, but these errors were encountered:
lilleswing
changed the title
Release Log To STDOUT instead of to install directory
Release Binary Should Log To STDERR instead of to install directory
Aug 17, 2022
lilleswing
changed the title
Release Binary Should Log To STDERR instead of to install directory
[SUGGESTION] Release Binary Should Log To STDERR instead of to install directory
Aug 17, 2022
In https://github.com/rdk/p2rank/blob/develop/distro/prank the program logs to a logfile, that is default inside the installation directory. I believe this is the run-script distributed in the release tarball.
When installing this on HPC systems often the installation directory is not writable by the users running the software leading to errors. In the case that it is writable by users then there can be thrashing and race conditions in the logfile if multiple jobs are writing to it at once.
It might be better to distribute the version that logs to stdout instead of a logfile in the install directory.
The text was updated successfully, but these errors were encountered: