The –with-db-lock parameter specifies if the DB-Config-Lock mode will be used. If set to 'true', then the server will use the DB-API DB-Config-Lock service for all configuration edit transactions to the <running> datastore. All client edits will be require this lock be granted or it will fail.


The server will use the db-lock-retry-interval and db-lock-timeout CLI parameters to control how lock retries will be done.


If set to 'false', the DB-Config-Lock will not be used by the server. The default is false.


The --with-db-lock parameter can be set via the command line when booting netconfd-pro:


user@system> netconfd-pro --with-db-lock=true


or configured in netconfd-pro's configuration file, usually /etc/yumapro/netconfd-pro.conf:


#
#### leaf with-db-lock
#
# If set to 'true', then the server will use the
# DB-API DB-Config-Lock service for all configuration
# edit transactions to the <running> datastore.
# All client edits will be require this lock be
# granted or it will fail.
# If set to 'false', the DB-Config-Lock will not be
# used by the server.
#
# with-db-lock false
#
with-db-lock true