Re: network slowness/freez-up since update 10/11

Andrey Chernov wrote:
> On Thu, Oct 14, 2004 at 02:59:34PM +0200, Ian FREISLICH wrote:
> 
>>but zero response IIRC.  Maybe making it on by default was a little
>>hasty, but anyone that follows -CURRENT like they should if they
>>run it weuld have been aware of this and set debug.mpsafenet=0 in
>>their loader.conf when they saw that commit.
> 
> 
> There is nowhere said in this commit that if_de would or ever may be 
> broken. Everydays something new coming, and this commit is one between 
> similar others, nothing brings special attention to be aware of. I'll 
> expect special 'WARNING: de owners' message to current in such situations, 
> i.e. if something is not fixed to work together.
> 

Andrey,

I just searched the PR database and I can't find any reports from you 
related to this problem.  I've also reviewed all of the email on this
subject and I can't find any actual details of the problem from you
nor any hint that you've attempted to debug it.  I'm also not aware
of Robert or any other developer being on paid contract by you to
guarantee that your hardware works.  And since you yourself are a
developer and former Core team member, I'm a little curious why you
are upset that other volunteers aren't jumping to your needs while
you make no effort to help yourself or even file a bug report.  Making
the network stack run without Giant is a big task, and any problems
that exist certainly are not intentional nor due to lack of effort.

That said, this is indeed a serious bug and we need to fix it.

Scott