| | 113 | * How can I share print quota between some printers only (not all) ? |
| | 114 | |
| | 115 | To do this you have to put the printers into a printers group, and |
| | 116 | set quota |
| | 117 | |
| | 118 | * What is a printer group ? |
| | 119 | |
| | 120 | A printer group is exactly like a normal printer, but is |
| | 121 | unknown by the printing system. You can use printer groups |
| | 122 | to share print quota between printers. |
| | 123 | |
| | 124 | * How can I create a printer group ? |
| | 125 | |
| | 126 | Just use edpykota, like for normal printers. |
| | 127 | |
| | 128 | * How can I put a printer into a printer group ? |
| | 129 | |
| | 130 | Use the new -G|--pgroups command line option to edpykota |
| | 131 | You can put sereval printers into several printers groups |
| | 132 | in one command using the following syntax : |
| | 133 | |
| | 134 | $ edpykota --pgroups pg1[,pg2,pg3,...] --printers p1[,p2,p3,...] |
| | 135 | |
| | 136 | What is between square brackets is optional. |
| | 137 | Both p1,p2 and pg1,pg2 can contain wildcards. |
| | 138 | |
| | 139 | * How quota checking and update is done with printer groups ? |
| | 140 | |
| | 141 | Print accounting and quota checking is done for a printer and |
| | 142 | all the printers groups it belongs to, recursively. |
| | 143 | If quota is reached on ANY of these printers for the current user, |
| | 144 | printing is denied. |
| | 145 | |
| | 146 | * Is this feature robust ? |
| | 147 | |
| | 148 | It should be. However, beware of integrity problems. LDAP has no |
| | 149 | sense of database integrity, and PostgreSQL constraints have not |
| | 150 | yet been fully implemented. The code actually *tries* to forbid |
| | 151 | circular printers groups, but if you create printer groups with |
| | 152 | another tool (e.g. psql or gq), then you are mostly on you |
| | 153 | own to not create infinite loops. |
| | 154 | |
