Sponsored Content
Top Forums Programming using signals instead of busy wait Post 302146582 by jut26 on Wednesday 21st of November 2007 08:39:42 AM
Old 11-21-2007
signals

Hi.

Thanks to everybody's ideas I have a solution to the problem.


Sincerely,
Jut
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

CD Drive is busy

one problem which seems simple but i've faced many times is when i've used cd & want to eject, however i'm not in /dev/cdrom/... in any of my Xterms but it gives the message that the the CD drive is busy. the only thing i could do is /etc/init.d/volmgt stop & eject the CD manually but it doesn't... (6 Replies)
Discussion started by: nikk
6 Replies

2. Shell Programming and Scripting

Need to execute 2 scripts, wait, execute 2 more wait, till end of file

:cool: I need to execute a shell script to do the following: cat a file run two back ground processes using the first two values from the file wait till those background processes finish run two more background processes using the next two values from the file wait till those background... (1 Reply)
Discussion started by: halo98
1 Replies

3. Shell Programming and Scripting

wait command - cat it wait for not-chile process?

Did not use 'wait' yet. How I understand by now the wait works only for child processes, started background. Is there any other way to watch completion of any, not related process (at least, a process, owned by the same user?) I need to start a background process, witch will be waiting... (2 Replies)
Discussion started by: alex_5161
2 Replies

4. UNIX for Advanced & Expert Users

Filesystem mystery: disks are not busy on one machine, very busy on a similar box

Hi, We have a filesystem mystery on our hands. Given: 2 machines, A and Aa. Machine Aa is the problem machine. Machine A is running Ubuntu, kernel 2.6.22.9 #1 SMP Wed Feb 20 08:46:16 CST 2008 x86_64 GNU/Linux. Machine Aa is running RHEL5.3, kernel 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38... (2 Replies)
Discussion started by: mschwage
2 Replies

5. Shell Programming and Scripting

calling a shell script in background and wait using "wait" in while loop

Hi, I am facing a strange issue, when i call a script from my while loop in background it doesnt go in background, despite the wait i put below the whil loop it goes forward even before the process put in background is completed. cat abc.txt | while read -u4 line do #if line contains #... (2 Replies)
Discussion started by: mihirvora16
2 Replies
sigset(3C)																sigset(3C)

NAME
sigset(), sighold(), sigrelse(), sigignore() - signal management SYNOPSIS
DESCRIPTION
The system defines a set of signals that can be delivered to a process. The set of signals is defined in signal(5), along with the meaning and side effects of each signal. An alternate mechanism for handling these signals is defined here. The facilities described here should not be used in conjunction with the other facilities described under signal(2) and sigspace(2). allows the calling process to choose one of four ways to handle the receipt of a specific signal. sig specifies the signal and func speci- fies the action handler. sig can be any one of the signals described under signal(5) except or func is assigned one of four values: or a function address. The actions prescribed by and are described under signal(5). The action pre- scribed by and function address are described below: Hold signal. The signal sig is held upon receipt. Any pending signal of this signal type remains held. Only one signal of each type is held. Note: the signals and cannot be held. function address Catch signal. func must be a pointer to a function, the signal-catching handler, that is called when signal sig occurs. specifies that the process calls this function upon receipt of signal sig. Any pending signal of this type is released. This handler address is retained across calls to the other signal management functions listed here. Upon receipt of signal sig, the receiving process executes the signal-catching function pointed to by func as described under signal(5) with the follow- ing differences: Before calling the signal-catching handler, the defined action of sig is set to During a normal return from the signal- catching handler, the defined action is restored to func and any held signal of this type is released. If a non-local goto (longjmp(3C)) is taken, must be called to restore the defined action to func and release any held signal of this type. holds the signal sig. restores the defined action of sig to that specified previously by and are used to establish critical regions of code. is analogous to raising the priority level and deferring or holding a signal until the priority is lowered by sets the action for signal sig to (see signal(5)). RETURN VALUE
Upon successful completion, returns the previous value of the defined action for the specified signal sig. Otherwise, a value of is returned and is set to indicate the error. is defined in For the other functions, a 0 value indicates that the call succeeded. A -1 return value indicates an error occurred and is set to indicate the reason. ERRORS
fails and the defined action for sig is not changed if any of the following occur: The func argument points to memory that is not a valid part of the process address space. Reliable detection of this error is implementation dependent. and and fail and the defined action for sig is not changed if any of the following occur: sig is not a valid signal number. An attempt is made to ignore, hold, or supply a handler for a signal that cannot be ignored, held, or caught; see signal(5). WARNINGS
These signal facilities should not be used in conjunction with signal(2) and sigspace(2). SEE ALSO
kill(1), kill(2), pause(2), signal(2), sigspace(2), wait(2), abort(3C), setjmp(3C), sigpause(3C), signal(5). STANDARDS CONFORMANCE
sigset(3C)
All times are GMT -4. The time now is 06:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy