On Tue, Jan 27, 2009 at 2:21 PM, <sowmini.varadhan at sun.com> wrote: > On (01/27/09 14:11), Jason King wrote: >> >> Don't forget high availability software. I'm not sure how Sun cluster >> handles it, but Veritas Cluster Server obviously has to use ifconfig >> to add and remove IP addresses associated with a service. While >> administrator-initiated failover of services wouldn't present an issue >> (since an orderly shutdown and removal of the IP address can be done), >> most places presumably but it to auto-restart services on other nodes >> when there is a node failure. In that case, having the repaired node >> restart with the service IP address wouldn't be a very popular >> behavior. > > Can't that be simply resolved by having the mechanism that > implements the persistence first check if there's a > undo-journal associated with the action?
Yes -- I was just giving an example of a widespread (I'm guessing probably every large customer of Sun uses one of them to some degree) where third party software invokes ifconfig directly (and why).
