generalising source of smb.conf

[nigel.williams at nomura.co.uk]

The idea was to very simply allow alternate methods for accessing Samba 
configuration data without breaking any existing code.  The read method 
for a standard file path would simply return the path to the file.  
However if someone wanted to say write an executable smb.conf generator 
they could simple write a module, say

libexeconf.so

and use 

include execonf://import/%m/executable_smbconf.sh 

within a standard smb.conf

Nigel Williams

-----Original Message-----
From: effugas [mailto:effugas at best.com]
Sent: 30 March 1999 23:18
To: Nigel Williams
Cc: effugas; samba-technical
Subject: Re: generalising source of smb.conf


Just a quick note--

 Include files are probably one of the more powerful aspects of
Samba--I'd venture to say conditional includes are my single favorite
feature of it, far outweighing its speed(how often is a server hammered 
to
maximum capacity?).

 Any system we design for LDAP access, or indeed any forms of
access, should take this into account.  We really *can* do the 
impossible
when it comes to Includes--SWAT's ignorance of them is problematic, and
LDAP access in the design phase should accept this.

Yours Truly,

 Dan Kaminsky
 DoxPara Research
 http://doxpara.netpedia.net