Your Path to Success: How to Pass the Oracle 1z0-822 Oracle Solaris 11 Advanced System Administration Exam

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.

re

page reclaims.

The information is given in units per second.

Note:

* vmstat reports virtual memory statistics regarding kernel thread, virtual memory, disk, trap, and CPU activity.

Incorrect:

Not B: sr, pages scanned by clock algorithm

Not C: free

size of the free list (Kbytes)

Not D: fr

kilobytes freed

Note:

* The default AI manifest must work for any client that does not match a custom manifest, for any service based on this image.

Interface mode displays the state of all IP interfaces (IP links) that are tracked by in.mpathd on the system.

Incorrect:

Not A: Address mode displays the state of all IPMP data addresses on the system.

Not B: Group mode displays the state of all IPMP groups on the system.

Not D: Probe mode displays information about the probes being sent by in.mpathd.

Not E: Target mode displays IPMP probe target information.

A: To restart remote logging:

svccfg -s system-log setprop config/log_from_remote=true

svcadm restart system-log

D: You can run 'snoop' on the interface to see if you see syslog packets leaving the server

snoop udp port 514

D: Example:

# prctl -n task.max-lwps $$

process: 111107: csh

NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT

task.max-lwps

usage 3

privileged 3 - deny -

system 2.15G max deny

F: The following command activates system logging of all violations of task.max-lwps.

# rctladm -e syslog task.max-lwps

#

Note: How to Set the Maximum Number of LWPs for Each Task in a Project

This procedure adds a project named x-files to the /etc/project file and sets a maximum number of LWPs for a task created in the project.

1.Become an administrator.

2. Use the projadd command with the -K option to create a project called x-files. Set the maximum number of LWPs for each task created in the project to 3.

# projadd -K 'task.max-lwps=(privileged,3,deny)' x-files

root@solaris:~# zfs snapshot pool1/sales/qrreports@qrreportroot@solaris:~# zfs list -t snapshot -r pool1/sales/qrreportsNAME USED AVAIL REFER MOUNTPOINTpool1/sales/qrreports@qrreport 0 - 31K -root@solaris:~# zfs send -i pool1/sales/qrreports@qrreport pool1/sales/qrreports@mth2qtrreportError: Stream can not be written to a terminal.You must redirect standard output.

Explain:

If you want to change the content of a manifest or script that has already been added to an install service, use the installadm update-manifest command. Criteria, default status, and manifest_or_script_name are not changed as a result of the update.

# installadm update-manifest -n s11-x86

-f ./newregion1.xml -m region1

The create-manifest and update-manifest subcommands validate XML manifest files before adding them to the install service. AI syntactically validates the AI manifests at client installation time.

Note - If an invalid manifest is provided to a client, the automated installation aborts. To investigate the cause of the validation failure, see the /system/volatile/install_log on the client.

Refer to step 3 below.

After a typical software installation, there can be a half dozen or more processes that need to be started and stopped during system startup and shutdown. In addition, these processes may depend on each other and may need to be monitored and restarted if they fail. For each process, these are the logical steps that need to be done to incorporate these as services in SMF:

1.Create a service manifest file.

2.Create a methods script file to define the start, stop, and restart methods for the service.

3.Validate and import the service manifest using svccfg(1M).

4.Enable or start the service using svcadm(1M).

5.Verify the service is running using svcs(1).

How to Manually Specify Target Systems for Probe-Based Failure Detection

1. Add a route to a particular host to be used as a target in probe-based failure detection.

$ route -p add -host destination-IP gateway-IP -static

where destination-IP and gateway-IP are IPv4 addresses of the host to be used as a target. For example, you would type the following to specify the target system 192.168.10.137, which is on the same subnet as the interfaces in IPMP group itops0:

$ route -p add -host 192.168.10.137 192.168.10.137 -static

This new route will be automatically configured every time the system is restarted. If you want to define only a temporary route to a target system for probe-based failure detection, then do not use the -p option.

2.Add routes to additional hosts on the network to be used as target systems.