home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.bash.bug
- Path: sparky!uunet!cis.ohio-state.edu!odin.ins.cwru.edu!chet
- From: chet@odin.ins.cwru.edu (Chet Ramey)
- Subject: Re: rsh, rcp with bash
- Message-ID: <9207241236.AA02088.SM@odin.INS.CWRU.Edu>
- Sender: gnulists@ai.mit.edu
- Reply-To: chet@po.cwru.edu
- Organization: GNUs Not Usenet
- References: chet@odin.ins.cwru.edu (Chet Ramey)
- Distribution: gnu
- Date: Fri, 24 Jul 1992 04:36:22 GMT
- Approved: bug-bash@prep.ai.mit.edu
- Lines: 37
-
- > I wonder whether this problem has been beaten to death in this group
- > before. I use bash 1.12.1 as login shell on my machines (Sun Sparcs
- > running SunOS 4.1.1) and having problem with rsh and rcp. The symptoms
- > are as follows:
- >
- > host1> rcp localfile host2:remotefile
- > stty: TCGETS: Operation not supported on socket
- > host1> rsh host2 ls
- > stty: TCGETS: Operation not supported on socket
-
- I'll bet you have something that does output or manipulates the terminal
- state in your .bashrc. Bash attempts to source the .bashrc for non-
- interactive shells running rsh and rcp so things like $PATH get set.
-
- What you should probably do is to make your .bashrc look like this:
-
- unset INTERACTIVE
- case "$-" in
- *i*) INTERACTIVE=on ;;
- esac
-
- ... initialization for all shells, interactive or not ...
-
- if [ -z "$INTERACTIVE" ]; then
- return
- fi
-
- ... initialization for all interactive shells ...
-
- Chet
-
- --
- ``The use of history as therapy means the corruption of history as history.''
- -- Arthur Schlesinger
-
- Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu
-
-