[Samba] static vs shared modules build

[Reindl Harald]

Am 17.03.2016 um 01:22 schrieb Miguel Medalha:
>>> surely, if i want it on all shares expect a single one
>
>>> [global] is for things you want without declare them in each and every
> share and so in the best case all of your shares just have
>
>>> [share]
>>>    path = /what/ever/dir
>
>>> and only list options where you differ from your global defaults
>
> Exactly. That's why an ADDITIONAL module on a particular share should not disable the module defined as a GLOBAL option. The behavior of the 3.x series was more correct.

*no*

the "=" sign of a option has really a unconditional meaning - frankly 
what you call "correct" is a fuzzy behavior and broken by definition

when i say "vfs objects = catia fruit streams_xattr" inside a share i 
mean *exactly* that and not "that and some random others"

https://www.mankier.com/8/vfs_fruit
"This module is not stackable other then described in this manpage"
proves the unpredictable and problematic behavior of what you call "correct"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba/attachments/20160317/a5fbef11/signature.sig>