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
Right now, while the choices are stderr and syslog, it might be worth having output default to stdout, or at least have it be an option. When packaging tuntox for nix, (NixOS/nixpkgs#160548), lack of stdout has made it more difficult to quickly check for a working build.
Even if it's decided to keep default behavior as is, having a version check, likely with --version or -v, should default to stdout.
The text was updated successfully, but these errors were encountered:
Thanks. The reasoning behind using stderr is mostly because -W option:
-W <remotehostname>:<remoteport> - forward <remotehostname>:<remoteport> to
stdin/stdout (SSH ProxyCommand mode)
But for --version, --help etc you're right, it should to stdout, I just checked how the standard GNU utilities do it and they print such output to stdout.
Also, there's no --version / --v, that needs to be implemented.
Right now, while the choices are stderr and syslog, it might be worth having output default to stdout, or at least have it be an option. When packaging tuntox for nix, (NixOS/nixpkgs#160548), lack of stdout has made it more difficult to quickly check for a working build.
Even if it's decided to keep default behavior as is, having a version check, likely with
--version
or-v
, should default to stdout.The text was updated successfully, but these errors were encountered: