Hi,

I just want to warn people that in some circumstances, using "tobyte"
can result in the tobyte process running wild, creating an output
file of many megabytes (and possibly up to 4 GB), eating CPU while it's
happening.

I reported this in 1999, and it was dropped (I can't find a Call ID).

I reported it again in April of 2000 (Call ID 3100150578), and just
noticed that it was closed *WITH NO EXPLANATION*.

I've encountered the tobyte problem on 5.0, 5.5, 6.0, and (IIRC) 6.5.
(I'm not 100% sure about 6.5).  It was generally on a tobyte
of the form "tobyte -at /S/G/A foo.txt" (I.e., ASCII, truncate)
And, it seems to happen about one time out of 200...
but is generally not repeatable.

(If anyone is encountering the problem, I have a sort-of-clone
"tobyte" called "sstobyte", available for free at
http://www.allegro.com/software/hp3000/allegro.html)



Side comment: please...don't accept it if a call is closed with
no explanation!

Yes...I've submitted another call, complaining that the first call
should not have been closed.

--
Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler