AMule Project FAQ - User contributions [en]

How to launch VNC with aMule at Linux boot

2005-06-23T09:49:14Z

PedroAlgarvio:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

'''ATENTION: THE BOOT PROCESS NOW WORKS'''

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no [http://www.x.org X] window manager at all. I only run web and mail services, and of course, [[aMule]]. Adapt to your situation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

# emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

<pre>
# vncserver :0
</pre>

I'm using '' ''':0''' ''because there is no window manager running, so no need to use'' ''':1''' '', plus, it will be simpler to connect to it like this, simply:

<pre>
# vncviewer <host>
</pre>

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

<pre>
# vncserver -kill :0
</pre>

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session. Edit ''~/.vnc/xstartup'':

<pre>
# vi ~/.vnc/xstartup
</pre>

You should see something like:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
exec wmaker
</pre>

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I now use [http://www.windowmaker.org/ WindowMaker], and don't want no terminal, just [[aMule]] so, it's like this:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
amule &
exec wmaker
</pre>

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

# vi /etc/init.d/vncserver

Make it look like:
<pre>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Load config"
PATH="$PATH:/usr/X11R6/bin/"

# The Username:Group that will run VNC
export USER="vampas"
#${RUNAS}

# The display that VNC will use
DISPLAY="0"

# Color depth (between 8 and 32)
DEPTH="16"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="800x600"
GEOMETRY="1024x780"
#GEOMETRY="1280x1024"

# The name that the VNC Desktop will have.
NAME="aMule"

OPTIONS="-name ${NAME} -depth ${DEPTH} -geometry ${GEOMETRY} :${DISPLAY}"
eend $? "Config not Loaded"
}

start() {
checkconfig
ebegin "Starting vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver ${OPTIONS}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
sleep 3
svc_start
}
</pre>

Make it executable:

# chmod +x /etc/init.d/vncserver

Now add it to boot:

# rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

----

AMule problems

2005-06-14T22:25:09Z

PedroAlgarvio:

<center>
<h4>[[aMule_Project_FAQ:About|aMule]] common problems</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[AMule_problems-es|Español]] | [[AMule_problems-nl|Nederlands]]
</center>

== I get an "aMule already running: exiting" message on the terminal when starting aMule. Will I be able to start it anyways? ==
The message is very clear: [[aMule]] is already running. But this doesn't refer to the entire system, rather that '''you''' (your user account) is already running [[aMule]]. 
It might seem that there is no instance of [[aMule]] running if it crashed on you. However, what sometimes happens is that some processes aren't completly closed keeping them in a state known as ''zombie'' or ''defunct''. To find out if this is your problem, run ''ps u | grep amule'' and if it shows any output (except the grep output itself), then there's some other aMule process running with your account. To kill it, either close it normally (if you can) or kill it with ''kill -9 <aMule-PID>'' or ''killall -9 amule'' or logoff and log in again (which, in most cases, will kill all [[aMule]] processes, unless you executed [[aMule]] with ''nohup'' or something similar). 
If non of the above suits you, then you can run another instance of [[aMule]] as another user (if you can log in with another account, of course). Read [[FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

== aMule starts but is never shown but works fine. What's going on? ==
This commonly happens when you set the type of systray integration, in Preferences -> General -> Misc Options, to ''Minimize to trayicon'' which starts [[aMule]] minimized. 
To be able to recover aMule's GUI, edit ''~/.eMule'' and search for ''StartupMinimized=1'' and once you find it, change that line to ''StartupMinimized=0''. The following script will do that for you: 
''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule'' 
When you next start [[aMule]] set the correct systray integration in Preferences so that you can enable "Start minimized" without having [[aMule]] hidden. 
If, for some reason, the above didn't work, try changing the Systray integration manually to the default by unchecking the "Enable tray icon'' option. To do so, set the ''DesktopMode='' value in ''~/.eMule'' to ''4''. The following script will do that for you: 
''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule'' 
'''NOTE:''' On [[aMule]] versions previous to 2.0.0rc4, you should set it to ''1'' instead of ''4'' since the Preferences storage changed a little.

== aMule starts but is never connecting/behaving very weird/crashing almost every few seconds/etc...? ==
aMule versions up to 2.0.0-rc3 shouldn't be linked against wxWidgets 2.5.x neither GTK2 although some Linux distributions tend to do so. Please make sure your aMule isn't the case. If unsure, paste you backtrace at [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum] or join aMule's IRC channel #amule at irc.freenode.net

== Where are my downloaded files? ==
By default, aMule stores completed files in ''~/.aMule/Incoming'' but, since ''~/.aMule'' directory is a hidden directory, your file manager might not show it. Make sure you have enabled your file manager to show hidden files. 
By default, files being downloaded are placed in ''~/.aMule/Temp'', so again, this is a hidden directory and the file managed must be configured to show hidden files.

== Why is aMule taking so much CPU resources at start-up? ==
This happens because aMule is hashing new files found on the Shared Directories. If aMule is always taking a lot of CPU at startup and no new files have been added or modified in any way in the Shared Directories, then something is wrong. 
In aMule versions earlier than 2.0.0-rc3 this used to happen when having the Temp, Incoming or any Shared Directory in a FAT32 partition. Since aMule 2.0.0-rc3 this is not happening any more. 
Also, in aMule versions earlier than 2.0.0-rc4 filesystems with UTF-8 encoding (known to happen with SuSE 9.1) could present problems when some file or directory in the Shared Directories path contanied a special character. If this is your problem, there's a walkaround (thanks '''nachbarnebenan'''): after aMule has hashed all shared files (that is, when it stops taking a lot of your CPU's resources), close aMule and enconde ~/.aMule/known.met into UTF-8 encoding (you can do this with the application ''[http://www.gnu.org/directory/recode.html recode]'' by running the following command: ''recode u8 ~/.aMule/known.met''). This should be done whenever a files is added or modified in any Shared Directory. So, best option is to upgrade to latest aMule version. 
If non of the above helps you, then something went really wrong on ''known.met'' file, probably some external program or user broke it. Best option is to delete it, start aMule and let aMule rehash all files again.

== So now aMule starts, but why is it displaying this message: "No valid servers to connect in serverlist found"? ==
That's because you enabled the option "Auto connect to servers the static list only". So, disable it or add some server to the static list. 
To disable that option, go to Preferences -> Servers -> "Auto connect to servers the static list only" 
To add a server to the static list, go to the Servers window and right-click on the server you want to add to the static list. Then select "Add to static" and do this exact process wit all the servers you want to add to the static list.

== aMule connects to server, but it is always given Low-ID. Why? and, can I do something about it? ==
This can bue due to three reasons:
<ul><li>Some necessary port is not opened in your firewall. Read [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|this]] to get to know what to do and check [http://www.amule.org/testport.php here] if the ports are open.</li>
<li>The server is very busy or maybe badly configured, so it's giving you a [[Low-ID]]. There's nothing that can be done in this case other than reconnect or connect to some other server.</li>
<li>Some ISP forbid the use of p2p applications, such as aMule, by not allowing traffic through popular p2p ports. In these cases, configure aMule to use some other port. It would be even better if it was some popular port used for some other issue. It's been known that on some ISPs it worked with port TCP 25600.</li></ul>

== [[aMule]] was interrupted while completing a file and it is now never completing it (allthough it's 100% downloaded). How can I complete it? ==
This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

Finally, run [[aMule]] and let it complete the files.

== I just lost a download. Is there anyway I can recover it? ==
This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault). 
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted. 
If *.part files have dissapeared, the only solution is to reastart the downloads from the beggining (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them. 
If *.part.met files have dissapeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running: 
''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done'' 
Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this: 
Either, use [http://www.bigwillystyle42.com/index.php?dest=mfr MetFileRegenerator] (Java needed) to reconstruct the *.part.met files. 
Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you ware down loading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have misteriously dissapeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddendly become unresponsive to the mouse although it's not hanged? ==
It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive untill you click OK, Cancel, or whatever you have to click. 
So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==
This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time). 
However, on some releases it has happened that after restarting aMule, some files dissapear from the Shared Folders window alllthough they are in the shared folders. In such cases, the only way to have them back is to delete ''~/.aMule/known.met'' but, of course, on next aMule start, all shared files will have to be rehashed, and that'll take some time most probably.

== I always get a message about addresses.met when I start aMule. What's wrong? ==
This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it. 

== I sometimes get a message on the log about credits being lost. Should I be worried? ==
No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you souldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==
Losing that file will automatically make you loose all your credits with it, sorry. IF you will to start collecting credits again from this very moment, delete ''~/.aMule/preferences.dat'' too. If you don't, you'll be unable to collect credits on those [[client]]s which had sometime (before loosing the ''cryptkey.dat file) identified you.

== Why is Upload/Download limit always back to 0 after every restart? ==
This happened on aMule versions previous to 2.0.0-rc4 when you trying to set a Upload or Download limit value higher than the Upload or Download Capacity value. However, since version 2.0.0-rc4 this is fixed (read [[FAQ_aMule#What_is_the_real_point_on_setting_up_Line_Capacities_in_Preferences?_Shouldn't_aMule_only_care_for_the_Bandwidth_Limits?|What is the real point on setting up Line Capacities
in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] to understand why) and shouldn't happen anymore.

== Why is aMule ignoring the bandwith I set per slot? ==
The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time. 
So, the maximum speed allowed per slot is '''BandwidthLimit/3'''. 
Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwith Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive. 
Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth. 

Example: 
Bandwidth Limit: 7 KBps
Slot allocation: 2 KBps
When [[aMule]] sets the slots to some clients to upload to them, after giving out three slots, it will notice that tehre are no more 2KBps left, since the limit is 7 KBps, but there is still 1 KBps left in the bandwicth before reaching the Bandwidth Limit. So, It will allow another slot to upload to a client and, isntead of giving that last slot a 1 KBps bandwidth connection (and leave the rest with a 2 KBps bandwidth connetcion), it will give all four slots a 1.8 KBps bandwidth connection.

== Why can't I set aMule's download limit to more than X? ==
To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:

From 0KBps to 3KBps: 
DownloadLimit can't be more than UploadLimit*3 
From 4KBps to 9KBps: 
DownloadLimit can't be more than UploadLimit*4 
UploadLimit values over 9KBps: 
There's no DownloadLimit limitation.

Be carefull when setting 0KBps as Upload Limit . It might not mean what you think it is. Read [[AMule_problems#I_set_Upload_Limit_to_0KBps,_but_aMule_is_still_transfering._What_did_I_do_wrong?|I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong?]] to make sure you understand it's meaning.

== I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong? ==
Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opossite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end. 
Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==
This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established). 
On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editting the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist): 
''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==
In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

== All my downloads suddenly paused and I can't resume them. What's going on? ==

Check if there's any free space in the filesystem where the Temp directory is placed. If there is any at all, check if there's more free space than the minimum free space set at Preferences -> Files -> "Min disk space".

The minimum free space required for [[aMule]] is 9.28MB, since that's what [[aMule]] needs to be able to download a [[FAQ_ed2k#What_is_a_chunk?|part]] of a file.

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==
Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.: 
''xterm -T "aMule preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==
Preview used to lock aMule on purpose until aMule reached version 2.0.0-rc4. As a result of this, people using MPlayer suffered from a bug on MPlayer which remains the main process in background when closing the main MPlayer window. The way to walk around this MPlayer bug on aMule versions previous to 2.0.0-rc4 is to exit MPlayer by pressing the '''Q''' key. Any way, it'd be better if you could possibly upgrade aMule to the latest versions.

== Why is ''Transfered'' a smaller number than ''Completed''? ==
It's a common mistake to think it should be bigger or, at least, equal. 
Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==
Yes it is. When aMule completes a download it checks it has not been corrupted. Allthough this is already checked while downloading (by checking the chunk's hash values), once the file is completly downloaded aMule hashes all the chunks to check that the chunks which were previously downloaded weren't somehow corrupted by the user or an external application while the rest of the file was being downloaded.

== Is there any way to recursively select a whole directory and its contents? ==
Yes, there is. And it's simple:
*On [[aMule]] 2.0.0-rc4 or later, right-click on the icon of the directory you want to recusively select.
*On [[aMule]] 1.x and up to 2.0.0-rc3 (included), while clicking on the directory, hold the CTRL key. 
And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==
If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]]. 
[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

== Things you should be aware when using NFS mounts with [[aMule]] ==
When using NFS mounts with [[aMule]], make sure you unmount those NFS mounts(the ones from the computer being shut down) from the computer running [[aMule]], because, otherwise, [[aMule]] will simply hang untill those mounts are back up again. How to notice this? If you leave [[aMule]] running at night, and on the other day you go to the stats and see straight lines for Download/Upload/Connections stats(NON ZERO), and after mounting those NFS mounts, those straight lines drop to zero resuming normal behaviour, that is a sign. Plus, after unmouting the NFS mounts from any computer beying shut down, '''reload''' [[aMule]]'s shared files. ''I noticed all this from my frustrating experience of countless days with no downloads at nigh ;) ... --[[User:PedroAlgarvio|PedroAlgarvio]] 00:25, 15 Jun 2005 (CEST)''

How to launch VNC with aMule at Linux boot

2005-06-12T16:23:23Z

PedroAlgarvio: =Server Config=

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

'''ATENTION: THE BOOT PROCESS NOW WORKS'''

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and of course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

# emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

# vncserver :0

I'm using '' ''':0''' ''because there isn't no window manager running, so no need to use'' ''':1''' '', plus, it will be simpler to connect to it like this, simply
# vncviewer <host>

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

# vncserver -kill :0

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

# vi ~/.vnc/xstartup

You should see something like:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
exec wmaker
</pre>

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I now use [http://www.windowmaker.org/ WindowMaker], and don't want no terminal, just [[aMule]] so, it's like this:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
amule &
exec wmaker
</pre>

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

# vi /etc/init.d/vncserver

Make it look like:
<pre>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Load config"
PATH="$PATH:/usr/X11R6/bin/"

# The Username:Group that will run VNC
export USER="vampas"
#${RUNAS}

# The display that VNC will use
DISPLAY="0"

# Color depth (between 8 and 32)
DEPTH="16"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="800x600"
GEOMETRY="1024x780"
#GEOMETRY="1280x1024"

# The name that the VNC Desktop will have.
NAME="aMule"

OPTIONS="-name ${NAME} -depth ${DEPTH} -geometry ${GEOMETRY} :${DISPLAY}"
eend $? "Config not Loaded"
}

start() {
checkconfig
ebegin "Starting vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver ${OPTIONS}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
svc_start
}
</pre>

Make it executable:

# chmod +x /etc/init.d/vncserver

Now add it to boot:

# rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

----

How to launch VNC with aMule at Linux boot

2005-06-12T16:22:59Z

PedroAlgarvio: =Install [http://www.realvnc.com VNC]=

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

'''ATENTION: THE BOOT PROCESS NOW WORKS'''

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and of course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

# emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :0
I'm using '' ''':0''' ''because there isn't no window manager running, so no need to use'' ''':1''' '', plus, it will be simpler to connect to it like this, simply
# vncviewer <host>

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

# vncserver -kill :0

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

# vi ~/.vnc/xstartup

You should see something like:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
exec wmaker
</pre>

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I now use [http://www.windowmaker.org/ WindowMaker], and don't want no terminal, just [[aMule]] so, it's like this:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
amule &
exec wmaker
</pre>

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

# vi /etc/init.d/vncserver

Make it look like:
<pre>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Load config"
PATH="$PATH:/usr/X11R6/bin/"

# The Username:Group that will run VNC
export USER="vampas"
#${RUNAS}

# The display that VNC will use
DISPLAY="0"

# Color depth (between 8 and 32)
DEPTH="16"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="800x600"
GEOMETRY="1024x780"
#GEOMETRY="1280x1024"

# The name that the VNC Desktop will have.
NAME="aMule"

OPTIONS="-name ${NAME} -depth ${DEPTH} -geometry ${GEOMETRY} :${DISPLAY}"
eend $? "Config not Loaded"
}

start() {
checkconfig
ebegin "Starting vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver ${OPTIONS}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
svc_start
}
</pre>

Make it executable:

# chmod +x /etc/init.d/vncserver

Now add it to boot:

# rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

----

How to launch VNC with aMule at Linux boot

2005-06-12T16:22:33Z

PedroAlgarvio:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

'''ATENTION: THE BOOT PROCESS NOW WORKS'''

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and of course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :0
I'm using '' ''':0''' ''because there isn't no window manager running, so no need to use'' ''':1''' '', plus, it will be simpler to connect to it like this, simply
# vncviewer <host>

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

# vncserver -kill :0

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

# vi ~/.vnc/xstartup

You should see something like:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
exec wmaker
</pre>

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I now use [http://www.windowmaker.org/ WindowMaker], and don't want no terminal, just [[aMule]] so, it's like this:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
amule &
exec wmaker
</pre>

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

# vi /etc/init.d/vncserver

Make it look like:
<pre>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Load config"
PATH="$PATH:/usr/X11R6/bin/"

# The Username:Group that will run VNC
export USER="vampas"
#${RUNAS}

# The display that VNC will use
DISPLAY="0"

# Color depth (between 8 and 32)
DEPTH="16"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="800x600"
GEOMETRY="1024x780"
#GEOMETRY="1280x1024"

# The name that the VNC Desktop will have.
NAME="aMule"

OPTIONS="-name ${NAME} -depth ${DEPTH} -geometry ${GEOMETRY} :${DISPLAY}"
eend $? "Config not Loaded"
}

start() {
checkconfig
ebegin "Starting vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver ${OPTIONS}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
svc_start
}
</pre>

Make it executable:

# chmod +x /etc/init.d/vncserver

Now add it to boot:

# rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

----

How to launch VNC with aMule at Linux boot

2005-06-12T16:21:50Z

PedroAlgarvio: =Programs to Start=

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

'''ATENTION: THE BOOT PROCESS NOW WORKS'''

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and of course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :0
I'm using '' ''':0''' ''because there isn't no window manager running, so no need to use'' ''':1''' '', plus, it will be simpler to connect to it like this, simply
# vncviewer <host>

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

# vncserver -kill :0

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

# vi ~/.vnc/xstartup

You should see something like:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
exec wmaker
</pre>

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I now use [http://www.windowmaker.org/ WindowMaker], and don't want no terminal, just [[aMule]] so, it's like this:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
amule &
exec wmaker
</pre>

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:
<pre>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Load config"
PATH="$PATH:/usr/X11R6/bin/"

# The Username:Group that will run VNC
export USER="vampas"
#${RUNAS}

# The display that VNC will use
DISPLAY="0"

# Color depth (between 8 and 32)
DEPTH="16"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="800x600"
GEOMETRY="1024x780"
#GEOMETRY="1280x1024"

# The name that the VNC Desktop will have.
NAME="aMule"

OPTIONS="-name ${NAME} -depth ${DEPTH} -geometry ${GEOMETRY} :${DISPLAY}"
eend $? "Config not Loaded"
}

start() {
checkconfig
ebegin "Starting vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver ${OPTIONS}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
svc_start
}
</pre>

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

----

How to launch VNC with aMule at Linux boot

2005-06-12T16:21:04Z

PedroAlgarvio:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

'''ATENTION: THE BOOT PROCESS NOW WORKS'''

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and of course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :0
I'm using '' ''':0''' ''because there isn't no window manager running, so no need to use'' ''':1''' '', plus, it will be simpler to connect to it like this, simply
# vncviewer <host>

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

# vncserver -kill :0

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

vi ~/.vnc/xstartup

You should see something like:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
exec wmaker
</pre>

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I now use [http://www.windowmaker.org/ WindowMaker], and don't want no terminal, just [[aMule]] so, it's like this:

<pre>
#!/bin/sh
PATH="$PATH:/usr/bin"
xrdb $HOME/.Xresources
xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
amule &
exec wmaker
</pre>

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:
<pre>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Load config"
PATH="$PATH:/usr/X11R6/bin/"

# The Username:Group that will run VNC
export USER="vampas"
#${RUNAS}

# The display that VNC will use
DISPLAY="0"

# Color depth (between 8 and 32)
DEPTH="16"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="800x600"
GEOMETRY="1024x780"
#GEOMETRY="1280x1024"

# The name that the VNC Desktop will have.
NAME="aMule"

OPTIONS="-name ${NAME} -depth ${DEPTH} -geometry ${GEOMETRY} :${DISPLAY}"
eend $? "Config not Loaded"
}

start() {
checkconfig
ebegin "Starting vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver ${OPTIONS}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user '${USER}' on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
svc_start
}
</pre>

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

----

How to launch VNC with aMule at Linux boot

2005-05-02T19:39:08Z

PedroAlgarvio:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

<h1> ATENTION: THE BOOT PROCESS DOENS'T WORK, I'LL TRY TO FIX IT AS SOON AS POSSIBLE </h1>
Why, while my HD Died a couple of days, I had to re-instal gentoo and I'm having some problems with X and fluxbox, as soon as this is fixed, I'll be needing this to works, so change WILL be made to correct what's wrong. Sorry, --[[User:PedroAlgarvio|PedroAlgarvio]] 21:37, 2 May 2005 (CEST)

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and o course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :1

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

vncserver -kill :1

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

vi ~/.vnc/xstartup

You should see something like:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I use [http://fluxbox.sourceforge.net fluxbox], and don't want no terminal, just [[aMule]] so, it's like this:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
amule &
fluxbox &

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:

#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Check config"
#PATH="$PATH:/usr/X11R6/bin/"

# The Username that will run VNC
USER="vampas"

# The display that VNC will use
DISPLAY="1"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="1280x1024"
GEOMETRY="1024x780"

# The name that the VNC Desktop will have.
NAME="aMule"
}

start() {
checkconfig
ebegin "Starting vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -name ${NAME} -geometry ${GEOMETRY} :${DISPLAY}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
svc_stop
svc_start
}

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

--[[User:PedroAlgarvio|PedroAlgarvio]] 06:10, 2 May 2005 (CEST)

How to launch VNC with aMule at Linux boot

2005-05-02T19:37:46Z

PedroAlgarvio: =[http://www.gentoo.org Gentoo]=

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

<h1> ATENTION: THE BOOT PROCESS DOENS'T WORK, I'LL TRY TO FIX IT AS SOON AS POSSIBLE </h1>
Why, while my HD Died a couple of days, I had to re-instal gentoo and I'm having some problems with X and fluxbox, as soon as this is fixed, I'll be needing this to works, so change WILL be made to correct what's wrong. Sorry, --[[User:PedroAlgarvio|PedroAlgarvio]] 21:37, 2 May 2005 (CEST)

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and o course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :1

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

vncserver -kill :1

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

vi ~/.vnc/xstartup

You should see something like:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I use [http://fluxbox.sourceforge.net fluxbox], and don't want no terminal, just [[aMule]] so, it's like this:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
amule &
fluxbox &

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:

#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Check config"
#PATH="$PATH:/usr/X11R6/bin/"

# The Username that will run VNC
USER="vampas"

# The display that VNC will use
DISPLAY="1"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="1280x1024"
GEOMETRY="1024x780"

# The name that the VNC Desktop will have.
NAME="aMule"
}

start() {
checkconfig
ebegin "Starting vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -name ${NAME} -geometry ${GEOMETRY} :${DISPLAY}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
stop
start
}

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

--[[User:PedroAlgarvio|PedroAlgarvio]] 06:10, 2 May 2005 (CEST)

How to launch VNC with aMule at Linux boot

2005-05-02T19:33:44Z

PedroAlgarvio: =Programs to Start=

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

== [http://www.gentoo.org Gentoo] ==

For [http://www.gentoo.org Gentoo]'ers follow these steps:

=== Install [http://www.realvnc.com VNC] ===

This is a how to for a server with no X window manager at all. I only run web and mail services, and o course, aMule. Adapt to you're sictuation.
I use [http://www.tightvnc.com TightVNC], but should also work with other [http://www.realvnc.com VNC]'s.

emerge tightvnc

=== Configuring [http://www.realvnc.com VNC] ===

==== Server Config ====

To configure the [http://www.realvnc.com VNC] server, execute:

vncserver :1

You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:

vncserver -kill :1

==== Programs to Start ====

Now let's config what should be started with this [http://www.realvnc.com VNC] session:
edit ~/.vnc/xstartup

vi ~/.vnc/xstartup

You should see something like:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

[http://www.x.org xterm] is a console, and [http://www.x.org twm] is the window manager. I use [http://fluxbox.sourceforge.net fluxbox], and don't want no terminal, just [[aMule]] so, it's like this:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
amule &
fluxbox &

=== Starting [http://www.realvnc.com VNC] at boot ===

Since I won't be starting no Window Manager at boot, but still want [[aMule]] started with the user interface(you could just run [[aMuled]]), I'll need an init script:

vi /etc/init.d/vncserver

Make it look like:

#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Check config"
#PATH="$PATH:/usr/X11R6/bin/"

# The Username that will run VNC
USER="vampas"

# The display that VNC will use
DISPLAY="1"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="1280x1024"
GEOMETRY="1024x780"

# The name that the VNC Desktop will have.
NAME="aMule"
}

start() {
checkconfig
ebegin "Starting vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -name ${NAME} -geometry ${GEOMETRY} :${DISPLAY}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
stop
start
}

Make it executable:

chmod +x /etc/init.d/vncserver

Now add it to boot:

rc-update add vncserver default

And you should be ready to go, if not ''<ufs AT sapo DOT pt>''

--[[User:PedroAlgarvio|PedroAlgarvio]] 06:10, 2 May 2005 (CEST)

How to launch VNC with aMule at Linux boot

2005-05-02T04:10:10Z

PedroAlgarvio:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com 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/husband 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/rc.d/rc.vnc { start | stop }"'' 
'';;''

''esac''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

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 [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer 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 [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net 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 [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== To start [[aMuleWeb]] also at startup: ==

This is probably the most unelegant way to do this, but it seems to work.

The problem is that you have to supply user input when starting [[aMuleWeb]] (the password).

You can circumvent this with supplying a password with the ''-pw'' option: ''amuleweb -pw ""'' (this is for no password, you have to remove the [http://www.ietf.org/rfc/rfc1321.txt MD5 sum] from the ''ECPassword'' entry in your ''~/.eMule'' file for this to work).

Now [[aMuleWeb]] starts without any user input, but unfortunately it wouldn't work when we would just add it to the xstartup-file, because [[aMule]] needs a few seconds more to start up.

Therefor we have to start [[aMuleWeb]] a few seconds after [[aMule]].

To achieve this, we add a line similar to this one:

''/bin/sh /home/aMule/amuleweb-start.sh &''

to the xstartup-file.

And in the home-directory, we create a file called ''amuleweb-start.sh'', with the following content:

#! /bin/sh
sleep 30;
/usr/bin/amuleweb -pw "";

That's all.

Like I said, probably extremely amateurish, but it should work...

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html 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 ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh'' 
''starticewm&'' 
''amule''

To start [http://www.redstonesoftware.com/vnc.html 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 [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>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 [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

==[http://www.gentoo.org Gentoo]==
For Gentoo'ers follow these steps:
=== Install VNC ===
This is a how to for a server with no X window manager at all. I only run web and mail services, and o course, aMule. Adapt to you're sictuation.
I use TightVNC, but should also work with other VNC's.
----
<pre>
emerge tightvnc
</pre>
----

=== Configuring VNC ===
==== Server Config ====
To configure the vnc server, execute:
----
<pre>
vncserver :1
</pre>
----
 You'll be asked to answer some questions, such as password, answer accordingly. After you can kill it:
----
<pre>
vncserver -kill :1
</pre>
----
 
==== Programs to Start ====
Now let's config what should be started with this VNC session:
edit ~/.vnc/xstartup
----
<pre>
vi ~/.vnc/xstartup
</pre>
----
 You should see something like:
----
<pre>
#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &
</pre>
----
 xterm is a console, and twm is the window manager. I use fluxbox, and don't want no terminal, just amule so, it's like this:
----
<pre>
#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
amule &
fluxbox &
</pre>
----
===Starting VNC at boot===
Since I won't be starting no Window Manager at boot, but still want aMule started with the user interface(you could just run the *amuled*), I'll need an init script:
----
<pre>
vi /etc/init.d/vncserver
</pre>
----
 Make it look like:
----
<pre>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

depend() {
need net
}

checkconfig() {
ebegin "Check config"
#PATH="$PATH:/usr/X11R6/bin/"

# The Username that will run VNC
USER="vampas"

# The display that VNC will use
DISPLAY="1"

# The Desktop geometry to use.
#GEOMETRY="<WIDTH>x<HEIGHT>"
#GEOMETRY="1280x1024"
GEOMETRY="1024x780"

# The name that the VNC Desktop will have.
NAME="aMule"
}

start() {
checkconfig
ebegin "Starting vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -name ${NAME} -geometry ${GEOMETRY} :${DISPLAY}"
eend $?
}

stop() {
checkconfig
ebegin "Stoping vncserver for user ${USER} on localhost:${DISPLAY}"
su ${USER} -c "/usr/bin/vncserver -kill :${DISPLAY}"
eend $?
}

restart() {
stop
start
}
</pre>
----
 
Make it executable:
----
<pre>
chmod +x /etc/init.d/vncserver
</pre>
----
 
Now add it to boot:
----
<pre>
rc-update add vncserver default
</pre>
-----
 And you should be ready to go, if not <ufs AT sapo DOT pt>. --[[User:PedroAlgarvio|PedroAlgarvio]] 06:10, 2 May 2005 (CEST)
----