Operating System - HP-UX
1833582 Members
3784 Online
110061 Solutions
New Discussion

bind X to another network interface

 
SOLVED
Go to solution
jamesps
Regular Advisor

bind X to another network interface

How do I bind the X server to another interface? It is currently bound to my primary nic which is lan0. When this interface loses connectivity, CDE hangs and I am trying to avoid that. I could bind it to localhost and never have the same problem again. Any advices? Thanks!

James.
5 REPLIES 5
harry d brown jr
Honored Contributor

Re: bind X to another network interface


I personally would replace my primary nic card if I was having that many problems.

live free or die
harry d brown jr
Live Free or Die
jamesps
Regular Advisor

Re: bind X to another network interface

How could I simply bind it to localhost?
harry d brown jr
Honored Contributor

Re: bind X to another network interface


Are you using cde on the console?

if not, then you must replace your nic card, cable, or switch ports.

how are you starting CDE?

live free or die
harry d brown jr
Live Free or Die
Bill Hassell
Honored Contributor
Solution

Re: bind X to another network interface

Xwindows is critically attached to networking, not a specific NIC. As long as you are using DNS, loss of your network will hang CDE, regardless of whether you are just working locally. To reduce your dependence on networking, edit the /etc/nsswitch.conf file and change the order of hostname resolution:

hosts: files [NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=retur
n UNAVAIL=continue TRYAGAIN=return]

Since /etc/hosts should have both localhost and loopback (127.0.0.1) as well as your hostname, loss of the network should only affect remote access.


Bill Hassell, sysadmin
jamesps
Regular Advisor

Re: bind X to another network interface

I am using CDE on the local console. CDE starts at boot normally via dtlogin.rc script. Everything works normally.

The problem I was experiencing was for example when I unplugged the network cable. I wanted the CDE to "use" the localhost instead of "looking out" for the external lan0 interface.

I will try changing the nsswitch.conf as Bill suggested.

Thank you all for your replies!

James