3 ms·
At GATech in the 90s/early 00s (can't speak to today) they used a unit of computational resource on the remote login systems called "bananas". You had a finite
by Jtsummers 13y ago
At GATech in the 90s/early 00s (can't speak to today) they used a unit of computational resource on the remote login systems called "bananas". You had a finite number of them. Staying logged in 24x7 throughout the semester but doing nothing else, you'd essentially use 0. Printing off something (they had, again can't speak to the present situation, a great printing service) might use up 0.01 bananas as a measure of the CPU time it took to submit the job. The effect was to mete out the limited computational resources. This wasn't 100% effective, but greatly discouraged abuse of the system (you had to go before the admins to ask for extra bananas).
The main way to bypass it: bananas weren't deducted until the job completed. If you had a long-running task, or a program caught in an infinite loop, you could leave it running indefinitely and take the hit at the end of the term or just postpone the hit until it was more convenient for you to go ask for forgiveness.
EDIT: And a note, this was not established on every computer system on campus. Just one of the more commonly used non-major systems.