On Wed, Feb 19, 2003 at 09:48:10AM -0600, Bob Willcox wrote: > On Wed, Feb 19, 2003 at 07:41:45AM -0800, Erick Mechler wrote: > > :: > For example, if you have xdm starting out of /etc/ttys and you blindly > > :: > update everything mergemaster tells you to, you might overwrite some of > > :: > your custom configs. > > :: > > :: Well, I don't use xdm. I always have (for many years now) started the > > :: X server using startx, and I do see that startx (which hasn't been > > :: changed on my system since last December) does explicitly specify > > :: "-nolisten tcp" if not told otherwise. > > > > Perhaps you had an entry in your .xinitrc to override the command-line > > settings which isn't there anymore? Eh, just grasping at straws here... > > I couldn't find anything...besides I haven't changed my .xinitrc in > sometime. > > Bob > > > > > Cheers - Erick > > -- > Bob Willcox We seem to have forgotten the simple truth that > [EMAIL PROTECTED] reason is never perfect. Only non-sense attains > Austin, TX perfection. -- Poul Henningsen [1894-1967]
This is just another shot in the dark, but I see that you are trying to connect to a machine named 'luke'. Maybe your /etc/hosts file was overwritten and now name resolution isn't happening like it should locally? What happens if you try to connect using the ip address like: $ xterm -display 192.168.1.100:0 Also, when on the machine named 'luke' what is the output of `xhost`. If you want everyone to be able to connect then it should output something like: $ xhost access control disabled, clients can connect from any host Also, can you verify 100% that X is actually listening on host 'luke' by browsing the output of `sockstat -l4`? One more thing: how did you upgrade? Are you certain that you don't have a firewall running on the newly upgraded system? Good luck, Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc
msg53811/pgp00000.pgp
Description: PGP signature
