Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!samsung!mips!pacbell.com!att!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!ux2.cso.uiuc.edu!ejk
From: ejk@ux2.cso.uiuc.edu (Ed Kubaitis - CSO )
Newsgroups: comp.unix.aix
Subject: Re: .Xdefaults not being used
Message-ID: <1991Mar14.121729.9595@ux1.cso.uiuc.edu>
Date: 14 Mar 91 12:17:29 GMT
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: ejk@ux2.cso.uiuc.edu (Ed Kubaitis - CSO )
Organization: University of Illinois - Urbana
Lines: 24


  >Has anyone else noticed that in X-Windows after updating to 3003, .Xdefaults
  >seem to stop being used after a while?  Things work for a few hours, ...
  
Perhaps until you happen to use InfoExplorer? If so, here's the story: Info's 
front-end shellscript does an 'xrdb' which wipes out your resource definitions
for all subsequently invoked clients. Circumvention is to comment out the 
'xrdb $KEYFILE' in /usr/bin/info.

This problem has been reported as APAR IX16234 which suggests editing the
script to change xrdb to xmodmap, apparently what was intended. Info also
alters the server font paths which creates problems for some non-IBM servers
such as NCD & HP (APAR IX16886). 

IMHO the real problem is clients have no business tampering with font paths, 
key definitions, resource database, or other server items. Only users or 
session managers acting on the user's behalf should modify them. At the very 
least, Info's tampering should be clearly documented and an option provided 
to bypass it. (Note: I really *like* InfoExplorer. I just find it's behavior
arrogant in this regard.)

----------------------------------
Ed Kubaitis (ejk@uxh.cso.uiuc.edu)
Computing Services Office - University of Illinois, Urbana