--OwLcNYc0lM97+oe1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

hi,

Michael Trausch wrote:
> On 7/15/05, Ignatios Souvatzis <ignatios@cs.uni-bonn.de> wrote:

> > I suggest to put entries for ::1 and 127.0.0.1 into /etc/hosts
> >=20
> > ::1             localhost
> > 127.0.0.1       localhost
> >=20
> > and to make sure that /etc/nsswitch.conf has
> >=20
> > hosts: files dns
>=20
> Yes, those are just as you describe that they should be, too.  :-(

In this case I think it must be a DNS problem. (you described xauth=20
as affected..)

(I'm assuming that you don't have your home on NFS here.)

Use tcpdump -v to find out what happens on the local net at the beginning
of those 5minute intervals.

Oh yes... are you using a (caching) DNS server inside your local network,
or does every DNS request go through the NAT?

Hm... do you have entries for both the addresses on your ethernet=20
interface:
>         inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
>         inet alias 192.168.0.99 netmask 0xffffff00 broadcast 192.168.0.255

in /etc/hosts? xauth and xdm, for example, try to find out the machine name
by finding a local address, then resolving that to a name. 192.168.x.y.=20
won't ever be resolved by public DNS...

Regards,
	-is

--OwLcNYc0lM97+oe1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBQtfMAzCn4om+4LhpAQEbeQgAxntHplYTY3A6mdHC0rX8dtln8Gp5Sk1K
iYiSDtPYxl4J3xgYmQLfgRW4e0LnUgDn/UIergc+yVKWhWuKR0RhfIrZPIH5bOrW
ozBhTNmc/dIYY47gDxnrSia0ff0DCszVenfw8L/95NFrc0u6ER8u58bk20Aw6tnB
C0HRef9AJ15n0lbpeJg1/tBgmkwpULlMGi3MD2U/ZRLEzUtN6NHXgVlDyZvAW4Z0
x+F4VoSojj5g8FqHNx1N9z0YynNZjxCLjjFKPpf23wmYC3CiUTCl1nZRLto35Vw4
LILnCGY1HV175t7gDKIXAxw20t9+I3eplDUVdZjxtgOZjQyOXfoKng==
=tVl6
-----END PGP SIGNATURE-----

--OwLcNYc0lM97+oe1--