Bug 18336 - Falsches parsing von sambaCustomSettings
Falsches parsing von sambaCustomSettings
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Shares
UCS 2.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks: 43768
  Show dependency treegraph
 
Reported: 2010-05-06 13:56 CEST by Janis Meybohm
Modified: 2022-06-30 14:38 CEST (History)
3 users (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 Janis Meybohm univentionstaff 2010-05-06 13:56:39 CEST
2010050310000386

# udm shares/share modify --dn cn=valwrite,cn=qamaster.univention.qa,cn=shares,dc=univention,dc=qa --append sambaCustomSettings='some = @"New Value", more'

# ldapsearch -x -LLL cn=valwrite  univentionShareSambaCustomSetting
dn: cn=valwrite,cn=qamaster.univention.qa,cn=shares,dc=univention,dc=qa
univentionShareSambaCustomSetting: some = @ = New Value

Wenn ich das über den UDM-Web setze:

univentionShareSambaCustomSetting: some = @"New Value", more
Comment 1 Arvid Requate univentionstaff 2013-07-24 21:03:46 CEST
This problem popped up again during my attempt to override the "vfs objects" parameter for some share via sambaCustomSettings. With current Samba code (3.6.8 and 4.0.3) the following workaround was possible which uses tabs instead of spaces to avoid splitting at the wrong locations:

eval "$(ucr shell)"; \
udm shares/share modify \
   --dn "cn=opsi_depot,cn=$(hostname -f),cn=shares,$ldap_base" \
   --set sambaCustomSettings="$(printf 'vfs\tobjects \t')"

This sets "vfs<tab>objects = <tab>" in the correspoding samba share subfile. Samba accepted this setting.
Comment 2 Stefan Gohmann univentionstaff 2014-02-18 21:37:39 CET
This issue has been filed against UCS 2.3.

UCS 2.3 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".
In this case please provide detailed information on how this issue is affecting
you.