Difference between revisions of "MuleLock file"

From AMule Project FAQ
Jump to: navigation, search
 
m (Notes: Typo: exists --> exits)
Line 21: Line 21:
 
== Notes ==
 
== Notes ==
  
This file is created when starting aMule and it writes its PID number in it. When aMule exists, it deletes the file.
+
This file is created when starting aMule and it writes its PID number in it. When aMule exits, it deletes the file.
  
 
When aMule starts, it checks if the ''muleLock'' fiel exists. If it does, it reads it and checks if the number it contains is the PID of a running process. If it is, then it closes itself to prevent two aMule intances running simoultaneously.
 
When aMule starts, it checks if the ''muleLock'' fiel exists. If it does, it reads it and checks if the number it contains is the PID of a running process. If it is, then it closes itself to prevent two aMule intances running simoultaneously.
  
 
Notice that aMule will not check that the process corresponds to a real aMule process. Any processes running with the PID contained in the ''muleLock'' file will prevent aMule from starting.
 
Notice that aMule will not check that the process corresponds to a real aMule process. Any processes running with the PID contained in the ''muleLock'' file will prevent aMule from starting.

Revision as of 18:04, 11 January 2011

File

Name: muleLock

Location: ~/.aMule/

Description

This file is generated by aMule to prevent two aMule instances being run by the same user. See the Notes section for more information.

Format

This file simply contains the PID of the user's running aMule instance.

Example

The following is the contents of a valid muleLock file:

3865

Notes

This file is created when starting aMule and it writes its PID number in it. When aMule exits, it deletes the file.

When aMule starts, it checks if the muleLock fiel exists. If it does, it reads it and checks if the number it contains is the PID of a running process. If it is, then it closes itself to prevent two aMule intances running simoultaneously.

Notice that aMule will not check that the process corresponds to a real aMule process. Any processes running with the PID contained in the muleLock file will prevent aMule from starting.