Phil,
I believe your observations are correct. That is, two manifestations
of the same bug.
I've had this problem for a number of months, as I said, on a FreeBSD
server. However we have an almost identical server (also running
FreeBSD) and the ircd has an uptime of almost six months.
Gah! I thought it was just the server as it had some hardware issues,
but I guess this confirms it's a software bug. It occurs in LIST and
NICK now and then too.
Have you actually compiled in Debug mode? I.E. with --enable-debug at
configure, and running with the "-x 9" argument. That will create
debug.log. (Beware: sensitive information such as passwords may be
logged.)
On 4 Oct 2005, at 17:37, Philip Craig wrote:
Marc Haber wrote:
One time it again broke at m_away.c line 88. Another time it
broke at m_away.c line 68
That, however, looks like that we have either _two_ bugs, or you have
a hardware issue. A single bug would most probnably show at the same
point .
Reading the code, it looked like it could be two manifestations of
the same bug to me. The two lines are doing exactly the same thing,
just under differing initial conditions (depending on exactly what
server away message it's processing it ends up under two different
if branches)
I am reluctant to call hardware bug because this server has served
and continues to serve several other daemons fulltime for many
months under its current setup without any glitches: sshd, apache,
imapd, exim4, dovecot-imapd, samba.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
