It appears that the 'mx=' parameter is ignored in router queues. For example, a router queue with 'mx=5000' in its printcap entry will pass a 10MB print job to a destination queue.
If the destination queue has 'mx=5000' in its printcap entry, the 10MB print job will be removed. Since I'm interested in using the 'mx=' parameter to avoid having my spool partition fill up, I would prefer that the job be terminated by the original receiving queue as soon as the maximum number of bytes is received. This also provided better feedback to the client which is submitting the job. Please let me know if I'm missing something. Thanks, -Rick -- |Rick Cochran phone: 607-255-7618| |Cornell CIT - Systems & Operations - Net-Print FAX: 607-255-8521| |730 Rhodes Hall, Ithaca, N.Y. 14853 email: [EMAIL PROTECTED]| ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address 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. -----------------------------------------------------------------------------
