🚀 go-pugleaf

kitty.UUCP!Larry (Larry Lippman) Writes:

|1.	There is no reason why more than one printer name cannot be associated
|with _one_ physical printer using _one_ physical I/O port.  The usefulness
|here is to invoke the _same_ printer in a different fashion merely by
|specifying a different printer name as an lp(1) argument.  For example,
|one name will invoke a laser printer for landscape printing (132 cols wide),
|with another name will invoke the laser printer for portrait printing (80
|cols wide).  The different setup commands for the laser printer are contained
|in the individual /usr/spool/lp/interface/printer_name shell scripts.

I can think of one reason NOT to do just this....The lpsched program 
just checks to see if a job is currently printing on the named printer.  It
DOESN'T check to see if the physical port is busy.  At least on SYSV 2.0, 2.1
			    ---------------------

So if you haven't figured this one out....If you have two printers with 
different names (lp1 and lp2) connected to the same physical I/O port (tty11)
then lpsched will print both jobs at once...

I patched our lpsched program so that it will check to see if there are ANY
printers busy which are connected to the  same physical port as the requested 
printer.  Other than that, I really like setting up printers this way....
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
John Lengeling			UUCP: {cepu,ihnp4,uiucdcs}!bradley!john
Bradley University		ARPA: cepu!bradley!john@CS.UCLA
Text Processing 		PH: (309) 677-2230
Bradley Hall Room 6F
Peoria, IL 61625