>>
>> They need to play well together. The rest is implementation detail.
>> (I thought that was all sorted out already, no?)
>>
>>
>>
> That is what I too thought. So, I am confused as to the need for this
> 'apachectl.smf' script - is this an implementation detail , that won't
> be exposed to the customers ?
>
> If yes, then again my concern is - why can't we leverage already
> existing '/lib/svc/method/http-apache2' script for this purpose.
/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.
If we can modify apachectl interface (like adding more options), then there is
no need
for another script.
I would like to know
1. If apachectl interface can be modified?
2. If no, then should we ask the users to manually invoke svcamd commands ?
3. or should we provide a wrapper script and handle svcadm command invocation
from within the script ?
4. or should we reuse /lib/svc/method/http-apache2 to invoke svcamd command and
ask the user to run "/lib/svc/method/http-apache2 start" to start the smf
service ?
Thanks,
Seema.
