Sponsored Content
Full Discussion: verify patch update
Special Forums UNIX and Linux Applications High Performance Computing verify patch update Post 302211881 by DukeNuke2 on Saturday 5th of July 2008 03:04:56 AM
Old 07-05-2008
no. only if the newer patch has some issues and a lower version is recommended until the problems are fixed.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to verify DST Update

Hello, Does anyone know how can I verify if the DST update on a SCO Unixware system has been installed successfully? UNIXWARE 7.1.4 MP3 Looking forward to some help, please.... Thanks (8 Replies)
Discussion started by: Yorgy
8 Replies

2. Solaris

patch update instructions

Hi All, I need to update my solaris with a particular patch. When reading the instruction on the sun web site, I got this: Installation Requirements: Reboot immediately after installing this patch on an active boot environment to bring the system to a consistent state. An alternative may... (8 Replies)
Discussion started by: itik
8 Replies

3. Solaris

patch update and break mirror

Hi All, How do you know if you need to break the mirror on solaris 8 patch update? Here's the patch example, 117350-54. On the site, it's just a low type update and not a medium or critical. Is breaking a mirror a best practice only or really a requirement to some patch? Thanks, itik (1 Reply)
Discussion started by: itik
1 Replies

4. Solaris

patch update with single user mode

Hi All, How do I execute patch update on a single user mode? Please give me the steps by step procedures? Is single user mode the same as run level 1? Thanks. (2 Replies)
Discussion started by: itik
2 Replies

5. Linux

kernel patch update how to

Hi All, I need to update my redhatas4 kernel with kernel-2.6.9-67.0.20.EL.src.rpm. When I run this # rpm -ivh kernel-2.6.9-67.0.20.EL.src.rpm warning: user brewbuilder does not exist - using root warning: group brewbuilder does not exist - using root warning: user brewbuilder does... (2 Replies)
Discussion started by: itik
2 Replies

6. High Performance Computing

veritas cluster with kernel patch update

hi all, can someone please share their process on how to kernel patch a red hat ent 4 with veritas cluster 5? it's compose of a primary and backup node. the resources are db, disk, nic. it doesn't need to be detail, just give me the steps like: login to the backup node and update the... (0 Replies)
Discussion started by: itik
0 Replies

7. Solaris

sendmail failed after patch update

Hi, I was troubleshooting H/W issue on a Ultra 5 workstation, whereby the system kept rebooting. In the course of isolating the issue, I patched the system with the latest Recommended cluster patch for solaris 7. SInce then, sendmail is not working and am getting the following errors. Kindly check... (6 Replies)
Discussion started by: incredible
6 Replies

8. Solaris

Update Solaris patch

Hi All I had update the solaris version, and now wish to update the patch. but when i check my patch version, i cant find any version for that. any idea? root@leo # showrev Hostname: leo Hostid: 839b58a3 Release: 5.10 Kernel architecture: sun4u Application architecture: sparc... (8 Replies)
Discussion started by: SmartAntz
8 Replies

9. Solaris

Solaris 10 10/09 (Update 8) Patch upgrade

Solaris 10 10/09 (Update 8) Patch upgrade can be done in single user mode? any suggestions.. thanks (2 Replies)
Discussion started by: chandravadrevu
2 Replies
SHAPE_PATCH(1)						      General Commands Manual						    SHAPE_PATCH(1)

NAME
shape_patch - shapeTools RMS generate patch file SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>] DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape patch from the top node of the central source repository creates a patch file for the whole system. The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH- FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output. Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure will leave an equally named patch file for each visited subsystem. The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1). INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit. SEE ALSO
shape_releas(1), vdiff(1), patch(1) FILES
<name1>+2+<name2>.pat 28.9.119 SHAPE_PATCH(1)
All times are GMT -4. The time now is 06:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy