samba configuration via rpc - beyond registry shares

Gerald (Jerry) Carter jerry at
Thu Jan 4 13:16:24 GMT 2007

Hash: SHA1

Volker Lendecke wrote:
> On Wed, Jan 03, 2007 at 02:48:56PM +0000, David Collier-Brown wrote:
>>   As an initial step, one should be able to request the state be
>> written out in textual form, so you can use a side-by-side diff
>> program to inspect the differences between the registry and the
>> smb.conf, and then either commit or abort the changes to both
>> the smb.conf and the registry.
> What I'd like to see is something like testparm walking the
> sources for smb.conf settings. Having code writing to
> smb.conf is something I would like to avoid if possible.
> Look at passdb/pdb_smbpassd.c to see how difficult it is to
> safely write a much simpler text file.

+1.  I think smb.conf should be a readonly backend with
the exception of the "add share command", et. al. parameters.

>>   The latter might be done by evaluating the smb.conf and "pushing"
>> the state of it to the registry...
> Sure, the other direction could also benefit from a separate
> tool.
>>   Think of this as a synchronization problem: one doesn't necessarily
>> have a master, one has a way of committing individual changes from
>> either to both, and it;s easiest for a Unix person to do that at the
>> Samba end.
> I'd delegate the sync problem to the human admin.
> What about the following policy: Once a particular setting
> in the main smb.conf is found, none of the settings there
> apply anymore, its contents are completely thrown away, and
> only the registry (or some other potential later source) is
> looked at.

See "config file".  We could reuse that.  Something like
config file = reg:/etc/samba/registry.tdb

cheers, jerry
Samba                                    -------
Centeris                         -----------
"What man is a man who does not make the world better?"      --Balian
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


More information about the samba-technical mailing list