home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp
- Path: sparky!uunet!news.claremont.edu!nntp-server.caltech.edu!draco.macsch.com!drd
- From: drd@macsch.com (Daniel R. Dawson)
- Subject: Re: ksh and HP Console?
- Message-ID: <1992Aug20.173408.19442@draco.macsch.com>
- Sender: usenet@draco.macsch.com (Usenet Poster)
- Organization: The MacNeal-Schwendler Corporation
- References: <GHENNIGA.92Aug18125155@ampere.ampere> <1992Aug19.191008.27222@hpcvusn.cv.hp.com>
- Date: Thu, 20 Aug 92 17:34:08 GMT
- Lines: 29
-
-
- |> No flames for what might be a dumb question, but, why is it that
- |> when I log in to the console and then start a terminal, by clicking the
- |> terminal icon under HP VUE, it doesn't appear to read my .kshrc or my
- |> .profile, even though it does start up in the Korn Shell? The "Console"
- |> terminal window reads everything OK but any subsequent terminal I start,
- |> whether it be by clicking the icon or manually via the hpterm executable
- |> fails to set my environment properly by reading these files.
-
- This ksh behavior is independent of HP VUE. When your LOGIN shell is ksh,
- it will read your ~/.profile. Subsequent invocations of /bin/ksh won't
- read any startup script unless you explicitly ask for it. How do you ask for
- it? The ENV environment variable. In your ~/.profile, do a
-
- ENV=~/.kshrc
- export ENV
-
- This will make the ksh read your ~/.kshrc each time it creates a subsequent
- shell.
-
- This parallels the C-Shell in that the .profile is like a .login, and
- a .kshrc is like a .cshrc. This method can also be used for the
- Bourne shell as well.
-
- Dan Dawson
- The MacNeal-Schwendler Corporation
- Phone: (414) 357-0338
- Email: D_Dawson@macsch.com or D_Dawson@draco.macsch.com
-
-