- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Microsoft
- >
- bash and whoami caused a 0 passwd file
Operating System - Microsoft
1753797
Members
8723
Online
108805
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО09-13-2005 07:25 AM
тАО09-13-2005 07:25 AM
bash and whoami caused a 0 passwd file
Superdome (SD32) running HP-UX 11.11 and user uses bash 2.05b for startup script. When they changed their password and did whoami the password file compressed to 0 and I think / filled up. I could only reboot to single user mode and take a copy of a backed up passwd file to get the partition active. Would what they did cause the / to fill or passwd file to compress to 0? I have a small /. /dev/vg00/lvol3 204800 189192 15608 92% /
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 09:26 AM
тАО09-13-2005 09:26 AM
Re: bash and whoami caused a 0 passwd file
It all depends on what is there in that scirpt which was executed.
Normally what happen if you try to backup the data to backup device which is not existing then entire data goes in to that file which resides under /dev which is part of your root.
Another reason would be somebody by mistake copied a huge file on root. You can use find command to locate the files with big sizes.
Regards,
Normally what happen if you try to backup the data to backup device which is not existing then entire data goes in to that file which resides under /dev which is part of your root.
Another reason would be somebody by mistake copied a huge file on root. You can use find command to locate the files with big sizes.
Regards,
You need to know a lot to actually know how little you know
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 09:26 AM
тАО09-14-2005 09:26 AM
Re: bash and whoami caused a 0 passwd file
You can use:
find / -xdev -type f -exec ls -la {} \; |sort +5 -nrb
find / -xdev -type f -ls |sort +6 -nrb
To find out if there is a bigfile out of place.
Are you sure that the passwd file was modified when you issued the whoami command?
find / -xdev -type f -exec ls -la {} \; |sort +5 -nrb
find / -xdev -type f -ls |sort +6 -nrb
To find out if there is a bigfile out of place.
Are you sure that the passwd file was modified when you issued the whoami command?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP