11-17-2011
Quote:
Originally Posted by
aksijain
here's the thing !
If I just change the grub.conf file and boot the server up with the old kernel will that solve my problem ?
This backout is needed since we are facing performance issues after the recent patch upgrade.
Any suggestions are much appreciated
Thanks in advance !
if the roll back is for the default kernel used then the above will solve your issue
Last edited by robo; 11-18-2011 at 03:15 AM..
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have 5 sub processes which are updating and commiting different records of a single table.I have a problem here.I want to rollback all the transaction if any one of processes fails.Can any one of you gurus suggest how to go about it ?
Thanks
Tushar Johri (3 Replies)
Discussion started by: tushar_johri
3 Replies
2. Red Hat
Hi all, :)
I'm quite new with installation of security patches in Linux Redhat Enterprise, here's my question.
I have 2 machine of this RHEL(never patch before) since it never connects directly to the internet(block by firewall) and I want to update the patches now because my boss asked me to... (2 Replies)
Discussion started by: flekzout
2 Replies
3. Solaris
What is the easiest or preferred way to roll back the solaris cluster patches?
My guess is to do a flash archive pre-patch and then install off of that if it doesn't work.
Any other ideas? (4 Replies)
Discussion started by: adelsin
4 Replies
4. Solaris
Is there an easy way to roll back or uninstall the latest Solaris patch cluster? I'm hoping I don't have to go into each patch that was applied and uninstall them one-by-one.
Thanks! (0 Replies)
Discussion started by: bluescreen
0 Replies
5. Red Hat
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies
6. Red Hat
Hi
Is there a direct way to apply a particular security advisory on the system.
Presently we have certain security advisories to be applied which require installation of multiple rpms and their dependencies.
These rpms as listed in the security advisory also mention that they have been... (0 Replies)
Discussion started by: Sapanvas
0 Replies
7. AIX
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
8. Shell Programming and Scripting
Hi
is there any shell script to roll back the code when the code is deployed in a wrong way in production servers (3 Replies)
Discussion started by: Purushotham
3 Replies
9. Red Hat
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies
10. Red Hat
Hello all, I am having a bit of an issue on my Spacewalk installation. Some amplifying information is that it is Spacewalk 2.3 installed on a RHEL 6 machine and I am attempting to install/update a RHEL 5 channel/repository. I am fairly new to Spacewalk so I am still learning but this is what I... (3 Replies)
Discussion started by: jstone4646
3 Replies
LEARN ABOUT DEBIAN
stg-sink
STG-SINK(1) StGit Manual STG-SINK(1)
NAME
stg-sink - Send patches deeper down the stack
SYNOPSIS
stg sink [-t <target patch>] [-n] [<patches>]
DESCRIPTION
This is the opposite operation of linkstg:float[]: move the specified patches down the stack. It is for example useful to group stable
patches near the bottom of the stack, where they are less likely to be impacted by the push of another patch, and from where they can be
more easily committed or pushed.
If no patch is specified on command-line, the current patch gets sunk. By default patches are sunk to the bottom of the stack, but the --to
option allows to place them under any applied patch.
Sinking internally involves popping all patches (or all patches including <target patch>), then pushing the patches to sink, and then
(unless --nopush is also given) pushing back into place the formerly-applied patches.
OPTIONS
-n, --nopush
Do not push back on the stack the formerly-applied patches. Only the patches to sink are pushed.
-t TARGET, --to TARGET
Specify a target patch to place the patches below, instead of sinking them to the bottom of the stack.
-k, --keep
Keep the local changes.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SINK(1)