Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I have a few machines running a distributed computing project 24/7 (folding@home), & I have recently set up XDMCP to manage them. Essentially I have a single management machine, which connects via XDMCP to the headless machines on my local network. I have created basic scripts to connect the 4 machines to display:2 through to display:5 & can hit ctrl-alt-F9 to F12 to keep an eye on these machines, which is a very tidy setup by my usual standards
Unfortunately I found the machines had dropped their sessions yesterday, and my scripts couldn't reconnect me as /tmp/X lockfiles were still present, is there any way I can force the X sessions to stay alive?
I also need the sessions to persist in the event that the monitoring machine is rebooted or the NIC in that box drops a few packets, so that when I reconnect I simply unlock my previous session, rather than being presented with the login screen anew.
If the connection drops again I will swap the onboard NIC in my monitoring machine with a pci 3com or maybe an intel NIC if I can find one amongst all the junk, which might cope with the load a little better - I noticed network utilisation was pretty high every now & then.
It's a good point, but I really like having sessions I can reach at any time with a simple ctrl-alt-F9 to F12 All has been well for the last day or two, I can see the switch is busy & the XDMCP connections are still alive, but if it drops again I might have to think about going the vnc route - thanks ramram.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.