"samba3" parameters in smb.conf when running as AD DC

Andrew Bartlett abartlet at samba.org
Thu Apr 12 02:49:07 MDT 2012

On Wed, 2012-04-04 at 10:49 -0700, Matthieu Patou wrote:
> On 04/04/2012 02:00 AM, Andrew Bartlett wrote:
> > On Wed, 2012-04-04 at 11:22 +0300, Alexander Bokovoy wrote:
> >> On Wed, Apr 4, 2012 at 10:32, Matthieu Patou<mat at samba.org>  wrote:
> >>> Hello,
> >>>
> >>> If I set samba3 parameter (ie. vfs object) in smb.conf for samba4 it will print an error message: Unknown parameter encountered: "vfs objects", but server will start.
> >>>
> >>> If I try to add it with python it will print this error message and the the line won't be added in the smb.conf if I then do a lp.dump(file).
> >>>
> >>> This is causing a problem during provision as it's using the python interface for loadparm and setting some samba file server options could be interesting.
> >>>
> >>> What's the solution ? Adding those parameters to samba 4 ? prefix them with s3fs and instruct source3/param/loadparam.c how to strip this prefix ?
> >> What about adding param flags FLAG_SAMBA3, FLAG_SAMBA4 and specify
> >> them explicitly in parm_table?
> >> In addition to that both parm tables could be provided in a common
> >> lib/param/ library so that code in samba4 could consult them both and
> >> ignore ones with FLAG_SAMBA3 while code in samba3 could also consult
> >> both and ignore ones with FLAG_SAMBA4.
> > It simply needs to be just one parameter table.  The starting point is
> > to get the two existing tables in sync (they are already for
> > service-specific parameters).
> >
> > We could start by using another #include to bring in the common
> > portion.
> Seems ok for me, are others ok too ?

I've started this work.  The efforts so far are in

This doesn't set up the #include, that is a future step.  It is made
more complex by the way the headings for swat are inline, in order in
the smb.conf.  

In the short term, we should try and get as much of the table as
identical as possible.  This is slow and tedious, but otherwise our
users will be swamped with these warnings. 

At the very least, we could import the s4-only parameters into a common
file I guess, to make them 'common' (and not warned about), but we also
need to write docs, and do many other things.

Andrew Bartlett

Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org

More information about the samba-technical mailing list