Xref: utzoo comp.sys.att:10710 comp.unix.sysv386:1667 Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ukma!kherron From: kherron@ms.uky.edu (Kenneth Herron) Newsgroups: comp.sys.att,comp.unix.sysv386 Subject: Re: Virtual Terminals Message-ID: Date: 30 Oct 90 15:11:16 GMT References: <1990Oct29.000407.13391@mccc.uucp> <1990Oct29.163846.4299@eci386.uucp> Organization: U of Ky, Math. Sciences, Lexington KY Lines: 24 woods@eci386.uucp (Greg A. Woods) writes: >In article <1990Oct29.000407.13391@mccc.uucp> pjh@mccc.uucp (Pete Holsberg) writes: >> However, when I invoke a new virtual terminal -- either with the hot key >> or via 'newvt' -- the shell in the new VT does not execute /etc/profile >> and it does not execute $HOME/.profile! It *does* execute /etc/env and >> $HOME/.env! >I'm not sure how it really works, but I would assume the new shell is >a child of newvt, thus inherits your current environment. If ksh is >executing $ENV, then you should have an identical working environment, >as well as identical environment variables. The new shell isn't a login shell, so it's not appropriate for it to run /etc/profile or .profile. I've always assumed without checking that shells started with vtlmgr use the environment that existed when vtlmgr was run, and that newvt'd shells use the current environment. If you add the line "ALTSHELL=YES" to /etc/default/login then newvt and vtlmgr will exec whatever your SHELL variable is set to. Kenneth Herron