{5} Accepted, Active Tickets by Owner (Full Description) (14 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

jerome (14 matches)

Ticket Summary Component Milestone Type Created
Description
#4 Support for CUPS' unix domain sockets pkipplib None enhancement 06/11/08

pkipplib doesn't support to communicate with CUPS through unix domain sockets, but only through inet domain sockets. This is problematic when people forbid their CUPS+PyKota server to listen to 127.0.0.1.

#5 Encryption support pykoticon None enhancement 06/11/08

PyKotIcon? doesn't encrypt datas when dialoguing with pknotify (or other compatible applications). This is mostly a problem when 'pknotify --checkauth --ask "Password:password"' is used, because the password will fly unencrypted over the network.

#11 Add a minimal cost per page when using ink accounting pykota 1.27 final enhancement 06/11/08

With ink accounting almost empty sheets are accounted for almost no credits. A base price per page could be used to set a minimum. Alternatively, the actual computation formula could be modified.

#12 Revamp the LDAP schema pykota None enhancement 06/11/08

The actual LDAP schema is overly complex : PyKota user account and user's balance are split in two for no valid reason. Last job of each printer is not stored in the printer object itself for no valid reason, and so on...

#13 Improve the relational schema pykota None enhancement 06/11/08

Additional informations could be stored, like the account balance's value at the time a job was printed, the details of the printed pages (format, orientation, duplex mode...)

#15 Allow to disable a particular print quota entry without deleting it or disabling the entire user account. pykota None enhancement 06/11/08

To entirely forbid an user to print, one can use pkusers --limitby noprint theUserName, but unfortunately there's currently no way to forbid an user to print but only for a particular printer.

#22 Add support for CUPS' CUPS_FILETYPE environment variable. pykota None enhancement 09/18/08

An enhancement request (CUPS STR 2799) I had submitted for CUPS has been implemented in CUPS' r7962 : the CUPS_FILETYPE environment variable available to the cupspykota backend (to any backend in fact) contains 'job-sheet' for a banner page, and 'document' for the real job.

This means that PyKota can now account differently banner pages and jobs.

#27 Can not set the Maximum Job Size(kBytes) pykota None enhancement 10/23/08

PyKota can not set the maximum job size allowed to printer to kBytes per job instead of pages. The CUPS command "lpadmin" just has quota control, the "job-k-limit" base on "job-quota-period". In other words, we can set the maximum job size for a period, and can not set the maximum job size for a single job.

#51 Export additional environment variables pykota 1.27 final enhancement 01/21/10

It would be useful to export additional environment variables, like for example the current user's email address as read from PyKota's database.

#53 SNMP accounter for HP designjet pykota enhancement 03/25/10

HP Designjet har the ability to report paper and ink usage. The attached diff shows how I read the used paper area (in square inch) and convert to A4 pages.

//Bse

diff /usr/lib/python2.4/site-packages/pykota/accounters/snmp.py snmp_designjet.py.work.without_extra_sleepdelay 56a57

pageAreaOID = "1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.12.2.5.1.0 "

94c95,96 < defaultErrorMask = 0x4fcc # [ 'No Paper', ---

#defaultErrorMask = 0x4fcc # [ 'No Paper', defaultErrorMask = 0x0 # [ 'No Paper',

285c287 < tuple([int(i) for i in pageCounterOID.split('.')]), \ ---

tuple([int(i) for i in pageAreaOID.split('.')]), \

320c322 < req.apiAlphaGetPdu().apiAlphaSetVarBindList((pageCounterOID, ver.Null()), \ ---

req.apiAlphaGetPdu().apiAlphaSetVarBindList((pageAreaOID, ver.Null()), \

400c402 < return acc.protocolHandler.retrieveInternalPageCounter() ---

return int ( acc.protocolHandler.retrieveInternalPageCounter() / 96.7 )

410c412,413 < print "Internal page counter's value is : %s" % pagecounter ---

#print "Internal page counter's value is : %s" % pagecounter print "%s" % pagecounter

#2 Incorrect handling of PJL statements pkpgcounter None defect 06/03/08

PJL statements appearing, at least, in PCL3/4/5 and PCLXL jobs, before the content of the very first page are not correctly taken into account. They are correctly parsed, but not used when computing number of copies and default page formats...

See this thread in Jasmine's mailing list : http://www.mail-archive.com/jasmine@ml.free.fr/msg00179.html

Fix is on the way... since December of 2007. PJL parser has been improved, but nothing committed just yet.

#39 pkpgcounter fails to read PJL-wrapped postscript pkpgcounter 1.27 final defect 02/24/09

Hi,

this is a copy of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515184, to be tracked in the proper tracker.

Summary: Some ppds create PJL headers for their postscript. This is passed py pkgpgcounter to ghostscript unmodified, causing it to fail.

A solution would be to detect the presence of these headers and strip them before sending the file to ghostscript. A simple striper (in perl) is in the patch http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=pkpgcounter.patch;att=1;bug=515184

Greetings, Joachim

#26 Switch autocommit mode off for relational backends. pykota None enhancement 10/04/08

Some RDBMS don't have an explicit way to begin a transaction (like DB2). Actually all relational backends set automatic commit mode to on, but this won't be possible for DB2 and probably other backends. PyKota's code must be changed to handle this problem which prevents PyKota from being ported to other RDBMS.

#34 Die gracefully or print when database is not available pykota None enhancement 12/05/08

When the cupspykota backend runs, we know that we need read+write access to the database. Introduce a printingwithnodb directive which allows either print or fail (and possibly ignore which is fail with an exit(0)), as values in pykota.conf. This directive will let PyKota know if it has to fail (as it does actually), or print anyway if the database isn't available.

Note: See TracReports for help on using and creating reports.