Bug 45458 - Misleading command description 'udm shares/share [...] --set group
Misleading command description 'udm shares/share [...] --set group
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Shares
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UDM maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-26 17:35 CEST by Nico Stöckigt
Modified: 2020-07-03 20:53 CEST (History)
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?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017092621000294
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 Nico Stöckigt univentionstaff 2017-09-26 17:35:58 CEST
The description - how to add a group to a share - is misleading

---8<---
shares/share variables:
  General:
    General directory share settings
        name (cmr)                               Name
        host (c)                                 Host
        path (c)                                 Directory
        owner                                    Directory owner of the share's root directory
        group                                    Directory owner group of the share's root directory
        directorymode                            Permissions for the share's root directory
--->8---

Due to there must be entered a guidNumber this should mentioned in the description!

--->
     group                                    Directory owner group of the share's root directory (guidNumber)
<---
Comment 1 Florian Best univentionstaff 2017-09-26 18:30:04 CEST
Well, and in UMC there is a username shown. Changing the description would make it irritating in UMC.
Comment 2 Ingo Steuwer univentionstaff 2020-07-03 20:53:30 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.