Re: gcj: SignalListener, process pid, ...

[Andrew Haley <aph at redhat dot com>]

Tom Tromey writes:
 > >>>>> "Erik" == Erik Poupaert <erik.poupaert@freestyler-toolkit.org> writes:
 > 
 > Erik> That should be ample enough to control linux daemons with, if it
 > Erik> weren't for the fact that the traditional SIGHUP signal is
 > Erik> missing. While the library permits listening to SIGHUP (and
 > Erik> SIGDANGER(?)), libgcj unfortunately prevents somehow the
 > Erik> signal-listening thread to respond to it.(Why?)
 > 
 > We reserve a signal to implement Thread.interrupt().
 > On Linux this is SIGHUP.

Oh dear.  That means to use a server process that can handle SIGHUP
you'll have to create a wrapper.

Andrew.