2012-10-05 1:44, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris) пишет:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Jim Klimov
There are also loops ;)
# svcs -d filesystem/usr
STATE STIME FMRI
online Aug_27 svc:/system/scheduler:default
...
# svcs -d scheduler
STATE STIME FMRI
online Aug_27 svc:/system/filesystem/minimal:default
...
# svcs -d filesystem/minimal
STATE STIME FMRI
online Aug_27 svc:/system/filesystem/usr:default
...
How is that possible? Why would the system be willing to startup in a
situation like that? It *must* be launching one of those, even without its
dependencies met ...
Well, it seems just like a peculiar effect of required vs. optional
dependencies. The loop is in the default installation. Details:
# svcprop filesystem/usr | grep scheduler
svc:/system/filesystem/usr:default/:properties/scheduler_usr/entities
fmri svc:/system/scheduler
svc:/system/filesystem/usr:default/:properties/scheduler_usr/external
boolean true
svc:/system/filesystem/usr:default/:properties/scheduler_usr/grouping
astring optional_all
svc:/system/filesystem/usr:default/:properties/scheduler_usr/restart_on
astring none
svc:/system/filesystem/usr:default/:properties/scheduler_usr/type
astring service
# svcprop scheduler | grep minimal
svc:/application/cups/scheduler:default/:properties/filesystem_minimal/entities
fmri svc:/system/filesystem/minimal
svc:/application/cups/scheduler:default/:properties/filesystem_minimal/grouping
astring require_all
svc:/application/cups/scheduler:default/:properties/filesystem_minimal/restart_on
astring none
svc:/application/cups/scheduler:default/:properties/filesystem_minimal/type
astring service
# svcprop filesystem/minimal | grep usr
usr/entities fmri svc:/system/filesystem/usr
usr/grouping astring require_all
usr/restart_on astring none
usr/type astring service
The answer to this question, will in all likelihood, shed some light on my
situation, trying to understand why my iscsi mounted zpool import/export
service is failing to go down or come up in the order I expected, when it's
dependent on the iscsi initiator.
Likewise - see what dependency type you introduced, and verify
that you've "svcadm refreshed" the service after config changes.
HTH,
//Jim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
