Displaying 4 results from an estimated 4 matches for "named_flags".
2009 Jan 26
2
FreeBSD-7.1STABLE w/BIND-9.4.3-P1 start problem followup
...953: file not found
Jan 27 13:54:08 ns named[36447]: the working directory is not writable
.
.
.
.
Jan 27 13:54:08 ns named[36447]: running
2./etc/rc.conf
-------------------
named_enable="YES"
named_program="/usr/local/sbin/named" # path to named, if you want a different one.
named_flags="-c named.conf"
named_uid="bind" # User to run named as
named_chrootdir="/var/named" # Chroot directory (or "" not to auto-chroot it)
named_chroot_autoupdate="YES" # Automatically install/update chrooted...
2009 Mar 17
3
rndc: connect failed: 127.0.0.1#953: connection refused
...messages or log. And it won't start using rndc, it cause error message. Why does the error shows port 953 when I specified for port 53 in the config?
rndc: connect failed: 127.0.0.1#953: connection refused
Below are parts of my configs:
/etc/rc.conf:
named_enable="YES"
named_flags="-4 -S 1024 -c /etc/namedb/named.conf"
....
/etc/rndc.key:
key "rndc-key" {
algorithm hmac-md5;
secret "y9eca/WZydNfi.......................";
};
/etc/namedb/rndc.conf:
include "/etc/namedb/rndc.key";
options {
defau...
2009 Jan 26
2
FreeBSD-7.1STABLE w/BIND-9.4.3-P1 start problem
...so"
moused_enable="YES"
moused_flags="-3"
moused_port="/dev/psm0"
moused_type="auto"
saver="logo"
sshd_enable="YES"
usbd_enable="YES"
sendmail_enable="NONE"
log_in_vain="YES"
named_enable="YES"
#named_flags="-u bind -t /etc/namedb/sandbox -c named.conf -d 9"
named_flags="-c named.conf"
#syslogd_flags="-ss -l /etc/namedb/sandbox/dev/log"
#named_pidfile="/var/named/run/named/pid" # Must set this in named.conf as well
named_uid="bind" # Use...
2009 Mar 17
1
general: warning: max open files (3636) is smaller than max sockets (4096)
This happend since I've upgraded bind 9.21 to 9.6.0. I've increased the max open files to 4096:
sysctl -w kern.maxfiles=4096
which shows it resized from 4040->4096
But I guess it's different for bind? I've googled and found several references to this warning message, but everyone states it's not a problem and shouldn't be concerned. Some real advice would be