https://bugzilla.mindrot.org/show_bug.cgi?id=1673
Summary: pseudoterminal option (-t) breaks standard out/error
separation
Product: Portable OpenSSH
Version: 5.1p1
Platform: Other
OS/Version: Other
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: [email protected]
ReportedBy: [email protected]
When connecting to run commands, standard error ends up mixed with
standard output when using the (-t) pseudoterminal option.
====================
Here's an example without pseudoterminal option where it is working
correctly, and the error messages from the server are captured by fd2
on the client:
---
$ ssh u...@server 'uptime ; ls -l /blah' > out 2> err
u...@server's password:
$ cat err
ls: cannot access /blah: No such file or directory
$ cat out
05:07:09 up 14 days, 1:40, 4 users, load average: 0.01, 0.02, 0.00
====================
And here's an example with pseudoterminal option where standard error
is mixed in with standard output, and the error messages from the
server are captured by fd1 on the client. The only error message that
went to fd2 was the error from the ssh client executable:
---
$ ssh -t u...@server 'uptime ; ls -l /blah' > out 2> err
u...@server's password:
$ cat err
Connection to elena closed.
$ cat out
05:07:20 up 14 days, 1:40, 5 users, load average: 0.01, 0.02, 0.00
ls: cannot access /blah: No such file or directory
====================
I tested this from solaris8 to solaris8, from solaris8 to redhat linux,
and from ubuntu linux to ubuntu linux, several versions of
client/server.
--
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
[email protected]
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
