Let me integrate John's, Huafeng's, Kacheong's and your options:
1, A SMF instance example will be created, like pen:http, which set the
listenport property to 80. So users can start/stop separating instances
conveniently. And this case shows the advantage of SMF.
2, Information will be provided in the man page. Users will be told multiple
'pen' processes could be executed by creating multiple SMF instances,
following the example, like pen:http.
3, No pen:http8888, pen:http8080, pen:http12345 etc. instances will be shipped
with the release. I think that makes solaris services look in a ridiculous
way. Just ask administrator to do so when they need.
4, 'pen' will be now located at svc:/network/loadbalancer/pen:default.
By the way, if a user want to create a new instance manually through command
line, the only way is to use 'svccfg import' utility, right?
Thank you!
-----Original Message-----
From: Darren J Moffat
Sent: 08/07/08 16:45
> Huafeng Lu wrote:
>> Darren J Moffat ??:
>>> Huafeng Lu wrote:
>>>> Darren J Moffat wrote:
>>>>> Jia Ni wrote:
>>>>>> I don't mean there can't be 2 pen process in the system.
>>>>>> I mean pen can't be used on ftp, according to my comprehension.
>>>>>>
>>>>>> Back to you question, I can configure 'pen' on port 80 for http
>>>>>> request. Meanwhile, I can configure it on port 8080 for http request.
>>>>>> Again, I can configure it on port 8888 for http request at the same
>>>>>> time.
>>>>>>
>>>>>> I don't know how to deal with such situation according to your
>>>>>> assumption. Should I add pen:http, pen:http8080, pen:http8888?
>>>>> Yes that is exactly what I was suggesting.
>>>> I'm not sure if I understand you correctly. Providing multiple SMF
>>>> instances for many http ports looks really funny to me. (Yes 8080 and
>>>> 8888 are common for http; with the pen command line options it's easy
>>>> to configure, but providing a SMF instance for each port doesn't seem
>>>> graceful to me.)
>>> That is the whole point of SMF instances. What you get from this is
>>> the ability to have different people control the difference instances
>>> and for them to be managed independently. For example if the 8080
>>> service needs to come down for maintenance the 80 and 8888 versions
>>> stay running if they are separate instances, if you put them all in
>>> one instance you disrupt all three.
>> So how about other ports? do we also need http:8088, http:6666,
>> http:8765, etc?
>
> You wouldn't use a : in the instance name it would look like this:
>
> svc:/network/pen:default
> May have nothing configured
> svc:/network/pen:http80
> pen/listen_port = 80
> svc:/network/pen:http8080
> pen/listen_port = 8080
>
> All instances in this case would have the same start/stop methods but
> would be able to have different properties.
>
--
Best regards,
Jia
