Client stops print queue

Question

I have approx 150 Panther and Tiger clients, both using Ethernet and 802.11G, print-served by a G5 Tiger Server. Often, a client user unintentionally somehow manages to stop the print queue, stopping print-services to that particular printer altogether. In order to find the offending client, I need to go around to each client to look for a printer icon in the Dock with a red exclamation point. Once found, I can restart the print queue from this client.
My questions are:
1) None of my users are advanced enough to purposefully stop the print queue. Is there a keyboard shortcut or print menu item that is easy to push by mistake - in other words, how can it be that my users repeatedly manage to accidentally stop my print queue? And how can set up my client to prevent accidental stops?
2) Is there a way I can restart the print queue from the server? Finding the offending client again and again can get a little tedious, and requires me to be present and available to do so, as none of my users are trained to restart the print queue from client.
Any thoughts are appreciated.
Regards,
Sigurd
G4 iBook, G4 iMac Mac OS X (10.4.5)
iBook G4, iMac G4, OSX Server   Mac OS X (10.4.5)  

Answer 1

Ah! This is what I had running:
#!/bin/bash
# This program deletes files older than 1 hour in /var/spool/cups
# and older than 5 minutes in /var/spool/cups/tmp .
# It also repairs permissions on SAMBA spool (for Windows printer sharing)
/usr/bin/find /private/var/spool/cups/ -type f -mmin +60 -delete
/usr/bin/find /private/var/spool/cups/tmp/ -type f -mmin +5 -delete
chmod 777 /var/spool/samba
Combine it with..
#!/bin/bash
/System/Library/StartupItems/PrintingServices/PrintingServices stop
rm -R /private/var/spool/cups/*
mkdir /private/var/spool/cups/tmp
/System/Library/StartupItems/PrintingServices/PrintingServices start
/usr/bin/enable `lpstat -p | grep 'disabled' | awk '{ print $2 }'`
And it might take care of itself.