Very Computer

Scenario:
I currently have a Compaq pentium 100 w/ 80mb ram and 2gig hd.  I have
about 40 (wy-50) users that telnet into the server (to use a order entry
system) from two serial port servers.(Computone Intelliservers)  At any
point during the day if I look into CPU utilization it is running extremely
high 90-100%.  If (using SCO Doctor Lite) I look at the processes using the
CPU, the telnet daemon (telnetd) seems to be peaking ~90-100% of the CPU
usage leaving none for the main database app the users are trying to
access.  I am expecting a CPU upgrade in the VERY near future.

Until then, Questions:
The only other way, besides telnet,  I see to configure the ports is by
using rlogin.  Is there any advantage, disadvantage to this option?  Am I
going to see other resources take the place of the telnet daemon if I use
rlogin?  Is one more efficient than the other?

I hope this question isn't too stupid.  Any advise will be greatly
appreciated.  Thanks in advance.

Heath Coleman

telnetd should only be consuming a lot of CPU if a lot of data is being
pushed through it.  Is a tremendous amount of screen I/O going on?  (It
would basically have to be continuous.)

Otherwise -- I haven't played with Doctor, but it sounds like it's
lumping together all instances of telnetd?  Use `ps -ef | awk '$4>0'` as
a quick check.  Processes that show up are those that have consumed any
CPU time in the last second or two.  The "C" column shows how much each
consumed.  Do you see one or more telnetd processes "spinning"?  Kill
those, leaving alone any telnetd's which aren't consuming lots of CPU
time.

If that's the problem, the next step is to figure out why -- under what
circumstances does telnetd get into a spin.

Quote:>Bela<