Tim, Forgive my ignorance, but I'm not sure I follow you when you said "you can't have multiple users without adding extra services".
Currently, I have one vnc service setup for each screen resolution/colordepth pair that I want/need available: //From /etc/services vnc-640x480x8 5950/tcp vnc-800x600x8 5951/tcp vnc-1024x768x8 5952/tcp vnc-1280x1024x8 5953/tcp vnc-1600x1200x8 5954/tcp . . . and other identical sets for color depths 16 (ports 596x), 24 (ports 597x) and 32 (ports 598x). 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. They can then use that to log into their own account. It isn't limited to one user per xinetd service at a time. In fact I can attach multiple times to my own account using port 5953 on the same box and get a new independent session for each instance. What (I don't think) I can do is share a single session across multiple viewer instances (unless possibly by adding some flags to the server_args entry in my xinetd.d/vncserver file) or have a persistent sessions. I also believe there is a way to secure it with SSH but I don't need to so I don't know for sure. What are MIT cookies? 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? Does this require joe to have already setup his .vnc directory and vncpassword file? Sounds like a lot more hassle to setup and configure (unless you need to share the desktop or have a persistent session survive even when the viewer is closed.) New enlightenment on this topic will be greatly appreciated. Jeff >>> [EMAIL PROTECTED] 10/26/01 04:10PM >>> On Fri, Oct 26, 2001 at 01:10:37PM -0600, Jeff Vincent wrote: > My information only works if using xinetd and not launching vncsever through > the rc.d scripts. I haven't yet figured out what the /etc/init.d/vncserver > script actually buys me yet. I'm open for any information on how or why to > use the vncserver startup script vs. configuring xinetd. Because that way you get your own xstartup run as well, and get the MIT cookie set up too. Also, with xinetd AFAIK you can't have multiple users without adding extra services. It seems neater to me to be able to add 'joe:3' to /etc/sysconfig/vncservers. This functionality had been asked for several times on this list. 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 --------------------------------------------------------------------- --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
