Bugzilla – Bug 183
make location of pidfile configurable
Last modified: 2008-06-09 17:08:43 CEST
The Filesystem Hierarchy Standard (FHS) see: http://www.pathname.com/fhs/pub/fhs-2.3.html
has defined where to locate pidfiles:
- either /var/lock if they were used for locking
- or /var/run if they were previously stored in /etc
- but no more in /etc
As I'm working on unbound for our distribution, I've to respect this FHS when building packages.
I noticed that unbound is using "--sysconfdir" as the location of pidfile, which is equal to "/etc/" (in most distributions). Can location of pidfiles been made more configurable to honor the FHS?
Ok, it was my fault - in a way.
The "--sysconfdir" was misleading to me. It's uncommon use to specify the runtime directory via this name, let me stumble over its unusual way.
Maybe it would be less error prone, to use a different configure variable to specify its location?
Having a look at different packages, like "squid", "(x)ntp", "openssh" or just at "bind": it seems that none let specify this runtime directory via configure.
Maybe the use of "/var/lib/unbound" without configure call instead, is a common practice?
Nevertheless. However this will be solved, please fix the example configuration file in the runtime environment later; otherwise users might run into trouble.
Change in file "doc/example.conf" every occurrance of "/usr/local/etc/unbound/" to "$(ug_dir)" via configure. A rename of "doc/example.conf" to "doc/example.conf.in" might help either. :-)
Created attachment 67 [details]
patch for configure.ac
I enhanced the configure as described
Created attachment 68 [details]
patch for doc/example.conf
doc/example.conf has to be renamed too
Created attachment 69 [details]
sorry, but I forgot the quotes on first try. :-(
Fix in trunk r1114. Also you can set the run-dir and chroot-dir using configure, and it puts the correct values into the manual pages as well.
Thank you for the patches,