Print

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

[hopelessone]

Hi,,

must be blind but i can't see a way to stop amuled?

where is the command?

thanks

[wuischke]

Use the Shutdown command of amulecmd.

[Kry]

kill it.

no, seriously, we have a SIGHUP.

[hopelessone]

firebox@firebox-desktop:~$ killall amuled
amuled: no process killed
firebox@firebox-desktop:~$ 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.
firebox@firebox-desktop:~$ killall amule
amule: no process killed
firebox@firebox-desktop:~$ killall amulecmd
amulecmd: no process killed
firebox@firebox-desktop:~$ 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.
firebox@firebox-desktop:~$


currently i have to reboot to start it again ??

[skolnick]

You can find the PID by doing:

Code: [Select]

ps -A | grep amule
and then to stop it use:

Code: [Select]

kill -9 $PID_of_amuled
and you will be happy.

Regards.

[Kry]

-9 is a SIGKILL. Use a SIGHUP, which is the default.

[hopelessone]

Tan-Q very much !!!!

[GonoszTopi]

-9 is a SIGKILL. Use a SIGHUP, which is the default.

JFYI, SIGTERM is the default.

[Kry]

Woops. I meant SIGTERM

[RRT4]

i have a problem, currently 5-6 times of 10 when i reboot the system running amuled known.met (or known2_64.met) result corrupted (something in amule log as 'missing headers etc', i do not remember well the error reported because it does not appear always in the log), so the system needs to rehash all files (more than 500 files on a 500Mhz downclocked athlon, it took 5/6 hours)

could the problem be based on the fact that sometimes amuled is not responding to signal SIGTERM (also other conf files are not saved but they do not result corrupted) ?

archlinux rc.shutdown script send in order these commands:

-/etc/rc.local.shutdown (local shutdown scripts)
-shutdown daemons (amuled start|stop|restart script) -> killall -15 --ignore-case $DAEMON
-terminate all processes -> /sbin/killall5 -15 &> /dev/null
-sending SIGKILL To Processes -> /sbin/killall5 -9 &> /dev/null




 

[GonoszTopi]

Or it could be that it takes too long for amuled to shut down, and is killed before the shutdown finishes.

[RRT4]

i tried putting
su amuled_user -c 'amulecmd -c shutdown' in /etc/rc.local/shutdown
but the problem persists

2008-04-07 01:31:16: KnownFileList.cpp(86): Warning: Knownfile list corrupted, contains invalid header.
...
2008-04-07 01:31:58: SharedFileList.cpp(358): Found 0 known shared file, 490 unknown

at this point really could be that amuled takes too long to shutdown properly (the cpu is slow and the known.met is not saved in time)

[GonoszTopi]

You may introduce some extra waiting time between the '/sbin/killall5 -15' and the '/sbin/killall5 -9' commands, such as 'sleep 10'.

The clean way would be to create a start/stop script, and let it wait for amuled shutdown on stop command.

[RRT4]

Not yet certain to 100% (still too few reboots), but the problem appears to be solved with 'sleep 15' (probably it works with 'sleep 10' too, i need to test, original was 'sleep 5')

tnx