[JDEV] Server feature request

[kadokev at msg.net]

> Those are the definitions of those signals in BIND though. They have 
> different (already used) meaning within Jabber - they are used by pth 
> (and I believe MIO). They are simply user-defined signals.

Right, exactly.

So we pick two new signals to serve this purpose in Jabber, the concept is
still the same. So we use SIGINFO to turn on debugging, and SIGWINCH to turn
it off, or any two other signals that are not already taken.

It would also be useful to have the ability to turn debugging on and off by
sending an admin message, but the signal method is more important, as it would
be very useful to debugging cases where I cannot connect/login at all, and thuse
cannot send any messages...
 
Kevin

> -David Waite
> kadokev at msg.net wrote:
> >Server feature request, the ability to turn debugging on/off by sending a
> >Unix signal to the jabberd process, something like this:
> >
> >     SIGUSR1   Turns on debugging; each SIGUSR1 increments debug level.
> >               (SIGEMTon older systems without SIGUSR1.)
> >
> >     SIGUSR2   Turns off debugging completely.   (SIGFPEon older systems
> >               without SIGUSR2.)
> >
> >The astute observer will notice that the two paragraphs above are verbatim from
> >the documentation for BIND :-)
...
> >>Yes!! It's been a long time I was thinking about it!
> >>In certain cases it is just necessary...
> >>
> >>/MAciek
> >>
> >>On Thu, 10 May 2001 11:45:35 -0600 Malone, Pat wrote:
> >>
> >>>In trying to work through a nasty client problem today, I had 'if only'
> >>>thought pass through my head.  So, here is a wish item for the jabberd
> >>>developer gods:
> >>>
> >>> Enable the ability to send a sig of some kind to jabberd to toggle
> >>>debugging on and off, a.k.a. the way debug can be toggled with named.
> >>>
> >>>It sure would be nice to toggle debug on when a problem shows up without
> >>>having to kill the server.