Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A better method to awake the OSXvnc server' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A better method to awake the OSXvnc server
Authored by: meikokun on Mar 07, '07 10:56:27AM

Whilst I still prefer my approach for an initial contact with a new VNC user (all the instructions it takes to start the connection is "double click the zip; in that folder double click the startvnc icon" with a maybe "click connect") I like your shell script for the e-mail option.
However, if I use it and start a vnc session, then stop that session, I am unable to start one again without going to the terminal (or activity monitor) and terminating the OSXvnc-server process. If I don't do this, on a second launch of the applescript containing the shell script, it just hangs (does the same if I run it from script editor). Short of manually terminating the process in activity monitor or terminal, which would of course leave those windows open on vnc disconnect, how do you enable a system for take over without more end user intervention?
For some reason using the GUI to restart the vnc session [either manually or with an applescript] with either Vine Server or OSX VNC -or indeed Schnitz remote- doesn't cause this problem, even if the process is not terminated as it would be by hitting the 'Disconnect'/'Stop Server' button or whatever.



[ Reply to This | # ]
A better method to awake the OSXvnc server
Authored by: wallybear on Mar 07, '07 11:48:20PM

In effect I did a GUI wrapper to this solution, and so all the user has to do is click the "connect" button of my application (there is a choice of ports too, just in case; moreover, it's scriptable).
I didn't make that GUI public because i'm not sure about OSXvnc server license.

I see that Schnitz Remote Lite wraps OSXvnc server in it, so now I can think there are no licensing problems. Perhaps I'll post it.



[ Reply to This | # ]