/var/adm/sw/save and cleanup

[Charles McCary]

group,

Hi - ran cleanup -c 1
### Cleanup program started at 07/11/02 11:01:07
Commit patches superseded at least 1 time(s) on 'lmxap03s'.
Obtaining superseded patch information...done.
No non-committed patches superseded at least 1 time(s) are present.
All information has been logged to /var/adm/cleanup.log.
### Cleanup program completed at 07/11/02 11:01:07

The output shows no patches...
However, there are still numerous patches in the save dir, it is my understanding that the save dir only contains superceded patches.

Any ideas?

tx,

c

[James R. Ferguson]

Hi Charles:

The concept is to have (and you do) the immediately prior version of a patch. You *want* to be able to roll-back (i.e. swremove and as a part of that removal, restore the prior state).

Regards!

...JRF...

[Charles McCary]

James,

thanks I was afraid that was the answer.

c

[S.K. Chan]

That's because you do not have any more patches in /var/adm/sw/save that were superseeded only once (since you use "-c 1"). The syntax ..

# cleanup -c <#-of-time-superseded>

[Sanjay_6]

Hi Charles,

Try this link,

http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000049452968

http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000050018528

Hope this helps.

Regds

[Martin Johnson]

cleanup gets rid of no longer needed patches. What you have left are patches that have been superceded but are needed in case of a rollback (i.e. swremove).

HTH
Marty

[Martin Johnson]

I have /var/adm/sw/save in its own file system. That way if I need more space, I can easily extend it (especially helpful on HFS only systems).

HTH
Marty