Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!rochester!udel!burdvax!bpa!asi!metro
From: metro@asi.UUCP (Metro T. Sauper)
Newsgroups: comp.bugs.sys5
Subject: Re: SysV lp spooler a security hole
Message-ID: <108@asi.UUCP>
Date: Tue, 15-Sep-87 21:26:56 EDT
Article-I.D.: asi.108
Posted: Tue Sep 15 21:26:56 1987
Date-Received: Fri, 18-Sep-87 06:26:40 EDT
References: <313@pvab.UUCP> <15000001@bradley>
Organization: Assessment Systems, Inc., Philadelphia, PA
Lines: 34
Summary: It works for me.

In article <15000001@bradley>, john@bradley.UUCP writes:
> 
> 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. 
> | .....
> 
> 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
> 			    ---------------------
> ........
>
> John Lengeling			UUCP: {cepu,ihnp4,uiucdcs}!bradley!john


Funny, we do EXACTLY this (define to spooler printer to the SAME tty port).
We don not have any problem what-so-ever with two spooled jobs printing at
the same time.  In fact, I got the impression that this was the way it was
suppose to work.

We use this feature to handle forms output to the printer.  On our system
we have LP1, LBLS2, LICS1, REN1, and WIDE1 all defined to the same printer.
Normally only the one device is enabled which corresponds with the type
of forms currently in the printer.  In the case of WIDE1 however, we also
enable LP1 which lets normal printed output print also.  We have never
had a conflict.


-- 
Metro T. Sauper, Jr.                              Assessment Systems, Inc.
Director, Remote Systems Development              210 South Fourth Street
(215) 592-8900                 ..!asi!metro       Philadelphia, PA 19106