Thanks for your advice.
-----Original Message-----
From: Darren J Moffat
Sent: 06/03/08 23:26
> Jia Ni wrote:
>>> My understanding from the above reference is that the pen program
>>> itself does NOT read the /etc/pen.cf file by default (it does take -f
>>> argument). In this case I highly recommend that the pen
>>> configuration be via SMF properties able to be set per instance of
>>> svc:/network/pen/ or at least that there is a per instance property
>>> for specifying the config file location.
>> Sorry. I am not quite understand the meaning of "specifying config file
>> location"?
>> Usually, smf instance don't take any arguments and it's config file is
>> fixed somewhere. Do you mean I should set the each instance of pen
>> config file in a separate place? Eg, "pen.http.conf" for http,
>> "pen.ftp.conf" for ftp ...?
>
> Two choices either use SMF properties for all of the configuration
> options of pen - this is the idea case. Or create a smaller set of SMF
When Huafeng and I doing the porting, we actually once thought about this
method.
But the difficulty is we can't set every argument with a default value. Eg,
you can't image which hostname/ip will the back-end server be.
So, if a user want to start 'pen', he should first set several SMF properties
correctly (and maybe he should understand what these properties represent
before that).
> properties including one that gives the location of a pen.cf file, the
Yes.
I think a configure file is really easy for user to setup and start 'pen',
rather than SMF properties.
> method script would use that property to find pen.cf instead of being
> hardcoded to /etc/pen.cf as it would in the original spec.
I agree. Thanks!
>
--
Best regards,
Jia
