<?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: mailx uses /tmp in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481901#M798780</link>
    <description>Hi Kevin,&lt;BR /&gt;&lt;BR /&gt;It's possible to unlink() a file, yet keep it open, and continue to write to it:&lt;BR /&gt;&lt;BR /&gt;1)  The space the file uses isn't returned to the file system until the file is closed, usually when the process terminates.&lt;BR /&gt;&lt;BR /&gt;2) The file has no name, and thus, can't be seen with ls, ll, find, and so forth.&lt;BR /&gt;&lt;BR /&gt;3) This is commonly done with temporary files, so that if the system crashes while the file is open, there is not a file left laying around, taking up space.&lt;BR /&gt;&lt;BR /&gt;If you can run glance, or the 3rd party tool lsof, you should be able to see files that mailx has open, and I suspect you'll see that mailx does in fact have an inode open in /tmp, with no associated filename.&lt;BR /&gt;&lt;BR /&gt;Hope this is helpful to you,&lt;BR /&gt;Bruce Laughlin</description>
    <pubDate>Thu, 11 Jan 2001 19:30:41 GMT</pubDate>
    <dc:creator>Bruce Laughlin</dc:creator>
    <dc:date>2001-01-11T19:30:41Z</dc:date>
    <item>
      <title>mailx uses /tmp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481900#M798779</link>
      <description>i have noticed that mailx -f username somehow seems to 'take'space from the /tmp directory, however nothing is written to the /tmp dir. upon exit of the mailx program, a bdf returns to normal..what is happening and what other programs perform similar to mailx -f??&lt;BR /&gt;thank you</description>
      <pubDate>Thu, 11 Jan 2001 18:18:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481900#M798779</guid>
      <dc:creator>Kevin Wright</dc:creator>
      <dc:date>2001-01-11T18:18:33Z</dc:date>
    </item>
    <item>
      <title>Re: mailx uses /tmp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481901#M798780</link>
      <description>Hi Kevin,&lt;BR /&gt;&lt;BR /&gt;It's possible to unlink() a file, yet keep it open, and continue to write to it:&lt;BR /&gt;&lt;BR /&gt;1)  The space the file uses isn't returned to the file system until the file is closed, usually when the process terminates.&lt;BR /&gt;&lt;BR /&gt;2) The file has no name, and thus, can't be seen with ls, ll, find, and so forth.&lt;BR /&gt;&lt;BR /&gt;3) This is commonly done with temporary files, so that if the system crashes while the file is open, there is not a file left laying around, taking up space.&lt;BR /&gt;&lt;BR /&gt;If you can run glance, or the 3rd party tool lsof, you should be able to see files that mailx has open, and I suspect you'll see that mailx does in fact have an inode open in /tmp, with no associated filename.&lt;BR /&gt;&lt;BR /&gt;Hope this is helpful to you,&lt;BR /&gt;Bruce Laughlin</description>
      <pubDate>Thu, 11 Jan 2001 19:30:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481901#M798780</guid>
      <dc:creator>Bruce Laughlin</dc:creator>
      <dc:date>2001-01-11T19:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: mailx uses /tmp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481902#M798781</link>
      <description>More info...&lt;BR /&gt;&lt;BR /&gt;Here's an indication, using glance, that mailx has opened an inode in /tmp, with no associated filename:&lt;BR /&gt;&lt;BR /&gt;From the glance "open files" screen, for the mailx process:&lt;BR /&gt;4 &lt;REG&gt;&lt;BR /&gt;&lt;BR /&gt;Now, let's see if there is any such inode _viewable_ in the /tmp directory:&lt;BR /&gt;# cd /tmp&lt;BR /&gt;# ls -i | grep 241&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;Nope, nothing, so mailx has likely opened this file, unlinked it, and is using it as a temporary file.  When mailx closes the file, or terminates, the space used by this file will be returned to the filesystem.&lt;BR /&gt;&lt;BR /&gt;Also, you can get lsof at the following URL:&lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.51/" target="_blank"&gt;http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.51/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bruce Laughlin&lt;BR /&gt;&lt;/REG&gt;</description>
      <pubDate>Thu, 11 Jan 2001 19:38:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481902#M798781</guid>
      <dc:creator>Bruce Laughlin</dc:creator>
      <dc:date>2001-01-11T19:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: mailx uses /tmp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481903#M798782</link>
      <description>I have that lsof program, and i have tried it. This is kind of what I thought was happening, mailx just reserves space kindof, but your explanation clears it up for me, thank you.</description>
      <pubDate>Thu, 11 Jan 2001 19:43:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mailx-uses-tmp/m-p/2481903#M798782</guid>
      <dc:creator>Kevin Wright</dc:creator>
      <dc:date>2001-01-11T19:43:26Z</dc:date>
    </item>
  </channel>
</rss>

