Seema Alevoor wrote: > > /lib/svc/method/http-apache2 is normally used by the SMF framework > to start/stop the service. > http-apache2 is not expected to invoke "svcamd enable .." command.
(Right, currently it is the other way around.) > If we can modify apachectl interface (like adding more options), > then there is no need for another script. Please be mindful about stating whether you are talking about public interfaces or implementation detail whenever you refer to "another script", as it makes all the difference... IF you meant yet another public interface to start the server, no, that is not an option. It's important there be no confusion here! There are only two public interfaces: - "svcadm enable apache2" - the formal Sun-supported way - "apachectl start" - the well-known way from the apache community IF you meant additional scripts as part of [hidden] implementation detail, then sure, if needed. Implementation simplicity is a virtue, so fewer is better but if some additional implementation script is truly needed that's ok. These are not things a customer will ever invoke or need to worry about. > I would like to know > > 1. If apachectl interface can be modified? Not incompatibly. If it needs to be extended, sure, that is a possibility. In general I'd like to minimize changes to the upstream code mainly to minimize maintenance efforts. But any change that justifiably makes sense is welcome for discussion. > 2. If no, then should we ask the users to manually invoke svcamd commands ? Of course! That's the primary documented interface! "svcadm enable apache2" There is no "if" about it. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
