10-19-2009
As already stated, some of the patches are freely available while other require a service contract. If you only want to experiment with patches and have no such contract, you can still do it by selecting security patches which are always available.
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. Solaris
I have to update on solaris 9. UPdating to 10 is not an option. Can I create a disk that will have all the updates/patches and just run it once and not sit and update one by one? If so, how? I have 10 Sun systems. (1 Reply)
Discussion started by: disturbe_d
1 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. Red Hat
I've inherited about 10 RHEL 3 boxes that are located in Europe behind a corporate firewall with no access to rhn.redhat.com
I've been tasked with patching all of these systems but I ask, Does redhat issue patch bundles? In AIX, there are maintenance levels and Sun has patch clusters available... (4 Replies)
Discussion started by: Steelysteel
4 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. Solaris
Hi, I installed Solaris 11 and I want to upgrade. I am doing this in by the documentation for pkg update. I read about the patch for solaris. Where and how to download and install this patch? (2 Replies)
Discussion started by: PtaQ
2 Replies
9. 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
10. 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
cleanup(1M) cleanup(1M)
NAME
cleanup - HP-UX patch cleanup utility
SYNOPSIS
DESCRIPTION
The command provides functions useful when dealing with HP-UX patches on HP-UX.
The command logs all information to
Options
recognizes the following options:
Preview the task but do not actually perform the requested action.
Notify the user of
tasks and request confirmation before performing the requested action.
Commit patches superseded at least
number times. This option is a front-end to the option of (see swmodify(1M)) that provides an easier interface to commit
multiple patches at once.
Remove patches in the specified software depot that have been superseded by
patches also available from the depot.
Specifies whether the software depot contains patches for HP-UX 10.X or 11.X
releases. This option is only valid with the option. If the option is not specified, it defaults to HP-UX 11.X patches.
Specifies whether patches in the software depot that contain a corequisite or
prerequisite attribute specifying one of the superseded patches as a dependency should also be removed. This option is valid
only with the option. If the option is not specified, it defaults to true.
Remove HP-UX 10.X patches that remain in the Installed Product Database
after an upgrade to HP-UX 11.X. These patches are removed from the IPD so that they are no longer displayed in the output of
the command (see swlist(1M)). The HP-UX 10.X patch files are also removed from
Correct the
attribute for HP-UX 11.X patches.
Recommendations
The command should be executed after updating to HP-UX 11.X from HP-UX 10.20. It is not necessary to execute after updating from one ver-
sion of HP-UX 11.X software to another because SD-UX will properly remove 11.X patch information from the IPD in these situations.
The command should be executed whenever patches are added to a software depot. It is not a requirement that superseded 11.X patches be
removed from a software depot, but it is a recommendation to conserve disk space and to avoid confusion. If superseded patches exist in
the same depot as patches that supersede them, SD-UX on HP-UX 11.X will handle the situation properly.
The command can be executed to commit all patches that have been superseded at least the specified number of times. The only benefit from
committing patches is that disk space will be recovered in the
The command can be executed to insure that the attribute of all patch filesets is set correctly. There are several known situations where
the attribute will be set incorrectly. This command can be run at any time, but will be most useful after a system has been installed
using Ignite-UX.
AVAILABILITY
This command is standard on HP-UX 11i v3. On 11i v2 it is available in patch PHCO_32220 or a superseding patch. On 11i v1 it is available
in patch PHCO_27780 or a superseding patch.
WARNINGS
Extreme care should be used when committing patches. Once a patch has been committed, it cannot be removed from the system. Patches
should only be committed when you are satisfied with their behavior. Recovering disk space should not be the only factor considered when
committing patches.
AUTHOR
was developed by HP.
SEE ALSO
show_patches(1), sysdiff(1), check_patches(1M), swlist(1M), swmodify(1M), swremove(1M), sd(4).
cleanup(1M)