Bug 29892 – more than one input fields for VFS object options on SAMBA shares

Bug 29892 - more than one input fields for VFS object options on SAMBA shares


Summary:	more than one input fields for VFS object options on SAMBA shares

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Shares
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-12-28 21:19 CET by Tobias Scherer
Modified:	2017-08-08 07:09 CEST (History)
CC List:	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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tobias Scherer

2012-12-28 21:19:04 CET

As reported on the forum
http://forum.univention.de/viewtopic.php?f=56&t=2180
it would be good to have more than one input field for VFS object options on SAMBA shares in the UMC shares modul.

Comment 1 Arvid Requate

2013-07-16 10:19:56 CEST

Workaround already published in the forum:

> You should be able to add your parameters in the GUI by putting them into the fields under:
> Shares:<sharename> -> [Advanced settings] -> Samba custom settings -> Custom share settings
> Here you can provide multiple key = value pairs.


But the customer reported back one remaining issue, which might be worth fixing:

> I noticed that one of the pairs did not work right away.
> When I added the pair "vfs objects = recycle", it removed "vfs objects = acl_xattr"

Comment 2 Arvid Requate

2013-07-16 10:30:14 CEST

The acl_xattr issue is now split off as Bug 31982, so this remains an enhancement bug.

Comment 3 Stefan Gohmann

2017-06-16 20:38:27 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 4 Stefan Gohmann

2017-08-08 07:09:49 CEST

This issue has been filed against UCS 3.1.

UCS 3.1 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.