Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 69 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

killproc



SYNOPSIS

       killproc  [-v]  [-q]  [-L] [-g|-G] [-p pid_file] [-c root]
       [-t<sec>] [-SIG] /full/path/to/executable

       killproc  [-v]  [-q]   [-g|-G]   [-n]   [-t<sec>]   [-SIG]
       name_of_kernel_thread

       killproc  [-v]  [-q]  [-g|-G]  [-n] [-t<sec>] [-SIG] base­
       name_of_executable

       killproc -l


DESCRIPTION

       killproc sends signals to all processes that use the spec­
       ified  executable.   If  no  signal name is specified, the
       signal SIGTERM is sent. If this program is not called with
       the  name  killproc  then  SIGHUP  is  used.  Note that if
       SIGTERM is used and does not terminate a process the  sig­
       nal SIGKILL is send after a few seconds (default is 5 sec­
       onds, see option -t).  If a program  has  been  terminated
       successfully  and  a verified pid file was found, this pid
       file will be removed  if  the  terminated  process  didn't
       already do so.

       killproc  does  not use the pid to send a signal to a pro­
       cess but the full path of the corresponding program  which
       is used to identify the executable (see proc(5)).  Only if
       inode number (/proc/<pid>/exe) and full path name  of  the
       executable (/proc/<pid>/cmdline) are unavailable or if the
       executable has changed its zeroth argument, killproc  uses
       the  base  name (/proc/<pid>/stat) to identify the running
       program. Note that if the option -n for kernel  thread  is
       given,  only (/proc/<pid>/stat) is used.  For this case an
       existing symbolic link  (/proc/<pid>/exe)  indicates  that
       the <pid> is not a kernel thread.

       The  last  variant  of  the killproc call is only with the
       basename of the executable.  This is required by the Linux
       Standard  Base  Specification  (LSB).  Note that this dis­
       ables the comparision of the inodes of the executable  and
       the information found within the proc table (see proc(5)).
       This implies that if no pid file is found it  may  happens
       that  programs  or  script  with  the  same base name will
       killed instead.  killproc tries to determine  the  pid  of
       its  parent  and pid of the parent of its parent to not to
       kill those two processes.

       Extended functionality is  provided  by  the  -p  pid_file
       option (former option -f changed due to the LSB specifica­
       tion).  If this option is  specified,  killproc  tries  to
       send  the signal to the pid read from this file instead of
       from the default pid file (/var/run/<basename>.pid).
              used, the name of the kernel thread. This  argument
              is always required.


OPTIONS

       -G     Sends  the  signal  to all session followers (chil­
              dren) of the identified process.

       -g     Sends the signal to  all  members  of  the  session
              including  the  identified process.  Note that usu­
              ally the option -G should be used.

       -L     This option causes symlinks to be followed, as  the
              like-named  option  in  ls(1).   Note: for the file
              name the original  name  of  the  program  is  used
              instead of the name of the symbolic link.

       -p pid_file
              (Former option -f changed due to the LSB specifica­
              tion.)  Use an alternate pid file  instead  of  the
              default (/var/run/<basename>.pid).

       -c root
              Change  root  directory  to root for services which
              have been started with this option by startproc(8).

       -n     This  option  indicates that a kernel thread should
              be signaled.  In this case not the executable  with
              its  full path name is required but the name of the
              kernel thread.

       -SIG   Signals  can be  specified  either  by  name  (e.g.
              -HUP, -SIGHUP) or by number (e.g. -1).

       -t<sec>
              The  number  <sec>  specifies  the  seconds to wait
              between the sent signal SIGTERM and the  subsequen­
              tially signal SIGKILL if the first SIGTERM does not
              show any result within the first few milli seconds.
              This defaults to 5 seconds.

       -q     This option is ignored.

       -v     Be more verbose.

       -l     This  option list all available signals and some of
              their synonyms by their number and signal names  to
              standard out.  and exits.


EXAMPLES

       killproc -TERM /usr/sbin/sendmail

              sends  the  signal  SIGTERM to the running sendmail
              no signal was specified and no  program  was  there
              for Termination because it is already terminated.


EXIT CODES

       The exit codes have the following LSB conform conditions:

               0    Success or program was not running (no signal
       specified)
              1    Generic or unspecified error
              2    Invalid or excess argument(s)
              4    Insufficient privilege(s)
              5    Program is not installed
              7    Program was not running to receive the  speci­
       fied signal

       In some error cases, diagnostic output is sent to standard
       error, or, if standard error is not available,  syslogd(8)
       is being used.


NOTE

       killproc  is  a  replacment  for the Bourne shell function
       killproc found in the  widely  used  SysVinit  package  of
       Miquel van Smoorenburg, <miquels@cistron.nl>.


BUGS

       Identifying a process based on the executable file and the
       corresponding inode number only works if the process stays
       alive during killproc's execution. Impure executables like
       shell scripts (the inode number of the shell is not  iden­
       tical  to that of the script) and programs rewriting their
       zeroth argument may not be identified by a file name.

       Killproc isn't able to signal processes being in the  zom­
       bie  state.  Zombies  are processes which  arn't alive but
       listed in the process table to have the exit status  ready
       for the corresponding parent processes.


FILES

       /proc/ path to the proc file system (see proc(5)).

       /etc/init.d/
              path to the SuSE boot concept script base directory
              as required by the Linux Standard  Base  Specifica­
              tion (LSB) (see init.d(7)).


SEE ALSO

       startproc(8),    checkproc(8),    insserv(8),   init.d(7),
       kill(1),  skill(1),  killall(8),  killall5(8),  signal(7),
       proc(5).


COPYRIGHT


  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds