23 June 2014

Netsupport Mac Client CPU Issue

Netsupport is great.  It allows you to remote access, and control other machines on your network.  Of course there are other ways to do it eg RDP, and VNC, but netsupport nicely ties it all together and makes it very easy.

I did have an issue however, on the Mac, I just wanted to install the Netsupport Manager,  ie I just wanted to control other machines, and not be controlled.  During the installation there didn't seem to be any options to not install the client, but as I checked the 'control and manage only' option (or words to that effect) and assumed the client wouldn't be installed.  

Not only was the client installed, but when the machine is idle. The Netsupport Client processing is running, and taking up about 8-10% CPU all the time.  As I have a reasonably decent machine (OS X 10.9.3, 2.3GHz i7, 16GB RAM) this CPU use is hardly noticeable, but it really bugged me.

Killing the process wont work as it's restarted automatically, so I had to look a little deeper.

The secret is in

/Library/Preferences/NetSupport/NetSupportManager

There are 2 files:

ns-login.sh
ns-logout.sh

In the login file I just commented out the line where the monitoring process is started:

#${SESSIOND} "*" /s &

This stops the client from being started, and restarted.  The Netsupport Manger still works, ie connects and Controls other machines, but I dont have the Client eating 10% of my CPU now.

No comments: