Remove the lock-file configuration and -X argument to named
The lock-file configuration (both from configuration file and -X argument to named) has better alternatives nowadays. Modern process supervisor should be used to ensure that a single named process is running on a given configuration. Alternatively, it's possible to wrap the named with flock(1).
This commit is contained in:
@@ -164,7 +164,6 @@ options {
|
||||
listen-on [ port <integer> ] [ tls <string> ] [ http <string> ] { <address_match_element>; ... }; // may occur multiple times
|
||||
listen-on-v6 [ port <integer> ] [ tls <string> ] [ http <string> ] { <address_match_element>; ... }; // may occur multiple times
|
||||
lmdb-mapsize <sizeval>;
|
||||
lock-file ( <quoted_string> | none ); // deprecated
|
||||
managed-keys-directory <quoted_string>;
|
||||
masterfile-format ( raw | text );
|
||||
masterfile-style ( full | relative );
|
||||
|
||||
Reference in New Issue
Block a user