New answers tagged vnc
Based on the info provided by Greg in this thread I wrote a bash script that will automate the process of changing your system's VNC listening port. Works well in my tests. Let me know if anyone has any issues with it. #!/bin/sh #If you find it useful (or have suggestions, feedback, etc.), shoot me an email at email@example.com. #Requires Mac OS 10.7.x ...
A useful tools is slay: sudo slay username If you don't run slay as root, you will end up killing off all of your processes however, rather than the specified user. See also: http://unix.stackexchange.com/questions/18043/how-do-i-kill-all-a-users-processes-using-their-uid
The CPU problem on team viewer seems to be only on newer versions of team viewer. So, if you downgrade to an older version, this may solve the problem. Older versions are available here.
On you local machine (outside your network) you should run ssh client with following parameters: ssh -L 5999:imac_host:5900 pi_host I chose 5999 for local port but it could be any port. You only have to make sure it is not used by any local service. Substitute imac_host and pi_host with ip addresses. When you successfully connect with given command, vnc ...
Top 50 recent answers are included