Questions and Answers
Amy Rich
Q When we first installed our Solaris 8 machines,
it seemed like 1G would be plenty of space for /var. However, we've gotten
to the point now where we need to delete logs early or we run out of disk space.
The biggest disk hog seems to be the /var/sadm directory, which claims
to hold package and patch information. Is there any way we can reclaim some
of this space for our log files?
A By default, the Solaris patching mechanism
creates backup copies of the packages replaced by the patch. Every time you
install a patch using patchadd, the current package is compressed into
a file called /var/sadm/pkg/<PKGNAME>/save/<PATCHNAME>/undo.Z.
If you install newer versions of the same patch, the undo.Z file in the
older version of the patch directory is renamed to obsolete.Z. Let's
say you've applied three different revisions of patch 117350, which replaces
the packages SUNWcsu, SUNWcsr, SUNWcarx, SUNWcar,
SUNWcsxu, and SUNWhea:
117350-12
117350-18
117350-25
You'll find the following save files under /var/sadm/pkg:
SIZE FILE NAME
20 SUNWcsu/save/117350-12/obsoleted_by
25947 SUNWcsu/save/117350-12/obsolete.Z
10 SUNWcsu/save/117350-18/obsoleted_by
26724 SUNWcsu/save/117350-18/obsolete.Z
28263 SUNWcsu/save/117350-25/undo.Z
20 SUNWcsr/save/117350-12/obsoleted_by
807215 SUNWcsr/save/117350-12/obsolete.Z
10 SUNWcsr/save/117350-18/obsoleted_by
819144 SUNWcsr/save/117350-18/obsolete.Z
820046 SUNWcsr/save/117350-25/undo.Z
20 SUNWcarx/save/117350-12/obsoleted_by
3035397 SUNWcarx/save/117350-12/obsolete.Z
|
