<?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/tmp 100% in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656548#M47337</link>
    <description>Hi:&lt;BR /&gt;&lt;BR /&gt;There is no really good answer to this because it is considered the job of the programmer/script writer to be aware of available resources. Aside from regular cleanup scripts the best answer is to have a daemon which monitors all filesystems and then either sends messages via mail or better yet to a tool like IT/O or VP/O. Just to be fair, sometimes it's not the fault of the idiot programmer but rather the fault of the idiot admin who killed processes via kill -9 so that the temp files could not be removed.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 31 Jan 2002 18:31:12 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2002-01-31T18:31:12Z</dc:date>
    <item>
      <title>/var/tmp 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656545#M47334</link>
      <description>There a way to limit users from filling up /var/tmp?  Sometimes a process doesnt remove a tmp file from /var/tmp.</description>
      <pubDate>Thu, 31 Jan 2002 18:11:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656545#M47334</guid>
      <dc:creator>Philip J. Priest_1</dc:creator>
      <dc:date>2002-01-31T18:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: /var/tmp 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656546#M47335</link>
      <description>Hi Philip,&lt;BR /&gt;&lt;BR /&gt;You can have a cron job than can clean /var/tmp on a regular basis. Another choice is to redirect your user tmp files to another directory using the "TMPDIR" variable and then setting a quota on the directory size/growth. This willl restrict the user to the amount of space allocated by quota.&lt;BR /&gt;&lt;BR /&gt;Maybe some other forum member has a better suggestion.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Jan 2002 18:18:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656546#M47335</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-01-31T18:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: /var/tmp 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656547#M47336</link>
      <description>Philip, you could remove your users, then they wouldn't be able to fill up /var/tmp. As Sanjay said, you should put a cron in place to clean up the directory. Another good thing to do, is make /var/tmp it's own mount point, so that other processes that might write to /var/whatever won't be hammered by some process filling up /var/tmp.&lt;BR /&gt;&lt;BR /&gt;You could use quota's as Sanjay mentioned, but with that you will face performance overhead, and the possibility of hammering a real production process.&lt;BR /&gt;&lt;BR /&gt;If you can identify the processes (users) that are doing this nasty deed, then have a discussion with them about "housekeeping".&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Thu, 31 Jan 2002 18:25:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656547#M47336</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-01-31T18:25:34Z</dc:date>
    </item>
    <item>
      <title>Re: /var/tmp 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656548#M47337</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;There is no really good answer to this because it is considered the job of the programmer/script writer to be aware of available resources. Aside from regular cleanup scripts the best answer is to have a daemon which monitors all filesystems and then either sends messages via mail or better yet to a tool like IT/O or VP/O. Just to be fair, sometimes it's not the fault of the idiot programmer but rather the fault of the idiot admin who killed processes via kill -9 so that the temp files could not be removed.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Jan 2002 18:31:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656548#M47337</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-01-31T18:31:12Z</dc:date>
    </item>
    <item>
      <title>Re: /var/tmp 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656549#M47338</link>
      <description>Philip,&lt;BR /&gt;&lt;BR /&gt;I created the attached script and config file to make this task a little easier.  When I find a user process that doesn't cleanup well after itself, I make an entry in the "autocleanuup.conf" file.  I run the autocleanup.sh script once per week.&lt;BR /&gt;&lt;BR /&gt;Tom&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Jan 2002 18:50:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-tmp-100/m-p/2656549#M47338</guid>
      <dc:creator>Tom Dawson</dc:creator>
      <dc:date>2002-01-31T18:50:22Z</dc:date>
    </item>
  </channel>
</rss>

