Strange behavior from kill command Post: 303037019

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

strange sed behavior

I have a file called products.kp which contains, for example, 12345678,1^M 87654321,2^M 13579123,3 when I run the command cat products.kp| sed -f kp.sed where kp.sed contains s,^M,, I get the output 12345678,1 87654321,2 13579123,3

2. Shell Programming and Scripting

nawk strange behavior

Dear guys; when deleting repeated lines using nawk as below ; Why the below syntax works? nawk ' !a++' infile > outfile and when using the other below syntax the nawk doesn't work? nawk ' { !a++ } ' infile > outfile or nawk ' { !a++ } ' infile > outfile BR

3. Programming

Strange behavior in C++

I have the following program: int main(int argc, char** argv){ unsigned long int mean=0; for(int i=1;i<10;i++){ mean+=poisson(12); cout<<mean<<endl; } cout<<"Sum of poisson: "<< mean; return 0; } when I run it, I get the...

4. Ubuntu

Ubuntu strange behavior

It is so till login screen. I mean that when I boot my computer, Ubuntu shows a splash screen with mouse instead of Ubuntu logo and in the login screen it shows XUbuntu login screen... It began when I upgraded to previous kernel, I suppose, but I'm not sure... I can't say that it annoys me very...

5. Red Hat

strange mail behavior

Hi I have script to to take backup and send mail to a group once a day. One strange behavior I have observed recently is that most of the time the mail we receive is fine . But someday it just sends out mail without any subject with undisclosed recipients. I dont know how to find the cause...

6. Shell Programming and Scripting

Strange behavior on one of my server

I am not sure what is wrong, but I have some strange behavior when printing things out. I do create a file with only one word test, no space, no new line etc. nano file<enter> test<ctrl x>y<enter> Server 1 gets (fail) awk '{print "+"$0"*"}' file *test Server 2 gets (OK) awk '{print...

7. Shell Programming and Scripting

Strange behavior of grep

Hi All, I am facing a strange problem while grepping for a process. Here is the small script that i have written. It will look for any process running with the parameter passed to the script. If no process is running it should print appropriate message. $ cat t.ksh #!/bin/ksh set -x ...

8. Shell Programming and Scripting

Strange behavior of find and rm command

Hi I run the below command to find and delete *.xml files 90 or more days old. find . -type f -name '*.xml' -mtime +90 -exec rm {} \; find: stat() error ./Hello/2014_EMPTY.xml: No such file or directory ./Hello/2014_EMPTY_8011.xml: No such file or directory ..... .... If the file...

9. Shell Programming and Scripting

Strange Ctrl+C behavior

Hello All, I have a strange issue. I've created a shell script which connects to RMAN (Oracle Recovery Manager) and executes full DB backup. I then executed this script with nohup and in the background: $ nohup my_script.sh > logfile.log 2>&1 &The issue is that when I tried to take a look into...

LEARN ABOUT REDHAT

kill

KILL(1) 						     Linux Programmer's Manual							   KILL(1)

NAME

       kill - terminate a process

SYNOPSIS

       kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
       kill -l [ signal ]

DESCRIPTION

       The command kill sends the specified signal to the specified process or process group.  If no signal is specified, the TERM signal is sent.
       The TERM signal will kill processes which do not catch this signal.  For other processes, it may be necessary to use the KILL  (9)  signal,
       since this signal cannot be caught.

       Most  modern  shells  have  a  builtin  kill function, with a usage rather similar to that of the command described here. The `-a' and `-p'
       options, and the possibility to specify pids by command name is a local extension.

OPTIONS

       pid... Specify the list of processes that kill should signal.  Each pid can be one of five things:

	      n      where n is larger than 0.	The process with pid n will be signaled.

	      0      All processes in the current process group are signaled.

	      -1     All processes with pid larger than 1 will be signaled.

	      -n     where n is larger than 1.	All processes in process group n are signaled.	When an argument of the form `-n' is given, and it
		     is  meant	to  denote  a process group, either the signal must be specified first, or the argument must be preceded by a `--'
		     option, otherwise it will be taken as the signal to send.

	      commandname
		     All processes invoked using that name will be signaled.

       -s signal
	      Specify the signal to send.  The signal may be given as a signal name or number.

       -l     Print a list of signal names.  These are found in /usr/include/linux/signal.h

       -a     Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.

       -p     Specify that kill should only print the process id (pid) of the named processes, and not send any signals.

SEE ALSO

       bash(1), tcsh(1), kill(2), sigvec(2), signal(7)

AUTHOR

       Taken from BSD 4.4.  The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.

Linux Utilities 						  14 October 1994							   KILL(1)