LPRng: rg entry in printcap - feature request

[Ashley GC]

Hey hey list,

The rg option works well for restricting a queue to a set of users 
according to their primary group, but would it be possible to check 
the user's additional groups, for example, I have:

[EMAIL PROTECTED] ~]$ id
uid=1200(ashley) gid=1300(admin) groups=1300(admin),1301(staff),1302(tech)

If I have :rg=admin: then I can print to the queue, but if I have 
:rg=staff: then I cannot.

Also, a negation option ( :rg=!students: ) would be very useful in 
order to avoid listing everyone-except-students.

As always, if I've missed something obvious, apologies and please 
point me to the correct documentation. And if a patch needs writing, 
I would be happy to do so.

Thanks in advance,
Ashley GC.



-
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.
-

accurate accounting without delay (Was: Re: LPRng: Username spoofing...)

[Ashley GC]

On Fri, 6 Feb 2004, Henrik Edlund wrote:

 See Appendix A on page 39 (PDF page 55) in
 http://www.ep.liu.se/exjobb/ida/2003/dd-c/019/exjobb.pdf where I wrote
 some stuff about it.
 
 Henrik

Thanks for that. I read most of your paper, and you seem to be doing 
what we're trying to do, namely:
- counting pages successfully printed by the printer, not pages in the 
  job
- use SNMP instead of proprietary solutions to collect info from the 
  printer

The problem I have is that synchronous printing and page 
counting causes a 17 second delay between jobs, due to the time taken 
between end of spooling and the first page coming out, which is due to 
the long paper path of our HP LaserJet 8150.

I've drawn a diagram:
http://www.dcs.warwick.ac.uk/~csuwf/printing.pdf (there's a .ps too)

I have a solution currently being developed which involves using PJL 
to set the PJL-job-name of the job to the job-id (integer) from the 
print server. A filter will do this, then fork. The parent will return 
(so the server can immediately send the next job to the printer) and 
the child will be left alone to collect info from the printer about 
how the job did as and when it appears.
This should enable accurate job-based page counting, which means fast 
asynchronous printing with no delay associated with the paper path 
being emptied and refilled.

If anyone is interested in this, or has already implemented it, please 
let me know.

Ashley GC.
DCS, UoW, UK.


-
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.
-