Ident trouble?
Jeffrey M. Vinocur
jeff at litech.org
Mon Jul 26 23:37:28 UTC 2004
I have no idea why since rc.c hasn't changed in ages, but since the 2.4.2
prerelease or so I've had innd hang several times in the following
fashion. I suppose it could be coincident with some other system changes
around here, but even if there's something wrong with our identd, innd
shouldn't die as a result...
#0 0x40127a98 in read () from /lib/libpthread.so.0
#1 0xbffff0a0 in ?? ()
#2 0x080653f8 in GoodIdent (fd=96, identd=0x80d4b10 "news") at rc.c:190
#3 0x080661f9 in RCreader (cp=0xbffff0a0) at rc.c:642
#4 0x0805b173 in CHANreadloop () at chan.c:1015
#5 0x0805d630 in main (ac=2, av=0x8243880) at innd.c:666
(gdb) step
Single stepping until exit from function read,
which has no line number information.
[ many second pause here, with read() never returning ]
Program received signal SIGINT, Interrupt.
--
Jeffrey M. Vinocur
jeff at litech.org
More information about the inn-workers
mailing list