12-05-2010
Facing problem after upgrading the kernal patch level to 142900-12
I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in finding the patch for removing this bug.
10 More Discussions You Might Find Interesting
1. Solaris
Hi
I am getting the uptime output as follows
12:40am up 4 day(s), 18:29, 2 users, load average: 38.97, 36.54, 34.89
The load average is too high .
I have checked the processes , but no process is taking too much cpu time
Please help (3 Replies)
Discussion started by: guy009
3 Replies
2. Solaris
Hi,
how do you check that the latest service packs/patches are installed on the server, When i look at the OS Modules file, all i see is these numbers like 117176-02 etc, what is currently the latest patch level for sunOS 5.9?
thnaks (1 Reply)
Discussion started by: narik007
1 Replies
3. Solaris
As i understand, Patch is a fix to bug in a product.
What is patch level wrt to solaris OS ? How do i know the patch level of a machine ? I have task to compare patch levels of 2 machines running solaris (3 Replies)
Discussion started by: shafi2all
3 Replies
4. Solaris
required Solaris 5.10 Kernel patch 137111-03
required Solaris 5.10 Fibre Channel Device Driver patch 125184-08
I want to know about the descriptions and what the patches will do. I searched www.sun.com (patches/updates) but don't see I am looking for. (1 Reply)
Discussion started by: Y4Net
1 Replies
5. Linux
Hi
Do let me know how to find OS Patch 's installed on Linux server ?
Thanks
~ SPai (3 Replies)
Discussion started by: sbanala
3 Replies
6. AIX
Hi,
How to find out patch level in AIX and what patches are installed on AIX box?
As per my knowledge oslevel -s will give service and maintanance level description , but regarding patch level any command is there?
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. Solaris
how can i know the patch level in solaris 10?
is there a command to know what patchs installed in my solaris?
i mean is there any tool i can run to know that other than pkginfo | more?
i need to make an inventory of all my SUN servers.
i can run explorer in all the machines but unfortunately i... (3 Replies)
Discussion started by: q8devilish
3 Replies
8. AIX
Hi,
I am able to login using su - or su directly ,
# prompt is coming, it doesnt ask for password.
any normal user on aix system is login using su - or su .
Please suggest where to change the configuration
direct root login is disabled in /etc/ssh/sshd_config file. (0 Replies)
Discussion started by: manoj.solaris
0 Replies
9. Solaris
Hi,
Anyone able to advise on how to find the kernel patch level of an ABE?
showrev and uname -a will provide kernel patch details of the running environment, but how can I run these commands against the ABE or where do these commands get their information from i.e. is the kernel patch level... (3 Replies)
Discussion started by: CiCa
3 Replies
10. UNIX for Advanced & Expert Users
Hi,
All of our production servers are installed with Apache and OpenSSL from source and not yum.
My boss has assigned me with a task of upgrading all production servers Apache httpd & openssl to the latest patch from Centos Repo.
Is it possible to do this via yum? Please suggest the best... (10 Replies)
Discussion started by: anaigini45
10 Replies
LEARN ABOUT MOJAVE
cpanplus::hacking5.18
CPANPLUS::Hacking(3pm) Perl Programmers Reference Guide CPANPLUS::Hacking(3pm)
NAME
CPANPLUS::Hacking - developing CPANPLUS
DESCRIPTION
This document attempts to describe how to develop with the CPANPLUS environment most easily, how certain things work and why.
This is basically a quick-start guide to people who want to add features or patches to CPANPLUS.
OBTAINING CPANPLUS
Checkout CPANPLUS from its GIT repository at <https://github.com/jib/cpanplus-devel> .
INSTALLING CPANPLUS
CPANPLUS follows the standard perl module installation process:
perl Makefile.PL
make
make test
make install
CONFIGURING CPANPLUS
When running "perl Makefile.PL" you will be prompted to configure. If you have already done so, and merely wish to update the "Makefile",
simply run:
perl Makefile.PL JFDI=1
This will keep your configuration intact. Note however, if there are changes to the default configuration file "Config.pm-orig", you should
either delete your current config file and reconfigure, or patch your config file from the new entries in "Config.pm-orig".
RUNNING CPANPLUS FROM DEVELOPMENT ENVIRONMENT
If you'd rather not install the development version to your "site_perl" directory, that's no problem. You can set your "PERL5LIB"
environment variable to CPANPLUS' "lib" directory, and you can run it from there.
RUNNING CPANPLUS TESTS
Tests are what tells us if CPANPLUS is working. If a test is not working, try to run it explicitly like this:
perl -I/path/to/cpanplus/lib t/XX_name_of_test.t 1
The extra '1' makes sure that all the messages and errors (they might be errors we're testing for!) are being printed rather than kept
quiet. This is a great way to find out the context of any failures that may occur.
If you believe this test failure proves a bug in CPANPLUS, the long output of the test file is something we'd like to see alongside your
bug report.
FINDING BUGS
Sometimes you might find bugs in CPANPLUS' behaviour. If you encounter these in a development snapshot, we'd appreciate a complete patch
(as described below in the "SENDING PATCHES" section.
If it's way over your head, then of course reporting the bug is always better than not reporting it at all. Before you do so though, make
sure you have the latest development snapshot, and the bug still persists there. If so, report the bug to this address:
bug-cpanplus@rt.cpan.org
A good "patch" would have the following characteristics:
Problem description
Describe clearly what the bug is you found, and what it should have done instead.
Program demonstrating the bug
Show us how to reproduce the bug, in a simple of a program as possible
[OPTIONAL] A patch to the test suite to test for the bug
Amend our test suite by making sure this bug will be found in this, and future versions of CPANPLUS (see "SUPPLYING PATCHES")
[OPTIONAL] A patch to the code + tests + documentation
Fix the bug, update the docs & tests. That way your bug will be gone forever :)
SUPPLYING PATCHES
Patches are a good thing, and they are welcome. Especially if they fix bugs you've found along the way, or that others have reported.
We prefer patches in the following format:
o In "diff -u" or "diff -c" format
o From the root of the snapshot
o Including patches for code + tests + docs
o Sent per mail to bug-cpanplus@rt.cpan.org
o With subject containing "[PATCH]" + description of the patch
You will always be informed if a patch is applied or rejected, and in case of rejection why that is (perhaps you can tweak the patch to
have it accepted after all).
perl v5.18.2 2014-01-06 CPANPLUS::Hacking(3pm)