Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsc!cbnews!smk
From: smk@cbnews.att.com (Stephen M. Kennedy)
Newsgroups: comp.unix.shell
Subject: Re: Remote shell question
Message-ID: <1991Feb6.203453.20443@cbnews.att.com>
Date: 6 Feb 91 20:34:53 GMT
References: <1991Feb1.145242.16915@bradley.bradley.edu> <1991Feb1.170808.24481@cbnews.att.com> <1991Feb6.043021.7019@NCoast.ORG>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 17

In article <1991Feb6.043021.7019@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) writes:
>As quoted from <1991Feb1.170808.24481@cbnews.att.com> by smk@cbnews.att.com (Stephen M. Kennedy):
>+---------------
>| 	remsh/rsh remote-host 'sleep 30 <&- >&- 2>&- 7>&- &'
>| 
>| The offending fd #7 showed up in a "/etc/pstat -u pid-of-sleep-process" in
>| the file section.
>+---------------
>*7* ????!  Was ist los?

Good question.  It seems to be a dup of stderr.  Also under certain
conditions it shows up as fd #6, so now I just close every fd I can (0-9)
in the script to be safe.  I don't think it's a shell problem, unless it's
one shared by both /bin/sh and ksh.  Anybody know?

Steve Kenndy
smk@cbosgd.att.com