> I updated the link management document at: > > http://www.opensolaris.org/os/project/clearview/uv/link_id_management.pdf
I assume that by "The stop method will do nothing" in 2.3 you think a null stop method will keep the service manager from stopping your daemon. That's not the case. If processes are left in the main contract after the stop method exits, the service manager will kill them with SIGKILL until they're gone. The comparison with network/physical is not valid because network/physical is a "transient" service with no daemon. The correct way to keep users from stopping your daemon is to mark the general/enabled property as private, which unfortunately is not possible with SMF right now. So you'll just have to make sure (a) it's well documented that disabling the daemon is a bad idea, and (b) the tools which talk to the daemon inform the user appropriately when the daemon is disabled. Configuration data should be available before any services are started. (Indeed, that's how the service manager knows which services to start.) You should know, however, that configuration in the SMF repository is read-only until filesystem/usr has successfully remounted the root filesystem read/write. Before then, attempts to modify configuration (persistently, nonpersistent modifications should work) will fail with an error like SCF_ERROR_BACKEND_READONLY. In the future we would like to change this so that configuration is modifiable right away, but that project hasn't been designed. David This message posted from opensolaris.org
