> From [EMAIL PROTECTED] Fri Jul 28 06:44:03 2000
> From: [EMAIL PROTECTED]
> Date: Fri, 28 Jul 2000 08:43:18 -0400
> Subject: Re: LPRng: 52 job limit!!!
> To: [EMAIL PROTECTED]
>
> 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
Ummm... I have a solution... but you cannot use it with non-LPRng
hosts. Effectively, I extend the job format to be:
dfXXXnnnHHH where XXX are letters.
Note that I think that RFC1179 might have wanted this.
This is in the commercial distribution, as I want to control the
distribution of this totally non-compatible extension as much as
possible...
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
