Sponsored Content
Full Discussion: Patching
Operating Systems Solaris Patching Post 302323084 by pgarousi on Friday 5th of June 2009 10:37:19 AM
Old 06-05-2009
I can just imagine how irritating it must be to patch those servers, especially since they have not been patched for years.

Are you familiar with xVM Ops Center 2.1 by any chance? It's Sun new product which is great for patching and provisioning. It has an intelligent knowledge base and it makes the patching scalable and automated. You might want to take a look at it.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Patching Solaris

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

Patching

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

Patching error

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

Patching utility?

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

Solaris Patching.

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

Mirror patching

HI Friends.... kindly explain os mirror patching?in SVM and Vxvm. :wall: (1 Reply)
Discussion started by: Rajesh_Apple
1 Replies

7. Solaris

patching a zone.

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

patching solaris 8

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

Java patching

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

ldom patching

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
APPLYPATCH(1p)						User Contributed Perl Documentation					    APPLYPATCH(1p)

NAME
applypatch - apply 'makepatch' generated script to update a source tree SYNOPSIS
applypatch [ options ] patch-kit DESCRIPTION
Applypatch applies a patch kit as generated by the makepatch program. It performs the following actions: o First, it will extensively verify that the patch kit is complete and did not get corrupted during transfer. o Then it will apply some heuristics to verify that the directory in which the patch will be applied does indeed contain the expected sources. If a corruption or verification error is detected, applypatch exits without making changes. o If the kit is okay, and the directory seems to be the right one: it creates new files and directories as necessary. o Then it runs the patch program to apply the patch to the source files. o Upon completion, obsolete files, directories and .orig files are removed, file modes of new files are set, and the timestamps of all patched files are adjusted. Applypatch arguments Applypatch takes one argument, the name of the patch kit as generated by makepatch. If no name is specified, the patch kit is read from standard input. Applypatch options Options are matched case insensitive, and may be abbreviated to uniqueness. -directory dir The name of the source directory to be patched. -check Perform the checks on the patch kit and patch directory, but do not make any changes. -force Force continuation of the patch process even when corruption or verification errors are detected. This is very dangerous! -retain Do not remove patch backup files (with extension ".orig") upon completion. -patch cmd The patch command to be used. Default is ""patch -p0 -N"". Additionally, a ""-s"" will be added unless option -verbose was specified. -verbose This option will cause applypatch and the patch program to emit verbose progress information. -quiet This option will cause applypatch and the patch program to emit no progress information, only error messages. Environment variables SIMPLE_BACKUP_SUFFIX The suffix used by (some versions of?) patch to back up the originals of patched files. Upon completion, these files are removed by applypatch unless the option -retain was specified. Default value if "".orig"". SEE ALSO
makepatch(1), diff(1), patch(1), perl(1), rm(1). AUTHOR AND CREDITS
This program is written by Johan Vromans <jvromans@squirrel.nl>. See section AUTHOR AND CREDITS of the makepatch program for an extensive list of people that helped one way or another in the makepatch / applypatch project. COPYRIGHT AND DISCLAIMER
This program is Copyright 1992,1999,2006 by Squirrel Consultancy. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of either: a) the GNU General Public License as published by the Free Software Foundation; either version 1, or (at your option) any later version, or b) the "Artistic License" which comes with Perl. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public License or the Artistic License for more details. perl v5.10.0 2006-10-08 APPLYPATCH(1p)
All times are GMT -4. The time now is 08:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy