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. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
