Re: Linux signals and GLIB g_io_channel usage




On Mon, 2006-10-23 at 13:42 -0400, Tristan Van Berkom wrote:

James Scott Jr wrote:
Folks,


Hi James,
    in a phrase - I've done it and it works fine.

some places might call for special attention though - for
example - if you were to call g_spawn_sync() or g_child_watch(),
you may want to have leave SIGCHLD available.


Thats what prompted the question.  I noticed that I needed to un-block
around a call to g_spawn_command_line_async() and wondered if I was
getting into trouble on this path.  Now I will only unblock SIGCHLD
around those calls instead of all signals.  

Thanks for the quick response.


Cheers,
              -Tristan



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]