make sprachenatelier working..

roles/common/templates/etc/cups/cups-browsed.conf.server.j2

@@ -1,4 +1,3 @@
-# {{ ansible_managed }}
 
 # All configuration options described here can also be supplied on the
 # command line of cups-browsed via the "-o" option. In case of
@@ -312,7 +311,7 @@ BrowseLocalProtocols CUPS
 
 # Set HTTP timeout (in seconds) for requests sent to local/remote
 # resources Note that too short timeouts can make services getting
-# missed when they are present and operations be unneccessarily
+# missed when they are present and operations be unnecessarily
 # repeated and too long timeouts can make operations take too long
 # when the server does not respond.
 
@@ -321,7 +320,7 @@ BrowseLocalProtocols CUPS
 
 # Set how many retries (N) should cups-browsed do for creating print
 # queues for remote printers which receive timeouts during print queue
-# creation.  The printers which are not successfuly set up even after
+# creation.  The printers which are not successfully set up even after
 # N retries, are skipped until the next restart of the service.  Note
 # that too many retries can cause high CPU load.
 
@@ -556,6 +555,23 @@ BrowseLocalProtocols CUPS
 # NewIPPPrinterQueuesShared Yes
 
 
+# How to handle the print queues cups-browsed creates when
+# cups-browsed is shut down:
+
+# "KeepGeneratedQueuesOnShutdown No" makes the queues being
+# removed. This makes sense as these queues only work while
+# cups-browsed is running. cups-browsed has to determine to which
+# member printer of a cluster to pass on the job.
+
+# "KeepGeneratedQueuesOnShutdown Yes" (the default) makes the queues
+# not being removed. This is the recommended setting for a system
+# where cups-browsed is permanently running and only stopped for short
+# times (like log rotation) or on shutdown. This avoids the
+# re-creation of the queues when cups-browsed is restarted, which
+# often causes a clutter of CUPS notifications on the desktop.
+
+# KeepGeneratedQueuesOnShutdown No
+
 # If there is more than one remote CUPS printer whose local queue
 # would get the same name and AutoClustering is set to "Yes" (the
 # default) only one local queue is created which makes up a
@@ -651,7 +667,7 @@ BrowseLocalProtocols CUPS
 
 # As DNS-SD service names are unique in a network you can create a
 # cluster from exactly specified printers (spaces replaced by
-# underscors):
+# underscores):
 
 # Cluster hrdep: oldlaser_@_hr-server1 newlaser_@_hr-server2
 
@@ -745,3 +761,11 @@ BrowseLocalProtocols CUPS
 # shutdown.
 
 # AutoShutdownTimeout 30
+
+# DebugLogFileSize defines the maximum size possible (in KBytes)
+# of the log files (cups-browsed_log and cups-browsed_previous_logs)
+# that is created using cups-browsed in the debugging mode.
+# Setting its value to 0 would turn off any restriction
+# on the size of the file.
+
+# DebugLogFileSize 300

roles/common/templates/etc/cups/cups-files.conf.j2

@@ -31,6 +31,10 @@ SystemGroup lpadmin
 #ConfigFilePerm 0640
 #LogFilePerm 00640
 
+< # Specifies the group name or ID that will be used for log files.
+< # The default group in Debian is "adm".
+< LogFileGroup adm
+
 # Location of the file logging all access to the scheduler; may be the name
 # "syslog". If not an absolute path, the value of ServerRoot is used as the
 # root directory.  Also see the "AccessLogLevel" directive in cupsd.conf.