<?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: /var is full in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281304#M180466</link>
    <description>Hey Kuzo,&lt;BR /&gt;Try going to the root of /var and looking to see what directories are your largest space hogs.  I usually use just 'du -s *' as root.  This will give you the total size of all of the files and subdirectories in /var.  From there you can see if it's an auditing issues (for us we have files under /var/audit), patch problem (again, for us it's /var/adm/patch), or logs (/var/logs, /var/adm/logs), etc.  If your system isn't a secure or classified system, post the findings of your 'du'.</description>
    <pubDate>Wed, 19 May 2004 20:49:08 GMT</pubDate>
    <dc:creator>Dani Seely</dc:creator>
    <dc:date>2004-05-19T20:49:08Z</dc:date>
    <item>
      <title>/var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281298#M180460</link>
      <description>&lt;BR /&gt;I think the problem is due to patches &lt;BR /&gt;Please indicate me &lt;BR /&gt;how to Commit superseded patches.&lt;BR /&gt;Run cleanup on patches.&lt;BR /&gt;Thank u</description>
      <pubDate>Wed, 19 May 2004 14:35:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281298#M180460</guid>
      <dc:creator>sassou</dc:creator>
      <dc:date>2004-05-19T14:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: /var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281299#M180461</link>
      <description>'man cleanup' should give you all the details.&lt;BR /&gt;&lt;BR /&gt;To commit patches that have been superseded twice do:&lt;BR /&gt;&lt;BR /&gt;# cleanup -c 2&lt;BR /&gt;&lt;BR /&gt;To commit patches that have been superseded only 1 time do:&lt;BR /&gt;&lt;BR /&gt;# cleanup -c 1&lt;BR /&gt;&lt;BR /&gt;If you want to preview what action will be talken without actually do anything (probably a good idea) do:&lt;BR /&gt;&lt;BR /&gt;# cleanup -p -c 2</description>
      <pubDate>Wed, 19 May 2004 14:42:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281299#M180461</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2004-05-19T14:42:25Z</dc:date>
    </item>
    <item>
      <title>Re: /var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281300#M180462</link>
      <description>To commit is:  cleanup -c &amp;lt;# of superceded patches&amp;gt;&lt;BR /&gt;T&lt;BR /&gt;But there are other command options you could use to do some cleanup..so you might review the manpage for cleanup.&lt;BR /&gt;&lt;BR /&gt;Rgrds,&lt;BR /&gt;Rita&lt;BR /&gt;</description>
      <pubDate>Wed, 19 May 2004 14:43:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281300#M180462</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2004-05-19T14:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: /var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281301#M180463</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You can verify just what's using the space with the following command:&lt;BR /&gt;&lt;BR /&gt;du -akx /var | sort -nr | more&lt;BR /&gt;&lt;BR /&gt;This will come sorted with the biggest dirs/files at the top.&lt;BR /&gt;&lt;BR /&gt;And as Patrick stated, cleanup is the command to trim /var/adm/save. BUT get a backup of it first as you won't be able to roll back to a patch that's been committed - you'd have to restore first.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Wed, 19 May 2004 14:45:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281301#M180463</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2004-05-19T14:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: /var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281302#M180464</link>
      <description>I do a cleanup -c 1 &lt;BR /&gt;&lt;BR /&gt;also , check /var/adm/crash&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Wed, 19 May 2004 15:21:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281302#M180464</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2004-05-19T15:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: /var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281303#M180465</link>
      <description>After you finish your cleanup, you might want to look at /var utilization.&lt;BR /&gt;&lt;BR /&gt;If the cleanup gives you a good safety margin great, but if you are still in the 90% plus range, you may need to expand /var&lt;BR /&gt;&lt;BR /&gt;If you have space and onlineJFS, you're all set. If not, you'll need to expand /var in single user mode.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 19 May 2004 15:25:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281303#M180465</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-05-19T15:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: /var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281304#M180466</link>
      <description>Hey Kuzo,&lt;BR /&gt;Try going to the root of /var and looking to see what directories are your largest space hogs.  I usually use just 'du -s *' as root.  This will give you the total size of all of the files and subdirectories in /var.  From there you can see if it's an auditing issues (for us we have files under /var/audit), patch problem (again, for us it's /var/adm/patch), or logs (/var/logs, /var/adm/logs), etc.  If your system isn't a secure or classified system, post the findings of your 'du'.</description>
      <pubDate>Wed, 19 May 2004 20:49:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281304#M180466</guid>
      <dc:creator>Dani Seely</dc:creator>
      <dc:date>2004-05-19T20:49:08Z</dc:date>
    </item>
    <item>
      <title>Re: /var is full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281305#M180467</link>
      <description>If you're still short of space after running cleanup, check the following:&lt;BR /&gt;&lt;BR /&gt;/var/adm/btmp&lt;BR /&gt;/var/adm/sulog&lt;BR /&gt;/var/adm/wtmp&lt;BR /&gt;&lt;BR /&gt;If large you can null them (e.g. &amp;gt; /var/adm/btmp). Do NOT rm them.&lt;BR /&gt;&lt;BR /&gt;/var/adm/cron/OLDlog&lt;BR /&gt;/var/adm/cron/log&lt;BR /&gt;/var/adm/lp/log&lt;BR /&gt;/var/adm/syslog/OLDsyslog.log&lt;BR /&gt;/var/adm/syslog/syslog.log (examine the contents first in case you have system problems you don't yet know about).&lt;BR /&gt;&lt;BR /&gt;I hope this helps.&lt;BR /&gt;&lt;BR /&gt;Mark Syder (like the drink but spelt different)</description>
      <pubDate>Thu, 20 May 2004 02:19:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-is-full/m-p/3281305#M180467</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2004-05-20T02:19:30Z</dc:date>
    </item>
  </channel>
</rss>

