home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.misc
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!paladin.american.edu!news.univie.ac.at!hp4at!mcsun!chsun!bernina!neptune!umueller
- From: umueller@iiic.ethz.ch (Urban Dominik Mueller)
- Subject: Re: csh 5.19 and CshResident
- Message-ID: <1992Nov19.002101.8539@neptune.inf.ethz.ch>
- Sender: news@neptune.inf.ethz.ch (Mr News)
- Nntp-Posting-Host: c11
- Organization: Dept. Informatik, Swiss Federal Institute of Technology (ETH), Zurich, CH
- References: <BxsJpC.6IG@ccu.umanitoba.ca>
- Date: Thu, 19 Nov 1992 00:21:01 GMT
- Lines: 15
-
- In article <BxsJpC.6IG@ccu.umanitoba.ca> kaarts@ccu.umanitoba.ca (Kenneth John Aarts) writes:
- >
- >What does the environment variable CshResident do? Csh 5.19 tries to open it
- >every time it is started. An egrep of csh: revealed nothing.
-
- A small optimization. Csh allows delayed loading of programs to be made
- resident. The names of those programs are stored in environment variables
- (since the apply to any invocation of csh). This would mean checking for
- and ENV: variable on every starting of an external prog, which is slowish
- and messes up SnoopDos. Thus, the variable CshResident is set if there
- are any delayed residents, and is checked for by every new invocation of
- csh. (Yes, I know about the race conditions).
- -Dominik
-
-
-