09-11-2009
yes, if ur server do not connect to internet, then u need to install it manually and apply it to ur servers.. its really bothering me as well, but if it's possible try to open the access-list from your router to allow it download from the redhat networks for a while then close it again. actually there is no use to patch the server when the server is not connected to internet. it only will bring an disaster and screw the systems of your server which is currently working fine. stupid auditors or security team makes this thing happened.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone, I hope this is the right place to ask this question...
I have a contract to convert a mainframe/DB2 application to using AIX/Oracle. Everything went fine but we are now running into a terminal problem. With the Mainframe app, the clients had great response time from remote... (5 Replies)
Discussion started by: rocky_triton
5 Replies
2. UNIX for Advanced & Expert Users
I have a suse linux 9(SLES 9)
I have configured "YOU" (yast online update) and it all working fine, synchronising on a daily base with http://sdb.suse.de/download but I would like to know if they is a tools or scripts that inform you of any patches that has not been applied and notify you via... (0 Replies)
Discussion started by: hassan1
0 Replies
3. Linux
Does anyone know who to centrally manage the distribution and application of patches to multiple Linux platforms ? Is there software for this ? (0 Replies)
Discussion started by: jimthompson
0 Replies
4. Linux
I was wondering how everyone else manages patching/upgrades for apache.
Latest doesnt mean greatest, we typically dont install the newest patches for our OS's. We typically run 3-6 months behind, to let fixes get fixed before installing them.
Does anyone here have a written detailed plan... (0 Replies)
Discussion started by: Ikon
0 Replies
5. UNIX for Advanced & Expert Users
Does anyone know of any tools that manage the rollout of patches across multiple types of Unix platform ( eg Solaris, Aix etc ).
I am looking for something that does a similiar job to SMS or WSUS in the Windows world (3 Replies)
Discussion started by: jimthompson
3 Replies
6. Solaris
Hello Friends..
I have not tried anything related to Solaris patch and wish to learn more about it. I just wanted to try the patchadd and patchrm commands and how they work, just for educational purpose. I tried to download Solaris 10 patches, it asked me to register at sunsolve.com and i... (5 Replies)
Discussion started by: saagar
5 Replies
7. UNIX for Advanced & Expert Users
We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies
8. HP-UX
HI all,
As per the audit policy, patch has to be apply periodically, but in my scenerio, it has been applied lastly in the year 2010.
Using HP UX 11.11, 11.21 and 11.31
I would like to know, how to identify the patches which are need to update, what will be the procedure to update, how to... (5 Replies)
Discussion started by: selvaforum
5 Replies
9. Solaris
Hi Guys,
I am doing L1 Level support for Solaris Platform. Eg. User Management, File system , Print management and Job monitoring.
I recently completer my IBM Aix 7 Administration certification. Issue is that my manager is asking me do full time unix / linux patch management work for new... (5 Replies)
Discussion started by: Nats
5 Replies
LEARN ABOUT CENTOS
redhat-upgrade-tool
REDHAT-UPGRADE-TOOL(8) redhat-upgrade-tool User Manual REDHAT-UPGRADE-TOOL(8)
NAME
redhat-upgrade-tool - Red Hat Upgrade tool
SYNOPSIS
redhat-upgrade-tool [OPTIONS] SOURCE
DESCRIPTION
redhat-upgrade-tool is the Red Hat Upgrade tool.
The redhat-upgrade-tool client runs on the system to be upgraded. It determines what packages are needed for upgrade and gathers them from
the source(s) given. It also fetches and sets up the boot images needed to run the upgrade and sets up the system to perform the upgrade at
next boot.
The actual upgrade takes place when the system is rebooted, using the boot images set up by redhat-upgrade-tool. The upgrade initrd starts
the existing system (mostly) as normal, lets it mount all the local filesystems, then starts the upgrade.
When the upgrade finishes, it reboots the system into the newly-upgraded OS.
OPTIONS
Optional arguments
-h, --help
Show a help message and exit.
-v, --verbose
Print more info.
-d, --debug
Print lots of debugging info.
--debuglog DEBUGLOG
Write debugging output to the given file. Defaults to /var/log/redhat-upgrade-tool.log.
--reboot
Automatically reboot to start the upgrade when ready.
SOURCE
These options tell redhat-upgrade-tool where to look for the packages and boot images needed to run the upgrade. At least one of these
options is required.
--device [DEV]
Device or mountpoint of mounted install media. If DEV is omitted, redhat-upgrade-tool will scan all currently-mounted removable devices
(USB disks, optical media, etc.)
--iso ISO
Installation image file.
--network VERSION
Online repos matching VERSION (a number or "rawhide")
Multiple sources may be used, if desired.
Additional options for --network
--enablerepo REPOID
Enable one or more repos (wildcards allowed).
--disablerepo REPOID
Disable one or more repos (wildcards allowed).
--addrepo REPOID=[@]URL
Add the repo at URL. Prefix URL with @ to indicate that the URL is a mirrorlist.
--instrepo REPOID
Get upgrader boot images from the repo named REPOID. The repo must contain a valid .treeinfo file which points to the location of
usable kernel and upgrade images.
Cleanup commands
--resetbootloader
Remove any modifications made to bootloader configuration.
--clean
Clean up everything written by redhat-upgrade-tool.
EXAMPLES
redhat-upgrade-tool --network 7.0 --instrepo <repo URL>
Upgrade to RHEL 7.0 by downloading all needed packages and data from the specified repository.
redhat-upgrade-tool --device --network 7.0
Upgrade to RHEL 7.0 using install media mounted somewhere on the system, fetching updates from the network if needed.
EXIT STATUS
0
Success.
1
Cancelled by user, failure writing files to disk, or other unknown error
2
Failed to download/copy files from the given SOURCE
3
RPM upgrade transaction test failed
BUGS
The --iso image must be on a filesystem listed in /etc/fstab.
AUTHORS
Will Woods <wwoods@redhat.com>
redhat-upgrade-tool 11/08/2013 REDHAT-UPGRADE-TOOL(8)