Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!orca!mesa!rthomson
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Newsgroups: comp.windows.x
Subject: Re: HP xdm problem
Message-ID: <1991Jan29.010127.2357@dsd.es.com>
Date: 29 Jan 91 01:01:27 GMT
References: <1991Jan28.193724.21751@msuinfo.cl.msu.edu>
Sender: news@dsd.es.com
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Lines: 30
Nntp-Posting-Host: 130.187.85.21

In article <1991Jan28.193724.21751@msuinfo.cl.msu.edu>
	leekin@kira.msu.edu (Kin-Wing Edwin Lee) writes:
>1. It does not read users' .Xdefault file instead it uses the
>system defaults.

Make sure that either the session script (Xsession) or the user's
.xsession loads their .Xdefaults into the database.  My .xsession has
``xrdb -load .Xdefaults'', just like my .xinitrc had (when I used
xinit).

>2. xclock is always two hours slower than the system clock
>which is kind of annoying.

On some systems, login(1) sets a variable to indicate the time zone of
the machine.  This is called TZ on MIPS boxes.  Check the man page for
login(1) to see what kind of environment it sets up.  There may be
more environment setup in the /etc/{cshrc,profile} system-wide startup
files.

Since xdm doesn't exec login, these environment variables may not be
setup properly.  I modified Xsession to set the time zone variable TZ
and the LOGNAME variable (from $USER).  See also the man page on
xdm(1) to see what the environment is like when these scripts are run.

						-- Rich
-- 
  ``Read my MIPS -- no new VAXes!!'' -- George Bush after sniffing freon
	    Disclaimer: I speak for myself, except as noted.
UUCP: ...!uunet!dsd.es.com!rthomson		Rich Thomson
ARPA: rthomson@dsd.es.com			PEXt Programmer