> well, not sure - in fact you can configure each share with different > "vfs objects" and so configuration likely still is needed - i referred > more to my expierience with httpd where you don't need "LoadModule" > lines for static compiled modulesThere has been a change in the configuration/behavior of modules and their stacking and that change is not well documented. In previous versions of Samba that exact same acl_xattr module could be declared in the [global] section of smb.conf and it would apply to ALL the shares, as should be expected. I still have here a retired samba 3.2 server and it behaves in that way. This can be very practical if all your clients are Windows workstations, as is often the case. As a matter of fact, there was a general principle, even referred to in the Samba documentation, that global "G" parameters could be used only globally but share "S" parameters could be used both in shares and globally, in which case they would apply to all shares. This was very practical but seems to no longer be the case for Samba 4.x.> at the end i would say it's not worth at all to spend time with that > micro-optimization if there is any optimization at all and stick with > defaultsIt is worth spending that time in the sense that we can learn about the behavior of the software we rely on.
Am 15.03.2016 um 21:51 schrieb Miguel Medalha:>> at the end i would say it's not worth at all to spend time with that >> micro-optimization if there is any optimization at all and stick with >> defaults > > It is worth spending that time in the sense that we can learn about the > behavior of the software we rely onagreed so far - i am one of the guys doing micro-optimizations others call me crazy - but sometimes you need to draw a line :-) in other words: itÄs a difference between study behavior and try to optimize something with nohing measurable to gain -------------- 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/20160315/9e1e5730/signature.sig>
On Tue, Mar 15, 2016 at 08:51:30PM +0000, Miguel Medalha wrote:> > >well, not sure - in fact you can configure each share with > >different "vfs objects" and so configuration likely still is > >needed - i referred more to my expierience with httpd where you > >don't need "LoadModule" lines for static compiled modules > > There has been a change in the configuration/behavior of modules and > their stacking and that change is not well documented. In previous > versions of Samba that exact same acl_xattr module could be declared > in the [global] section of smb.conf and it would apply to ALL the > shares, as should be expected. I still have here a retired samba 3.2 > server and it behaves in that way. This can be very practical if all > your clients are Windows workstations, as is often the case. As a > matter of fact, there was a general principle, even referred to in > the Samba documentation, that global "G" parameters could be used > only globally but share "S" parameters could be used both in shares > and globally, in which case they would apply to all shares. This was > very practical but seems to no longer be the case for Samba 4.x.Wait -- this is supposed to still work, and I have a lot of customers that do exactly that. "vfs objects" in [global] that applies to all shares then. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt at sernet.de
>>Wait -- this is supposed to still work, and I have a lot of customers thatdo exactly that.>>"vfs objects" in [global] that applies to all shares then.I just tested it. It works until you put some other vfs module in some share. Then it ceases to work, you have to declare it for all shares. This works: [global] vfs objects = acl_xattr [share] /some/path This does not work: [global] vfs objects = acl_xattr [share] /some/path vfs objects = recycle acl_xattr ceases to work for the share. The only way to make it work is to declare it for all shares: [share] /some/path vfs objects = acl_xattr recycle This behavior only exist since Samba 4.x. All prior versions worked as expected. Although it's not the worst thing in the world, it is nevertheless somewhat of a PITA and violates a general principle that we used to trust and cherish: global (G) parameters work in [global] and share (S) parameters work both in (S) and in (G).