1z0-822 Oracle Solaris 11 Advanced System Administration Free Practice Exam Questions (2025 Updated)

* -p pattern

Set the per-process core file name pattern to pattern for each of the specified process-IDs. The pattern can contain any of the special % variables

* Variables:

%f, executable file name, up to a maximum of MAXCOMLEN characters

%p, process-ID

* Example. The core file name pattern:

/var/core/core.%f.%p

would result, for command foo with process-ID 1234, in the core file name: /var/core/core.foo.1234

* Example. Setting the core file name pattern

When executed from a user's $HOME/.profile or $HOME/.login, the following command sets the core file name pattern for all processes run during the login session:

example$ coreadm -p core.%f.%p $$

$$ is the process-id of the currently running shell. The per-process core file name pattern is inherited by all child processes.

Note (see synopsis 2 below).

* The coreadm command is used to specify the name and location of core files produced by abnormally-terminating processes.

SYNOPSIS

coreadm [-g pattern] [-i pattern] [-d option...] [-e option...]

coreadm [-p pattern] [pid...]

coreadm –u

The first form shown in the synopsis can be executed only by the super-user and is used to configure system-wide core file options, including a global core file name pattern and a per-process core file name pattern for the init(1M) process.

The second form can be executed by non-privileged users and is used to specify the file name pattern to be used by the operating system when generating a per-process core file.

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

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

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.

dumpadm - configure operating system crash dump

SYNOPSIS

/usr/sbin/dumpadm [-nuy] [-c content-type] [-d dump-device]

[-m mink | minm | min%] [-s savecore-dir]

[-r root-dir] [-z on | off]

The options include:

A: -d dump-device

Modify the dump configuration to use the specified dump device.

B: -s savecore-dir

Modify the dump configuration to use the specified directory to

save files written by savecore.

D: -m mink | minm | min%

Create a minfree file in the current savecore directory indicating

that savecore should maintain at least the specified amount of free

space in the file system where the savecore directory is located.

E: -z on | off

Modify the dump configuration to control the operation of savecore on reboot. The options are on, to enable saving core files in a compressed format, and off, to automatically uncompress the crash dump file. The default is on, because crash dump files can be very large and require less file system space if saved in a compressed format.

Note:

You might want a local IPS repository for the following reasons:

Performance and security. You do not want your client systems to go to the Internet to retrieve new software packages or update existing packages.

Replication. You want to ensure that you can perform the same installation next year that you perform today.

Custom packages. You want to include your own IPS package in the same repository with Oracle Solaris OS packages.

svcs -x: Explains why a service is not available.

Incorrect:

not A: svcs -l FMRI: Provides a long listing of information about FMRI; includes dependency information

not B, not C: svcs -d FMRI: Lists dependencies for FMRI.

not e: svcadm clear FMRI: Clear faults for FMRI.

The Zone Management profile grants the power to manage all of the non-global zones on the system to a user.

Dump Parameter: minimum free space

Minimum amount of free space required in the savecoredirectory after

saving crash dump files. If no minimum free space has been configured, the

default is one Mbyte.

* Syntax:

priocntl -s [-c class] [class-specific options]

[-i idtype] [idlist]

* The priocntl command displays or sets scheduling parameters of the specified process(es). It can also be used to display the current configuration information for the system's process scheduler or execute a command with specified scheduling parameters.

Processes fall into distinct classes with a separate scheduling policy applied to each class. The process classes currently supported are the real-time class, time-sharing class, interactive class, fair-share class, and the fixed priority class.

* priocntl options include:

-c

class

Specifies the class to be set. (The valid class arguments are RT for real-time, TS for time-sharing, IA for inter-active, FSS for fair-share, or FX for fixed-priority.) If the specified class is not already configured, it is automatically configured.

-s

Sets the scheduling parameters associated with a set of processes.

A:

* nscfg

- import, export name service configurations

* subcommand import

import [-fvq] FMRI

If none of the SMF repository properties for the specified FMRI are currently populated, import the legacy configuration files associated with the specified FMRI into the SMF repository.

* Example: Importing DNS Client Configuration

The following command imports the DNS client configuration, stored in resolv.conf, into the SMF repository.

# nscfg import svc:/network/dns/client:default

* svcadm– manipulate service instances

D: netcfg

- create and modify network configuration profiles

The netcfg utility manipulates system network configuration profiles. netcfg can be invoked interactively, with an individual subcommand, or by specifying a command file that contains a series of subcommands.

/ netcfg location properties include:

/ nameservices: enum value list: files | dns | nis | ldap

Specifies the name services that should be configured, such as DNS, NIS, and LDAP.

Incorrect:

Not B: netcfg has no subcommand import.

Note:

* Each workstation has a nsswitch.conf file in its /etc directory. Each line of that file identifies a particular type of network information, such as host, password, and group, followed by one or more sources, such as NIS+ tables, NIS maps, the DNS hosts table, or local /etc, where the client is to look for that information.

* The Solaris platform provides the following naming services.

/ DNS, the Domain Name System

/ /etc files, the original UNIX naming system

/ NIS, the Network Information Service

/ NIS+, the Network Information Service Plus

/ LDAP, the Lightweight Directory Access Protocol

