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 BSD

kill

KILL(1) 						      General Commands Manual							   KILL(1)

NAME

       kill - terminate a process with extreme prejudice

SYNOPSIS

       kill [ -sig ] processid ...
       kill -l

DESCRIPTION

       Kill  sends the TERM (terminate, 15) signal to the specified processes.	If a signal name or number preceded by `-' is given as first argu-
       ment, that signal is sent instead of terminate (see sigvec(2)).	 The  signal  names  are  listed  by  `kill  -l',  and	are  as  given	in
       /usr/include/signal.h, stripped of the common SIG prefix.

       The  terminate  signal  will  kill  processes  that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
       caught.	By convention, if process number 0 is specified, all members in the process group  (i.e.  processes  resulting	from  the  current
       login)  are  signaled  (but  beware:  this works only if you use sh(1); not if you use csh(1).)	Negative process numbers also have special
       meanings; see kill(2) for details.

       The killed processes must belong to the current user unless he is the super-user.

       The process number of an asynchronous process started with `&' is reported by the shell.  Process numbers can also be found by using ps(1).
       Kill  is  a  built-in  to  csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
       arguments.  See csh(1) for details.

SEE ALSO

       csh(1), ps(1), kill(2), sigvec(2)

BUGS

       A replacement for ``kill 0'' for csh(1) users should be provided.

4th Berkeley Distribution					  April 20, 1986							   KILL(1)