Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#20917 - [amule] after reboot of system amule doesn't start

Attached to Project: Arch Linux
Opened by ivan (thecrow) - Wednesday, 22 September 2010, 17:01 GMT
Last edited by Giovanni Scafora (giovanni) - Thursday, 30 September 2010, 09:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Giovanni Scafora (giovanni)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

* amule 2.2.6

Steps to reproduce:
1. launch amule
2. reboot the system without closing amule
3. After a reboot try to open amule
not always happen but sometimes you can not start amule and from the shell you will receive the following message:
Initialising aMule 2.2.6 using wxGTK2 v2.8.10
Checking if there is an instance already running ...
There is an instance of aMule already running
(Lock file: / home / king / .aMule / muleLock) Raising current running instance.
4. removing the file / home / king / .aMule / muleLock amule back to work.

IMPORTANT: I reported the problem to amule bugtracker and they told me this:

"aMule is not shut down properly on reboot. aMule can take quite a while to
shut down, to flush all files, close connections etc. This appears not to
be handled properly by the shutdown script.

This is an issue of the shutdown/start up scripts which are not part of
aMule."

Thanks.
This task depends upon

Closed by  Giovanni Scafora (giovanni)
Thursday, 30 September 2010, 09:21 GMT
Reason for closing:  Works for me
Comment by Jan de Groot (JGC) - Wednesday, 22 September 2010, 21:23 GMT
AFAIK you're not using any startup/shutdown scripts for aMule. You just start aMule, and when you don't close it properly, the lock file isn't removed and aMule refuses to start. IMHO aMule should be able to recover from incorrect shutdowns itself. Even MySQL comes back online without manual adjustments when you plug the power cord or kill -9 the process.

Loading...