- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cleanup command
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-06-2004 01:59 AM
тАО03-06-2004 01:59 AM
thank,
scott
Solved! Go to Solution.
- Tags:
- cleanup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-06-2004 03:29 AM
тАО03-06-2004 03:29 AM
SolutionFirst, check to see you've got the command (the fact that you don't have a man page concerns me) - ll /usr/sbin/cleanup.
Second, just entering the cleanup command will give you usage.
Third, what you probably want to run is "cleanup -c2" or maybe "cleanup -c1" (if you're really desparate). Make sure you have an adequate backup beforhand - make_tape_recovery would be perfect.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-06-2004 03:35 AM
тАО03-06-2004 03:35 AM
Re: cleanup command
I should add that you should probably check all the other normal /var offenders (but you knew this, right?). Check on log files with sam's "routine tasks". Look for large entries in /var with "du -sk /var/* |sort -n" (be careful about what you delete in here though - stay away from anything /var/adm/sw, for example). Most anything in /var/tmp should be eligible for deletion.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-06-2004 02:44 PM
тАО03-06-2004 02:44 PM
Re: cleanup command
Then survey /var for big directories:
du -kx /var | sort -rn | more
The directories at the top are the biggest. Just fix those as necessary.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-06-2004 06:06 PM
тАО03-06-2004 06:06 PM
Re: cleanup command
As mentioned, 'cleanup -c n' will removed the patches that got superceded 'n' times. If you are going with n <= 2, it is strongly recommended that you take a backup of your /var/adm/sw/save directory.
I would create /var/adm/sw/save as a seperate filesystem mounted from another volume group if I have. This is a static directory and is used when a patch is committed|removed.
Other major offenders in /var are /var/adm/syslog, /var/mail and /var/tmp. Check your /var/stm/logs directory also.
Or you can run 'du -ks /var |sort -n' to find them out.
-Sri