| Top | |
|
|
|
Locking the user/group database is required when modifications are needed to the database e.g. adding and deleting users. Lock can be called multiple times as it merely increases the lock counter after acquiring the lock for the first time. Similarly unlock can be called multiple times as it decreases lock counter until it the count reaches to 0 when the lock is released. Locking and unlocking the database is disabled for when testing is enabled as tests are run on dummy databases.
//return value must be checked if the lock succeed or not. gboolean ret = gum_lock_pwdf_lock (); //return value must be checked if the unlock succeed or not. ret = gum_lock_pwdf_unlock ();
gboolean
gum_lock_pwdf_lock (void);
Gets the lock to the user/group database file(s). Lock can be called multiple times as it merely increases the lock counter after acquiring the lock for the first time. In order to release the lock, unlock needs to be called the same number of times as that of lock. Locking and unlocking the database is disabled for when testing is enabled as tests are run on dummy databases.
gboolean
gum_lock_pwdf_unlock (void);
Releases the lock to the user/group database file(s). Unlock can be called multiple times as it decreases lock counter until it the count reaches to 0 when the lock is released. In order to release the lock, unlock needs to be called the same number of times as that of lock. Locking and unlocking the database is disabled for when testing is enabled as tests are run on dummy databases.