Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Signal Processing
Top Forums UNIX for Dummies Questions & Answers Signal Processing Post 8125 by sanjay92 on Friday 5th of October 2001 05:24:59 PM
Old 10-05-2001
Hello Perderabo,
---------------------------------------------------
"
I know that my method leaves a sleep process running if the timed command completes in time. I think that's harmless. It will be reaped by init when it exits. That's the only real cost of a very easily coded solution. Capturing and killing that last pid will drive script back up in complexity.
"
----------------------------------------------------

Does sleep process creates any kind of overhead for the unix system.

When I execute the following command (sleep 30; echo hello) &
, it create the two processes one is the shell process and the other is sleep process and the sleep process pid is always 1 greater than the shell process pid. Is it always true ?.
sanjay92
 

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

LEARN ABOUT MOJAVE

caffeinate

CAFFEINATE(8)						    BSD System Manager's Manual 					     CAFFEINATE(8)

NAME

     caffeinate -- prevent the system from sleeping on behalf of a utility

SYNOPSIS

     caffeinate [-disu] [-t timeout] [-w pid] [utility arguments...]

DESCRIPTION

     caffeinate creates assertions to alter system sleep behavior.  If no assertion flags are specified, caffeinate creates an assertion to pre-
     vent idle sleep.  If a utility is specified, caffeinate creates the assertions on the utility's behalf, and those assertions will persist for
     the duration of the utility's execution. Otherwise, caffeinate creates the assertions directly, and those assertions will persist until
     caffeinate exits.

     Available options:

     -d      Create an assertion to prevent the display from sleeping.

     -i      Create an assertion to prevent the system from idle sleeping.

     -m      Create an assertion to prevent the disk from idle sleeping.

     -s      Create an assertion to prevent the system from sleeping. This assertion is valid only when system is running on AC power.

     -u      Create an assertion to declare that user is active. If the display is off, this option turns the display on and prevents the display
	     from going into idle sleep. If a timeout is not specified with '-t' option, then this assertion is taken with a default of 5 second
	     timeout.

     -t      Specifies the timeout value in seconds for which this assertion has to be valid. The assertion is dropped after the specified time-
	     out. Timeout value is not used when an utility is invoked with this command.

     -w      Waits for the process with the specified pid to exit. Once the the process exits, the assertion is also released.	This option is
	     ignored when used with utility option.

EXAMPLE

     caffeinate -i make
	caffeinate forks a process, execs "make" in it, and holds an assertion that prevents idle sleep as long as that process is running.

SEE ALSO

     pmset(1)

LOCATION

     /usr/bin/caffeinate

Darwin								 November 9, 2012							    Darwin
All times are GMT -4. The time now is 02:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy