04-14-2010
I don't question you choice, it is obviously up to you to choose the method you are more comfortable with. I was only commenting about the "control over what I'm doing point" which is questionable as Live Upgrade does provide at least the same level of control.
7 More Discussions You Might Find Interesting
1. Solaris
Hi there,
Apologies if this question has been asked and answered already but I've not been able to find the thread.
Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in... (3 Replies)
Discussion started by: nm146332
3 Replies
2. Shell Programming and Scripting
Dear experts,
I have an epoch time input file such as : -
1302451209564
1302483698948
1302485231072
1302490805383
1302519244700
1302492787481
1302505299145
1302506557022
1302532112140
1302501033105
1302511536485
1302512669550
I need the epoch time above to be converted into real... (4 Replies)
Discussion started by: aismann
4 Replies
3. Solaris
I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing.
... (0 Replies)
Discussion started by: christr
0 Replies
4. UNIX for Dummies Questions & Answers
what are the typical steps used by system adminstrators while applying an application patch upgrade (1 Reply)
Discussion started by: ramky79
1 Replies
5. Shell Programming and Scripting
# date +%s -d "Mon Feb 11 02:26:04"
1360567564
# perl -e 'print scalar localtime(1360567564), "\n";'
Mon Feb 11 02:26:04 2013
the epoch conversion is working fine. but one of my application needs 13 digit epoch time as input
1359453135154
rather than 10 digit epoch time 1360567564... (3 Replies)
Discussion started by: vivek d r
3 Replies
6. Ubuntu
I have applied a patch using this command:
patch -p1 < (file)
then I did git commit -a.
Now I want to recompile the kernel for making this patch live.
Should I use
make oldconfig
or
make localmodconfig
After that,
make -j$(grep -c "processor" /proc/cpuinfo)
sudo make... (1 Reply)
Discussion started by: BHASKAR JUPUDI
1 Replies
7. Debian
The version of Samba in our billing server is 4.1.17-Debian.
I have been reminded by our management to implement the patch for Samba on this server.
However, I am not sure how to implement the patch. I have browsed some websites for the correct patch to implement for Samba 4.1.17, and the patch... (11 Replies)
Discussion started by: anaigini45
11 Replies
lucurr(1M) lucurr(1M)
NAME
lucurr - display the name of the active boot environment
SYNOPSIS
/usr/sbin/lucurr [-l error_log] [-m mount_point] [-o outfile] [-X]
DESCRIPTION
The lucurr 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 lucurr command displays the name of the currently running boot environment (BE). If no BEs are configured on the system, lucurr dis-
plays the message "No Boot Environments are defined". Note that lucurr reports only the name of the current BE, not the BE that will be
active upon the next reboot. Use lustatus(1M) or luactivate(1M) for this information.
The lucurr command requires root privileges.
OPTIONS
The lucurr 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.
-m mount_point
Returns the name of the BE that owns mount_point, where mount_point is the mount point of a BE's root file system. This can be a mount
point of the current BE or the mount point of a BE other than the current BE. If the latter, the file system of the BE must have been
mounted with lumount(1M) or mount(1M) before entering this option.
-o outfile
All command output is sent to outfile, in addition to where it is sent in your current environment.
-X
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.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
FILES
/etc/lutab
list of BEs on the system
/usr/share/lib/xml/dtd/lu_cli.dtd.<num>
Live Upgrade DTD (see -X option)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWluu |
+-----------------------------+-----------------------------+
SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure-
name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)
SunOS 5.10 24 Jan 2002 lucurr(1M)