Pass the Oracle Solaris 1z0-822 Questions and answers with ExamsMirror

Link-Based Failure Detection

Link-based failure detection is always enabled, provided that the interface supports this type of failure detection.

To determine whether a third-party interface supports link-based failure detection, use the ipmpstat -i command. If the output for a given interface includes an unknown status for its LINK column, then that interface does not support link-based failure detection. Refer to the manufacturer's documentation for more specific information about the device.

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.

How to Move a Running Process Into a New Task

This example shows how to associate a running process with a different task and new project.

To perform this action, you must either be superuser, or be the owner of the process and be a

member of the new project.

1. Become superuser or assume an equivalent role

2. Obtain the process ID of thebook_catalogprocess.

# pgrep book_catalog

8100

3. Associate process8100with a new task ID in thebooksiteproject.

# newtask -v -p booksite -c 8100

17

The -coption specifies that newtaskoperate on the existing named process.

4. Confirm the task to process ID mapping.

# pgrep -T 17

8100

Incorrect:

Not C: projmod does not change the processes of a project.

The projmod utility modifies a project's definition on the system. projmod changes the definition of the specified project and makes the appropriate project-related system file and file system changes.

By default, a new BE is automatically created when you perform one of the following operations:

* (D) Set the be-policy image policy to always-new. Under this policy, all package operations are performed in a new BE set as active on the next boot.

* Update particular key system packages such as some drivers and other kernel components. This can happen when you install, uninstall, update, change variant, or change facet.

* Often a new BE is created when you execute the pkg update command to update all packages that have updates available.

* Specify any of the following options: --be-name, --require-new-be, --backup-be-name, --require-backup-be.

* Use the zfs holds command to display a list of held snapshots.

* Holding a snapshot prevents it from being destroyed (B). In addition, this feature allows a snapshot with clones to be deleted pending the removal of the last clone by using the zfs destroy -d command. Each snapshot has an associated user-reference count, which is initialized to zero. This count increases by one whenever a hold is put on a snapshot and decreases by one whenever a hold is released.

Note:

* Example:

# zfs holds tank/home@now

NAME TAG TIMESTAMP

tank/home@now keep Thu Jul 15 11:25:39 2010

* You can use the zfs release command to release a hold on a snapshot or set of snapshots.

If the snapshot is released, the snapshot can be destroyed by using the zfs destroy command.

* Two new properties identify snapshot hold information:

The defer_destroy property is on if the snapshot has been marked for deferred destruction by using the zfs destroy -d command. Otherwise, the property is off.

The userrefs property is set to the number of holds on this snapshot, also referred to as the user-reference count.

audit_remote

- send Solaris audit logs to a remote server

The audit_remote plugin module for Solaris audit, /usr/lib/security/audit_remote.so, sends binary audit records (audit.log) to audit servers as they are configured with auditconfig.

The audit_remote plugin is loaded by auditd if the plugin is configured as an active via auditconfig. Use the auditconfig -setplugin option to change all the plugin related configuration parameters.

Incorrect:

not D: Audit policy determines the characteristics of the audit records for the local host. When auditing is enabled, the contents of the /etc/security/audit_startup file determine the audit policy.

A: The pkd.depotd service is managed by SMF under the service identifier svc:/application/pkg/server.

D:

* Example:

Configure pkg.depotd to provide remote access. pkg.depotd provides an HTTP interface to a pkg repo. Here we are going to make the repo server listen on port 10000, and use the repo dir we created as its default.

# svcadm disable pkg/server

# svccfg -s pkg/server setprop pkg/inst_root = /data/myrepo

# svccfg -s pkg/server setprop pkg/port = 10000

# svcadm refresh pkg/server

# svcadm enable pkg/server

* pkg.depotd is the depot server for the image packaging system. It provides network access to the data contained within a package repository. Clients that do not support direct access to a repository through the file system, or for which network access is the only available or preferred method of transport, typically use the package depot.

* The following directives cause audit_binfile.so to be loaded, specify the directories for writing audit logs, and specify the percentage of required free space per directory.

auditconfig -setplugin audit_binfile active \

"p_dir=/var/audit/jedgar/eggplant,/var/audit/jedgar.aux/eggplant,

/var/audit/global/eggplant;p_minfree=20;p_fsize=4.5GB"

* The attributes specifying the configuration of audit_binfile plugin include:

p_dir

dir1[,dir2],.. [,dirn]

A list of directories, where the audit files will be created. Any valid writable directory can be specified.

p_fsize

The p_fsize attribute defines the maximum size that an audit file can become before it is automatically closed and a new audit file is opened. This is equivalent to an administrator issuing an audit -ncommand when the audit file size equals the value specified by the administrator. The default size is zero (0), which allows the file to grow without bound.