Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site cbneb.UUCP Path: utzoo!watmath!clyde!floyd!vax135!houxz!houxm!ihnp4!cbosgd!cbscc!cbneb!adm From: adm@cbneb.UUCP Newsgroups: net.unix Subject: Re: Re: ksh as /bin/sh - (nf) Message-ID: <927@cbneb.UUCP> Date: Wed, 20-Jun-84 14:24:06 EDT Article-I.D.: cbneb.927 Posted: Wed Jun 20 14:24:06 1984 Date-Received: Thu, 21-Jun-84 08:44:04 EDT Sender: adm@cbneb.UUCP Organization: AT&T Bell Laboratories, Columbus, OHIO Lines: 15 #R:druxh:-77000:cbnap:27300003:000:684 cbnap!whp Jun 20 13:30:00 1984 > While we have not installed "ksh" as "/bin/sh", setting the > variable "SHELL" in the environment simulates this. We noted that > the performance of "make" was seriously affected (~20%) because every > time "make" started "ksh", "ksh" read in the startup file (set in "ENV"). What do you keep in the $ENV file?? It should be used for aliases, setting the prompt, and not much else. These type of operations execute very fast, since the're built into ksh (alias for example). Prehaps your problem is that you have too much stuff in the $ENV file that could be put elsewhere (i.e., .profile). We have been using ksh for some time, and have not noticed any performance drop.