Sponsored Content
Full Discussion: Patching Solaris
Top Forums UNIX for Dummies Questions & Answers Patching Solaris Post 20866 by manderson19 on Monday 6th of May 2002 03:27:24 PM
Old 05-06-2002
Bug

either way, make sure you do it when the least amount of people are accessing your server (after business hours). that way, if something goes wrond you have all night to fix it
 

8 More Discussions You Might Find Interesting

1. Solaris

Solaris patching info

SOLUTION: You'll want to download the Solaris patches from: http://sunsolve.sun.com/show.do?target=home - get yourself an account, and you'll want to at least download the 'Sun Alert Patch Cluster' for your OS, as well as the 'Recommended' patch archive, which usually has a generic title like... (2 Replies)
Discussion started by: b1f30
2 Replies

2. Solaris

Solaris 10 patching - 14 hours!!!

Hi, we have a problem recently with Sun Fire T200 server, when installing 10_SPARC_EIS-Jul09 patchbundle resulted for 14 hours of outage! Steps, that was done by me is pretty straightforward: reboot -- -s ./installcluster --s10cluster Then I made 1 reboot after kernel patch was installed... (10 Replies)
Discussion started by: masloff
10 Replies

3. Solaris

Patching Solaris 10

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

4. Solaris

Regarding Solaris patching..

Hi Gurus, I am new to solaris patching.. while doing the patching do we need to have the root previligies and also need help while doing patching work if the server has veritas on it........ Thanks in advance.......... (10 Replies)
Discussion started by: samanth009
10 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

Solaris Patching vs OS Upgrade

Hello, I have a doubt regarding patching and OS upgrade. What is the difference when i install a Recomended Patch Cluster using installcluster script on a solaris10 update 6 server vs Upgrading Solaris 10 update 6 to update 10 ? I have applied update10 Recomended Patch Cluster on a... (1 Reply)
Discussion started by: fugitive
1 Replies

7. 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

8. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 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 04:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy