- Original Message -
From: "Chmouel Boudjnah" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 13, 2001 12:11 AM
Subject: Re: [Cooker] talkd problemsrace condition after being
portscanned?
Chmouel Boudjnah [EMAIL PROTECTED] writes:
"Ryan Little&qu
Not sure who's maintaining talk and ntalk but here's an odd one for ya...
[root@littlebox /]# rpm -q talk
talk-0.17-5mdk
[root@littlebox /]# rpm -q xinetd
xinetd-2.1.8.9pre14-2mdk
After a portscan in.talkd starts running wild...here's what it looks like :
[root@littlebox /]# nmap localhost
"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
opinionCan anyone reproduce
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
Hello...
i know... its icq time... irc time.. but... i use talk a lot... did you
remember it?
talk [EMAIL PROTECTED]
or
ytalk -x [EMAIL PROTECTED]
so.. the daemon in 8-beta2 is dead...
sugestions?
Juan Diego
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 29, 2001 2:08 PM
Subject: [Cooker] talkd
Hello...
i know... its icq time... irc time.. but... i use talk a lot... did you
remember it?
talk [EMAIL PROTECTED]
or
ytalk -x [EMAIL