| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001569 | aMule | Utilities | public | 2009-12-23 14:12 | 2009-12-26 16:41 |
|
| Reporter | bill lee | |
| Assigned To | | |
| Priority | normal | Severity | major | Reproducibility | random |
| Status | closed | Resolution | not fixable | |
| Platform | | OS | | OS Version | |
| Product Version | 2.2.6 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001569: The method of dectecting amule process running already has a bug |
| Description | When an amule process has been running, there is a file, mulelock, which records the pid of the running process. If user run a second process, amule will read mulelock. If the process which has been recorded in mulelock exists, amule will shutdown.
However, here comes a bug. After amule crashes, the pid may be assigned to another process, when I try to run amule again, it believe that an amule process has already running and shutdown. |
| Additional Information | This is the way to solve this problem.
When finding the process recorded in mulelock exists, amule should read /proc/<pid>/cmdline. If there is a word, amule, in it, shutdown. If none, amule should be run. |
| Tags | No tags attached. |
|
| Fixed in Revision | |
| Operating System | Linux |
|
| Attached Files | |
|
Relationships 
Relationships 