James Carlson wrote: > lianep at eng.sun.com writes: >> You're talking about actually duplicating an instance, which often >> (but not always) means that both couldn't run at the same time, as they'd >> be competing for the same system resources. Can you help me understand >> how this is useful in testing? Is it just so you can revert back to >> the system's original state/configuration after the test, or for >> something more subtle? > > I've often wanted to do this -- by running the two instances with > different configuration files, and different configured network ports > or lists of interfaces. > > For example, I sometimes want to run more than one sshd, with > different sets of interfaces and ports bound, and different > configuration files specified for each. (For example, one bound on an > internal RFC 1918 address and another bound on an external Internet- > facing address.) > > There's no "competition," because they're intentionally configured > differently. > > The only way I've found to do it so far is by setting up my own rc*.d > scripts. >
Hi, Thanks for prompt response. I, like James, wanted the same ability but for dns/server. 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 This is I believe the intention for having an instance for dns/server. Cheers, Stacey
