.
As stated I'm going to be taking some time to investigate the socket
engine issues that have arisen recently.
On 12 Oct 2005, at 07:03, Marc Haber wrote:
On Tue, Oct 11, 2005 at 10:24:27PM +0100, Alasdair McWilliam wrote:
What socket engine module is 2.0.1-1 compiled with?
rt
On 11 Oct 2005, at 13:10, Marc Haber wrote:
On Tue, Oct 11, 2005 at 11:55:34AM +, Johannes Berg wrote:
Subject: Bug#33: rageircd: extremely high lag on encrypted
connections
^^ you know that you got to buy all Debian
Developers
a drink for hi
o, a great mystery.
Alasdair McWilliam wrote:
Hi
From the lack of communication I assume your server has stabilised
by compiling with -O0 instead of -O2?
Rather odd I have a gut feeling this is going to take a
serious amount of debugging. :-(
--
To UNSUBSCRIBE, email to [EMAIL
Hi
From the lack of communication I assume your server has stabilised
by compiling with -O0 instead of -O2?
Rather odd I have a gut feeling this is going to take a serious
amount of debugging. :-(
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
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.
Ga
PS. I can never actually re-create the issue; it happens at random.
I've found that if I wait for it to happen, it doesn't!!
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, how
On 4 Oct 2005, at 10:46, Philip Craig wrote:
The server has 0 users connected and 1 other server connected. It's
a backup server in case of connectivity loss on the main server.
The crashes happen at random, after say 3-6 hours. When the crashes
happen, no one on the server that crashes h
Rather an interesting one.
What strikes me is that AWAY verifies sptr->user is non-NULL before
it does anything. However just because sptr->user is non-NULL does
not mean it's valid memory space. Methinks a heap corruption.
What are you doing on the server prior to this occurring?
How long
Now, I see the following on stdout:
No random state, generating entropy from /dev/random. I see this
repeatedly if I ctrl-c that process.
Yeah, rageircd uses a 1024-byte random key to establish an encrypted
session server-to-server.
If the ircd can't get enough entropy from the system
Basically, listen * { ... }; will make the ircd bind to _all
available interfaces_ on the specified ports. So, if your server has
two network interfaces (i.e. 192.168.0.1 and 10.0.0.1) it will bind
to these, and (| think) 127.0.0.1 too.
It's possible that if for any reason any ports on an i
Could you include a copy of the 'listen' configuration in your
rageircd config file?
Cheers
On 30 Sep 2005, at 10:49, Philip Craig wrote:
Package: rageircd
Version: 2.0.1-1
Severity: important
On my system, rageircd starts up but doesn't even beind to 6667,
according to netstat. The /etc/i
y -
gcc 2)
On 13 Jul 2005, at 22:15, Florian Weimer wrote:
* Alasdair McWilliam:
The original 2.0.0 release does indeed include a vulnerable zlib
verison.
Patch to use the system zlib is attached. A compiled package is
temporarily available from:
http://static.enyo.de/fw/volatile/rag
The original 2.0.0 release does indeed include a vulnerable zlib
verison.
However 2.0.1 (currently post-rc1) development has wound down and
will be released within a few days, and will be near enough the
current build/revision.
On 13 Jul 2005, at 13:26, Florian Weimer wrote:
retitle 309
Quoted from ./configure --help
--with-bindir=DIR Sets binaries to live in DIR (default:
PREFIX)
--with-moddir=DIR Sets modules to live in DIR (default:
PREFIX/modules)
--with-confdir=DIR Sets conf files to live in DIR (default:
PREFIX)
--wit
Thanks. So I can upload the patched version to unstable, fixing the
s390 issue?
Yes :-)
It is an issue which makes the current rageircd unsuitable for release
with a stable version. We have missed sarge anyway, so the package
wouldn't migrate from unstable to testing anyway. That bug report
doesn't
I expect you know more than me about this so I'll go with the patch
you've given.
Thanks for your input on this issue too it's really appreciated. :-)
I'll re-fix the BLUEMOON branch tomorrow evening probably.
Is it possible to close the other bug associated with rageircd as
it's not really a
Package: rageircd
Version: 2.0.0-2
Sorry, the previous messages were attached to this bug report by
mistake. Whoops!
Re. zlib, yes it's been sorted out in the next version, 2.0.1, ETA June.
Cheers
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EM
See messages forwarded below. Sent to the wrong bug report in error.Begin forwarded message:From: Alasdair McWilliam <[EMAIL PROTECTED]>Date: 16 May 2005 14:45:15 BDTTo: Marc Haber <[EMAIL PROTECTED]>Cc: [EMAIL PROTECTED]Subject: Fwd: Bug#307231: RageIRCd build failure on
Package: rageircdVersion: 2.0.0-2Re. the below message, the configure.ac line number may be incorrect as autoconf has changed a bit between 2.0.0 and the current BLUEMOON revision. It shouldn't be too far out though.AlasdairBegin forwarded message:From: Alasdair McWilliam <[EMAIL PROTECT
Package: rageircd
Version: 2.0.0-2
Hi Marc,
Apologies for not getting back to you sooner - I've been working hard.
I've got around to the proper bug fix so bare with me.
Firstly, replace all the current VA_COPY declaration statements in
include/common.h with:
#ifdef HAVE___VA_COPY
#define VA_COP
17:13, Marc Haber wrote:
tags #307231
thanks
On Sun, May 01, 2005 at 11:44:56PM +0100, Alasdair McWilliam wrote:
The compile failure is in src/ircsprintf.c as follows.
cc -g -Wall -O2 -export-dynamic -I../adns -I../include -I../zlib -c
ircsprintf.c
ircsprintf.c: In function `ircvsprintf
y 2005, at 06:36, Marc Haber wrote:
severity #307231 serious
thanks
Justification: hidden FTBFS
Hi,
On Sun, May 01, 2005 at 11:44:56PM +0100, Alasdair McWilliam wrote:
I've checked the build logs for rageircd 2.0.0-2 in unstable and have
noticed that the actual rageircd binary doesn'
Package: rageircdVersion: 2.0.0-2HiI've checked the build logs for rageircd 2.0.0-2 in unstable and have noticed that the actual rageircd binary doesn't build on the s390 architecture. Hence I am reporting it here.The compile failure is in src/ircsprintf.c as follows.cc -g -Wall -O2 -export-dynami
23 matches
Mail list logo
