Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Feb 2003 09:23:47 -0800
From:      Nathan Kinkade <nkinkade@dsl-only.net>
To:        stable list <freebsd-stable@freebsd.org>
Subject:   Re: Updated to today's -stable and can no longer connect to the XFree86 server
Message-ID:  <20030219172347.GV288@sub21-156.member.dsl-only.net>
In-Reply-To: <20030219154810.GA53525@luke.immure.com>
References:  <20030218161705.GA4876@luke.immure.com> <20030219011808.GK50962@rot13.obsecurity.org> <20030219033811.GA25426@luke.immure.com> <20030219152441.GG64649@techometer.net> <20030219153806.GA41721@luke.immure.com> <20030219154145.GI64649@techometer.net> <20030219154810.GA53525@luke.immure.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--D/26AIznG/rf8cgR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 bli=
ndly=20
> > :: > update everything mergemaster tells you to, you might overwrite so=
me of=20
> > :: > your custom configs.
> > ::=20
> > :: 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.
> >=20
> > 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...
>=20
> I couldn't find anything...besides I haven't changed my .xinitrc in
> sometime.
>=20
> Bob
>=20
> >=20
> > Cheers - Erick
>=20
> --=20
> Bob Willcox            We seem to have forgotten the simple truth that
> bob@vieo.com           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`?=20

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

--=20
GPG Public Key ID: 0x4250A04C
gpg --keyserver pgp.mit.edu --recv-keys 4250A04C
http://63.105.21.156/gpg_nkinkade_4250A04C.asc

--D/26AIznG/rf8cgR
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+U72jWZYS9EJQoEwRAo6zAKC+HhFhZs35lc0wnlUhAbUbrvUCyQCffbvt
jt39qxeBt5gIR3Pr1WhFNjY=
=NrVn
-----END PGP SIGNATURE-----

--D/26AIznG/rf8cgR--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030219172347.GV288>