I had the same situation a few days ago (with kernel 1.3.91-93, not sure).
The machine that originate the overload in my Linux box was a NEXT.
The target user of talk have 'mesg y' instead. The load average was 8, i
think!
I can't figure what cause the uncontrolled spawning of in.ntalkd.
The config of my Linux box is based too on slackware 3.0.
Regards - Alfredo
> evening. Otherwise, it's been excellent. The situation: a series of talk
> requests made from an OSF machine to my Linux box, to a user who had mesg
> n resulted in a rapid, cpu-intensive spawning of in.ntalkd. I was present
--- Alfredo Sanjuan, Director Tecnico, Internet Business Development S.L., Spain Mail1: alfre@ibd.es Mail2: siasaala@sc.ehu.es (http://www.sc.ehu.es/~siasaala/) Tlf. : +34-43-474930