On 16-Nov-99 Mel wrote:
>>Pipe wouldnt' work in this case because the child is executed with
>system(). If I didn't use system, I would be using execl because I need a
>totally seperate process, a copy with fork doesn't work. Can I use a pipe
>with that sort of setup? I think atexit() (new function to me) might do
>the job but at the moment, it's causing segfaults. I have a feeling it's
>because the quit function is part of a library which is loaded at runtime.
>By program termination, the library has been unloaded with my quit
>function along with it (no, I can't compile the quit function into the
>main part of the program). What does work, is trapping SIGUSR1 in the
>parent and periodically getting the child to send SIGUSR1. If it fails, it
>dies. God, the architecture for this program is beginning to irritate me.
Plop the source somewhere, comment what you want to do in the source and
give us some pointers to it and someone might have a look at it and fix it.
Show us the source baby.
Real Life: Caolan McNamara * Doing: MSc in HCI
Work: Caolan.McNamara at ul.ie * Phone: +353-86-8790257
URL: http://www.csn.ul.ie/~caolan * Sig: an oblique strategy
Don't be afraid of things because they are easy to do
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!