[comp.sys.ncr] /bin/sh bug ?

nigel@cmsfl@labtam.oz (Nigel Harwood) (07/24/90)

I have a strange situation using UNIX SYSV.2 1.03 and the bourne shell.

The sequence of events is as follows :

1) A COBOL report program is started in batch mode on tty01.

2) A large /bin/sh script is started on ttyb.

3) The /bin/sh script exits with a status of zero at a point where
   it is impossible for it to do so.

The last statement the /bin/sh script executes is the last statement
of a function.

The /bin/sh script works fine if the COBOL report program is not running.

I have run the COBOL report program in interactive mode and then started
the /bin/sh script and things work correctly.

I have run sar while the /bin/sh script is running and none of the
system tables get close to 50% full.

I have run the /bin/sh script with set -x and found that the run with
the batch program produces a corrupted result.

For example in the script are the statements :

   ps -e | grep ABCD > /dev/null

The successful /bin/sh script run produces :

   + grep mcontrol 
   + ps -e 

The unsuccessful run produces :

   + + grepps  mcontrol-e  

Can anyone shed any light on any of this behaviour ?

Regards
-- 
<<<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia     >>
<< Phone: +61 3 829 6090  E-mail: nigel@cnw01.storesys.coles.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>