|
Description
|
The current behaviour is made clear here:
$ svcprop /network/ssh | grep ^start/
start/exec astring /lib/svc/method/sshd\ start
start/timeout_seconds count 30
start/type astring method
$ svcprop /network/login\:rlogin | grep ^inetd_start/
inetd_start/exec astring /usr/sbin/in.rlogind
inetd_start/group astring root
inetd_start/limit_privileges astring :default
inetd_start/privileges astring :default
inetd_start/project astring :default
inetd_start/resource_pool astring :default
...
The /network/ssh manifest has no <method_context> element in its starter's <exec_method>, so properties such as start/resource_pool are not even created on importing the manifest.
For /network/login:rlogin, the manifest /does/ have a <method_context>, so all properties derived from <method_context> are created, even if they're the default value, as can be seen above.
For usability's sake, we should always get the import manifest operation to create all the properties, even in the (legitimate) absence of a <method_context>.
Worse, if the user adds an empty method_context (for, e.g. specifying the project)
the project is *silently* ignored unless either method_credential or method_profile
is specified.
bustos 2006-04-10
The project part of this has been moved to
6411391 Empty method_context's don't work
|