Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tekgen!mike From: mike@tekgen.BV.TEK.COM (Mike Ewan) Newsgroups: comp.sys.dec Subject: Re: whither .login with Xprompter/dxsession on DS5000 Message-ID: <7275@tekgen.BV.TEK.COM> Date: 3 Feb 91 16:57:19 GMT References: <34338@fmsrl7.UUCP> Reply-To: mike@tekgen.BV.TEK.COM (Mike Ewan) Organization: Tektronix, Inc., Beaverton, OR. Lines: 26 In article libove@libove.det.dec.com (Jay Vassos-Libove) writes: >I believe that this thread is relevant to something I tracked down in >the source code a while back... > >When a user logs in to a unix system the shell that gets started up >is usually a "login" shell, which is very closely defined by how it >is started up. It turns out that it is not possible to get a shell to >be a "login" shell _underneath_ the X Session Manager under the Ultrix >Worksystem Software and therefore have all applications inherit a path, >environment variables, etc. [stuff deleted] However, if you run xdm instead of Xprompter you can do something like the following and assuming xdm runs a csh script called ~/.xsession: In ~/.xsession: !#/bin/csh source .csh_env dxsession In .csh_env put all your appropriate setenv's. If you start mwm and a dxterm in .xsession instead of dxsession, mwm will inherit the environment. I don't know for sure that dxsession will but I believe so. Mike