🚀 go-pugleaf

In article <CC1427840A7F201C26@BAYLOR.BITNET> CALIFFM@BAYLOR.CCIS.BAYLOR.EDU (Michael Califf) writes:
}
}Along this line, has anyone else had problems with a KBox running KStar
}losing track of addresses which it has handed out after a period of
}inactivity?  MacTCP acquires its address when opened.  If we run
}NCSA Telnet, then quit and go on to other activities and then go back
}to Telnet some time (hours) later things lock up, often requiring a
}reboot.  I'll have more specifics after I get a few minutes to watch
}the packets.
}
}Mike Califf
}califfm@baylor.edu

Hmmm.  We might have something here...  I'm using NCSA Telnet's own static
addressing, without MacTCP (since I never got around to setting up K-Star
for dynamic addressing).  I have a Mac SE with a EtherSC on it, and I've
had lots of periodic crashes with NCSA.  Usually it will happen after many
hours of running NCSA, or several launches of it.  Lately it's settled down,
and I _do_ realize that it could be any one of a million other things, but
it always seemed to somehow be related to NCSA.  I'm using v2.3, and I guess
now is the time to at least mention it - perhaps there are others like your-
self and myself out there who have had this problem but have ignored it like
I have, thinking that it was merely some init conflict or other...  Ideas?
Questions?  Comments?  Post or Email - whatever's easier for you.

-- 
----- Steve Lemke, Engineering Quality Assurance, Radius Inc., San Jose -----
----- Reply to: radius!lemke@apple.com    (Coming soon: radius.com ...) -----