MuleLock file - Revision history

Reorder: /* Notes */

2012-06-20T11:02:59Z

‎Notes

Reorder: /* Notes */ Typo: exists --> exits

2011-01-11T17:04:53Z

‎Notes: Typo: exists --> exits

Jacobo221 at 22:41, 14 December 2005

2005-12-14T22:41:45Z

New page

== 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 [[muleLock_file#Notes|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 exists, 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.

← Older revision		Revision as of 11:02, 20 June 2012
Line 26:		Line 26:

	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.
		+
		+
		+	[[Category:Program Files]]

@@ Line 21: / Line 21: @@
 == 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.
 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.