----- Original Message -----
From: "Chmouel Boudjnah" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 13, 2001 12:11 AM
Subject: Re: [Cooker] talkd problems....race condition after being
portscanned?
> Chmouel Boudjnah <[EMAIL PROTECTED]> writes:
>
> > "Ryan Little" <[EMAIL PROTECTED]> writes:
> >
> > > basically the scan calls in.talkd from xinetd (as it should) but the
talk
> > > daemon continues to run, producing this buttload of errors and eating
up 90%
> > > of my cpu, sort of a "race condition" this is very very bad in my
> > > opinion....Can anyone reproduce this? I'm running beta2 with a few
things
> > > moved around a bit as I've been trying to debug this, I've gotten the
same
> > > error from several mandrake versions of talkd...I'm out of ideas on
this
> > > one.
> >
> > ok i can reproduce should be fixed now in -6mdk.
>
> you need also the last setup to get it works..
>
> --
> MandrakeSoft Inc http://www.chmouel.org
> --Chmouel
I've also noticed that in.ntalkd doesn't close after ending a remote talk
session, it doesn't create the race condition like in.talkd, it just sits
there idle though.
Also...where can I find talk-0.17-6mdk? or are you saying it WILL be fixed
when it comes out...
Ryan
