<?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 Re: wtmp corrupted in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498233#M20409</link>
    <description>to read wtmp file,  that now seems to be corrupted ,do like this: &lt;BR /&gt;&lt;BR /&gt;the following will convert it to ASCII file &lt;BR /&gt;#/usr/sbin/acct/fwtmp &amp;lt; /var/adm/wtmp &amp;gt; /tmp/file &lt;BR /&gt;then you can either edit the file or read it. &lt;BR /&gt;&lt;BR /&gt;Then you can convert it back to binary form: &lt;BR /&gt;##/usr/sbin/acct/fwtmp -ic &amp;lt; /tmp/file &amp;gt; /var/adm/wtmp &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Bye &lt;BR /&gt;federico &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 26 Feb 2001 12:36:05 GMT</pubDate>
    <dc:creator>federico_3</dc:creator>
    <dc:date>2001-02-26T12:36:05Z</dc:date>
    <item>
      <title>wtmp corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498231#M20407</link>
      <description>When my /var is full, I release disk space but /var/adm/wtmp files remains corrupted (/usr/bin/last command dumps a core).&lt;BR /&gt;&lt;BR /&gt;I used wtmpfix but /usr/bin/last dumps on.&lt;BR /&gt;&lt;BR /&gt;I move wtmp to wtmp.old and create a new wtmp to log new logins. But wtmp.old is still corrupted.&lt;BR /&gt;&lt;BR /&gt;How to proceed to solve the wtmp corruption ?</description>
      <pubDate>Mon, 26 Feb 2001 11:56:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498231#M20407</guid>
      <dc:creator>Damian Benavent Pla</dc:creator>
      <dc:date>2001-02-26T11:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: wtmp corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498232#M20408</link>
      <description>Try moving it back from wtmp.old to wtmp (removing the version you created) and flush it with "cat /dev/null &amp;gt; /var/adm/wtmp"</description>
      <pubDate>Mon, 26 Feb 2001 12:24:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498232#M20408</guid>
      <dc:creator>Hakan Dedorson</dc:creator>
      <dc:date>2001-02-26T12:24:04Z</dc:date>
    </item>
    <item>
      <title>Re: wtmp corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498233#M20409</link>
      <description>to read wtmp file,  that now seems to be corrupted ,do like this: &lt;BR /&gt;&lt;BR /&gt;the following will convert it to ASCII file &lt;BR /&gt;#/usr/sbin/acct/fwtmp &amp;lt; /var/adm/wtmp &amp;gt; /tmp/file &lt;BR /&gt;then you can either edit the file or read it. &lt;BR /&gt;&lt;BR /&gt;Then you can convert it back to binary form: &lt;BR /&gt;##/usr/sbin/acct/fwtmp -ic &amp;lt; /tmp/file &amp;gt; /var/adm/wtmp &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Bye &lt;BR /&gt;federico &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 26 Feb 2001 12:36:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498233#M20409</guid>
      <dc:creator>federico_3</dc:creator>
      <dc:date>2001-02-26T12:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: wtmp corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498234#M20410</link>
      <description>Just a note about wtmp.  It can become corrupted if /var fills up or by programs that write to wtmp improperly.  First, I would lookk at how your system is used and consider breaking up /var into several different mountpoints. Each mountpoint will be used by a different subsystem of HP-UX and by separating them, one subsystem will not affect another (for example, spooling problems no longer affect email or logging):&lt;BR /&gt;&lt;BR /&gt;/var&lt;BR /&gt;/var/tmp&lt;BR /&gt;/var/mail&lt;BR /&gt;/var/spool&lt;BR /&gt;/var/adm&lt;BR /&gt;/var/adm/sw&lt;BR /&gt;&lt;BR /&gt;If you do not use email heavily, then the /var/mail directory can be a part of /var. Similarly, if spooling os limited to a few printers and not used for PC shares (where spool files can become gigantic), spooling can also be part of /var.  /var/adm/sw should always be made separate as it will grow quite large with patches and application updates.</description>
      <pubDate>Mon, 26 Feb 2001 12:57:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498234#M20410</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2001-02-26T12:57:26Z</dc:date>
    </item>
    <item>
      <title>Re: wtmp corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498235#M20411</link>
      <description>Hakan and Bill: My problem is how to recover that lost information.&lt;BR /&gt;&lt;BR /&gt;Thank you Federico. I knew that procedure.</description>
      <pubDate>Mon, 26 Feb 2001 13:45:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wtmp-corrupted/m-p/2498235#M20411</guid>
      <dc:creator>Damian Benavent Pla</dc:creator>
      <dc:date>2001-02-26T13:45:02Z</dc:date>
    </item>
  </channel>
</rss>

