Most Recent Oracle 1Z0-580 Exam Questions & Answers

How to Loopback Mount a File That Is Usually Not Visible in a Labeled Zone

This procedure enables a user in a specified labeled zone to view files that are not exported from the global zone by default.

1. Halt the zone whose configuration you want to change.

# zoneadm -z zone-name halt

2. Loopback mount a file or directory.

For example, enable ordinary users to view a file in the /etc directory.

# zonecfg -z zone-name

add filesystem

set special=/etc/filename

set directory=/etc/filename

set type=lofs

add options [ro,nodevices,nosetuid]

end

exit

Note - Certain files are not used by the system, so that loopback mounting them has no effect. For example, the /etc/dfs/dfstab file in a labeled zone is not checked by Trusted Extensions software. For more information, see Sharing Files From a Labeled Zone.

3. Start the zone.

# zoneadm -z zone-name boot

Note:

* In this Solaris release, you create a ZFS file system share and publish the share as follows:

Create the file system share and define the NFS or SMB share properties by using the zfs share command.

* ZFS File Sharing Within a Non-Global Zone

In previous Solaris releases, you could not create and publish NFS or SMB shares in a Oracle Solaris non-global zone. In this Solaris release, you can create and publish NFS shares by using the zfs set share command and the legacy share command with a non-global zone.

* If a ZFS file system is mounted and available in a non-global zone, it can be shared in that zone.

* A file system can be shared in the global zone if it is not mounted in a non-global zone or is not shared to a non-global zone.

* If a ZFS file system's mountpoint property set to legacy, the file system can be shared by using the legacy share command.

Note:

* sendmail

* Enabling Access to Remote Clients

On an unmodified system, access to sendmail by remote clients is enabled and disabled through the service management facility (see smf(5)). In particular, remote access is determined by the value of the local_only SMF property:

svc:/network/smtp:sendmail/config/local_only = true

A setting of true, as above, disallows remote access; false allows remote access. The default value is true.

The following example shows the sequence of SMF commands used to enable sendmail to allow access to remote systems:

# svccfg -s svc:/network/smtp:sendmail setprop config/local_only = false

# svcadm refresh svc:/network/smtp:sendmail

# svcadm restart svc:/network/smtp:sendmail

Note:

* In many cases, one software package depends on another package. For example, one package might require functionality that is in a second package in order to function or install correctly. These relationships, or dependencies, between packages are important for automating package installation operations and for upgrading system software to known and well-tested states. IPS supports a number of different relationships between packages.

Incorrect:

Not B: IPS relies on network-accessible or locally available software repositories as a delivery mechanism.

Not D:

Table, SVR4 and IPS Package Command Equivalents

SVR4 Package Command

IPS Package Command Equivalent

pkgadd

pkg install

patchadd

pkg update

pkgrm

pkg uninstall

pkgadm addcert, pkgadm removecert

pkg set-publisher -k, -c, --approve-ca-cert, --revoke-ca-cert, unset-ca-cert

pkginfo, pkgchk -l

pkg info, pkg list, pkg contents, pkg search

pkgchk

pkg verify, pkg fix, pkg revert

A: project.cpu-shares

Number of CPU shares granted to this project for use with the fair share scheduler

B: project.cpu-cap

Absolute limit on the amount of CPU resources that can be consumed by a project. A value of 100 means 100% of one CPU as the project.cpu-cap setting. A value of 125 is 125%, because 100% corresponds to one full CPU on the system when using CPU caps.

You can display information about snapshots, boot environments, and datasets that were created by the beadm command by using the beadm list subcommand. The beadm list command output also displays boot environments that are created by the pkg command.

The beadm list command syntax is:

Syntax: beadm list [-a | [-ds] [-H] [BeName]

The command lists information about the existing boot environment. To view information for a specific boot environment, replace BeName with a boot environment name. If a specific boot environment is not specified, the command lists information about all boot environments. The default is to list boot environments without additional information.

-a -- Lists all available information about the boot environment. This information includes subordinate datasets and snapshots.

-d -- Lists information about all subordinate datasets that belong to the boot environment.

-s -- Lists information about the snapshots of the boot environment.

-H -- Prevents listing header information. Each field in the output is separated by a semicolon.