/var is full

[sassou]

I think the problem is due to patches
Please indicate me
how to Commit superseded patches.
Run cleanup on patches.
Thank u

[Patrick Wallek]

'man cleanup' should give you all the details.

To commit patches that have been superseded twice do:

# cleanup -c 2

To commit patches that have been superseded only 1 time do:

# cleanup -c 1

If you want to preview what action will be talken without actually do anything (probably a good idea) do:

# cleanup -p -c 2

[Rita C Workman]

To commit is: cleanup -c <# of superceded patches>
T
But there are other command options you could use to do some cleanup..so you might review the manpage for cleanup.

Rgrds,
Rita

[Jeff Schussele]

Hi,

You can verify just what's using the space with the following command:

du -akx /var | sort -nr | more

This will come sorted with the biggest dirs/files at the top.

And as Patrick stated, cleanup is the command to trim /var/adm/save. BUT get a backup of it first as you won't be able to roll back to a patch that's been committed - you'd have to restore first.

Rgds,
Jeff

[Geoff Wild]

I do a cleanup -c 1

also , check /var/adm/crash


Rgds...Geoff

[Steven E. Protter]

After you finish your cleanup, you might want to look at /var utilization.

If the cleanup gives you a good safety margin great, but if you are still in the 90% plus range, you may need to expand /var

If you have space and onlineJFS, you're all set. If not, you'll need to expand /var in single user mode.

SEP

[Dani Seely]

Hey Kuzo,
Try going to the root of /var and looking to see what directories are your largest space hogs. I usually use just 'du -s *' as root. This will give you the total size of all of the files and subdirectories in /var. From there you can see if it's an auditing issues (for us we have files under /var/audit), patch problem (again, for us it's /var/adm/patch), or logs (/var/logs, /var/adm/logs), etc. If your system isn't a secure or classified system, post the findings of your 'du'.

[MarkSyder]

If you're still short of space after running cleanup, check the following:

/var/adm/btmp
/var/adm/sulog
/var/adm/wtmp

If large you can null them (e.g. > /var/adm/btmp). Do NOT rm them.

/var/adm/cron/OLDlog
/var/adm/cron/log
/var/adm/lp/log
/var/adm/syslog/OLDsyslog.log
/var/adm/syslog/syslog.log (examine the contents first in case you have system problems you don't yet know about).

I hope this helps.

Mark Syder (like the drink but spelt different)