🚀 go-pugleaf

In article <34338@fmsrl7.UUCP>, pms415!reso@fmsrl7.srl.ford.com (Dennis M. Reso) writes:
|> 
|> I am using Ultrix 4.1 on a DECstation 5000, UWS version 4.1
|> with the following in /etc/ttys to start the X server and
|> hang the Xprompter on the console instead of getty:
|> 
|>   :0 "/usr/bin/login -P /usr/bin/Xprompter \
|>       -C /usr/bin/dxsession" none on secure \
|>       window="/usr/bin/Xtm -bs -su"
|> 
|> I would assume that somewhere along the line, a login csh
|> will get exec'd by /bin/login, and read the $HOME/.login
|> file for csh users. But this doesn't happen. The .login
|> file is ignored.

     The only shells that start are in (d)xterms.  I'm assuming that you
     have some environment variables set in .login that you want set globally
     for the session.
 
|> One can always use the "-ls" flags with dxterm, for example,
|> to get the environment (or put everything in .cshrc).  But
|> what of a single process that one would like to background
|> at login: you don't want one for every window you start
|> with "dxterm -ls".

      What I would do is replace the call to /usr/bin/dxsession in /etc/ttys
      with a csh script that sources the user's .cshrc and .login then
      exec's dxsession.
 
|> The MWM window manager seems no better behaved than dxwm.
|> Is there something I'm missing in the above ttys line?
      
      It's not the resposibility of the window manager to set up the 
      environment.  It just passes the environment in which it starts
      on to the clients.
 
Mike

-- 
 Michael Ewan    (503)627-6468      Internet:  mike@raven.USS.TEK.COM
 Unix Systems Support                   UUCP:  ...!uunet!raven.uss.tek.com!mike
 Tektronix, Inc.                  Compuserve:  73747,2304
"Fig Newton: The force required to accelerate a fig 39.37 inches/sec."--J. Hart