Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!seismo!dimacs.rutgers.edu!aramis.rutgers.edu!paul.rutgers.edu!njin!njitgw.njit.edu!hertz.njit.edu!brw
From: brw@hertz.njit.edu (Brian White)
Newsgroups: comp.unix.ultrix
Subject: Re: tcsh and Ultrix 4.2
Message-ID: <1991Jun12.180204.29425@njitgw.njit.edu>
Date: 12 Jun 91 18:02:04 GMT
References: <1991Jun6.192555.25183@unhd.unh.edu> <1991Jun7.081957.14087@pa.dec.com>
Sender: news@njit.edu
Organization: New Jersey Institute of Technology, Newark, N.J.
Lines: 21
Nntp-Posting-Host: hertz.njit.edu

In article <1991Jun7.081957.14087@pa.dec.com> neideck@kaputt.enet.dec.com (Burkhard Neidecker-Lutz) writes:
>
>There is a bug in tcsh that is triggered under Ultrix 4.2. The 4.2
>prompter sets the close-on-exec flags on file descriptors 0,1 and 2
>and tcsh gets confused when it tries to get around the closed descriptors.
>(i.e. the reopening code is broken). My login shell is tcsh under
>4.2, but we patched tcsh. I didn't do the patch, I will have to check
>with the author of it whether it's ok to post it.
>
>
>				Burkhard Neidecker-Lutz
>				Digital CEC Karlsruhe
>				Project NESTOR

Any followup on this, Burkhard? I'm currently "exec"ing tcsh in .login on our
5000 and would like a more elegant solution :^).


Brian White, System Manager
New Jersey Institute of Technology
brw@hertz.njit.edu brw@njit.edu