<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic bash and whoami caused a 0 passwd file in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/bash-and-whoami-caused-a-0-passwd-file/m-p/3625117#M6540</link>
    <description>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% /</description>
    <pubDate>Tue, 13 Sep 2005 14:25:07 GMT</pubDate>
    <dc:creator>trpjr1</dc:creator>
    <dc:date>2005-09-13T14:25:07Z</dc:date>
    <item>
      <title>bash and whoami caused a 0 passwd file</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/bash-and-whoami-caused-a-0-passwd-file/m-p/3625117#M6540</link>
      <description>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% /</description>
      <pubDate>Tue, 13 Sep 2005 14:25:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/bash-and-whoami-caused-a-0-passwd-file/m-p/3625117#M6540</guid>
      <dc:creator>trpjr1</dc:creator>
      <dc:date>2005-09-13T14:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: bash and whoami caused a 0 passwd file</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/bash-and-whoami-caused-a-0-passwd-file/m-p/3625118#M6541</link>
      <description>It all depends on what is there in that scirpt which was executed.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Sep 2005 16:26:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/bash-and-whoami-caused-a-0-passwd-file/m-p/3625118#M6541</guid>
      <dc:creator>Bharat Katkar</dc:creator>
      <dc:date>2005-09-13T16:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: bash and whoami caused a 0 passwd file</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/bash-and-whoami-caused-a-0-passwd-file/m-p/3625119#M6542</link>
      <description>You can use:&lt;BR /&gt;&lt;BR /&gt;find / -xdev -type f -exec ls -la {} \; |sort +5 -nrb&lt;BR /&gt;&lt;BR /&gt;find / -xdev -type f -ls |sort +6 -nrb&lt;BR /&gt;&lt;BR /&gt;To find out if there is a bigfile out of place.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Are you sure that the passwd file was modified when you issued the whoami command?</description>
      <pubDate>Wed, 14 Sep 2005 16:26:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/bash-and-whoami-caused-a-0-passwd-file/m-p/3625119#M6542</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-09-14T16:26:16Z</dc:date>
    </item>
  </channel>
</rss>

