Sponsored Content
Full Discussion: Signal Processing
Top Forums UNIX for Dummies Questions & Answers Signal Processing Post 8202 by Perderabo on Monday 8th of October 2001 10:19:26 AM
Old 10-08-2001
Gee, thanks for the kind words guys!

No, you cannot just assume the next pid will be the current pid +1. You're on a multi-user machine. Stuff like cron runs all the time. If someone else forks first, they get the next pid. Also in a multi-cpu system, each cpu will usually reserve a chunk of 10 or so pids at once to cut down on spinlocks. Finally, pids recycle after pid 32,000.

The worst consequence of the sleep program in the background is that it is consuming a proc table entry. Too many of these and eventually you bump into maxuprc and cannot fork anymore. As long as that was not an issue, I'd just let it run. Remember that it will take code to remember or find the pid and then kill the pid. The load that this code would put on the system is trivial, but the only payback is the early death of a sleep statement...it can't make a profit.

If you really got to nail that last sleep process, a "kill $(ps -f | grep [s]leep |awk '{print $2}')" should get it.
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script Signal Processing

I am trying to develop a script that will properly handle kill signals particularly kill -2. I have program (_progres) that properly receives the signal if I run it from the command line directly: _progres -T /tmp -p /home/mejones/signal.p -b 2>&1 & If I try to put it in a script (i.e.... (2 Replies)
Discussion started by: mejones99
2 Replies

2. Programming

Signal processing

We have written a deamon which have many threads. We are registering for the SIGTERM and trying to close main thread in this signal handling. Actually these are running on Mac OS X ( BSD unix). When we are unloading the deamon with command launchctl, it's sending SIGTERM signal to our process... (1 Reply)
Discussion started by: Akshay4u
1 Replies

3. Programming

alarm signal processing

I'm writing a function right now, and I want to set an alarm to avoid a timeout, here's the general idea of my code: int amt = -2; alarm(10); amt = read(fd, &t->buf, TASKBUFSIZ - tailpos); //do a read when the alarm goes off, i want to check the value of "amt" ... (1 Reply)
Discussion started by: liaobert
1 Replies

4. Solaris

Signal Processing in unix

I've read the man page of singal(3) but I still can't quite understand what is the difference between SIGINT, SIGALRM and SIGTERM. Can someone tell me what is the behavioral difference among these 3 signals in kill command? Thanks! (2 Replies)
Discussion started by: joe228
2 Replies

5. Shell Programming and Scripting

How to make parallel processing rather than serial processing ??

Hello everybody, I have a little problem with one of my program. I made a plugin for collectd (a stats collector for my servers) but I have a problem to make it run in parallel. My program gathers stats from logs, so it needs to run in background waiting for any new lines added in the log... (0 Replies)
Discussion started by: Samb95
0 Replies

6. Programming

awk processing / Shell Script Processing to remove columns text file

Hello, I extracted a list of files in a directory with the command ls . However this is not my computer, so the ls functionality has been revamped so that it gives the filesizes in front like this : This is the output of ls command : I stored the output in a file filelist 1.1M... (5 Replies)
Discussion started by: ajayram
5 Replies

7. Shell Programming and Scripting

Continue Processing after a signal is caught

Is it possible to continue after signal is caught and control goes to function specified in the trap statement? (3 Replies)
Discussion started by: Soham
3 Replies
kill(2) 							System Calls Manual							   kill(2)

Name
       kill - send signal to a process

Syntax
       #include <sys/types.h>
       #include <signal.h>

       kill(pid, sig)
       pid_t pid;
       int sig;

Description
       The  system  call sends the signal sig to a process specified by the process number pid.  The sig can be a signal specified in a call or it
       can be 0.  If the sig is 0, error checking is performed, but a signal is not sent.  This call can be used to check the validity of pid.

       The sending and receiving processes must have the same effective user ID, otherwise this call is  restricted  to  the  superuser  with  the
       exception of the signal SIGCONT.  The signal SIGCONT can always be sent to a child or grandchild of the current process.

       If the process number is 0, the signal is sent to all other processes in the sender's process group.

       If  the process number is negative but not -1, the signal is sent to all processes whose process-group-id is equal to the absolute value of
       the process number.

       The above two options are variants of

       If the process number is -1, and the user is the superuser, the signal is broadcast for all processes except to system  processes  and  the
       process sending the signal.

       Processes may send signals to themselves.

Environment
       System Five
       POSIX

       When  your  program  is	compiled in the System V or POSIX environment, a signal is sent if either the real or effective uid of the sending
       process matches the real or saved-set-uid (as described in ) of the receiving process. In addition, any process can use a pid  of  -1,  and
       the signal is sent to all processes subject to these permission checks.

       In POSIX mode, the pid argument is of type pid_t.

Return Values
       Upon successful completion, a value of 0 is returned.  Otherwise, a value of -1 is returned, and is set to indicate the error.

Diagnostics
       The system call fails under the following conditions:

       [EINVAL]       The sig is not a valid signal number.

       [EPERM]	      The  sending  process  is not the superuser, and its effective user ID does not match the effective user ID of the receiving
		      process.

       [ESRCH]	      No process can be found corresponding to that specified by pid.

See Also
       execve(2), getpgrp(2), getpid(2), killpg(2), sigvec(2), pause(3)

																	   kill(2)
All times are GMT -4. The time now is 07:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy