🚀 go-pugleaf

----------------------------Original message----------------------------
When I _use_ to run PC labs, I found that restrictions only resulted in
Agro and clever work-arounds. So if you like headaches or want your
students to push you to your technical limit - enforce restrictions.

My suggestion is perhaps not loading the INTERNET software on some
machines, and imposing timelimits on the units say 1 hour in peak periods.
If students install the INTERNET software on these units place the units
on their own subnet and configure subnet on your routers for WAN only
access.

A possible solution for enforcing the 1 hour time limit - Under Novell give
the units two generic account IDs eg. ODDS and EVENS use SYSCON's
time restrictions and give ODDS 1 hour On , 1 hour Off and give EVENS
the alternate hours. WATCHDOG will give them 5 minutes notice before
disconnecting them. Of course those students who don't start on the
hour won't get a complete hour.

Generally I found that most students would give up their computer when
asked. But I got mildy miffed having to ask (because some students wont
ask themselves). Especially when the newly placed student fired up an
IRC session. I did have to disconnect my LAN from the WAN when a lab
of IRC'ers wouldn't shift - but after the second time they figured out I
was as stubborn as them.

*Enjoy*

Patrick Ryan
Prospect Energy
email: ryan@prospect.com.au
from 31st January 1996
soon: pryan@zip.com.au