Get 1z0-822 Dumps : Verified Oracle Solaris 11 Advanced System Administration

create uses a default template of SYSdefault. The default template can be changed on a system-wide basis using the default_template SMF property of the svc:/system/zones:default service.

Note:

create [-F] [ -a path |-b | -t template]

Create an in-memory configuration for the specified zone. Use create to begin to configure a new zone

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

* policy.conf

policy.conf– configuration file for security policy.

The policy.conf file provides the security policy configuration for user-level attributes.

* Example: Modifying Every User's Basic Privilege Set

In this example, the security administrator of a large Sun Ray installation does not want regular users to view the processes of other Sun Ray users. Therefore, on every system that is configured with Trusted Extensions, the root role removes proc_info from the basic set of privileges. The PRIV_DEFAULT setting in the /etc/policy.conf file is uncommented and modified as follows:

PRIV_DEFAULT=basic,!proc_info

C: You cannot activate an unbootable BE in a nested BE.

BE solaris-1 is marked with !R.

Unbootable BEs inside of a nested BE are represented by an exclamation point (!)

BF: BE solaris-1 is marked with !R.

Unbootable BEs inside of a nested BE are represented by an exclamation point (!)

Incorrect:

Not A: BE1 can be activated. It is bootable (not marked with a !)

Not D: Different BEs can be used in the two zones.

Not E: BE solaris-1 is not marked with an N. The Active field indicates whether the boot environment is active now, represented by N

The ps command prints information about active processes.

Without options, ps prints information about processes asso-

ciated with the controlling terminal. The output contains

only the process ID, terminal identifier, cumulative execu-

tion time, and the command name. Otherwise, the information

that is displayed is controlled by the options.