Dan Melomedman wrote:
> Bill Hacker wrote:
>
>>I still thing fixing the application is preferable.
>
>
> What's there to fix if it's not the application's fault?
*SNIP*
We should call a halt to this.
http://directory.fsf.org/email/spam/MessageWall.html
Has the e-mail address of the developer and maintainer with whom you
should be having this discussion.
I see no complaints here from that source about kernel problems.
The addressess of the FreeBSD port maintainer and others who have
contributed patches to fix what I class as serious flaws are listed in
the Makefile in the ports tree.
The features it touts have largely been bypassed by MTA's and their
common 'sputniks', which may be why we have heard little of it. All of
those, BTW, DO have connection-limit and other load-management settings.
MessageWall should have also.
It relies on "firestring, firedns, *daemontools (with 'svscan'
running)*". That last entry shouts 'unstable' in a loud voice.
I see nothing that justifies further waste of kernel developers time.
Wrong venue, that's all.
Bill Hacker