Jan Setje-Eilers wrote:
>
> Is there any chance we can separate this case from a general archive
> recovery discussion?
>
> In particular this case attempts to provide a method to configure the
> archive update behavior n uadmin invocation in light of very different
> requirements depending on deployment. This configuration is needed
> regardless of the level to which the system can recover itself.
>
> Some background to help clarify the motivation for this particular case:
>
> The previous users of uadmin(3c) that we had encountered were
> clustering applications that require the ability to tear down a node as
> quickly as possible. The current customer as an update/configuration
> deployment framework that calls uadmin(3c) after applying the changes to
> the system.
>
> -jan
If this view ultimately prevails, I think you should consider reversing
the default so that the more robust behavior occurs unless you
specifically disable it (e.g. for a clustered system).
Besides optimizing for the common case, I think Jim Carlson makes a good
point that you don't want to spread folklore that Solaris needs special
tuning to be enterprise-worthy.
Scott
--
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)
