samba run-time modification to smb.conf files

[Luke Kenneth Casson Leighton]

On Sat, 25 Apr 1998, Andrew Tridgell wrote:

> > there are numerous dce/rpc "set" calls.  is it reasonable to support
> > these?
> 
> maybe :-)
>  
> > if so, we will need to add the capability (currently only found in swat)
> > to smbd to write to smb.conf files.  
> 
> actually, swat can't write to smb.conf files. In fact, the swat code
> doesn't even really know what a smb.conf file is. It just calls
> loadparm.c routines, for example lp_dump() is used to write a
> smb.conf. This is the same routine that testparm uses.
> 
> > this is one reason why i suggested that swat (or swat v2) go "via" a
> > samba daemon instead of editing smb.conf files direct.
> 
> One problem will be that these existing (ie. NT) set calls will almost
> certainly not be flexible enough to handle the full smb.conf
> syntax. So if you wanted to create a new share then how do you decide
> what "hosts allow" settings to have? What about "widelinks" ?
> 
> You could make these just go to defaults I suppose, but I'm not really
> sure that is good enough.

ok, i was thinking more along the lines of allowing run-time changing of
parameters that do exist, and leaving alone those that don't.  then we
also write client-side code to change these params.

later, we can extend the dce/rpc set to include the bits that nt doesn't
do, and write those into the client-side too.

step-by-step...

maybe microsoft will code up smb.conf support if we do that :-)