<?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: fuser in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fuser/m-p/2517473#M23133</link>
    <description>Well let's think about it...&lt;BR /&gt;&lt;BR /&gt;Doing a kill on a PID (process) owned by the user...ok.&lt;BR /&gt;But since there could be same name processes being run by a number of users, how could you seperate this process from that by doing a fuser command.  It would kill all the processes matching, not just one PID.  That may be the issue.  And obviously, not knowing what child processes may be out there...could lead to alot of defunct processes.  &lt;BR /&gt;Generally, fuser is a command that is run by someone sitting higher (like root) who has the authority to clean up all parts of a process.&lt;BR /&gt;&lt;BR /&gt;Just a thought,&lt;BR /&gt;/rcw</description>
    <pubDate>Tue, 17 Apr 2001 13:08:42 GMT</pubDate>
    <dc:creator>Rita C Workman</dc:creator>
    <dc:date>2001-04-17T13:08:42Z</dc:date>
    <item>
      <title>fuser</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fuser/m-p/2517471#M23131</link>
      <description>Is there really a risk allowing everyone to run fuser?&lt;BR /&gt;&lt;BR /&gt;It appears that `fuser -kf filename` run by a non-privledged user isn't any different than allowing them to run `kill -9 filename`.  Where as they will only be allowed to kill PIDs owned by themselves.</description>
      <pubDate>Mon, 16 Apr 2001 21:59:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fuser/m-p/2517471#M23131</guid>
      <dc:creator>AFI HP-UX ADMIN</dc:creator>
      <dc:date>2001-04-16T21:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: fuser</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fuser/m-p/2517472#M23132</link>
      <description>No warnig if the user can't kill PID.</description>
      <pubDate>Mon, 16 Apr 2001 22:32:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fuser/m-p/2517472#M23132</guid>
      <dc:creator>Vincenzo Restuccia</dc:creator>
      <dc:date>2001-04-16T22:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: fuser</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fuser/m-p/2517473#M23133</link>
      <description>Well let's think about it...&lt;BR /&gt;&lt;BR /&gt;Doing a kill on a PID (process) owned by the user...ok.&lt;BR /&gt;But since there could be same name processes being run by a number of users, how could you seperate this process from that by doing a fuser command.  It would kill all the processes matching, not just one PID.  That may be the issue.  And obviously, not knowing what child processes may be out there...could lead to alot of defunct processes.  &lt;BR /&gt;Generally, fuser is a command that is run by someone sitting higher (like root) who has the authority to clean up all parts of a process.&lt;BR /&gt;&lt;BR /&gt;Just a thought,&lt;BR /&gt;/rcw</description>
      <pubDate>Tue, 17 Apr 2001 13:08:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fuser/m-p/2517473#M23133</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2001-04-17T13:08:42Z</dc:date>
    </item>
  </channel>
</rss>

