Matt Ingenthron wrote: > > An alternate approach is for apachectl to be modified to know how to > retrieve properties from SMF, call the enable/disable (though there's > not an exact equivalence of semantics here), etc. > This is what I'd intended :) Sorry for the lack of clarity in my previous post about renaming apachectl to apachectl.private. My intention was to provide SMF support via apachectl for options where it was possible e.g.
% svcadm enable apache2 % apachectl stop I didn't intend to suggest that all other options of apachectl be disabled/removed. The apachectl that I had in mind was that it was a combination of a) being a wrapper around SMF commands for options that could be mapped to SMF b) being a wrapper around apachectl.private for the other options > We may want to do this in the interim, but if it's practical to make > modifications to the apachectl script to use SMF and push them upstream, Yes. I was thinking of something along the lines of adding support for an additional flag to configure Apache e.g. --enable-smf Arvind
