10. Multi-Admins Features

In an environment where several admins may have to edit rulesets, isba provides features to avoid simultaneous editing of the same ruleset.


Ruleset locking
Ruleset modification checking

Ruleset locking

When you open a ruleset, isba checks if a lock is present on it, and warns you if this is so. Then you can choose either to break the lock or to open the ruleset read-only.

If there is no lock on the ruleset you open, isba creates one. A lock is simply a file named .ruleset-name.lock located next to the source file ruleset-name.isba. The lock contains the following informations:

  • the UID of the user that edits the ruleset
  • the host which runs the isba process
  • the date and time the ruleset was opened
  • the display isba is running on.
Lock informations

This information is provided to you when you try to open a ruleset that is locked, so you can know if the lock is real or spurious.


If the lock is real, you may want to open this ruleset in read-only mode to be sure that simultaneous modification won't occur.

Read-only mode

You can manually remove a lock by deleting the ".ruleset-name.lock" file.

Manually removing a lock
Ruleset modification checking
Before saving a ruleset, isba checks if the ruleset file has been modified (by someone else) since the time it was opened, and opens a warning popup if it has. In this case you may want to save your ruleset under a different name and check differences. Ruleset modification

Isba User's Guide - last modified on 09-Jan-2002 22:33 MET - Copyright (c) 2001