Bug 24640 – Tag UCR variables as Samba3 / Samba4 specific in description

Bug 24640 - Tag UCR variables as Samba3 / Samba4 specific in description


Summary:	Tag UCR variables as Samba3 / Samba4 specific in description

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-11-15 20:46 CET by Stefan Gohmann
Modified:	2020-07-03 20:51 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
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):	Cleanup
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 Stefan Gohmann

2011-11-15 20:46:48 CET

Es sollte eine Unterscheidung der Variablennamen oder zumindest der Beschreibungen geben:

> Ich halte es für wichtig bei den UCR-Variablen kenntlich zu machen, welche
> nur mit Samba3 und welche nur mit Samba4 funktionieren. Da ein umbenennen
> der Variablen zum jetzigen Zeitpunkt sehr aufwändig wäre würde ich
> vorschlagen, das zumindest in den Beschreibungen zu integrieren?

Comment 1 Arvid Requate

2011-11-24 22:10:00 CET

Bei der Gelegenheit kann man dann mal die unbenutzte UCR-Variable samba4/debug/level aus univention-samba4.univention-config-registry-variables herausnehmen.

Comment 2 Ingo Steuwer

2020-07-03 20:51:56 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have 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 it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.