This info describes the link between Pcounter and WolfPrint. Plans are to decommission Pcounter on or about July 1, 2009. Here's the old data, cut and pasted about:

Keeping Things In Sync

Generally every transaction in wolfprint land is proceeded with a call to lp_ndssync. This stored procedure simply inserts a username into a table in the lpquota database (aptly named ndssync), which a job reads routinely to process usernames, read in their current quota from the lpquota database, and set NDS to have the same quota. Visa versa, there are jobs that run under the Windows (NDS?) servers to watch the PCounter logs and sync up jobs printed there with the unix lpquota database. Generally we try to sync anytime anything occurs. It doesn't hurt to cause the sync so we consider it an easy thing to do. Looking users up in user lookup even causes a sync.

Print Servers

The print servers are a mixed batch. The primary print.ncsu.edu servers are run on a collection of unix print servers, whereas the Windows jobs go to NDPS servers. Unix and Mac all print to the unix servers.

Windows

The Novell servers running NDPS and Pcounter are named ndsXXps.unity.ncsu.edu .  The sysnews tool will tell you which Novell server is handling a particular queue.

There are NDPS print servers that handle the real work. A product called PCounter handles charging for pages printed. A printsync job runs on a particular server that reads in all of the logs from PCounter and syncs up print records with the lpquota database.

The print syncronization runs on a virtual machine printsync.unity.ncsu.edu .

There is a mini-web interface that the printer status page can talk to to remove jobs and check queues and such. Not all printers in the unix environment are available/supported in the Windows environment.