Dean Roehrich wrote:
> For Shared-QFS filesystems the network must be available and this is
> enforced by a new service, network/qfs/svc-shared-mount. The new
Why svc:/network/qfs/svc-shared-mount ?
Isn't the svc- redundant I would have expected one of these to be the FMRI:
svc:/network/qfs/shared:default
svc:/network/qfs/shared-mount:default
svc:/network/qfs/shared/mount:default
> service manifest, qfs/shared-mount.xml, places dependencies on
> loopback and physical network interfaces prior to starting the service
> script.
>
>
> Deliverables:
>
> /var/svc/manifest/system/sam-fsd.xml
> /var/svc/manifest/network/qfs/shared-mount.xml
> /lib/svc/method/svc-qfs-shared-mount
> /lib/svc/method/svc-sam-fsd
>
> Exported Interfaces:
>
> sam-fsd Committed Private Commandline syntax
> /var/svc/manifest/network/qfs/shared-mount.xml
> Project Private Executable location
> /lib/svc/method/svc-qfs-shared-mount
> Project Private Executable location
> /var/svc/manifest/system/sam-fsd.xml
> Project Private Executable location
> /lib/svc/method/svc-sam-fsd
> Project Private Executable location
The FMRI is an exported interface.
This case appears to export two new services (based on the fact that
there are two method scripts and to manifests in /var/svc/manifest) what
is the FMRI for the one with sam-fsd.xml manifest ? Is that a
deliverable from this case or some other one ?
Looks to me like there should also be a svc:/system/sam:default or
similar. Are there other parts to the sam service other than sam-fsd ?
--
Darren J Moffat
