Print the full path of the working directory in startup log messages
Description
It would be helpful to know, at startup, the full path of the directory that BIND has determined to be its working directory. I think this would be a useful data point anyway, but especially so if there is a problem with the installation and it will not start because of a fatal error such as:
Date Time Hostname named[xxxx]: the working directory is not writable
Request
(Potentially) two new startup log messages, looking something like this:
Date Time Hostname named[xxxx]: the initial working directory is <full_path e.g. /var/named/>
Date Time Hostname named[xxxx]: the working directory is now <full_path e.g. /var/named/>
The first one would be as soon as named
is running, before it's had a chance to read its configuration and discover whether a directory...
statement exist in the options {
block (if that even exists).
The second message would be printed if there is a directory...
statement.
It is possible that the paths could be the same in both cases. But better to know that than not.
Links / references
Edited by Greg Choules