Comitting patches

[Joe Profaizer]

I'm cleaning up /var on all my systems. 5 of 6 systems went well when comitting PHSS* patches. I'm getting an error on one system and I know for a fact there are numerous PHSS* when I run #ll /var/adm/sw/save PHSS*

The error follows and I don't quite understand it:

# swmodify -x patch_commit=true PHSS*
ERROR: The selected software to be committed was not modified. This
is probably the result of none of the selected software having
a patch fileset to commit.

There is at least 25 directories of PHSS*.

Thanks,

..Joe

[Steve Steel]

hi

You need to use this syntax:
# swmodify -x patch_commit=true PHSS_01111.*


Steve Steel

[Joe Profaizer]

I'll do that, but why? I used the syntax I indicated above for my other systems?

[Joe Profaizer]

I did the following command:
swmodify -x patch_commit=true PHSS*.*

Received many similar error messages and all the PHSS* entries have been removed.

ERROR: Cannot commit the patch fileset "PHSS_21283.X11R6-SHLIBS" in
the target "/" because its patch state is not "applied" or
"superseded".

Could this be due to creating this system from an ignite tape of another system? I've created systems from other system's ignite tapes, but didn't run into this commit problem.

Thanks!!

..Joe

[James R. Ferguson]

Hi Joe:

The 'cleanup' utility as originally released for 11.0 did now address space recovery in /var/adm/sw/save/ and as a consequence, one had to use 'swmodify' to commit patches and recover disk space.

If you download PHCO_24347 for 11.0 you will have a version of 'cleanup' that can manage superseded patches and recover disk space in lieu of using 'swmodify'.

There are man pages with the patch, but essentially you can choose the level which you commit patches superseded at least times:

# cleanup -c 1

This option is a front-end to the 'patch_commit' option of 'swmodify' that provides an easier interface to commit multiple patches at once.

Regards!

...JRF...

[James R. Ferguson]

Hi (again) Joe:

I happened to stumble on this (from the man pages for 'cleanup'). I think you will find it most interesting in light of your comments about how your server was built:

"The cleanup -s command can be executed to insure that the 'patch_state' attribute of all patch filesets is set correctly. There are several known situations where the 'patch_state' 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."

I would urge you to obtain and apply the current 'cleanup' patch (PHCO_24347) I suggested above, run 'cleanup -s' and then use 'cleanup -c [1|2]' in lieu of continuing to use the 'swmodify' method of committing patches.

Regards!

...JRF...