[follow-up] ctlinnd reload history <reason> kills innd

[William F. Maton]

On Wed, 6 Mar 2002, Jeffrey M. Vinocur wrote:

> On Wed, 6 Mar 2002, William F. Maton wrote:
>
> > On Wed, 6 Mar 2002, Jeffrey M. Vinocur wrote:
> >
> > > > The former message appears far more frequently than the latter....
> > >
> > > Oooh, ok, I can fix this.
>
> Actually...on further consultation, I'm not ready to fix it yet.
>
> If you can help me -- we need to find out what signal it is that's
> interrupting the system call.  I think you can find that out from gdb.

And another:

(gdb) cont
Continuing.

Breakpoint 1, ThrottleIOError (when=0x81206fd "history write") at util.c:268
268             oerrno = errno;
(gdb) bt
#0  ThrottleIOError (when=0x81206fd "history write") at util.c:268
#1  0x80791a0 in InndHisWrite (
    key=0x87ee70c "<a65qss$bru$01$1 at news.t-online.com>", arrived=1015454103,
    posted=1015443061, expires=0, token=0xbffff708) at util.c:353
#2  0x80648fe in ARTpost (cp=0x4043a1e8) at art.c:2540
#3  0x806c064 in NCpostit (cp=0x4043a1e8) at nc.c:193
#4  0x806d655 in NCproc (cp=0x4043a1e8) at nc.c:973
#5  0x806ddaf in NCreader (cp=0x4043a1e8) at nc.c:1175
#6  0x806998d in CHANreadloop () at chan.c:1093
#7  0x806ba94 in main (ac=2, av=0xbffffe94) at innd.c:649
(gdb)


wfms