<?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: About the kill command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795144#M265641</link>
    <description>Note also that a kill signals just the specific process (assuming you are killing with a positive process ID). However, some processes are not independent so killing one process (regardless of the kill signal) may cause dependent processes to also terminate. For example, killing a parent of a process will also terminate the child process.</description>
    <pubDate>Fri, 26 May 2006 06:48:07 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2006-05-26T06:48:07Z</dc:date>
    <item>
      <title>About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795136#M265633</link>
      <description>I use the the command "kill -8" to kill the system process  , but I found that it will kill other processes simultaneously ( may be the -8 is too powerful ) , please suggest which parameter ( -1, -2 ... ) is lowest "power" to kill the process ? thx</description>
      <pubDate>Fri, 26 May 2006 03:14:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795136#M265633</guid>
      <dc:creator>nash11</dc:creator>
      <dc:date>2006-05-26T03:14:27Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795137#M265634</link>
      <description>man kill:&lt;BR /&gt;&lt;BR /&gt;   signum   signame   Name            Description&lt;BR /&gt;   ___________________________________________________________________________&lt;BR /&gt;      0     SIGNULL   Null            Check access to pid&lt;BR /&gt;      1     SIGHUP    Hangup          Terminate; can be trapped&lt;BR /&gt;      2     SIGINT    Interrupt       Terminate; can be trapped&lt;BR /&gt;      3     SIGQUIT   Quit            Terminate with core dump; can be trapped&lt;BR /&gt;      9     SIGKILL   Kill            Forced termination; cannot be trapped&lt;BR /&gt;     15     SIGTERM   Terminate       Terminate; can be trapped&lt;BR /&gt;     24     SIGSTOP   Stop            Pause the process; cannot be trapped&lt;BR /&gt;     25     SIGTSTP   Terminal stop   Pause the process; can be trapped&lt;BR /&gt;     26     SIGCONT   Continue        Run a stopped process&lt;BR /&gt;</description>
      <pubDate>Fri, 26 May 2006 03:23:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795137#M265634</guid>
      <dc:creator>Jannik</dc:creator>
      <dc:date>2006-05-26T03:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795138#M265635</link>
      <description>you can use kill without parameter to kill the process safely, it uses signal number as 15.</description>
      <pubDate>Fri, 26 May 2006 03:23:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795138#M265635</guid>
      <dc:creator>Kenan Erdey</dc:creator>
      <dc:date>2006-05-26T03:23:37Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795139#M265636</link>
      <description>Hi,&lt;BR /&gt;see:&lt;BR /&gt;man kill&lt;BR /&gt;&lt;BR /&gt;    0     SIGNULL   Null            Check access to pid&lt;BR /&gt;      1     SIGHUP    Hangup          Terminate; can be trapped&lt;BR /&gt;      2     SIGINT    Interrupt       Terminate; can be trapped&lt;BR /&gt;      3     SIGQUIT   Quit            Terminate with core dump; can be trapped&lt;BR /&gt;      9     SIGKILL   Kill            Forced termination; cannot be trapped&lt;BR /&gt;     15     SIGTERM   Terminate       Terminate; can be trapped&lt;BR /&gt;     24     SIGSTOP   Stop            Pause the process; cannot be trapped&lt;BR /&gt;     25     SIGTSTP   Terminal stop   Pause the process; can be trapped&lt;BR /&gt;     26     SIGCONT   Continue        Run a stopped process&lt;BR /&gt;If you kill a parent process this may trigger the kill on the attached processes.</description>
      <pubDate>Fri, 26 May 2006 03:24:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795139#M265636</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-05-26T03:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795140#M265637</link>
      <description>Sinal "8" (FPE) is surely not the right one to kill your process.&lt;BR /&gt;&lt;BR /&gt;First you should try simply&lt;BR /&gt;&lt;BR /&gt;# kill &lt;PID&gt;&lt;BR /&gt;&lt;BR /&gt;which is equivalent to "-15" SIGTERM. This gives your process the possibility to terminate gracefully.&lt;BR /&gt;&lt;BR /&gt;If this doesn't help, use&lt;BR /&gt;&lt;BR /&gt;# kill -9 &lt;PID&gt;&lt;BR /&gt;&lt;BR /&gt;kill command is used to send signals to processes, not only to "kill" them.&lt;BR /&gt;&lt;BR /&gt;see "man kill"&lt;/PID&gt;&lt;/PID&gt;</description>
      <pubDate>Fri, 26 May 2006 03:27:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795140#M265637</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2006-05-26T03:27:51Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795141#M265638</link>
      <description>Hi Nash, &lt;BR /&gt;&lt;BR /&gt;Floating Point Exception (FPE) is not a best way to kill a process. It will dump a core. &lt;BR /&gt;You can try with -15 or -9 with kill command, &lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Fri, 26 May 2006 03:34:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795141#M265638</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-05-26T03:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795142#M265639</link>
      <description>&lt;!--!*#--&gt;Hi:&lt;BR /&gt;&lt;BR /&gt;First, make usre that you isolate the process that you *really* want. Use the XPG4 (UNIX95) options of 'ps' achieves this. &lt;BR /&gt;&lt;BR /&gt;Never kill with 'kill -9' except as a last resort. A 'kill -9' cannot be ignored or trapped and it doesn't give a process any chance to clean up shared memory segments or remove temporary files.&lt;BR /&gt;&lt;BR /&gt;Instead, use a multi-level kill, starting with a hangup; then a simple 'kill -15'; and as a last resort a 'kill -9'.&lt;BR /&gt;&lt;BR /&gt;The following code accomplishs the above. If any level of killing succeeds, the script exits.  If there is any chance that you have multiple processes by the same name, this code accomodates that too.&lt;BR /&gt;&lt;BR /&gt;# cat .killer&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;myproc=`basename ${1}`&lt;BR /&gt;[ -z "${1}" ] &amp;amp;&amp;amp; { echo "no process specified!"; exit 1; }&lt;BR /&gt;mypid=`UNIX95= ps -C ${myproc} -o pid=`&lt;BR /&gt;if [ ! -z "${mypid}" ]; then&lt;BR /&gt;    kill -1 ${mypid} 2&amp;gt;/dev/null&lt;BR /&gt;    sleep 3&lt;BR /&gt;    kill -15 ${mypid} 2&amp;gt;/dev/null&lt;BR /&gt;    sleep 3&lt;BR /&gt;    kill -9 ${mypid} 2&amp;gt;/dev/null&lt;BR /&gt;fi&lt;BR /&gt;exit 0&lt;BR /&gt;&lt;BR /&gt;...You can see how this works by doing:&lt;BR /&gt;&lt;BR /&gt;# sleep 120 &amp;amp;&lt;BR /&gt;# ./killer sleep&lt;BR /&gt;&lt;BR /&gt;(or)&lt;BR /&gt;&lt;BR /&gt;# nohup /usr/bin/sleep 120 &amp;amp;&lt;BR /&gt;# ./killer sleep&lt;BR /&gt;&lt;BR /&gt;If you wish to integrate this into a subroutine in an existing script, change the 'exit' to a 'return' within the subroutine&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Fri, 26 May 2006 03:44:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795142#M265639</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-05-26T03:44:39Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795143#M265640</link>
      <description>The kill command sends a signal to each process specified by a pid&lt;BR /&gt;      process identifier.  The default signal is SIGTERM, which normally&lt;BR /&gt;      terminates processes that do not trap or ignore the signal.&lt;BR /&gt;&lt;BR /&gt;      pid is a process identifier, an unsigned or negative integer that can&lt;BR /&gt;      be one of the following:&lt;BR /&gt;&lt;BR /&gt;           &amp;gt; 0  The number of a process.&lt;BR /&gt;&lt;BR /&gt;           = 0  All processes, except special system processes, whose&lt;BR /&gt;                process group ID is equal to the process group ID of the&lt;BR /&gt;                sender.&lt;BR /&gt;&lt;BR /&gt;           =-1  All processes, except special system processes, if the user&lt;BR /&gt;                has appropriate privileges.  Otherwise, all processes,&lt;BR /&gt;                except special system processes, whose real or effective&lt;BR /&gt;                user ID is the same as the user ID of the sending process.&lt;BR /&gt;&lt;BR /&gt;           &amp;lt;-1  All processes, except special system processes, whose&lt;BR /&gt;                process group ID is equal to the absolute value of pid and&lt;BR /&gt;                whose real or effective user ID is the same as the user of&lt;BR /&gt;                the sending process.&lt;BR /&gt;&lt;BR /&gt;      Process numbers can be found with the ps command (see ps(1)) and with&lt;BR /&gt;      the built-in jobs command available in some shells.&lt;BR /&gt;&lt;BR /&gt;first try #kill &lt;PROCESS_ID&gt;&lt;BR /&gt;and then try #kill -9 &amp;gt;process_id&amp;gt;&lt;BR /&gt;but -9 will kill other dependency process.&lt;BR /&gt;&lt;BR /&gt;regards;&lt;BR /&gt;mustafa&lt;BR /&gt;&lt;/PROCESS_ID&gt;</description>
      <pubDate>Fri, 26 May 2006 04:01:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795143#M265640</guid>
      <dc:creator>Mustafa Gulercan</dc:creator>
      <dc:date>2006-05-26T04:01:18Z</dc:date>
    </item>
    <item>
      <title>Re: About the kill command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795144#M265641</link>
      <description>Note also that a kill signals just the specific process (assuming you are killing with a positive process ID). However, some processes are not independent so killing one process (regardless of the kill signal) may cause dependent processes to also terminate. For example, killing a parent of a process will also terminate the child process.</description>
      <pubDate>Fri, 26 May 2006 06:48:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-the-kill-command/m-p/3795144#M265641</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2006-05-26T06:48:07Z</dc:date>
    </item>
  </channel>
</rss>

