home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.unix.questions
- Subject: Re: .profile vs. .kshrc
- Date: 6 Nov 1992 17:30:16 GMT
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 21
- Distribution: na
- Message-ID: <1dea38INN9r8@early-bird.think.com>
- References: <Bwwo6r.5CE@constant.demon.co.uk> <Bx5wxp.2oH@constant.demon.co.uk> <1992Nov04.233827.1078@trebor.uucp>
- NNTP-Posting-Host: telecaster.think.com
-
- In article <1992Nov04.233827.1078@trebor.uucp> root@trebor.uucp (Bob Stockler) writes:
- > If the
- >ENV environmental parameter is set (and exported) in either "/etc/profile" or
- >"$HOME/.profile" to contain the full pathname of any file, that file will be
- >read (and the commands in it executed, as though it were a "dot" file) upon
- >the invocation of any instance of the KornShell, at any level of subshells
- >(Bourne or Korn). I have no idea how this relates to C shell users.
-
- It's not as good as the C shell's .login and .cshrc facility.
-
- The main problem with this Korn Shell feature is that it doesn't provide
- any way to customize the shell environment in a shell that isn't descended
- from a login shell. These include the shell in which cron, at, and batch
- jobs run, and commands executed with rsh/remsh. The C shell always
- executes the user's .cshrc (unless the "-f" option is specified), so you
- always get your custom environment.
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-