<?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 lsof stuck in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040725#M432844</link>
    <description>What/how does lsof work?  In trying to play around trying to identify Unidata user sessions and their port/pid correlation, I tried to do a lsof on one session via the "port" and the command has not returned going on now for 5 minutes.  Looking for lsof, I discovered my command along with another one w/o any arguments and a PPID of 1.&lt;BR /&gt;&lt;BR /&gt;Tried killing without and with -9 and yet the process prevails.</description>
    <pubDate>Tue, 17 Apr 2007 13:28:14 GMT</pubDate>
    <dc:creator>Raymond Wu - MTG</dc:creator>
    <dc:date>2007-04-17T13:28:14Z</dc:date>
    <item>
      <title>lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040725#M432844</link>
      <description>What/how does lsof work?  In trying to play around trying to identify Unidata user sessions and their port/pid correlation, I tried to do a lsof on one session via the "port" and the command has not returned going on now for 5 minutes.  Looking for lsof, I discovered my command along with another one w/o any arguments and a PPID of 1.&lt;BR /&gt;&lt;BR /&gt;Tried killing without and with -9 and yet the process prevails.</description>
      <pubDate>Tue, 17 Apr 2007 13:28:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040725#M432844</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T13:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040726#M432845</link>
      <description>what OS version do you have and also the lsof version you are running&lt;BR /&gt;&lt;BR /&gt;and did you run the lsof command as root? or a user?</description>
      <pubDate>Tue, 17 Apr 2007 13:31:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040726#M432845</guid>
      <dc:creator>Aussan</dc:creator>
      <dc:date>2007-04-17T13:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040727#M432846</link>
      <description>also the exact command used</description>
      <pubDate>Tue, 17 Apr 2007 13:33:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040727#M432846</guid>
      <dc:creator>Aussan</dc:creator>
      <dc:date>2007-04-17T13:33:33Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040728#M432847</link>
      <description>11.23 4.77 ran as root</description>
      <pubDate>Tue, 17 Apr 2007 13:34:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040728#M432847</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T13:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040729#M432848</link>
      <description>lsof -i :199</description>
      <pubDate>Tue, 17 Apr 2007 13:35:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040729#M432848</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T13:35:52Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040730#M432849</link>
      <description>was a typo - I had wanted to look at 1199 but inadvertently dropped off the trailing (or first 9).  Yeah, yeah â   lucky it wasnâ  t a kill or something else like that. 8-).</description>
      <pubDate>Tue, 17 Apr 2007 13:39:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040730#M432849</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T13:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040731#M432850</link>
      <description>try adding the protcol name (udp/tcp)&lt;BR /&gt;&lt;BR /&gt;# lsof -i tcp:1199</description>
      <pubDate>Tue, 17 Apr 2007 13:43:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040731#M432850</guid>
      <dc:creator>Robert-Jan Goossens_1</dc:creator>
      <dc:date>2007-04-17T13:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040732#M432851</link>
      <description>There are two sections of the lsof man page that you should have read BEFORE using lsof: "BLOCKS AND TIMEOUTS" and "AVOIDING KERNEL BLOCKS". Lsof is kernel intrusive and can certainly block on some operations but you are allowed to adjust timeouts and void potentially blocking system calls using the -b option.</description>
      <pubDate>Tue, 17 Apr 2007 13:43:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040732#M432851</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-04-17T13:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040733#M432852</link>
      <description>Okay, I have been educated as to the future use of lsof AND reading through the entire manpage of a command before trying it.  But what do I do now?  Do they effectively become zombies and need to wait for a reboot to clear them out?  Any potential harm - reason why I am asking is that the box hasn't been rebooted in almost 1/2 year and the people here frown on even thinking of rebooting....</description>
      <pubDate>Tue, 17 Apr 2007 13:54:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040733#M432852</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T13:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040734#M432853</link>
      <description>sorry i got confused a bit&lt;BR /&gt;&lt;BR /&gt;the command you are trying is lsof -i:1199 or lsof -l?&lt;BR /&gt;&lt;BR /&gt;and also can you do bdf on your system&lt;BR /&gt;&lt;BR /&gt;i know that sometime if i have a dead nfs mount bdf does not work, and lsof does not work also...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Apr 2007 13:58:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040734#M432853</guid>
      <dc:creator>Aussan</dc:creator>
      <dc:date>2007-04-17T13:58:49Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040735#M432854</link>
      <description>if it's a zombie process with ppid of 1 a reboot is the only way to clear it</description>
      <pubDate>Tue, 17 Apr 2007 14:01:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040735#M432854</guid>
      <dc:creator>Aussan</dc:creator>
      <dc:date>2007-04-17T14:01:38Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040736#M432855</link>
      <description>Aussan,&lt;BR /&gt;&lt;BR /&gt;No, no stuck unresolvable/unmountable mounts out there - bdf works.&lt;BR /&gt;&lt;BR /&gt;Killed the parent of the one I fired off;  the parent died but init inherited the surviving child now so there's two zombies.&lt;BR /&gt;&lt;BR /&gt;Oh well...&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Apr 2007 14:09:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040736#M432855</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T14:09:01Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040737#M432856</link>
      <description>Aussan,&lt;BR /&gt;&lt;BR /&gt;and the command was lsof -i :119 - was trying to find out who/what was running on 1199.</description>
      <pubDate>Tue, 17 Apr 2007 14:16:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040737#M432856</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T14:16:17Z</dc:date>
    </item>
    <item>
      <title>Re: lsof stuck</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040738#M432857</link>
      <description>chalking it up to just another learning experience.</description>
      <pubDate>Tue, 17 Apr 2007 14:57:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-stuck/m-p/5040738#M432857</guid>
      <dc:creator>Raymond Wu - MTG</dc:creator>
      <dc:date>2007-04-17T14:57:35Z</dc:date>
    </item>
  </channel>
</rss>

