Perhaps the error is specific to Red Hat? I reproduced it with remote hosts running RHEL 5.2, 5.8, 6.3. The local host is RHEL 5.8.
ANY invocation of stty, even without arguments, provokes the "tcgetattr: Invalid argument" error message. [afratkin@vl001 src]$ echo hello | ssh -tt -oLogLevel=quiet g4t0930c stty | cat # RHEL 5.2 tcgetattr: Invalid argument speed 0 baud; line = 0; intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>; start = <undef>; stop = <undef>; susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>; flush = <undef>; min = 1; time = 0; -brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -iexten -echo -echoe -echok -echoctl -echoke [afratkin@vl001 src]$ echo hello | ssh -tt -oLogLevel=quiet g4t0439 stty | cat # RHEL 5.8 tcgetattr: Invalid argument speed 0 baud; line = 0; intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>; start = <undef>; stop = <undef>; susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>; flush = <undef>; min = 1; time = 0; -brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -iexten -echo -echoe -echok -echoctl -echoke [afratkin@vl001 src]$ echo hello | ssh -tt -oLogLevel=quiet v001 stty | cat # RHEL 6.3 tcgetattr: Invalid argument speed 0 baud; line = 0; intr = M-^?; quit = M-^?; erase = M-^?; kill = M-^?; eof = M-^?; eol = M-^?; eol2 = M-^?; start = M-^?; stop = M-^?; susp = M-^?; rprnt = M-^?; werase = M-^?; lnext = M-^?; flush = M-^?; min = 1; time = 0; -brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -iexten -echo -echoe -echok -echoctl -echoke [afratkin@vl001 src]$ RHEL 5.2, 5.8: stty (GNU coreutils) 5.97 Copyright (C) 2006 Free Software Foundation, Inc. This is free software. You may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. Written by David MacKenzie. RHEL 6.3: stty (GNU coreutils) 8.4 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by David MacKenzie. Local host's ssh version (RHEL 5.8): OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 -- Allyn Fratkin [email protected] Hewlett-Packard Company http://www.fratkin.com/ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ole Tange Sent: Tuesday, May 07, 2013 11:10 PM To: Fratkin, Allyn Cc: [email protected] Subject: Re: Poor job distribution? On Tue, May 7, 2013 at 9:55 PM, Fratkin, Allyn <[email protected]> wrote: > Fantastic! Works great now. Thank you for the quick turnaround. Now I get > a job distribution of 2, 1, 2, 1, 2, 2, 1. Perfect. If it does not break anything this may be the default in the future. > Only problem is now I get an error message "tcgetattr: Invalid argument" from > each job, appears to result from "$remote_pre .= ::shell_quote_scalar('stty > isig -onlcr -echo;');" on line 3810. Did you mean "and" rather than "or" on > line 3798? No: --ctrlc is now default unless you use --pipe. I have not seen the error you get before, so I would like to be able to reproduce that error. My guess is that it is due to your version of stty or terminal. Can you post the output from the commands on the remote system: stty --version stty -onlcr stty isig stty -echo echo $TERM uname -a If you can reproduce it on one of the virtualbox-images from http://sourceforge.net/projects/virtualboximage/files/ it will be even better. For --ctrlc to work I need: -onlcr - make output 8-bit clean - otherwise binary output will not work. isig - pass CTRL-C as signal -echo - do not print input back /Ole
