On Mon, Jan 28, 2008 at 07:48:48PM -0800, David Bustos wrote: > Quoth Mike Shapiro on Mon, Jan 28, 2008 at 11:48:16AM -0800: > > I think two things are needed: > > > > (a) The notion of this "proxy restarter" (come up with some better name) > > where > > startd does method script but hooks are provided for interaction with > > another service that is involved in managing or configuring the resource > > Do you know how such a service would manage or configure the service? > I suspect you're describing an administrative agent. In any case, > please file an RFE for the features you think SMF is missing.
The service doesn't configure the resource: the method script configures it, the service does something else on top of that information: adds more config, modifies it, triggers another thing to happen based on it reaching the online state, whatever. > > (b) The idea that who the proxy is varies based on another service config. > > e.g. network-physical:old, or network-physical:nwam, or > > network-physical:cluster being enabled determines who's in charge, > > but they all are sharing method scripts and a common SMF service > > model for the underlying datalink and interface abstractions. > > Do you think this model will be so common that it should be settled into > the framework? If it's just networking, then I suspect it would be > better to have a networking restarter which knows how to change behavior > based on configuration, rather than it being a generic option available > to any developer. But do file an RFE to be a focal point of discussion. I do think it should be in the framework: I think this has more general applications. -Mike -- Mike Shapiro, Solaris Kernel Development. blogs.sun.com/mws/
