Lock file

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
m
(somewhat less naïve description)
 
Line 4: Line 4:
 
|extensions={{ext|lck}}, {{ext|lock}}
 
|extensions={{ext|lck}}, {{ext|lock}}
 
}}
 
}}
 +
'''Lock files''' are used to prevent simultaneous access to a specific file, device, or to prevent an application from being started twice.  Lock files are found in Unix-like systems under the directory <code>/var/lock</code> (or more recently, <code>/run/lock</code>).
  
=Introduction=
+
A lock file may be empty, but it usually contains the process ID of the program holding the lock.
A lock file is used by an application to indicate there is something going on. For example, to prevent an application to be started twice.  Not to be confused with a [[File lock]], although a lock file often has a file lock.
+
  
Often a lock file is empty (0 bytes), but it can contain data such as the [[PID (Process ID)]].
+
Not to be confused with a [[File lock]], although a lock file often has a file lock.
 +
 
 +
== External links ==
 +
* [[wikipedia:Lock file|Lock files at Wikipedia]]

Latest revision as of 10:05, 1 June 2015

File Format
Name Lock file
Ontology
Extension(s) .lck, .lock

Lock files are used to prevent simultaneous access to a specific file, device, or to prevent an application from being started twice. Lock files are found in Unix-like systems under the directory /var/lock (or more recently, /run/lock).

A lock file may be empty, but it usually contains the process ID of the program holding the lock.

Not to be confused with a File lock, although a lock file often has a file lock.

[edit] External links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox