In case anyone os interested, the problem turned out to be some spurious entries in my .Xauthority file. While poking around looking for the cause of the dialout, I did a 'xauth list' and got back about a dozen lines of stuff, including some entries for 192.168.0.1, which doesn't exist on my network. Apparently there was an attempt at a reverse name lookup for it.
In any event, deleting the .Xauthority file took care of it. I don't know where all of the other entries came from -- I have been using X on one platform or another for about 10 years and I recall seeing this once, and only once before and I didn't understand it then either. On Sun, Sep 19, 1999 at 10:35:15AM -0600, [EMAIL PROTECTED] wrote: > Greetings: > > After upgrading some X-window packages last night I cannot start X without > waiting for the modem to dial out and connect. It seems to be doing a name > lookup since, if I get back out of X and hang up the modem and then do a > startx immediately, there is no dial-out since the name lookup is still > cached. A few hours later, though, the problem is back. The packages that > updated last night were mostly fonts, but xbase-clients updated also. > > I am running slink, and my X packages come fronm: > > deb http://samosa.debian.org/~branden/ xfree86-334-slink/ > > Has anyone else seen this? Any ideas on how to stop it? > > -- Mark Zimmerman > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
