Bug 37017 - cups-printers listener doesn't properly reload samba
cups-printers listener doesn't properly reload samba
Status: NEW
Product: UCS Test
Classification: Unclassified
Component: Printserver
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on: 36578
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-26 07:08 CET by Stefan Gohmann
Modified: 2018-04-14 13:34 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
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 Stefan Gohmann univentionstaff 2014-11-26 07:08:59 CET
Please check if a test case is possible.

+++ This bug was initially created as a clone of Bug #36578 +++

The cups-printers listener doesn't properly reload samba:


10.11.14 16:26:09.638  LISTENER    ( WARN    ) : cups-printers: info: univention-lpadmin -u allow:all -o auth-info-required=none -p printer1dcs -v file:/tmp/printer1dcs -E
Reloading /etc/samba/smb.conf: smbd.
Usage: /etc/init.d/samba-ad-dc {start|stop|restart|force-reload|status}


This causes issues with default samba printer share options not getting applied (like "force printername").
Comment 1 Arvid Requate univentionstaff 2014-11-26 12:04:21 CET
Please note that the reload was actually done (line "Reloading /etc/samba/smb.conf: smbd."), but it was attempted to also do a "reload" on the  samba-ad-dc init script, which is not a valid option. So that was an irritating message.

I think this was more a "one off" issue which occurred because "somebody" (maybe me) replaced all occurrances of of /etc/init.d/samba4 by /etc/init.d/samba-ad-dc for the Samba 4.2 update.

The real issue that I fixed for Bug 36578 is that the cups-printers listener did not commit /etc/samba/smb.conf, which causes the samba printer share definitions not to be included in case the first printers are created while the central /etc/samba/printers.conf itself has not yet been included in the smb.conf. This causes subtle errors: The printer shares are visible because samba automatically determines them from CUPS, but the printer share options in /etc/smb/printers.conf.d/* (like "force printer name") are not activated.

That's what should be testet here.