Bug 13456 - in manpage 'usershare max shares' default value is wrong.
Summary: in manpage 'usershare max shares' default value is wrong.
Status: RESOLVED INVALID
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 4.5.12
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba Documentation QA Contact~
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-29 15:45 UTC by Marco Gaiarin
Modified: 2018-05-30 08:14 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Gaiarin 2018-05-29 15:45:43 UTC
Manpage report:

 usershare max shares (G)

  This parameter specifies the number of user defined shares that are allowed to be created by users belonging to the group owning the usershare directory. If set to zero (the default) user
  defined shares are ignored.

  Default: usershare max shares = 0

but lie, because seems that the default values is '100'. Jeremy in 'samba' list sayed:

> It was set to 100 so that desktop Linux users could
> use the file manager to right click and "Share As.." by
> default without configuring the server. Did that back
> when I was in Novell selling SuSE Linux.

The difference is that 'usershare max shares = 0' disable usershare feature, so manpage say that is disabled while it is enabled by default.

Please, fix manpage. Thanks.
Comment 1 Karolin Seeger 2018-05-30 06:50:44 UTC
Thanks for the report, but on my Samba 4.8.1, the default is "0".

user@host:~$ testparm -sv | grep "usershare max shares"
Load smb config files from /etc/samba/smb.conf
Processing section "[share1]"
Loaded services file OK.
Server role: ROLE_STANDALONE

        usershare max shares = 0

So it's like described in the manpage.
Jeremy, would you like to comment on this one?
Comment 2 Andrew Bartlett 2018-05-30 07:49:09 UTC
Sorry, this is not a bug in Samba, but in the package of Samba.  Samba's defaults are verified during our make test, but that can't catch changes by distributors. 

Please file (eg) Debian bugs at bugs.debian.org.
Comment 3 Marco Gaiarin 2018-05-30 08:14:31 UTC
Sorry, i've never minded could be a packaging bug.

Louis fire up the proper debian bug:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900396