Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.UUCP (Tom Neff)
Newsgroups: comp.bugs.sys5
Subject: Re: ksh bugs
Message-ID: <14571@bfmny0.UUCP>
Date: 21 Aug 89 06:12:16 GMT
References: <10166@fluke.COM> <10450@fluke.COM> <177@uci.UUCP> <1035@virtech.UUCP>
Reply-To: tneff@bfmny0.UU.NET (Tom Neff)
Distribution: na
Organization: ^
Lines: 17
Keywords: ksh

In article <1035@virtech.UUCP> cpcahil@virtech.UUCP (Conor P. Cahill) writes:
[why KSH can fork slower]
>Another reason may be that you use the "ENV" mechanism of causing sub-shells
>to read and process the .profile equivalent named in the ENV environment
>variable.

This is usually the cause.  A workaround suggested in K&B or the AT&T man
page, I forget which, is this line (taken from my .profile):

	export Envfile=$HOME/.env
	export ENV='${Envfile[(_$-=1)+(_=0)-(_$-!=_${-%%*i*})]}'

This has the effect of nulling $ENV unless your copy of ksh was invoked
interactively -- so shelldowns and such run much faster.
-- 
"We walked on the moon --	((	Tom Neff
	you be polite"		 )) 	tneff@bfmny0.UU.NET