Return to BSD News archive
Xref: sserve comp.unix.bsd:12170 comp.unix.shell:9699 comp.unix.questions:36045 comp.sys.sun.misc:8488 Newsgroups: comp.unix.bsd,comp.unix.shell,comp.unix.questions,comp.sys.sun.misc Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!darwin.sura.net!howland.reston.ans.net!math.ohio-state.edu!usc!elroy.jpl.nasa.gov!decwrl!csus.edu!netcom.com!marquis From: marquis@netcom.com (Roger Marquis) Subject: Re: "stty: TCGETS: Operation not supported on socket" problem Message-ID: <marquisC9II2K.BCr@netcom.com> Followup-To: comp.unix.bsd,comp.unix.shell,comp.unix.questions,comp.sys.sun.misc Organization: NETCOM On-line Communication Services (408 241-9760 guest) X-Newsreader: TIN [version 1.1 PL9] References: <20g29q$11l@yawl.htc.com> Date: Fri, 2 Jul 1993 00:44:43 GMT Lines: 19 Thomas Naughton (naughton@htc.com) wrote: >|> I'm getting this problem on a Sun system as I'm trying to rcp >|> a file from one machine to another. If I do this as root, I have no >|> problem, but a regular user gets this error. It seems to occur when I >|> do a number of remote commands. Has anyone seen this? Thanks in >|> advance. >Probably the user has a command "stty something" in their .cshrc file. >rcp and rsh end up running the users shell on the other machine, which >causes their .cshrc to get executed if they use csh. This works for most cases but sometimes you want an stty command in your .cshrc, say if your .login isn't sourced or if you use multiple shells. In such cases just put the offending (stty) commands after the following line: if (! $?prompt ) exit Roger Marquis