Sponsored Content
Operating Systems Solaris What kind of steps should be followed while applying patch in real time? Post 302412896 by jlliagre on Tuesday 13th of April 2010 11:43:01 PM
Old 04-14-2010
Quote:
Originally Posted by garskoci
I prefer this method over something like live upgrade because I have control over what I'm doing.
I don't get that. You have control over what you are doing with live upgrade too. Your method is also inducing a service interruption time which might be unacceptable on a production system. Patching can take several hours to complete and live upgrade allows to do it while the system is running normally.
 

7 More Discussions You Might Find Interesting

1. Solaris

Applying Recommended Patch Cluster to Whole Root Zone

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

Shell script to convert epoch time to real time

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

Jumpstart and Applying Recommended Patch Cluster

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

Typical steps to be followed while applying an application patch upgrade on linux

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

Converting real time to epoch time

# 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

Recompile the kernel after applying a patch in 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

Applying patch for Samba version 4.1.17

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
lutab(4)																  lutab(4)

NAME
lutab - list of boot environments SYNOPSIS
/etc/lutab DESCRIPTION
The file /etc/lutab is a list of the boot environments (BEs) configured on a system. There are two entries for each BE. These entries have the following form: BE_id:BE_name:completion_flag:0 BE_id:root_slice:root_device:1 The fields in the lutab entries are described as follows: BE_id A unique, internally generated id for a BE. BE_name The user-assigned name of a BE. completion_flag Indicates whether the BE is complete (C) or incomplete (NC). A complete BE is one that is not involved in any copy or upgrade operation. A BE can be activated or compared only when it is complete. 0 Indicates first of two lines. BE_id As described above. root_slice Designation of the root slice. root_device Device on which the root slice is mounted. 1 Indicates second of two lines. The lutab file must not be edited by hand. Any user modification to this file will result in the incorrect operation of live upgrade. SEE ALSO
lu(1M), luactivate(1M), lucreate(1M), lucurr(1M), lufslist(1M), lustatus(1M), luupgrade(1M), attributes(5), live_upgrade(5) WARNINGS
The lutab file is not a public interface. The format and contents of lutab are subject to change. Use lufslist(1M) and lustatus(1M) to obtain information about BEs. SunOS 5.10 8 Jun 2001 lutab(4)
All times are GMT -4. The time now is 11:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy