[2862] in SIPB_Linux_Development
Returned mail: User unknown
daemon@ATHENA.MIT.EDU (Mail Delivery Subsystem)
Tue May 16 02:18:45 2000
Date: Tue, 16 May 00 02:18:09 EDT
From: MAILER-DAEMON@MIT.EDU (Mail Delivery Subsystem)
To: <linux-dev@MIT.EDU>
----- Transcript of session follows -----
>>> RCPT To:<willkoffel@sauna.ne.mediaone.net>
<<< 550 <willkoffel@sauna.ne.mediaone.net>... Relaying denied
550 <willkoffel@sauna.ne.mediaone.net>... User unknown
----- Unsent message follows -----
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
id AA18793; Tue, 16 May 00 02:18:09 EDT
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id CAA11868;
Tue, 16 May 2000 02:18:11 -0400 (EDT)
Received: from Jessica-Rabbit.mit.edu (IDENT:amu@JESSICA-RABBIT.MIT.EDU [18.241.1.193])
by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id CAA09801;
Tue, 16 May 2000 02:18:11 -0400 (EDT)
Received: by Jessica-Rabbit.mit.edu (8.8.7/4.7) id CAA12668; Tue, 16 May 2000 02:18:10 -0400
Sender: amu@JESSICA-RABBIT.MIT.EDU
To: Bryan S Ly <bly@MIT.EDU>
Cc: linux-help@MIT.EDU
Subject: Re: overriding .Xresources
References: <200005160459.AAA01002@bryan.mit.edu>
X-No-Markup: yes
Reply-To: linux-help@MIT.EDU
From: amu@MIT.EDU (Aaron M. Ucko)
Date: 16 May 2000 02:18:08 -0400
In-Reply-To: Bryan S Ly's message of "Tue, 16 May 2000 00:59:06 -0400"
Message-Id: <udlzopr9fxb.fsf@Jessica-Rabbit.mit.edu>
Lines: 17
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4.92
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Bryan S Ly <bly@MIT.EDU> writes:
> for some reason, my Redhat 6.2 - Athena install overrides my .Xresources file
> when i log in. Has anyone exeperienced this or know a way to solve this
> problem?
Does this problem occur all the time, or just for remote X logins from
PCs? If it's restricted to the latter case, the problem is that an X
server is supposed to reset itself and discard all its resources when
it finds it has no clients, which happens if xrdb is the first client
you run. You can work around that problem by running xrdb with the
-retain flag.
Otherwise, please describe your problem in more detail.
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)