Taming SAMBA
Submitted by Rory Jaffe on
Optimizing Samba for Windows clients
It took me a while to figure this out. Hopefully this can help others
The following changes to smb.conf:
# in the [global] section
# note that wide links are disabled if UNIX extensions
# note that wide links are disabled if UNIX extensions
# are not set to No
wide links = Yes
UNIX extensions = No
# if the clients are on a LAN
socket options = IPTOS_LOWDELAY TCP_NODELAY
# in the [homes] section
# if [homes] is on certain filesystems,
wide links = Yes
UNIX extensions = No
# if the clients are on a LAN
socket options = IPTOS_LOWDELAY TCP_NODELAY
# in the [homes] section
# if [homes] is on certain filesystems,
# the following will improve performance.
# use on XFS, ext4, btrfs, ocfs2, JFS2
# use on XFS, ext4, btrfs, ocfs2, JFS2
# do not use on ext3, ZFS, HFS+
strict allocate = Yes
# if [homes] is on a RAID array, use the following
strict allocate = Yes
# if [homes] is on a RAID array, use the following
# and set to your RAID chunk size
# run the following as root to find the chunk size
# run the following as root to find the chunk size
#(change md0 to your raid device as needed)
# mdadm —detail /dev/md0
# mdadm —detail /dev/md0
write cache size = 65536
Stopping those darn warnings in the logs if you don't have printers attached to the Samba server
The following changes to smb.conf:
# in the [global] section
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
Stopping the complaints about IDMAP_VERSION if your server is a stand-alone server
Run the following commands as root:
service winbind stop
update-rc.d -f winbind remove
update-rc.d -f winbind remove
