Hi Jan,
I have a couple more responses inline.
On 09/29/10 05:33 AM, Jan Damborsky wrote:
Section 12.2:
--------------
- I am confused by the first bullet.
"SCI tool invoked by start method of
svc:/system/install/config:default smf service".
I thought the SCI tool is invoked as a standalone application.
To me, that means that is something a user/role would
execute a command to run. What does that have to do with a SMF
service?
Let me try to clarify. By standalone application it is meant that it
is not part
of text installer, but instead separate 'binary'.
In most common scenarios (e.g. installed/cloned/migrated zone), we
want that
tool automatically be invoked during first boot of installed system
at the right
point - this is why it is called from
svc:/system/install/config:default smf service.
So, is it correct to say that the SCI tool, standalone, will only be
invoked via SMF scripts?
Will it ever be a case that this tool get invoked after the system is
fully booted?
For example, will it ever be a case where a user assume the root role
and run the tool?
For scenarios we have considered so far, the standalone SCI tool would
be invoked
via SMF.
If this is the case, would it make more sense to make this standalone
SCI tool into a function
that the SMF scripts can call? The advantage is that users/roles will
not accidentally
invoke the command, and the command will have to worry about checking
whether
it is invoked from a SMF context or not.
However, there might be cases we are not aware of right now when user
might
want to invoke SCI tool from command line. For instance, slightly
enhanced SCI
tool could be used to generate sample SC profile.
When we need to handle this case in the future, we can write a quick
application
that calls the SCI tool function above.
Thanks,
--Karen
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
