smb.conf adalah file konfigurasi untuk suite Samba, dan berisi konfigurasi runtime untuk Samba. smb.conf juga dibuat untuk bisa dikongurasi dan diadminister dari swat (8) program. Deskripsi lengkap dari format dan parameter terdapat di dalam dokumen ini.
File smb.conf terdiri dari 'section' dan parameters. Section diawal dengan nama section di dalam kurung siku dan seteusnya sampai section berikut. Section berisi parameter dalam bentuk seperti
'name = value'
File ini berbasis baris (line-based)-artinya, setiap baris baru mewakili perintah, komentar, nama section atau parameter
Setiap section dan parameter tidak case sensitive.
Hanya tanda sama-dengan pertama dalam parameter yang digunakan, spasi sebelum atau sesudah tanda sama-dengan diabaikan. Leading, trailing, dan spasi di dalam section dan parameter akan menyebabkan parameter tidak berfungsi.
Setiap baris yang diawali dengan titik-koma (;) atau hash (#) akan diabaikan, seperti juga baris kosong
Setiap baris yang diakhiri dengan '\'
akan dilanjutkan pada baris berikut sesuai standar UNIX.
Nilai boolean parameter setelah tanda sama-dengan, bisa berupa pilihan yes/no, 0/1
atau true/false
. Atau bisa berupa string yang tidak membutuhkan 'quote.' Dalam boolean, perbedaan huruf besar/kecil tidak berpengaruh.
Setiap section dalam smb.conf (kecuali di section [global]) mendeskripsikan shared resource. Atau juga disebut sebagai "share"). Nama section adalah nama dari shared resourcenya, dan parameter di bawahnya menentukan atribut share di resource tersebut.
Ada 3 section khusus, [global], [homes] dan [printers], yang ditentukan dibawah 'special sections'. Catatan di bawah ini berlaku pada deskripsi section standar
Share terdiri dari direktori yang aksesnya dibuka dan deskripsi hak akses yang diberikan pada user mana saja. Beberapa option juga bisa diberikan di sini.
Section di dalam share ini bisa berupa servis filespace (remote directori) atau servis printer.
Section juga bisa memberikan servis guest, yang tidak mengharuskan user memasukkan password agar bisa diakses. Akan tetapi di dalam mesin UNIX anda, anda harus memasukkan satu user sebagai guest account.
Section selain guest mengharuskan klien untuk memasukkan password, dan juga user name supaya bisa diakses. Tapi karena klien versi lama (seperti LAN Manager, MS DOS Client) hanya menampilkan password tanpa user name, maka anda bisa memberikan daftar nama dengan opsi "user=" di dalam definisi share. Untuk klien Windows 95/98 dan Windows NT, opsi ini tidak diperlukan
Catatan
Server memberikan hak akses berdasarkan daftar user di mesin host UNIX. Server tidak memberikan akses lebih dari yang diberikan oleh host.
Contoh section berikut menunjukkan file-space berupa folder /home/bar
yang di-share dengan nama "foo," dan user memiliki hak akses untuk membuat dan mengubah file (write permission) di folder tersebut.
[foo] path = /home/bar writeable = true
Contoh berikut merupakan printer yang di-share. Share-nya read-only, tapi user bisa menggunakan printer. Dalam printer hak akses 'write' hanya diberikan lewat spool file. Parameter 'guest ok' menunjukkan akses diberikan juga pada user guest.
[aprinter] path = /usr/spool/public read only = true printable = true guest ok = true
Parameter yang diberikan di sini berlaku secara keseluruhan di server, atau berlaku secara default untuk section yang tidak menentukan parameter. Lihat catatan di 'PARAMETERS' untuk keterangan lebih jelas.
Jika section 'homes'
ini dimasukkan dalam smb.conf, samba akan membuat 'home directory' dari client begitu mereka masuk ke dalam server.
Pada saat ada permintaan koneksi (connection request), seluruh section di smb.conf akan discan, dan system menemukan user yang sama maka digunakan homedir tersebut. Jika tidak, maka request tadi akan dianggap sebagai user name dan dicek ke dalam local password file (/etc/passwd). Jika nama tersebut ditemukan di dalam password file, maka share akan dibuat dengan meng-klone section [homes].
Kemudian akan dibuat beberapa perubahan pda share baru tersebut:
'homes'
menjadi nama user
Sekiranya anda akan menentukan path= di dalam section [homes], maka sebaiknya gunakan makro: %S Seperti :
path=/data/pchome/%S
Ini akan berguna jika anda memiliki homedir yang berbeda di UNIX dan PC anda.
Cara tersebut merupakan cara tercepat dan termudah untuk memberi hak akses pada klien dalam jumlah banyak sekaligus.
Proses serupa juga akan terjadi jika anda hanya menggunakan "homes"
saja,
hanya nama share tidak dirubah menjadi nama user. Metode [homes] ini berguna jika satu PC dipakai bersama-sama oleh banyak orang.
Menentukan parameter di [homes] sama seperti parameter di servis lain. Parameter seperti di bawah ini merupakan parameter umum dan cocok digunakan di [homes]:
[homes] writeable = yes
Satu hal penting dan harus diingat adalah jika anda memberikan akses guest dalam [homes], maka seluruh homedir akan terlihat oleh klien, tanpa password. Sebaiknya jangan berikan hak akses seperti demikian, namun cukup read only access.
Harap diingat bahwa flag browseable untuk auto home directories akan diturunkan dari flag browseable secara global. Dengan memberikan setting browseable=no di [homes], maka [homes] sebagai share tidak akan terlihat, tapi langsung ke auto home directories
Section ini sama seperti [homes].
Jika ada [printers] di smb.conf, maka user bisa menggunakan seluruh printer di dalam file printcap di host (/etc/printcap atau lainnya).
Jika ada connection request, section ini akan discan, jika system menemukan maka shared itu akan digunakan. Jika tidak ada, tapi terdapat [homes], maka ia akan digunakan seperti di atas. Jika tidak ditemukan, nama section itu akan dijadikan nama printer kemudian Samba akan mencari file printcap untuk menemukan daftar printer. Jika ada, maka share baru untuk printer akan dibuat dengan meng-klone [printers].
Beberapa modifikasi yang dilakukan pada saat share baru adalah:
Perhatikan: bahwa [printers] HARUS memiliki opsi printable - jika tidak, server akan menolak memberikan akses dan user tidak bisa mem-print.
Secara umum, path yang dispesifikasikan harus bisa diprint oleh semua orang. Biasanya entri di [printers] cukup sebagai berikut:
[printers] path = /usr/spool/public guest ok = yes printable = yes
Seluruh alias yang diberikan untuk printer merupakan nama printer. Jika sub-system printer anda tidak demikian, anda harus membuat sebuah pseudo-printcap, yaitu berupa file yang isinya seperti demikian
alias|alias|alias|alias...
Setiap alias harus bisa dibaca oleh susbystem printing anda. Dalam [global], tentukan file baru sebagai printcap anda, Server hanya akan mengenali nama printer yang ada di pseudo-printcap, dan tentunya anda bisa memberi nama sesuka hati anda. Teknik serupa bisa anda terapkan untuk membatasi akses ke printer anda.
Alias sendiri merupakan komponen dari entri pertama dalam records printcap. Records ini dipisahkan dengan baris, sedang komponen (jika lebih dari satu) dipisahkan dengan simbol bar vertical (|)
CACATAN:
Dalam sistem SYSV yang menerapkan lpstat untuk menentukan printer mana yang dipakai dalam sistem,
anda bisa meletakkan opsi"printcap name = lpstat",
yang secara otomatis akan mengambil list printer dari lpstat.
Silakan lihat "printcap name" untuk jelasnya.
Parameter menentukan atribut spesifik dari section.
Beberapa parameter hanya spesifik pada section [global]
(contoh: security).
Beberapa parameter lain bisa digunakan di section lain
(contoh create mode).
Sebagian lagi hanya bisa digunakan di section normal, yaitu [homes] dan
[printers]
Huruf 'G'
dalam kurung mengindikasikan bahwa parameter itu spesifik pada [global], sedang huruf 'S'
menunjukkan parameter itu bisa dispesifikasikan dalam section servis.
CACATAN
Seluruh parameter 'S'
juga bisa diletakkan di section
[global]
- yang tentunya akan mempengaruhi seluruh servis secara default.
Parameter disusun di sini dalam urutan abjad. Sebagian punya sinonim (alias sama dengan parameter lain). Keterangan bisa jadi ada di parameter tersebut, bisa juga di sinonimnya. Kalo mau protes silakan e-mail ke tim Samba. :-D
Beberapa string dalam smb.conf memiliki substitusi (pengganti).
Contohnya "path =
/tmp/%u"
akan diinterpretasikan sebagai "path = /tmp/john"
jika user yang sedang terhubung ke server bernama john. Begitu juga kalo user yang sedang masuk namanya Udin atau Zen...
Berikut adalah daftar substitusi yang paling sering dipakai. Meski ada juga substitusi lain yang bisa digunakan jika relevan.
Ada banyak hal bisa dilakukan dengan substitusi ini dan beberapa opsi smb.conf
Samba mendukung "name mangling", yang memungkinkan klien DOS dan Windows bisa menggunakan file dengan format 8.3. Samba pun mampu menyesuaikan format huruf besar/kecil (case) dalam penamaan file.
Ada beberapa opsi yang bisa mengontrol mangling ini, opsi tersebut dikelompokkan di sini. Untuk default, silakan lihat hasil tes dari testparm. Setiap opsi bisa di-set secara terpisah untuk setiap servis atau secara global.
Berikut opsi-opsi tersebut:
"mangle case = yes/no"
mengontrol jika karakter di dalam nama file secara "default" tidak di-mangle
Contoh, jika di set=yes, maka nama file seperti "Surat"
akan dimangle.
Default no.
"case sensitive = yes/no"
mengontrol apakah nama file case sensitive atau tidak. Jika tidak maka Samba harus melakukan pencarian file berdasarkan nama dan penggunaan huruf besar/kecil.
Default no.
"default case = upper/lower"
mengontrol penggunaan huruf kapital/kecil (case) secara default untuk nama file baru.
Default lower.
"preserve case = yes/no"
mengontrol apakah nama urutan huruf kapital/kecil dari nama file tetap dipertahankan,
atau dipaksa mengikuti parameter "default"
.
Default Yes.
"short preserve case = yes/no"
mengontrol jika format nama file 8.3 tetap dipertahankan case-nya, atau dipaksa mengikuti parameter "default"
.
Opsi ini bisa digunakan dengan "preserve case = yes"
yes" untuk memberikan LFN (Long File Name) tetap dalam case mereka.
Default Yes.
Secara default, Samba 2.0 memiliki semantil sama dengan Windows NT server, yang 'case insensitive' tapi 'case preserving.'
Ada beragam cara user bisa terhubung ke server. Server melakukan langkah berikut untuk melakukan validasi terhadap user, jika seluruh langkah gagal maka permintaan koneksi (connection request) dari user akan ditolak. Jika salah satu langkah berhasil, maka langkah berikut tidak akan dilakukan.
Jika servis Samba memiliki "guest only = yes" maka langkah 1 sampai 5 akan dilewati
\\server\service%username
.
'@'
, maka pengecekan akan berkembang ke dalam grup yang memiliki nama sama.
Berikut ini adalah daftar dari seluruh parameter global. Lihat section dari setiap parameter untuk lebih jelasnya. Beberapa di dalam daftar adalah sinonim.
Berikut daftar lengkap dari parameter servis, lihat section dari setiap parameter untuk keterangan lebih lanjut. Beberapa diantara daftar ini adalah sinonim.
Merupakan path tempat dimana script akan dijalankan sebagai ROOT oleh smbd (8) dalam keadaan berikut:
Samba server biasanya mengambil daftar user UNIX guna memberi hak akses. Untuk situs yang menggunakan databse account dari Windows NT sebagai database user utama, menjaga sinkronisasi dalam daftar user dengan PDC NT merupakan tugas tersendiri. Opsi ini memberikan hak pada smbd untuk membuat user UNIX agar bisa mengakses server Samba berdasarkan daftar di PDC.
Untuk menggunakannya, smbd harus di-set ke security=server atau security=domain dan "add user script" harus di-set ke path dimana script untuk membuat user UNIX memberikan argumen %u, yang akan mengembangkan hak akses pada user UNIX.
Saat user Windows mengakses server Samba pada saat "login"(session setup dalam protokol SMB), smbd akan mengontak password server dan mencoba mengautentikasi user dan passwordnya. Jika berhasil, maka smbd akan mencari user UNIX dalam database password di UNIX untuk di-map dengan user Windows. Jika proses lookup ini gagal, maka"add user script" akan di-set dan smbd akan memanggil script sebagai ROOT, mengembangkan setiap argumen %u untuk menjadi nama user.
Jika script ini sukses membuat user, maka smbd akan meneruskan proses seakan-akan user UNIX telah ada. Dengan cara demikian user UNIX secara dinamis akan dibuat untuk dicocokkan dengan daftar user account di Windows NT.
Lihat juga security=server, security=domain, password server, delete user script.
Default:
add user script = <kosong>
Contoh:
add user script = /usr/local/samba/bin/add_user %u
Merupakan daftar yang memiliki hak administratif. Dengan pemberian hak ini, maka user ini mampu melakukan semua operasi sebagai super-user alias root di dalam share.
Hati-hati dengan opsi ini, sebab user yang masuk dalam daftar ini akan mampu melakukan apa saja dengan share, dan mengabaikan hak akses file.
Default:
tidak ada
Contoh:
admin users = jason
admin users = itta
Sinonim untuk hosts allow.
Opsi ini hanya akan berpengaruh jika security diset ke server atau domain. Jika opsi ini diset menjadi no, setiap upaya masuk ke dalam share dari workgroup/domain lain akan gagal, meskipun domain itu mendapat trust.
Opsi ini berguna jika anda ingin server Samba anda hanya melayani user di dalam domainnya saja. Contoh, jika ada 2 domain: DOM_A dan DOM_B, kemudian DOM_A memberi trust pada DOM_B, di DOM_A ada server Samba. Dalam kondisi biasa, user di DOM_B bisa mengakses resource di DOM_A dengan menggunakan user account di DOM_A. Dengan mengaktifkan opsi ini, maka hal itu tidak akan dapat dilakukan.
Default:
allow trusted domains = Yes
Example:
allow trusted domains = No
Merupakan parameter lama dan tidak lagi digunakan di Samba2.0. Dalam versi sebelum 2.0, parameter ini mempengaruhi atribut "read only" sebuah file dalam DOS. Dalam Samba2.0, sebuah file menjadi "read only" jika file itu tidak punya atribut 'w' untuk pemilik file, baik pemilik file itu merupakan user yang sedang logon atau tidak.
Mempengaruhi bagaimana server nmbd memperkenalkan dirinya. Secara default, opsi ini diset ke Windows NT. Opsi lain yang valid adalah NT atau NT Server (keduanya sama), NT Workstation, Win95, atau WfW yang artinya sama dengan Windows NT Server, Windows NT Workstation, Windows 95 dan Windows for Workgroups. Jangan merubah parameter ini ke NT Server kecuali jika anda ingin mesin Samba anda dianggap sebagai NT Server dan ikut dalam pemilihan browser.
Default:
announce as = NT Server
Contoh
announce as = Win95
Menentukan versi mayor/minor yang digunakan nmb saat memperkenalkan diri sebagai server. Jangan rubah parameter ini, kecuali anda ingin Samba server anda menjadi downlevel server.
Default:
announce version = 4.2
Contoh:
announce version = 2.0
Memberikan daftar layanan (servis) yang secara otomatis diberikan pada daftar browser. Sangat berguna bagi servis homes dan printers yang tidak dimunculkan.
Catatan: Jika anda ingin seluruh isi printer di dalam printcap dimunculkan, masukkan opsi "load printers".
Default:
kosong
Contoh:
auto services = fred lp colorlp
Parameter ini membolehkan anda mematikan servis. Jika 'available = no'
,
maka SEMUA akses ke servis akan gagal,
dan kegagalannya akan disimpan di log.
Default:
available = yes
Contoh:
available = no
Parameter global ini memberi batasan pada Samba pada interface mana saja di mesin akan dilayani request smb-nya. Jika mempengaruhi servis smbd dan name service nmbd dengan cara berbeda.
Untuk name service, parameter ini menyebabkan nmbd port 137 dan 138 di-bind ke interface yang terdaftar di parameter 'interfaces'. Juga akan menyebabkan nmbd di-bind ke seluruh alamat interface (0.0.0.0) di port 137 dan 138 guna broadcast pesan. Jika opsi ini tidak diset, maka nmbd akan melayani seluruh 'name request' di socket ini. Jika "bind interfaces only" diset, maka nmbd akan mengecek sumber alamat dari seluruh paket yang datang dalam socket broadcast berdasarkan daftar di 'interfaces'. Kemudian jika sumber paket tidak cocok, maka paket akan dibuang. Begitu paket unicast diterima, maka nmbd akan menolak melayani permintaan name service jika permintaan (request) itu datang bukan dari interface yang terdaftar di daftar "interfaces". Tapi IP spoofing mampu mengalahkan pengecekan simpel seperti ini. Makanya ia tidak bisa digunakan sebagai feature sekuriti dari nmbd.
Untuk file service, parameter ini menyebabkan smbd hanya mem-bind interface yang terdaftar di 'interfaces' Kemudian akan membatasi smbd untuk hanya melayani request yang datang dari interface tersebut. Anda sebaiknya tidak menggunakan parameter ini jika mesin tersebut melayani PPP atau intermiten atau interface non-broadcast, sebab semuanya tidak akan dilayani sebab tidak memiliki permanen IP
Jika "bind interfaces only" diset maka jika alamat IP 127.0.0.1 tidak dimasukkan ke dalam daftar 'interfaces', maka smbpasswd dan swat tidak akan bekerja, sebab:
Untuk merubah SMB password dari user, smbpasswd secara default akan mengontak alamat "localhost" - 127.0.0.1 sebagai klien SMB untuk melakukan perubahan password. Jika "bind interfaces only" diset dan 127.0.0.1 tidak terdaftar dalam daftar interface, maka smbpasswd tidak akan bisa melakukan perubahan password. smbpasswd bisa dipaksa untuk menggunakan IP primer dari localhost menggunakan parameter "-r remote machine", dengan "remote machine" diset ke IP dari localhost.
Status dari swat juga melakukan pencarian ke alamat 127.0.0.1 untuk mengecek apakah smbd dan nmbd berjalan. Dengan tidak menambahkan 127.0.0.1 akan menyebabkan smbd dan nmbd akan selalu menunjukkan "not running", padahal mereka berjalan. Ini dapat membuat swat tidak bisa menyetop/memulai/me-restart smbd dan nmbd.
Default:
bind interfaces only = False
Contoh:
bind interfaces only = True
Parameter ini mengontrol perilaku smbd ketika menerima permintaan (request) dari klien yang meminta byte range lock dari sebuah file yang terbuka,
Jika parameter diset dan permintaan lock range tadi tidak bisa dipenuhi segera, maka Samba 2.0 akan membuat antrian (queue) dari lock request, dan secara berkala akan mencoba memperoleh lock tersebut sampai waktu timeout habis.
Jika parameter ini "False", maka Samba 2.0 akan berlaku seperti Samba versi sebelumnya yang tidak membuat antrian terhadap pemintaan lock.
Parameter ini bisa di-set per share.
Default:
blocking locks = True
Contoh:
blocking locks = False
Sinonim dari browseable.
Mengontrol apakah smbd akan melayani daftar browse (browse list) ke klien yang melakukan pemanggilan NetServerEnum. Biasanya parameter ini= true. Anda sebaiknya jangan merubah ini.
Default:
browse list = Yes
Mengontrol apakah share ini bisa dilihat oleh klien dari daftar share dalam perintah net view atau dari daftar browse.
Default:
browseable = Yes
Contoh:
browseable = No
Lihat pembahasan di NAME MANGLING.
Sinonim dengan "case sensitive".
"ChangeNotify" merupakan satu dari request SMB di NT yang di-support Samba 2.0. Opsi ini memungkinkan klien memberitahu server untuk melakukan pengawasan pada sebuah direktori untuk setiap perubahan dan hanya menjawab request SMB ketika perubahan di direktori itu terjadi. smbd hanya akan melakukan scanning di dalam direktori yang diminta setiap change notify timeout detik.
change notify timeout dalam detik.
Default:
change notify timeout = 60
Contoh:
change notify timeout = 300
---
Akan merubah waktu scan setiap 5 menit.
Memungkinkan samba melakukan map nama file dari code page DOS (lihat parameter client code page) untuk beberapa character set yag built-in di UNIX. Code page yang built-in adalah:
BUG. code page MSDOS to mapping character set di UNIX sebaiknya dinamis, seperti di code page MS DOS, yang juga tidak statis.
Lihat juga client code page. Biasanya sih, parameter ini tidak diset, artinya gak ada terjemahan karakter yang musti dikerjain Samba...
Default:
character set = <empty string>
Contoh:
character set = ISO8859-1
Parameter ini menspesifikasikan code page DOS yang digunakan oleh klien yang mengakses Samba kita. Jika pengen tahu apa code page yang dipake oleh klien Windows dan DOS kita, dari command prompt DOS, jalanin perintah "chcp". Outputnya akan memberikan code page. Default untuk MS-DOS, Windows 95 dan NT rilis USA adalah 437. Default untuk rilis Eropa Barat (western european) adalah code page 850.
Parameter ini memberitahu smbd
codepage.XXX
mana yang secara dinamis akan diload pada saat startup.
File-file ini yang secara detail dijelaskan di dalam manual make_smbcodepage (1),
memberitahu smbd bagaimana melakukan mapping huruf kecil ke huruf kapital
(apa sih bahasa Indonesia-nya upper dan lower case yang baku?)
untuk memberikan 'case insensitivity' seperti yang diinginkan klien Windows.
Samba saat ini memilikii file code page berikut :
Berdasarkan daftar di atas, parameter ini hanya mungkin berisi nilai 437, 737, 850, 852, 861, 932, 936, 949, ataw 950. Kalo code page yang anda butuhkan tidak ketemu (nah lo...), baca komentar dalam file codepage lain dan manual make_smbcodepage (1) dan tulis sendiri. Seperti untuk Indonesia anda bisa menulis code page aksara Jawa Kuno, aksara Batak atau Aksara Bali... Tapi kalo udah jadi, jangan lupa kirimkan juga ke Samba User Community.
Parameter ini bekerja sama dengan "valid chars" dalam menentukan karakter/aksara apa yang valid dalam penamaan file dan bagaimana penulisan huruf kapitalnya. Kalo keduanya diset dan juga "valid chars", maka parameter "client code page" KUDU diset sebelum "valid chars" dalam smb.conf
Jika tidak diset, maka nilai default adalah 850.
Lihat juga : "valid chars"
Default:
client code page = 850
Contoh:
client code page = 936
Untuk menentukan bagaimana karakter/aksara (apa sih bahasa Indonesia bakunya?) Shift-JIS Japanese di-map dari "client code page" dari klien, menjadi nama file dalam filesystem UNIX. Cuma bisa dipakai jika "client code page" diset ke 932 (Japanese Shift-JIS).
Opsinya adalah :
:AB
.
:AB
.
Digunakan untuk keperluan kompatibilitas Samba dan CAP.
Merupakan filed yang muncul di share waktu klien melakukan query ke server, baik lewat network neighborhood atau via "net view"
Jika anda ingin menge-set string yang muncul di nama mesin, lihat server string
Default:
Gak ada apa-apa
Contoh:
comment = Filenya si Anu
Memungkinkan anda 'override' file konfigurasi yang digunakan selain smb.conf. Tapi bakal ada masalah (tim Samba bilang masalah telur dan ayam) jika opsi ini diset.
Untuk itu, jika nama file konfigurasi telah berubah saat parameter di-load maka ia akan me-load ulang berdasarkan file konfigurasi yang baru.
Opsi ini mengambil substitusi biasa, yang mungkin ada gunanya buat merubah konfigurasi file selain default.
Jika file konfigurasi tidak ada, maka ia tidak akan diload)
Contoh:
config file = /usr/local/samba/lib/smb.conf.%m
Dengan parameter ini anda bisa meng-'kloning' entri servis. Servis biasanya diduplikasi dibawah nama servisnya. Setiap parameter yang dispesifikasi di section ini akan melakukan 'override' parameter di section yang dikopi.
Dengan feature ini anda bisa mengeset 'template' untuk servis dan membuat servis yang sama dengan mudah. Catat: Servis yang dikopi harus muncul lebih dulu di file konfigurasi, sebelum pernyataan kopi-nya.
Default:
none
Contoh:
copy = nama_servis_lain
Sinonim dengan 'create mode'.
Saat sebuah file dibuat, ijin akses (permissions) dihitung berdasarkan mapping hak akses dari DOS ke UNIX dan hasil di UNIX diberi 'bit-wise' dan ditambahkan parameter ini. Parameter ini sama seperti MASK 'bit-wise' file untuk UNIX. Setiap bit yang *tidak* diset di sini akan dipindahkan dari set mode pada saat file dibuat.
Nilai default parameter ini adalah membuang 'group' dan 'other' dari hak w(write) dan x(execute).
Dengan mengikuti model ini Samba yang akan melakukan 'bit-wise' atau mode UNIX dibuat dari parameter ini dengan nilai dari "force create mode" yang nilai defaultnya=000
Parameter ini tidak mempengaruhi mode direktori. Untuk detail, lihat parameter 'directory mode'
Lihat juga parameter
"force create mode"
untuk memaksakan mode bit tertentu yang diset pada setiap file.
Lihat juga parameter
"directory mode"
untuk memberikan masking bit mode pada direktori.
Default:
create mask = 0744
Contoh:
create mask = 0775
Sinonim dengan create mask.
Nilai parameter ini (berupa integer desimal) merepresentasikan jumlah menit dari ketidak aktifan sebelum koneksi dianggap mati dan diputus. Deadtime hanya berpengaruh jika tidak ada file yang terbuka.
Berguna untuk menghentikan penggunaan sumber daya server yang berlebihan karena telalu banyak koneksi yang tidak aktif.
Sebagian besar klien punya feature 'auto-reconnect' saaat koneksi terputus, Oki (Oleh karena itu) parameter ini harus transparan pada user.
Penggunaan parameetr ini dengan timeout beberapa menit direkomendasikan untuk sebagian besar sistem (daripada jaringan kehabisan sumber daya).
Deadtime sama dengan nol mengindikasikan tidak ada diskoneksi yang dilakukan.
Default:
deadtime = 0
Contoh:
deadtime = 15
Kadang timestamps dalam pesan di log dibutuhkan dengan ketepatan di atas detik. Parameter boolean ini akan menambahkan mikro sekon (detik) pada timestamp .
Catatan: pramuka, eh... parameter debug timestamp harus diset 'on' supaya efeknya terasa.
Default:
debug hires timestamp = No
Contoh:
debug hires timestamp = Yes
Debug dari pesan log Samba2.0 diberi timestamp secara default. Jika anda menjalankan "debug level" yang tinggi, time stamp ini bisa mengganggu. Parameter ini (boolean) memungkinkan timestamp dimatikan.
Default:
debug timestamp = Yes
Contoh:
debug timestamp = No
Saat anda menjalankan lebih dari 1 proses smbd dan hanya membuat 1 file log, maka anda akan repot untuk menentukan output dari masing-masing proses. Parameter ini menambahkan process-id dari pesan timestamp di file log.
Catat: parameter debug timestamp harus di-set 'on' supaya parameter ini bisa jalan.
Default:
debug pid = No
Contoh:
debug pid = Yes
Samba kadang berjalan sebagai root dan kadang berjalan sebagai user yang sedang terkoneksi, parameter ini memasukkan euid, egid, uid dan gid pada header pesan timestamp di file log.
Catat: parameter debug timestamp harus di-set 'on' supaya efeknya ada.
Default:
debug uid = No
Contoh:
debug uid = Yes
Nilai ini (integer) memungkinkan level debug (log) ditentukan di smb.conf Parameter ini akan memberi fleksibilitas pada konfigurasi sistem.
Default-nya akan dibuat berdasarkan command line atau nol jika tidak ada.
Contoh:
debug level = 3
Sinonim dari default service.
Lihat bahasan di "NAME MANGLING". Juga lihat parameter "short preserve case"
Parameter ini menentukan nama servis yang akan di-koneksi jika servis yang diminta klien tidak ditemukan. Catat tanda kurung siku TIDAK diberikan dalam nilai parameter (liat contohnya di bawah)
Gak ada nilai default parameter ini. Jika parameter tidak diberikan, saat ada klien mencari servis yang gak ada, maka hasilnya akan error.
Biasanya nilai ini guest ok, atau read-only
Catat juga bahwa servis yang muncul akan sama dengan servis yang diminta, Ini akan sangat berguna sebab memungkinkan anda memakai makro macam %S untuk membuat servis wildcard.
Catatjuga bahwa setiap tanda '_'
dalam nama servis akan di-map
juga ke '/'
. Ini menarik..
Contoh:
default service = pub [pub] path = /%S
Merupakan 'full pathname' dari script yang akan dijalankan sebagai AS ROOT oleh smbd (8) berdasarkan situasi berikut:
Biasanya, server Samba menggunakan semua user UNIX yang ada untuk user yang mengakses file di server ini. Untuk situs yang memakai database account Windows NT sebagai database user, membuat user di UNIX dan menjaga sinkronisasi dengan user di NT merupakan kerjaan yang menyebalkan. Opsi ini memungkinkan smbd menghapus user UNIX ON DEMAND pada saat user mengakses server Samba, sedang di NT user ini sudah tidak terdaftar lagi.
Supaya opsi ini berjalan, smbd harus diset ke security=domain dan "delete user script" harus di-set ke full pathname dari script yang akan menghapus user UNIX dengan satu argumen %u, dan menghapus user yang dimaksud. CATAT Ini berbeda dengan add user script yang bekerja dengan opsi security=server atau security=domain. Sebab hanya jika Samba menjadi anggota domain, ia akan mendapat informasi dari user yang mencoba login tapi user tersebut tidak ada. Dalam mode security=server user yang tidak ada dianggap sama seperti 'invalid logon attempt.' Menghapus user dalam situasi ini bukan merupakan ide bagus.
Saat user Windows mencoba mengakses server Samba, saat "login" (yang merupakan session setup dalam protokol SMB), smbd akan mengontak a href="smb.conf.5.html#passwordserver">password server dan memberikan autentikasi berdasarkan nama user dan password-nya. Jika proses autentikasi gagal, dan error-nya menampilkan 'user no longer exist' maka smbd akan mencoba untuk mengunakan user UNIX dalam database password UNIX yang sama dengan user di NT. Jika proses lookup ini berhasil, dan "delete user script" diset, maka smbd akan menghapus user berdasarkan argumen %u sebagai AS ROOT.
Script ini akan menghapus user UNIX, dengan cara ini, user UNIX akan secara dinamis dihapus guna kecocokan dengan user di Windows NT.
Lihat juga security=domain, password server, add user script.
Default:
delete user script = <kosong>
Contoh:
delete user script = /usr/local/samba/bin/del_user %u
Parameter ini memungkinkan file readonly untuk dihapus. Dalam DOS ini bukan hal normal, tapi di UNIX bisa dilakukan.
Opsi ini berguna untuk aplikasi yang berjalan seperti rcs, dimana kepemilikan (ownership) file dari UNIX tidak membolehkan perubahan hak akses file, dan DOS tidak membolehkan penghapusan file readonly.
Default:
delete readonly = No
Contoh:
delete readonly = Yes
Opsi ini digunakan saat Samba mencoba menghapus direktori yang berisi lebih dari satu direktori yang di-veto (lihat opsi 'veto files' option). Jika opsi ini=False, maka setiap upaya penghapusan direktori yang di-veto dan berisi file/direktori yang juga di-veto, maka penghapusan akan gagal. Biasanya yang begini yang kita inginkan.
Jika opsi ini=True, maka Samba akan mencoba menghapus secara recursive
seluruh file dan direktori di dalam direktori veto tersebut.
Ini bisa berguna untuk integrasi dengan sistem file serving seperti
NetAtalk, yang membuat meta-files dalam direktori
yang biasanya tidak bisa dilihat oleh user DOS/Windows
(seperti: .AppleDouble
)
Menjadikan 'delete veto files = True'
membuat direktori ini
bisa secara transparan dihapus saat 'parent directory'-nya dihapus
(asal user-nya punya 'permission buat menghapus).
Lihat juga veto files.
Default:
delete veto files = False
Contoh:
delete veto files = True
Sinonim dengan hosts deny.
Setting dfree ini sebaiknya hanya digunakan dalam sistem yang punya masalah dengan kalkulasi 'disk space.' Biasanya di Ultrix, tapi bisa juga di sistem operasi lain. Gejala yang bisa kelihatan adalah error "Abort Retry Ignore" dalam setiap akhir listing direktori.
Setting ini memungkinkan penggantian rutin internal guna kalkukasi total disk space dan jumlah sisanya dengan rutin external. Contoh di bawah ini memberi kemungkinan script guna menjalankan fungsi ini.
Program external akan memberikan parameter single yang mengindikasikan
direktori dan filesystem yang sedang di-query.
Biasanya berisi string "./"
.
Script pun akan menampilkan 2 nilai integer dalam format ascii.
Nilai pertama adalah total ruang hard disk dalam hitungan blocks,
dan yang kedua adalah jumlah blok yang tersedia.
Nilai ketiga (opsional) berisi ukuran blok dalam hitungan byte.
Default biasanya 1024 bits.
Catat: script anda sebaiknya BUKAN setuid atau setgid dan sebaiknya hanya dimiliki dan 'writable' hanya oleh root!
Default:
Contoh:
Script dfree (yang musti executable) bisa seperti ini:
atau (dalam system yang berbasis Sys V, seperti RedHat):
Catat dalam beberapa sistem, bahwa anda mungkin harus memberikan
'full path name'
Sinonim dengan path.
Berisi mode octal yang digunakan untuk konversi mode DOS ke UNIX saat
membuat direktori UNIX
Saat satu direktori dibuat, permission dihitung berdasarkan mapping mode DOS
ke UNIX, dan hasilnya berupa bit-wise dengan penambahan parameter ini.
Parameter ini bisa dianggap sebagai bit-wise MASK dari direktori
untuk mode UNIX. Setiap bit yang *tidak* di sini akan diganti
berdasarkan mode direktori pada saat dibuat.
Nilai default-nya adalah menghapus hak write untuk 'group' and 'other'
dari mode UNIX, memungkinkan hanya user pemilik yang bisa memodifikasinya.
Dengan mengacu pada mode di atas, Samba akan memberi bit-wise 'OR' dari mode
UNIX yang dibuat dari parameter ini dengan nilai
force directory mode
Secara default parameter ini adalah 000.
Lihat parameter "force directory mode"
yang akan membuat mode tertentu selalu diset setiap satu direktori dibuat. Lihat juga parameter
"create mode"
untuk memberi mode masking dari setiap file yang dibuat, dan
"directory security mask"
Default:
Contoh:
Sinonim dengan directory mask.
Mengontrol permission UNIX yang bia dimodifikasi saat klien NT mengubah
permission-nya menggunakan security dialog box di NT
Parameter ini diterapkan sebagai mask pada perubahan permission,
dan mencegah setiap bit yang tidak ada di mask ini untuk dirubah.
Pada prinsipnya, bit nol dalam mask ini akan dianggap sebagai set yang tidak
membolehkan user melakukan perubahan.
Jika tidak diset, parameter ini akan diset ke nilai yang sama dengan
directory mask,
guna memungkinkan user memodifikasi seluruh permission untuk user/group/world,
parameter ini di-set ke 0777.
Catat bahwa user yang bisa mengakses server Samba server
lewat cara lain bisa dengan mudah mem-bypass restriksi ini.
Maka ini hanya bisa bekerja baik dengan sistem standalone appliance.
Administrator dari sebagian besar sistem biasanya menge-set ini menjadi 0777.
Lihat juga
force directory security mode,
security mask,
force security mode
Default:
Contoh:
Menentukan apakah nmbd
sebagai server WINS saat menemukan satu nama NetBIOS yang belum terdaftar,
akan memperlakukan nama NetBIOS tersebut sebagai nama DNS
dan melakukan lookup dengan server DNS untuk nama tersebut atas nama klien.
Catat bahwa panjang maksimum nama NetBIOS adalah 15 huruf,
jadi penetapan nama DNS (atau aliasnya) juga hanya bisa 15 huruf.
nmbd
akan mengembang jadi dua kopi guna melakukan DNS name lookup requests.
Lihat juga parameter
wins support.
Default:
Parameter ini masih EXPERIMENTAL dan belum selesai
dalam implementasi di Windows NT Domain Controller.
Parameter ini mungkin tidak dimasukkan lagi dalam rilis berikit.
Guna mengetahui kode terakhir yang mampu mendukung fungsi
Samba NT Domain Controller, silakan bergabung ke milis Samba-ntdom
dengan mengirim e-mail ke listproc@samba.org.
Parameter ini masih EXPERIMENTAL dan belum selesai
dalam implementasi di Windows NT Domain Controller.
Parameter ini mungkin tidak dimasukkan lagi dalam rilis berikit.
Guna mengetahui kode terakhir yang mampu mendukung fungsi
Samba NT Domain Controller, silakan bergabung ke milis Samba-ntdom
dengan mengirim e-mail ke listproc@samba.org.
Parameter ini TIDAK LAGI DIGUNAKAN, dan sebaiknya
tidak dipakai di smb.conf anda.
Parameter ini sengaja ditinggalkan untuk alasan kompatibilitas.
Parameter ini masih EXPERIMENTAL dan belum selesai
dalam implementasi di Windows NT Domain Controller.
Parameter ini mungkin tidak dimasukkan lagi dalam rilis berikit.
Guna mengetahui kode terakhir yang mampu mendukung fungsi
Samba NT Domain Controller, silakan bergabung ke milis Samba-ntdom
dengan mengirim e-mail ke listproc@samba.org.
Parameter ini masih EXPERIMENTAL dan belum selesai
dalam implementasi di Windows NT Domain Controller.
Parameter ini mungkin tidak dimasukkan lagi dalam rilis berikit.
Guna mengetahui kode terakhir yang mampu mendukung fungsi
Samba NT Domain Controller, silakan bergabung ke milis Samba-ntdom
dengan mengirim e-mail ke listproc@samba.org.
Parameter ini masih EXPERIMENTAL dan belum selesai
dalam implementasi di Windows NT Domain Controller.
Parameter ini mungkin tidak dimasukkan lagi dalam rilis berikit.
Guna mengetahui kode terakhir yang mampu mendukung fungsi
Samba NT Domain Controller, silakan bergabung ke milis Samba-ntdom
dengan mengirim e-mail ke listproc@samba.org.
Jika sama dengan true, server Samba akan melayani logon request dari
Windows 95/98 yang satu workgroup.
Untuk lebih jelasnya, lihat file DOMAINS.txt dalam dokumentasi Samba yang
termasuk dalam source code ini.
Perlu diingat bahwa Domain logons di Win95/98 TIDAK sama seperti di
NT dengan PDC-nya. Dalam rilis berikut dari Samba (TNG) akan mampu memberikan
fungsi ini untuk klien Windows NT.
Default:
Akan memberitahu nmbd
untuk menjadi WAN-wide browse list collation.
Dengan mengeset opsi ini akan membuat nmbd mengklaim dirinya dengan nama NetBIOS khusus sebagai
domain master browser di dalam workgroup.
Local master browser dalam workgroup yang sama dan subnet yang terisolasi
akan memberi nmbd daftar browse di
lingkungan mereka sendiri (local).
Kemudian meminta smbd untuk memberi
dafatr lengkap browse dalam seluruh wide area network.
Klien browser akan mengontak local master browser dan menerima daftar browse
di seluruh domain, selain subnet mereka sendiri.
Catat bahwa Windows NT PDC secara default selalu mengklaim dirinya sebagai
domain master browser dalam workgroup
(Tidak ada cara untuk mencegah NT melakukan klaim ini).
Artinya jika parameter ini di-set dan nmbd
mengklaim dirinya nama khusus NetBIOS sebagai domain master browser sebelum
PDC NT melakukannya, maka browsing antar subnet akan gagal. Sebab Windows NT
tidak akan mampu menyediakan daftar browse seluruh domain.
Default:
Dalam beberapa sistem, ada direktori yang seharusnya tidak perlu diketahui
klien, seperti Catat bahwa Samba bisa sangat membingungkan dengan format pasti dari
entri "dontdescend" ini.
Contoh, anda mungkin perlu menulis Default:
Contoh:
Dibawah filesystem FAT DOS dan Windows putaran waktu (granularity) resolusi
waktu terbaik adalah 2 detik. Merubah parameter ini untuk share menyebabkan
Samba melakukan putaran waktu mendekati 2 detik saat ada panggilan query untuk
melakukan resolusi 1 detik untuk smbd.
Opsi ini digunakan sebagai kompatibilitas dengan Visual C++ saat digunakan
terhadap share Samba. Jika di dalam share oplocks di-enable, Visual C++ akan
menggunakan 2 waktu pembacaan (time reading calls) yang berbeda untuk mengecek
ada-tidaknya perubahan file sejak terakhir kali file tersebut dibaca. Salah
satunya menggunakan putaran satu-detik, satunya lagi menggunakan putaran
dua-detik. Pengecekan dua detik akan membulatkan setiap detik ganjil ke bawah,
kemudian jika file memiliki timestamp ganjil dalam detik, kemudian jika
keduanya tidak cocok maka Visual C++ akan selalu menerima laporan adanya perubahan file terus menerus.
Menge-set parameter ini akan menyebabkan Visual C++ menerima laporan bahwa
timestamp cocok.
Default:
Contoh:
Dalam DOS dan Windows, jika user bisa menulis file, maka mereka bisa
merubah timestamp file itu. Dalam POSIX, hanya pemilik file atau root yang
bisa melakukan ini. Secara default, Samba berjalan dengan semantik POSIX, dan
akan menolak membuat perubahan timestamp jika user smbd yang masuk bukan
pemilik file tersebut. Menjadikan opsi ini True akan menyebabkan semantik DOS
dan smbd akan merubah timestamp dari file seperti DOS.
Default:
Contoh:
Mengontrol apakah password ter-enkripsi (encrypted passwords) akan digunakan
dalam hubungan server dengan klien.
Windows NT 4.0 SP3 keatas dan Windows 98 secara default melakukan enkripsi
kecuali dirubah di registri.
Untuk menggunakan password ter-enkripsi, lihat file ENCRYPTION.txt yang ada
di direktori dokumentasi Samba dan terdapat di source code-nya.
Supaya password ter-enkripsi bisa bekerja dengan baik smbd
harus bisa mengakses file smbpasswd (5)
(lihat informasi di smbpasswd (8) tentang bagaimana mengelola file ini).
Atau anda juga bisa menge-set parameter security= menjadi
"server" atau
"domain",
yang akan membuat smbd
melakukan autentikasi dengan server lain.
Sinonim dengan preexec.
Filesystem NTFS dan Windows VFAT menyimpan waktu pembuatan file untuk semua
file dan direktori. Ini berbeda dengan ctime - status change time di UNIX.
Samba secara default melaporkan waktu paling awal yang disimpan UNIX. Jika
parameter ini di-set di share, maka Samba akan selalu memberi laporan waktu
pembuatan direktori pada midnight 1-1-1980.
Opsi ini digunakan sebagai kompatibilitas dengan Visual C++ saat digunakan
terhadap share Samba. makefiles yang dibuat Visual C++ membuat dependensi dari
direktori obyek dengan setiap file obyek, dan rule make untuk membuat
direktori. Juga saat NMAKE membandingkan timestamp, ia memakai waktu pembuatan
direktori. Kemudian diektori obyek akan dibuat jika tidak ada, tapi sekali
direktori terbentuk, ia akan selalu memiliki timestamp yang lebih awal dari
file obyek di dalamnya.
Semantik UNIX akan membuat create time yang dilaporkan Samba untuk selalu
di-update kapan pun satu file dibuat atau dihapus dari direktori. NMAKE pun
akan menemukan bahwa file obyek dalam obyek direktori yang terakhir kali
dibuat lebih awal dari direktorinya, dan akan merubahnya. Menghidupkan opsi
ini membuat waktu pembuatan direktori selalu lebih awal dari isinya, dan NMAKE
akan berjalan normal.
Default:
Contoh:
Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
(opportunistic lock) then the client is free to assume that it is the
only one accessing the file and it will aggressively cache file
data. With some oplock types the client may even cache file open/close
operations. This can give enormous performance benefits.
When you set It is generally much better to use the real oplocks
support rather than this parameter.
If you enable this option on all read-only shares or shares that you
know will only be accessed from one client at a time such as
physically read-only media like CDROMs, you will see a big performance
improvement on many operations. If you enable this option on shares
where multiple clients may be accessing the files read-write at the
same time you can get data corruption. Use this option carefully!
This option is disabled by default.
This parameter allows the Samba administrator to stop
smbd from following symbolic links in a
particular share. Setting this parameter to "No" prevents any file
or directory that is a symbolic link from being followed (the user
will get an error). This option is very useful to stop users from
adding a symbolic link to This option is enabled (i.e. smbd will follow
symbolic links) by default.
This parameter specifies a set of UNIX mode bit permissions that will
*always* be set on a file created by Samba. This is done by
bitwise 'OR'ing these bits onto the mode bits of a file that is being
created. The default for this parameter is (in octal) 000. The modes
in this parameter are bitwise 'OR'ed onto the file mode after the mask
set in the "create mask" parameter is applied.
See also the parameter "create mask" for details
on masking mode bits on created files.
Default:
Example:
would force all created files to have read and execute permissions set
for 'group' and 'other' as well as the read/write/execute bits set for
the 'user'.
This parameter specifies a set of UNIX mode bit permissions that will
*always* be set on a directory created by Samba. This is done by
bitwise 'OR'ing these bits onto the mode bits of a directory that is
being created. The default for this parameter is (in octal) 0000 which
will not add any extra permission bits to a created directory. This
operation is done after the mode mask in the parameter
"directory mask" is applied.
See also the parameter "directory mask" for
details on masking mode bits on created directories.
Default:
Example:
would force all created directories to have read and execute
permissions set for 'group' and 'other' as well as the
read/write/execute bits set for the 'user'.
This parameter controls what UNIX permission bits can be modified when
a Windows NT client is manipulating the UNIX permission on a directory
using the native NT security dialog box.
This parameter is applied as a mask (OR'ed with) to the changed
permission bits, thus forcing any bits in this mask that the user may
have modified to be on. Essentially, one bits in this mask may be
treated as a set of bits that, when modifying security on a directory,
the user has always set to be 'on'.
If not set explicitly this parameter is set to the same value as the
force directory mode parameter. To allow
a user to modify all the user/group/world permissions on a directory,
with restrictions set this parameter to 000.
Note that users who can access the Samba server through other
means can easily bypass this restriction, so it is primarily
useful for standalone "appliance" systems. Administrators of
most normal systems will probably want to set it to 0000.
See also the directory security mask,
security mask, force security
mode parameters.
Default:
Example:
This specifies a UNIX group name that will be assigned as the default
primary group for all users connecting to this service. This is useful
for sharing files by ensuring that all access to files on service will
use the named group for their permissions checking. Thus, by assigning
permissions for this group to the files and directories within this
service the Samba administrator can restrict or allow sharing of these
files.
In Samba 2.0.5 and above this parameter has extended functionality in the following
way. If the group name listed here has a '+' character prepended to it
then the current user accessing the share only has the primary group
default assigned to this group if they are already assigned as a member
of that group. This allows an administrator to decide that only users
who are already in a particular group will create files with group
ownership set to that group. This gives a finer granularity of ownership
assignment. For example, the setting If the "force user" parameter is also set the
group specified in force group will override the primary group
set in "force user".
See also "force user"
Default:
Example:
This parameter controls what UNIX permission bits can be modified when
a Windows NT client is manipulating the UNIX permission on a file
using the native NT security dialog box.
This parameter is applied as a mask (OR'ed with) to the changed
permission bits, thus forcing any bits in this mask that the user may
have modified to be on. Essentially, one bits in this mask may be
treated as a set of bits that, when modifying security on a file, the
user has always set to be 'on'.
If not set explicitly this parameter is set to the same value as the
force create mode parameter. To allow
a user to modify all the user/group/world permissions on a file,
with no restrictions set this parameter to 000.
Note that users who can access the Samba server through other
means can easily bypass this restriction, so it is primarily
useful for standalone "appliance" systems. Administrators of
most normal systems will probably want to set it to 0000.
See also the force directory security
mode, directory security
mask, security mask
parameters.
Default:
Example:
This specifies a UNIX user name that will be assigned as the default
user for all users connecting to this service. This is useful for
sharing files. You should also use it carefully as using it
incorrectly can cause security problems.
This user name only gets used once a connection is established. Thus
clients still need to connect as a valid user and supply a valid
password. Once connected, all file operations will be performed as the
This can be very useful.
In Samba 2.0.5 and above this parameter also causes the primary
group of the forced user to be used as the primary group for all
file activity. Prior to 2.0.5 the primary group was left as the
primary group of the connecting user (this was a bug).
See also "force group"
Default:
Example:
This parameter allows the administrator to configure the string that
specifies the type of filesystem a share is using that is reported by
smbd when a client queries the filesystem type
for a share. The default type is "NTFS" for compatibility with
Windows NT but this can be changed to other strings such as "Samba" or
"FAT" if required.
Default:
Example:
This is a tuning option. When this is enabled a caching algorithm
will be used to reduce the time taken for getwd() calls. This can have
a significant impact on performance, especially when the
widelinks parameter is set to False.
Default:
Example:
Synonym for "force group".
This is a username which will be used for access to services which are
specified as 'guest ok' (see below). Whatever
privileges this user has will be available to any client connecting to
the guest service. Typically this user will exist in the password
file, but will not have a valid login. The user account "ftp" is
often a good choice for this parameter. If a username is specified in
a given service, the specified username overrides this one.
One some systems the default guest account "nobody" may not be able to
print. Use another account in this case. You should test this by
trying to log in as your guest user (perhaps by using the Default:
Example:
If this parameter is 'yes' for a service, then no password is
required to connect to the service. Privileges will be those of the
guest account.
See the section below on security for more
information about this option.
Default:
Example:
If this parameter is 'yes' for a service, then only guest
connections to the service are permitted. This parameter will have no
affect if "guest ok" or "public"
is not set for the service.
See the section below on security for more
information about this option.
Default:
Example:
This is a boolean parameter that controls whether files starting with
a dot appear as hidden files.
Default:
Example:
This is a list of files or directories that are not visible but are
accessible. The DOS 'hidden' attribute is applied to any files or
directories that match.
Each entry in the list must be separated by a Each entry must be a Unix path, not a DOS path and must not include the
Unix directory separator Note that the case sensitivity option is applicable in hiding files.
Setting this parameter will affect the performance of Samba, as it
will be forced to check all files and directories for a match as they
are scanned.
See also "hide dot files", "veto
files" and "case sensitive".
Default
Example
The above example is based on files that the Macintosh SMB client
(DAVE) available from Thursby creates for
internal use, and also still hides all files beginning with a dot.
If "nis homedir" is true, and
smbd is also acting as a Win95/98 logon
server then this parameter specifies the NIS (or YP)
map from which the server for the user's home directory should be
extracted. At present, only the Sun auto.home map format is
understood. The form of the map is:
and the program will extract the servername from before the first
NB: A working NIS is required on the system for this option to work.
See also "nis homedir", domain
logons.
Default:
Example:
A synonym for this parameter is 'allow hosts'
This parameter is a comma, space, or tab delimited set of hosts which
are permitted to access a service.
If specified in the [global] section then it will
apply to all services, regardless of whether the individual service
has a different setting.
You can specify the hosts by name or IP number. For example, you could
restrict access to only the hosts on a Class C subnet with something
like Note that the localhost address 127.0.0.1 will always be allowed
access unless specifically denied by a "hosts deny" option.
You can also specify hosts by network/netmask pairs and by netgroup
names if your system supports netgroups. The EXCEPT keyword can also
be used to limit a wildcard list. The following examples may provide
some help:
Example 1: allow all IPs in 150.203.*.* except one
Example 2: allow hosts that match the given network/netmask
Example 3: allow a couple of hosts
Example 4: allow only hosts in NIS netgroup "foonet", but
deny access from one particular host
Note that access still requires suitable user-level passwords.
See testparm (1) for a way of testing your
host access to see if it does what you expect.
Default:
Example:
The opposite of 'hosts allow' - hosts listed
here are NOT permitted access to services unless the specific
services have their own lists to override this one. Where the lists
conflict, the 'allow' list takes precedence.
Default:
Example:
If this global parameter is a non-null string, it specifies the name
of a file to read for the names of hosts and users who will be allowed
access without specifying a password.
This is not be confused with hosts allow which
is about hosts access to services and is more useful for guest
services. hosts equiv may be useful for NT clients which will not
supply passwords to samba.
NOTE: The use of hosts equiv can be a major security hole. This is
because you are trusting the PC to supply the correct username. It is
very easy to get a PC to supply a false username. I recommend that the
hosts equiv option be only used if you really know what you are
doing, or perhaps on a home network where you trust your spouse and
kids. And only if you really trust them :-).
Default
Example
This allows you to include one config file inside another. The file
is included literally, as though typed in place.
This option allows you to override the default network interfaces list
that Samba will use for browsing, name registration and other NBT
traffic. By default Samba will query the kernel for the list of all
active interfaces and use any interfaces except 127.0.0.1 that are
broadcast capable.
The option takes a list of interface strings. Each string can be in
any of the following forms:
The "mask" parameters can either be a bit length (such as 24 for a C
class network) or a full netmask in dotted decmal form.
The "IP" parameters above can either be a full dotted decimal IP
address or a hostname which will be looked up via the OSes normal
hostname resolution mechanisms.
For example, the following line:
would configure three network interfaces corresponding to the eth0
device and IP addresses 192.168.2.10 and 192.168.3.10. The netmasks of
the latter two interfaces would be set to 255.255.255.0.
See also "bind interfaces only".
This is a list of users that should not be allowed to login to this
service. This is really a "paranoid" check to absolutely ensure an
improper setting does not breach your security.
A name starting with a A name starting with The current servicename is substituted for
%S. This is useful in the [homes]
section.
See also "valid users".
Default:
Example:
The value of the parameter (an integer) represents the number of
seconds between 'keepalive' packets. If this parameter is zero, no
keepalive packets will be sent. Keepalive packets, if sent, allow the
server to tell whether a client is still present and responding.
Keepalives should, in general, not be needed if the socket being used
has the SO_KEEPALIVE attribute set on it (see "socket
options"). Basically you should only use this option
if you strike difficulties.
Default:
Example:
For UNIXs that support kernel based oplocks
(currently only IRIX but hopefully also Linux and FreeBSD soon) this
parameter allows the use of them to be turned on or off.
Kernel oplocks support allows Samba oplocks to be
broken whenever a local UNIX process or NFS operation accesses a file
that smbd has oplocked. This allows complete
data consistency between SMB/CIFS, NFS and local file access (and is a
very cool feature :-).
This parameter defaults to "On" on systems that have the support,
and "off" on systems that don't. You should never need to touch
this parameter.
See also the "oplocks" and "level2 oplocks"
parameters.
This parameter is part of the EXPERIMENTAL Samba support for a
password database stored on an LDAP server back-end. These options
are only available if your version of Samba was configured with
the --with-ldap option.
This parameter specifies an LDAP search filter used to search for a
user name in the LDAP database. It must contain the string
%u which will be replaced with the user being
searched for.
Default:
This parameter is part of the EXPERIMENTAL Samba support for a
password database stored on an LDAP server back-end. These options
are only available if your version of Samba was configured with
the --with-ldap option.
This parameter specifies the TCP port number to use to contact
the LDAP server on.
Default:
This parameter is part of the EXPERIMENTAL Samba support for a
password database stored on an LDAP server back-end. These options
are only available if your version of Samba was configured with
the --with-ldap option.
This parameter specifies the entity to bind to the LDAP server
as (essentially the LDAP username) in order to be able to perform
queries and modifications on the LDAP database.
See also ldap root passwd.
Default:
This parameter is part of the EXPERIMENTAL Samba support for a
password database stored on an LDAP server back-end. These options
are only available if your version of Samba was configured with
the --with-ldap option.
This parameter specifies the password for the entity to bind to the
LDAP server as (the password for this LDAP username) in order to be
able to perform queries and modifications on the LDAP database.
BUGS: This parameter should NOT be a readable parameter
in the smb.conf file and will be removed once a correct
storage place is found.
See also ldap root.
Default:
This parameter is part of the EXPERIMENTAL Samba support for a
password database stored on an LDAP server back-end. These options
are only available if your version of Samba was configured with
the --with-ldap option.
This parameter specifies the DNS name of the LDAP server to use
for SMB/CIFS authentication purposes.
Default:
This parameter is part of the EXPERIMENTAL Samba support for a
password database stored on an LDAP server back-end. These options
are only available if your version of Samba was configured with
the --with-ldap option.
This parameter specifies the Default:
This parameter (new in Samba 2.0.5) controls whether Samba supports
level2 (read-only) oplocks on a share. In Samba 2.0.4 this parameter
defaults to "False" as the code is new, but will default to "True"
in a later release.
Level2, or read-only oplocks allow Windows NT clients that have an
oplock on a file to downgrade from a read-write oplock to a read-only
oplock once a second client opens the file (instead of releasing all
oplocks on a second open, as in traditional, exclusive oplocks). This
allows all openers of the file that support level2 oplocks to cache
the file for read-ahead only (ie. they may not cache writes or lock
requests) and increases performance for many acesses of files that
are not commonly written (such as application .EXE files).
Once one of the clients which have a read-only oplock writes to
the file all clients are notified (no reply is needed or waited
for) and told to break their oplocks to "none" and delete any
read-ahead caches.
It is recommended that this parameter be turned on to speed access
to shared executables (and also to test the code :-).
For more discussions on level2 oplocks see the CIFS spec.
Currently, if "kernel oplocks" are supported
then level2 oplocks are not granted (even if this parameter is set
to See also the "oplocks" and "kernel oplocks" parameters.
Default:
Example:
This parameter determines if nmbd will produce
Lanman announce broadcasts that are needed by OS/2 clients in order
for them to see the Samba server in their browse list. This parameter
can have three values, See also "lm interval".
Default:
Example:
If Samba is set to produce Lanman announce broadcasts needed by
OS/2 clients (see the "lm announce"
parameter) then this parameter defines the frequency in seconds with
which they will be made. If this is set to zero then no Lanman
announcements will be made despite the setting of the "lm
announce" parameter.
See also "lm announce".
Default:
Example:
A boolean variable that controls whether all printers in the printcap
will be loaded for browsing by default. See the
"printers" section for more details.
Default:
Example:
This option allows nmbd to try and become a
local master browser on a subnet. If set to False then
nmbd will not attempt to become a local master
browser on a subnet and will also lose in all browsing elections. By
default this value is set to true. Setting this value to true doesn't
mean that Samba will become the local master browser on a subnet,
just that nmbd will participate in
elections for local master browser.
Setting this value to False will cause nmbd
never to become a local master browser.
Default:
Synonym for "lock directory".
This option specifies the directory where lock files will be placed.
The lock files are used to implement the "max
connections" option.
Default:
Example:
This controls whether or not locking will be performed by the server
in response to lock requests from the client.
If If This option may be useful for read-only filesystems which may
not need locking (such as cdrom drives), although setting this
parameter of Be careful about disabling locking either globally or in a specific
service, as lack of locking may result in data corruption. You should
never need to set this parameter.
Default:
Example:
This options allows you to override the name of the Samba log file
(also known as the debug file).
This option takes the standard substitutions, allowing you to have
separate log files for each user or machine.
Example:
Synonym for "debug level".
This parameter specifies the local path to which the home directory
will be connected (see "logon home") and is only
used by NT Workstations.
Note that this option is only useful if Samba is set up as a
logon server.
Example:
This parameter specifies the home directory location when a Win95/98 or
NT Workstation logs into a Samba PDC. It allows you to do
from a command prompt, for example.
This option takes the standard substitutions, allowing you to have
separate logon scripts for each user or machine.
Note that this option is only useful if Samba is set up as a
logon server.
Example:
Default:
This parameter specifies the home directory where roaming profiles
(USER.DAT / USER.MAN files for Windows 95/98) are stored.
This option takes the standard substitutions, allowing you to have
separate logon scripts for each user or machine. It also specifies
the directory from which the The share and the path must be readable by the user for the
preferences and directories to be loaded onto the Windows 95/98
client. The share must be writeable when the logs in for the first
time, in order that the Windows 95/98 client can create the user.dat
and other directories.
Thereafter, the directories and any of the contents can, if required, be
made read-only. It is not advisable that the USER.DAT file be made
read-only - rename it to USER.MAN to achieve the desired effect (a
MANdatory profile).
Windows clients can sometimes maintain a connection to the [homes]
share, even though there is no user logged in. Therefore, it is vital
that the logon path does not include a reference to the homes share
(i.e. setting this parameter to This option takes the standard substitutions, allowing you to have
separate logon scripts for each user or machine.
Note that this option is only useful if Samba is set up as a
logon server.
Default:
Example:
This parameter specifies the batch file (.bat) or NT command file
(.cmd) to be downloaded and run on a machine when a user successfully
logs in. The file must contain the DOS style cr/lf line endings.
Using a DOS-style editor to create the file is recommended.
The script must be a relative path to the The contents of the batch file is entirely your choice. A suggested
command would be to add Note that it is particularly important not to allow write access to
the This option takes the standard substitutions, allowing you to have
separate logon scripts for each user or machine.
Note that this option is only useful if Samba is set up as a
logon server.
Example:
This parameter specifies the command to be executed on the server host
in order to stop printing or spooling a specific print job.
This command should be a program or script which takes a printer name
and job number to pause the print job. One way of implementing this is
by using job priorities, where jobs having a too low priority won't be
sent to the printer.
If a Note that it is good practice to include the absolute path in the
lppause command as the PATH may not be available to the server.
See also the "printing" parameter.
Default:
Currently no default value is given to this string, unless the
value of the "printing" parameter is or if the value of the "printing" parameter is Example for HPUX:
lppause command = /usr/bin/lpalt %p-%j -p0
This controls how long lpq info will be cached for to prevent the
lpq command being called too often. A separate cache is kept for
each variation of the lpq command used by the system, so if you
use different lpq commands for different users then they won't
share cache information.
The cache files are stored in The default is 10 seconds, meaning that the cached results of a
previous identical lpq command will be used if the cached data is
less than 10 seconds old. A large value may be advisable if your
lpq command is very slow.
A value of 0 will disable caching completely.
See also the "printing" parameter.
Default:
Example:
This parameter specifies the command to be executed on the server host
in order to obtain This command should be a program or script which takes a printer name
as its only parameter and outputs printer status information.
Currently eight styles of printer status information are supported;
BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX and SOFTQ. This covers most UNIX
systems. You control which type is expected using the
"printing =" option.
Some clients (notably Windows for Workgroups) may not correctly send
the connection number for the printer they are requesting status
information about. To get around this, the server reports on the first
printer service connected to by the client. This only happens if the
connection number sent is invalid.
If a Note that it is good practice to include the absolute path in the lpq
command as the PATH may not be available to the server.
See also the "printing" parameter.
Default:
Example:
This parameter specifies the command to be executed on the server host
in order to restart or continue printing or spooling a specific print
job.
This command should be a program or script which takes a printer name
and job number to resume the print job. See also the "lppause
command" parameter.
If a Note that it is good practice to include the absolute path in the lpresume
command as the PATH may not be available to the server.
See also the "printing" parameter.
Default:
Currently no default value is given to this string, unless the
value of the "printing" parameter is or if the value of the "printing" parameter is Example for HPUX:
This parameter specifies the command to be executed on the server host
in order to delete a print job.
This command should be a program or script which takes a printer name
and job number, and deletes the print job.
If a Note that it is good practice to include the absolute path in the
lprm command as the PATH may not be available to the server.
See also the "printing" parameter.
Default:
Example 1:
Example 2:
If a Samba server is a member of an Windows NT Domain (see the
"security=domain") parameter) then
periodically a running smbd process will try and
change the MACHINE ACCOUNT PASWORD stored in the file called
See also smbpasswd (8), and the
"security=domain") parameter.
Default:
This parameter specifies the name of a file which will contain output
created by a magic script (see the "magic
script" parameter below).
Warning: If two clients use the same "magic
script" in the same directory the output file content
is undefined.
Default:
Example:
This parameter specifies the name of a file which, if opened, will be
executed by the server when the file is closed. This allows a UNIX
script to be sent to the Samba host and executed on behalf of the
connected user.
Scripts executed in this way will be deleted upon completion,
permissions permitting.
If the script generates output, output will be sent to the file
specified by the "magic output" parameter (see
above).
Note that some shells are unable to interpret scripts containing
carriage-return-linefeed instead of linefeed as the end-of-line
marker. Magic scripts must be executable "as is" on the host,
which for some hosts and some shells will require filtering at the DOS
end.
Magic scripts are EXPERIMENTAL and should NOT be relied upon.
Default:
Example:
See the section on "NAME MANGLING".
This option is was introduced with Samba 2.0.4 and above and has been
removed in Samba 2.0.6 as Samba now dynamically configures such things
on 32 bit systems.
This is for those who want to directly map UNIX file names which can
not be represented on Windows/DOS. The mangling of names is not always
what is needed. In particular you may have documents with file
extensions that differ between DOS and UNIX. For example, under UNIX
it is common to use So to map One very useful case is to remove the annoying default:
Example:
This controls whether non-DOS names under UNIX should be mapped to
DOS-compatible names ("mangled") and made visible, or whether non-DOS
names should simply be ignored.
See the section on "NAME MANGLING" for details
on how to control the mangling process.
If mangling is used then the mangling algorithm is as follows:
Note that the character to use may be specified using the
"mangling char" option, if you don't like
The two-digit hash value consists of upper case alphanumeric
characters.
This algorithm can cause name collisions only if files in a directory
share the same first five alphanumeric characters. The probability of
such a clash is 1/1300.
The name mangling (if enabled) allows a file to be copied between UNIX
directories from Windows/DOS while retaining the long UNIX
filename. UNIX files can be renamed to a new extension from
Windows/DOS and will retain the same basename. Mangled names do not
change between sessions.
Default:
Example:
This controls what character is used as the "magic" character in
name mangling. The default is a Default:
Example:
This parameter controls the number of mangled names that should be
cached in the Samba server smbd.
This stack is a list of recently mangled base names (extensions are
only maintained if they are longer than 3 characters or contains upper
case characters).
The larger this value, the more likely it is that mangled names can be
successfully converted to correct long UNIX names. However, large
stack sizes will slow most directory access. Smaller stacks save
memory in the server (each stack element costs 256 bytes).
It is not possible to absolutely guarantee correct long file names, so
be prepared for some surprises!
Default:
Example:
This controls whether the DOS archive attribute should be mapped to
the UNIX owner execute bit. The DOS archive bit is set when a file
has been modified since its last backup. One motivation for this
option it to keep Samba/your PC from making any file it touches from
becoming executable under UNIX. This can be quite annoying for shared
source code, documents, etc...
Note that this requires the "create mask"
parameter to be set such that owner execute bit is not masked out
(i.e. it must include 100). See the parameter "create
mask" for details.
Default:
Example:
This controls whether DOS style hidden files should be mapped to the
UNIX world execute bit.
Note that this requires the "create mask" to be
set such that the world execute bit is not masked out (i.e. it must
include 001). See the parameter "create mask"
for details.
Default:
Example:
This controls whether DOS style system files should be mapped to the
UNIX group execute bit.
Note that this requires the "create mask" to be
set such that the group execute bit is not masked out (i.e. it must
include 010). See the parameter "create mask"
for details.
Default:
Example:
This parameter is only useful in security modes
other than "security=share" - i.e. user,
server, and domain.
This parameter can take three different values, which tell
smbd what to do with user login requests that
don't match a valid UNIX user in some way.
The three settings are :
Note that this parameter is needed to set up "Guest" share
services when using security modes other than
share. This is because in these modes the name of the resource being
requested is *not* sent to the server until after the server has
successfully authenticated the client so the server cannot make
authentication decisions at the correct time (connection to the
share) for "Guest" shares.
For people familiar with the older Samba releases, this parameter
maps to the old compile-time setting of the GUEST_SESSSETUP value
in local.h.
Default:
This option allows the number of simultaneous connections to a service
to be limited. If "max connections" is greater than 0 then
connections will be refused if this number of connections to the
service are already open. A value of zero mean an unlimited number of
connections may be made.
Record lock files are used to implement this feature. The lock files
will be stored in the directory specified by the "lock
directory" option.
Default:
Example:
This option allows you to put an upper limit on the apparent size of
disks. If you set this option to 100 then all shares will appear to be
not larger than 100 MB in size.
Note that this option does not limit the amount of data you can put on
the disk. In the above case you could still store much more than 100
MB on the disk, but if a client ever asks for the amount of free disk
space or the total disk size then the result will be bounded by the
amount specified in "max disk size".
This option is primarily useful to work around bugs in some pieces of
software that can't handle very large disks, particularly disks over
1GB in size.
A "max disk size" of 0 means no limit.
Default:
Example:
This option (an integer in kilobytes) specifies the max size the log
file should grow to. Samba periodically checks the size and if it is
exceeded it will rename the file, adding a A size of 0 means no limit.
Default:
Example:
This option controls the maximum number of outstanding simultaneous
SMB operations that samba tells the client it will allow. You should
never need to set this parameter.
Default:
This parameter limits the maximum number of open files that one
smbd file serving process may have open for
a client at any one time. The default for this parameter is set
very high (10,000) as Samba uses only one bit per unopened file.
The limit of the number of open files is usually set by the
UNIX per-process file descriptor limit rather than this parameter
so you should never need to touch this parameter.
Default:
Synonym for ">(packetsize).
This option tells nmbd what the default 'time
to live' of NetBIOS names should be (in seconds) when
nmbd is requesting a name using either a
broadcast packet or from a WINS server. You should never need to
change this parameter. The default is 3 days.
Default:
This option tells nmbd when acting as a WINS
server (wins support =true) what the maximum
'time to live' of NetBIOS names that nmbd will
grant will be (in seconds). You should never need to change this
parameter. The default is 6 days (518400 seconds).
See also the "min wins ttl" parameter.
Default:
This option controls the maximum packet size that will be negotiated
by Samba. The default is 65535, which is the maximum. In some cases
you may find you get better performance with a smaller value. A value
below 2048 is likely to cause problems.
Default:
Example:
This specifies what command to run when the server receives a WinPopup
style message.
This would normally be a command that would deliver the message
somehow. How this is to be done is up to your imagination.
An example is:
This delivers the message using xedit, then removes it
afterwards. NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN
IMMEDIATELY. That's why I have the All messages are delivered as the global guest user. The command takes
the standard substitutions, although %u won't work
(%U may be better in this case).
Apart from the standard substitutions, some additional ones apply. In
particular:
You could make this command send mail, or whatever else takes your
fancy. Please let us know of any really interesting ideas you have.
Here's a way of sending the messages as mail to root:
If you don't have a message command then the message won't be
delivered and Samba will tell the sender there was an
error. Unfortunately WfWg totally ignores the error code and carries
on regardless, saying that the message was delivered.
If you want to silently delete it then try:
Default:
Example:
This sets the minimum amount of free disk space that must be available
before a user will be able to spool a print job. It is specified in
kilobytes. The default is 0, which means a user can always spool a print
job.
See also the printing parameter.
Default:
Example:
This option sets the minimum length in characters of a plaintext password
than smbd will accept when performing UNIX password changing.
See also "unix password sync",
"passwd program" and "passwd chat
debug".
Default:
This option tells nmbd when acting as a WINS
server (wins support = true) what the minimum
'time to live' of NetBIOS names that nmbd will
grant will be (in seconds). You should never need to change this
parameter. The default is 6 hours (21600 seconds).
Default:
This option is used by the programs in the Samba suite to determine
what naming services and in what order to resolve host names to IP
addresses. The option takes a space separated string of different name
resolution options.
The options are :"lmhosts", "host", "wins" and "bcast". They cause
names to be resolved as follows :
Default:
Example:
This will cause the local lmhosts file to be examined first, followed
by a broadcast attempt, followed by a normal system hostname lookup.
This is a list of NetBIOS names that nmbd will
advertise as additional names by which the Samba server is known. This
allows one machine to appear in browse lists under multiple names. If
a machine is acting as a browse server or
logon server none of these names will be
advertised as either browse server or logon servers, only the primary
name of the machine will be advertised with these capabilities.
See also "netbios name".
Default:
Example:
This sets the NetBIOS name by which a Samba server is known. By
default it is the same as the first component of the host's DNS name.
If a machine is a browse server or
logon server this name (or the first component
of the hosts DNS name) will be the name that these services are
advertised under.
See also "netbios aliases".
Default:
Example:
Get the home share server from a NIS map. For UNIX systems that use an
automounter, the user's home directory will often be mounted on a
workstation on demand from a remote server.
When the Samba logon server is not the actual home directory server,
but is mounting the home directories via NFS then two network hops
would be required to access the users home directory if the logon
server told the client to use itself as the SMB server for home
directories (one over SMB and one over NFS). This can be very
slow.
This option allows Samba to return the home share as being on a
different server to the logon server and as long as a Samba daemon is
running on the home directory server, it will be mounted on the Samba
client directly from the directory server. When Samba is returning the
home share to the client, it will consult the NIS map specified in
"homedir map" and return the server listed
there.
Note that for this option to work there must be a working NIS
system and the Samba server with this option must also be a
logon server.
Default:
Example:
This boolean parameter controls whether smbd
will attempt to map UNIX permissions into Windows NT access control lists.
Default:
Example:
This boolean parameter controls whether smbd
will allow Windows NT clients to connect to the NT SMB specific
Default:
This boolean parameter controls whether smbd
will negotiate NT specific SMB support with Windows NT
clients. Although this is a developer debugging option and should be
left alone, benchmarking has discovered that Windows NT clients give
faster performance with this option set to Default:
Allow or disallow client access to accounts that have null passwords.
See also smbpasswd (5).
Default:
Example:
This parameter allows an administrator to turn off the byte range lock
manipulation that is done within Samba to give compatibility for OLE
applications. Windows OLE applications use byte range locking as a
form of inter-process communication, by locking ranges of bytes around
the 2^32 region of a file range. This can cause certain UNIX lock
managers to crash or otherwise cause problems. Setting this parameter
to Default:
Example:
A synonym for "guest only".
This is a boolean option that controls whether connections with
usernames not in the user= list will be allowed. By
default this option is disabled so a client can supply a username to
be used by the server.
Note that this also means Samba won't try to deduce usernames from the
service name. This can be annoying for the [homes]
section. To get around this you could use "user =
%S" which means your "user" list
will be just the service name, which for home directories is the name
of the user.
See also the user parameter.
Default:
Example:
This boolean option tells smbd whether to issue oplocks (opportunistic
locks) to file open requests on this share. The oplock code can
dramatically (approx. 30% or more) improve the speed of access to files
on Samba servers. It allows the clients to aggressively cache files
locally and you may want to disable this option for unreliable network
environments (it is turned on by default in Windows NT Servers). For
more information see the file Speed.txt in the Samba docs/ directory.
Oplocks may be selectively turned off on certain files on a per share basis.
See the 'veto oplock files' parameter. On some systems oplocks are recognized
by the underlying operating system. This allows data synchronization between
all access to oplocked files, whether it be via Samba or NFS or a local
UNIX process. See the kernel oplocks parameter
for details.
See also the "kernel oplocks" and
"level2 oplocks" parameters.
Default:
Example:
This is a tuning parameter added due to bugs in both Windows 9x and WinNT.
If Samba responds to a client too quickly when that client issues an SMB that
can cause an oplock break request, then the client redirector can fail and
not respond to the break request. This tuning parameter (which is set in
milliseconds) is the amount of time Samba will wait before sending an
oplock break request to such (broken) clients.
DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA
OPLOCK CODE.
Default:
This is a very advanced smbd tuning option to improve
the efficiency of the granting of oplocks under multiple client contention for the same file.
In brief it specifies a number, which causes smbd not to grant an oplock even
when requested if the approximate number of clients contending for an oplock on
the same file goes over this limit. This causes smbd to
behave in a similar way to Windows NT.
DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA
OPLOCK CODE.
Default:
This integer value controls what level Samba advertises itself as for
browse elections. The value of this parameter determines whether
nmbd has a chance of becoming a local master
browser for the WORKGROUP in the local broadcast
area. The default is zero, which means nmbd will
lose elections to Windows machines. See BROWSING.txt in the Samba
docs/ directory for details.
Default:
Example:
This is a deprecated parameter that how no effect on the current
Samba code. It is left in the parameter list to prevent breaking
old smb.conf files.
This is a Samba developer option that allows a system command to be
called when either smbd or
nmbd crashes. This is usually used to draw
attention to the fact that a problem occurred.
Default:
This string controls the "chat" conversation that takes places
between smbd and the local password changing
program to change the users password. The string describes a sequence
of response-receive pairs that smbd uses to
determine what to send to the passwd program
and what to expect back. If the expected output is not received then
the password is not changed.
This chat sequence is often quite site specific, depending on what
local methods are used for password control (such as NIS etc).
The string can contain the macros The string can also contain a Double quotes can be used to collect strings with spaces in them into
a single string.
If the send string in any part of the chat sequence is a fullstop
Note that if the "unix password sync"
parameter is set to true, then this sequence is called *AS ROOT*
when the SMB password in the smbpasswd file is being changed, without
access to the old password cleartext. In this case the old password
cleartext is set to See also "unix password sync",
"passwd program" and "passwd chat
debug".
Example:
Default:
This boolean specifies if the passwd chat script parameter is run in
See also "passwd chat", "passwd
program".
Example:
Default:
The name of a program that can be used to set UNIX user passwords.
Any occurrences of %u will be replaced with the
user name. The user name is checked for existence before calling the
password changing program.
Also note that many passwd programs insist in "reasonable"
passwords, such as a minimum length, or the inclusion of mixed case
chars and digits. This can pose a problem as some clients (such as
Windows for Workgroups) uppercase the password before sending it.
Note that if the "unix password sync"
parameter is set to If the "unix password sync" parameter is
set this parameter MUST USE ABSOLUTE PATHS for ALL programs
called, and must be examined for security implications. Note that by
default "unix password sync" is set to
See also "unix password sync".
Default:
Example:
Some client/server combinations have difficulty with mixed-case
passwords. One offending client is Windows for Workgroups, which for
some reason forces passwords to upper case when using the LANMAN1
protocol, but leaves them alone when using COREPLUS!
This parameter defines the maximum number of characters that may be
upper case in passwords.
For example, say the password given was If password level was set to 2, the following combinations would
also be tried:
And so on.
The higher value this parameter is set to the more likely it is that a
mixed case password will be matched against a single case
password. However, you should be aware that use of this parameter
reduces security and increases the time taken to process a new
connection.
A value of zero will cause only two attempts to be made - the password
as is and the password in all-lower case.
Default:
Example:
By specifying the name of another SMB server (such as a WinNT box)
with this option, and using "security = domain" or
"security = server" you can get Samba to do all
its username/password validation via a remote server.
This options sets the name of the password server to use. It must be a
NetBIOS name, so if the machine's NetBIOS name is different from its
internet name then you may have to add its NetBIOS name to the lmhosts
file which is stored in the same directory as the smb.conf file.
The name of the password server is looked up using the parameter
"name resolve order=" and so may resolved
by any method and order described in that parameter.
The password server much be a machine capable of using the "LM1.2X002"
or the "LM NT 0.12" protocol, and it must be in user level security
mode.
NOTE: Using a password server means your UNIX box (running Samba) is
only as secure as your password server. DO NOT CHOOSE A PASSWORD
SERVER THAT YOU DON'T COMPLETELY TRUST.
Never point a Samba server at itself for password serving. This will
cause a loop and could lock up your Samba server!
The name of the password server takes the standard substitutions, but
probably the only useful one is %m, which means
the Samba server will use the incoming client as the password
server. If you use this then you better trust your clients, and you
better restrict them with hosts allow!
If the "security" parameter is set to
"domain", then the list of machines in this option must be a list
of Primary or Backup Domain controllers for the
Domain or the character If the "password server" option is set to the character If the "security" parameter is set to
"server", then there are different
restrictions that "security=domain"
doesn't suffer from:
See also the "security" parameter.
Default:
Example:
Example:
This parameter specifies a directory to which the user of the service
is to be given access. In the case of printable services, this is
where print data will spool prior to being submitted to the host for
printing.
For a printable service offering guest access, the service should be
readonly and the path should be world-writeable and have the sticky bit
set. This is not mandatory of course, but you probably won't get the
results you expect if you do otherwise.
Any occurrences of %u in the path will be replaced
with the UNIX username that the client is using on this
connection. Any occurrences of %m will be replaced
by the NetBIOS name of the machine they are connecting from. These
replacements are very useful for setting up pseudo home directories
for users.
Note that this path will be based on "root dir" if
one was specified.
Default:
Example:
This option specifies a command to be run whenever the service is
disconnected. It takes the usual substitutions. The command may be run
as the root on some systems.
An interesting example may be do unmount server resources:
See also preexec.
Default:
Example:
This parameter forces a printer to interpret the print files as
postscript. This is done by adding a This is most useful when you have lots of PCs that persist in putting
a control-D at the start of print jobs, which then confuses your
printer.
Default:
Example:
This option specifies a command to be run whenever the service is
connected to. It takes the usual substitutions.
An interesting example is to send the users a welcome message every
time they log in. Maybe a message of the day? Here is an example:
Of course, this could get annoying after a while :-)
See also preexec close and postexec.
Default:
Example:
This boolean option controls whether a non-zero return code from
"preexec" should close the service being connected to.
Default:
Example:
This boolean parameter controls if nmbd is a
preferred master browser for its workgroup.
If this is set to true, on startup, nmbd will
force an election, and it will have a slight advantage in winning the
election. It is recommended that this parameter is used in
conjunction with "domain master = yes", so
that nmbd can guarantee becoming a domain
master.
Use this option with caution, because if there are several hosts
(whether Samba servers, Windows 95 or NT) that are preferred master
browsers on the same subnet, they will each periodically and
continuously attempt to become the local master browser. This will
result in unnecessary broadcast traffic and reduced browsing
capabilities.
See also os level.
Default:
Example:
Synonym for "preferred master" for people
who cannot spell :-).
This controls if new filenames are created with the case that the
client passes, or if they are forced to be the Default:
See the section on "NAME MANGLING" for a
fuller discussion.
After a print job has finished spooling to a service, this command
will be used via a The print command is simply a text string. It will be used verbatim,
with two exceptions: All occurrences of The print command MUST contain at least one occurrence of If specified in the "[global]" section, the print
command given will be used for any printable service that does not
have its own print command specified.
If there is neither a specified print command for a printable service
nor a global print command, spool files will be created but not
processed and (most importantly) not removed.
Note that printing may fail on some UNIXs from the You can form quite complex print commands by realizing that they are
just passed to a shell. For example the following will log a print
job, print the file, then remove it. Note that You may have to vary this command considerably depending on how you
normally print files on your system. The default for the parameter
varies depending on the setting of the "printing="
parameter.
Default:
For "printing=" BSD, AIX, QNX, LPRNG or PLP :
For "printing=" SYS or HPUX :
For "printing=" SOFTQ :
Example:
Synonym for printable.
If this parameter is Note that a printable service will ALWAYS allow writing to the service
path (user privileges permitting) via the spooling of print data. The
"read only" parameter controls only non-printing
access to the resource.
Default:
Example:
Synonym for printcapname.
This parameter may be used to override the compiled-in default
printcap name used by the server (usually /etc/printcap). See the
discussion of the [printers] section above for
reasons why you might want to do this.
On System V systems that use lpstat to list available printers you
can use A minimal printcap file would look something like this:
where the NOTE: Under AIX the default printcap name is
Default:
Example:
This parameter specifies the name of the printer to which print jobs
spooled through a printable service will be sent.
If specified in the [global] section, the printer
name given will be used for any printable service that does not have
its own printer name specified.
Default:
none (but may be Example:
printer name = laserwriter
This option allows you to control the string that clients receive when
they ask the server for the printer driver associated with a
printer. If you are using Windows95 or WindowsNT then you can use this
to automate the setup of printers on your system.
You need to set this parameter to the exact string (case sensitive)
that describes the appropriate printer driver for your system. If you
don't know the exact string to use then you should first try with no
"printer driver" option set and the client will give you a list of
printer drivers. The appropriate strings are shown in a scrollbox
after you have chosen the printer manufacturer.
See also "printer driver file".
Example:
printer driver = HP LaserJet 4L
This parameter tells Samba where the printer driver definition file,
used when serving drivers to Windows 95 clients, is to be found. If
this is not set, the default is :
This file is created from Windows 95 Default:
Example:
See also "printer driver location".
This parameter tells clients of a particular printer share where to
find the printer driver files for the automatic installation of
drivers for Windows 95 machines. If Samba is set up to serve printer
drivers to Windows 95 machines, this should be set to
Where MACHINE is the NetBIOS name of your Samba server, and PRINTER$
is a share you set up for serving printer driver files. For more
details on setting this up see the documentation file in the docs/
directory, PRINTER_DRIVER.txt.
Default:
Example:
See also "printer driver file".
Synonym for printer.
This parameters controls how printer status information is interpreted
on your system, and also affects the default values for the
"print command", "lpq
command" "lppause command",
"lpresume command", and "lprm
command".
Currently eight printing styles are supported. They are
"printing=BSD", "printing=AIX", "printing=LPRNG",
"printing=PLP",
"printing=SYSV","printing="HPUX","printing=QNX" and
"printing=SOFTQ".
To see what the defaults are for the other print commands when using
these three options use the "testparm" program.
This option can be set on a per printer basis
See also the discussion in the [printers] section.
The value of the parameter (a string) is the highest protocol level
that will be supported by the server.
Possible values are :
Normally this option should not be set as the automatic negotiation
phase in the SMB protocol takes care of choosing the appropriate
protocol.
Default:
Example:
Synonym for "guest ok".
This parameter specifies the command to be executed on the server host
in order to pause the printerqueue.
This command should be a program or script which takes a printer name
as its only parameter and stops the printerqueue, such that no longer
jobs are submitted to the printer.
This command is not supported by Windows for Workgroups, but can be
issued from the Printer's window under Windows 95 & NT.
If a Note that it is good practice to include the absolute path in the
command as the PATH may not be available to the server.
Default:
Example:
This parameter specifies the command to be executed on the server host
in order to resume the printerqueue. It is the command to undo the
behavior that is caused by the previous parameter
("queuepause command).
This command should be a program or script which takes a printer name
as its only parameter and resumes the printerqueue, such that queued
jobs are resubmitted to the printer.
This command is not supported by Windows for Workgroups, but can be
issued from the Printer's window under Windows 95 & NT.
If a Note that it is good practice to include the absolute path in the
command as the PATH may not be available to the server.
Default:
Example:
This boolean parameter controls whether smbd
will support the "Read Block Multiplex" SMB. This is now rarely used
and defaults to off. You should never need to set this parameter.
Default:
read bmpx = No
This is a list of users that are given read-only access to a
service. If the connecting user is in this list then they will not be
given write access, no matter what the "read only"
option is set to. The list can include group names using the syntax
described in the "invalid users" parameter.
See also the "write list" parameter and
the "invalid users" parameter.
Default:
Example:
Note that this is an inverted synonym for
"writeable" and "write ok".
See also "writeable" and "write
ok".
NOTE: This code is currently disabled in Samba2.0 and
may be removed at a later date. Hence this parameter has
no effect.
This options enables or disables the read prediction code used to
speed up reads from the server. When enabled the server will try to
pre-read data from the last accessed file that was opened read-only
while waiting for packets.
Default:
This parameter controls whether or not the server will support the raw
read SMB requests when transferring data to clients.
If enabled, raw reads allow reads of 65535 bytes in one packet. This
typically provides a major performance benefit.
However, some clients either negotiate the allowable block size
incorrectly or are incapable of supporting larger block sizes, and for
these clients you may need to disable raw reads.
In general this parameter should be viewed as a system tuning tool and left
severely alone. See also "write raw".
Default:
The option "read size" affects the overlap of disk reads/writes
with network reads/writes. If the amount of data being transferred in
several of the SMB commands (currently SMBwrite, SMBwriteX and
SMBreadbraw) is larger than this value then the server begins writing
the data before it has received the whole packet from the network, or
in the case of SMBreadbraw, it begins writing to the network before
all the data has been read from disk.
This overlapping works best when the speeds of disk and network access
are similar, having very little effect when the speed of one is much
greater than the other.
The default value is 16384, but very little experimentation has been
done yet to determine the optimal value, and it is likely that the
best value will vary greatly between systems anyway. A value over
65536 is pointless and will cause you to allocate memory
unnecessarily.
Default:
Example:
This option allows you to setup nmbd to
periodically announce itself to arbitrary IP addresses with an
arbitrary workgroup name.
This is useful if you want your Samba server to appear in a remote
workgroup for which the normal browse propagation rules don't
work. The remote workgroup can be anywhere that you can send IP
packets to.
For example:
the above line would cause nmbd to announce itself to the two given IP
addresses using the given workgroup names. If you leave out the
workgroup name then the one given in the
"workgroup" parameter is used instead.
The IP addresses you choose would normally be the broadcast addresses
of the remote networks, but can also be the IP addresses of known
browse masters if your network config is that stable.
See the documentation file BROWSING.txt in the docs/ directory.
Default:
Example:
This option allows you to setup nmbd to
periodically request synchronization of browse lists with the master
browser of a samba server that is on a remote segment. This option
will allow you to gain browse lists for multiple workgroups across
routed networks. This is done in a manner that does not work with any
non-samba servers.
This is useful if you want your Samba server and all local clients to
appear in a remote workgroup for which the normal browse propagation
rules don't work. The remote workgroup can be anywhere that you can
send IP packets to.
For example:
the above line would cause nmbd to request the
master browser on the specified subnets or addresses to synchronize
their browse lists with the local server.
The IP addresses you choose would normally be the broadcast addresses
of the remote networks, but can also be the IP addresses of known
browse masters if your network config is that stable. If a machine IP
address is given Samba makes NO attempt to validate that the remote
machine is available, is listening, nor that it is in fact the browse
master on it's segment.
Default:
Example:
This is a boolean parameter. If it is true, then anonymous access
to the server will be restricted, namely in the case where the server
is expecting the client to send a username, but it doesn't. Setting
it to true will force these anonymous connections to be denied, and
the client will be required to always supply a username and password
when connecting. Use of this parameter is only recommened for homogenous
NT client environments.
This parameter makes the use of macro expansions that rely
on the username (%U, %G, etc) consistant. NT 4.0 likes to use
anonymous connections when refreshing the share list, and this
is a way to work around that.
When restrict anonymous is true, all anonymous connections are denied
no matter what they are for. This can effect the ability of a machine
to access the samba Primary Domain Controller to revalidate it's machine
account after someone else has logged on the client interactively. The
NT client will display a message saying that the machine's account in
the domain doesn't exist or the password is bad. The best way to deal
with this is to reboot NT client machines between interactive logons,
using "Shutdown and Restart", rather than "Close all programs and logon
as a different user".
Default:
Example:
Note that this option only works with
"security=share" and will be ignored if
this is not the case.
This option controls whether Samba will allow a previously validated
username/password pair to be used to attach to a share. Thus if you
connect to If "revalidate" is Default:
Example:
Synonym for "root directory".
Synonym for "root directory".
The server will Adding a "root directory" entry other than Default:
Example:
This is the same as the "postexec" parameter
except that the command is run as root. This is useful for unmounting
filesystems (such as cdroms) after a connection is closed.
See also "postexec".
This is the same as the "preexec" parameter except
that the command is run as root. This is useful for mounting
filesystems (such as cdroms) before a connection is finalized.
See also "preexec"
and "root preexec close".
This is the same as the "preexec close" parameter
except that the command is run as root.
See also "preexec", "preexec close".
This option affects how clients respond to Samba and is one of the most
important settings in the smb.conf file.
The option sets the The default is "security=user", as this is
the most common setting needed when talking to Windows 98 and Windows
NT.
The alternatives are "security = share",
"security = server" or
"security=domain".
*****NOTE THAT THIS DEFAULT IS DIFFERENT IN SAMBA2.0 THAN FOR
PREVIOUS VERSIONS OF SAMBA *******.
In previous versions of Samba the default was
"security=share" mainly because that was
the only option at one stage.
There is a bug in WfWg that has relevance to this setting. When in
user or server level security a WfWg client will totally ignore the
password you type in the "connect drive" dialog box. This makes it
very difficult (if not impossible) to connect to a Samba service as
anyone except the user that you are logged into WfWg as.
If your PCs use usernames that are the same as their usernames on the
UNIX machine then you will want to use "security = user". If you
mostly use usernames that don't exist on the UNIX box then use
"security = share".
You should also use security=share if
you want to mainly setup shares without a password (guest
shares). This is commonly used for a shared printer server. It is more
difficult to setup guest shares with
security=user, see the "map to
guest"parameter for details.
It is possible to use smbd in a "hybrid
mode" where it is offers both user and share level security under
different NetBIOS aliases. See the
NetBIOS aliases and the
include parameters for more information.
The different settings will now be explained.
Note that smbd *ALWAYS* uses a valid UNIX
user to act on behalf of the client, even in "security=share"
level security.
As clients are not required to send a username to the server
in share level security, smbd uses several
techniques to determine the correct UNIX user to use on behalf
of the client.
A list of possible UNIX usernames to match with the given
client password is constructed using the following methods :
If the "guest only" parameter is not set, then
this list is then tried with the supplied password. The first user for
whom the password matches will be used as the UNIX user.
If the "guest only" parameter is set, or no
username can be determined then if the share is marked as available to
the "guest account", then this guest user will
be used, otherwise access is denied.
Note that it can be *very* confusing in share-level security as to
which UNIX username will eventually be used in granting access.
See also the section "NOTE ABOUT USERNAME/PASSWORD
VALIDATION".
This is the default security setting in Samba2.0. With user-level
security a client must first Note that the name of the resource being requested is
*not* sent to the server until after the server has successfully
authenticated the client. This is why guest shares don't work in user
level security without allowing the server to automatically map unknown
users into the "guest account". See the
"map to guest" parameter for details on
doing this.
See also the section "NOTE ABOUT USERNAME/PASSWORD
VALIDATION".
In this mode Samba will try to validate the username/password by
passing it to another SMB server, such as an NT box. If this fails it
will revert to "security = user", but note that if encrypted
passwords have been negotiated then Samba cannot revert back to
checking the UNIX password file, it must have a valid smbpasswd file
to check users against. See the documentation file in the docs/
directory ENCRYPTION.txt for details on how to set this up.
Note that from the clients point of view "security=server" is
the same as "security=user". It only
affects how the server deals with the authentication, it does not in
any way affect what the client sees.
Note that the name of the resource being requested is
*not* sent to the server until after the server has successfully
authenticated the client. This is why guest shares don't work in server
level security without allowing the server to automatically map unknown
users into the "guest account". See the
"map to guest" parameter for details on
doing this.
See also the section "NOTE ABOUT USERNAME/PASSWORD
VALIDATION".
See also the "password server" parameter.
and the "encrypted passwords" parameter.
This mode will only work correctly if
smbpasswd has been used to add this machine
into a Windows NT Domain. It expects the "encrypted
passwords" parameter to be set to Note that a valid UNIX user must still exist as well as the
account on the Domain Controller to allow Samba to have a valid
UNIX account to map file access to.
Note that from the clients point of view "security=domain" is
the same as "security=user". It only
affects how the server deals with the authentication, it does not in
any way affect what the client sees.
Note that the name of the resource being requested is
*not* sent to the server until after the server has successfully
authenticated the client. This is why guest shares don't work in domain
level security without allowing the server to automatically map unknown
users into the "guest account". See the
"map to guest" parameter for details on
doing this.
BUG: There is currently a bug in the implementation of
"security=domain with respect to multi-byte character
set usernames. The communication with a Domain Controller
must be done in UNICODE and Samba currently does not widen
multi-byte user names to UNICODE correctly, thus a multi-byte
username will not be recognized correctly at the Domain Controller.
This issue will be addressed in a future release.
See also the section "NOTE ABOUT USERNAME/PASSWORD
VALIDATION".
See also the "password server" parameter.
and the "encrypted passwords" parameter.
Default:
Example:
This parameter controls what UNIX permission bits can be modified
when a Windows NT client is manipulating the UNIX permission on a
file using the native NT security dialog box.
This parameter is applied as a mask (AND'ed with) to the changed
permission bits, thus preventing any bits not in this mask from
being modified. Essentially, zero bits in this mask may be treated
as a set of bits the user is not allowed to change.
If not set explicitly this parameter is set to the same value as the
create mask parameter. To allow a user to
modify all the user/group/world permissions on a file, set this
parameter to 0777.
Note that users who can access the Samba server through other
means can easily bypass this restriction, so it is primarily
useful for standalone "appliance" systems. Administrators of
most normal systems will probably want to set it to 0777.
See also the force directory security
mode, directory security
mask, force security
mode parameters.
Default:
Example:
This controls what string will show up in the printer comment box in
print manager and next to the IPC connection in It also sets what will appear in browse lists next to the machine
name.
A A Default:
Example:
If The setdir command is only implemented in the Digital Pathworks
client. See the Pathworks documentation for details.
Default:
Example:
This enables or disables the honoring of the These open modes are not directly supported by UNIX, so they are
simulated using shared memory, or lock files if your UNIX doesn't
support shared memory (almost all do).
The share modes that are enabled by this option are DENY_DOS,
DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB.
This option gives full share compatibility and enabled by default.
You should *NEVER* turn this parameter off as many Windows
applications will break if you do so.
Default:
It specifies the size of the shared memory (in bytes) to use between
smbd processes. This parameter defaults to one
megabyte of shared memory. It is possible that if you have a large
server with many files open simultaneously that you may need to
increase this parameter. Signs that this parameter is set too low are
users reporting strange problems trying to save files (locking errors)
and error messages in the smbd log looking like If your OS refuses the size that Samba asks for then Samba will try a
smaller size, reducing by a factor of 0.8 until the OS accepts it.
Default:
Example:
This boolean parameter controls if new files which conform to 8.3
syntax, that is all in upper case and of suitable length, are created
upper case, or if they are forced to be the See the section on NAME MANGLING.
Default:
This option sets the path to the encrypted smbpasswd file. By default
the path to the smbpasswd file is compiled into Samba.
Default:
Example:
This sets the full path to the smbrun binary. This defaults to the
value in the Makefile.
You must get this path right for many services to work correctly.
You should not need to change this parameter so long as Samba
is installed correctly.
Default:
Example:
This option allows you to control what address Samba will listen for
connections on. This is used to support multiple virtual interfaces on
the one server, each with a different configuration.
By default samba will accept connections on any address.
Example:
This option allows you to set socket options to be used when talking
with the client.
Socket options are controls on the networking layer of the operating
systems which allow the connection to be tuned.
This option will typically be used to tune your Samba server for
optimal performance for your local network. There is no way that Samba
can know what the optimal parameters are for your net, so you must
experiment and choose them yourself. We strongly suggest you read the
appropriate documentation for your operating system first (perhaps
"man setsockopt" will help).
You may find that on some systems Samba will say "Unknown socket
option" when you supply an option. This means you either incorrectly
typed it or you need to add an include file to includes.h for your OS.
If the latter is the case please send the patch to
samba-bugs@samba.org.
Any of the supported socket options may be combined in any way you
like, as long as your OS allows it.
This is the list of socket options currently settable using this
option:
Those marked with a To specify an argument use the syntax SOME_OPTION=VALUE for example
If you are on a local network then a sensible option might be
If you have a local network then you could try:
If you are on a wide area network then perhaps try setting
IPTOS_THROUGHPUT.
Note that several of the options may cause your Samba server to fail
completely. Use these options with caution!
Default:
Example:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This variable enables or disables the entire SSL mode. If it is set to
"no", the SSL enabled samba behaves exactly like the non-SSL samba. If
set to "yes", it depends on the variables "ssl
hosts" and "ssl hosts resign"
whether an SSL connection will be required.
Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This variable defines where to look up the Certification
Authorities. The given directory should contain one file for each CA
that samba will trust. The file name must be the hash value over the
"Distinguished Name" of the CA. How this directory is set up is
explained later in this document. All files within the directory that
don't fit into this naming scheme are ignored. You don't need this
variable if you don't verify client certificates.
Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This variable is a second way to define the trusted CAs. The
certificates of the trusted CAs are collected in one big file and this
variable points to the file. You will probably only use one of the two
ways to define your CAs. The first choice is preferable if you have
many CAs or want to be flexible, the second is preferable if you only
have one CA and want to keep things simple (you won't need to create
the hashed file names). You don't need this variable if you don't
verify client certificates.
Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This variable defines the ciphers that should be offered during SSL
negotiation. You should not set this variable unless you know what you
are doing.
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
The certificate in this file is used by
smbclient if it exists. It's needed if the
server requires a client certificate.
Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This is the private key for smbclient. It's
only needed if the client should have a certificate.
Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This variable defines whether SSLeay should be configured for bug
compatibility with other SSL implementations. This is probably not
desirable because currently no clients with SSL implementations other
than SSLeay exist.
Default:
See "ssl hosts resign".
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
These two variables define whether samba will go into SSL mode or
not. If none of them is defined, samba will allow only SSL
connections. If the "ssl hosts" variable lists
hosts (by IP-address, IP-address range, net group or name), only these
hosts will be forced into SSL mode. If the "ssl hosts resign"
variable lists hosts, only these hosts will NOT be forced into SSL
mode. The syntax for these two variables is the same as for the
"hosts allow" and "hosts
deny" pair of variables, only that the subject of the
decision is different: It's not the access right but whether SSL is
used or not. See the "allow hosts" parameter for
details. The example below requires SSL connections from all hosts
outside the local net (which is 192.168.*.*).
Default:
Example:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
If this variable is set to Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
If this variable is set to Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This is the file containing the server's certificate. The server _must_
have a certificate. The file may also contain the server's private key.
See later for how certificates and private keys are created.
Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This file contains the private key of the server. If this variable is
not defined, the key is looked up in the certificate file (it may be
appended to the certificate). The server *must* have a private key
and the certificate *must* match this private key.
Default:
This variable is part of SSL-enabled Samba. This is only available if
the SSL libraries have been compiled on your system and the configure
option Note that for export control reasons this code is **NOT**
enabled by default in any current binary version of Samba.
This enumeration variable defines the versions of the SSL protocol
that will be used. Default:
This parameter determines if smbd will use a
cache in order to speed up case insensitive name mappings. You should
never need to change this parameter.
Default:
This parameter determines the number of entries in the stat
cache. You should never need to change this parameter.
Default:
This enables or disables logging of connections to a status file that
smbstatus can read.
With this disabled smbstatus won't be able
to tell you what connections are active. You should never need to
change this parameter.
Default:
status = yes
This is a boolean that controls the handling of file locking in the
server. When this is set to When strict locking is Well behaved clients always ask for lock checks when it is important,
so in the vast majority of cases "strict locking = no" is
preferable.
Default:
Example:
Many Windows applications (including the Windows 98 explorer shell)
seem to confuse flushing buffer contents to disk with doing a sync to
disk. Under UNIX, a sync call forces the process to be suspended until
the kernel has ensured that all outstanding data in kernel disk
buffers has been safely stored onto stable storage. This is very slow
and should only be done rarely. Setting this parameter to "no" (the
default) means that smbd ignores the Windows applications requests for
a sync call. There is only a possibility of losing data if the
operating system itself that Samba is running on crashes, so there is
little danger in this default setting. In addition, this fixes many
performance problems that people have reported with the new Windows98
explorer shell file copies.
See also the "sync always" parameter.
Default:
Example:
This is a boolean that controls whether to strip trailing dots off
UNIX filenames. This helps with some CDROMs that have filenames ending
in a single dot.
Default:
Example:
This is a boolean parameter that controls whether writes will always
be written to stable storage before the write call returns. If this is
false then the server will be guided by the client's request in each
write call (clients can set a bit indicating that a particular write
should be synchronous). If this is true then every write will be
followed by a fsync() call to ensure the data is written to disk.
Note that the "strict sync" parameter must be
set to See also the "strict sync" parameter.
Default:
Example:
This parameter maps how Samba debug messages are logged onto the
system syslog logging levels. Samba debug level zero maps onto syslog
LOG_ERR, debug level one maps onto LOG_WARNING, debug level two maps
onto LOG_NOTICE, debug level three maps onto LOG_INFO. All higher
levels are mapped to LOG_DEBUG.
This paramter sets the threshold for sending messages to syslog.
Only messages with debug level less than this value will be sent
to syslog.
Default:
If this parameter is set then Samba debug messages are logged into the
system syslog only, and not to the debug log files.
Default:
This parameter is a setting in minutes to add to the normal GMT to
local time conversion. This is useful if you are serving a lot of PCs
that have incorrect daylight saving time handling.
Default:
Example:
This parameter determines if nmbd advertises
itself as a time server to Windows clients. The default is False.
Default:
Example:
Samba2.0 will a timestamps to all log entries by default. This
can be distracting if you are attempting to debug a problem. This
parameter allows the timestamping to be turned off.
Default:
Example:
This boolean parameter controls whether Samba attempts to synchronize
the UNIX password with the SMB password when the encrypted SMB
password in the smbpasswd file is changed. If this is set to true the
program specified in the "passwd program"
parameter is called *AS ROOT* - to allow the new UNIX password to be
set without access to the old UNIX password (as the SMB password has
change code has no access to the old password cleartext, only the
new). By default this is set to See also "passwd program", "passwd
chat".
Default:
Example:
This boolean parameter when set causes samba to supply the real name
field from the unix password file to the client. This is useful for
setting up mail clients and WWW browsers on systems used by more than
one person.
Default:
Example:
This boolean parameter allows a user logging on with a plaintext
password to have their encrypted (hashed) password in the smbpasswd
file to be updated automatically as they log on. This option allows a
site to migrate from plaintext password authentication (users
authenticate with plaintext password over the wire, and are checked
against a UNIX account database) to encrypted password authentication
(the SMB challenge/response authentication mechanism) without forcing
all users to re-enter their passwords via smbpasswd at the time the
change is made. This is a convenience option to allow the change over
to encrypted passwords to be made over a longer period. Once all users
have encrypted representations of their passwords in the smbpasswd
file this parameter should be set to In order for this parameter to work correctly the "encrypt
passwords" parameter must be set to Note that even when this parameter is set a user authenticating to
smbd must still enter a valid password in order to connect correctly,
and to update their hashed (smbpasswd) passwords.
Default:
Example:
If this global parameter is a true, it specifies that the UNIX users
NOTE: The use of use rhosts can be a major security hole. This is
because you are trusting the PC to supply the correct username. It is
very easy to get a PC to supply a false username. I recommend that the
use rhosts option be only used if you really know what you are
doing.
Default:
Example:
Synonym for "username".
Synonym for "username".
Multiple users may be specified in a comma-delimited list, in which
case the supplied password will be tested against each username in
turn (left to right).
The username= line is needed only when the PC is unable to supply
its own username. This is the case for the COREPLUS protocol or where
your users have different WfWg usernames to UNIX usernames. In both
these cases you may also be better using the The username= line is not a great solution in many cases as it
means Samba will try to validate the supplied password against each of
the usernames in the username= line in turn. This is slow and a bad
idea for lots of users in case of duplicate passwords. You may get
timeouts or security breaches using this parameter unwisely.
Samba relies on the underlying UNIX security. This parameter does not
restrict who can login, it just offers hints to the Samba server as to
what usernames might correspond to the supplied password. Users can
login as whoever they please and they will be able to do no more
damage than if they started a telnet session. The daemon runs as the
user that they log in as, so they cannot do anything that user cannot
do.
To restrict a service to a particular set of users you can use the
"valid users=" parameter.
If any of the usernames begin with a If any of the usernames begin with a If any of the usernames begin with a Note that searching though a groups database can take quite some time,
and some clients may time out during the search.
See the section "NOTE ABOUT USERNAME/PASSWORD
VALIDATION" for more
information on how this parameter determines access to the services.
Default:
Examples:
This option helps Samba to try and 'guess' at the real UNIX username,
as many DOS clients send an all-uppercase username. By default Samba
tries all lowercase, followed by the username with the first letter
capitalized, and fails if the username is not found on the UNIX
machine.
If this parameter is set to non-zero the behavior changes. This
parameter is a number that specifies the number of uppercase
combinations to try whilst trying to determine the UNIX user name. The
higher the number the more combinations will be tried, but the slower
the discovery of usernames will be. Use this parameter when you have
strange usernames on your UNIX machine, such as Default:
Example:
This option allows you to specify a file containing a mapping of
usernames from the clients to the server. This can be used for several
purposes. The most common is to map usernames that users use on DOS or
Windows machines to those that the UNIX box uses. The other is to map
multiple users to a single username so that they can more easily share
files.
The map file is parsed line by line. Each line should contain a single
UNIX username on the left then a The file is processed on each line by taking the supplied username and
comparing it with each username on the right hand side of the If any line begins with a If any line begins with an For example to map from the name Or to map anyone in the UNIX group You can have as many mappings as you like in a username map file.
If your system supports the NIS NETGROUP option then the netgroup
database is checked before the You can map Windows usernames that have spaces in them by using double
quotes around the name. For example:
would map the windows username The following example would map mary and fred to the unix user sys,
and map the rest to guest. Note the use of the Note that the remapping is applied to all occurrences of
usernames. Thus if you connect to Also note that no reverse mapping is done. The main effect this has is
with printing. Users who have been mapped may have trouble deleting
print jobs as PrintManager under WfWg will think they don't own the
print job.
Default:
Example:
The option allows you to specify additional characters that should be
considered valid by the server in filenames. This is particularly
useful for national character sets, such as adding u-umlaut or a-ring.
The option takes a list of characters in either integer or character
form with spaces between them. If you give two characters with a colon
between them then it will be taken as an lowercase:uppercase pair.
If you have an editor capable of entering the characters into the
config file then it is probably easiest to use this method. Otherwise
you can specify the characters in octal, decimal or hexadecimal form
using the usual C notation.
For example to add the single character The last two examples above actually add two characters, and alter the
uppercase and lowercase mappings appropriately.
Note that you MUST specify this parameter after the "client
code page" parameter if you have both set. If
"client code page" is set after the
"valid chars" parameter the "valid chars" settings will be
overwritten.
See also the "client code page" parameter.
Default:
Example
The above example allows filenames to have the Swedish characters in
them.
NOTE: It is actually quite difficult to correctly produce a "valid
chars" line for a particular system. To automate the process
tino@augsburg.net has written a package called "validchars"
which will automatically produce a complete "valid chars" line for
a given client system. Look in the examples/validchars/ subdirectory
of your Samba source code distribution for this package.
This is a list of users that should be allowed to login to this
service. Names starting with If this is empty (the default) then any user can login. If a username
is in both this list and the "invalid users"
list then access is denied for that user.
The current servicename is substituted for
"%S". This is useful in the
[homes] section.
See also "invalid users".
Default:
Example:
This is a list of files and directories that are neither visible nor
accessible. Each entry in the list must be separated by a Each entry must be a unix path, not a DOS path and must *not* include the
unix directory separator Note that the "case sensitive" option is
applicable in vetoing files.
One feature of the veto files parameter that it is important to be
aware of, is that if a directory contains nothing but files that match
the veto files parameter (which means that Windows/DOS clients cannot
ever see them) is deleted, the veto files within that directory *are
automatically deleted* along with it, if the user has UNIX permissions
to do so.
Setting this parameter will affect the performance of Samba, as it
will be forced to check all files and directories for a match as they
are scanned.
See also "hide files" and "case
sensitive".
Default:
Examples:
Example 1.
Example 2.
This parameter is only valid when the "oplocks"
parameter is turned on for a share. It allows the Samba administrator
to selectively turn off the granting of oplocks on selected files that
match a wildcarded list, similar to the wildcarded list used in the
"veto files" parameter.
Default:
Examples:
You might want to do this on files that you know will be heavily
contended for by clients. A good example of this is in the NetBench
SMB benchmark program, which causes heavy client contention for files
ending in This allows you to override the volume label returned for a
share. Useful for CDROMs with installation programs that insist on a
particular volume label.
The default is the name of the share.
This parameter controls whether or not links in the UNIX file system
may be followed by the server. Links that point to areas within the
directory tree exported by the server are always allowed; this
parameter controls access only to areas that are outside the directory
tree being exported.
Note that setting this parameter can have a negative effect on your
server performance due to the extra system calls that Samba has to
do in order to perform the link checks.
Default:
Example:
This is a boolean that controls if nmbd will
respond to broadcast name queries on behalf of other hosts. You may
need to set this to Default:
This specifies the IP address (or DNS name: IP address for preference)
of the WINS server that nmbd should register with.
If you have a WINS server on your network then you should set this to
the WINS server's IP.
You should point this at your WINS server if you have a
multi-subnetted network.
NOTE. You need to set up Samba to point to a WINS server if you
have multiple subnets and wish cross-subnet browsing to work correctly.
See the documentation file BROWSING.txt in the docs/ directory of your
Samba source distribution.
Default:
Example:
When Samba is running as a WINS server this allows you to call an
external program for all changes to the WINS database. The primary use
for this option is to allow the dynamic update of external name
resolution databases such as dynamic DNS.
The wins hook parameter specifies the name of a script or executable
that will be called as follows:
wins_hook operation name nametype ttl IP_list
The first argument is the operation and is one of "add", "delete",
or "refresh". In most cases the operation can be ignored as the rest
of the parameters provide sufficient information. Note that "refresh"
may sometimes be called when the name has not previously been added,
in that case it should be treated as an add.
The second argument is the netbios name. If the name is not a legal
name then the wins hook is not called. Legal names contain only
letters, digits, hyphens, underscores and periods.
The third argument is the netbios name type as a 2 digit hexadecimal
number.
The fourth argument is the TTL (time to live) for the name in seconds.
The fifth and subsequent arguments are the IP addresses currently
registered for that name. If this list is empty then the name should
be deleted.
An example script that calls the BIND dynamic DNS update program
"nsupdate" is provided in the examples directory of the Samba source
code.
This boolean controls if the nmbd process in
Samba will act as a WINS server. You should not set this to true
unless you have a multi-subnetted network and you wish a particular
nmbd to be your WINS server. Note that you
should *NEVER* set this to true on more than one machine in your
network.
Default:
This controls what workgroup your server will appear to be in when
queried by clients. Note that this parameter also controls the Domain
name used with the "security=domain"
setting.
Default:
Example:
workgroup = MYGROUP
Synonym for "writeable" for people who can't spell :-).
This is a list of users that are given read-write access to a
service. If the connecting user is in this list then they will be
given write access, no matter what the "read only"
option is set to. The list can include group names using the @group
syntax.
Note that if a user is in both the read list and the write list then
they will be given write access.
See also the "read list" option.
Default:
Example:
Synonym for writeable.
This parameter controls whether or not the server will support raw
writes SMB's when transferring data from clients. You should never
need to change this parameter.
Default:
An inverted synonym is "read only".
If this parameter is Note that a printable service ("printable = yes")
will *ALWAYS* allow writing to the directory (user privileges
permitting), but only via spooling operations.
Default:
Examples:
Although the configuration file permits service names to contain
spaces, your client software may not. Spaces will be ignored in
comparisons anyway, so it shouldn't be a problem - but be aware of the
possibility.
On a similar note, many clients - especially DOS clients - limit
service names to eight characters. Smbd has no
such limitation, but attempts to connect from such clients will fail
if they truncate the service names. For this reason you should
probably keep your service names down to eight characters in length.
Use of the [homes] and [printers]
special sections make life for an administrator easy, but the various
combinations of default attributes can be tricky. Take extreme care
when designing these sections. In particular, ensure that the
permissions on spool directories are correct.
This man page is correct for version 2.0 of the Samba suite.
smbd (8), smbclient (1),
nmbd (8), testparm (1),
testprns (1), Samba,
nmblookup (1), smbpasswd (5),
smbpasswd (8).
Software Samba dan utilitas lain pertama kali dibuat oleh
Andrew Tridgell samba-bugs@samba.org.
Samba sekarang dikembangkan oleh tim Samba sebagai proyek Open Source, sama seperti pengembangan kernel Linux.
Samba is now developed
Manual pertama kali ditulis oleh Karl Auer. Manual ini kemudian dikonversikan ke format YODL
(satu software hebat lagi dari Open Source, tersedia bebas di ftp://ftp.icce.rug.nl/pub/unix/)
dan di-update pada Samba2.0 oleh Jeremy Allison.
Terjemahan bahasa Indonesia oleh M. ZEN Muttaqien aka. ZEN el GUAY atas nama tim Samba.
Silakan lihat samba (7) untuk mengetahui daftar lengkap kontributor dan detail mengenai bagaimana memberikan laporan bugs, komentar dan sebagainya.
Secara default rutin intenal yang akan digunakan
untuk penentuan kapasitas dan tempat sisa di hard disk.
dfree command = /usr/local/samba/bin/dfree
#!/bin/sh
df $1 | tail -1 | awk '{print $2" "$4}'
#!/bin/sh
/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
directory mask = 0755
directory mask = 0775
directory security mask = <sama seperti directory mask>
directory security mask = 0777
dns proxy = yes
domain logons = no
domain master = no
/proc
di Linux.
Parameter ini memungkinkan anda memberi koma pemisah dari dafar direktori itu
sehingga server selalu mengatakan bahwa direktori tersebut kosong.
"./proc"
bukan cuma "/proc"
.
Eksperimen adalah kebijakan terbaik, kata anggota tim :-)
kosong (artinya semua direktori gak masalah ditampilkan)
dont descend = /proc,/dev
dos filetime resolution = False
dos filetime resolution = True
dos filetimes = False
dos filetimes = True
fake directory create times = False
fake directory create times = True
"fake oplocks = yes"
smbd will
always grant oplock requests no matter how many clients are using the
file.
/etc/passwd
in their home directory for
instance. However it will slow filename lookups down slightly.
force create mode = 000
force create mode = 0755
force directory mode = 000
force directory mode = 0755
force directory security mode = <same as force directory mode>
force directory security mode = 0
force group = +sys
means
that only users who are already in group sys will have their default
primary group assigned to sys when accessing this Samba share. All
other users will retain their ordinary primary group.
no forced group
force group = agroup
force security mode = <same as force create mode>
force security mode = 0
"forced user"
, no matter what username the client connected as.
no forced user
force user = auser
fstype = NTFS
fstype = Samba
getwd cache = No
getwd cache = Yes
"su -"
command) and trying to print using the system print command such as
lpr (1) or lp (1).
specified at compile time, usually "nobody"
guest account = ftp
guest ok = no
guest ok = yes
guest only = no
guest only = yes
hide dot files = yes
hide dot files = no
'/'
, which allows
spaces to be included in the entry. '*'
and '?'
can be used
to specify multiple files or directories as in DOS wildcards.
'/'
.
No files or directories are hidden by this option (dot files are
hidden by default because of the "hide dot files" option).
hide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/
username server:/some/file/system
':'
. There should probably be a better parsing system that copes
with different map formats and also Amd (another automounter) maps.
homedir map = auto.home
homedir map = amd.homedir
"allow hosts = 150.203.5."
. The full syntax of the list is
described in the man page hosts_access (5). Note that this man
page may not be present on your system, so a brief description will
be given here also.
hosts allow = 150.203. EXCEPT 150.203.6.66
hosts allow = 150.203.15.0/255.255.255.0
hosts allow = lapland, arvidsjaur
hosts allow = @foonet
hosts deny = pirate
none (i.e., all hosts permitted access)
allow hosts = 150.203.5. myhost.mynet.edu.au
none (i.e., no hosts specifically excluded)
hosts deny = 150.203.4. badhost.mynet.edu.au
No host equivalences
hosts equiv = /etc/hosts.equiv
interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
'@'
is interpreted as an NIS netgroup first
(if your system supports NIS), and then as a UNIX group if the name
was not found in the NIS netgroup database.
'+'
is interpreted only by looking in the
UNIX group database. A name starting with '&'
is interpreted only
by looking in the NIS netgroup database (this requires NIS to be
working on your system). The characters '+'
and '&'
may be
used at the start of the name in either order so the value
"+&group"
means check the UNIX group database, followed by the NIS
netgroup database, and the value "&+group"
means check the NIS
netgroup database, followed by the UNIX group database (the same as
the '@'
prefix).
No invalid users
invalid users = root fred admin @wheel
keepalive = 0
keepalive = 60
empty string.
ldap port = 389.
empty string (no user defined)
empty string.
ldap server = localhost
"dn"
or LDAP "distinguished name"
that tells smbd to start from when searching
for an entry in the LDAP password database.
empty string.
"true"
). Note also, the "oplocks" parameter must
be set to "true" on this share in order for this parameter to have any
effect.
level2 oplocks = False
level2 oplocks = True
"true"
, "false"
, or "auto"
. The
default is "auto"
. If set to "false"
Samba will never produce
these broadcasts. If set to "true"
Samba will produce Lanman
announce broadcasts at a frequency set by the parameter "lm
interval". If set to "auto"
Samba will not send Lanman
announce broadcasts by default but will listen for them. If it hears
such a broadcast on the wire it will then start sending them at a
frequency set by the parameter "lm interval".
lm announce = auto
lm announce = true
lm interval = 60
lm interval = 120
load printers = yes
load printers = no
local master = yes
lock directory = /tmp/samba
lock directory = /usr/local/samba/var/locks
"locking = no"
, all lock and unlock requests will appear to
succeed and all lock queries will indicate that the queried lock is
clear.
"locking = yes"
, real locking will be performed by the server.
"no"
is not really recommended even in this case.
locking = yes
locking = no
log file = /usr/local/samba/var/log.%m
logon drive = h:
"NET USE H: /HOME"
logon home = "\\remote_smb_server\%U"
logon home = "\\%N\%U"
"desktop"
, "start menu"
,
"network neighborhood"
and "programs"
folders, and their
contents, are loaded and displayed on your Windows 95/98 client.
\\%N\HOMES\profile_path
will cause
problems).
logon path = \\%N\%U\profile
logon path = \\PROFILESERVER\HOME_DIR\%U\PROFILE
[netlogon]
service. If
the [netlogon]
service specifies a path of
/usr/local/samba/netlogon, and logon script = STARTUP.BAT, then the
file that will be downloaded is:
/usr/local/samba/netlogon/STARTUP.BAT
NET TIME \\SERVER /SET /YES
, to force every
machine to synchronize clocks with the same time server. Another use
would be to add NET USE U: \\SERVER\UTILS
for commonly used
utilities, or NET USE Q: \\SERVER\ISO9001_QA
for example.
[netlogon]
share, or to grant users write permission on the
batch files in a secure environment, as this would allow the batch
files to be arbitrarily modified and security to be breached.
logon script = scripts\%U.bat
"%p"
is given then the printername is put in its place. A
"%j"
is replaced with the job number (an integer). On HPUX (see
printing=hpux), if the "-p%p"
option is added
to the lpq command, the job will show up with the correct status,
i.e. if the job priority is lower than the set fence priority it will
have the PAUSED status, whereas if the priority is equal or higher it
will have the SPOOLED or PRINTING status.
SYSV
, in
which case the default is :
lp -i %p-%j -H hold
softq
,
then the default is:
qstat -s -j%j -h
/tmp/lpq.xxxx
where xxxx is a hash of
the lpq command in use.
lpq cache time = 10
lpq cache time = 30
"lpq"
-style printer status information.
%p
is given then the printername is put in its place. Otherwise
it is placed at the end of the command.
depends on the setting of printing =
lpq command = /usr/bin/lpq %p
%p
is given then the printername is put in its place. A
%j
is replaced with the job number (an integer).
SYSV
, in
which case the default is :
lp -i %p-%j -H resume
softq
,
then the default is:
qstat -s -j%j -r
lpresume command = /usr/bin/lpalt %p-%j -p2
%p
is given then the printername is put in its place. A
%j
is replaced with the job number (an integer).
depends on the setting of "printing ="
lprm command = /usr/bin/lprm -P%p %j
lprm command = /usr/bin/cancel %p-%j
<Domain>.<Machine>.mac
where <Domain>
is the name of the
Domain we are a member of and <Machine>
is the primary
"NetBIOS name" of the machine
smbd is running on. This parameter specifies how
often this password will be changed, in seconds. The default is one
week (expressed in seconds), the same as a Windows NT Domain member
server.
machine password timeout = 604800
magic output = <magic script name>.out
magic output = myfile.txt
None. Magic scripts disabled.
magic script = user.csh
".html"
for HTML files, whereas under
Windows/DOS ".htm"
is more commonly used.
"html"
to "htm"
you would use:
mangled map = (*.html *.htm)
";1"
off the ends
of filenames on some CDROMS (only visible under some UNIXs). To do
this use a map of (*;1 *).
no mangled map
mangled map = (*;1 *)
"~"
is appended to the first part of the mangled
name, followed by a two-character unique sequence, based on the
original root name (i.e., the original filename minus its final
extension). The final extension is included in the hash calculation
only if it contains any upper case characters or is longer than three
characters.
'~'
.
"___"
as its extension regardless
of actual original extension (that's three underscores).
mangled names = yes
mangled names = no
'~'
but
this may interfere with some software. Use this option to set it to
whatever you prefer.
mangling char = ~
mangling char = ^
mangled stack = 50
mangled stack = 100
map archive = yes
map archive = no
map hidden = no
map hidden = yes
map system = no
map system = yes
map to guest = Never
Example:
map to guest = Bad User
max connections = 0
max connections = 10
max disk size = 0
max disk size = 1000
".old"
extension.
max log size = 5000
max log size = 1000
max mux = 50
max open files = 10000
max ttl = 259200
max wins ttl = 518400
max xmit = 65535
max xmit = 8192
message command = csh -c 'xedit %s;rm %s' &
'&'
on the end. If it doesn't
return immediately then your PCs may freeze when sending messages
(they should recover after 30secs, hopefully).
"%s"
= the filename containing the message.
"%t"
= the destination that the message was sent to (probably the server
name).
"%f"
= who the message is from.
message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s
"message command = rm %s"
.
no message command
message command = csh -c 'xedit %s;rm %s' &
min print space = 0
min print space = 2000
min passwd length = 5
min wins ttl = 21600
name resolve order = lmhosts host wins bcast
name resolve order = lmhosts bcast host
empty string (no additional names)
netbios aliases = TEST TEST1 TEST2
Machine DNS name.
netbios name = MYNAME
nis homedir = false
nis homedir = true
nt acl support = yes
nt acl support = no
IPC$
pipes. This is a developer debugging option and can be left
alone.
nt pipe support = yes
"no"
. This is still
being investigated. If this option is set to "no"
then Samba
offers exactly the same SMB calls that versions prior to Samba2.0
offered. This information may be of use if any users are having
problems with NT SMB support.
nt support = yes
null passwords = no
null passwords = yes
"no"
means you trust your UNIX lock manager to handle such cases
correctly.
ole locking compatibility = yes
ole locking compatibility = no
only user = False
only user = True
oplocks = True
oplocks = False
oplock break wait time = 10
oplock contention limit = 2
os level = 20
os level = 65 ; This will win against any NT Server
panic action = <empty string>
"%o"
and "%n"
which are
substituted for the old and new passwords respectively. It can also
contain the standard macros "\n"
, "\r"
, "\t"
and "\s"
to give line-feed, carriage-return, tab and space.
'*'
which matches any sequence of
characters.
"."
then no string is sent. Similarly, is the expect string is a
fullstop then no string is expected.
""
(the empty string).
passwd chat = "*Enter OLD password*" %o\n "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*"
passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed*
"debug"
mode. In this mode the strings passed to and received from
the passwd chat are printed in the smbd log with
a "debug level" of 100. This is a dangerous
option as it will allow plaintext passwords to be seen in the
smbd log. It is available to help Samba admins
debug their "passwd chat" scripts when calling
the "passwd program" and should be turned off
after this has been done. This parameter is off by default.
passwd chat debug = True
passwd chat debug = False
"True"
then this program is called *AS
ROOT* before the SMB password in the
smbpasswd file is changed. If this UNIX
password change fails, then smbd will fail to
change the SMB password also (this is by design).
"False"
.
passwd program = /bin/passwd
passwd program = /sbin/passwd %u
"FRED"
. If password
level is set to 1, the following combinations would be tried if
"FRED"
failed:
"Fred"
, "fred"
, "fRed"
, "frEd"
, "freD"
"FRed"
, "FrEd"
, "FreD"
, "fREd"
, "fReD"
,
"frED"
, ..
password level = 0
password level = 4
*
, as the Samba server is cryptographicly
in that domain, and will use cryptographicly authenticated RPC calls
to authenticate the user logging on. The advantage of using
"security=domain" is that if you list
several hosts in the "password server" option then
smbd will try each in turn till it finds one
that responds. This is useful in case your primary server goes down.
*
,
then Samba will attempt to auto-locate the Primary or Backup Domain controllers
to authenticate against by doing a query for the name WORKGROUP<1C>
and then contacting each server returned in the list of IP addresses
from the name resolution source.
password server = <empty string>
password server = NT-PDC, NT-BDC1, NT-BDC2
password server = *
none
path = /home/fred
postexec = /etc/umount /cdrom
none (no command executed)
postexec = echo "%u disconnected from %S from %m (%I)" >> /tmp/log
%!
to the start of print output.
postscript = False
postscript = True
preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' &
none (no command executed)
preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log
preexec close = no
preexec close = yes
preferred master = no
preferred master = yes
"default"
case.
preserve case = yes
system()
call to process the spool
file. Typically the command specified will submit the spool file to
the host's printing subsystem, but there is no requirement that this
be the case. The server will not remove the spool file, so whatever
command you specify should remove the spool file when it has been
processed, otherwise you will need to manually remove old spool files.
"%s"
and "%f"
will be
replaced by the appropriate spool file name, and all occurrences of
"%p"
will be replaced by the appropriate printer name. The spool
file name is generated automatically by the server, the printer name
is discussed below.
"%s"
or "%f"
- the "%p"
is optional. At the time a job is
submitted, if no printer name is supplied the "%p"
will be
silently removed from the printer command.
"nobody"
account. If this happens then create an alternative guest account that
can print and set the "guest account" in the
"[global]" section.
';'
is the usual
separator for command in shell scripts.
print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s
print command = lpr -r -P%p %s
print command = lp -c -d%p %s; rm %s
print command = lp -d%p -s %s; rm %s
print command = /usr/local/samba/bin/myprintscript %p %s
"yes"
, then clients may open, write to and
submit spool files on the directory specified for the service.
printable = no
printable = yes
"printcap name = lpstat"
to automatically obtain lists of
available printers. This is the default for systems that define SYSV
at configure time in Samba (this includes most System V based
systems). If "printcap name" is set to lpstat on these systems
then Samba will launch "lpstat -v"
and attempt to parse the output
to obtain a printer list.
print1|My Printer 1
print2|My Printer 2
print3|My Printer 3
print4|My Printer 4
print5|My Printer 5
'|'
separates aliases of a printer. The fact that the
second alias has a space in it gives a hint to Samba that it's a
comment.
"/etc/qconfig"
. Samba will assume the file is in AIX "qconfig"
format if the string "/qconfig"
appears in the printcap filename.
printcap name = /etc/printcap
printcap name = /etc/myprintcap
"lp"
on many systems)
SAMBA_INSTALL_DIRECTORY/lib/printers.def
"msprint.def"
files found on
the Windows 95 client system. For more details on setting up serving
of printer drivers to Windows 95 clients, see the documentation file
in the docs/ directory, PRINTER_DRIVER.txt.
None (set in compile).
printer driver file = /usr/local/samba/printers/drivers.def
\\MACHINE\PRINTER$
None
printer driver location = \\MACHINE\PRINTER$
protocol = NT1
protocol = LANMAN1
"%p"
is given then the printername is put in its
place. Otherwise it is placed at the end of the command.
depends on the setting of "printing ="
queuepause command = disable %p
"%p"
is given then the printername is put in its
place. Otherwise it is placed at the end of the command.
depends on the setting of "printing ="
queuepause command = enable %p
read list = <empty string>
read list = mary, @students
read prediction = False
read raw = yes
read size = 16384
read size = 8192
remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF
remote announce = <empty string>
remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF
remote browse sync = 192.168.2.255 192.168.4.255
remote browse sync = <empty string>
remote browse sync = 192.168.2.255 192.168.4.255
restrict anonymous = false
restrict anonymous = true
\\server\share1
then to \\server\share2
it won't
automatically allow the client to request connection to the second
share as the same username as the first without a password.
"True"
then the client will be denied
automatic access as the same username.
revalidate = False
revalidate = True
"chroot()"
(i.e. Change it's root directory) to
this directory on startup. This is not strictly necessary for secure
operation. Even without it the server will deny access to files not in
one of the service entries. It may also check for, and deny access to,
soft links to other parts of the filesystem, or attempts to use
".."
in file names to access other directories (depending on the
setting of the "wide links" parameter).
"/"
adds an extra
level of security, but at a price. It absolutely ensures that no
access is given to files not in the sub-tree specified in the "root
directory" option, *including* some files needed for complete
operation of the server. To maintain full operability of the server
you will need to mirror some system files into the "root
directory" tree. In particular you will need to mirror /etc/passwd
(or a subset of it), and any binaries or configuration files needed
for printing (if required). The set of files that must be mirrored is
operating system dependent.
root directory = /
root directory = /homes/smb
"security mode bit"
in replies to protocol
negotiations with smbd to turn share level
security on or off. Clients decide based on this bit whether (and how)
to transfer user and password information to the server.
"log-on"
with a valid username and
password (which can be mapped using the "username
map" parameter). Encrypted passwords (see the
"encrypted passwords" parameter) can also
be used in this security mode. Parameters such as
"user" and "guest only", if set
are then applied and may change the UNIX user to use on this
connection, but only after the user has been successfully
authenticated.
"true"
. In
this mode Samba will try to validate the username/password by passing
it to a Windows NT Primary or Backup Domain Controller, in exactly the
same way that a Windows NT Server would do.
security = USER
security = DOMAIN
security mask = <same as create mask>
security mask = 0777
"net view"
. It can be
any string that you wish to show to your users.
"%v"
will be replaced with the Samba version number.
"%h"
will be replaced with the hostname.
server string = Samba %v
server string = University of GNUs Samba Server
"set directory = no"
, then users of the service may not use the
setdir command to change directory.
set directory = no
set directory = yes
"share modes"
during a
file open. These modes are used by clients to gain exclusive read or
write access to a file.
share modes = yes
"ERROR
smb_shm_alloc : alloc of XX bytes failed"
.
shared mem size = 1048576
shared mem size = 5242880 ; Set to 5mb for a large number of files.
"default"
case. This
option can be use with "preserve case
=yes" to permit long filenames to retain their
case, while short names are lowered. Default Yes.
short preserve case = yes
smb passwd file= <compiled default>
smb passwd file = /usr/samba/private/smbpasswd
smbrun=<compiled default>
smbrun = /usr/local/samba/bin/smbrun
socket address = 192.168.2.20
*
take an integer argument. The others can
optionally take a 1 or 0 argument to enable or disable the option, by
default they will be enabled if you don't specify 1 or 0.
SO_SNDBUF=8192
. Note that you must not have any spaces before or after
the = sign.
socket options = IPTOS_LOWDELAY
socket options = IPTOS_LOWDELAY TCP_NODELAY
socket options = TCP_NODELAY
socket options = IPTOS_LOWDELAY
"--with-ssl"
was given at configure time.
ssl=no
Example:
ssl=yes
"--with-ssl"
was given at configure time.
ssl CA certDir = /usr/local/ssl/certs
"--with-ssl"
was given at configure time.
ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem
"--with-ssl"
was given at configure time.
"--with-ssl"
was given at configure time.
ssl client cert = /usr/local/ssl/certs/smbclient.pem
"--with-ssl"
was given at configure time.
ssl client key = /usr/local/ssl/private/smbclient.pem
"--with-ssl"
was given at configure time.
ssl compatibility = no
"--with-ssl"
was given at configure time.
ssl hosts = <empty string>
ssl hosts resign = <empty string>
ssl hosts resign = 192.168.
"--with-ssl"
was given at configure time.
"yes"
, the server will not tolerate
connections from clients that don't have a valid certificate. The
directory/file given in "ssl CA certDir" and
"ssl CA certFile" will be used to look up the
CAs that issued the client's certificate. If the certificate can't be
verified positively, the connection will be terminated. If this
variable is set to "no"
, clients don't need certificates. Contrary
to web applications you really *should* require client
certificates. In the web environment the client's data is sensitive
(credit card numbers) and the server must prove to be trustworthy. In
a file server environment the server's data will be sensitive and the
clients must prove to be trustworthy.
ssl require clientcert = no
"--with-ssl"
was given at configure time.
"yes"
, the
smbclient will request a certificate from
the server. Same as "ssl require
clientcert" for the server.
ssl require servercert = no
"--with-ssl"
was given at configure time.
ssl server cert = <empty string>
"--with-ssl"
was given at configure time.
ssl server key = <empty string>
"--with-ssl"
was given at configure time.
"ssl2or3"
allows dynamic negotiation of SSL v2
or v3, "ssl2"
results in SSL v2, "ssl3"
results in SSL v3 and
"tls1" results in TLS v1. TLS (Transport Layer Security) is the
(proposed?) new standard for SSL.
ssl version = "ssl2or3"
stat cache = yes
stat cache size = 50
"yes"
the server will check every read and
write access for file locks, and deny access if locks exist. This can
be slow on some systems.
"no"
the server does file lock checks only
when the client explicitly asks for them.
strict locking = no
strict locking = yes
strict sync = no
strict sync = yes
strip dot = no
strip dot = yes
"yes"
in order for this parameter to have any affect.
sync always = no
sync always = yes
syslog = 1
syslog only = no
time offset = 0
time offset = 60
time server = False
time server = True
timestamp logs = True
timestamp logs = False
"false"
.
unix password sync = False
unix password sync = True
unix realname = no
unix realname = yes
"off"
.
"no"
when
this parameter is set to "yes"
.
update encrypted = no
update encrypted = yes
".rhosts"
file in their home directory will be read to find the
names of hosts and users who will be allowed access without specifying
a password.
use rhosts = no
use rhosts = yes
\\server\share%user
syntax instead.
'@'
then the name will be
looked up first in the yp netgroups list (if Samba is compiled with
netgroup support), followed by a lookup in the UNIX groups database
and will expand to a list of all users in the group of that name.
'+'
then the name will be
looked up only in the UNIX groups database and will expand to a list
of all users in the group of that name.
'&'
then the name will be
looked up only in the yp netgroups database (if Samba is compiled with
netgroup support) and will expand to a list of all users in the
netgroup group of that name.
The guest account if a guest service, else the name of the service.
username = fred
username = fred, mary, jack, jane, @users, @pcgroup
"AstrangeUser"
.
username level = 0
username level = 5
'='
followed by a list of
usernames on the right. The list of usernames on the right may contain
names of the form @group in which case they will match any UNIX
username in that group. The special client name '*'
is a wildcard
and matches any name. Each line of the map file may be up to 1023
characters long.
'='
signs. If the supplied name matches any of the names on the right hand
side then it is replaced with the name on the left. Processing then
continues with the next line.
'#'
or a ';'
then it is ignored
'!'
then the processing will stop after
that line if a mapping was done by the line. Otherwise mapping
continues with every line being processed. Using '!'
is most
useful when you have a wildcard mapping line later in the file.
"admin"
or "administrator"
to
the UNIX name "root"
you would use:
root = admin administrator
"system"
to the UNIX name
"sys"
you would use:
sys = @system
/etc/group
database for matching
groups.
tridge = "Andrew Tridgell"
"Andrew Tridgell"
to the unix
username tridge.
'!'
to tell Samba
to stop processing if it gets a match on that line.
!sys = mary fred
guest = *
"\\server\fred"
and "fred"
is remapped to "mary"
then you will actually be connecting to
"\\server\mary"
and will need to supply a password suitable for
"mary"
not "fred"
. The only exception to this is the username
passed to the "password server" (if you have
one). The password server will receive whatever username the client
supplies without modification.
no username map
username map = /usr/local/samba/lib/users.map
'Z'
to the charset (which
is a pointless thing to do as it's already there) you could do one of
the following
valid chars = Z
valid chars = z:Z
valid chars = 0132:0172
Samba defaults to using a reasonable set of valid characters
for English systems
valid chars = 0345:0305 0366:0326 0344:0304
'@'
, '+'
and '&'
are
interpreted using the same rules as described in the "invalid
users" parameter.
No valid users list. (anyone can login)
valid users = greg, @pcusers
'/'
,
which allows spaces to be included in the entry. '*'
and '?'
can be used to specify multiple files or directories as in DOS
wildcards.
'/'
.
No files or directories are vetoed.
Veto any files containing the word Security,
any ending in .tmp, and any directory containing the
word root.
veto files = /*Security*/*.tmp/*root*/
Veto the Apple specific files that a NetAtalk server
creates.
veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
No files are vetoed for oplock grants.
".SEM"
. To cause Samba not to grant oplocks on these
files you would use the line (either in the [global]
section or in the section for the particular NetBench share :
veto oplock files = /*.SEM/
wide links = yes
wide links = no
"yes"
for some older clients.
wins proxy = no
wins server =
wins server = 192.9.200.1
wins support = no
set at compile time to WORKGROUP
write list = <empty string>
write list = admin, root, @staff
write raw = yes
"no"
, then users of a service may not create
or modify files in the service's directory.
writeable = no
read only = no
writeable = yes
write ok = yes
WARNINGS
VERSION
SEE ALSO
AUTHOR