Thank you, Jeff. I just commented the stty line out and it doesn't seem to have any ill effect with interactive shells. I guess my stty erase ^\? was superfluous to begin with. I have hard time remembering which rc file invokes/chains what other rc file.
Regards, Tena Sakai tsa...@gallo.ucsf.edu On 1/13/11 11:10 AM, "Jeff Squyres" <jsquy...@cisco.com> wrote: > FWIW: you can typically put that kind of stuff in a portion of your .bashrc > that is only invoked for interactive logins. I.e., the automated ssh's that > OMPI's mpirun won't invoke those commands because they're non-interactive > logins. > > I'm a tcsh user myself, so I don't know the appropriate mojo offhand to detect > interactive vs. non-interactive bash logins, but I'm sure it exists. > > > > On Jan 12, 2011, at 7:13 PM, Tena Sakai wrote: > >> Thank you, Gus. >> >> I grep'ed "stty" in all .<files> in my home directory and found >> that I had a line >> stty erase ^\? >> in .bashrc. When I commented out the line, the error message >> "stty: standard input: Invalid argument" went away. >> >> I appreciate your tip. >> >> Tena Sakai >> tsa...@gallo.ucsf.edu >> >> >> On 1/12/11 3:44 PM, "Gus Correa" <g...@ldeo.columbia.edu> wrote: >> >>> Tena Sakai wrote: >>>> Hi, >>>> >>>> I am trying to run simple mpirun commands (pretty much straight out of >>>> mpirun man page) and getting a bit of error message. Here¹s what I mean: >>>> >>>> [tsakai@vixen Rmpi]$ >>>> [tsakai@vixen Rmpi]$ hostname >>>> vixen.egcrc.org >>>> [tsakai@vixen Rmpi]$ >>>> [tsakai@vixen Rmpi]$ mpirun -H vixen -np 1 hostname >>>> vixen.egcrc.org >>>> [tsakai@vixen Rmpi]$ mpirun -H blitzen -np 1 hostname >>>> stty: standard input: Invalid argument >>>> blitzen.egcrc.org >>>> [tsakai@vixen Rmpi]$ mpirun -H vixen -np 1 hostname : -H blitzen -np >>>> 1 hostname >>>> stty: standard inputvixen.egcrc.org >>>> blitzen.egcrc.org >>>> [tsakai@vixen Rmpi]$ : Invalid argument >>>> >>>> [tsakai@vixen Rmpi]$ >>>> [tsakai@vixen Rmpi]$ mpirun -H vixen -np 1 hostname : -H blitzen -np >>>> 1 hostname 2> stdErr >>>> vixen.egcrc.org >>>> blitzen.egcrc.org >>>> [tsakai@vixen Rmpi]$ >>>> [tsakai@vixen Rmpi]$ cat stdErr >>>> stty: standard input: Invalid argument >>>> [tsakai@vixen Rmpi]$ >>>> [tsakai@vixen Rmpi]$ ssh -l tsakai blitzen >>>> Last login: Wed Jan 12 15:41:59 2011 from vixen.egcrc.org >>>> Platform OCS Frontend Node - Blitzen Cluster >>>> Platform OCS 4.5.1 (Flintstone) >>>> Profile built 11:01 10-Jul-2008 >>>> >>>> Kickstarted 11:02 10-Jul-2008 >>>> [tsakai@blitzen ~]$ >>>> [tsakai@blitzen ~]$ hostname >>>> blitzen.egcrc.org >>>> [tsakai@blitzen ~]$ >>>> [tsakai@blitzen ~]$ mpirun -H blitzen -np 1 hostname >>>> blitzen.egcrc.org >>>> [tsakai@blitzen ~]$ mpirun -H vixen -np 1 hostname >>>> stty: standard inputvixen.egcrc.org >>>> [tsakai@blitzen ~]$ : Invalid argument >>>> >>>> [tsakai@blitzen ~]$ mpirun -H vixen -np 1 hostname : -H blitzen -np 1 >>>> hostname >>>> stty: standard inputblitzen.egcrc.org >>>> vixen.egcrc.org >>>> [tsakai@blitzen ~]$ : Invalid argument >>>> >>>> [tsakai@blitzen ~]$ >>>> [tsakai@blitzen ~]$ mpirun -H vixen -np 1 hostname : -H blitzen -np 1 >>>> hostname 2> stdErr >>>> blitzen.egcrc.org >>>> vixen.egcrc.org >>>> [tsakai@blitzen ~]$ >>>> [tsakai@blitzen ~]$ cat stdErr >>>> stty: standard input: Invalid argument >>>> [tsakai@blitzen ~]$ >>>> [tsakai@blitzen ~]$ exit >>>> logout >>>> [tsakai@vixen Rmpi]$ >>>> >>>> I am using two hosts: vixen and blitzen. It appears that when a machine >>>> other than >>>> the one I am on it is specified via H flag, I get ³stty: standard >>>> input: Invalid argument² >>>> message to stderr. It doesn¹t seem to impeed the execution of the >>>> command (in >>>> my example, hostname), though. >>>> >>>> Can somebody please tell me what this means and what it takes to cure >>>> the problem? >>>> >>>> Thank you. >>>> >>>> Tena Sakai >>>> tsa...@gallo.ucsf.edu >>>> >>> >>> Guessin' ... >>> Anything in your .bashrc/.tcshrc or on >>> system-wide initialization files in /etc /etc/profile.d >>> that may be causing the stty output to stderr? >>> I did a little googling and found some stuff about it. >>> Perhaps it is not redirecting stderr 2>dev/null. >>> The message may come from the ssh session opened when mpiexec connects >>> you to the remote machine. >>> >>> My $0.02 >>> Gus Correa >>> _______________________________________________ >>> users mailing list >>> us...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/users >> >> >> _______________________________________________ >> users mailing list >> us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/users >
