[Samba] static vs shared modules build

Volker Lendecke
Wed, 16 Mar 2016 05:59:57 -0000

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