You are not logged in.
Where should startup options for daemons be placed?
Should they be hardcoded in the respective startup script in /etc/rc.d?
Offline
Where should startup options for daemons be placed?
Should they be hardcoded in the respective startup script in /etc/rc.d?
It should be hardcoded as much as possible, and any user configurable options should go in /etc/conf.d/
Offline
It should be hardcoded as much as possible, and any user configurable options should go in /etc/conf.d/
So if I want to run named with -t /var/named should it go into /etc/rc.d/named or /etc/conf.d/named.
If it gos into /etc/conf.d/named, are these files in /etc/conf.d documented somewhere?
Offline
phrakture wrote:It should be hardcoded as much as possible, and any user configurable options should go in /etc/conf.d/
So if I want to run named with -t /var/named should it go into /etc/rc.d/named or /etc/conf.d/named.
If it gos into /etc/conf.d/named, are these files in /etc/conf.d documented somewhere?
No, you can change that setting in /etc/named.conf
Offline
No, you can change that setting in /etc/named.conf
But there is no chroot directive for /etc/named.conf as there is an invocation option -t for named.
Offline
phrakture wrote:No, you can change that setting in /etc/named.conf
But there is no chroot directive for /etc/named.conf as there is an invocation option -t for named.
The option is:
directory "/var/named"
it's somewhere in the man page....
Offline
The option is:
directory "/var/named"
it's somewhere in the man page....
Yes it's in /usr/man/man8/named.conf.5.gz.
To read it, type
gzip -d </usr/man/man8/named.conf.5.gz | nroff -man | less
But the discription of directory is lacking here.
The manpage of Debian has the discription included.
But this is not the chroot directory. That is, the working root directory remains the same if this one is specified. It's only used for relative pathnames in named.conf.
Offline
gzip -d </usr/man/man8/named.conf.5.gz | nroff -man | less
:shock:
man named.conf
But this is not the chroot directory. That is, the working root directory remains the same if this one is specified. It's only used for relative pathnames in named.conf.
Hmm, well, I thought it was correct. I would suggest the following:
Add a request to the bug tracker to add a conf.d setup for named, or some way to specify options not configurable via a config file.
Then, I would just directly edit /etc/rc.d/named and add your chroot option in there until something is implemented.
Offline
twelvegates wrote:gzip -d </usr/man/man8/named.conf.5.gz | nroff -man | less
:shock:
man named.conf
This doesn't work on my installation. It clains: No manual entry for named.conf
My bind is 9.3.0-1.
Hmm, well, I thought it was correct. I would suggest the following:
Add a request to the bug tracker to add a conf.d setup for named, or some way to specify options not configurable via a config file.
Ok, I've created one.
Offline