Patch Cluster and Patch Bundle


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Patch Cluster and Patch Bundle
# 1  
Old 01-19-2010
Patch Cluster and Patch Bundle

Patch Clusters and Patch Bundles are popular collections of patches providing specific functionality. They contain an install script for ease of installation. Patch Clusters and Patch Bundles are provided for the Solaris OS; Solaris, shared component, and middleware patches for Java Enterprise System; and Solaris patches recommended for J2SE.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Recommended patchset for Solaris and the patch bundle

Hello I recently downloaded and installed the latest patchset for Solaris 10 (update 5) running on SPARC. Actually I am new to Solaris (I come from Red Hat) and the security department asked me to update the system for security fixes. I logged in to Oracle support and used the recommended patch... (3 Replies)
Discussion started by: abohmeed
3 Replies

2. Solaris

Recommended Patch Cluster Using ZFS Snapshots

I have a question regarding installing recommended patch clusters via ZFS snapshots. Someone wrote a pretty good blog about it here: Initial Program Load: Live Upgrade to install the recommended patch cluster on a ZFS snapshot The person's article is similar to what I've done in the past. ... (0 Replies)
Discussion started by: christr
0 Replies

3. Solaris

Cannot mount Veritas volumes after cluster patch.

I am working with a Sun StoredgeTek 6540 disk array connected to two Sun 490 servers. After taking one of the 490 nodes on the cluster down to single user mode I proceeded to install the latest cluster patch from Oracle. After the patch was completed the system rebooted, failed to rejoin the... (2 Replies)
Discussion started by: buggin
2 Replies

4. Solaris

Jumpstart and Applying Recommended Patch Cluster

I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing. ... (0 Replies)
Discussion started by: christr
0 Replies

5. Solaris

Solaris patch cluster installation error

Hi Admins, I came across an error while installing patch cluster on solaris. # ./installcluster --s10cluster ERROR: Another instance of an install script is already running for target boot environment '/'. I did killed the related processes. Now there is no any process running from ps... (1 Reply)
Discussion started by: snchaudhari2
1 Replies

6. Solaris

Problem with patch bundle installation on Solairs 10

:mad: :mad: Hello, Could some help me to resolve why i am geting the below errors... :( Just tried installing patch bundle on solairs 10. many patches are been failed. wen i am trying to install it manualy i am geting the below errors.. ... (8 Replies)
Discussion started by: bullz26
8 Replies

7. Solaris

patch cluster question.

What if ,all of my patches in solaris10 05/08 there are not find following: 118731-01 122660-10 119254-59 138217-01 .... about 30 How i can fill up 30 patches? Do command patchadd separetely for everyone? Or make all patch cluster in S mode? Do it in global? I must stop zones befor patchadd... (0 Replies)
Discussion started by: sotich82
0 Replies

8. Solaris

Download patch cluster

Does anyone have an alternate site to download J2SE Solaris Recommended Patch Cluster for Solaris 8. Sun does not let me download the patches unless I have a support contract. I do not. Our software is legal, but our support contract wore out. I need this patchset to avoid downloading 30... (6 Replies)
Discussion started by: hshapiro
6 Replies

9. IP Networking

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down. I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies
Login or Register to Ask a Question
Monkey::Patch(3pm)					User Contributed Perl Documentation					Monkey::Patch(3pm)

NAME
Monkey::Patch - Scoped monkeypatching (you can at least play nice) VERSION
version 0.03 SYNOPSIS
use Monkey::Patch qw(:all); sub some_subroutine { my $pkg = patch_class 'Some::Class' => 'something' => sub { my $original = shift; say "Whee!"; $original->(@_); }; Some::Class->something(); # says Whee! and does whatever undef $pkg; Some::Class->something(); # no longer says Whee! my $obj = Some::Class->new; my $obj2 = Some::Class->new; my $whoah = patch_object $obj, 'twiddle' => sub { my $original = shift; my $self = shift; say "Whoah!"; $self->$original(@_); }; $obj->twiddle(); # says Whoah! $obj2->twiddle(); # doesn't $obj->twiddle() # still does undef $whoah; $obj->twiddle(); # but not any more SUBROUTINES
The following subroutines are available (either individually or via :all) patch_package (package, subname, code) Wraps "package"'s subroutine named <subname> with your <code>. Your code recieves the original subroutine as its first argument, followed by any arguments the subroutine would have normally gotten. You can always call the subroutine ref your received; if there was no subroutine by that name, the coderef will simply do nothing. patch_class (class, methodname, code) Just like "patch_package", except that the @ISA chain is walked when you try to call the original subroutine if there wasn't any subroutine by that name in the package. patch_object (object, methodname, code) Just like "patch_class", except that your code will only get called on the object you pass, not the entire class. HANDLES
All the "patch" functions return a handle object. As soon as you lose the value of the handle (by calling in void context, assigning over the variable, undeffing the variable, letting it go out of scope, etc), the monkey patch is unwrapped. You can stack monkeypatches and let go of the handles in any order; they obey a stack discipline, and the most recent valid monkeypatch will always be called. Calling the "original" argument to your wrapper routine will always call the next-most-recent monkeypatched version (or, the original subroutine, of course). BUGS
This magic is only faintly black, but mucking around with the symbol table is not for the faint of heart. Help make this module better by reporting any strange behavior that you see! perl v5.10.1 2010-07-16 Monkey::Patch(3pm)