Configuration File Options
Samba has well over 200 configuration options at its disposal. So let’s start off easy by introducing some of the options you can use to modify the configuration file itself.
As we hinted earlier in the chapter, configuration files are by no means static. You can instruct Samba to include or even replace configuration options as it is processing them. The options to do this are summarized in Table 4.2.
Table 4-2. Configuration File Options
|
Option |
Parameters |
Function |
Default |
Scope |
|---|---|---|---|---|
|
|
string (fully-qualified name) |
Sets the location of a configuration file to use instead of the current one. |
None |
Global |
|
|
string (fully-qualified name) |
Specifies an additional segment of configuration options to be included at this point in the configuration file. |
None |
Global |
|
|
string (name of share) |
Allows you to clone the configuration options of another share in the current share. |
None |
Share |
config file
The global config
file option specifies a replacement configuration file that will be loaded when the option is encountered. If the target file exists, the remainder of the current configuration file, as well as the options encounter so far, will be discarded; Samba will configure itself entirely with the options in the new file. The config
file option takes advantage of the variables above, which is useful in the event that you want load a special configuration file based on the machine name or user of the client that it connecting. ...