MORE INFO -- Re: Bizzare ksh behavior, Tru64 UNIX V4.0F

From: Narendra Raavi <narendra_at_spiff.mt.att.com>
Date: Fri, 22 Jun 2001 11:24:03 -0400

Managers,

We are convinced that this is a bug. Here is more information about
the problem:

> Managers,
>
> We are having a very bizzare shell program behavior. Here is the context:
>
> ENV=/home/narendra/.kshrc
> PATH=/home/narendra/bin:/usr/bin:.
>
> The file .kshrc contains the following line:
> typeset -x MYTEST=55
>
> I have two scripts named tst: one in ~/bin and another in ~/tmp
>
> /home/narendra/tmp/tst has the following two lines:
>
> #!/bin/ksh
> print "In the tmp directory"
>
> /home/narendra/bin/tst has the following two lines:
>
> #!/bin/ksh
> print "In the bin directory"
>
>
> When I change directory to tmp and execute /home/narendra/tmp/tst
> I see the following output:
>
> In the bin directory

command line: /home/narendra/tmp/tst
CWD: /home/narendra/tmp
For the record, I expected 'tmp' instead of 'bin' in the output.

> When I execute ./tst from tmp, I see the following output:
>
> In the tmp directory

command line: ./tst
CWD: /home/narendra/tmp
For the record, this is the expected output.

> When I execute /home/narendra/tmp/tst from anywhere else, I see the
> following output:
>
> In the tmp directory

command line: /home/narendra/tmp/tst
CWD: any other directory other than /home/narendra/tmp
For the record, this is the expected output.

> This behavior is seen only on Tru64 UNIX (V4.0F), not on solaris 5.6, HP-UX
> 10.20 or HP-UX 11.x.
>
> I do not have access to other versions of Tru64 UNIX.
>
> I believe this is a bug. Can others on this list confirm this? What's the
> process if this is indeed a bug?
>
> Thank you,

The following statements are true:

 1. If I remove the line #!/bin/ksh from /home/narendra/tmp/tst,
     everything works fine.

 2. If I unset ENV, everything works fine.

 3. If I use an empty file as value of ENV, everything works fine.

 4. If the last command in the file pointed by ENV is a shell built-in or
     a command it does not find or another shell script I see this bizzare
     behavior.

-- 
 -- Narendra Ra[a]vi     Email : narendra_at_spiff.hr.att.com
    MT  A4-4B27       Phone : 732-420-7792
Received on Fri Jun 22 2001 - 15:22:43 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT