- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: /usr/adm/ directory ..
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
Forums
Discussions
Discussions
Discussions
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
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
04-15-2002 01:25 PM
04-15-2002 01:25 PM
I had a full filesytem issue and noticed that that I have a /usr/adm directory. It look like /var/adm and I had a huge wtmp file in /usr/adm
40034820 Apr 15 16:04 wtmp
Now I have realized that /usr/adm is linked to /var/adm. But the changes that were made in /var/adm did not take for /usr/adm since /var/adm is just fine.
Can someone tell me a little more about why /usr/adm is linked to /var/adm.
And why the link seems to be broken and how to fix it.
ll -d /usr/adm
lrwxr-xr-t 1 root sys 8 Nov 20 2000 /usr/adm -> /var/adm
bdf still shows to be 100% even after moving the huge wtmp file that should have freed up some space.
Any ideas on that?
Besides rebooting the server to kill runaways running from /usr. If I have to reboot so be it.
Thanks,
Richard
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 01:30 PM
04-15-2002 01:30 PM
Re: /usr/adm/ directory ..
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 01:37 PM
04-15-2002 01:37 PM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 04:41 PM
04-15-2002 04:41 PM
Re: /usr/adm/ directory ..
You might find this "old" paper provides some more insight. History, after all, is a valuable teacher. The white paper appeared around the introduction of HP-UX 10.x:
http://www.software.hp.com/HPUX-RDMP/history/slide2.html
http://docs.hp.com/hpux/onlinedocs/5963-8942/5963-8942.html
As always, it is better (both for speed and for future compatability) to use a direct reference rather than a transition link.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 07:02 PM
04-15-2002 07:02 PM
Re: /usr/adm/ directory ..
Note that transition links should NOT be relied on--they may disappear in the future. Or a sysadmin might remove them with the tlremove command.
The reason that wtmp did not shrink was that it was still open by several processes. Since this file is constantly growing, you need to copy it if needed for record-keeping, then aero out the size of the file with something like:
cat /dev/null > /var/adm/wtmp
There are many other files in /var/adm that will grow without bounds. Use this command to sort the files by size:
ls -l | sort -rnk5 | more
Use cron to automatically trim logfile.
Bill Hassell, sysadmin