Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.sys.hp
Subject: Re: HPUX 6.5 problems (long)
Message-ID: <1505@auspex.auspex.com>
Date: 25 Apr 89 19:08:41 GMT
References: <1725@Portia.Stanford.EDU> <39006@bbn.COM>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 48

>Check the user's {.cshrc,.profile} files.  If they are executing an stty
>command, it could very well be that they are performing a non-valid
>operation on a network socket (If you are unclear about what it means
>to have an operation not supported on a socket, see socket(2), or
>"ARPA Services User's Guide".)

I don't think *any* of the standard tty mode-setting "ioctl"s are valid
on sockets, which means just about any "stty" command will cause this
error.

>In other words, this is probably a valid, legal error message. 
>Personally, I get them all the time when I rlogin/xterm to my Sun;
>I find that ignoring the error messages causes no ill effects.

...other than perhaps minor irritation.

".profile" shouldn't be a problem; that's only executed by login shells,
and I certainly hope the shell fired off by "remsh" (I assume that, like
AT&T, HP dealt with the namespace collision between the 4.[23]BSD Remote
SHell and the S5 Restricted SHell by calling the former "remsh") isn't a
login shell (the vanilla BSD "rshd" doesn't stick a "-" in front of the
shell's name when passing it as the 0th argument, so it's not a login
shell there).

".cshrc" could be a problem, although I'd expect "stty"s to be in
".login" rather than ".cshrc" (is there any need to do it in a shell
other than your login shell?).  If you're doing an "stty" in ".cshrc",
you can keep it from happening in "rsh"/"remsh" shells by wrapping it in:

	if ( $?prompt ) then
		...
	endif

which makes it happen only in interactive shells.  You may want to wrap
other things in this as well....

If you have the Korn shell, or some Bourne shell variant that has a
per-instance ".rc" file (i.e., the moral equivalent of ".cshrc"), you'll
probably want some similar form of protection;

	case "$-" in

	*i*)
		...
		;;
	esac

worked for me with the Korn shell, as I remember.