<?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: running application directory removed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019776#M299891</link>
    <description>You can't remove it.  Either you get text busy on the executable, or because that is your current directory.&lt;BR /&gt;&lt;BR /&gt;Of course if that directory is on the server and the application is being run over NFS, you may be able to remove it.  But you may get .nfs files that prevent the removal.</description>
    <pubDate>Thu, 14 Jun 2007 00:54:49 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2007-06-14T00:54:49Z</dc:date>
    <item>
      <title>running application directory removed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019775#M299890</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If an application is running and directory containing by it is removed by mistake by someone then will it become a zombie process ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Thu, 14 Jun 2007 00:34:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019775#M299890</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2007-06-14T00:34:24Z</dc:date>
    </item>
    <item>
      <title>Re: running application directory removed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019776#M299891</link>
      <description>You can't remove it.  Either you get text busy on the executable, or because that is your current directory.&lt;BR /&gt;&lt;BR /&gt;Of course if that directory is on the server and the application is being run over NFS, you may be able to remove it.  But you may get .nfs files that prevent the removal.</description>
      <pubDate>Thu, 14 Jun 2007 00:54:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019776#M299891</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-06-14T00:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: running application directory removed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019777#M299892</link>
      <description>Are there anymore opinions on this ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Sat, 16 Jun 2007 14:22:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019777#M299892</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2007-06-16T14:22:44Z</dc:date>
    </item>
    <item>
      <title>Re: running application directory removed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019778#M299893</link>
      <description>Hi Shiv:&lt;BR /&gt;&lt;BR /&gt;If you are referring to an inuse, executable file, then as Dennis has noted, you should not be able to remove the file.   Trying to do so should return a "text busy" error for the file.  Attempting to remove the directory housing the inuse, executable file should be denied, too, because (at least) one file in the directory can't be removed.&lt;BR /&gt;&lt;BR /&gt;Removing a file or directory referenced by a a running process will not cause the process to become a zombie.  At most, processes that do not already have files open will not be able to access the file(s) in question.&lt;BR /&gt;&lt;BR /&gt;A zombie process is only a remanent of a child process that has terminated but for whom its parent process has not (yet) "reaped" ['wait()'ed] to collect the child's exit status.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Sat, 16 Jun 2007 16:15:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019778#M299893</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2007-06-16T16:15:04Z</dc:date>
    </item>
    <item>
      <title>Re: running application directory removed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019779#M299894</link>
      <description>My answer would be: no, at least not directly.&lt;BR /&gt;&lt;BR /&gt;The only way a process becomes a zombie is when the process terminates and its parent process does not read its child's result code (by calling wait() on the child's PID number).&lt;BR /&gt;&lt;BR /&gt;As long as the application does not need to read anything from the removed files and the OS has no need to page in any code from the application binaries, the application can keep running just as before. &lt;BR /&gt;&lt;BR /&gt;The OS will protect the application binary and the associated libraries from deletion, unless NFS is involved. With NFS, this protection cannot be absolute. If there is no way to page in data from the binary or the libraries whenever it's needed, the program will certainly crash.&lt;BR /&gt;&lt;BR /&gt;Whenever you see zombie processes, look at the parent process (PPID) of the zombie: that process is not allowing the zombie to go its final rest, and needs to be fixed. The quick way to get rid of the zombies is to "kill that evil zombie master". &lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sat, 16 Jun 2007 16:33:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/running-application-directory-removed/m-p/4019779#M299894</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2007-06-16T16:33:16Z</dc:date>
    </item>
  </channel>
</rss>

