+q Quiets Users in ALL Channels, even after removal

Sat, 06 Jan 2007 12:03:48 -0000

It seems that a quiet ban, sticks, even after removal, to show this case this is the problem

ClientA
Nick: A
Hostmask: A!foo@53-34.bbc.co.uk

ClientB
Nick: B
Hostmask: B!bar@4325.tvnz.co.nz

ClientC
Nick: C
Hostmask: C!bofh@25.94.abc.com.au
Already in #tvnz w/ ChanOps and in #bbc

ClientA: /join #bbc
ClientA Receives ChanOp
ClientA decides to quiet TVNZ management (+q *!*@*.tvnz.co.nz)
ClientB: /join #bbc,#tvnz
ClientB: /msg #bbc Hi
Server->ClientB: Cannot send to channel (+q)
ClientA removes quiet
ClientB: /msg #bbc Take two
Server->ClientB: Cannot send to channel (+q)
ClientB: /msg #tvnz Hi
Server->ClientB: Cannot send to channel (+q)

From initial assessment of the issue I think it is something to do with the caching of bans/quiets, and I think it needs testing more. (I think around r6)

Mac OSX Build Errors

Sun, 31 Dec 2006 12:59:36 -0000

I spotted two interesting problems when building SVN trunk on the Compile Farm with OSX.

Number One: Autodetection came up with a really stupid Max Connections limit. Easy fix: Specify --with-maxconnections=1024 (or whatever)

Number Two: GCC would produce "bad macro argument list" errors while compiling src/fds.c and src/socketengine_select.c. This can be fixed by adding CC="gcc -no-cpp-precomp" before the ./configure statement.

My suggestions:
Investigate a new ./configure script that will actually default to 1024 connections (override on --with-maxconnections
If building on a 'powerpc-apple-darwin6.8' add -no-cpp-precomp to the gcc args.

Recent changes to bugs

+q Quiets Users in ALL Channels, even after removal

Mac OSX Build Errors