On Tue, 2006-10-10 at 18:00 +0100, SheridanJ West wrote:

On 10/10/06, Dave Howorth wrote:

...

SheridanJ West wrote:

...

change the default x server's ip and use another instead

It sounds like you're trying to specify network behaviour at the application level. An X server runs on a host and is contacted via a port on a host. It's up to the network software to decide how to route packets between it and a client.

What are you trying to do that you think needs you to specify an interface for the X server? And why don't you think you can do that in the networking subsystem?

Cheers, Dave

Dave

specifying that a will use x, and b shall use y is straightforward in say mail systems.

I don't know what a is, or x, or b or y. And we're talking about X servers, not mail systems. So this doesn't help me, or I suspect anybody else, understand what you're trying to do.

Host is a fancy term for machine.

Indeed so. It's the term X uses, as it happens. I'm happy with either.

The network subsystem does not seem to have a option to say x use this ip than another to and my knowledge, while a proxy would message the issue, firewalling too is not a good option either

You still haven't explained what you're trying to do.

Theres got to be a way of telling X to use this ip a rather than ip b.

Why? That is, why do you believe that and also, why do you need to do it? As long as X can make a connection from client to server, why should it care how it's routed? Cheers, Dave PS Please don't copy me on replies.