I am working toward a solution for the following Call Records: 6461591 dns/server should not use its config file as a dependency 6461587 named(1M) CLI options should have corresponding SMF properties
The issue I have is how to upgrade currently installed network/dns/server instances such that the configuration file and execution string command line options are retained. For example, lets assume the current system has a modified default instance with the following exec property and : $ svcprop -p start/exec dns/server:default /usr/sbin/named -4 $ svcprop -p config_data/entities dns/server:default file://localhost/etc/named.conf What must be done during upgrade to convert these settings to the following SMF properties? $ svcprop -p start/exec dns/server:default /lib/svc/method/dns-server %m %i $ svcprop -p options/ip_interfaces dns/server:default IPv4 $ svcprop -p options/configuration_file dns/server:default /etc/named.conf $ One suggestion was that the replacement start method could be used to populate the future settings. For this to work I presume an interim setting would have to take place; for example this might take on the following form: $ svcprop -p start/exec dns/server:default /lib/svc/method/dns-server %m %i upgrade /usr/sbin/named -4 The start method could then update the required properties and start/exec string accordingly; assuming permissions allow. One issue I see here is that to address 6461591 I had removed the property from usr/src/cmd/bind/server.xml. But if its removed before the upgrade then it will no longer exist! Looking at usr/src/pkgdefs/SUNWbindr/postinstal [1] It seems that I may be able to retrieve the current settings by writing to /var/svc/profile/upgrade. Indeed it seems that this is where the new manifest is imported. I could thus safely collect config_data/entities values and append them also to the initial start/exec method as well, meaning we'd have something like: Looking at usr/src/pkgdefs/SUNWbindr/postinstal [1] It seems that I may be able to retrieve the current settings by writing to /var/svc/profile/upgrade. I could thus safely collect config_data/entities values and append them also to the initial start/exec method as well, meaning we'd have something like: $ svcprop -p start/exec dns/server:default /lib/svc/method/dns-server %m %i upgrade /usr/sbin/named -4 file://localhost/etc/named.conf And I do realize that I must consider that the configuration file may have been overridden using the '-c' option on the start/exec line! So, What is the consensus here for how to accomplish this? Any solution needs to consider that more than one instance may exist and require changes. Thanks for your help in this matter, Stacey [1] http://src.opensolaris.org/source/xref/sfw/usr/src/pkgdefs/SUNWbindr/postinstall -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3261 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20070109/bdf11751/attachment.bin>
