Stacey Marshall writes: > I, like James, wanted the same ability but for dns/server.
Then you also need to file a similar bug as Jim found for ssh. The dns/server service needs to make its config file location configurable as a service property. (It shouldn't be specified as a dependency either.) > For example I wanted to leave the :default instance and add > another with the following differences: > > start/user astring named > start/privileges astring > basic,!proc_session,!proc_info,!file_link_any,net_privaddr,file_dac_read,file > _dac_search,sys_resource,proc_chroot > config_data/entities fmri file://localhost/var/named/named.conf As I mentioned above, this isn't sufficient, to specify an alternate config file for named to actually use? It seems like even if it was, the tricky bit is your desire to overwrite the user the start method runs as, right? You're not looking to completely duplicate the instance's config so much as tweak a few property groups just a little bit. That seems like a reasonable RFE for SMF to provide help with on the command line. I've just filed 6452754 to capture what I think the requirements are. Visual Panels will make this *lots* easier if you're willing to use a GUI. But even if we gave you code for 6452754, you'll still need to file a bug against dns/server to get it to read a config file property. I strongly encourage you to do that, and please add me to the interest list. :) thanks, liane -- Liane Praza, Solaris Kernel Development liane.praza at sun.com - http://blogs.sun.com/lianep
