Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!keith
From: keith@EXPO.LCS.MIT.EDU (Keith Packard)
Newsgroups: comp.windows.x
Subject: Re: xdm => bug (or should I call it an insect)
Message-ID: <9008160412.AA18389@xenon.lcs.mit.edu>
Date: 16 Aug 90 04:12:12 GMT
References: <HARKCOM.90Aug15143320@potato.pa.Yokogawa.CO.JP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 41


>    I recently started using xdm. At first I thought "no problem, I can
> put up with the changes". Now I see that it is more than a minor change.
> xdm doesn't read the 'login' file when it logs in a user. This makes for
> some nasty complaints from the users.

You can get xdm to read the .login/.profile file by:

	a) invoking xterm -ls as the user session.  xterm -ls creates
	   a login shell process which should read the file.

	b) including code in Xsession which checks the shell of the
	   user, and invokes a separate session program which reads the
	   file

Xsession:

#!/bin/sh

case $SHELL in
/bin/sh)
	exec Xsession-sh
	;;
/bin/csh)
	exec Xsession-csh
	;;
esac
exec xterm -ls

Xsession-sh:

#!/bin/sh
. $HOME/.profile

<insert rest of session here>

Xsession-csh:
#!/bin/csh
source ~/.login

<insert rest of session here>