[fj.windows.x] Summary of xdm

harkcom@potato.pa.Yokogawa.CO.JP (Alton Harkcom) (08/17/90)

   I would like to thank everybody for their help. Here is a list of
the different methods for handling .login in xdm.

   I've edited them to try and make them as small as possible, yet still
use as much of the original posts as possible :-)


From: albert@ee.su.oz.au (Albert Hirawan)

1. Include the followings in .xsession (in this order):
- setenv TERM xterm
- source $HOME/.login
- execute .xinitrc if it exists, otherwise run twm (if desired,
  after creating a couple of xterm windows)
  This way, you don't have to modify your .cshrc, .kshrc, .login, ...

2. Make sure you DON'T test for environment variables in any of .cshrc,
  .login, .kshrc, .xinitrc,...   Xdm doesn't like it at all. Testing
  for existence of files is ok.


From: kucharsk@Solbourne.COM (William Kucharski)  --and--
From: timr@labtam.labtam.oz.au (Tim Roper)        --and--
From: jfy@castor.cis.ksu.edu (Joseph F. Young)

jfy> Use the "-ls" option on xterm and it will cause the shell to source
jfy> the .login or .profile as appropriate.
jfy> If you want to make it the default for xterm, add "xterm*loginShell: true"
jfy> to you X resources.


From: tale@turing.cs.rpi.edu (David C Lawrence)

 Seemingly the only thing you would be missing when
xdm does things its way is
the environment variables.  In order to keep them in one place to more
easily maintain them I have a .env file which I source from my
.bash_profile and my .Xsession.  I've told the users here that no
login files are processed automatically for them and that if they want
to do something like change the default path (which here includes all
of our bin directories) then they will have to do it from their own


From: keith@expo.lcs.mit.edu (Keith Packard)

  case $SHELL in
     exec Xsession-sh
     exec Xsession-csh
  exec xterm -ls

  . $HOME/.profile
  <insert rest of session here>

  source ~/.login
  <insert rest of session here>


From: Erik M. van der Poel <erik@sra.co.jp>

A good way to debug your .xsession is to have an .xsession like this:

  if test -f $HOME/.xsession.real
     exec xterm -e $HOME/.xsession.real
     exec xterm

And then have your ordinary .xsession renamed to .xsession.real. This
way, you can see any errors produced by .xsession.real.


   if I offended anybody by posting their reply, I'm sorry. I thought
there might be a lot of people out there who could use this :-)

  $@2#2OEE5!3t<02q<R(J PA$@#15;#22](J
  TEL 0422-52-5748  FAX 0422-55-1728
  E-mail harkcom@pa.yokogawa.co.jp