Re: Why is "ssh -V" written to stderr? I want to separate output and error...
From: Dimitri Maziuk (dima@127.0.0.1)Date: 11/14/02
- Next message: Ian! D. Allen: "limiting scope of reverse port forwarding (-R)"
- Previous message: Ian! D. Allen: "ssh -N bypasses command="command" in authorized_keys"
- In reply to: : "Why is "ssh -V" written to stderr? I want to separate output and error..."
- Next in thread: Steven Wilmot: "Re: Why is "ssh -V" written to stderr? I want to separate output and error..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Dimitri Maziuk <dima@127.0.0.1> Date: Thu, 14 Nov 2002 16:48:18 +0000 (UTC)
thus spake Goran Brannstrom:
>
> ...and capture stdout and stderr separately?
>
> "ssh -V" seems to be written to stderr by default.
>
> Any help would be great!
>
> /Goran Brannstrom
>
> Troubled Bash Programmer
^^^^^^^^^^^^^^^^^^^^^^^^
Indeed.
Ever heard of "man bash"?
Dima (2>ERRS)
-- True courage comes from steadying yourself and forcing yourself to ssh into the fscking thing yet again and not admitting that it doesn't care what it's done to your life. -- "Hidden among the nodes" by ADB
- Next message: Ian! D. Allen: "limiting scope of reverse port forwarding (-R)"
- Previous message: Ian! D. Allen: "ssh -N bypasses command="command" in authorized_keys"
- In reply to: : "Why is "ssh -V" written to stderr? I want to separate output and error..."
- Next in thread: Steven Wilmot: "Re: Why is "ssh -V" written to stderr? I want to separate output and error..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]