SunSolve Patches and Updates


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS SunSolve Patches and Updates
# 1  
Old 01-19-2010
SunSolve Patches and Updates

SunSolve resource for Patches and Updates for multiple Sun Products - including links to Patch Cluster and Patch Bundle Downloads, Earlier Solaris releases, and more.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. AIX

List of Installed patches for AIX from given set of patches

I need to find out list of installed patches from given list of patches. I have tried using instfix -f <File containing list of patches> -i -c But I was not able to understand the output of this command. It was like below. bos.perf.tools: :0.0.0.0:?: bos.rte.libc: :0.0.0.0:?: ... (4 Replies)
Discussion started by: Saurabh Agrawal
4 Replies

2. Solaris

Sunsolve like ;-)

Hello dear sysadmin, I've tried to created a great tools to help out every solaris sysadmin out there... A tool where you can find patches, bugs, and this in a quick way. Also a portal where you can see details about the patchlevel of your server, check if you've got the latest patch. check... (0 Replies)
Discussion started by: wildcat
0 Replies

3. Solaris

OS patches

Hi all, I am working on SUN-fire server solaris-10 How to find out what & how much " OS patches " installed on it?? plz help me out .:( (3 Replies)
Discussion started by: saurabh84g
3 Replies

4. Solaris

OS Patches

Hi all, We are planning to install Oracle 10g in the Sun Solaris 10 (64 bit Sun Sparc ). Can any one please tell me what are the OS level patches that has to be installed in the OS before starting installation of Oracle 10g. Thanks and Regards, Prashanth (1 Reply)
Discussion started by: prashanth_gs
1 Replies

5. AIX

unix updates- Where can I find unix updates online for IBM servers?

I have a Unix based server running Sagitta and the server is giving me an error of 4b10004 and my research tells me this is an EPROM issue, which means the processor needs to be flashed or repaired. Once up and running where can I go to get updates for Unix? (1 Reply)
Discussion started by: crainer
1 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)