You're not the only one to run into this problem.
The solutions that involve splitting the print job into multiple print
jobs, via xargs or other means, do work. But if you need your multiple
files to be printed in sequence with perfect accuracy, you can't use
multiple jobs. There's no guarantee those multiple jobs will print in
first-in, first-out sequence, especially if you're using a separate
spooling server.
The only solution I've found is to cat all the print files into one big
wad, and then "lpr" the big wad. The burden is on you to insert any
printer control language between files in the big wad. It's not a pretty
solution, but the problem was designed into RFC1179 in the first place.
Phillip Griffith (803) 952-8776
Information Technology Department
Westinghouse Savannah River Company
Robert McCallum <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/27/2000 04:18 PM
Please respond to lprng
To: [EMAIL PROTECTED]
cc:
Subject: Re: LPRng: 52 job limit!!!
hey thanks...
I was not sure if this list even worked.
I guess I don't get my own submissions like with the other lists I am on.
thanks for the workaround... is this 52 file limit in LPRng or is it some
other
dependency??
I cannot believe that no one else has had this problem.
thanks for the help.
Robert
Avery Earle wrote:
> Not a fix but a workaround ......
>
> cd /tmp/labels
> for f in lab* ; do
> lp -dlabel2 $f
> done
>
> On Thu, Jul 27, 2000 at 10:37:01AM -0500, Robert McCallum wrote:
> > hello,
> > I just installed LPRng and I think it is great, however I am not sure
> > how to get past this 52 request limit...
> > I really need to .. for a cron job that I have to print all the labels
> > that sit in a directory each night...
> > it is a simple script
> >
> > cd /tmp/labels
> > lp -dlabel2 lab*
> >
> > of course this fails with...
> > Fatal error - Sorry, can only print 52 files at a time, split job up
> >
> > can I get around this limitation??
> >
>
>
-----------------------------------------------------------------------------
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the
impatient,
> to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
> with: | example:
> subscribe LIST <mailaddr> | subscribe lprng-digest
[EMAIL PROTECTED]
> unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems, send email to [EMAIL PROTECTED] with the
word
> LPRNGLIST in the SUBJECT line.
>
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the
impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the
word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
