Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have xinetd set up to start my Xvnc server. Occaisionally, my VPN hangs or disconnects and so I lose my vncviewer/client session. I would expect to be able to reconnect to the Xvnc server by restarting vncviewer, but xinetd seems to be terminating the server when my vncviewer session ends. I would like the Xvnc server to stay alive so I can reconnect to it with vncviewer.
As a workaround, I've stopped xinetd and started a Xvnc session from the command line, and this works exactly as I want. But I have to stop xinetd to accomplish this, or else my vncviewer sessions only connect to the Xvnc server which is started by xinetd.
I've tried many different Xvnc opions to accomplish this (-noreset, removed
the -once, etc) but none seem to matter. I've also changed the xinetd WAIT
from no to yes, but that doesn't work either. (In fact, it has a wierd
side effect of spinning on starting a Xvnc server, which immediately dies,
and so it starts another one.)
And as long as we're on this subject, what is the ":42" in the server options in /etc/xinetd.d/vnc? The normal way to start Xvnc is the :1, :2 etc which correspond to the display for the vncviewer session.
I guess I just need to learn where can I learn more about how xinetd controls Xvnc.