ckill man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

ckill(1)							      ckill(1)

       ckill  -	 Displays or kills named processes on multiple hosts in paral‐
       lel. ckill is part of the Distributed Systems Administration  Utilities

       [command fanout options] [kill options] processname

       {-h | --help | -?}

       {-V | --version}

       ckill,  in parallel, displays or kills processes on multiple hosts.  In
       a Serviceguard cluster, displays or kills the  named  process  cluster-
       wide by default.	 When not in a Serviceguard cluster, defaults to issu‐
       ing commands on the local host.	To kill a process, specify  a  process
       name  (ckill  does not accept a numeric PID to kill a process).	If the
       process name is specified with  a  path,	 ckill	kills  processes  that
       exactly match the specified process name.  If just a basename is speci‐
       fied, ckill kills all processes with a matching basename.  See EXAMPLES
       for more details.

       Select  how  ckill  connects  to target systems at runtime using the -R
       option.	ssh is the default transport.	The  following	protocols  are

	      ·	 rsh  :	 Uses  an  internal, thread-safe implementation of BSD
		 rcmd(3) to run commands using the standard rsh(1) protocol.

	      ·	 ssh (default): Uses a variant of  popen(3)  to	 run  multiple
		 copies of the ssh(1) command.

       -a	 cexec	reads  the  /etc/machines  file	 to obtain the list of
		 nodes.	  This	option	has  no	 arguments.   Note  that   the
		 /etc/machines	file is not shipped by default and can be cre‐
		 ated on each host.  The format for the /etc/machines file  is
		 the same as that for the hostsfile described below.

       -f | --hostsfile filename
		 Runs  the  command on all hosts listed in the specified file.
		 The file must contain a list of target	 hosts,	 one  hostname
		 per  line.   Hostlist	expressions  are  valid;  see HOSTLIST

       -n | -w | --nodes host1,host2,...
		 Target the specified list of hosts.  No spaces are allowed in
		 the  comma-separated list.  The host list may contain expres‐
		 sions of the  form  ``host[1-5,7]''.	For  more  information
		 about	the hostlist format, see the HOSTLIST EXPRESSIONS sec‐
		 tion below.  This option overrides all other host  specifica‐
		 tion options.

       --fanout number
		 Set  the  maximum  number  of simultaneous remote commands to

       -h | --help
		 Display command help and quit.

       -l | --list
		 List valid signal names.

       -R | --rcmd  {rsh | ssh}
		 Set remote command transport to or .

       -s signame | -s signum
		 Kill using signal name (signame) or signal number (signum).

       -signame | -signum
		 Obsolescent.  Kill using signal name (signame) or signal num‐
		 ber (signum).

       -t | --timeout seconds
		 Set the connect timeout.

       -u | --ctime seconds
		 Set a limit on the amount of time a remote command is allowed
		 to execute.  Default is no limit.

       -U username
		 Consider processname only when owned by username.

       --user username
		 Execute remote commands as username.

       -v | --verify processname
		 List processes with  the  specified  process  name.   If  the
		 process is specified with a path, an exact match is required.
		 If the process is specified as a name (for example,  a	 base‐
		 name), then all processes with that basename are matched.

       -V | --version
		 Shows the version of ckill.

       -x | --exclude host1,host2,...
		 Exclude the specified hosts.


       On  non-Serviceguard  clusters,	if  no	other node selection option is
       used, the CFANOUT_HOSTS environment variable may be set to  a  filename
       from  which  a  list  of target hosts is read.  The file must contain a
       list of hosts, one per line.

       When using the ssh transport, password-less ssh must have already  been
       configured between the source and destination hosts.  will not interac‐
       tively prompt for passwords.  Use the tool to help you configure	 pass‐
       word-less  ssh.	 Similarly,  when  using rsh, the .rhosts files on the
       nodes  must  be	properly  configured.	The  connect  timeout  is  not
       adjustable when using ssh.

       The  number  of	nodes on which ckill can simultaneously execute remote
       jobs is limited by the maximum number of threads that  can  be  created
       concurrently,  as well as the availability of reserved ports in the rsh
       rcmd modules.

       For additional limitations, see the manpage.

       ckill accepts lists of hosts in the general form:  prefix[n-m,l-k,...],
       where  n	 <  m and l < k are an alternative to explicit lists of hosts.
       This form should not be	confused  with	regular	 expression  character
       classes (also denoted by `[]'').	 For example, node[19] does not repre‐
       sent an expression matching node1 or node9, but the degenerate hostlist

       Hostlist	 syntax	 is provided only as a convenience on clusters using a
       prefixNNN naming convention and specification of ranges should  not  be
       considered  necessary  --  thus	you  could  specify node1,node9 or the
       hostlist node[1,9].

       Note that some shells interpret brackets ([ and ]) in pattern matching.
       Depending  on  your  shell, you may need to enclose ranged lists within
       quotes.	For example, in tcsh, the hostname should be  quoted  as  fol‐

       ckill -w "node[01-05]" process1

       To ckill the following processes on node01:

	      1. process1

	      2. bin/process1

	      3. /usr/bin/process1


	      ckill -w node1 process1

       To ckill ONLY bin/process1, use:

	      ckill -w node1 bin/process1

       To  list	 all  processes	 with name process1 on node1, node2 and node3,

	      ckill -v -w nodel,node2,node3 process1

       pdsh(1), rsh(1), ssh(1), kill(1), ccp(1),  cexec(1),  clog(1),  cps(1),
       cuptime(1), cwall(1M), csshsetup(1)


List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net