Загрузить это руководство в формате PDF (4505 КБ)

luactivate(1M)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | OPERANDS | EXIT STATUS | FILES | ATTRIBUTES | SEE ALSO

NAME

luactivate– activate a boot environment

SYNOPSIS

/usr/sbin/luactivate [-l error_log] [-o outfile] [-s] [BE_name]

DESCRIPTION

The luactivate command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See live_upgrade(5) for a description of the Live Upgrade feature.

The luactivate command, with no arguments, displays the name of the boot environment (BE) that will be active upon the next reboot of the system. When an argument (a BE) is specified, luactivate activates the specified BE.

luactivate activates a BE by making the BE's root partition bootable. On an IA machine, this might require that you take steps following the completion of luactivate. If so, luactivate displays the correct steps to take.

To successfully activate a BE, that BE must meet the following conditions:

• The BE must have a status of “complete,” as reported by lustatus(1M).

• If the BE is not the current BE, you cannot have mounted the partitions of that BE (using lumount(1M) or mount(1M)).

• The BE you want to activate cannot be involved in an lucompare(1M) operation.

After activating a specified BE, luactivate displays the steps to be taken for fallback in case of any problem on the next reboot. Make note of these instructions and follow them exactly, if necessary.

The luactivate command requires root privileges.

OPTIONS

The luactivate command has the following options:

-l error_log

Error and status messages are sent to error_log, in addition to where they are sent in your current environment.

-o outfile

All command output is sent to outfile, in addition to where it is sent in your current environment.

-s

Forced synchronization. The first time you boot from a newly created BE, Live Upgrade software synchronizes this BE with the BE that was last active. (This is not necessarily the BE that was the source for the newly created BE.) It does not perform this synchronization after this initial boot, unless you use this option. Use this option with great caution, because you might not be aware or in control of changes that might have occurred in the last active BE.

OPERANDS

BE_name

Name of the BE to be activated.

EXIT STATUS

The following exit values are returned:

0

Successful completion.

>0

An error occurred.

FILES

/etc/lutab

list of BEs on the system

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWluu

SEE ALSO

lu(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludelete(1M), lufslist(1M), lumake(1M), lumount(1M), lurename(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | OPERANDS | EXIT STATUS | FILES | ATTRIBUTES | SEE ALSO