Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[macolo]

Hi there,

I have a remote debian lenny system running on a Virtual Server. The only way to access it is by SSH. That's why I don't have access to amule's GUI and use the webserver with amuled configuration instead.

My question is:

I would like to change my amule root directory from /root/.aMule to /srv/amule

That's what I changed in order to make it work:

/etc/init.d/amule:

Code: [Select]

case "$1" in
  start)
    echo -n "Starting $DESC: "
       su $USER -c "$DAEMON --config-dir=/srv/amule/"
       while ! netstat -l -n -p -t | grep -q amuled ; do sleep 1 ; done
       su $USER -c "$WEB --quiet --config-file=/srv/amule/amule.conf &"
    echo "$NAME."
    ;;
Explanation: /usr/bin/amuled is called by the init.d script with the parameter --config-dir=/srv/amule/. That should be sufficient to show the executable the location of the additional amule-files.
The same goes with /usr/bin/amuleweb but the parameters are slightly different (I looked them up by typing amuleweb --help resp. amuled --help on the command line.): --quiet --config-file=/srv/amule/amule.conf

Additionally, I made the following changes to the amule.conf in the new root folder /srv/amule/:

Code: [Select]

TempDir=/srv/amule/temp
IncomingDir=/srv/amule/incoming
OSDirectory=/srv/amule/
With the new settings, amuled throws the following message at me:

Code: [Select]

aldebaran:/srv/jail/glftpd/site# /etc/init.d/amule start
Starting amuled: amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
There is an instance of aMule already running
Raising current running instance.
aldebaran:/srv/jail/glftpd/site#

a ps -ef | grep amule right afterwards shows nothing at all.

How do I get amule to run in a different location?

Thank you very much for your help!

All the best

Mario

[macolo]

I resolved that on my own:

My errors:

1) /usr/bin/amuleweb --config-file= takes as parameter path/to/remote.conf and not path/to/amule.conf

2) in the amule root directory there's a couple of lock files named amule + a couple of random characters. If amule is not able to delete them because it gets shut down improperly the above message will be thrown at you (There is an instance of aMule already running). This message didn't have anything to do with my real problem.

That's in fact how I worked it out.

Cheers

macolo