telnet sounds like a client runnign from the netbsd box.

	Good thing to run is 'ps axww | grep telnet' to get a ful listing
	of any arguments given to telnet.

	Also, 'netstat | grep telnet' will show you if anything is
	connected inbound or outbound to the default telnet port (this
	would not pick up if the telnet had been used to connect out
	to a mud or similar on a different port).


-- 
		David/absolute		-- www.netbsd.org: No hype required --


On Fri, 15 Jun 2001, Ray Phillips wrote:

> Dear NetBSD/i386:
>
> This morning I ran top on a PC which is running NetBSD/i386 1.5 and found a
> telnet process was using about 50% of the CPU.  There seemed to be no
> telnet session corresponding to it, so I killed the process.  Doing so
> didn't seem to cause any problems.  I've appended top's output before and
> after killing the process to this message.
>
> I assume the process was left over from when the Macintosh I was running a
> telnet session on crashed, but why would it have been using up so much of
> the CPU time; and why was that command named telnet instead of telnetd like
> the two near the bottom of the list?
>
>
> Ray Phillips
>
>
>
>
> Before:
> ------
> load averages:  2.33,  2.04,  1.59                                     12:04:53
> 14 processes:  2 runnable, 11 sleeping, 1 on processor
> CPU states: 55.7% user,  0.0% nice, 43.8% system,  0.0% interrupt,  0.5% idle
> Memory: 3712K Act, 1708K Inact, 144K Wired, 74M Free, 382M Swap free
>
>  PID USERNAME PRI NICE   SIZE   RES STATE     TIME   WCPU    CPU COMMAND
> 11259 root      64    0   204K  964K run     167.7H 49.07% 49.07% telnet
> 19038 ray        2    0   504K  220K sleep     2:15 25.29% 25.29% gunzip
> 19039 ray       62    0    56K  304K run       2:08 23.49% 23.49% tail
>   167 root      10    0   220K  420K sleep     0:08  0.00%  0.00% cron
>    84 root       2    0   100K  400K sleep     0:06  0.00%  0.00% syslogd
> 19057 ray       28    0   152K  604K onproc    0:00  0.00%  0.00% top
> 19041 ray       18    0   432K  292K sleep     0:00  0.00%  0.00% csh
> 17917 ray       18    0   432K  280K sleep     0:00  0.00%  0.00% csh
> 11172 root      18    0   428K  280K sleep     0:00  0.00%  0.00% csh
>     1 root      10    0   312K  192K sleep     0:00  0.00%  0.00% init
>   169 root       3    0    48K  436K sleep     0:00  0.00%  0.00% getty
> 19040 root       2    0   108K  960K sleep     0:00  0.00%  0.00% telnetd
> 17916 root       2    0   108K  960K sleep     0:00  0.00%  0.00% telnetd
>   164 root       2    0    76K  448K sleep     0:00  0.00%  0.00% inetd
>
> After:
> -----
> load averages:  1.75,  1.90,  1.60                                     12:07:41
> 13 processes:  2 runnable, 10 sleeping, 1 on processor
> CPU states: 85.1% user,  0.0% nice, 12.9% system,  0.0% interrupt,  2.0% idle
> Memory: 3400K Act, 1788K Inact, 136K Wired, 74M Free, 382M Swap free
>
>   PID USERNAME PRI NICE   SIZE   RES STATE     TIME   WCPU    CPU COMMAND
> 19038 ray       64    0   504K  220K run       3:34 51.12% 51.12% gunzip
> 19039 ray       64    0    56K  304K run       3:22 46.97% 46.97% tail
>   167 root      10    0   220K  420K sleep     0:08  0.00%  0.00% cron
>    84 root       2    0   100K  400K sleep     0:06  0.00%  0.00% syslogd
> 19062 root      28    0   152K  604K onproc    0:00  0.00%  0.00% top
> 19041 ray       18    0   432K  292K sleep     0:00  0.00%  0.00% csh
> 19059 root      18    0   432K  284K sleep     0:00  0.00%  0.00% csh
> 17917 ray       18    0   432K  280K sleep     0:00  0.00%  0.00% csh
>     1 root      10    0   312K  192K sleep     0:00  0.00%  0.00% init
>   169 root       3    0    48K  436K sleep     0:00  0.00%  0.00% getty
> 17916 root       2    0   108K  960K sleep     0:00  0.00%  0.00% telnetd
> 19040 root       2    0   108K  960K sleep     0:00  0.00%  0.00% telnetd
>   164 root       2    0    76K  448K sleep     0:00  0.00%  0.00% inetd
>
>
>