Tight VNC Server load on boot

[wwihead]

Hi all,
I'm trying to follow the instructions on raspberrypi.org/documentation for loading a tightvncserver on boot of the pi. I'm new to this, so please forgive my basic question - how do I create a file within the directory /etc/init.d and how do I then save it, please?

Many thanks

[DougieLawson]

There's a skeleton in /etc/init.d/skeleton. Copy that and save it with a new name in /etc/init.d. Then edit the new file to start tightvnc. Make the file executable with chmod 755 /etc/init.d/newfilename. Then use update-rc.d to activate it at boot time.

[wwihead]

Thank you for the reply. I followed the instructions but I still get an active refusal from the pi to the viewer machine. Is there a way to check if the server is running on the pi after startup please?

[DougieLawson]

sudo netstat -tlnp

[AndyD]

Thank you for the reply. I followed the instructions but I still get an active refusal from the pi to the viewer machine. Is there a way to check if the server is running on the pi after startup please?

Have a look at this thread.

[wwihead]

Thank you. Tried netstat before and after a manual startup of vncserver and it appears it hadn't loaded on boot.

[DougieLawson]

Is your new /etc/init.d/newscript executable?
What happens if you run /etc/init.d/newscript start or /etc/init.d/newscript status

[wwihead]

Thank you both so much. I think I have solved it. The target machine was named incorrectly in the script and was refusing connections. Great forum and I've learnt so much already!