Do not warn about lock-file option change when -X is used

When -X is used the 'lock-file' option change detection condition
is invalid, because it compares the 'lock-file' option's value to
the '-X' argument's value instead of the older 'lock-file' option
value (which was ignored because of '-X').

Don't warn about changing 'lock-file' option if '-X' is used.

(cherry picked from commit 41945b32d7)
This commit is contained in:
Aram Sargsyan 2023-10-26 12:28:25 +00:00
parent 4ed32424c8
commit 08de15e5f2

View file

@ -8408,7 +8408,7 @@ check_lockfile(named_server_t *server, const cfg_obj_t *config,
if (!first_time) {
if (obj != NULL && cfg_obj_isstring(obj) &&
server->lockfile != NULL &&
server->lockfile != NULL && !named_g_forcelock &&
strcmp(cfg_obj_asstring(obj), server->lockfile) != 0)
{
isc_log_write(named_g_lctx, NAMED_LOGCATEGORY_GENERAL,