Path: utzoo!utgpu!watmath!clyde!att!rutgers!tut.cis.ohio-state.edu!bloom-beacon!ICASE.EDU!tom From: tom@ICASE.EDU (Tom Crockett) Newsgroups: comp.windows.x Subject: Re: Starting remote xterms Message-ID: <8812011625.AA15086@icase.icase.edu> Date: 1 Dec 88 16:25:45 GMT Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 22 > ... both the local rsh process and the remote rshd would go away > after xterm was started. Just to complicate the discussion, there might be a reason for wanting to keep the "rsh" around. It seems that the source code for xterm is littered with fprintf's to stderr. If you redirect stderr and stdout for the remote xterm to /dev/null and dispose of the rsh process, then you wouldn't get any potential error messages. If you kept rsh around and don't redirect, then error messages would come back to your server machine (probably to /dev/console, if you started rsh from a window manager menu). But then again, how often does "xterm" generate errors? Not very, from my experience. Tom Crockett -------------------------------------------------------------------------------- Institute for Computer Applications in Science and Engineering M.S. 132C, NASA Langley Research Center Hampton, VA 23665 e-mail: tom@icase.edu phone: (804) 865-4097 --------------------------------------------------------------------------------