brad@bradley.UUCP (02/27/87)
We have a printronix mvp printer with the IGP board. I would like
to set it up so that we can have the printer do 10,13.3,15,17 pitch
on the same printer. I have 4 different filters to do the print
pitch change, and for different printers listed in the /etc/printcap,
each with its own spool directory. the problem is that if the printer
is printing 10 pitch and you send something at 15pitch either 2 things
happen. 1. the job 15 pitch doesn come off or 2. it goes to the bit
bucket and I never see (not even on the printer).
I did move one bit of code. in printjob.c that has to do with the
execlusive open with didn't seem to be called because before this
printouts would be printed at the same time.
I also put the spool directorys to the same (/usr/spool/lpd) and that
worked fine, but if the printer was sending something, your printout
would come out in that pitch.
thanks
Bradley Smith UUCP: {cepu,ihnp4,noao,uiucdcs}!bradley!brad
Text Processing ARPA: cepu!bradley!brad@UCLA-LOCUS
Bradley University PH: (309) 677-2337
Peoria, IL 61625jerry@oliveb.UUCP (03/05/87)
In article <8300001@bradley> brad@bradley.UUCP writes: >on the same printer. I have 4 different filters to do the print >pitch change, and for different printers listed in the /etc/printcap, >each with its own spool directory. the problem is that if the printer >is printing 10 pitch and you send something at 15pitch either 2 things >happen. 1. the job 15 pitch doesn come off or 2. it goes to the bit >bucket and I never see (not even on the printer). I have the same problem, wanting to access the same printer device with two entirely different filters. This results in nothing but problems if jobs are placed in both queues at the same time. My solution is to make the "lock" file in each additional spool directory a symbolic link to the lock file of the first spool directory for that device. This eliminates the problem of multiple daemons attempting simultainious access to the same device. I suspect that there are problems with this as the daemon may finish the first queue and leave files in the other queue unprocessed until something starts the daemon for that queue. There really needs to be some more flexable software that allows multiple printers for one queue and multiple queues for one printer.