On 03/ 3/10 02:32 AM, Jan Damborsky wrote: > On 03/ 2/10 10:25 PM, Dave Miner wrote: >> On 03/ 1/10 08:06 AM, Jan Damborsky wrote: >>> 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? > > That is a good point - I don't think there might be a need for this. > Another question might be if we want to expose this path to the > user. I can see it might be useful in case user wants to inspect or > modify http configuration (e.g. change 'Listen'). Then one > could take a look at SMF property to find out where to search for > config file. > It might become more appealing with this fix, since it will allow to > change default HTTP port. >
Sure, but we usually just document fixed paths for configuration files that don't have a requirement to be relocatable. Telling them to go look in SMF for the path is somewhat indirect by comparison. Dave
