current community

your communities

more stack exchange communities

company blog
Stack Exchange Inbox Reputation and Badges
tour help
Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
up vote 1 down vote favorite

I have multiple computers in my house and like to change the VNC listening ports on each to unique numbers as an added layer of protection.

In the past, when changing the VNC listening port on my two Macs, I've followed the following prior article:

 http://superuser.com/questions/148095/how-to-change-the-default-screen-sharing-vnc-port-number-on-mac-os-x

However, when I tried to following this article (after upgrading to El Capitan), SUDO will not permit me to Write / Save the file after making the requisite changes. It just says "ERROR WRITING".

I never had this problem before with Mountain Lion or Yosemite.

Your suggestions are greatly appreciate (please note that I am only a novice so please provide step by step instructions).

Thanks!

share|improve this question
    
What were you doing with sudo when the error occurred? Sudo doesn't really do anything except for run another command, so it would be helpful to know what command "sudo" was trying to run. The text editor (vim / nano) or launchctl? (The "sudo" command helps with some permissions.) Also, the title of your question has a spelling error (s/Chance/Change/) – TOOGAM Oct 3 '15 at 13:10
    
This is entirely down to the new 'rootless' feature of El Capitan. su/sudo now no longer gives you permission to write files in the system directory. One option is to disable this feature; but this is not recommended. – PaulSkinner Oct 5 '15 at 12:40
up vote 2 down vote

The best way I've found so far for El Capitan is: http://superuser.com/a/714931/135611 whereby you change the port number for the vnc-server service by editing /etc/services (which is still allowed with rootless).

So: sudo nano /etc/services and change the vnc-server ports. Then restart vnc-server with:

sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -restart -agent
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.