According to CHANGES:
> If you want to use force_lpq_status according to the docs (HOWTO), the
> following patch has to be applied. Otherwise it doesn't work when you have
> several ip netmasks listed as in the example:
> force_lpq_status=s=pc*.eng.com,130.192.12.0/24,l=sun*.eng.com
> Change is:
> - Split(&l,t,Value_sep,0,0,0,0,0,0);
> Value_sep DEFINE( = " \t=#@" );
< + Split(&l,t,File_sep,0,0,0,0,0,0);
> File_sep DEFINE( = " \t,;:" );
> (Pointed out to me by: Henrik Edlund <[EMAIL PROTECTED]>)
The problem is that you changed Value_sep to File_sep a few lines above
the specified one above. Hence the implementation is even more broken now.
The following patch to lpd_status.c against 3.8.22 fixes the mis-patching
and makes force_lpq_status work again:
for(i = 0; i < listv.count; ++i ){
s = listv.list[i];
- if( (t = safestrpbrk(s,File_sep)) ) *t++ = 0;
+ if( (t = safestrpbrk(s,Value_sep)) ) *t++ = 0;
Free_line_list(&l);
- Split(&l,t,Value_sep,0,0,0,0,0,0);
+ Split(&l,t,File_sep,0,0,0,0,0,0);
DEBUGF(DLPQ1)("Job_status: Force_lpq_status '%s'='%s'", s,t);
if( Match_ipaddr_value( &l, &RemoteHost_IP ) == 0 ){
DEBUGF(DLPQ1)("Job_status: forcing status '%s'", s);
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
