1Z0-822 · Question #80
There is a valid SMF manifest located underneath the /var/svc/manifest directory. Which four methods can be used to add it to the services repository?
The correct answer is A. Reboot the system. C. Use the svccfg apply command. D. Restart the manifest-import service. E. Use the svccfg import command. AD: Manifests from the standard directory trees /lib/svc/manifest and /var/svc/manifest are processed during system boot and anytime an administrator or program runs: $ svcadm restart manifest-import apply subcommand If the argument is a service profile or manifest, apply the…
Question
There is a valid SMF manifest located underneath the /var/svc/manifest directory. Which four methods can be used to add it to the services repository?
Options
- AReboot the system.
- BRestart the early-manifest-import service.
- CUse the svccfg apply command.
- DRestart the manifest-import service.
- EUse the svccfg import command.
How the community answered
(22 responses)- A73% (16)
- B27% (6)
Explanation
AD: Manifests from the standard directory trees /lib/svc/manifest and /var/svc/manifest are processed during system boot and anytime an administrator or program runs: $ svcadm restart manifest-import apply subcommand If the argument is a service profile or manifest, apply the configuration to the admin layer of the SMF repository. Services, instances, property groups, and properties will be created as E: import [-V] [file | directory] svccfg import on a file in a system-managed filesystem location (subdirectories of /lib/svc/manifest and /var/svc/manifest) invokes: svcadm restart manifest-import. Placing your manifests in a system-managed location and invoking svcadm restart manifest- import to import them is the recommended practice. svccfg import on files in other locations imports their properties as administrative customization into the admin layer. It is equivalent to: svccfg apply [file | directory] not B: Manifests are processed in two different phases during boot. The service svc:/system/early-manifest-import:default, a pseudo service, is responsible for the first manifest processing. This service processes only manifests from the /lib/svc/manifest directory tree before svc.startd(1M) initializes any services thus enabling services delivered in /lib/svc/manifest to always start with their most updated definition. Since this is a pseudo service, svcadm(1M) commands are ignored though svcs(1) can be used to observe status and get log file information. The svc:/system/manifest-import:default service handles the second manifest processing and imports manifest files from both /lib/svc/manifest and /var/svc/manifest directory trees, in that respective order.
Topics
Community Discussion
No community discussion yet for this question.