Hi all!
I made a change to some DNS zones last week and restarted named. I use the Sun
version with the default manifest. As a result, the DNS server service was
disabled and I only noticed days later;
[ Jan 19 18:01:29 Stopping because service restarting. ]
[ Jan 19 18:01:30 Executing stop method (:kill) ]
[ Jan 19 18:01:31 Disabled. ]
[ Jan 21 22:53:31 Enabled. ]
[ Jan 21 22:53:32 Executing start method ("/usr/sbin/named") ]
[ Jan 21 22:53:32 Method "start" exited with status 0 ]
So I glance at the manifest and find this curious detail;
<dependency name='config_data' grouping='require_all' restart_on='none'
type='path'>
<service_fmri value='file://localhost/etc/named.conf'/>
</dependency>
And furthermore I also find the following fun fact;
# ls -lc /etc/named.conf
-rw-r--r-- 1 root root 1432 Jan 19 20:13 /etc/named.conf
# ls -l /etc/named.conf
-rw-r--r-- 1 root root 1432 Nov 27 09:06 /etc/named.conf
Did the time stamp on /etc/named.conf prevent the service from restarting? If
so, shouldn't the service have gone into an offline state rather than disabled?
-Alex
This message posted from opensolaris.org
