On Fri, Oct 26, 2001 at 05:40:57PM -0600, Jeff Vincent wrote: > I can have ALL users connect to port 5953 (for example) if they so desire, > because they each will get their own new session with their own login prompt.
Okay, my mistake. But then the session is not persistent, if I understand correctly. With the initscript, the session is persistent, so that when you reconnect you get your own session back again (subject to RFB authorisation). > What are MIT cookies? The strings of bits that 'xauth' deals with. > So with the "joe:3" and the init.d/vncserver script method, joe gets his own > session running in the background when the server boots on screen 3 that he > merely needs to connect to in order to use? Correct? If running many users, > would having many sessions running (potentially unused) cause system resource > (CPU, memory) issues? Yes, but then there is no real way to avoid that and still have persistent sessions. It's not really for lots and lots of users. > Does this require joe to have already setup his .vnc > directory and vncpassword file? Yes, it does. I think that probably both methods are useful for different purposes. Should the Red Hat Linux VNC RPM make the xinetd method easier? (One way to do that would be to bundle an xinetd config file with it for the 'VNC' service, and then you just need to 'chkconfig vnc on'.) Let me know if there is demand. Tim. */ [demime 0.97b removed an attachment of type application/pgp-signature] --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
