Operating System - HP-UX
1833772 Members
2281 Online
110063 Solutions
New Discussion

easy 'cleanup' in HP-UX 11.0

 
SOLVED
Go to solution
Irine Gibilisco
Advisor

easy 'cleanup' in HP-UX 11.0

HP 9000/D370
HP-UX 11.0
Does anyone have a clean and simple script to replace the original functionality of the 'cleanup' utility, which existed in 10.20 and has all but disappeared in 11.0? All I want to do is remove all superseded patches installed on my machine.
UNIX is forever.
6 REPLIES 6
RikTytgat
Honored Contributor

Re: easy 'cleanup' in HP-UX 11.0

Hi,

This functionality is integrated in SD now. Just do a

swmodify -x patch_commit=true PHKL_1234

Hope this helps,
Rik.
Stefan Farrelly
Honored Contributor
Solution

Re: easy 'cleanup' in HP-UX 11.0


Take a look at this summary;

http://www.dutchworks.nl/htbin/hpsysadmin?h=3&dn=45007&q=cleanup%20for%2011&fh
Im from Palmerston North, New Zealand, but somehow ended up in London...
federico_3
Honored Contributor

Re: easy 'cleanup' in HP-UX 11.0

Cleanup utility exists even on version 11.00.

Do man cleanup.


federico
federico_3
Honored Contributor

Re: easy 'cleanup' in HP-UX 11.0

Cleanup utility exists even on version 11.00.

Do man cleanup.


federico
marc seguin
Regular Advisor

Re: easy 'cleanup' in HP-UX 11.0

The command swmodify with patch_commit=true option applies on filesets, not on products.

So, it gives something like :
swmodify -xpatch_commit=true PHSS_1234.*
Irine Gibilisco
Advisor

Re: easy 'cleanup' in HP-UX 11.0

To frederico: Thanks, but did you do the "man cleanup" on 11.0 or try running the "cleanup" utility there? It no longer does what you expect.

To Stefan Farelly and Sequin: Thanks, your recommendation is similar to what I understand from HP documentation... but I am still confused. Assuming that I get a list of superseded patches from "show_patches -s" command, do I then feed the list into the "swmodify" command? In that case, how does commiting of the superseded patches result in removal of their backups in the /var/adm/sw/save area? Wouldn't it instead remove the filesets that were saved prior to the superseded patch's application, thus making it impossible to ever go back To the original set up. It is almost as if I would want to 1) remove the superseding patch 2) remove the superseded patch 3) re-apply the superseding patch, to truly make things work. Am I making too much out of this?
UNIX is forever.