On Mon, 2006-11-13 at 17:02 -0800, C.R. Kirkwood-Watts wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> James Scott Jr wrote:
> > On Mon, 2006-11-13 at 02:15 -0500, Freddie Unpenstein wrote:
> >
> >> On Mon 10/23, James Scott Jr < [EMAIL PROTECTED] > wrote:
> >>> I am about to write
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Scott Jr wrote:
> On Mon, 2006-11-13 at 02:15 -0500, Freddie Unpenstein wrote:
>
>> On Mon 10/23, James Scott Jr < [EMAIL PROTECTED] > wrote:
>>> I am about to write the socket module of a program that follows the
>>> gnu standard structure for
On Mon, 2006-11-13 at 02:15 -0500, Freddie Unpenstein wrote:
> On Mon 10/23, James Scott Jr < [EMAIL PROTECTED] > wrote:
> > I am about to write the socket module of a program that follows the
> > gnu standard structure for a daemon. I am using glib wherever
> > possible and have a question concer
On Mon 10/23, James Scott Jr < [EMAIL PROTECTED] > wrote:
> I am about to write the socket module of a program that follows the
> gnu standard structure for a daemon. I am using glib wherever
> possible and have a question concerning the use of linux signals.
> Basically, I have blocked all signal
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(),
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.
Cheers,
-Tristan
__
Folks,
I am about to write the socket module of a program that follows the gnu
standard structure for a daemon. I am using glib wherever possible and
have a question concerning the use of linux signals. Basically, I have
blocked all signals on all threads according to the standard daemon
model a
