|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| High Level Programming Post questions about C, C++, Java, SQL, and other programming languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| catching a signal from child process | emil2006 | High Level Programming | 2 | 05-03-2008 09:20 AM |
| catching some errors | bebop1111116 | Shell Programming and Scripting | 5 | 09-29-2006 02:12 PM |
| Catching all Exit Codes | Sivaswami J | Shell Programming and Scripting | 3 | 02-16-2006 07:13 PM |
| Awk- catching the last two chars | Gerry405 | UNIX for Dummies Questions & Answers | 9 | 11-22-2005 06:23 AM |
| catching interrupts | toughguy2handle | UNIX for Dummies Questions & Answers | 1 | 09-19-2005 04:17 PM |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
11-12-2005
|
||||
|
||||
|
Catching signal and piping
Hi,
Recently I was reading some c coding by some colleagues and I noticed that the above trend. They will create a pipe for the process then they will use the standard signal handler to capture a particular signal and write that signal to the pipe. On the other end, the process will read the pipe and retreive the signal. Is it enough to simply use the signal handler and do a switch case. Why do they have to create a pipe? I am sorry if this is a newbie question.  |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Threaded Mode
