Re: Experiences running named and rndc on 4.4 vs 4.3

2008-11-13 Thread 23号
-- Best Regards My Chaos: https://n23.appspot.com vi /etc/rc: ... if [ X${named_flags} != XNO ]; then if ! cmp -s /etc/rndc.key /var/named/etc/rndc.key ; then echo -n rndc-confgen: generating new shared secret... if /usr/sbin/rndc-confgen -a -t /var/named

Re: Experiences running named and rndc on 4.4 vs 4.3

2008-11-12 Thread Woodchuck
On Tue, 11 Nov 2008, Don Jackson wrote: Today I began testing named on a freshly installed OpenBSD 4.4 amd64 machine, using my old named.conf file from 4.3 (which was still running named version 9.4.2) When the machine first boots after the install, /etc/rc determines there is no rndc.key,

Re: Experiences running named and rndc on 4.4 vs 4.3 - Solved/Explained

2008-11-12 Thread Don Jackson
Yes, you are exactly right. My OS install script renames the existing /var/named/etc directory, and creates a new one pulled from version control, and in so doing, does not restore the correct ownership of the etc directory. So later on, during the execution of /etc/rc, the rndc.key file gets

Experiences running named and rndc on 4.4 vs 4.3

2008-11-11 Thread Don Jackson
Today I began testing named on a freshly installed OpenBSD 4.4 amd64 machine, using my old named.conf file from 4.3 (which was still running named version 9.4.2) When the machine first boots after the install, /etc/rc determines there is no rndc.key, and generates one: rndc-confgen: generating

Re: Experiences running named and rndc on 4.4 vs 4.3

2008-11-11 Thread Stijn
Don Jackson wrote: Today I began testing named on a freshly installed OpenBSD 4.4 amd64 machine, using my old named.conf file from 4.3 (which was still running named version 9.4.2) When the machine first boots after the install, /etc/rc determines there is no rndc.key, and generates one: