<?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: /tmp - mysterious hidden files? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396649#M200077</link>
    <description>The DATA Blocks of the FS assigned to /tmp  are not cleared immediately after use by the processes. Rather the inodes are reused as Clay mentioned. Thats the reason you see this. You wouldnt however notice this when the system is just rebooted :)&lt;BR /&gt;-Cheers&lt;BR /&gt;Govind</description>
    <pubDate>Fri, 08 Oct 2004 16:41:38 GMT</pubDate>
    <dc:creator>Govind_3</dc:creator>
    <dc:date>2004-10-08T16:41:38Z</dc:date>
    <item>
      <title>/tmp - mysterious hidden files?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396646#M200074</link>
      <description>what is using all the space in /tmp?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I'll admit I've limited UX experience, but what am I missing here? Or is my math just bad?&lt;BR /&gt;&lt;BR /&gt;Here's my /tmp FS with %used, blks free and blks total:&lt;BR /&gt;&lt;BR /&gt;/tmp      82%      142276     819200  &lt;BR /&gt;&lt;BR /&gt;and here is output from du&lt;BR /&gt;icgsil1:/tmp&amp;gt; du&lt;BR /&gt;0       ./lost+found&lt;BR /&gt;0       ./.opccfgmerge&lt;BR /&gt;4056    .&lt;BR /&gt;&lt;BR /&gt;and here is what's in /tmp:&lt;BR /&gt;icgsil1:/tmp&amp;gt; ll&lt;BR /&gt;total 2952&lt;BR /&gt;drwxr-xr-x   2 root       sys             96 Apr 19  2002 .opccfgmerge&lt;BR /&gt;-rw-rw-rw-   1 root       sys        1469558 Oct  8 14:36 JSPlog.txt&lt;BR /&gt;-rw-r--r--   1 root       root           102 Oct  8 12:06 btmp.out&lt;BR /&gt;-rw-r--r--   1 root       root             6 Oct  8 12:06 btmp.stat&lt;BR /&gt;-rw-r--r--   1 root       sys              0 Oct  7 19:14 iPlanetIcgs.out&lt;BR /&gt;-rw-rw-rw-   1 root       sys            331 Oct  8 14:34 icgsFtp.out&lt;BR /&gt;drwxr-xr-x   2 root       root            96 Apr 19  2002 lost+found&lt;BR /&gt;-rw-rw-rw-   1 root       sys            227 Oct  8 14:31 queueManager.log&lt;BR /&gt;-rw-rw-rw-   1 icgroute   icgs           130 Oct  8 14:18 receive.ksh.out&lt;BR /&gt;-rw-rw-rw-   1 root       sys           1454 Oct  6 11:00 web_tab.log&lt;BR /&gt;-rw-r--r--   1 root       root           525 Oct  8 14:35 wtmp.out&lt;BR /&gt;-rw-r--r--   1 root       root             7 Oct  8 14:35 wtmp.stat&lt;BR /&gt;icgsil1:/tmp&amp;gt; &lt;BR /&gt;&lt;BR /&gt;Thanks in advance!!!!!!!</description>
      <pubDate>Fri, 08 Oct 2004 14:38:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396646#M200074</guid>
      <dc:creator>Tim Killinger</dc:creator>
      <dc:date>2004-10-08T14:38:02Z</dc:date>
    </item>
    <item>
      <title>Re: /tmp - mysterious hidden files?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396647#M200075</link>
      <description>do&lt;BR /&gt;du -skx /tmp/* | sort -rn&lt;BR /&gt;&lt;BR /&gt;Anil</description>
      <pubDate>Fri, 08 Oct 2004 14:41:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396647#M200075</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2004-10-08T14:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: /tmp - mysterious hidden files?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396648#M200076</link>
      <description>UNIX has no hidden files; those that begin with "." are only "hidden" in the sense that ls by default doesn't display them. Almost certainly, you are dealing with files that have been unlinked (rm'ed) but not yet free. The space is not really freed until all processes which have the file open either close the file or terminate.&lt;BR /&gt;&lt;BR /&gt;One very common operation in the /tmp directory (although it should now be done by applications in /var/tmp) is to create a file, immediately unlink it, and then continue to use the file. Although there will not be a directory entry for this temporary file, it does exist and occupies space until closed. To get a good understanding of this, man 2 unlink.&lt;BR /&gt;&lt;BR /&gt;Generally the cure is to find the processes that have the files open and kill them. Lsof is a very good tool to help you find these files.&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Oct 2004 14:43:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396648#M200076</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-10-08T14:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: /tmp - mysterious hidden files?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396649#M200077</link>
      <description>The DATA Blocks of the FS assigned to /tmp  are not cleared immediately after use by the processes. Rather the inodes are reused as Clay mentioned. Thats the reason you see this. You wouldnt however notice this when the system is just rebooted :)&lt;BR /&gt;-Cheers&lt;BR /&gt;Govind</description>
      <pubDate>Fri, 08 Oct 2004 16:41:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tmp-mysterious-hidden-files/m-p/3396649#M200077</guid>
      <dc:creator>Govind_3</dc:creator>
      <dc:date>2004-10-08T16:41:38Z</dc:date>
    </item>
  </channel>
</rss>

