Solaris 9 RealVNC Startup Script Wanted

ingerul9 · 02-05-2008, 10:08 AM

Hi. I have a Sparc Solaris 9 machine. I've installed VNC.

Now the problem is how do I make it to automatically start when I reboot to machine? Does anyone have any idea how should I make this possible?

bathory · 02-06-2008, 03:26 AM

Take a look at this one.

Regards

ingerul9 · 02-06-2008, 04:35 AM

Ok. I don't know much about scripting so that's why I'm going to ask how to change the following for user root only.

Can I change it to

/bin/su - root -c "/usr/local/bin/vncserver :1"

In the end of the script it's written "esac". Shouldn't it be "case"? Any help is apreciated. Thank you.

#!/bin/sh
#
# Startup/Stop script for vncservers for some users.
#

case "$1" in

'start')
/bin/su - bob -c "/usr/local/bin/vncserver :1"
/bin/su - sally -c "/usr/local/bin/vncserver :2"
/bin/su - jim -c "/usr/local/bin/vncserver :3"
;;

'stop')
/bin/su - bob -c "/usr/local/bin/vncserver -kill :1"
/bin/su - sally -c "/usr/local/bin/vncserver -kill :2"
/bin/su - jim -c "/usr/local/bin/vncserver -kill :3"
;;

*)
echo "Usage: /etc/init.d/rc.vnc { start | stop }"
;;

esac

bathory · 02-06-2008, 05:03 AM

esac is the closing of case

So if you're sure you want just root to start vncserver modify the script like this:

Code:

#!/bin/sh
#
# Startup/Stop script for vncservers for some users.
#

case "$1" in

'start')
/bin/su - root -c "/usr/local/bin/vncserver :1"
;;

'stop')
/bin/su - root -c "/usr/local/bin/vncserver -kill :1"
;;

*)
echo "Usage: /etc/init.d/rc.vnc { start | stop }"
;;

esac

and create the appropriate symlinks

ingerul9 · 02-06-2008, 05:05 AM

Ok. I will try this way. Thanks a lot. I'll be posting if it works.

chris · 06-15-2009, 12:16 PM

Quote:

Originally Posted by bathory

esac is the closing of case

So if you're sure you want just root to start vncserver modify the script like this:

Code:

#!/bin/sh
#
# Startup/Stop script for vncservers for some users.
#

case "$1" in

'start')
/bin/su - root -c "/usr/local/bin/vncserver :1"
;;

'stop')
/bin/su - root -c "/usr/local/bin/vncserver -kill :1"
;;

*)
echo "Usage: /etc/init.d/rc.vnc { start | stop }"
;;

esac

and create the appropriate symlinks

Hi guys,

I have used this start script and it works well to start vncserver :1 but when I try and stop it with /etc/init.d/rc.vnc stop, what it does is start vncserver :2. Not too sure why that is or how to fix that.. any ideas??

Thank you,

Chris

bathory · 06-15-2009, 01:48 PM

What happens if you run directly from CLI:

Code:

/bin/su - root -c "/usr/local/bin/vncserver -kill :1"

after vncserver was started using /etc/init.d/rc.vnc start

chris · 06-15-2009, 02:18 PM

Quote:

Originally Posted by bathory

What happens if you run directly from CLI:

Code:

/bin/su - root -c "/usr/local/bin/vncserver -kill :1"

after vncserver was started using /etc/init.d/rc.vnc start

Thanks for the response.. looks like my problem was not using the quotes at the CLI. It still started the process when I started vncserver but killing whithout the quotes was what created a second vncserver PID.

All works well now thanks!

chris · 06-15-2009, 02:23 PM

Quote:

Originally Posted by chris

Thanks for the response.. looks like my problem was not using the quotes at the CLI. It still started the process when I started vncserver but killing whithout the quotes was what created a second vncserver PID.

All works well now thanks!

Actually there is one minor issue that is not preventing vncserver from starting but still is a cause for concern as it delays the start process and not sure exactly what else it may impact.

when I start vncserver I get the following message:

xauth: timeout in locking authority file /export/home/clamontagne/.Xauthority
xauth: timeout in locking authority file /export/home/clamontagne/.Xauthority

I'm trying to figure out what is causing this but any help on tihs one would be appreciated.

thanks!

bathory · 06-15-2009, 04:43 PM

Hi glad to see that the stop script had worked.
Now, about the xauth timeout quoting from openwin documentation, possible reasons and remedies:

Quote:

1. The user's $HOME is not writable by the user; $HOME may be owned by an entirely different user.
2. The lock file $HOME/.Xauthority-l already exists; remove this file.