The Lock was already taken by another process, we cannot lock.
This will only be returned if the LockConfig provided explicitly
disables hang_lock. In other-words, if we want to fail immediately
on the inability to lock.
This can be due to a number of issues. Using FileLock as an example,
if the temporary file disappears due to an unreliable OS File-Cleaner,
its permissions change out-from-under-us, etc.
The File Descriptor was created with permissions you do not currently have.
This may happen if the program was executed as a super-user and failed to clean up
open files. If not using the provided utility functionality, please revisit them to
see if any fit your needs. They may handle an edge-case your application hits.
An unexpected error from one of the Lock implementations.
If this happens, please file a ticket with us as we would like to
harden this library over time.