Date: Tue, 11 Mar 1997 00:55:56 +0100 (MET) From: " steve howe" <un_x@hotmail.com> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/2934: sh(1) has problems with $ENV Message-ID: <199703102355.AAA10899@uriah.heep.sax.de> Resent-Message-ID: <199703110030.QAA11609@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2934
>Category: bin
>Synopsis: sh(1) has problems with $ENV
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Mar 10 16:30:02 PST 1997
>Last-Modified:
>Originator: steve howe
>Organization:
unknown
>Release: FreeBSD 3.0-CURRENT i386
>Environment:
/bin/sh in any FreeBSD system so far.
>Description:
/bin/sh processes $ENV fine if it has been set inside ~/.profile like:
ENV=${HOME}/.env; export ENV
However, it fails to source $ENV in this case:
export ENV=${HOME}/.env
>How-To-Repeat:
Use:
export ENV=${HOME}/.env
in your ~/.profile, and re-invoke another level of sh(1). $ENV won't
be read. Now invoke any other Bourne-alike shell (pdksh, ksh93,
bash), it will process $ENV correctly.
>Fix:
Not known.
>Audit-Trail:
>Unformatted:
[This PR sent by joerg on behalf of Steve who doesn't have a good
enough IP connectivity.]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703102355.AAA10899>