Return to BSD News archive
Xref: sserve comp.unix.bsd:12122 comp.unix.shell:9622 comp.unix.questions:35790 comp.sys.sun.misc:8401 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!math.ohio-state.edu!news.acns.nwu.edu!uicvm.uic.edu!yawl.htc.com!htc.com!naughton From: naughton@htc.com (Thomas Naughton) Newsgroups: comp.unix.bsd,comp.unix.shell,comp.unix.questions,comp.sys.sun.misc Subject: Re: "stty: TCGETS: Operation not supported on socket" problem Date: 25 Jun 1993 23:38:34 GMT Organization: Hull Trading Company Lines: 23 Distribution: world Message-ID: <20g29q$11l@yawl.htc.com> References: <20fqja$2me@gilligan.htc.com> NNTP-Posting-Host: nauts.htc.com In article <20fqja$2me@gilligan.htc.com>, naughton@htc.com (Thomas Naughton) wri |> |> 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. |> I can't find anything in the manuals or man pages. If it's |> relevant, I'm running 4.1 on one of the machines. I know it's bad form to followup your own post, but I've received a half-dozen relies already (seems like this has happened before!). Since I'm not a C-shell person (ksh), I guess that's why I hadn't run into it before. For completeness sake, here's Mark Sienkiewicz's E-mail that explains it clearly: ====================== 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. I used to be forever telling people "put the stty in .login"... :) ======================