Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!ukma!david
From: david@ms.uky.edu (David Herron -- One of the vertebrae)
Newsgroups: comp.unix.ultrix
Subject: Re: Bug in /bin/sh??
Message-ID: <12064@s.ms.uky.edu>
Date: 6 Jul 89 00:26:28 GMT
References: <400@mipos3.intel.com> <12045@s.ms.uky.edu> <1394@rivm05.UUCP>
Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae)
Organization: U of Kentucky, Mathematical Sciences
Lines: 39

In article <1394@rivm05.UUCP> a3@rivm.UUCP (Adri Verhoef) writes:
>From sh(1) of TFM of version 3.0:
>
>RESTRICTIONS

[The same bug listing that's been on the sh(1) manual page from at least v7]

In my case I have lots of scripts which are run out of cron at various
times of the day.  I tend to put (..)'s around the whole script so that
I can redirect the output of the entire script to a log file.  I also
tend, when I need a "procedure", to cat the procedure out to a script
file in a "here" document and then execute that.  This all worked fine
and perfectly under Ultrix v2.2, SunOS v3.4, and Dynix v2.? and v3.?.

It started breaking when we upgraded to Ultrix v3.0 but continued to
work on the other machines.  Even with upgrading the Sun's to v4.1.

Mark Evans tells me by mail:


From: evans@decvax.zk3.dec.com
To: jbrayton@mipos2.intel.com, maart@star.cs.vu.nl, 
    ukma!david@decvax.zk3.dec.com
Subject: RE: Bug in /bin/sh??
Date: Wed, 05 Jul 89 16:49:08 EDT

(I would post this to the net, but alas, my xrn program seems to be broken and
I can not. You are welcome to forward this to the net...)

If you use /bin/sh5, this will solve your immediate problem. This unfortunately
is not very portable, but is the mechanism that DEC decided to provide for
SYS V compatability.

- Marc Evans
-- 
<- David Herron; an MMDF guy                              <david@ms.uky.edu>
<- ska: David le casse\*'      {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<-
<- New word for the day: Obnoxity -- an act of obnoxiousness