RHEL5 enterprise-level server configuration Part 2 Samba Server Configuration

1. Check whether the required software rpm-qa | grepsamba2 for samba is installed. Run the following command rpm-ivhsamba * to install the rpm package for samba *. rpm (common tool and library package, graphical management toolkit for main package client package) or if you have configured YUM, you can directly use the following command to operate yuminstallsamba (this method is the best, you can install all samba packages completely.) 3

1. Check whether samba software is installed.

Rpm-qa | grep samba

2. Install the samba rpm package and use the following command.

Rpm-ivh samba *. rpm

(Master package client package common tools and library package, graphical management toolkit)

Or if you have configured YUM, you can directly use the following command to operate

Yum install samba (this method is the best, you can install all the packages about samba completely)

3. Build a process

[1] edit the main configuration file/etc/samba/smb. conf, specify the shared directory, www.linuxidc.com, and set the sharing permission for the shared directory;

[2] specify the log file name and storage path in the main configuration file smb. conf;

[3] set local system permissions for the shared directory;

[4] Reload the configuration file or restart the smb service to make the configuration take effect.

4. samba Server Security Mode

[1] share security level Mode

When a customer logs on to the server, the user can browse server resources without entering the user name and password. It is applicable to public shared resources with poor security.

[2] user security mode

When a customer logs on to the server, the account and password must be submitted for access after verification. This is the default level.

[3] server Security Mode

The customer needs the account password and submits it to a server for verification. If an error occurs, the user-level access will be used.

[4] domain security level mode,

If a server is added to a domain, domain control is required for verification. A domain-level server is only a member client of the domain and does not have the characteristics of the server.