On 03/ 1/10 08:06 AM, Jan Damborsky wrote: > On 02/26/10 12:13 PM, Jan Damborsky wrote: >> installadm.h >> ------------ >> >> #define HTTPDCONF >> "/var/installadm/ai-webserver/ai-httpd.conf" >> >> With this fix, we will have 4 places when this path is defined: >> >> cmd/installadm/setup-image.sh >> cmd/installadm/svc-install-server >> cmd/installadm/installadm.h >> cmd/installadm/installadm-common.sh >> >> Thinking about how we might consolidate it, I am wondering if >> we could >> >> * specify that path as SMF property of install/server SMF service >> * read that path from SMF property instead of having it hardcoded >> at several places >> * deliver appropriate SMF profile to initialize that property >> when installadm(1M) tools are installed - profile might look like >> >> <?xml version='1.0'?> >> <!DOCTYPE service_bundle SYSTEM >> '/usr/share/lib/xml/dtd/service_bundle.dtd.1'> >> <service_bundle type="profile" name="default"> >> <service name="system/install/server" version="1" type="service"> >> <instance name="default" enabled="false"> >> <property_group name="http" type="application"> >> <propval name="httpd-conf-path" type="astring" >> value="/var/installadm/ai-webserver/ai-httpd.conf"/> >> </property_group> >> <instance> >> </service> >> </service_bundle> > > Thinking about this, maybe better approach would be to put > this stuff into SMF manifest itself - manifest resides in > usr/src/cmd/installadm/server.xml. >
It's not clear to me that this path should be configurable; placing it in SMF makes it so, but is that something we want? Dave
