![]() If they appear in the section, they define a default behavior for all services, unless a specific share overrides the option with a value of its own. Share options can appear in share definitions, the section, or both. These options apply to the behavior of the Samba server itself and not to any of its shares. Global options must appear in the section and nowhere else. ![]() Weâve configured very basic event logging to use a logfile not to exceed 1 MB in size and added the share to allow Samba to export the home directory of each user who has a Unix account on the server. ![]() WINS server support is enabled and to be provided by the nmbd daemon. This configuration file, based on the one we created in Chapter 2, sets up a workgroup in which Samba authenticates users using encrypted passwords and the default user-level security method. Here is an example of a Samba configuration file: The format to be simple and easy to learn. If you have ever worked with such a file on a Microsoft client, you will find smb.conf easy to create and modify. The Samba configuration file, called smb.conf by default, uses the same format as the Windows ini files. In subsequent chapters, we discuss browsing, how to configure users, security, printing, and other topics related to implementing Samba on your network. In this chapter, we introduce the structure of the Samba configuration file and show you how to use options to create and modify disk shares. If you require a full reference, the smb.conf manpage, available both in the documentation and on the Samba web site, contains an alphabetical index of all the configuration options and their meanings. Rather, our approach is present the common and necessary parameters in the context of a working server. For this reason, we do not discuss every option. Consider how much functionality we were able to obtain with fewer than a dozen in Chapter 2. Though this sounds intimidating, approximately 90 percent of installations require less than one-quarter of the available options (or parameters we use these terms interchangeably). At last count, there are more than 360 configuration options defined in the Samba source code. In previous chapters, we introduced some of the basic smb.conf settings, yet we have so far barely scratched the surface. There are several editing tools for smb.conf, such as SWAT, but most administrators still prefer to fire up their favorite text editor. The database ( tdb) files are normally managed through command-line tools such as pdbedit or net and Windows management tools such as User Manager or MMC plug-ins. Today settings are mixed between the smb.conf file and local database files in /usr/local/samba/var/locks (or the location specified by the lock directory setting in smb.conf). In the beginning, Samba servers were managed solely by a text configuration file named smb.conf. Chapter 4. The Samba Configuration File
0 Comments
Leave a Reply. |