Ok, I see what you mean. The more requirements the more difficult it will be to
build an appropriate start string directly from within the manifest.
This means the method wrapper in /lib/method/svc is back in business. Probably
the only way to do it. As long as it solves something that cannot be supported
from within the manifest then I'm of course not against it ... and I think with
all the requirements now on the table that is probably the case.
To summarize the manifest could have the following properties in group 'httpd':
version: Controls which version of Apache is started, i.e. a string on the form
'2.2'. Defaults to: (don't know actually)
startup_options: Pass-thru options to pass to apachectl, e.g. a string such as
'-f /foo/apache/conf/httpd.conf'. Defaults to: empty string.
server_type: A string of either either 'prefork' or 'worker'. Defaults to
'prefork'.
bit64 : a boolean indicating to start the 64 bit version rather than 32 bit
version. Defaults to 'false'.
(note that I name I name this property bit64 rather than 64bit to avoid having
a name that does not start with a letter, just to be on the safe side)
The start string can then be:
/lib/svc/method/httpd-apache2 %{httpd/version} %{httpd/startup_options}
%{httpd/server_type} %{httpd/bit64}
The httpd-apache2 shell script would then take appropriate action based on
$1-$4 parameters.
Lars
This message posted from opensolaris.org
