[Contents] [Prev] [Next] [Index] [Report an Error]

Locking and Unlocking the Candidate Configuration

When a client application is requesting or changing configuration information, it can use one of two methods to access the configuration:

Lock the candidate configuration, which prevents other users or applications from changing it until the application releases the lock (equivalent to the CLI configure exclusive command).
Change the candidate configuration without locking it. We do not recommend this method, because of the potential for conflicts with changes made by other applications or users that are editing the configuration at the same time.

If an application is simply requesting configuration information and not changing it, locking the configuration is not required. The application can begin requesting information immediately, as described in Requesting Configuration Information. However, it is appropriate to lock the configuration if it is important that the information being returned not change during the session.

For more information about locking and unlocking the candidate configuration, see the following sections:

[Contents] [Prev] [Next] [Index] [Report an Error]