All-
We are running RHEL3 and RHEL4 on our network and have run into a problem with some third party design tools we run on a compute farm as part of that network. They want to contact an X-server as part of license identity checking. In order so to do we have to run xhost + <compute farm hosts> since we don't know which host it will end up on, and we do not want to open access to all the desktop machines as well as the compute farm. ( So just xhost + by itself is not adequate. ) I have seen under some third party X servers the ability to place a .xhost file in a users home directory and get the effect I want without having to enter it explicitly. For a number of reasons, it is highly desireable that we not fiddle with user's environments, so embedding an xhost command in .login or .cshrc for instance is not a real good solution. Is there any hope to use the .xhost idea or something like it under RHEL3 or 4? If so, what are the details?
Thanks,
Wilville
We are running RHEL3 and RHEL4 on our network and have run into a problem with some third party design tools we run on a compute farm as part of that network. They want to contact an X-server as part of license identity checking. In order so to do we have to run xhost + <compute farm hosts> since we don't know which host it will end up on, and we do not want to open access to all the desktop machines as well as the compute farm. ( So just xhost + by itself is not adequate. ) I have seen under some third party X servers the ability to place a .xhost file in a users home directory and get the effect I want without having to enter it explicitly. For a number of reasons, it is highly desireable that we not fiddle with user's environments, so embedding an xhost command in .login or .cshrc for instance is not a real good solution. Is there any hope to use the .xhost idea or something like it under RHEL3 or 4? If so, what are the details?
Thanks,
Wilville