par marlone41 » 11 Nov 2003 01:33
voici mon smb.conf
<BR>
<BR>
<BR>
<BR># This is the main Samba configuration file. You should read the
<BR># smb.conf(5) manual page in order to understand the options listed
<BR># here. Samba has a huge number of configurable options (perhaps too
<BR># many!) most of which are not shown in this example
<BR>#
<BR># Any line which starts with a ; (semi-colon) or a # (hash)
<BR># is a comment and is ignored. In this example we will use a #
<BR># for commentry and a ; for parts of the config file that you
<BR># may wish to enable
<BR>#
<BR># NOTE: Whenever you modify this file you should run the command "testparm"
<BR># to check that you have not made any basic syntactic errors.
<BR>#
<BR>#======================= Global Settings =====================================
<BR>[global]
<BR>
<BR># 1. Server Naming Options:
<BR># workgroup = NT-Domain-Name or Workgroup-Name
<BR> workgroup = serveur
<BR># netbios name is the name you will see in "Network Neighbourhood",
<BR># but defaults to your hostname
<BR> netbios name = serveurlinux
<BR>
<BR># server string is the equivalent of the NT Description field
<BR> server string = Samba Server %v
<BR>
<BR># Message command is run by samba when a "popup" message is sent to it.
<BR># The example below is for use with LinPopUp:
<BR>; message command = /usr/bin/linpopup "%f" "%m" %s; rm %s
<BR>
<BR># 2. Printing Options:
<BR># CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
<BR># (as cups is now used in linux-mandrake 7.2 by default)
<BR># if you want to automatically load your printer list rather
<BR># than setting them up individually then you'll need this
<BR> printcap name = cups
<BR> load printers = yes
<BR>
<BR># It should not be necessary to spell out the print system type unless
<BR># yours is non-standard. Currently supported print systems include:
<BR># bsd, sysv, plp, lprng, aix, hpux, qnx, cups
<BR> printing = cups
<BR>
<BR># Samba 2.2 supports the Windows NT-style point-and-print feature. To
<BR># use this, you need to be able to upload print drivers to the samba
<BR># server. The printer admins (or root) may install drivers onto samba.
<BR># Note that this feature uses the print$ share, so you will need to
<BR># enable it below.
<BR># This parameter works like domain admin group:
<BR># printer admin = @<group> <user>
<BR> printer admin = @adm
<BR># This should work well for winbind:
<BR>; printer admin = @"Domain Admins"
<BR>
<BR># 3. Logging Options:
<BR># this tells Samba to use a separate log file for each machine
<BR># that connects
<BR> log file = /var/log/samba/log.%m
<BR>
<BR># Put a capping on the size of the log files (in Kb).
<BR> max log size = 50
<BR>
<BR># Set the log (verbosity) level (0 <= log level <= 10)
<BR>; log level = 3
<BR>
<BR># 4. Security and Domain Membership Options:
<BR># This option is important for security. It allows you to restrict
<BR># connections to machines which are on your local network. The
<BR># following example restricts access to two C class networks and
<BR># the "loopback" interface. For more examples of the syntax see
<BR># the smb.conf man page. Do not enable this if (tcp/ip) name resolution does
<BR># not work for all the hosts in your network.
<BR>; hosts allow = 192.168.1. 192.168.2. 127.
<BR>
<BR># Uncomment this if you want a guest account, you must add this to /etc/passwd
<BR># otherwise the user "nobody" is used
<BR>; guest account = pcguest
<BR># Allow users to map to guest:
<BR> map to guest = bad user
<BR>
<BR># Security mode. Most people will want user level security. See
<BR># security_level.txt for details.
<BR> security = share
<BR> # Use password server option only with security = server or security = domain
<BR># When using security = domain, you should use password server = *
<BR>; password server = <NT-Server-Name>
<BR>; password server =
<BR>
<BR># Password Level allows matching of _n_ characters of the password for
<BR># all combinations of upper and lower case.
<BR>; password level = 8
<BR>; username level = 8
<BR>
<BR># You may wish to use password encryption. Please read
<BR># ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
<BR># Do not enable this option unless you have read those documents
<BR># Encrypted passwords are required for any use of samba in a Windows NT domain
<BR># The smbpasswd file is only required by a server doing authentication, thus
<BR># members of a domain do not need one.
<BR> encrypt passwords = no
<BR> smb passwd file = /etc/samba/smbpasswd
<BR>
<BR># The following are needed to allow password changing from Windows to
<BR># also update the Linux system password.
<BR># NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
<BR># NOTE2: You do NOT need these to allow workstations to change only
<BR># the encrypted SMB passwords. They allow the Unix password
<BR># to be kept in sync with the SMB password.
<BR>; unix password sync = Yes
<BR># You either need to setup a passwd program and passwd chat, or
<BR># enable pam password change
<BR>; pam password change = yes
<BR>; passwd program = /usr/bin/passwd %u
<BR>; passwd chat = *New*UNIX*password* %nn *ReType*new*UNIX*password* %nn
<BR>;*passwd:*all*authentication*tokens*updated*successfully*
<BR>
<BR># Unix users can map to different SMB User names
<BR>; username map = /etc/samba/smbusers
<BR>
<BR># Using the following line enables you to customise your configuration
<BR># on a per machine basis. The %m gets replaced with the netbios name
<BR># of the machine that is connecting
<BR>; include = /etc/samba/smb.conf.%m
<BR>
<BR># Options for using winbind. Winbind allows you to do all account and
<BR># authentication from a Windows or samba domain controller, creating
<BR># accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
<BR># and gid's. winbind uid and winbind gid are the only required parameters.
<BR>#
<BR># winbind uid is the range of uid's winbind can use when mapping RIDs to uid's
<BR>; winbind uid = 10000-20000
<BR>#
<BR># winbind gid is the range of uid's winbind can use when mapping RIDs to gid's
<BR>; winbind gid = 10000-20000
<BR>#
<BR># winbind separator is the character a user must use between their domain
<BR># name and username, defaults to ""
<BR>; winbind separator = +
<BR>#
<BR># winbind use default domain allows you to have winbind return usernames
<BR># in the form user instead of DOMAIN+user for the domain listed in the
<BR># workgroup parameter.
<BR>; winbind use default domain = yes
<BR>#
<BR># template homedir determines the home directory for winbind users, with
<BR># %D expanding to their domain name and %U expanding to their username:
<BR>; template homedir = /home/%D/%U
<BR>
<BR># When using winbind, you may want to have samba create home directories
<BR># on the fly for authenticated users. Ensure that /etc/pam.d/samba is
<BR># using 'service=system-auth-winbind' in pam_stack modules, and then
<BR># enable obedience of pam restrictions below:
<BR>; obey pam restrictions = yes
<BR>
<BR>#
<BR># template shell determines the shell users authenticated by winbind get
<BR>; template shell = /bin/bash
<BR>
<BR># 5. Browser Control and Networking Options:
<BR># Most people will find that this option gives better performance.
<BR># See speed.txt and the manual pages for details
<BR> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
<BR>
<BR># Configure Samba to use multiple interfaces
<BR># If you have multiple network interfaces then you must list them
<BR># here. See the man page for details.
<BR>; interfaces = 192.168.12.2/24 192.168.13.2/24
<BR>
<BR># Configure remote browse list synchronisation here
<BR># request announcement to, or browse list sync from:
<BR># a specific host or from / to a whole subnet (see below)
<BR>; remote browse sync = 192.168.3.25 192.168.5.255
<BR># Cause this host to announce itself to local subnets here
<BR>; remote announce = 192.168.1.255 192.168.2.44
<BR>
<BR># set local master to no if you don't want Samba to become a master
<BR># browser on your network. Otherwise the normal election rules apply
<BR>; local master = no
<BR>
<BR># OS Level determines the precedence of this server in master browser
<BR># elections. The default value should be reasonable
<BR>; os level = 33
<BR>
<BR># Domain Master specifies Samba to be the Domain Master Browser. This
<BR># allows Samba to collate browse lists between subnets. Don't use this
<BR># if you already have a Windows NT domain controller doing this job
<BR>; domain master = yes
<BR>
<BR># Preferred Master causes Samba to force a local browser election on startup
<BR># and gives it a slightly higher chance of winning the election
<BR>; preferred master = yes
<BR>
<BR># 6. Domain Control Options:
<BR># Enable this if you want Samba to be a domain logon server for
<BR># Windows95 workstations or Primary Domain Controller for WinNT and Win2k
<BR>; domain logons = yes
<BR>
<BR># if you enable domain logons then you may want a per-machine or
<BR># per user logon script
<BR># run a specific logon batch file per workstation (machine)
<BR>; logon script = %m.bat
<BR># run a specific logon batch file per username
<BR>; logon script = %U.bat
<BR>
<BR># Where to store roaming profiles for WinNT and Win2k
<BR># %L substitutes for this servers netbios name, %U is username
<BR># You must uncomment the [Profiles] share below
<BR>; logon path = %LProfiles%U
<BR>
<BR># Where to store roaming profiles for Win9x. Be careful with this as it also
<BR># impacts where Win2k finds it's /HOME share
<BR>; logon home = %L%U.profile
<BR>
<BR># The add user script is used by a domain member to add local user accounts
<BR># that have been authenticated by the domain controller, or by the domain
<BR># controller to add local machine accounts when adding machines to the domain.
<BR># The script must work from the command line when replacing the macros,
<BR># or the operation will fail. Check that groups exist if forcing a group.
<BR># Script for domain controller for adding machines:
<BR>; add user script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M %u
<BR># Script for domain controller with LDAP backend for adding machines (please
<BR># configure in /etc/samba/smbldap_conf.pm first):
<BR>; add user script = /usr/share/samba/scripts/smbldap-useradd.pl -w -d /dev/null -g machines -c 'Machine Account' -s /bin/false %u
<BR># Script for domain member for adding local accounts for authenticated users:
<BR>; add user script = /usr/sbin/useradd -s /bin/false %u
<BR>
<BR># Domain groups:
<BR># domain admin group is a list of unix users or groups who are made members
<BR># of the Domain Admin group
<BR>; domain admin group = root @adm
<BR>#
<BR># domain guest groups is a list of unix users or groups who are made members
<BR># of the Domain Guests group
<BR>; domain guest group = nobody @guest
<BR>
<BR># LDAP configuration for Domain Controlling:
<BR># The account (dn) that samba uses to access the LDAP server
<BR># This account needs to have write access to the LDAP tree
<BR># You will need to give samba the password for this dn, by
<BR># running 'smbpasswd -w mypassword'
<BR>; ldap admin dn = cn=root,dc=mydomain,dc=com
<BR>; ldap ssl = start_tls
<BR># start_tls should run on 389, but samba defaults incorrectly to 636
<BR>; ldap port = 389
<BR>; ldap suffix = dc=mydomain,dc=com
<BR>; ldap server = ldap.mydomain.com
<BR>
<BR>
<BR># 7. Name Resolution Options:
<BR># All NetBIOS names must be resolved to IP Addresses
<BR># 'Name Resolve Order' allows the named resolution mechanism to be specified
<BR># the default order is "host lmhosts wins bcast". "host" means use the unix
<BR># system gethostbyname() function call that will use either /etc/hosts OR
<BR># DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
<BR># and the /etc/resolv.conf file. "host" therefore is system configuration
<BR># dependant. This parameter is most often of use to prevent DNS lookups
<BR># in order to resolve NetBIOS names to IP Addresses. Use with care!
<BR># The example below excludes use of name resolution for machines that are NOT
<BR># on the local network segment
<BR># - OR - are not deliberately to be known via lmhosts or via WINS.
<BR>; name resolve order = wins lmhosts bcast
<BR>
<BR># Windows Internet Name Serving Support Section:
<BR># WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
<BR>; wins support = yes
<BR>
<BR># WINS Server - Tells the NMBD components of Samba to be a WINS Client
<BR># Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
<BR>; wins server = w.x.y.z
<BR>
<BR># WINS Proxy - Tells Samba to answer name resolution queries on
<BR># behalf of a non WINS capable client, for this to work there must be
<BR># at least one WINS Server on the network. The default is NO.
<BR>; wins proxy = yes
<BR>
<BR># DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
<BR># via DNS nslookups. The built-in default for versions 1.9.17 is yes,
<BR># this has been changed in version 1.9.18 to no.
<BR> dns proxy = no
<BR>
<BR># 8. File Naming Options:
<BR># Case Preservation can be handy - system default is _no_
<BR># NOTE: These can be set on a per share basis
<BR>; preserve case = no
<BR>; short preserve case = no
<BR># Default case is normally upper case for all DOS files
<BR>; default case = lower
<BR># Be very careful with case sensitivity - it can break things!
<BR>; case sensitive = no
<BR>
<BR># Enabling internationalization:
<BR># you can match a Windows code page with a UNIX character set.
<BR># Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
<BR># 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian),
<BR># 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul),
<BR># 950 (Trad. Chin.).
<BR># UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
<BR># ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
<BR># This is an example for french users:
<BR>; client code page = 850
<BR>; character set = ISO8859-1
<BR>
<BR>
<BR>#============================ Share Definitions ==============================
<BR>[homes]
<BR> comment = Home Directories
<BR> browseable = yes
<BR> writable = yes
<BR># You can enable VFS recycle bin on a per share basis:
<BR># Uncomment the next 2 lines (make sure you create a
<BR># .recycle folder in the base of the share and ensure
<BR># all users will have write access to it. See
<BR># examples/VFS/recycle/REAME in samba-doc for details
<BR>; vfs object = /usr/lib/samba/vfs/recycle.so
<BR>; vfs options= /etc/samba/recycle.conf
<BR># You may want to prevent abuse of your server disk space, and spread of virii
<BR>; veto files = /*.eml/*.nws/*.dll/*.mp3/*.MP3/*.mpg/*.MPG/*.vbs/*.VBS/
<BR>
<BR># Un-comment the following and create the netlogon directory for Domain Logons
<BR>; [netlogon]
<BR>; comment = Network Logon Service
<BR>; path = /var/lib/samba/netlogon
<BR>; guest ok = yes
<BR>; writable = no
<BR>
<BR>#Uncomment the following 2 lines if you would like your login scripts to
<BR>#be created dynamically by ntlogon (check that you have it in the correct
<BR>#location (the default of the ntlogon rpm available in contribs)
<BR>;root preexec = /usr/bin/ntlogon -u %U -g %G -o %a -d /var/lib/samba/netlogon/
<BR>;root postexec = rm -f /var/lib/samba/netlogon/%U.bat
<BR>
<BR># Un-comment the following to provide a specific roving profile share
<BR># the default is to use the user's home directory
<BR>;[Profiles]
<BR>; path = /var/lib/samba/profiles
<BR>; browseable = no
<BR>; guest ok = yes
<BR>; writable = yes
<BR># This script can be enabled to create profile directories on the fly
<BR># You may want to turn off guest acces if you enable this, as it
<BR># hasn't been thoroughly tested.
<BR>; root preexec = PROFILE=/var/lib/samba/profiles/%u; if [ ! -e $PROFILE ];
<BR>; then mkdir -pm700 $PROFILE; chown %u.%g $PROFILE;fi
<BR>
<BR>
<BR># NOTE: If you have a CUPS print system there is no need to
<BR># specifically define each individual printer.
<BR># You must configure the samba printers with the appropriate Windows
<BR># drivers on your Windows clients. On the Samba server no filtering is
<BR># done. If you wish that the server provides the driver and the clients
<BR># send PostScript ("Generic PostScript Printer" under Windows), you have
<BR># to swap the 'print command' line below with the commented one.
<BR>[printers]
<BR> comment = All Printers
<BR> path = /var/spool/samba
<BR> browseable = no
<BR># to allow user 'guest account' to print.
<BR> guest ok = yes
<BR> writable = no
<BR> printable = yes
<BR> create mode = 0700
<BR># =====================================
<BR># print command: see above for details.
<BR># =====================================
<BR> print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.
<BR>; print command = lpr-cups -P %p %s -r # using cups own drivers (use generic PostScript on clients).
<BR># The following two commands are the samba defaults for printing=cups
<BR># change them only if you need different options:
<BR>; lpq command = lpq -P %p
<BR>; lprm command = cancel %p-%j
<BR>
<BR># This share is used for Windows NT-style point-and-print support.
<BR># To be able to install drivers, you need to be either root, or listed
<BR># in the printer admin parameter above. Note that you also need write access
<BR># to the directory and share definition to be able to upload the drivers.
<BR># For more information on this, please see the Printing Support Section of
<BR># /usr/share/doc/samba-<version>/docs/Samba-HOWTO-Collection.pdf
<BR>[print$]
<BR> path = /var/lib/samba/printers
<BR> browseable = yes
<BR> read only = yes
<BR> write list = @adm root
<BR> guest ok = yes
<BR>
<BR># A useful application of samba is to make a PDF-generation service
<BR># To streamline this, install windows postscript drivers (preferably colour)
<BR># on the samba server, so that clients can automatically install them.
<BR>
<BR>[pdf-generator]
<BR> path = /var/tmp
<BR> guest ok = No
<BR> printable = Yes
<BR> comment = PDF Generator (only valid users)
<BR> #print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP doc_name &
<BR> print command = /usr/share/samba/scripts/print-pdf %s ~%u //%L/%u %m %I "%J" &
<BR>
<BR># This one is useful for people to share files
<BR>[tmp]
<BR> comment = Temporary file space
<BR> path = /tmp
<BR> read only = no
<BR> public = yes
<BR>
<BR># A publicly accessible directory, but read only, except for people in
<BR># the "staff" group
<BR>[public]
<BR> comment = Public Stuff
<BR> path = /home/samba/public
<BR> public = yes
<BR> writable = no
<BR> write list = @staff
<BR># Audited directory through experimental VFS audit.so module:
<BR># Uncomment next line.
<BR>; vfs object = /usr/lib/samba/vfs/audit.so
<BR>
<BR># Other examples.
<BR>#
<BR># A private printer, usable only by Fred. Spool data will be placed in Fred's
<BR># home directory. Note that fred must have write access to the spool directory,
<BR># wherever it is.
<BR>[joe]
<BR> comment = Fred's Printer
<BR> valid users = joe
<BR> path = /home/joe
<BR> printer = joe_printer
<BR> public = no
<BR> writable = no
<BR> printable = yes
<BR>
<BR># A private directory, usable only by Fred. Note that Fred requires write
<BR># access to the directory.
<BR>[joe]
<BR> comment = joe's Service
<BR> path = /home/joe/Documents/photo
<BR> valid users = Mic2
<BR> public = no
<BR> writable = yes
<BR> printable = no
<BR>
<BR># a service which has a different directory for each machine that connects
<BR># this allows you to tailor configurations to incoming machines. You could
<BR># also use the %u option to tailor it by user name.
<BR># The %m gets replaced with the machine name that is connecting.
<BR>;[pchome]
<BR>; comment = PC Directories
<BR>; path = /usr/pc/%m
<BR>; public = no
<BR>; writable = yes
<BR>
<BR># A publicly accessible directory, read/write to all users. Note that all files
<BR># created in the directory by users will be owned by the default user, so
<BR># any user with access can delete any other user's files. Obviously this
<BR># directory must be writable by the default user. Another user could of course
<BR># be specified, in which case all files would be owned by that user instead.
<BR>[public]
<BR> path = /usr/somewhere/else/public
<BR> public = yes
<BR> only guest = yes
<BR> writable = yes
<BR> printable = no
<BR>
<BR># The following two entries demonstrate how to share a directory so that two
<BR># users can place files there that will be owned by the specific users. In this
<BR># setup, the directory should be writable by both users and should have the
<BR># sticky bit set on it to prevent abuse. Obviously this could be extended to
<BR># as many users as required.
<BR>[myshare]
<BR> writeable = yes
<BR> printable = no
<BR> path = /home/joe/Documents/
<BR> create mask = 0765
<BR> comment = joe sert toi
<BR> valid users = joe
<BR>
<BR> <IMG SRC="images/smiles/icon_smile.gif">