@markusjx/shared_mutex v1.1.1

Installation

npm install @markusjx/shared_mutex

Requires Node.js 12 or later

Usage

Import the module

const shared_mutex = require('@markusjx/shared_mutex');

Check if your program is already running

Check whether your program is already running. This script uses named semaphores to check whether a program is already running to make sure only one instance of a program is running at once.

You could use the destroy method on an instance of the process_mutex class to allow another instance of your program to start. You don't have to do this, the semaphores will be automatically destroyed once the instance is garbage-collected.

new process_mutex

Create a new instance of process_mutex. This will throw an exception if another instance already owns a mutex with the same name.

const lock = new shared_mutex.process_mutex("YOUR_PROGRAM_NAME");

process_mutex.destroy

Delete the lock instance to release it and allow another instance to gain ownership of the mutex.

// This will also be called when lock
// is garbage-collected
lock.destroy();

process_mutex.try_create

It is also possible to try creating a process_mutex instance using try_create(). The function will either return null if a semaphore with the same name already exists or a new instance of process_mutex if no semaphore with the same name already exists.

const try_lock = shared_mutex.process_mutex.try_create("YOUR_PROGRAM_NAME");

Shared mutexes

new shared_mutex

Create a shared mutex

const mutex = new shared_mutex.shared_mutex("A_MUTEX_NAME");

shared_mutex.lock

Lock the mutex

mutex.lock().then(() => {
  // Mutex locked
}, () => {
  // The ownership could not be acquired
});

// In an async context
await mutex.lock();

shared_mutex.lock_blocking

Blocking call (not recommended as it will freeze your node.js instance):

mutex.lock_blocking();

shared_mutex.try_lock

Try locking the mutex: try_lock() will return true, if the mutex ownership could be acquired. If so, the mutex will now be owned by your shared_mutex instance and must be unlocked using unlock(). If another instance already owns the mutex, try_lock() will return false and unlock() must not be called. Although you can call it to remove the ownership over the mutex from the other instance, which is not really recommended.

let could_lock = mutex.try_lock();

if (could_lock) {
  // We now own the mutex and should call unlock
  // when leaving the critical area 
} else {
  // We could not acquire ownership over the mutex,
  // guess we'll have to accept that...
}

shared_mutex.unlock

Unlocking the mutex so another instance can now acquire the ownership over the mutex:

mutex.unlock();

shared_mutex.destroy

Delete the mutex: destroy() will also be called when the instance is garbage-collected. destroy() will also call unlock() if this instance of shared_mutex is currently the owner of the mutex, so any other instance can acquire ownership over the mutex. NOTE: destroy() can only be called once on a single shared_mutex instance.

mutex.delete();