Difference between revisions of "How to launch VNC with aMule at Linux boot"

Revision as of 05:16, 7 September 2004

By Frankk

This describes a very simple configuration to launch VNC at Linux startup (as a specified user). aMule will be launched automatically with VNC. This will work in Slackware and distro based on the same init method. If someone knows how to modify it to make it work under other distros you are welcome to add it to this page. Thanks.

Add the rc.vnc script to /etc/rc.d

Modify user according to the user running aMule.
The rm /tmp/.X11-unix/X$theScreen is there in case the server crashes or your mother/wife removes the power plug cleaning the room... ;-)

#!/bin/sh
#
# Startup/Stop script for vncserver.
#

#Here, the choosen user to run amule
theUser=choosenuser
#And here, the choosen screen to run the vncserver
theScreen=1

case "$1" in

'start')
if [ -f /tmp/.X11-unix/X$theScreen ]; then rm /tmp/.X11-unix/X$theScreen; fi
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"
;;

'stop')
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver -kill :$theScreen"
;;

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

esac

Make it executable with:

chmod 755 /etc/rc.d/rc.vnc

Modify the following files:

In /etc/rc.d/rc.local add:

# Start VNC server
if [ -x /etc/rc.d/rc.vnc ]; then
. /etc/rc.d/rc.vnc start
fi

In /etc/rc.d/rc.6 add:

# Shut down the VNC server
if [ -x /etc/rc.d/rc.vnc ]; then
/etc/rc.d/rc.vnc stop
fi

In ~/.vnc/xstartup (in home directory of the user specified above) add (change with your preferred aMule startup script):

amule &

On Debian Woody

Run (as root):

apt-get install vncserver xvncviewer apt-get install vncserver flwm

There is no support for ~/.vnc/xstartup so, instead, use $vncStartup in .vncrc to determine a xstartup-script (this replaces your ~/.xsession file).

For more information, read man vnc.conf

For example, in a Woody/Sarge/Sid:
Login as the user who is going to run aMule
mkdir ~/.vnc/
Create the ~/.vnc/xstartup file, with the next content

/usr/bin/flwm &
/usr/bin/amule &
/usr/bin/amule &

With sone versions of vncserver, it's necessary to launch at least twice the aMule. The flwm is an optional window manager.

Create the file ~/.vncrc with the next content:
Login as the user and run xvncviewer :1 to create the password file and debug possible probelms (the logs are under the ~/.vnc/ dir

$vncStartup = "/home/amule/.vnc/xstartup";
$geometry ="800x600";

(replace /home/amule for the home of the user running VNC)

To show the aMule window, run:

xvncviewer localhost:1

Mandrake 10.0

The script from Frankk is the one I use, but you can customize the size of the VNC server :

/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"

add

/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen -geometry 1240x980"

or whatever value.

Personaly, I use as xstartup script (iceWM is really nice and so CPU-cheap) :

#!/bin/sh
starticewm&
amule

To start VNC at startup, I called the previous script /etc/init.d/amulevnc and chmod to 744 (chmod 744 /etc/init.d/amulevnc as root).
Instead of modifying /etc/rc.d/rc.vnc, I added links in the corresponding /etc/rc$RUNLEVEL.d directories.
It's quite simple to understand how it works:
Each directory represents a runlevel, and contains links to the scripts from /etc/init.d which need to be run/stop.
For instance, the link /etc/rc5.d/S55sshd to /etc/init.d/sshd will start sshd on runlevel 5, whereas /etc/rc6.d/K25sshd linked to /etc/init.d/sshd will stop it in runlevel 6.
You get it? Links starting with 'KXX' will stop a service, and those starting with 'SXX' will start them. The number will define the order.

So to run VNC on startup, just do (as root :-) )

ln -s /etc/init.d/amulevnc /etc/rc5.d/S99amule
ln -s /etc/init.d/amulevnc /etc/rc6.d/K02amule

and you're all set!

PS: This method should work on systems other than Mandrake, give it a test.

Questions & comments: air_1 at libertysurtf.fr