HP Visualize J210XC IRIX to HP-UX Migration Guide - Page 54
Stopping and Restarting the lp Spooler
View all HP Visualize J210XC manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 54 highlights
Printers # reject -r"Use alternate printer." laser1 4. (Optional.) Determine if there are any jobs in the printer's queue. For example: # lpstat -o laser1 5. (Optional.) Move all pending print requests in the request directory for the printer class to another printer or printer class. For example: # lpmove laser1 laser2 6. Remove the printer class. For example: # lpadmin -xlaser1 7. Restart the lp spooler: # lpsched 8. When you remove a printer class, the printers in the class are not removed; you can still use them as individual printers. But, if you remove all individual printers from a class, that printer class is automatically removed. Stopping and Restarting the lp Spooler Typically, the lp spooler is started during the boot process. (To change the boot-up procedure by not starting the scheduler, edit the file /etc/rc.config.d/lp and set the shell environment variable lp to 0). The spooler must be stopped whenever the spooling system needs modification (such as when adding or removing a printer). Subsequently, the spooler must be restarted after the modification has been made. You can use either SAM or HP-UX commands to stop or start the lp spooler. If you use HP-UX commands to stop the lp spooler, follow these steps: 1. Become superuser with the su command or login as root. 2. Check for requests printing or being sent to a remote printer (it is best to wait until requests finish printing before stopping the lp spooler). # lpstat -o -i In the above command, the -i option inhibits the reporting of remote requests (that is, lpstat will only show local requests). 3. Stop the lp spooler: # lpshut When lpshut is executed, all requests will be stopped, but will remain in the print queues. 4. Restart the lp spooler: # lpsched 5. When the spooler is restarted, the requests in the print queue will be completely reprinted, regardless of how much of the request was printed prior to the shutdown. 49