msc@qubix.UUCP (Mark Callow) (11/04/83)
The newly distributed version of vnews certainly solves a lot
of problems. for example it always refreshes the screen correctly.
However it seems to use huge amounts of CPU time when it is
sitting idle waiting for a command. I have had a quick poke
through the source but I can't see anything significantly
different from the original vnews in that area of the program.
Does anyone know what it's doing to use all that CPU time.
As an illustration, yesterday someone forgot to exit vnews and
logout when they went home. After 6hrs 45mins of idle time,
ps reported that the vnews had used in excess of 200 minutes (!!)
of cpu time.
--
Mark Callow, Saratoga, CA.
...{decvax,ucbvax,ihnp4}!decwrl!
...{ittvax,amd70}!qubix!msc
decwrl!qubix!msc@Berkeley.ARPA