Sun Microsystems, Inc.
spacer | | |  
black dot
A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z
System Administration Commandsluactivate(1M)


 luactivate - activate a boot environment


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



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 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.) "Synchronize" here means that certain system files and directories are copied from the last-active BE to the BE being booted. Live Upgrade software does not perform this synchronization after a BE's initial boot, unless you use the -s option, described below.

If luactivate detects conflicts between files that are subject to synchronization, it issues a warning and does not perform the synchronization for those files. Activation can complete successfully, in spite of such a conflict. A conflict can occur if you upgrade one BE or another to a new operating system version or if you modify system files (for example, /etc/passwd) on one of the BEs.

The luactivate command requires root privileges.



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.
Causes synchronization to occur (see DESCRIPTION) even if next boot of a specified BE is not the first boot of that BE. 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.

If using -s, take special care when booting to an earlier release of Solaris than what is installed on the last-active BE. For example, consider that the last-active BE contains Solaris 9 and you want to activate a BE that contains Solaris 2.6. If you forced synchronization with the -s option, the BE containing Solaris 2.6 might be synchronized with files that, while compatible with Solaris 9, might not work under Solaris 2.6.

Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version number of the DTD file.


Name of the BE to be activated.



The following exit values are returned:

Successful completion.
An error occurred.


list of BEs on the system
Live Upgrade DTD (see -X option)



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




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

SunOS 5.9Go To TopLast Changed 24 Jan 2002

Copyright 2002 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.