Bug 24065 - Drucker- Policies werden im pykota Backend nicht aktualisiert
Drucker- Policies werden im pykota Backend nicht aktualisiert
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Printserver - pykota
UCS 3.0
Other Linux
: P5 normal (vote)
: UCS 3.2-x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-14 14:56 CEST by Felix Botner
Modified: 2018-04-14 13:34 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2011-10-14 14:56:47 CEST
Damit die Policy, die für Benutzer oder Gruppen per UDM gesetzt werden, im Pykota ankommen, verwenden wir 

policy: external(/usr/sbin/univention-printquota-setuser user printer

in /etc/pykota/pykota.conf. Wenn ein Benutzer druckt, wird über das Script /usr/sbin/univention-printquota-setuser die UDM Policy für den Benutzer ausgewertet und per edpykota im Pykota gesetzt. Dieses Kommando führt er aber nur aus, wenn

  # Default policy to apply when either :
  #
  #       - Printer doesn't exist in PyKota's database
  #       - User doesn't exist in PyKota's database
  #       - User has no quota entry for this Printer in PyKota's database

Wir eine bestehende UDM DruckQuota Policy für einen Benuzter geändert, der schon eine Quota im Pykota Backend hat, wird die neue Richtlinie also nicht angewendet.

Hier muss man sich überlegen, wie man die Richtlinie des UDM und die Konfiguration in pykota synchron hält.
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:38:16 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:08:47 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.