Service Dependency. This element identifies a group of FMRIs upon which the service is in some sense dependent.

ATTRIBUTE: Grouping:

Possible values:

'require_all',

'require_any',

'exclude_all',

‘optional_all'

Note:

* Example 1:

name='network'

grouping='require_all'

restart_on='none'

type='service'>

* In this example, let's choose the svc:/system/zones:default service instance. We can use the -l option and the service name to get more information, as shown in Listing 3.

# svcs -l svc:/system/zones:default

fmri svc:/system/zones:default

name Zones autoboot and graceful shutdown

enabled true

state online

next_state none

state_time June 14, 2012 08:30:31 PM NZST

logfile /var/svc/log/system-zones:default.log

restarter svc:/system/svc/restarter:default

manifest /etc/svc/profile/generic.xml

manifest /lib/svc/manifest/system/zones.xml

manifest /lib/svc/manifest/system/zonestat.xml

dependency require_all/none svc:/milestone/multi-user-server (online)

dependency optional_all/none svc:/system/pools:default (disabled)

dependency optional_all/none svc:/system/pools/dynamic:default (disabled)

dependency optional_all/none svc:/system/zones-monitoring (online)

See % below.

coredump parameter: -m mink | minm | min%

Create a minfree file in the current savecore directory indicating that savecore should maintain at least the specified amount of free space in the file system where the savecore directory is located. The min argument can be one of the following:

k

A positive integer suffixed with the unit k specifying kilobytes.

m

A positive integer suffixed with the unit m specifying megabytes.

%

A % symbol, indicating that the minfree value should be computed as the specified percentage of the total current size of the file system containing the savecore directory.

The savecore command will consult the minfree file, if present, prior to writing the dump files. If the size of these files would decrease the amount of free disk space below the minfree threshold, no dump files are written and an error message is logged. The administrator should immediately clean up the savecore directory to provide adequate free space, and re-execute the savecore command manually. The administrator can also specify an alternate directory on the savecore command-line.

Incorrect:

Not C: Separate ZFS volumes must be used for the swap area and dump devices.

The zfs get command supports the -H and -o options, which are designed for scripting. You can use the -H option to omit header information and to replace white space with the Tab character. Uniform white space allows for easily parseable data. You can use the -o option to customize the output in the following ways:

* The literal name can be used with a comma-separated list of properties as defined in the Introducing ZFS Properties section.

* A comma-separated list of literal fields, name, value, property, and source, to be output followed by a space and an argument, which is a comma-separated list of properties.

The following example shows how to retrieve a single value by using the -H and -o options of zfs get:

# zfs get -H -o value compression tank/home

on

See 1 below.

Precedence Rules

For nfsmapid to work properly, NFS version 4 clients and servers must have the same domain. To ensure matching NFS version 4 domains, nfsmapid follows these strict precedence rules:

1. The daemon first checks the SMF repository for a value that has been assigned to the nfsmapid_domain parameter. If a value is found, the assigned value takes precedence over any other settings. The assigned value is appended to the outbound attribute strings and is compared against inbound attribute strings.

2. If no value has been assigned to nfsmapid_domain, then the daemon checks for a domain name from a DNS TXT RR. nfsmapid relies on directives in the /etc/resolv.conf file that are used by the set of routines in the resolver. The resolver searches through the configured DNS servers for the _nfsv4idmapdomain TXT RR.

3. If no DNS TXT record is configured to provide a domain name, then the nfsmapid daemon uses the value specified by the domain or search directive in the /etc/resolv.conf file, with the directive specified last taking precedence.

4. If the /etc/resolv.conf file does not exist, nfsmapid obtains the NFS version 4 domain name by following the behavior of the domainname command. Specifically, if the /etc/defaultdomain file exists, nfsmapid uses the contents of that file for the NFS version 4 domain. If the /etc/defaultdomain file does not exist, nfsmapid uses the domain name that is provided by the network's configured naming service.

* DiffServ uses the 6-bit Differentiated services Field (DS field) in the IP header for packet classification purposes.

* In the Diffserv model, the marker marks a packet with a value that reflects a forwarding behavior. Marking is the process of placing a value in the packet's header to indicate how to forward the packet to the network. IPQoS contains two marker modules:

/ dscpmk – Marks the DS field in an IP packet header with a numeric value that is called the Differentiated Services codepoint, or DSCP. A Diffserv-aware router can then use the DS codepoint to apply the appropriate forwarding behavior to the packet.

/ dlcosmk – Marks the virtual local area network (VLAN) tag of an Ethernet frame header with a numeric value that is called the user priority. The user priority indicates the class of service (CoS), which defines the appropriate forwarding behavior to be applied to the datagram.

Note:

* Differentiated services or DiffServ is a computer networking architecture that specifies a simple, scalable and coarse-grained mechanism for classifying and managing network traffic and providing quality of service (QoS) on modern IP networks. DiffServ can, for example, be used to provide low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as web traffic or file transfers.

* IPQoS, included in Solaris, includes the following modules, which are part of the Differentiated Services (Diffserv) architecture that is defined in RFC 2475:

Classifier

Meter

Marker

IPQoS adds the following enhancements to the Diffserv model:

Flow-accounting module

802.1D datagram marker

URL: http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-118-s11-script-zones-524499.html