10-14-2014
This is definitely not the route to go. However, here is another thought to think about.
This all depends on the time it takes you to roll your patches through your environment.
We have a 4 environment development strategy.
Dev - Test - QA (PreProd) - Prod
We actually patch our preprod environment first then we roll to prod, dev, test.
I know, sounds a little strange to do it this way but our development cycle is fairly rapid and our patching schedule is not as fast, so we have ran into issues with developing code on a newly patched DEV machine that wouldn't run in the other environments until they got patched. So we found that we patch the preprod systems first, if nothing breaks then roll it into prod, if it does break back out the patch or use the prod image to recover it.
Most of the time code developed on an OS with older patches ran just fine on the OS that is up-to-date on patches. I think I only had 2 instances in 5 years where that didn't happen and I believe that was because of java and a path change.
8 More Discussions You Might Find Interesting
1. 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
2. Virtualization and Cloud Computing
HPL-2008-80 Adaptive Information Technology for Service Lifecycle Management - Rolia, Jerry; Belrose, Guillaume; Brand, Klaus; Edwards, Nigel; Gmach, Daniel; Graupner, Sven; Kirschnick, Johannes; Stephenson, Bryan; Vickers, Paul; Wilcock, Lawrence
Keyword(s): Software as a Service, Enterprise... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. Solaris
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... (3 Replies)
Discussion started by: sbk1972
3 Replies
4. 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
5. Solaris
Hello to all, I have a quick question. I am learning Solaris, with Solaris 10 x86, and one of the chapters in the manual is about patching. So can I download free patches from the Sun page, I mean with out paying a license. Because It would be a great exercise to patch my installation of Solaris.... (1 Reply)
Discussion started by: piukeman
1 Replies
6. 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
7. 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
8. Homework & Coursework Questions
Hello,
I would like to build some sample C++ application on Solaris SunOS 5.8 Generic Virtual sun4v sparc.
so I would like to know what are the compilation utilities and runtime utilities I need to get in my machine
and will any one explain me the detaied life cycle of program like
what... (1 Reply)
Discussion started by: Revathi R
1 Replies
LEARN ABOUT CENTOS
splitdiff
SPLITDIFF(1) Man pages SPLITDIFF(1)
NAME
splitdiff - separate out incremental patches
SYNOPSIS
splitdiff [-a] [-d] [-p n] [-E] [file]
splitdiff {[--help] | [--version]}
DESCRIPTION
If you have a patch file composed of several incremental patches, you can use splitdiff to separate them out. You may want to do this in
preparation for re-combining them with combinediff(1).
The effect of running splitdiff is to separate its input into a set of output files, with no output file patching the same file more than
once.
OPTIONS
-a
Split out every single file-level patch.
-d
Create file names such as a_b.c.patch for a patch that modifies a/b.c.
-p n
Strip the first n components of the pathname to aid comparisons.
-E
Don't use .patch filename extension when writing output files.
--help
Display a short usage message.
--version
Display the version number of splitdiff.
SEE ALSO
combinediff(1), lsdiff(1)
AUTHOR
Tim Waugh <twaugh@redhat.com>
Package maintainer
patchutils 25 May 2011 SPLITDIFF(1)