Selected 1z0-822 Oracle Solaris Questions Answers

Profiles are, in many ways, similar to manifests in that they use the same XML DTD. However, instead of providing information about a service, its dependencies, and methods, a profile is used to provide customization of a service or an instance of a service. Customizations include whether an instance of a service should be enabled or disabled and any modifications to service configuration properties.

Incorrect:

Not A: Manifests (not profiles) are used to describe services and instances of a service, including any property groups and properties they might have.

A: Resource Allocation: Zones, Pools and FSS

Example:

Then create a pool for your zone (in this example, we'll use the zones named 'habitue,' 'creator,' 'netid,' and 'linguo'): pooladm -x

pooladm -s

poolcfg -c 'create pool habitue-pool ( string pool.scheduler = "FSS" )'

poolcfg -c 'create pool creator-pool ( string pool.scheduler = "FSS" )'

poolcfg -c 'create pool linguo-pool ( string pool.scheduler = "FSS" )'

poolcfg -c 'create pool netid-pool ( string pool.scheduler = "FSS" )'

pooladm -c

B: Set the default scheduler for the system to be the FSS.

# dispadmin -d FSS

D: Example:

global# zonecfg -z global

zonecfg:myzone> set cpu-shares=100

zonecfg:myzone> set scheduling-class=FSS

zonecfg:myzone> exit

C: You can use the scheduling-class property in zonecfg to set the scheduling class for the zone.

D: When you explicitly set the cpu-shares property, the fair share scheduler (FSS) will be used as the scheduling class for that zone. However, the preferred way to use FSS in this case is to set FSS to be the system default scheduling class with the dispadmin command. That way, all zones will benefit from getting a fair share of the system CPU resources. If cpu-shares is not set for a zone, the zone will use the system default scheduling class.

E: You can set the scheduling class for a zone through the resource pools facility. If the zone is associated with a pool that has its pool.scheduler property set to a valid scheduling class, then processes running in the zone run in that scheduling class by default.

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

C: svccfg

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 necessary.

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]

Incorrect:

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.