home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!vmsb.is.csupomona.edu!cvadrtbc
- From: cvadrtbc@vmsb.is.csupomona.edu (Srikanth Viswanathan)
- Subject: Re: NCSA telnet CPU usage
- Organization: California Polytechnic University, Pomona
- References: <1992Aug21.135137.1131@murdoch.acc.Virginia.EDU> <66529@hydra.gatech.EDU> <price.714418392@helios> <173cs0INNs9b@moe.ksu.ksu.edu>
- Message-ID: <23AUG199219041899@vmsb.is.csupomona.edu>
- News-Software: VAX/VMS VNEWS 1.41
- Distribution: usa
- Sender: news@ctr.columbia.edu (The Daily Lose)
- Date: Mon, 24 Aug 1992 03:04:00 GMT
- X-Posted-From: vmsb.is.csupomona.edu
- X-Posted-Through: sol.ctr.columbia.edu
- Lines: 14
-
- >>You need to play with the idle detect and the other parameter just above it
- >>on the DOS parameters list. Since NCSA telnet constantly polls to see what
- >>is happening, (as far as I can tell), you'll need to adjust the DOS session
- >>so reduce the priority in background.
- >
- >Well, at least when *I* adjust those settings, no change can be seen on
- >Pulse. It is kinda annoying to have everything slow down just because I
- >have a telnet window open.
-
- Is NCSA Telnet DV aware? If it is, you can get a program from hobbes
- called OS2SPEED and try that. It will reduce the hogging of the CPU
- by certain programs like GSZ.
-
- Srikanth
-