Re: samba run-time modification to smb.conf files

Andrew Tridgell (tridge@samba.anu.edu.au)
Sat, 25 Apr 1998 13:40:10 +1000

From:	Andrew Tridgell <tridge@samba.anu.edu.au>
To:	lkcl@regent.push.net
Subject: Re: samba run-time modification to smb.conf files
Message-Id: <19980425034014Z12583765-461+13335@samba.anu.edu.au>
Date:	Sat, 25 Apr 1998 13:40:10 +1000

> 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.

Cheers, Andrew