05-07-2009
Patching
Hi all
Ive got 12 odd sun servers, running solars 8, 9 and soon 10. Have to admit I havent patched for years. Infact the last time I did patch a load of servers, sun provided you will a small script which would review the current patch levels, create a xml file that you would use on sunsolve to create you a bundle of relative patches. This was back in 2002.
So, what do I do now ?? Looking at the kernel patch levels, most of these servers are well out of date.
Whats the correct method to use now to patch ? Do I just go onto sunsolve, download the latest kernel bundle for solaris 8 and install ?
Or do I try and taylor a patch bundle for my individual installation ??
Do Sun provide a small script to help me ?
Cheers
SBK
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
quick and question for the unix expert here
i downloaded the lastest patch from sun.
i'm ready to patch my production server. should i just patch it as is or go in to init 1 or init S to do the patching.
someone told me that you can just patch the server in init 3 and some other... (2 Replies)
Discussion started by: xNYx
2 Replies
2. Solaris
Hi all,
I'm new to Solaris. How can i make sure that all my servers are patched to the same level. When i do a uname -a, i see different level. How can i make sure that they are having the same patches. Any expert to guide me through pls?
eg.
ServerA#uname -a
SunOS ServerA 5.10... (0 Replies)
Discussion started by: ahlude
0 Replies
3. Solaris
Hi Gurus
I wanted to patch two servers yesterday with the SUN provided patch_cluster for solaris 10
One server is had the same patchlevel before and after patching
SunOS svr10008 5.10 Generic_125100-10 sun4v sparc SUNW,Sun-Fire-T200
The other had after the patching a different patchlevel... (3 Replies)
Discussion started by: gnom
3 Replies
4. Solaris
I know the smpatch utility has the set-uid 0 bit on it, so I'm wondering what privileges does it take to use this tool? I don't have to be root do I? How can I let a normal account do maintenance?
Thanks in advance. (4 Replies)
Discussion started by: solarisx86
4 Replies
5. Solaris
Hi All,
I have a question ? Which all patches need to be applied in single user mode and which all not .Is there any rule all patches need to be applied in /var/tmp.Thanks in advance for answers.:) (1 Reply)
Discussion started by: rama krishna
1 Replies
6. Solaris
HI Friends....
kindly explain os mirror patching?in SVM and Vxvm.
:wall: (1 Reply)
Discussion started by: Rajesh_Apple
1 Replies
7. Solaris
what are prerequisites or precautions we take before we install a patch in a zone.what if zone fails to boot after patching.How to recover form this situation.?
Thanks in advance..:) (1 Reply)
Discussion started by: ravijanjanam12
1 Replies
8. Solaris
OK, finally managed to get root access to the machines.
Now running
# uname -a
SunOS unknown 5.8 Generic_108528-22 sun4u sparc SUNW,UltraAX-e2
# showrev -p
Patch: 112668-01 Obsoletes: Requires: Incompatibles: Packages: SUNWgzip
Patch: 109889-01 Obsoletes: 109353-04 Requires: ... (2 Replies)
Discussion started by: Norman Khine
2 Replies
9. Red Hat
hello,
I'm a Solaris admin and I was asked to patch some RHEL servers. I'm having trouble trying to figure out the RHEL java version. Can someone help me?
This what I do in Solaris
java -version
java version "1.5.0_34"
java(TM) 2 Runtime Envirement, Standard Edition (build 1.5.0_34-b03)... (5 Replies)
Discussion started by: bitlord
5 Replies
10. Solaris
Greetings everyone! I have the task of patching six ldoms and two control domains. I have never done this before and would like to know of any pitfalls or "gotchas" I may encounter. I have been looking online but have found very little about patching ldoms. Thank you all. (4 Replies)
Discussion started by: desertdenizen
4 Replies
LEARN ABOUT DEBIAN
stg-sink
STG-SINK(1) StGit Manual STG-SINK(1)
NAME
stg-sink - Send patches deeper down the stack
SYNOPSIS
stg sink [-t <target patch>] [-n] [<patches>]
DESCRIPTION
This is the opposite operation of linkstg:float[]: move the specified patches down the stack. It is for example useful to group stable
patches near the bottom of the stack, where they are less likely to be impacted by the push of another patch, and from where they can be
more easily committed or pushed.
If no patch is specified on command-line, the current patch gets sunk. By default patches are sunk to the bottom of the stack, but the --to
option allows to place them under any applied patch.
Sinking internally involves popping all patches (or all patches including <target patch>), then pushing the patches to sink, and then
(unless --nopush is also given) pushing back into place the formerly-applied patches.
OPTIONS
-n, --nopush
Do not push back on the stack the formerly-applied patches. Only the patches to sink are pushed.
-t TARGET, --to TARGET
Specify a target patch to place the patches below, instead of sinking them to the bottom of the stack.
-k, --keep
Keep the local changes.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SINK(1)