<?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: lsof vs fuser in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094582#M49475</link>
    <description>thank you</description>
    <pubDate>Tue, 26 Feb 2008 21:55:54 GMT</pubDate>
    <dc:creator>chakri</dc:creator>
    <dc:date>2008-02-26T21:55:54Z</dc:date>
    <item>
      <title>lsof vs fuser</title>
      <link>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094580#M49473</link>
      <description>Which command is best to find if the file is still open?? lsof or fuser. which command will take more cpu??</description>
      <pubDate>Tue, 26 Feb 2008 20:32:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094580#M49473</guid>
      <dc:creator>chakri</dc:creator>
      <dc:date>2008-02-26T20:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: lsof vs fuser</title>
      <link>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094581#M49474</link>
      <description>&lt;!--!*#--&gt;About cpu usage for sure lsof, but is really great.&lt;BR /&gt;&lt;BR /&gt;Last time I had a problem with a file system near full. But if you do du over the file system, the information does not match. The problem was a file already deleted, but not released by the process.&lt;BR /&gt;&lt;BR /&gt;I have a "screenshow" of that!!!&lt;BR /&gt;&lt;BR /&gt;COMMAND     PID USER   FD   TYPE             DEVICE      SIZE  NODE NAME&lt;BR /&gt;java       7699  oas   22u   REG              253,1 856117248    59 /tmp/dat000407699 (deleted)&lt;BR /&gt;&lt;BR /&gt;800 MB in a "ghost" file was found with lsof.</description>
      <pubDate>Tue, 26 Feb 2008 20:40:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094581#M49474</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-02-26T20:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: lsof vs fuser</title>
      <link>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094582#M49475</link>
      <description>thank you</description>
      <pubDate>Tue, 26 Feb 2008 21:55:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094582#M49475</guid>
      <dc:creator>chakri</dc:creator>
      <dc:date>2008-02-26T21:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: lsof vs fuser</title>
      <link>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094583#M49476</link>
      <description>It depends on what information you want to get.&lt;BR /&gt;&lt;BR /&gt;As for how much CPU, we're talking milliseconds of difference in favour of fuser.&lt;BR /&gt;&lt;BR /&gt;Now, regarding usefulness, I'm an lsof fan, no question.&lt;BR /&gt;&lt;BR /&gt;But as I said, it depends on what information you want.</description>
      <pubDate>Tue, 26 Feb 2008 21:58:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094583#M49476</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2008-02-26T21:58:17Z</dc:date>
    </item>
    <item>
      <title>Re: lsof vs fuser</title>
      <link>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094584#M49477</link>
      <description>wow, who cares about the cpu usage of such a tool, unless you want to put it in cron and run it every 2 minutes it doesn't matter!</description>
      <pubDate>Wed, 27 Feb 2008 08:41:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/lsof-vs-fuser/m-p/5094584#M49477</guid>
      <dc:creator>dirk dierickx</dc:creator>
      <dc:date>2008-02-27T08:41:40Z</dc:date>
    </item>
  </channel>
</rss>

