summaryrefslogtreecommitdiffstats
path: root/docs/htmldocs/smb.conf.5.html
blob: e16d79fbd266054fc051a3048d534093dc02cbfc (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071



 



<html><head><title>smb.conf (5)</title>

<link rev="made" href="mailto:samba@samba.org">
</head>
<body>

<hr>

<h1>smb.conf (5)</h1>
<h2>Samba</h2>
<h2>23 Oct 1998</h2>


    
<p><a name="NAME"></a>
<h2>NAME</h2>
    smb.conf - The configuration file for the Samba suite
<p><a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
     
<p><strong>smb.conf</strong> The <strong>smb.conf</strong> file is a configuration file for the
Samba suite. <strong>smb.conf</strong> contains runtime configuration information
for the Samba programs. The <strong>smb.conf</strong> file is designed to be
configured and administered by the <a href="swat.8.html"><strong>swat (8)</strong></a>
program. The complete description of the file format and possible
parameters held within are here for reference purposes.
<p><a name="FILEFORMAT"></a>
<h2>FILE FORMAT</h2>
    
<p>The file consists of sections and parameters. A section begins with
the name of the section in square brackets and continues until the
next section begins. Sections contain parameters of the form 
<p><code>'name = value'</code>
<p>The file is line-based - that is, each newline-terminated line
represents either a comment, a section name or a parameter.
<p>Section and parameter names are not case sensitive.
<p>Only the first equals sign in a parameter is significant. Whitespace
before or after the first equals sign is discarded. Leading, trailing
and internal whitespace in section and parameter names is
irrelevant. Leading and trailing whitespace in a parameter value is
discarded. Internal whitespace within a parameter value is retained
verbatim.
<p>Any line beginning with a semicolon (';') or a hash ('#') character is
ignored, as are lines containing only whitespace.
<p>Any line ending in a <code>'\'</code> is "continued" on the next line in the
customary UNIX fashion.
<p>The values following the equals sign in parameters are all either a
string (no quotes needed) or a boolean, which may be given as yes/no,
0/1 or true/false. Case is not significant in boolean values, but is
preserved in string values. Some items such as create modes are
numeric.
<p><a name="SECTIONDESCRIPTIONS"></a>
<h2>SECTION DESCRIPTIONS</h2>
    
<p>Each section in the configuration file (except for the
<a href="smb.conf.5.html#global"><strong>[global]</strong></a> section) describes a shared resource (known
as a <em>"share"</em>). The section name is the name of the shared resource
and the parameters within the section define the shares attributes.
<p>There are three special sections, <a href="smb.conf.5.html#global"><strong>[global]</strong></a>,
<a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> and <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a>, which are
described under <a href="smb.conf.5.html#SPECIALSECTIONS"><strong>'special sections'</strong></a>. The
following notes apply to ordinary section descriptions.
<p>A share consists of a directory to which access is being given plus
a description of the access rights which are granted to the user of
the service. Some housekeeping options are also specifiable.
<p>Sections are either filespace services (used by the client as an
extension of their native file systems) or printable services (used by
the client to access print services on the host running the server).
<p>Sections may be designated <a href="smb.conf.5.html#guestok"><strong>guest</strong></a> services, in which
case no password is required to access them. A specified UNIX
<a href="smb.conf.5.html#guestaccount"><strong>guest account</strong></a> is used to define access
privileges in this case.
<p>Sections other than guest services will require a password to access
them. The client provides the username. As older clients only provide
passwords and not usernames, you may specify a list of usernames to
check against the password using the <a href="smb.conf.5.html#user"><strong>"user="</strong></a> option in
the share definition. For modern clients such as Windows 95/98 and
Windows NT, this should not be necessary.
<p>Note that the access rights granted by the server are masked by the
access rights granted to the specified or guest UNIX user by the host
system. The server does not grant more access than the host system
grants.
<p>The following sample section defines a file space share. The user has
write access to the path <code>/home/bar</code>. The share is accessed via
the share name "foo":
<p><pre>


 	[foo]
 		path = /home/bar
 		writeable = true


</pre>

<p>The following sample section defines a printable share. The share
is readonly, but printable. That is, the only write access permitted
is via calls to open, write to and close a spool file. The
<a href="smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> parameter means access will be permitted
as the default guest user (specified elsewhere):
<p><pre>

 	[aprinter]
 		path = /usr/spool/public
 		writeable = false
 		printable = true
 		guest ok = true

</pre>

<p><a name="SPECIALSECTIONS"></a>
<h2>SPECIAL SECTIONS</h2>
    
<p><dl>
<p><a name="global"></a>
<p></p><dt><strong><strong>The [global] section</strong></strong><dd>
<p>Parameters in this section apply to the server as a whole, or are
defaults for sections which do not specifically define certain
items. See the notes under <a href="smb.conf.5.html#PARAMETERS"><strong>'PARAMETERS'</strong></a> for more
information.
<p><a name="homes"></a>
<p></p><dt><strong><strong>The [homes] section</strong></strong><dd>
<p>If a section called <code>'homes'</code> is included in the configuration file,
services connecting clients to their home directories can be created
on the fly by the server.
<p>When the connection request is made, the existing sections are
scanned. If a match is found, it is used. If no match is found, the
requested section name is treated as a user name and looked up in the
local password file. If the name exists and the correct password has
been given, a share is created by cloning the [homes] section.
<p>Some modifications are then made to the newly created share:
<p><dl>
<p><li > The share name is changed from <code>'homes'</code> to the located
username
<p><li > If no path was given, the path is set to the user's home
directory.
<p></dl>
<p>If you decide to use a <a href="smb.conf.5.html#path"><strong>path=</strong></a> line in your [homes]
section then you may find it useful to use the <a href="smb.conf.5.html#percentS"><strong>%S</strong></a>
macro. For example :
<p><code>path=/data/pchome/%S</code>
<p>would be useful if you have different home directories for your PCs
than for UNIX access.
<p>This is a fast and simple way to give a large number of clients access
to their home directories with a minimum of fuss.
<p>A similar process occurs if the requested section name is <code>"homes"</code>,
except that the share name is not changed to that of the requesting
user. This method of using the [homes] section works well if different
users share a client PC.
<p>The [homes] section can specify all the parameters a normal service
section can specify, though some make more sense than others. The
following is a typical and suitable [homes] section:
<p><pre>

 	[homes]
 		writeable = yes

</pre>

<p>An important point is that if guest access is specified in the [homes]
section, all home directories will be visible to all clients
<strong>without a password</strong>. In the very unlikely event that this is
actually desirable, it would be wise to also specify <a href="smb.conf.5.html#readonly"><strong>read only
access</strong></a>.
<p>Note that the <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a> flag for auto home
directories will be inherited from the global browseable flag, not the
[homes] browseable flag. This is useful as it means setting
browseable=no in the [homes] section will hide the [homes] share but
make any auto home directories visible.
<p><a name="printers"></a>
<p></p><dt><strong><strong>The [printers] section</strong></strong><dd>
<p>This section works like <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a>, but for printers.
<p>If a <strong>[printers]</strong> section occurs in the configuration file, users are
able to connect to any printer specified in the local host's printcap
file.
<p>When a connection request is made, the existing sections are
scanned. If a match is found, it is used. If no match is found, but a
<a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> section exists, it is used as described
above. Otherwise, the requested section name is treated as a printer
name and the appropriate printcap file is scanned to see if the
requested section name is a valid printer share name. If a match is
found, a new printer share is created by cloning the <strong>[printers]</strong>
section.
<p>A few modifications are then made to the newly created share:
<p><dl>
<p><li > The share name is set to the located printer name
<p><li > If no printer name was given, the printer name is set to the
located printer name
<p><li > If the share does not permit guest access and no username was
given, the username is set to the located printer name.
<p></dl>
<p>Note that the <strong>[printers]</strong> service MUST be printable - if you specify
otherwise, the server will refuse to load the configuration file.
<p>Typically the path specified would be that of a world-writeable spool
directory with the sticky bit set on it. A typical <strong>[printers]</strong> entry
would look like this:
<p><pre>

 	[printers]
 		path = /usr/spool/public
 		guest ok = yes
 		printable = yes 

</pre>

<p>All aliases given for a printer in the printcap file are legitimate
printer names as far as the server is concerned. If your printing
subsystem doesn't work like that, you will have to set up a
pseudo-printcap. This is a file consisting of one or more lines like
this:
<p><pre>
        alias|alias|alias|alias...    
</pre>

<p>Each alias should be an acceptable printer name for your printing
subsystem. In the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section, specify the new
file as your printcap.  The server will then only recognize names
found in your pseudo-printcap, which of course can contain whatever
aliases you like. The same technique could be used simply to limit
access to a subset of your local printers.
<p>An alias, by the way, is defined as any component of the first entry
of a printcap record. Records are separated by newlines, components
(if there are more than one) are separated by vertical bar symbols
("|").
<p>NOTE: On SYSV systems which use lpstat to determine what printers are
defined on the system you may be able to use <a href="smb.conf.5.html#printcapname"><strong>"printcap name =
lpstat"</strong></a> to automatically obtain a list of
printers. See the <a href="smb.conf.5.html#printcapname"><strong>"printcap name"</strong></a> option for
more details.
<p></dl>
<p><a name="PARAMETERS"></a>
<h2>PARAMETERS</h2>
    
<p>Parameters define the specific attributes of sections.
<p>Some parameters are specific to the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section
(e.g., <a href="smb.conf.5.html#security"><strong>security</strong></a>).  Some parameters are usable in
all sections (e.g., <a href="smb.conf.5.html#createmode"><strong>create mode</strong></a>). All others are
permissible only in normal sections. For the purposes of the following
descriptions the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> and
<a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> sections will be considered normal.
The letter <code>'G'</code> in parentheses indicates that a parameter is
specific to the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section. The letter <code>'S'</code>
indicates that a parameter can be specified in a service specific
section. Note that all <code>'S'</code> parameters can also be specified in the
<a href="smb.conf.5.html#global"><strong>[global]</strong></a> section - in which case they will define
the default behavior for all services.
<p>Parameters are arranged here in alphabetical order - this may not
create best bedfellows, but at least you can find them! Where there
are synonyms, the preferred synonym is described, others refer to the
preferred synonym.
<p><a name="VARIABLESUBSTITUTIONS"></a>
<h2>VARIABLE SUBSTITUTIONS</h2>
    
<p>Many of the strings that are settable in the config file can take
substitutions. For example the option <a href="smb.conf.5.html#path"><strong><code>"path =
/tmp/%u"</code></strong></a> would be interpreted as <code>"path = /tmp/john"</code> if
the user connected with the username john.
<p>These substitutions are mostly noted in the descriptions below, but
there are some general substitutions which apply whenever they might
be relevant. These are:
<p><dl>
<p><a name="percentS"></a> 
<li > <strong>%S</strong> = the name of the current service, if any.
<p><a name="percentP"></a>
<li > <strong>%P</strong> = the root directory of the current service, if any.
<p><a name="percentu"></a>
<li > <strong>%u</strong> = user name of the current service, if any.
<p><a name="percentg"></a>
<li > <strong>%g</strong> = primary group name of <a href="smb.conf.5.html#percentu"><strong>%u</strong></a>.
<p><a name="percentU"></a> 
<li > <strong>%U</strong> = session user name (the user name that
the client wanted, not necessarily the same as the one they got).
<p><a name="percentG"></a>
<li > <strong>%G</strong> = primary group name of <a href="smb.conf.5.html#percentU"><strong>%U</strong></a>.
<p><a name="percentH"></a>
<li > <strong>%H</strong> = the home directory of the user given by <a href="smb.conf.5.html#percentu"><strong>%u</strong></a>.
<p><a name="percentv"></a>
<li > <strong>%v</strong> = the Samba version.
<p><a name="percenth"></a>
<li > <strong>%h</strong> = the internet hostname that Samba is running on.
<p><a name="percentm"></a>
<li > <strong>%m</strong> = the NetBIOS name of the client machine (very useful).
<p><a name="percentL"></a>
<li > <strong>%L</strong> = the NetBIOS name of the server. This allows you to change your
config based on what the client calls you. Your server can have a "dual
personality".
<p><a name="percentM"></a> 
<li > <strong>%M</strong> = the internet name of the client machine.
<p><a name="percentN"></a>
<li > <strong>%N</strong> = the name of your NIS home directory server.  This is
obtained from your NIS auto.map entry.  If you have not compiled Samba
with the <strong>--with-automount</strong> option then this value will be the same
as <a href="smb.conf.5.html#percentL"><strong>%L</strong></a>.
<p><a name="percentp"></a>
<li > <strong>%p</strong> = the path of the service's home directory, obtained from your NIS
auto.map entry. The NIS auto.map entry is split up as "%N:%p".
<p><a name="percentR"></a> 
<li > <strong>%R</strong> = the selected protocol level after protocol
negotiation. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1.
<p><a name="percentd"></a>
<li > <strong>%d</strong> = The process id of the current server process.
<p><a name="percenta"></a> 
<li > <strong>%a</strong> = the architecture of the remote
machine. Only some are recognized, and those may not be 100%
reliable. It currently recognizes Samba, WfWg, WinNT and
Win95. Anything else will be known as "UNKNOWN". If it gets it wrong
then sending a level 3 log to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>
should allow it to be fixed.
<p><a name="percentI"></a>
<li > <strong>%I</strong> = The IP address of the client machine.
<p><a name="percentT"></a>
<li > <strong>%T</strong> = the current date and time.
<p></dl>
<p>There are some quite creative things that can be done with these
substitutions and other smb.conf options.
<p><a name="NAMEMANGLING"></a>
<h2>NAME MANGLING</h2>
    
<p>Samba supports <em>"name mangling"</em> so that DOS and Windows clients can
use files that don't conform to the 8.3 format. It can also be set to
adjust the case of 8.3 format filenames.
<p>There are several options that control the way mangling is performed,
and they are grouped here rather than listed separately. For the
defaults look at the output of the testparm program.
<p>All of these options can be set separately for each service (or
globally, of course).
<p>The options are:
<p><a name="manglecaseoption"></a>
<strong>"mangle case = yes/no"</strong> controls if names that have characters that
aren't of the "default" case are mangled. For example, if this is yes
then a name like <code>"Mail"</code> would be mangled. Default <em>no</em>.
<p><a name="casesensitiveoption"></a>
<strong>"case sensitive = yes/no"</strong> controls whether filenames are case
sensitive. If they aren't then Samba must do a filename search and
match on passed names. Default <em>no</em>.
<p><a name="defaultcaseoption"></a>
<strong>"default case = upper/lower"</strong> controls what the default case is for new
filenames. Default <em>lower</em>.
<p><a name="preservecaseoption"></a>
<strong>"preserve case = yes/no"</strong> controls if new files are created with the
case that the client passes, or if they are forced to be the <code>"default"</code>
case. Default <em>Yes</em>.
<p><a name="shortpreservecaseoption"></a>
<p><strong>"short preserve case = yes/no"</strong> 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 <code>"default"</code>
case. This option can be use with <a href="smb.conf.5.html#preservecaseoption"><strong>"preserve case =
yes"</strong></a> to permit long filenames to retain their
case, while short names are lowered. Default <em>Yes</em>.
<p>By default, Samba 2.0 has the same semantics as a Windows NT
server, in that it is case insensitive but case preserving.
<p><a name="NOTEABOUTUSERNAMEPASSWORDVALIDATION"></a>
<h2>NOTE ABOUT USERNAME/PASSWORD VALIDATION</h2>
    
<p>There are a number of ways in which a user can connect to a
service. The server follows the following steps in determining if it
will allow a connection to a specified service. If all the steps fail
then the connection request is rejected. If one of the steps pass then
the following steps are not checked.
<p>If the service is marked <a href="smb.conf.5.html#guestonly"><strong>"guest only = yes"</strong></a> then
steps 1 to 5 are skipped.
<p><ol>
<p><li> Step 1: If the client has passed a username/password pair and
that username/password pair is validated by the UNIX system's password
programs then the connection is made as that username. Note that this
includes the <code>\\server\service%username</code> method of passing a
username.
<p><li> Step 2: If the client has previously registered a username with
the system and now supplies a correct password for that username then
the connection is allowed.
<p><li> Step 3: The client's netbios name and any previously used user
names are checked against the supplied password, if they match then
the connection is allowed as the corresponding user.
<p><li> Step 4: If the client has previously validated a
username/password pair with the server and the client has passed the
validation token then that username is used. 
<p><li> Step 5: If a <a href="smb.conf.5.html#user"><strong>"user = "</strong></a> field is given in the
smb.conf file for the service and the client has supplied a password,
and that password matches (according to the UNIX system's password
checking) with one of the usernames from the <a href="smb.conf.5.html#user"><strong>user=</strong></a>
field then the connection is made as the username in the
<a href="smb.conf.5.html#user"><strong>"user="</strong></a> line. If one of the username in the
<a href="smb.conf.5.html#user"><strong>user=</strong></a> list begins with a <code>'@'</code> then that name
expands to a list of names in the group of the same name.
<p><li> Step 6: If the service is a guest service then a connection is
made as the username given in the <a href="smb.conf.5.html#guestaccount"><strong>"guest account
="</strong></a> for the service, irrespective of the supplied
password.
<p></ol>
<p><a name="COMPLETELISTOFGLOBALPARAMETERS"></a>
<h2>COMPLETE LIST OF GLOBAL PARAMETERS</h2>
    
<p>Here is a list of all global parameters. See the section of each
parameter for details.  Note that some are synonyms.
<p><dl>
<p><li > <a href="smb.conf.5.html#adduserscript"><strong>add user script</strong></a>
<p><li > <a href="smb.conf.5.html#allowtrusteddomains"><strong>allow trusted domains</strong></a>
<p><li > <a href="smb.conf.5.html#announceas"><strong>announce as</strong></a>
<p><li > <a href="smb.conf.5.html#announceversion"><strong>announce version</strong></a>
<p><li > <a href="smb.conf.5.html#autoservices"><strong>auto services</strong></a>
<p><li > <a href="smb.conf.5.html#bindinterfacesonly"><strong>bind interfaces only</strong></a>
<p><li > <a href="smb.conf.5.html#browselist"><strong>browse list</strong></a>
<p><li > <a href="smb.conf.5.html#changenotifytimeout"><strong>change notify timeout</strong></a>
<p><li > <a href="smb.conf.5.html#characterset"><strong>character set</strong></a>
<p><li > <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a>
<p><li > <a href="smb.conf.5.html#codingsystem"><strong>coding system</strong></a>
<p><li > <a href="smb.conf.5.html#configfile"><strong>config file</strong></a>
<p><li > <a href="smb.conf.5.html#deadtime"><strong>deadtime</strong></a>
<p><li > <a href="smb.conf.5.html#debughirestimestamp"><strong>debug hires timestamp</strong></a>
<p><li > <a href="smb.conf.5.html#debugpid"><strong>debug pid</strong></a>
<p><li > <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
<p><li > <a href="smb.conf.5.html#debuguid"><strong>debug uid</strong></a>
<p><li > <a href="smb.conf.5.html#debuglevel"><strong>debug level</strong></a>
<p><li > <a href="smb.conf.5.html#default"><strong>default</strong></a>
<p><li > <a href="smb.conf.5.html#defaultservice"><strong>default service</strong></a>
<p><li > <a href="smb.conf.5.html#deleteuserscript"><strong>delete user script</strong></a>
<p><li > <a href="smb.conf.5.html#dfreecommand"><strong>dfree command</strong></a>
<p><li > <a href="smb.conf.5.html#dnsproxy"><strong>dns proxy</strong></a>
<p><li > <a href="smb.conf.5.html#domainadmingroup"><strong>domain admin group</strong></a>
<p><li > <a href="smb.conf.5.html#domainadminusers"><strong>domain admin users</strong></a>
<p><li > <a href="smb.conf.5.html#domaingroups"><strong>domain groups</strong></a>
<p><li > <a href="smb.conf.5.html#domainguestgroup"><strong>domain guest group</strong></a>
<p><li > <a href="smb.conf.5.html#domainguestusers"><strong>domain guest users</strong></a>
<p><li > <a href="smb.conf.5.html#domainlogons"><strong>domain logons</strong></a>
<p><li > <a href="smb.conf.5.html#domainmaster"><strong>domain master</strong></a>
<p><li > <a href="smb.conf.5.html#encryptpasswords"><strong>encrypt passwords</strong></a>
<p><li > <a href="smb.conf.5.html#getwdcache"><strong>getwd cache</strong></a>
<p><li > <a href="smb.conf.5.html#homedirmap"><strong>homedir map</strong></a>
<p><li > <a href="smb.conf.5.html#hostsequiv"><strong>hosts equiv</strong></a>
<p><li > <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a>
<p><li > <a href="smb.conf.5.html#keepalive"><strong>keepalive</strong></a>
<p><li > <a href="smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a>
<p><li > <a href="smb.conf.5.html#ldapfilter"><strong>ldap filter</strong></a>
<p><li > <a href="smb.conf.5.html#ldapport"><strong>ldap port</strong></a>
<p><li > <a href="smb.conf.5.html#ldaproot"><strong>ldap root</strong></a>
<p><li > <a href="smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a>
<p><li > <a href="smb.conf.5.html#ldapserver"><strong>ldap server</strong></a>
<p><li > <a href="smb.conf.5.html#ldapsuffix"><strong>ldap suffix</strong></a>
<p><li > <a href="smb.conf.5.html#lmannounce"><strong>lm announce</strong></a>
<p><li > <a href="smb.conf.5.html#lminterval"><strong>lm interval</strong></a>
<p><li > <a href="smb.conf.5.html#loadprinters"><strong>load printers</strong></a>
<p><li > <a href="smb.conf.5.html#localmaster"><strong>local master</strong></a>
<p><li > <a href="smb.conf.5.html#lockdir"><strong>lock dir</strong></a>
<p><li > <a href="smb.conf.5.html#lockdirectory"><strong>lock directory</strong></a>
<p><li > <a href="smb.conf.5.html#logfile"><strong>log file</strong></a>
<p><li > <a href="smb.conf.5.html#loglevel"><strong>log level</strong></a>
<p><li > <a href="smb.conf.5.html#logondrive"><strong>logon drive</strong></a>
<p><li > <a href="smb.conf.5.html#logonhome"><strong>logon home</strong></a>
<p><li > <a href="smb.conf.5.html#logonpath"><strong>logon path</strong></a>
<p><li > <a href="smb.conf.5.html#logonscript"><strong>logon script</strong></a>
<p><li > <a href="smb.conf.5.html#lpqcachetime"><strong>lpq cache time</strong></a>
<p><li > <a href="smb.conf.5.html#machinepasswordtimeout"><strong>machine password timeout</strong></a>
<p><li > <a href="smb.conf.5.html#mangledstack"><strong>mangled stack</strong></a>
<p><li > <a href="smb.conf.5.html#maptoguest"><strong>map to guest</strong></a>
<p><li > <a href="smb.conf.5.html#maxdisksize"><strong>max disk size</strong></a>
<p><li > <a href="smb.conf.5.html#maxlogsize"><strong>max log size</strong></a>
<p><li > <a href="smb.conf.5.html#maxmux"><strong>max mux</strong></a>
<p><li > <a href="smb.conf.5.html#maxopenfiles"><strong>max open files</strong></a>
<p><li > <a href="smb.conf.5.html#maxpacket"><strong>max packet</strong></a>
<p><li > <a href="smb.conf.5.html#maxttl"><strong>max ttl</strong></a>
<p><li > <a href="smb.conf.5.html#maxwinsttl"><strong>max wins ttl</strong></a>
<p><li > <a href="smb.conf.5.html#maxxmit"><strong>max xmit</strong></a>
<p><li > <a href="smb.conf.5.html#messagecommand"><strong>message command</strong></a>
<p><li > <a href="smb.conf.5.html#minpasswdlength"><strong>min passwd length</strong></a>
<p><li > <a href="smb.conf.5.html#minpasswordlength"><strong>min password length</strong></a>
<p><li > <a href="smb.conf.5.html#minwinsttl"><strong>min wins ttl</strong></a>
<p><li > <a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a>
<p><li > <a href="smb.conf.5.html#netbiosaliases"><strong>netbios aliases</strong></a>
<p><li > <a href="smb.conf.5.html#netbiosname"><strong>netbios name</strong></a>
<p><li > <a href="smb.conf.5.html#netbiosscope"><strong>netbios scope</strong></a>
<p><li > <a href="smb.conf.5.html#nishomedir"><strong>nis homedir</strong></a>
<p><li > <a href="smb.conf.5.html#ntaclsupport"><strong>nt acl support</strong></a>
<p><li > <a href="smb.conf.5.html#ntpipesupport"><strong>nt pipe support</strong></a>
<p><li > <a href="smb.conf.5.html#ntsmbsupport"><strong>nt smb support</strong></a>
<p><li > <a href="smb.conf.5.html#nullpasswords"><strong>null passwords</strong></a>
<p><li > <a href="smb.conf.5.html#olelockingcompatibility"><strong>ole locking compatibility</strong></a>
<p><li > <a href="smb.conf.5.html#oplockbreakwaittime"><strong>oplock break wait time</strong></a>
<p><li > <a href="smb.conf.5.html#oslevel"><strong>os level</strong></a>
<p><li > <a href="smb.conf.5.html#packetsize"><strong>packet size</strong></a>
<p><li > <a href="smb.conf.5.html#panicaction"><strong>panic action</strong></a>
<p><li > <a href="smb.conf.5.html#passwdchat"><strong>passwd chat</strong></a>
<p><li > <a href="smb.conf.5.html#passwdchatdebug"><strong>passwd chat debug</strong></a>
<p><li > <a href="smb.conf.5.html#passwdprogram"><strong>passwd program</strong></a>
<p><li > <a href="smb.conf.5.html#passwordlevel"><strong>password level</strong></a>
<p><li > <a href="smb.conf.5.html#passwordserver"><strong>password server</strong></a>
<p><li > <a href="smb.conf.5.html#preferedmaster"><strong>prefered master</strong></a>
<p><li > <a href="smb.conf.5.html#preferredmaster"><strong>preferred master</strong></a>
<p><li > <a href="smb.conf.5.html#preload"><strong>preload</strong></a>
<p><li > <a href="smb.conf.5.html#printcap"><strong>printcap</strong></a>
<p><li > <a href="smb.conf.5.html#printcapname"><strong>printcap name</strong></a>
<p><li > <a href="smb.conf.5.html#printerdriverfile"><strong>printer driver file</strong></a>
<p><li > <a href="smb.conf.5.html#protocol"><strong>protocol</strong></a>
<p><li > <a href="smb.conf.5.html#readbmpx"><strong>read bmpx</strong></a>
<p><li > <a href="smb.conf.5.html#readprediction"><strong>read prediction</strong></a>
<p><li > <a href="smb.conf.5.html#readraw"><strong>read raw</strong></a>
<p><li > <a href="smb.conf.5.html#readsize"><strong>read size</strong></a>
<p><li > <a href="smb.conf.5.html#remoteannounce"><strong>remote announce</strong></a>
<p><li > <a href="smb.conf.5.html#remotebrowsesync"><strong>remote browse sync</strong></a>
<p><li > <a href="smb.conf.5.html#restrictanonymous"><strong>restrict anonymous</strong></a>
<p><li > <a href="smb.conf.5.html#root"><strong>root</strong></a>
<p><li > <a href="smb.conf.5.html#rootdir"><strong>root dir</strong></a>
<p><li > <a href="smb.conf.5.html#rootdirectory"><strong>root directory</strong></a>
<p><li > <a href="smb.conf.5.html#security"><strong>security</strong></a>
<p><li > <a href="smb.conf.5.html#serverstring"><strong>server string</strong></a>
<p><li > <a href="smb.conf.5.html#sharedmemsize"><strong>shared mem size</strong></a>
<p><li > <a href="smb.conf.5.html#smbpasswdfile"><strong>smb passwd file</strong></a>
<p><li > <a href="smb.conf.5.html#smbrun"><strong>smbrun</strong></a>
<p><li > <a href="smb.conf.5.html#socketaddress"><strong>socket address</strong></a>
<p><li > <a href="smb.conf.5.html#socketoptions"><strong>socket options</strong></a>
<p><li > <a href="smb.conf.5.html#sourceenvironment"><strong>source environment</strong></a>
<p><li > <a href="smb.conf.5.html#ssl"><strong>ssl</strong></a>
<p><li > <a href="smb.conf.5.html#sslCAcertDir"><strong>ssl CA certDir</strong></a>
<p><li > <a href="smb.conf.5.html#sslCAcertFile"><strong>ssl CA certFile</strong></a>
<p><li > <a href="smb.conf.5.html#sslciphers"><strong>ssl ciphers</strong></a>
<p><li > <a href="smb.conf.5.html#sslclientcert"><strong>ssl client cert</strong></a>
<p><li > <a href="smb.conf.5.html#sslclientkey"><strong>ssl client key</strong></a>
<p><li > <a href="smb.conf.5.html#sslcompatibility"><strong>ssl compatibility</strong></a>
<p><li > <a href="smb.conf.5.html#sslhosts"><strong>ssl hosts</strong></a>
<p><li > <a href="smb.conf.5.html#sslhostsresign"><strong>ssl hosts resign</strong></a>
<p><li > <a href="smb.conf.5.html#sslrequireclientcert"><strong>ssl require clientcert</strong></a>
<p><li > <a href="smb.conf.5.html#sslrequireservercert"><strong>ssl require servercert</strong></a>
<p><li > <a href="smb.conf.5.html#sslservercert"><strong>ssl server cert</strong></a>
<p><li > <a href="smb.conf.5.html#sslserverkey"><strong>ssl server key</strong></a>
<p><li > <a href="smb.conf.5.html#sslversion"><strong>ssl version</strong></a>
<p><li > <a href="smb.conf.5.html#statcache"><strong>stat cache</strong></a>
<p><li > <a href="smb.conf.5.html#statcachesize"><strong>stat cache size</strong></a>
<p><li > <a href="smb.conf.5.html#stripdot"><strong>strip dot</strong></a>
<p><li > <a href="smb.conf.5.html#syslog"><strong>syslog</strong></a>
<p><li > <a href="smb.conf.5.html#syslogonly"><strong>syslog only</strong></a>
<p><li > <a href="smb.conf.5.html#templatehomedir"><strong>template homedir</strong></a>
<p><li > <a href="smb.conf.5.html#templateshell"><strong>template shell</strong></a>
<p><li > <a href="smb.conf.5.html#timeoffset"><strong>time offset</strong></a>
<p><li > <a href="smb.conf.5.html#timeserver"><strong>time server</strong></a>
<p><li > <a href="smb.conf.5.html#timestamplogs"><strong>timestamp logs</strong></a>
<p><li > <a href="smb.conf.5.html#unixpasswordsync"><strong>unix password sync</strong></a>
<p><li > <a href="smb.conf.5.html#unixrealname"><strong>unix realname</strong></a>
<p><li > <a href="smb.conf.5.html#updateencrypted"><strong>update encrypted</strong></a>
<p><li > <a href="smb.conf.5.html#userhosts"><strong>use rhosts</strong></a>
<p><li > <a href="smb.conf.5.html#usernamelevel"><strong>username level</strong></a>
<p><li > <a href="smb.conf.5.html#usernamemap"><strong>username map</strong></a>
<p><li > <a href="smb.conf.5.html#utmpdirectory"><strong>utmp directory</strong></a>
<p><li > <a href="smb.conf.5.html#validchars"><strong>valid chars</strong></a>
<p><li > <a href="smb.conf.5.html#winbindcachetime"><strong>winbind cache time</strong></a>
<p><li > <a href="smb.conf.5.html#winbindgid"><strong>winbind gid</strong></a>
<p><li > <a href="smb.conf.5.html#winbinduid"><strong>winbind uid</strong></a>
<p><li > <a href="smb.conf.5.html#winshook"><strong>wins hook</strong></a>
<p><li > <a href="smb.conf.5.html#winsproxy"><strong>wins proxy</strong></a>
<p><li > <a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a>
<p><li > <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a>
<p><li > <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a>
<p><li > <a href="smb.conf.5.html#writeraw"><strong>write raw</strong></a>
<p></dl>
<p><a name="COMPLETELISTOFSERVICEPARAMETERS"></a>
<h2>COMPLETE LIST OF SERVICE PARAMETERS</h2>
    
<p>Here is a list of all service parameters. See the section of each
parameter for details. Note that some are synonyms.
<p><dl>
<p><li > <a href="smb.conf.5.html#adminusers"><strong>admin users</strong></a>
<p><li > <a href="smb.conf.5.html#allowhosts"><strong>allow hosts</strong></a>
<p><li > <a href="smb.conf.5.html#alternatepermissions"><strong>alternate permissions</strong></a>
<p><li > <a href="smb.conf.5.html#available"><strong>available</strong></a>
<p><li > <a href="smb.conf.5.html#blockinglocks"><strong>blocking locks</strong></a>
<p><li > <a href="smb.conf.5.html#browsable"><strong>browsable</strong></a>
<p><li > <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a>
<p><li > <a href="smb.conf.5.html#casesensitive"><strong>case sensitive</strong></a>
<p><li > <a href="smb.conf.5.html#casesignames"><strong>casesignames</strong></a>
<p><li > <a href="smb.conf.5.html#comment"><strong>comment</strong></a>
<p><li > <a href="smb.conf.5.html#copy"><strong>copy</strong></a>
<p><li > <a href="smb.conf.5.html#createmask"><strong>create mask</strong></a>
<p><li > <a href="smb.conf.5.html#createmode"><strong>create mode</strong></a>
<p><li > <a href="smb.conf.5.html#defaultcase"><strong>default case</strong></a>
<p><li > <a href="smb.conf.5.html#deletereadonly"><strong>delete readonly</strong></a>
<p><li > <a href="smb.conf.5.html#deletevetofiles"><strong>delete veto files</strong></a>
<p><li > <a href="smb.conf.5.html#denyhosts"><strong>deny hosts</strong></a>
<p><li > <a href="smb.conf.5.html#directory"><strong>directory</strong></a>
<p><li > <a href="smb.conf.5.html#directorymask"><strong>directory mask</strong></a>
<p><li > <a href="smb.conf.5.html#directorymode"><strong>directory mode</strong></a>
<p><li > <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security mask</strong></a>
<p><li > <a href="smb.conf.5.html#dontdescend"><strong>dont descend</strong></a>
<p><li > <a href="smb.conf.5.html#dosfiletimeresolution"><strong>dos filetime resolution</strong></a>
<p><li > <a href="smb.conf.5.html#dosfiletimes"><strong>dos filetimes</strong></a>
<p><li > <a href="smb.conf.5.html#exec"><strong>exec</strong></a>
<p><li > <a href="smb.conf.5.html#fakedirectorycreatetimes"><strong>fake directory create times</strong></a>
<p><li > <a href="smb.conf.5.html#fakeoplocks"><strong>fake oplocks</strong></a>
<p><li > <a href="smb.conf.5.html#followsymlinks"><strong>follow symlinks</strong></a>
<p><li > <a href="smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a>
<p><li > <a href="smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a>
<p><li > <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security mode</strong></a>
<p><li > <a href="smb.conf.5.html#forcegroup"><strong>force group</strong></a>
<p><li > <a href="smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a>
<p><li > <a href="smb.conf.5.html#forceuser"><strong>force user</strong></a>
<p><li > <a href="smb.conf.5.html#fstype"><strong>fstype</strong></a>
<p><li > <a href="smb.conf.5.html#group"><strong>group</strong></a>
<p><li > <a href="smb.conf.5.html#guestaccount"><strong>guest account</strong></a>
<p><li > <a href="smb.conf.5.html#guestok"><strong>guest ok</strong></a>
<p><li > <a href="smb.conf.5.html#guestonly"><strong>guest only</strong></a>
<p><li > <a href="smb.conf.5.html#hidedotfiles"><strong>hide dot files</strong></a>
<p><li > <a href="smb.conf.5.html#hidefiles"><strong>hide files</strong></a>
<p><li > <a href="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a>
<p><li > <a href="smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a>
<p><li > <a href="smb.conf.5.html#include"><strong>include</strong></a>
<p><li > <a href="smb.conf.5.html#inheritpermissions"><strong>inherit permissions</strong></a>
<p><li > <a href="smb.conf.5.html#invalidusers"><strong>invalid users</strong></a>
<p><li > <a href="smb.conf.5.html#level2oplocks"><strong>level2 oplocks</strong></a>
<p><li > <a href="smb.conf.5.html#locking"><strong>locking</strong></a>
<p><li > <a href="smb.conf.5.html#lppausecommand"><strong>lppause command</strong></a>
<p><li > <a href="smb.conf.5.html#lpqcommand"><strong>lpq command</strong></a>
<p><li > <a href="smb.conf.5.html#lpresumecommand"><strong>lpresume command</strong></a>
<p><li > <a href="smb.conf.5.html#lprmcommand"><strong>lprm command</strong></a>
<p><li > <a href="smb.conf.5.html#magicoutput"><strong>magic output</strong></a>
<p><li > <a href="smb.conf.5.html#magicscript"><strong>magic script</strong></a>
<p><li > <a href="smb.conf.5.html#manglecase"><strong>mangle case</strong></a>
<p><li > <a href="smb.conf.5.html#manglelocks"><strong>mangle locks</strong></a>
<p><li > <a href="smb.conf.5.html#mangledmap"><strong>mangled map</strong></a>
<p><li > <a href="smb.conf.5.html#manglednames"><strong>mangled names</strong></a>
<p><li > <a href="smb.conf.5.html#manglingchar"><strong>mangling char</strong></a>
<p><li > <a href="smb.conf.5.html#maparchive"><strong>map archive</strong></a>
<p><li > <a href="smb.conf.5.html#maphidden"><strong>map hidden</strong></a>
<p><li > <a href="smb.conf.5.html#mapsystem"><strong>map system</strong></a>
<p><li > <a href="smb.conf.5.html#maxconnections"><strong>max connections</strong></a>
<p><li > <a href="smb.conf.5.html#minprintspace"><strong>min print space</strong></a>
<p><li > <a href="smb.conf.5.html#onlyguest"><strong>only guest</strong></a>
<p><li > <a href="smb.conf.5.html#onlyuser"><strong>only user</strong></a>
<p><li > <a href="smb.conf.5.html#oplockcontentionlimit"><strong>oplock contention limit</strong></a>
<p><li > <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a>
<p><li > <a href="smb.conf.5.html#path"><strong>path</strong></a>
<p><li > <a href="smb.conf.5.html#postexec"><strong>postexec</strong></a>
<p><li > <a href="smb.conf.5.html#postscript"><strong>postscript</strong></a>
<p><li > <a href="smb.conf.5.html#preexec"><strong>preexec</strong></a>
<p><li > <a href="smb.conf.5.html#preexecclose"><strong>preexec close</strong></a>
<p><li > <a href="smb.conf.5.html#preservecase"><strong>preserve case</strong></a>
<p><li > <a href="smb.conf.5.html#printcommand"><strong>print command</strong></a>
<p><li > <a href="smb.conf.5.html#printok"><strong>print ok</strong></a>
<p><li > <a href="smb.conf.5.html#printable"><strong>printable</strong></a>
<p><li > <a href="smb.conf.5.html#printer"><strong>printer</strong></a>
<p><li > <a href="smb.conf.5.html#printeradmin"><strong>printer admin</strong></a>
<p><li > <a href="smb.conf.5.html#printerdriver"><strong>printer driver</strong></a>
<p><li > <a href="smb.conf.5.html#printerdriverlocation"><strong>printer driver location</strong></a>
<p><li > <a href="smb.conf.5.html#printername"><strong>printer name</strong></a>
<p><li > <a href="smb.conf.5.html#printing"><strong>printing</strong></a>
<p><li > <a href="smb.conf.5.html#public"><strong>public</strong></a>
<p><li > <a href="smb.conf.5.html#queuepausecommand"><strong>queuepause command</strong></a>
<p><li > <a href="smb.conf.5.html#queueresumecommand"><strong>queueresume command</strong></a>
<p><li > <a href="smb.conf.5.html#readlist"><strong>read list</strong></a>
<p><li > <a href="smb.conf.5.html#readonly"><strong>read only</strong></a>
<p><li > <a href="smb.conf.5.html#rootpostexec"><strong>root postexec</strong></a>
<p><li > <a href="smb.conf.5.html#rootpreexec"><strong>root preexec</strong></a>
<p><li > <a href="smb.conf.5.html#rootpreexecclose"><strong>root preexec close</strong></a>
<p><li > <a href="smb.conf.5.html#securitymask"><strong>security mask</strong></a>
<p><li > <a href="smb.conf.5.html#setdirectory"><strong>set directory</strong></a>
<p><li > <a href="smb.conf.5.html#sharemodes"><strong>share modes</strong></a>
<p><li > <a href="smb.conf.5.html#shortpreservecase"><strong>short preserve case</strong></a>
<p><li > <a href="smb.conf.5.html#status"><strong>status</strong></a>
<p><li > <a href="smb.conf.5.html#strictlocking"><strong>strict locking</strong></a>
<p><li > <a href="smb.conf.5.html#strictsync"><strong>strict sync</strong></a>
<p><li > <a href="smb.conf.5.html#syncalways"><strong>sync always</strong></a>
<p><li > <a href="smb.conf.5.html#user"><strong>user</strong></a>
<p><li > <a href="smb.conf.5.html#username"><strong>username</strong></a>
<p><li > <a href="smb.conf.5.html#users"><strong>users</strong></a>
<p><li > <a href="smb.conf.5.html#utmp"><strong>utmp</strong></a>
<p><li > <a href="smb.conf.5.html#validusers"><strong>valid users</strong></a>
<p><li > <a href="smb.conf.5.html#vetofiles"><strong>veto files</strong></a>
<p><li > <a href="smb.conf.5.html#vetooplockfiles"><strong>veto oplock files</strong></a>
<p><li > <a href="smb.conf.5.html#volume"><strong>volume</strong></a>
<p><li > <a href="smb.conf.5.html#widelinks"><strong>wide links</strong></a>
<p><li > <a href="smb.conf.5.html#writable"><strong>writable</strong></a>
<p><li > <a href="smb.conf.5.html#writecachesize"><strong>write cache size</strong></a>
<p><li > <a href="smb.conf.5.html#writelist"><strong>write list</strong></a>
<p><li > <a href="smb.conf.5.html#writeok"><strong>write ok</strong></a>
<p><li > <a href="smb.conf.5.html#writeable"><strong>writeable</strong></a>
<p></dl>
<p><a name="EXPLANATIONOFEACHPARAMETER"></a>
<h2>EXPLANATION OF EACH PARAMETER</h2>
    
<p><dl>
<p><a name="adduserscript"></a>
<p></p><dt><strong><strong>add user script (G)</strong></strong><dd>
<p>This is the full pathname to a script that will be run <em>AS ROOT</em> by
<a href="smbd.8.html"><strong>smbd (8)</strong></a> under special circumstances decribed
below.
<p>Normally, a Samba server requires that UNIX users are created for all
users accessing files on this server. For sites that use Windows NT
account databases as their primary user database creating these users
and keeping the user list in sync with the Windows NT PDC is an
onerous task. This option allows <a href="smbd.8.html"><strong>smbd</strong></a> to create
the required UNIX users <em>ON DEMAND</em> when a user accesses the Samba
server.
<p>In order to use this option, <a href="smbd.8.html"><strong>smbd</strong></a> must be set to
<a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> or
<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a> and <strong>"add user script"</strong>
must be set to a full pathname for a script that will create a UNIX user
given one argument of <strong>%u</strong>, which expands into the UNIX user name to
create.
<p>When the Windows user attempts to access the Samba server, at
<em>"login"</em>(session setup in the SMB protocol) time,
<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="smb.conf.5.html#passwordserver"><strong>password
server</strong></a> and attempts to authenticate the given user
with the given password. If the authentication succeeds then
<a href="smbd.8.html"><strong>smbd</strong></a> attempts to find a UNIX user in the UNIX
password database to map the Windows user into. If this lookup fails,
and <strong>"add user script"</strong> is set then <a href="smbd.8.html"><strong>smbd</strong></a> will
call the specified script <em>AS ROOT</em>, expanding any <strong>%u</strong> argument
to be the user name to create.
<p>If this script successfully creates the user then
<a href="smbd.8.html"><strong>smbd</strong></a> will continue on as though the UNIX user
already existed. In this way, UNIX users are dynamically created to
match existing Windows NT accounts.
<p>See also <a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a>,
<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>, <a href="smb.conf.5.html#passwordserver"><strong>password
server</strong></a>, <a href="smb.conf.5.html#deleteuserscript"><strong>delete user
script</strong></a>.
<p><strong>Default:</strong>
<code>	add user script = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	add user script = /usr/local/samba/bin/add_user %u</code>
<p><a name="adminusers"></a>
<p></p><dt><strong><strong>admin users (S)</strong></strong><dd>
<p>This is a list of users who will be granted administrative privileges
on the share. This means that they will do all file operations as the
super-user (root).
<p>You should use this option very carefully, as any user in this list
will be able to do anything they like on the share, irrespective of
file permissions.
<p><strong>Default:</strong> <br>
<code>	no admin users</code>
<p><strong>Example:</strong> <br>
<code>	admin users = jason</code>
<p><a name="allowhosts"></a>
<p></p><dt><strong><strong>allow hosts (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a>.
<p><a name="allowtrusteddomains"></a>
<p></p><dt><strong><strong>allow trusted domains (G)</strong></strong><dd>
<p>This option only takes effect when the <a href="smb.conf.5.html#security"><strong>security</strong></a>
option is set to <strong>server</strong> or <strong>domain</strong>.  If it is set to no,
then attempts to connect to a resource from a domain or workgroup other than
the one which smbd is running in will fail, even if that domain
is trusted by the remote server doing the authentication.
<p>This is useful if you only want your Samba server to serve resources
to users in the domain it is a member of. As an example, suppose that there are
two domains DOMA and DOMB.  DOMB is trusted by DOMA, which contains
the Samba server.  Under normal circumstances, a user with an account
in DOMB can then access the resources of a UNIX account with the same
account name on the Samba server even if they do not have an account
in DOMA.  This can make implementing a security boundary difficult.
<p><strong>Default:</strong>
<code>     allow trusted domains = Yes</code>
<p><strong>Example:</strong>
<code>     allow trusted domains = No</code>
<p><a name="alternatepermissions"></a>
<p></p><dt><strong><strong>alternate permissions (S)</strong></strong><dd>
<p>This is a deprecated parameter. It no longer has any effect in Samba2.0.
In previous versions of Samba it affected the way the DOS "read only"
attribute was mapped for a file. In Samba2.0 a file is marked "read only"
if the UNIX file does not have the 'w' bit set for the owner of the file,
regardless if the owner of the file is the currently logged on user or not.
<p><a name="announceas"></a>
<p></p><dt><strong><strong>announce as (G)</strong></strong><dd>
<p>This specifies what type of server <a href="nmbd.8.html"><strong>nmbd</strong></a> will
announce itself as, to a network neighborhood browse list. By default
this is set to Windows NT. The valid options are : "NT", which is a
synonym for "NT Server", "NT Server", "NT Workstation", "Win95" or
"WfW" meaning Windows NT Server, Windows NT Workstation, Windows 95
and Windows for Workgroups respectively. Do not change this parameter
unless you have a specific need to stop Samba appearing as an NT server
as this may prevent Samba servers from participating as browser servers correctly.
<p><strong>Default:</strong>
<code>	announce as = NT Server</code>
<p><strong>Example</strong>
<code>	announce as = Win95</code>
<p><a name="announceversion"></a>
<p></p><dt><strong><strong>announce version (G)</strong></strong><dd>
<p>This specifies the major and minor version numbers that nmbd will use
when announcing itself as a server. The default is 4.2.  Do not change
this parameter unless you have a specific need to set a Samba server
to be a downlevel server.
<p><strong>Default:</strong>
<code>	announce version = 4.2</code>
<p><strong>Example:</strong>
<code>	announce version = 2.0</code>
<p><a name="autoservices"></a>
<p></p><dt><strong><strong>auto services (G)</strong></strong><dd>
<p>This is a list of services that you want to be automatically added to
the browse lists. This is most useful for homes and printers services
that would otherwise not be visible.
<p>Note that if you just want all printers in your printcap file loaded
then the <a href="smb.conf.5.html#loadprinters"><strong>"load printers"</strong></a> option is easier.
<p><strong>Default:</strong>
<code>	no auto services</code>
<p><strong>Example:</strong>
<code>	auto services = fred lp colorlp</code>
<p><a name="available"></a>
<p></p><dt><strong><strong>available (S)</strong></strong><dd>
<p>This parameter lets you <em>'turn off'</em> a service. If <code>'available = no'</code>,
then <em>ALL</em> attempts to connect to the service will fail. Such failures
are logged.
<p><strong>Default:</strong>
<code>	available = yes</code>
<p><strong>Example:</strong>
<code>	available = no</code>
<p><a name="bindinterfacesonly"></a>
<p></p><dt><strong><strong>bind interfaces only (G)</strong></strong><dd>
<p>This global parameter allows the Samba admin to limit what interfaces
on a machine will serve smb requests. If affects file service
<a href="smbd.8.html"><strong>smbd</strong></a> and name service <a href="nmbd.8.html"><strong>nmbd</strong></a>
in slightly different ways.
<p>For name service it causes <a href="nmbd.8.html"><strong>nmbd</strong></a> to bind to ports
137 and 138 on the interfaces listed in the
<a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a>
parameter. <a href="nmbd.8.html"><strong>nmbd</strong></a> also binds to the 'all
addresses' interface (0.0.0.0) on ports 137 and 138 for the purposes
of reading broadcast messages. If this option is not set then
<a href="nmbd.8.html"><strong>nmbd</strong></a> will service name requests on all of these
sockets. If <strong>"bind interfaces only"</strong> is set then
<a href="nmbd.8.html"><strong>nmbd</strong></a> will check the source address of any
packets coming in on the broadcast sockets and discard any that don't
match the broadcast addresses of the interfaces in the
<a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list. As unicast packets
are received on the other sockets it allows <a href="nmbd.8.html"><strong>nmbd</strong></a>
to refuse to serve names to machines that send packets that arrive
through any interfaces not listed in the
<a href="smb.conf.5.html#interfaces"><strong>"interfaces"</strong></a> list.  IP Source address spoofing
does defeat this simple check, however so it must not be used
seriously as a security feature for <a href="nmbd.8.html"><strong>nmbd</strong></a>.
<p>For file service it causes <a href="smbd.8.html"><strong>smbd</strong></a> to bind only to
the interface list given in the <a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a>
parameter. This restricts the networks that <a href="smbd.8.html"><strong>smbd</strong></a>
will serve to packets coming in those interfaces.  Note that you
should not use this parameter for machines that are serving PPP or
other intermittent or non-broadcast network interfaces as it will not
cope with non-permanent interfaces.
<p>If <strong>"bind interfaces only"</strong> is set then unless the network address
<em>127.0.0.1</em> is added to the <a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter
list <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> and
<a href="swat.8.html"><strong>swat</strong></a> may not work as expected due to the
reasons covered below.
<p>To change a users SMB password, the <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a>
by default connects to the <em>"localhost" - 127.0.0.1</em> address as an SMB
client to issue the password change request. If <strong>"bind interfaces only"</strong>
is set then unless the network address <em>127.0.0.1</em> is added to the
<a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list then
<a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> will fail to connect in it's
default mode. <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> can be forced to
use the primary IP interface of the local host by using its
<a href="smbpasswd.8.html#minusr"><strong>"-r remote machine"</strong></a> parameter, with
<strong>"remote machine"</strong> set to the IP name of the primary interface
of the local host.
<p>The <a href="swat.8.html"><strong>swat</strong></a> status page tries to connect with
<a href="smbd.8.html"><strong>smbd</strong></a> and <a href="nmbd.8.html"><strong>nmbd</strong></a> at the address 
<em>127.0.0.1</em> to determine if they are running.  Not adding <em>127.0.0.1</em>  will cause
<a href="smbd.8.html"><strong>smbd</strong></a> and <a href="nmbd.8.html"><strong>nmbd</strong></a> to always show
"not running" even if they really are.  This can prevent
<a href="swat.8.html"><strong>swat</strong></a> from starting/stopping/restarting
<a href="smbd.8.html"><strong>smbd</strong></a> and <a href="nmbd.8.html"><strong>nmbd</strong></a>.
<p><strong>Default:</strong>
<code>	bind interfaces only = False</code>
<p><strong>Example:</strong>
<code>	bind interfaces only = True</code>
<p><a name="blockinglocks"></a>
<p></p><dt><strong><strong>blocking locks (S)</strong></strong><dd>
<p>This parameter controls the behavior of <a href="smbd.8.html"><strong>smbd</strong></a> when
given a request by a client to obtain a byte range lock on a region
of an open file, and the request has a time limit associated with it.
<p>If this parameter is set and the lock range requested cannot be
immediately satisfied, Samba 2.0 will internally queue the lock 
request, and periodically attempt to obtain the lock until the
timeout period expires.
<p>If this parameter is set to "False", then Samba 2.0 will behave
as previous versions of Samba would and will fail the lock
request immediately if the lock range cannot be obtained.
<p>This parameter can be set per share.
<p><strong>Default:</strong>
<code>	blocking locks = True</code>
<p><strong>Example:</strong>
<code>	blocking locks = False</code>
<p><a name="browsable"></a>
<p></p><dt><strong><strong>browsable (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a>.
<p><a name="browselist"></a>
<p></p><dt><strong><strong>browse list(G)</strong></strong><dd>
<p>This controls whether <a href="smbd.8.html"><strong>smbd</strong></a> will serve a browse
list to a client doing a NetServerEnum call. Normally set to true. You
should never need to change this.
<p><strong>Default:</strong>
<code>	browse list = Yes</code>
<p><a name="browseable"></a>
<p></p><dt><strong><strong>browseable</strong></strong><dd>
<p>This controls whether this share is seen in the list of available
shares in a net view and in the browse list.
<p><strong>Default:</strong>
<code>	browseable = Yes</code>
<p><strong>Example:</strong>
<code>	browseable = No</code>
<p><a name="casesensitive"></a>
<p></p><dt><strong><strong>case sensitive (S)</strong></strong><dd>
<p>See the discussion in the section <a href="smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>.
<p><a name="casesignames"></a>
<p></p><dt><strong><strong>casesignames (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>.
<p><a name="changenotifytimeout"></a>
<p></p><dt><strong><strong>change notify timeout (G)</strong></strong><dd>
<p>One of the new NT SMB requests that Samba 2.0 supports is the
"ChangeNotify" requests. This SMB allows a client to tell a server to
<em>"watch"</em> a particular directory for any changes and only reply to
the SMB request when a change has occurred. Such constant scanning of
a directory is expensive under UNIX, hence an
<a href="smbd.8.html"><strong>smbd</strong></a> daemon only performs such a scan on each
requested directory once every <strong>change notify timeout</strong> seconds.
<p><strong>change notify timeout</strong> is specified in units of seconds.
<p><strong>Default:</strong>
<code>	change notify timeout = 60</code>
<p><strong>Example:</strong>
<code>	change notify timeout = 300</code>
<p>Would change the scan time to every 5 minutes.
<p><a name="characterset"></a>
<p></p><dt><strong><strong>character set (G)</strong></strong><dd>
<p>This allows a smbd to map incoming filenames from a DOS Code page (see
the <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> parameter) to several
built in UNIX character sets. The built in code page translations are:
<p><dl>
<p><li > <strong>ISO8859-1</strong> Western European UNIX character set. The parameter
<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
page 850 if the <strong>character set</strong> parameter is set to iso8859-1
in order for the conversion to the UNIX character set to be done
correctly.
<p><li > <strong>ISO8859-2</strong> Eastern European UNIX character set. The parameter
<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
page 852 if the <strong>character set</strong> parameter is set to ISO8859-2
in order for the conversion to the UNIX character set to be done
correctly. 
<p><li > <strong>ISO8859-5</strong> Russian Cyrillic UNIX character set. The parameter
<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
page 866 if the <strong>character set</strong> parameter is set to ISO8859-5
in order for the conversion to the UNIX character set to be done
correctly. 
<p><li > <strong>ISO8859-7</strong> Greek UNIX character set. The parameter
<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
page 737 if the <strong>character set</strong> parameter is set to ISO8859-7
in order for the conversion to the UNIX character set to be done
correctly. 
<p><li > <strong>KOI8-R</strong> Alternate mapping for Russian Cyrillic UNIX
character set. The parameter <a href="smb.conf.5.html#clientcodepage"><strong>client code
page</strong></a> <em>MUST</em> be set to code page 866 if the
<strong>character set</strong> parameter is set to KOI8-R in order for the
conversion to the UNIX character set to be done correctly.
<p></dl>
<p><em>BUG</em>. These MSDOS code page to UNIX character set mappings should
be dynamic, like the loading of MS DOS code pages, not static.
<p>See also <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a>.  Normally this
parameter is not set, meaning no filename translation is done.
<p><strong>Default:</strong>
<code>	character set = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	character set = ISO8859-1</code>
<p><a name="clientcodepage"></a>
<p></p><dt><strong><strong>client code page (G)</strong></strong><dd>
<p>This parameter specifies the DOS code page that the clients accessing
Samba are using. To determine what code page a Windows or DOS client
is using, open a DOS command prompt and type the command "chcp". This
will output the code page. The default for USA MS-DOS, Windows 95, and
Windows NT releases is code page 437. The default for western european
releases of the above operating systems is code page 850.
<p>This parameter tells <a href="smbd.8.html"><strong>smbd</strong></a> which of the
<code>codepage.XXX</code> files to dynamically load on startup. These files,
described more fully in the manual page <a href="make_smbcodepage.1.html"><strong>make_smbcodepage
(1)</strong></a>, tell <a href="smbd.8.html"><strong>smbd</strong></a> how
to map lower to upper case characters to provide the case insensitivity
of filenames that Windows clients expect.
<p>Samba currently ships with the following code page files :
<p><dl>
<p><li > <strong>Code Page 437 - MS-DOS Latin US</strong>
<p><li > <strong>Code Page 737 - Windows '95 Greek</strong>
<p><li > <strong>Code Page 850 - MS-DOS Latin 1</strong>
<p><li > <strong>Code Page 852 - MS-DOS Latin 2</strong>
<p><li > <strong>Code Page 861 - MS-DOS Icelandic</strong>
<p><li > <strong>Code Page 866 - MS-DOS Cyrillic</strong>
<p><li > <strong>Code Page 932 - MS-DOS Japanese SJIS</strong>
<p><li > <strong>Code Page 936 - MS-DOS Simplified Chinese</strong>
<p><li > <strong>Code Page 949 - MS-DOS Korean Hangul</strong>
<p><li > <strong>Code Page 950 - MS-DOS Traditional Chinese</strong>
<p></dl>
<p>Thus this parameter may have any of the values 437, 737, 850, 852,
861, 932, 936, 949, or 950.  If you don't find the codepage you need,
read the comments in one of the other codepage files and the
<a href="make_smbcodepage.1.html"><strong>make_smbcodepage (1)</strong></a> man page and
write one. Please remember to donate it back to the Samba user
community.
<p>This parameter co-operates with the <a href="smb.conf.5.html#validchars"><strong>"valid
chars"</strong></a> parameter in determining what characters are
valid in filenames and how capitalization is done. If you set both
this parameter and the <a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter
the <strong>"client code page"</strong> parameter <em>MUST</em> be set before the
<a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter in the <strong>smb.conf</strong>
file. The <a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> string will then augment
the character settings in the "client code page" parameter.
<p>If not set, <strong>"client code page"</strong> defaults to 850.
<p>See also : <a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a>
<p><strong>Default:</strong>
<code>	client code page = 850</code>
<p><strong>Example:</strong>
<code>	client code page = 936</code>
<p><a name="codingsystem"></a>
<p></p><dt><strong><strong>codingsystem (G)</strong></strong><dd>
<p>This parameter is used to determine how incoming Shift-JIS Japanese
characters are mapped from the incoming <a href="smb.conf.5.html#clientcodepage"><strong>"client code
page"</strong></a> used by the client, into file names in the
UNIX filesystem. Only useful if <a href="smb.conf.5.html#clientcodepage"><strong>"client code
page"</strong></a> is set to 932 (Japanese Shift-JIS).
<p>The options are :
<p><dl>
<p><li > <strong>SJIS</strong>  Shift-JIS. Does no conversion of the incoming filename.
<p><li > <strong>JIS8, J8BB, J8BH, J8@B, J8@J, J8@H </strong> Convert from incoming
Shift-JIS to eight bit JIS code with different shift-in, shift out
codes.
<p><li > <strong>JIS7, J7BB, J7BH, J7@B, J7@J, J7@H </strong> Convert from incoming
Shift-JIS to seven bit JIS code with different shift-in, shift out
codes.
<p><li > <strong>JUNET, JUBB, JUBH, JU@B, JU@J, JU@H </strong> Convert from incoming
Shift-JIS to JUNET code with different shift-in, shift out codes.
<p><li > <strong>EUC</strong>  Convert an incoming Shift-JIS character to EUC code.
<p><li > <strong>HEX</strong> Convert an incoming Shift-JIS character to a 3 byte hex
representation, i.e. <code>:AB</code>.
<p><li > <strong>CAP</strong> Convert an incoming Shift-JIS character to the 3 byte hex
representation used by the Columbia AppleTalk Program (CAP),
i.e. <code>:AB</code>.  This is used for compatibility between Samba and CAP.
<p></dl>
<p><a name="comment"></a>
<p></p><dt><strong><strong>comment (S)</strong></strong><dd>
<p>This is a text field that is seen next to a share when a client does a
queries the server, either via the network neighborhood or via "net
view" to list what shares are available.
<p>If you want to set the string that is displayed next to the machine
name then see the server string command.
<p><strong>Default:</strong>
<code>	No comment string</code>
<p><strong>Example:</strong>
<code>	comment = Fred's Files</code>
<p><a name="configfile"></a>
<p></p><dt><strong><strong>config file (G)</strong></strong><dd>
<p>This allows you to override the config file to use, instead of the
default (usually <strong>smb.conf</strong>). There is a chicken and egg problem
here as this option is set in the config file!
<p>For this reason, if the name of the config file has changed when the
parameters are loaded then it will reload them from the new config
file.
<p>This option takes the usual substitutions, which can be very useful.
<p>If the config file doesn't exist then it won't be loaded (allowing you
to special case the config files of just a few clients).
<p><strong>Example:</strong>
<code>	config file = /usr/local/samba/lib/smb.conf.%m</code>
<p><a name="copy"></a>
<p></p><dt><strong><strong>copy (S)</strong></strong><dd>
<p>This parameter allows you to <em>'clone'</em> service entries. The specified
service is simply duplicated under the current service's name. Any
parameters specified in the current section will override those in the
section being copied.
<p>This feature lets you set up a 'template' service and create similar
services easily. Note that the service being copied must occur earlier
in the configuration file than the service doing the copying.
<p><strong>Default:</strong>
<code>	none</code>
<p><strong>Example:</strong>
<code>	copy = otherservice</code>
<p><a name="createmask"></a>
<p></p><dt><strong><strong>create mask (S)</strong></strong><dd>
<p>A synonym for this parameter is <a href="smb.conf.5.html#createmode"><strong>'create mode'</strong></a>.
<p>When a file is created, the necessary permissions are calculated
according to the mapping from DOS modes to UNIX permissions, and the
resulting UNIX mode is then bit-wise 'AND'ed with this parameter.
This parameter may be thought of as a bit-wise MASK for the UNIX modes
of a file. Any bit <em>*not*</em> set here will be removed from the modes set
on a file when it is created.
<p>The default value of this parameter removes the 'group' and 'other'
write and execute bits from the UNIX modes.
<p>Following this Samba will bit-wise 'OR' the UNIX mode created from
this parameter with the value of the "force create mode" parameter
which is set to 000 by default.
<p>This parameter does not affect directory modes. See the parameter
<a href="smb.conf.5.html#directorymode"><strong>'directory mode'</strong></a> for details.
<p>See also the <a href="smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> parameter
for forcing particular mode bits to be set on created files. See also
the <a href="smb.conf.5.html#directorymode"><strong>"directory mode"</strong></a> parameter for masking
mode bits on created directories.
See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	create mask = 0744</code>
<p><strong>Example:</strong>
<code>	create mask = 0775</code>
<p><a name="createmode"></a>
<p></p><dt><strong><strong>create mode (S)</strong></strong><dd>
<p>This is a synonym for <a href="smb.conf.5.html#createmask"><strong>create mask</strong></a>.
<p><a name="deadtime"></a>
<p></p><dt><strong><strong>deadtime (G)</strong></strong><dd>
<p>The value of the parameter (a decimal integer) represents the number
of minutes of inactivity before a connection is considered dead, and
it is disconnected. The deadtime only takes effect if the number of
open files is zero.
<p>This is useful to stop a server's resources being exhausted by a large
number of inactive connections.
<p>Most clients have an auto-reconnect feature when a connection is
broken so in most cases this parameter should be transparent to users.
<p>Using this parameter with a timeout of a few minutes is recommended
for most systems.
<p>A deadtime of zero indicates that no auto-disconnection should be
performed.
<p><strong>Default:</strong>
<code>	deadtime = 0</code>
<p><strong>Example:</strong>
<code>	deadtime = 15</code>
<p><a name="debughirestimestamp"></a>
<p></p><dt><strong><strong>debug hires timestamp (G)</strong></strong><dd>
<p>Sometimes the timestamps in the log messages are needed with a
resolution of higher that seconds, this boolean parameter adds
microsecond resolution to the timestamp message header when turned on.
<p>Note that the parameter <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
must be on for this to have an effect.
<p><strong>Default:</strong>
<code> debug hires timestamp = No</code>
<p><strong>Example:</strong>
<code> debug hires timestamp = Yes</code>
<p><a name="debugtimestamp"></a>
<p></p><dt><strong><strong>debug timestamp (G)</strong></strong><dd>
<p>Samba2.0 debug log messages are timestamped by default. If you are
running at a high <a href="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> these timestamps
can be distracting. This boolean parameter allows timestamping to be turned
off.
<p><strong>Default:</strong>
<code>	debug timestamp = Yes</code>
<p><strong>Example:</strong>
<code>	debug timestamp = No</code>
<p><a name="debugpid"></a>
<p></p><dt><strong><strong>debug pid (G)</strong></strong><dd>
<p>When using only one log file for more then one forked smbd-process
there may be hard to follow which process outputs which message.
This boolean parameter is adds the process-id to the timestamp message
headers in the logfile when turned on.
<p>Note that the parameter <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
must be on for this to have an effect.
<p><strong>Default:</strong>
<code>	debug pid = No</code>
<p><strong>Example:</strong>
<code>	debug pid = Yes</code>
<p><a name="debuguid"></a>
<p></p><dt><strong><strong>debug uid (G)</strong></strong><dd>
<p>Samba is sometimes run as root and sometime run as the connected
user, this boolean parameter inserts the current euid, egid, uid
and gid to the timestamp message headers in the log file if turned on.
<p>Note that the parameter <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
must be on for this to have an effect.
<p><strong>Default:</strong>
<code>	debug uid = No</code>
<p><strong>Example:</strong>
<code>	debug uid = Yes</code>
<p><a name="debuglevel"></a>
<p></p><dt><strong><strong>debug level (G)</strong></strong><dd>
<p>The value of the parameter (an integer) allows the debug level
(logging level) to be specified in the <strong>smb.conf</strong> file. This is to
give greater flexibility in the configuration of the system.
<p>The default will be the debug level specified on the command line
or level zero if none was specified.
<p><strong>Example:</strong>
<code>	debug level = 3</code>
<p><a name="default"></a>
<p></p><dt><strong><strong>default (G)</strong></strong><dd>
<p>A synonym for <a href="smb.conf.5.html#defaultservice"><strong>default service</strong></a>.
<p><a name="defaultcase"></a>
<p></p><dt><strong><strong>default case (S)</strong></strong><dd>
<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a>. Also note
the <a href="smb.conf.5.html#shortpreservecase"><strong>"short preserve case"</strong></a> parameter.
<p><a name="defaultservice"></a>
<p></p><dt><strong><strong>default service (G)</strong></strong><dd>
<p>This parameter specifies the name of a service which will be connected
to if the service actually requested cannot be found. Note that the
square brackets are <em>NOT</em> given in the parameter value (see example
below).
<p>There is no default value for this parameter. If this parameter is not
given, attempting to connect to a nonexistent service results in an
error.
<p>Typically the default service would be a <a href="smb.conf.5.html#guestok"><strong>guest ok</strong></a>,
<a href="smb.conf.5.html#readonly"><strong>read-only</strong></a> service.
<p>Also note that the apparent service name will be changed to equal that
of the requested service, this is very useful as it allows you to use
macros like <a href="smb.conf.5.html#percentS"><strong>%S</strong></a> to make a wildcard service.
<p>Note also that any <code>'_'</code> characters in the name of the service used
in the default service will get mapped to a <code>'/'</code>. This allows for
interesting things.
<p><strong>Example:</strong>
<pre>

	default service = pub
        
	[pub]
		path = /%S

</pre>

<p><a name="deleteuserscript"></a>
<p></p><dt><strong><strong>delete user script (G)</strong></strong><dd>
<p>This is the full pathname to a script that will be run <em>AS ROOT</em> by
<a href="smbd.8.html"><strong>smbd (8)</strong></a> under special circumstances decribed
below.
<p>Normally, a Samba server requires that UNIX users are created for all
users accessing files on this server. For sites that use Windows NT
account databases as their primary user database creating these users
and keeping the user list in sync with the Windows NT PDC is an
onerous task. This option allows <a href="smbd.8.html"><strong>smbd</strong></a> to delete
the required UNIX users <em>ON DEMAND</em> when a user accesses the Samba
server and the Windows NT user no longer exists.
<p>In order to use this option, <a href="smbd.8.html"><strong>smbd</strong></a> must be set to
<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a> and <strong>"delete user
script"</strong> must be set to a full pathname for a script that will delete
a UNIX user given one argument of <strong>%u</strong>, which expands into the UNIX
user name to delete. <em>NOTE</em> that this is different to the
<a href="smb.conf.5.html#adduserscript"><strong>add user script</strong></a> which will work with the
<a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> option as well as
<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>. The reason for this
is only when Samba is a domain member does it get the information
on an attempted user logon that a user no longer exists. In the
<a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> mode a missing user
is treated the same as an invalid password logon attempt. Deleting
the user in this circumstance would not be a good idea.
<p>When the Windows user attempts to access the Samba server, at
<em>"login"</em>(session setup in the SMB protocol) time,
<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="smb.conf.5.html#passwordserver"><strong>password
server</strong></a> and attempts to authenticate the given user
with the given password. If the authentication fails with the specific
Domain error code meaning that the user no longer exists then
<a href="smbd.8.html"><strong>smbd</strong></a> attempts to find a UNIX user in the UNIX
password database that matches the Windows user account. If this lookup succeeds,
and <strong>"delete user script"</strong> is set then <a href="smbd.8.html"><strong>smbd</strong></a> will
call the specified script <em>AS ROOT</em>, expanding any <strong>%u</strong> argument
to be the user name to delete.
<p>This script should delete the given UNIX username. In this way, UNIX
users are dynamically deleted to match existing Windows NT accounts.
<p>See also <a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>,
<a href="smb.conf.5.html#passwordserver"><strong>password server</strong></a>, <a href="smb.conf.5.html#adduserscript"><strong>add user
script</strong></a>.
<p><strong>Default:</strong>
<code>	delete user script = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	delete user script = /usr/local/samba/bin/del_user %u</code>
<p><a name="deletereadonly"></a>
<p></p><dt><strong><strong>delete readonly (S)</strong></strong><dd>
<p>This parameter allows readonly files to be deleted.  This is not
normal DOS semantics, but is allowed by UNIX.
<p>This option may be useful for running applications such as rcs, where
UNIX file ownership prevents changing file permissions, and DOS
semantics prevent deletion of a read only file.
<p><strong>Default:</strong>
<code>	delete readonly = No</code>
<p><strong>Example:</strong>
<code>	delete readonly = Yes</code>
<p><a name="deletevetofiles"></a>
<p></p><dt><strong><strong>delete veto files (S)</strong></strong><dd>
<p>This option is used when Samba is attempting to delete a directory
that contains one or more vetoed directories (see the <a href="smb.conf.5.html#vetofiles"><strong>'veto
files'</strong></a> option).  If this option is set to False (the
default) then if a vetoed directory contains any non-vetoed files or
directories then the directory delete will fail. This is usually what
you want.
<p>If this option is set to True, then Samba will attempt to recursively
delete any files and directories within the vetoed directory. This can
be useful for integration with file serving systems such as <strong>NetAtalk</strong>,
which create meta-files within directories you might normally veto
DOS/Windows users from seeing (e.g. <code>.AppleDouble</code>)
<p>Setting <code>'delete veto files = True'</code> allows these directories to be 
transparently deleted when the parent directory is deleted (so long
as the user has permissions to do so).
<p>See also the <a href="smb.conf.5.html#vetofiles"><strong>veto files</strong></a> parameter.
<p><strong>Default:</strong>
<code>	delete veto files = False</code>
<p><strong>Example:</strong>
<code>	delete veto files = True</code>
<p><a name="denyhosts"></a>
<p></p><dt><strong><strong>deny hosts (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a>.
<p><a name="dfreecommand"></a>
<p></p><dt><strong><strong>dfree command (G)</strong></strong><dd>
<p>The dfree command setting should only be used on systems where a
problem occurs with the internal disk space calculations. This has
been known to happen with Ultrix, but may occur with other operating
systems. The symptom that was seen was an error of "Abort Retry
Ignore" at the end of each directory listing.
<p>This setting allows the replacement of the internal routines to
calculate the total disk space and amount available with an external
routine. The example below gives a possible script that might fulfill
this function.
<p>The external program will be passed a single parameter indicating a
directory in the filesystem being queried. This will typically consist
of the string <code>"./"</code>. The script should return two integers in
ascii. The first should be the total disk space in blocks, and the
second should be the number of available blocks. An optional third
return value can give the block size in bytes. The default blocksize
is 1024 bytes.
<p>Note: Your script should <em>NOT</em> be setuid or setgid and should be
owned by (and writeable only by) root!
<p><strong>Default:</strong>
<code>	By default internal routines for determining the disk capacity
and remaining space will be used.</code>
<p><strong>Example:</strong>
<code>	dfree command = /usr/local/samba/bin/dfree</code>
<p>Where the script dfree (which must be made executable) could be:
<p><pre>

	#!/bin/sh
	df $1 | tail -1 | awk '{print $2" "$4}'

</pre>

<p>or perhaps (on Sys V based systems):
<p><pre>

	#!/bin/sh
	/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'

</pre>

<p>Note that you may have to replace the command names with full
path names on some systems.
<p><a name="directory"></a>
<p></p><dt><strong><strong>directory (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#path"><strong>path</strong></a>.
<p><a name="directorymask"></a>
<p></p><dt><strong><strong>directory mask (S)</strong></strong><dd>
<p>This parameter is the octal modes which are used when converting DOS
modes to UNIX modes when creating UNIX directories.
<p>When a directory is created, the necessary permissions are calculated
according to the mapping from DOS modes to UNIX permissions, and the
resulting UNIX mode is then bit-wise 'AND'ed with this parameter.
This parameter may be thought of as a bit-wise MASK for the UNIX modes
of a directory. Any bit <em>*not*</em> set here will be removed from the
modes set on a directory when it is created.
<p>The default value of this parameter removes the 'group' and 'other'
write bits from the UNIX mode, allowing only the user who owns the
directory to modify it.
<p>Following this Samba will bit-wise 'OR' the UNIX mode created from
this parameter with the value of the "force directory mode"
parameter. This parameter is set to 000 by default (i.e. no extra mode
bits are added).
<p>See the <a href="smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a> parameter
to cause particular mode bits to always be set on created directories.
<p>See also the <a href="smb.conf.5.html#createmode"><strong>"create mode"</strong></a> parameter for masking
mode bits on created files, and the <a href="smb.conf.5.html#directorysecuritymask"><strong>"directory security mask"</strong></a>
parameter.
<p>See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	directory mask = 0755</code>
<p><strong>Example:</strong>
<code>	directory mask = 0775</code>
<p><a name="directorymode"></a>
<p></p><dt><strong><strong>directory mode (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#directorymask"><strong>directory mask</strong></a>.
<p><a name="directorysecuritymask"></a>
<p></p><dt><strong><strong>directory security mask (S)</strong></strong><dd>
<p>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.
<p>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.
<p>If not set explicitly this parameter is set to the same value as the
<a href="smb.conf.5.html#directorymask"><strong>directory mask</strong></a> parameter. To allow a user to
modify all the user/group/world permissions on a directory, set this
parameter to 0777.
<p><em>Note</em> 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.
<p>See also the <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security
mode</strong></a>, <a href="smb.conf.5.html#securitymask"><strong>security
mask</strong></a>, <a href="smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a>
parameters.
<p><strong>Default:</strong>
<code>	directory security mask = &lt;same as directory mask&gt;</code>
<p><strong>Example:</strong>
<code>	directory security mask = 0777</code>
<p><a name="dnsproxy"></a>
<p></p><dt><strong><strong>dns proxy (G)</strong></strong><dd>
<p>Specifies that <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS
server and finding that a NetBIOS name has not been registered, should
treat the NetBIOS name word-for-word as a DNS name and do a lookup
with the DNS server for that name on behalf of the name-querying
client.
<p>Note that the maximum length for a NetBIOS name is 15 characters, so
the DNS name (or DNS alias) can likewise only be 15 characters,
maximum.
<p><a href="nmbd.8.html"><strong>nmbd</strong></a> spawns a second copy of itself to do the
DNS name lookup requests, as doing a name lookup is a blocking action.
<p>See also the parameter <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a>.
<p><strong>Default:</strong>
<code>	dns proxy = yes</code>
<p><a name="domainadmingroup"></a>
<strong>domain admin group (G)</strong>
<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished
Samba NT Domain Controller Code. It may be removed in a later release.
To work with the latest code builds that may have more support for
Samba NT Domain Controller functionality please subscribe to the
mailing list <strong>Samba-ntdom</strong> available by visiting the web page at
<a href="http://lists.samba.org/">http://lists.samba.org/</a>
<p><a name="domainadminusers"></a> 
<p></p><dt><strong><strong>domain admin users (G)</strong></strong><dd>
<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished
Samba NT Domain Controller Code. It may be removed in a later release.
To work with the latest code builds that may have more support for
Samba NT Domain Controller functionality please subscribe to the
mailing list <strong>Samba-ntdom</strong> available by visiting the web page at
<a href="http://lists.samba.org/">http://lists.samba.org/</a>
<p><a name="domaingroups"></a>
<p></p><dt><strong><strong>domain groups (G)</strong></strong><dd>
<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished
Samba NT Domain Controller Code. It may be removed in a later release.
To work with the latest code builds that may have more support for
Samba NT Domain Controller functionality please subscribe to the
mailing list <strong>Samba-ntdom</strong> available by visiting the web page at
<a href="http://lists.samba.org/">http://lists.samba.org/</a>
<p><a name="domainguestgroup"></a>
<p></p><dt><strong><strong>domain guest group (G)</strong></strong><dd>
<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished
Samba NT Domain Controller Code. It may be removed in a later release.
To work with the latest code builds that may have more support for
Samba NT Domain Controller functionality please subscribe to the
mailing list <strong>Samba-ntdom</strong> available by visiting the web page at 
<a href="http://lists.samba.org/">http://lists.samba.org/</a>
<p><a name="domainguestusers"></a>
<p></p><dt><strong><strong>domain guest users (G)</strong></strong><dd>
<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished
Samba NT Domain Controller Code. It may be removed in a later release.
To work with the latest code builds that may have more support for
Samba NT Domain Controller functionality please subscribe to the
mailing list <strong>Samba-ntdom</strong> available by visiting the web page at
<a href="http://lists.samba.org/">http://lists.samba.org/</a>
<p><a name="domainlogons"></a>
<p></p><dt><strong><strong>domain logons (G)</strong></strong><dd>
<p>If set to true, the Samba server will serve Windows 95/98 Domain
logons for the <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> it is in. For more
details on setting up this feature see the file DOMAINS.txt in the
Samba documentation directory <code>docs/</code> shipped with the source code.
<p>Note that Win95/98 Domain logons are <em>NOT</em> the same as Windows
NT Domain logons. NT Domain logons require a Primary Domain Controller
(PDC) for the Domain. It is intended that in a future release Samba
will be able to provide this functionality for Windows NT clients
also.
<p><strong>Default:</strong>
<code>	domain logons = no</code>
<p><a name="domainmaster"></a>
<p></p><dt><strong><strong>domain master (G)</strong></strong><dd>
<p>Tell <a href="nmbd.8.html"><strong>nmbd</strong></a> to enable WAN-wide browse list
collation. Setting this option causes <a href="nmbd.8.html"><strong>nmbd</strong></a> to
claim a special domain specific NetBIOS name that identifies it as a
domain master browser for its given
<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a>. Local master browsers in the same
<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> on broadcast-isolated subnets will give
this <a href="nmbd.8.html"><strong>nmbd</strong></a> their local browse lists, and then
ask <a href="smbd.8.html"><strong>smbd</strong></a> for a complete copy of the browse list
for the whole wide area network.  Browser clients will then contact
their local master browser, and will receive the domain-wide browse
list, instead of just the list for their broadcast-isolated subnet.
<p>Note that Windows NT Primary Domain Controllers expect to be able to
claim this <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> specific special NetBIOS
name that identifies them as domain master browsers for that
<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> by default (i.e. there is no way to
prevent a Windows NT PDC from attempting to do this). This means that
if this parameter is set and <a href="nmbd.8.html"><strong>nmbd</strong></a> claims the
special name for a <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> before a Windows NT
PDC is able to do so then cross subnet browsing will behave strangely
and may fail.
<p><strong>Default:</strong>
<code>	domain master = no</code>
<p><a name="dontdescend"></a>
<p></p><dt><strong><strong>dont descend (S)</strong></strong><dd>
<p>There are certain directories on some systems (e.g., the <code>/proc</code> tree
under Linux) that are either not of interest to clients or are
infinitely deep (recursive). This parameter allows you to specify a
comma-delimited list of directories that the server should always show
as empty.
<p>Note that Samba can be very fussy about the exact format of the "dont
descend" entries. For example you may need <code>"./proc"</code> instead of
just <code>"/proc"</code>. Experimentation is the best policy :-)
<p><strong>Default:</strong>
<code>	none (i.e., all directories are OK to descend)</code>
<p><strong>Example:</strong>
<code>	dont descend = /proc,/dev</code>
<p><a name="dosfiletimeresolution"></a>
<p></p><dt><strong><strong>dos filetime resolution (S)</strong></strong><dd>
<p>Under the DOS and Windows FAT filesystem, the finest granularity on
time resolution is two seconds. Setting this parameter for a share
causes Samba to round the reported time down to the nearest two second
boundary when a query call that requires one second resolution is made
to <a href="smbd.8.html"><strong>smbd</strong></a>.
<p>This option is mainly used as a compatibility option for Visual C++
when used against Samba shares. If oplocks are enabled on a share,
Visual C++ uses two different time reading calls to check if a file
has changed since it was last read. One of these calls uses a
one-second granularity, the other uses a two second granularity. As
the two second call rounds any odd second down, then if the file has a
timestamp of an odd number of seconds then the two timestamps will not
match and Visual C++ will keep reporting the file has changed. Setting
this option causes the two timestamps to match, and Visual C++ is
happy.
<p><strong>Default:</strong>
<code>	dos filetime resolution = False</code>
<p><strong>Example:</strong>
<code>	dos filetime resolution = True</code>
<p><a name="dosfiletimes"></a>
<p></p><dt><strong><strong>dos filetimes (S)</strong></strong><dd>
<p>Under DOS and Windows, if a user can write to a file they can change
the timestamp on it. Under POSIX semantics, only the owner of the file
or root may change the timestamp. By default, Samba runs with POSIX
semantics and refuses to change the timestamp on a file if the user
smbd is acting on behalf of is not the file owner. Setting this option
to True allows DOS semantics and smbd will change the file timestamp as
DOS requires.
<p><strong>Default:</strong>
<code>	dos filetimes = False</code>
<p><strong>Example:</strong>
<code>	dos filetimes = True</code>
<p><a name="encryptpasswords"></a>
<p></p><dt><strong><strong>encrypt passwords (G)</strong></strong><dd>
<p>This boolean controls whether encrypted passwords will be negotiated
with the client. Note that Windows NT 4.0 SP3 and above and also
Windows 98 will by default expect encrypted passwords unless a
registry entry is changed. To use encrypted passwords in Samba see the
file ENCRYPTION.txt in the Samba documentation directory <code>docs/</code>
shipped with the source code.
<p>In order for encrypted passwords to work correctly
<a href="smbd.8.html"><strong>smbd</strong></a> must either have access to a local
<a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a> file (see the
<a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a> program for information on
how to set up and maintain this file), or set the
<a href="smb.conf.5.html#security"><strong>security=</strong></a> parameter to either
<a href="smb.conf.5.html#securityequalserver"><strong>"server"</strong></a> or
<a href="smb.conf.5.html#securityequaldomain"><strong>"domain"</strong></a> which causes
<a href="smbd.8.html"><strong>smbd</strong></a> to authenticate against another server.
<p><a name="exec"></a>
<p></p><dt><strong><strong>exec (S)</strong></strong><dd>
<p>This is a synonym for <a href="smb.conf.5.html#preexec"><strong>preexec</strong></a>.
<p><a name="fakedirectorycreatetimes"></a>
<p></p><dt><strong><strong>fake directory create times (S)</strong></strong><dd>
<p>NTFS and Windows VFAT file systems keep a create time for all files
and directories. This is not the same as the ctime - status change
time - that Unix keeps, so Samba by default reports the earliest of
the various times Unix does keep. Setting this parameter for a share
causes Samba to always report midnight 1-1-1980 as the create time for
directories.
<p>This option is mainly used as a compatibility option for Visual C++
when used against Samba shares. Visual C++ generated makefiles have
the object directory as a dependency for each object file, and a make
rule to create the directory. Also, when NMAKE compares timestamps it
uses the creation time when examining a directory. Thus the object
directory will be created if it does not exist, but once it does exist
it will always have an earlier timestamp than the object files it
contains.
<p>However, Unix time semantics mean that the create time reported by
Samba will be updated whenever a file is created or deleted in the
directory. NMAKE therefore finds all object files in the object
directory bar the last one built are out of date compared to the
directory and rebuilds them. Enabling this option ensures directories
always predate their contents and an NMAKE build will proceed as
expected.
<p><strong>Default:</strong>
<code>	fake directory create times = False</code>
<p><strong>Example:</strong>
<code>	fake directory create times = True</code>
<p><a name="fakeoplocks"></a>
<p></p><dt><strong><strong>fake oplocks (S)</strong></strong><dd>
<p>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.
<p>When you set <code>"fake oplocks = yes"</code> <a href="smbd.8.html"><strong>smbd</strong></a> will
always grant oplock requests no matter how many clients are using the
file.
<p>It is generally much better to use the real <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a>
support rather than this parameter.
<p>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!
<p>This option is disabled by default.
<p><a name="followsymlinks"></a>
<p></p><dt><strong><strong>follow symlinks (S)</strong></strong><dd>
<p>This parameter allows the Samba administrator to stop
<a href="smbd.8.html"><strong>smbd</strong></a> from following symbolic links in a
particular share. Setting this parameter to <em>"No"</em> 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 <code>/etc/passwd</code> in their home directory for
instance.  However it will slow filename lookups down slightly.
<p>This option is enabled (i.e. <a href="smbd.8.html"><strong>smbd</strong></a> will follow
symbolic links) by default.
<p><a name="forcecreatemode"></a>
<p></p><dt><strong><strong>force create mode (S)</strong></strong><dd>
<p>This parameter specifies a set of UNIX mode bit permissions that will
<em>*always*</em> be set on a file by Samba. This is done by bitwise
'OR'ing these bits onto the mode bits of a file that is being created
or having its permissions changed. 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 <a href="smb.conf.5.html#createmask"><strong>"create
mask"</strong></a> parameter is applied.
<p>See also the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> for details
on masking mode bits on files.
<p>See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	force create mode = 000</code>
<p><strong>Example:</strong>
<code>	force create mode = 0755</code>
<p>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'.
<p><a name="forcedirectorymode"></a>
<p></p><dt><strong><strong>force directory mode (S)</strong></strong><dd>
<p>This parameter specifies a set of UNIX mode bit permissions that will
<em>*always*</em> 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
<a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> is applied.
<p>See also the parameter <a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> for
details on masking mode bits on created directories.
<p>See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	force directory mode = 000</code>
<p><strong>Example:</strong>
<code>	force directory mode = 0755</code>
<p>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'.
<p><a name="forcedirectorysecuritymode"></a>
<p></p><dt><strong><strong>force directory security mode (S)</strong></strong><dd>
<p>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.
<p>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'.
<p>If not set explicitly this parameter is set to the same value as the
<a href="smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a> parameter. To allow
a user to modify all the user/group/world permissions on a directory,
with restrictions set this parameter to 000.
<p><em>Note</em> 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.
<p>See also the <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security mask</strong></a>,
<a href="smb.conf.5.html#securitymask"><strong>security mask</strong></a>, <a href="smb.conf.5.html#forcesecuritymode"><strong>force security
mode</strong></a> parameters.
<p><strong>Default:</strong>
<code>	force directory security mode = &lt;same as force directory mode&gt;</code>
<p><strong>Example:</strong>
<code>	force directory security mode = 0</code>
<p><a name="forcegroup"></a>
<p></p><dt><strong><strong>force group (S)</strong></strong><dd>
<p>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.
<p>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 <code>force group = +sys</code> 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.
<p>If the <a href="smb.conf.5.html#forceuser"><strong>"force user"</strong></a> parameter is also set the
group specified in <strong>force group</strong> will override the primary group
set in <a href="smb.conf.5.html#forceuser"><strong>"force user"</strong></a>.
<p>See also <a href="smb.conf.5.html#forceuser"><strong>"force user"</strong></a>
<p><strong>Default:</strong>
<code>	no forced group</code>
<p><strong>Example:</strong>
<code>	force group = agroup</code>
<p><a name="forcesecuritymode"></a>
<p></p><dt><strong><strong>force security mode (S)</strong></strong><dd>
<p>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.
<p>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'.
<p>If not set explicitly this parameter is set to the same value as the
<a href="smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a> parameter. To allow
a user to modify all the user/group/world permissions on a file,
with no restrictions set this parameter to 000.
<p><em>Note</em> 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.
<p>See also the <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security
mode</strong></a>, <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security
mask</strong></a>, <a href="smb.conf.5.html#securitymask"><strong>security mask</strong></a>
parameters.
<p><strong>Default:</strong>
<code>	force security mode = &lt;same as force create mode&gt;</code>
<p><strong>Example:</strong>
<code>	force security mode = 0</code>
<p><a name="forceuser"></a>
<p></p><dt><strong><strong>force user (S)</strong></strong><dd>
<p>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.
<p>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
<code>"forced user"</code>, no matter what username the client connected as.
<p>This can be very useful.
<p>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).
<p>See also <a href="smb.conf.5.html#forcegroup"><strong>"force group"</strong></a>
<p><strong>Default:</strong>
<code>	no forced user</code>
<p><strong>Example:</strong>
<code>	force user = auser</code>
<p><a name="fstype"></a>
<p></p><dt><strong><strong>fstype (S)</strong></strong><dd>
<p>This parameter allows the administrator to configure the string that
specifies the type of filesystem a share is using that is reported by
<a href="smbd.8.html"><strong>smbd</strong></a> when a client queries the filesystem type
for a share. The default type is <strong>"NTFS"</strong> for compatibility with
Windows NT but this can be changed to other strings such as "Samba" or
"FAT" if required.
<p><strong>Default:</strong>
<code>	fstype = NTFS</code>
<p><strong>Example:</strong>
<code>	fstype = Samba</code>
<p><a name="getwdcache"></a>
<p></p><dt><strong><strong>getwd cache (G)</strong></strong><dd>
<p>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
<a href="smb.conf.5.html#widelinks"><strong>widelinks</strong></a> parameter is set to False.
<p><strong>Default:</strong>
<code>	getwd cache = No</code>
<p><strong>Example:</strong>
<code>	getwd cache = Yes</code>
<p><a name="group"></a>
<p></p><dt><strong><strong>group (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#forcegroup"><strong>"force group"</strong></a>.
<p><a name="guestaccount"></a>
<p></p><dt><strong><strong>guest account (S)</strong></strong><dd>
<p>This is a username which will be used for access to services which are
specified as <a href="smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> (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 <strong>"ftp"</strong> is
often a good choice for this parameter. If a username is specified in
a given service, the specified username overrides this one.
<p>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 <code>"su -"</code>
command) and trying to print using the system print command such as
<strong>lpr (1)</strong> or <strong>lp (1)</strong>.
<p><strong>Default:</strong>
<code>	specified at compile time, usually "nobody"</code>
<p><strong>Example:</strong>
<code>	guest account = ftp</code>
<p><a name="guestok"></a>
<p></p><dt><strong><strong>guest ok (S)</strong></strong><dd>
<p>If this parameter is <em>'yes'</em> for a service, then no password is
required to connect to the service. Privileges will be those of the
<a href="smb.conf.5.html#guestaccount"><strong>guest account</strong></a>.
<p>See the section below on <a href="smb.conf.5.html#security"><strong>security</strong></a> for more
information about this option.
<p><strong>Default:</strong>
<code>	guest ok = no</code>
<p><strong>Example:</strong>
<code>	guest ok = yes</code>
<p><a name="guestonly"></a>
<p></p><dt><strong><strong>guest only (S)</strong></strong><dd>
<p>If this parameter is <em>'yes'</em> for a service, then only guest
connections to the service are permitted. This parameter will have no
affect if <a href="smb.conf.5.html#guestok"><strong>"guest ok"</strong></a> or <a href="smb.conf.5.html#public"><strong>"public"</strong></a>
is not set for the service.
<p>See the section below on <a href="smb.conf.5.html#security"><strong>security</strong></a> for more
information about this option.
<p><strong>Default:</strong>
<code>	guest only = no</code>
<p><strong>Example:</strong>
<code>	guest only = yes</code>
<p><a name="hidedotfiles"></a>
<p></p><dt><strong><strong>hide dot files (S)</strong></strong><dd>
<p>This is a boolean parameter that controls whether files starting with
a dot appear as hidden files.
<p><strong>Default:</strong>
<code>	hide dot files = yes</code>
<p><strong>Example:</strong>
<code>	hide dot files = no</code>
<p><a name="hidefiles"></a>
<p></p><dt><strong><strong>hide files(S)</strong></strong><dd>
<p>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.
<p>Each entry in the list must be separated by a <code>'/'</code>, which allows
spaces to be included in the entry.  <code>'*'</code> and <code>'?'</code> can be used
to specify multiple files or directories as in DOS wildcards.
<p>Each entry must be a Unix path, not a DOS path and must not include the 
Unix directory separator <code>'/'</code>.
<p>Note that the case sensitivity option is applicable in hiding files.
<p>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.
<p>See also <a href="smb.conf.5.html#hidedotfiles"><strong>"hide dot files"</strong></a>, <a href="smb.conf.5.html#vetofiles"><strong>"veto
files"</strong></a> and <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>.
<p><strong>Default</strong>
<pre>

	No files or directories are hidden by this option (dot files are
	hidden by default because of the "hide dot files" option).

</pre>

<p><strong>Example</strong>
<code>	hide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/</code>
<p>The above example is based on files that the Macintosh SMB client
(DAVE) available from <a href="http://www.thursby.com"><strong>Thursby</strong></a> creates for
internal use, and also still hides all files beginning with a dot.
<p><a name="homedirmap"></a>
<p></p><dt><strong><strong>homedir map (G)</strong></strong><dd>
<p>If <a href="smb.conf.5.html#nishomedir"><strong>"nis homedir"</strong></a> is true, and
<a href="smbd.8.html"><strong>smbd</strong></a> is also acting as a Win95/98 <a href="smb.conf.5.html#domainlogons"><strong>logon
server</strong></a> 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:
<p><code>username	server:/some/file/system</code>
<p>and the program will extract the servername from before the first
<code>':'</code>.  There should probably be a better parsing system that copes
with different map formats and also Amd (another automounter) maps.
<p>NB: A working NIS is required on the system for this option to work.
<p>See also <a href="smb.conf.5.html#nishomedir"><strong>"nis homedir"</strong></a>, <a href="smb.conf.5.html#domainlogons"><strong>domain
logons</strong></a>.
<p><strong>Default:</strong>
<code>	homedir map = auto.home</code>
<p><strong>Example:</strong>
<code>	homedir map = amd.homedir</code>
<p><a name="hostsallow"></a>
<p></p><dt><strong><strong>hosts allow (S)</strong></strong><dd>
<p>A synonym for this parameter is <a href="smb.conf.5.html#allowhosts"><strong>'allow hosts'</strong></a>
<p>This parameter is a comma, space, or tab delimited set of hosts which
are permitted to access a service.
<p>If specified in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section then it will
apply to all services, regardless of whether the individual service
has a different setting.
<p>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 <code>"allow hosts = 150.203.5."</code>. The full syntax of the list is
described in the man page <strong>hosts_access (5)</strong>. Note that this man
page may not be present on your system, so a brief description will
be given here also.
<p>Note that the localhost address 127.0.0.1 will always be allowed
access unless specifically denied by a "hosts deny" option.
<p>You can also specify hosts by network/netmask pairs and by netgroup
names if your system supports netgroups. The <em>EXCEPT</em> keyword can also
be used to limit a wildcard list. The following examples may provide
some help:
<p><strong>Example 1</strong>: allow all IPs in 150.203.*.* except one
<p><code>	hosts allow = 150.203. EXCEPT 150.203.6.66</code>
<p><strong>Example 2</strong>: allow hosts that match the given network/netmask
<p><code>	hosts allow = 150.203.15.0/255.255.255.0</code>
<p><strong>Example 3</strong>: allow a couple of hosts
<p><code>	hosts allow = lapland, arvidsjaur</code>
<p><strong>Example 4</strong>: allow only hosts in NIS netgroup "foonet", but 
deny access from one particular host
<p><code> 	hosts allow = @foonet</code>
<p><code> 	hosts deny = pirate</code>
<p>Note that access still requires suitable user-level passwords.
<p>See <a href="testparm.1.html"><strong>testparm (1)</strong></a> for a way of testing your
host access to see if it does what you expect.
<p><strong>Default:</strong>
<code>	none (i.e., all hosts permitted access)</code>
<p><strong>Example:</strong>
<code>	allow hosts = 150.203.5. myhost.mynet.edu.au</code>
<p><a name="hostsdeny"></a>
<p></p><dt><strong><strong>hosts deny (S)</strong></strong><dd>
<p>The opposite of <a href="smb.conf.5.html#hostsallow"><strong>'hosts allow'</strong></a> - hosts listed
here are <em>NOT</em> permitted access to services unless the specific
services have their own lists to override this one. Where the lists
conflict, the <a href="smb.conf.5.html#hostsallow"><strong>'allow'</strong></a> list takes precedence.
<p><strong>Default:</strong>
<code>	none (i.e., no hosts specifically excluded)</code>
<p><strong>Example:</strong>
<code>	hosts deny = 150.203.4. badhost.mynet.edu.au</code>
<p><a name="hostsequiv"></a>
<p></p><dt><strong><strong>hosts equiv (G)</strong></strong><dd>
<p>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.
<p>This is not be confused with <a href="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a> which
is about hosts access to services and is more useful for guest
services. <strong>hosts equiv</strong> may be useful for NT clients which will not
supply passwords to samba.
<p>NOTE: The use of <strong>hosts equiv</strong> 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
<strong>hosts equiv</strong> 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 <em>really</em> trust them :-).
<p><strong>Default</strong>
<code>	No host equivalences</code>
<p><strong>Example</strong>
<code>	hosts equiv = /etc/hosts.equiv</code>
<p><a name="include"></a>
<p></p><dt><strong><strong>include (G)</strong></strong><dd>
<p>This allows you to include one config file inside another.  The file
is included literally, as though typed in place.
<p>It takes the standard substitutions, except <a href="smb.conf.5.html#percentu"><strong>%u</strong></a>,
<a href="smb.conf.5.html#percentP"><strong>%P</strong></a> and <a href="smb.conf.5.html#percentS"><strong>%S</strong></a>.
<p><a name="inheritpermissions"></a>
<p></p><dt><strong><strong>inherit permissions (S)</strong></strong><dd>
<p>The permissions on new files and directories are normally governed by
<a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>,
<a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a>,
<a href="smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> and
<a href="smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a>
but the boolean inherit permissions parameter overrides this.
<p>New directories inherit the mode of the parent directory,
including bits such as setgid.
<p>New files inherit their read/write bits from the parent directory.
Their execute bits continue to be determined by
<a href="smb.conf.5.html#maparchive"><strong>"map archive"</strong></a>,
<a href="smb.conf.5.html#maphidden"><strong>"map hidden"</strong></a> and
<a href="smb.conf.5.html#mapsystem"><strong>"map system"</strong></a> as usual.
<p>Note that the setuid bit is *never* set via inheritance
(the code explicitly prohibits this).
<p>This can be particularly useful on large systems with many users,
perhaps several thousand,
to allow a single <strong>[homes]</strong> share to be used flexibly by each user.
<p>See also <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>, <a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a>,
<a href="smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> and
<a href="smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a>.
<p><strong>Default</strong>
<code>   inherit permissions = no</code>
<p><strong>Example</strong>
<code>   inherit permissions = yes</code>
<p><a name="interfaces"></a>
<p></p><dt><strong><strong>interfaces (G)</strong></strong><dd>
<p>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.
<p>The option takes a list of interface strings. Each string can be in
any of the following forms:
<p><dl>
<li > a network interface name (such as eth0). This may include
     shell-like wildcards so eth* will match any interface starting
     with the substring "eth"
<li > an IP address. In this case the netmask is determined
     from the list of interfaces obtained from the kernel
<li > an IP/mask pair. 
<li > a broadcast/mask pair. 
</dl>
<p>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.
<p>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.
<p>For example, the following line:
<p><code>interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0</code>
<p>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.
<p>See also <a href="smb.conf.5.html#bindinterfacesonly"><strong>"bind interfaces only"</strong></a>.
<p><a name="invalidusers"></a>
<p></p><dt><strong><strong>invalid users (S)</strong></strong><dd>
<p>This is a list of users that should not be allowed to login to this
service. This is really a <em>"paranoid"</em> check to absolutely ensure an
improper setting does not breach your security.
<p>A name starting with a <code>'@'</code> 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.
<p>A name starting with <code>'+'</code> is interpreted only by looking in the
UNIX group database. A name starting with <code>'&amp;'</code> is interpreted only
by looking in the NIS netgroup database (this requires NIS to be
working on your system). The characters <code>'+'</code> and <code>'&amp;'</code> may be
used at the start of the name in either order so the value
<code>"+&amp;group"</code> means check the UNIX group database, followed by the NIS
netgroup database, and the value <code>"&amp;+group"</code> means check the NIS
netgroup database, followed by the UNIX group database (the same as
the <code>'@'</code> prefix).
<p>The current servicename is substituted for
<a href="smb.conf.5.html#percentS"><strong>%S</strong></a>. This is useful in the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a>
section.
<p>See also <a href="smb.conf.5.html#validusers"><strong>"valid users"</strong></a>.
<p><strong>Default:</strong>
<code>	No invalid users</code>
<p><strong>Example:</strong>
<code>	invalid users = root fred admin @wheel</code>
<p><a name="keepalive"></a>
<p></p><dt><strong><strong>keepalive (G)</strong></strong><dd>
<p>The value of the parameter (an integer) represents the number of
seconds between <strong>'keepalive'</strong> 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.
<p>Keepalives should, in general, not be needed if the socket being used
has the SO_KEEPALIVE attribute set on it (see <a href="smb.conf.5.html#socketoptions"><strong>"socket
options"</strong></a>). Basically you should only use this option
if you strike difficulties.
<p><strong>Default:</strong>
<code>	keepalive = 0</code>
<p><strong>Example:</strong>
<code>	keepalive = 60</code>
<p><a name="kerneloplocks"></a>
<p></p><dt><strong><strong>kernel oplocks (G)</strong></strong><dd>
<p>For UNIXs that support kernel based <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a>
(currently only IRIX but hopefully also Linux and FreeBSD soon) this
parameter allows the use of them to be turned on or off.
<p>Kernel oplocks support allows Samba <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a> to be
broken whenever a local UNIX process or NFS operation accesses a file
that <a href="smbd.8.html"><strong>smbd</strong></a> has oplocked. This allows complete
data consistency between SMB/CIFS, NFS and local file access (and is a
<em>very</em> cool feature :-).
<p>This parameter defaults to <em>"On"</em> on systems that have the support,
and <em>"off"</em> on systems that don't. You should never need to touch
this parameter.
<p>See also the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="smb.conf.5.html#level2oplocks"><strong>"level2 oplocks"</strong></a>
parameters.
<p><a name="ldapfilter"></a>
<p></p><dt><strong><strong>ldap filter (G)</strong></strong><dd>
<p>This parameter is part of the <em>EXPERIMENTAL</em> 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 <strong>--with-ldap</strong> option.
<p>This parameter specifies an LDAP search filter used to search for a
user name in the LDAP database. It must contain the string
<a href="smb.conf.5.html#percentU"><strong>%u</strong></a> which will be replaced with the user being
searched for.
<p><strong>Default:</strong>
<code>	empty string.</code>
<p><a name="ldapport"></a>
<p></p><dt><strong><strong>ldap port (G)</strong></strong><dd>
<p>This parameter is part of the <em>EXPERIMENTAL</em> 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 <strong>--with-ldap</strong> option.
<p>This parameter specifies the TCP port number to use to contact
the LDAP server on.
<p><strong>Default:</strong>
<code>	ldap port = 389.</code>
<p><a name="ldaproot"></a>
<p></p><dt><strong><strong>ldap root (G)</strong></strong><dd>
<p>This parameter is part of the <em>EXPERIMENTAL</em> 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 <strong>--with-ldap</strong> option.
<p>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.
<p>See also <a href="smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a>.
<p><strong>Default:</strong>
<code>	empty string (no user defined)</code>
<p><a name="ldaprootpasswd"></a>
<p></p><dt><strong><strong>ldap root passwd (G)</strong></strong><dd>
<p>This parameter is part of the <em>EXPERIMENTAL</em> 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 <strong>--with-ldap</strong> option.
<p>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.
<p><em>BUGS:</em> This parameter should <em>NOT</em> be a readable parameter
in the <strong>smb.conf</strong> file and will be removed once a correct
storage place is found.
<p>See also <a href="smb.conf.5.html#ldaproot"><strong>ldap root</strong></a>.
<p><strong>Default:</strong>
<code>	empty string.</code>
<p><a name="ldapserver"></a>
<p></p><dt><strong><strong>ldap server (G)</strong></strong><dd>
<p>This parameter is part of the <em>EXPERIMENTAL</em> 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 <strong>--with-ldap</strong> option.
<p>This parameter specifies the DNS name of the LDAP server to use
for SMB/CIFS authentication purposes.
<p><strong>Default:</strong>
<code>	ldap server = localhost</code>
<p><a name="ldapsuffix"></a>
<p></p><dt><strong><strong>ldap suffix (G)</strong></strong><dd>
<p>This parameter is part of the <em>EXPERIMENTAL</em> 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 <strong>--with-ldap</strong> option.
<p>This parameter specifies the <code>"dn"</code> or LDAP <em>"distinguished name"</em>
that tells <a href="smbd.8.html"><strong>smbd</strong></a> to start from when searching
for an entry in the LDAP password database.
<p><strong>Default:</strong>
<code>	empty string.</code>
<p><a name="level2oplocks"></a>
<p></p><dt><strong><strong>level2 oplocks (S)</strong></strong><dd>
<p>This parameter (new in Samba 2.0.5) controls whether Samba supports
level2 (read-only) oplocks on a share. In Samba 2.0.5 this parameter
defaults to "False" as the code is new, but will default to "True"
in a later release.
<p>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).
<p>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.
<p>It is recommended that this parameter be turned on to speed access
to shared executables (and also to test the code :-).
<p>For more discussions on level2 oplocks see the CIFS spec.
<p>Currently, if <a href="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> are supported
then level2 oplocks are not granted (even if this parameter is set
to <code>"true"</code>). Note also, the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> parameter must
be set to "true" on this share in order for this parameter to have any
effect.
<p>See also the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> parameters.
<p><strong>Default:</strong>
<code> level2 oplocks = False</code>
<p><strong>Example:</strong>
<code> level2 oplocks = True</code>
<p><a name="lmannounce"></a>
<p></p><dt><strong><strong>lm announce (G)</strong></strong><dd>
<p>This parameter determines if <a href="nmbd.8.html"><strong>nmbd</strong></a> will produce
Lanman announce broadcasts that are needed by <strong>OS/2</strong> clients in order
for them to see the Samba server in their browse list. This parameter
can have three values, <code>"true"</code>, <code>"false"</code>, or <code>"auto"</code>. The
default is <code>"auto"</code>.  If set to <code>"false"</code> Samba will never produce
these broadcasts. If set to <code>"true"</code> Samba will produce Lanman
announce broadcasts at a frequency set by the parameter <a href="smb.conf.5.html#lminterval"><strong>"lm
interval"</strong></a>. If set to <code>"auto"</code> 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 <a href="smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>.
<p>See also <a href="smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>.
<p><strong>Default:</strong>
<code>	lm announce = auto</code>
<p><strong>Example:</strong>
<code>	lm announce = true</code>
<p><a name="lminterval"></a>
<p></p><dt><strong><strong>lm interval (G)</strong></strong><dd>
<p>If Samba is set to produce Lanman announce broadcasts needed by
<strong>OS/2</strong> clients (see the <a href="smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a>
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 <a href="smb.conf.5.html#lmannounce"><strong>"lm
announce"</strong></a> parameter.
<p>See also <a href="smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a>.
<p><strong>Default:</strong>
<code>	lm interval = 60</code>
<p><strong>Example:</strong>
<code>	lm interval = 120</code>
<p><a name="loadprinters"></a>
<p></p><dt><strong><strong>load printers (G)</strong></strong><dd>
<p>A boolean variable that controls whether all printers in the printcap
will be loaded for browsing by default. See the
<a href="smb.conf.5.html#printers"><strong>"printers"</strong></a> section for more details.
<p><strong>Default:</strong>
<code>	load printers = yes</code>
<p><strong>Example:</strong>
<code>	load printers = no</code>
<p><a name="localmaster"></a>
<p></p><dt><strong><strong>local master (G)</strong></strong><dd>
<p>This option allows <a href="nmbd.8.html"><strong>nmbd</strong></a> to try and become a
local master browser on a subnet. If set to False then
<a href="nmbd.8.html"><strong>nmbd</strong></a> 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 <em>become</em> the local master browser on a subnet,
just that <a href="nmbd.8.html"><strong>nmbd</strong></a> will <em>participate</em> in
elections for local master browser.
<p>Setting this value to False will cause <a href="nmbd.8.html"><strong>nmbd</strong></a>
<em>never</em> to become a local master browser.
<p><strong>Default:</strong>
<code>	local master = yes</code>
<p><a name="lockdir"></a>
<p></p><dt><strong><strong>lock dir (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#lockdirectory"><strong>"lock directory"</strong></a>.
<p><a name="lockdirectory"></a>
<p></p><dt><strong><strong>lock directory (G)</strong></strong><dd>
<p>This option specifies the directory where lock files will be placed.
The lock files are used to implement the <a href="smb.conf.5.html#maxconnections"><strong>"max
connections"</strong></a> option.
<p><strong>Default:</strong>
<code>	lock directory = /tmp/samba</code>
<p><strong>Example:</strong>
<code>	lock directory = /usr/local/samba/var/locks</code>
<p><a name="locking"></a>
<p></p><dt><strong><strong>locking (S)</strong></strong><dd>
<p>This controls whether or not locking will be performed by the server
in response to lock requests from the client.
<p>If <code>"locking = no"</code>, all lock and unlock requests will appear to
succeed and all lock queries will indicate that the queried lock is
clear.
<p>If <code>"locking = yes"</code>, real locking will be performed by the server.
<p>This option <em>may</em> be useful for read-only filesystems which <em>may</em>
not need locking (such as cdrom drives), although setting this
parameter of <code>"no"</code> is not really recommended even in this case.
<p>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.
<p><strong>Default:</strong>
<code> 	locking = yes</code>
<p><strong>Example:</strong>
<code> 	locking = no</code>
<p><a name="logfile"></a>
<p></p><dt><strong><strong>log file (G)</strong></strong><dd>
<p>This options allows you to override the name of the Samba log file
(also known as the debug file).
<p>This option takes the standard substitutions, allowing you to have
separate log files for each user or machine.
<p><strong>Example:</strong>
<code>	log file = /usr/local/samba/var/log.%m</code>
<p><a name="loglevel"></a>
<p></p><dt><strong><strong>log level (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a>.
<p><a name="logondrive"></a>
<p></p><dt><strong><strong>logon drive (G)</strong></strong><dd>
<p>This parameter specifies the local path to which the home directory
will be connected (see <a href="smb.conf.5.html#logonhome"><strong>"logon home"</strong></a>) and is only
used by NT Workstations. 
<p>Note that this option is only useful if Samba is set up as a
<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
<p><strong>Example:</strong>
<code>	logon drive = h:</code>
<p><a name="logonhome"></a>
<p></p><dt><strong><strong>logon home (G)</strong></strong><dd>
<p>This parameter specifies the home directory location when a Win95/98 or
NT Workstation logs into a Samba PDC.  It allows you to do 
<p><code>"NET USE H: /HOME"</code>
<p>from a command prompt, for example.
<p>This option takes the standard substitutions, allowing you to have
separate logon scripts for each user or machine.
<p>This parameter can be used with Win9X workstations to ensure that
roaming profiles are stored in a subdirectory of the user's home
directory.  This is done in the following way:
<p><code>"     logon home = \\%L\%U\profile"</code>
<p>This tells Samba to return the above string, with substitutions made
when a client requests the info, generally in a NetUserGetInfo request.
Win9X clients truncate the info to \\server\share when a user does <code>"net use /home"</code>,
but use the whole string when dealing with profiles.
<p>Note that in prior versions of Samba, the <code>"logon path"</code> was returned rather than
<code>"logon home"</code>.  This broke <code>"net use /home"</code> but allowed profiles outside the 
home directory.  The current implementation is correct, and can be used for profiles
if you use the above trick.
<p>Note that this option is only useful if Samba is set up as a
<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
<p><strong>Example:</strong>
<code>	logon home = "\\remote_smb_server\%U"</code>
<p><strong>Default:</strong>
<code>	logon home = "\\%N\%U"</code>
<p><a name="logonpath"></a>
<p></p><dt><strong><strong>logon path (G)</strong></strong><dd>
<p>This parameter specifies the home directory where roaming profiles
(NTuser.dat etc files for Windows NT) are stored.  Contrary to previous 
versions of these manual pages, it has nothing to do with Win 9X roaming
profiles.  To find out how to handle roaming profiles for Win 9X system, see 
the <code>"logon home"</code> parameter.
<p>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 <code>"application data"</code>, (<code>"desktop"</code>, <code>"start menu"</code>,
<code>"network neighborhood"</code>, <code>"programs"</code> and other folders, and their
contents, are loaded and displayed on your Windows NT client.
<p>The share and the path must be readable by the user for the
preferences and directories to be loaded onto the Windows NT
client.  The share must be writeable when the logs in for the first
time, in order that the Windows NT client can create the NTuser.dat
and other directories.
<p>Thereafter, the directories and any of the contents can, if required, be
made read-only.  It is not advisable that the NTuser.dat file be made
read-only - rename it to NTuser.man to achieve the desired effect (a
<em>MAN</em>datory profile). 
<p>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 <code>\\%N\HOMES\profile_path</code> will cause
problems).
<p>This option takes the standard substitutions, allowing you to have
separate logon scripts for each user or machine.
<p>Note that this option is only useful if Samba is set up as a
<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
<p><strong>Default:</strong>
<code> 	logon path = \\%N\%U\profile</code>
<p><strong>Example:</strong>
<code>	logon path = \\PROFILESERVER\HOME_DIR\%U\PROFILE</code>
<p><a name="logonscript"></a>
<p></p><dt><strong><strong>logon script (G)</strong></strong><dd>
<p>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.
<p>The script must be a relative path to the <code>[netlogon]</code> service.  If
the <code>[netlogon]</code> service specifies a <a href="smb.conf.5.html#path"><strong>path</strong></a> of
/usr/local/samba/netlogon, and logon script = STARTUP.BAT, then the
file that will be downloaded is:
<p><code>/usr/local/samba/netlogon/STARTUP.BAT</code>
<p>The contents of the batch file is entirely your choice.  A suggested
command would be to add <code>NET TIME \\SERVER /SET /YES</code>, to force every
machine to synchronize clocks with the same time server.  Another use
would be to add <code>NET USE U: \\SERVER\UTILS</code> for commonly used
utilities, or <code>NET USE Q: \\SERVER\ISO9001_QA</code> for example.
<p>Note that it is particularly important not to allow write access to
the <code>[netlogon]</code> 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.
<p>This option takes the standard substitutions, allowing you to have
separate logon scripts for each user or machine.
<p>Note that this option is only useful if Samba is set up as a
<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
<p><strong>Example:</strong>
<code>	logon script = scripts\%U.bat</code>
<p><a name="lppausecommand"></a>
<p></p><dt><strong><strong>lppause command (S)</strong></strong><dd>
<p>This parameter specifies the command to be executed on the server host
in order to stop printing or spooling a specific print job.
<p>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.
<p>If a <code>"%p"</code> is given then the printername is put in its place. A
<code>"%j"</code> is replaced with the job number (an integer).  On HPUX (see
<a href="smb.conf.5.html#printing"><strong>printing=hpux</strong></a>), if the <code>"-p%p"</code> 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.
<p>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.
<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
<p><strong>Default:</strong>
        Currently no default value is given to this string, unless the
value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>SYSV</code>, in
which case the default is :
<p><code>	lp -i %p-%j -H hold</code>
<p>or if the value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</code>,
then the default is:
<p><code>	qstat -s -j%j -h</code>
<p><strong>Example for HPUX:</strong>
        lppause command = /usr/bin/lpalt %p-%j -p0
<p><a name="lpqcachetime"></a>
<p></p><dt><strong><strong>lpq cache time (G)</strong></strong><dd>
<p>This controls how long lpq info will be cached for to prevent the
<strong>lpq</strong> command being called too often. A separate cache is kept for
each variation of the <strong>lpq</strong> command used by the system, so if you
use different <strong>lpq</strong> commands for different users then they won't
share cache information.
<p>The cache files are stored in <code>/tmp/lpq.xxxx</code> where xxxx is a hash of
the <strong>lpq</strong> command in use.
<p>The default is 10 seconds, meaning that the cached results of a
previous identical <strong>lpq</strong> command will be used if the cached data is
less than 10 seconds old. A large value may be advisable if your
<strong>lpq</strong> command is very slow.
<p>A value of 0 will disable caching completely.
<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	lpq cache time = 10</code>
<p><strong>Example:</strong>
<code>	lpq cache time = 30</code>
<p><a name="lpqcommand"></a>
<p></p><dt><strong><strong>lpq command (S)</strong></strong><dd>
<p>This parameter specifies the command to be executed on the server host
in order to obtain <code>"lpq"</code>-style printer status information.
<p>This command should be a program or script which takes a printer name
as its only parameter and outputs printer status information.
<p>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
<a href="smb.conf.5.html#printing"><strong>"printing ="</strong></a> option.
<p>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.
<p>If a <code>%p</code> is given then the printername is put in its place. Otherwise
it is placed at the end of the command.
<p>Note that it is good practice to include the absolute path in the <strong>lpq
command</strong> as the PATH may not be available to the server.
<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
<p><strong>Default:</strong>
<code>        depends on the setting of printing =</code>
<p><strong>Example:</strong>
<code> 	lpq command = /usr/bin/lpq %p</code>
<p><a name="lpresumecommand"></a>
<p></p><dt><strong><strong>lpresume command (S)</strong></strong><dd>
<p>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.
<p>This command should be a program or script which takes a printer name
and job number to resume the print job. See also the <a href="smb.conf.5.html#lppausecommand"><strong>"lppause
command"</strong></a> parameter.
<p>If a <code>%p</code> is given then the printername is put in its place. A
<code>%j</code> is replaced with the job number (an integer).
<p>Note that it is good practice to include the absolute path in the <strong>lpresume
command</strong> as the PATH may not be available to the server.
<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
<p><strong>Default:</strong>
<p>Currently no default value is given to this string, unless the
value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>SYSV</code>, in
which case the default is :
<p><code>	lp -i %p-%j -H resume</code>
<p>or if the value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</code>,
then the default is:
<p><code>	qstat -s -j%j -r</code>
<p><strong>Example for HPUX:</strong>
<code>        lpresume command = /usr/bin/lpalt %p-%j -p2</code>
<p><a name="lprmcommand"></a>
<p></p><dt><strong><strong>lprm command (S)</strong></strong><dd>
<p>This parameter specifies the command to be executed on the server host
in order to delete a print job.
<p>This command should be a program or script which takes a printer name
and job number, and deletes the print job.
<p>If a <code>%p</code> is given then the printername is put in its place. A
<code>%j</code> is replaced with the job number (an integer).
<p>Note that it is good practice to include the absolute path in the
<strong>lprm command</strong> as the PATH may not be available to the server.
<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	depends on the setting of "printing ="</code>
<p><strong>Example 1:</strong>
<code> 	lprm command = /usr/bin/lprm -P%p %j</code>
<p><strong>Example 2:</strong>
<code> 	lprm command = /usr/bin/cancel %p-%j</code>
<p><a name="machinepasswordtimeout"></a>
<p></p><dt><strong><strong>machine password timeout (G)</strong></strong><dd>
<p>If a Samba server is a member of an Windows NT Domain (see the
<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter) then
periodically a running <a href="smbd.8.html"><strong>smbd</strong></a> process will try and
change the <strong>MACHINE ACCOUNT PASWORD</strong> stored in the file called
<code>&lt;Domain&gt;.&lt;Machine&gt;.mac</code> where <code>&lt;Domain&gt;</code> is the name of the
Domain we are a member of and <code>&lt;Machine&gt;</code> is the primary
<a href="smb.conf.5.html#netbiosname"><strong>"NetBIOS name"</strong></a> of the machine
<a href="smbd.8.html"><strong>smbd</strong></a> 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.
<p>See also <a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>, and the
<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter.
<p><strong>Default:</strong>
<code>	machine password timeout = 604800</code>
<p><a name="magicoutput"></a>
<p></p><dt><strong><strong>magic output (S)</strong></strong><dd>
<p>This parameter specifies the name of a file which will contain output
created by a magic script (see the <a href="smb.conf.5.html#magicscript"><strong>"magic
script"</strong></a> parameter below).
<p>Warning: If two clients use the same <a href="smb.conf.5.html#magicscript"><strong>"magic
script"</strong></a> in the same directory the output file content
is undefined.
<p><strong>Default:</strong>
<code> 	magic output = &lt;magic script name&gt;.out</code>
<p><strong>Example:</strong>
<code> 	magic output = myfile.txt</code>
<p><a name="magicscript"></a>
<p></p><dt><strong><strong>magic script (S)</strong></strong><dd>
<p>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.
<p>Scripts executed in this way will be deleted upon completion,
permissions permitting.
<p>If the script generates output, output will be sent to the file
specified by the <a href="smb.conf.5.html#magicoutput"><strong>"magic output"</strong></a> parameter (see
above).
<p>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 <em>"as is"</em> on the host,
which for some hosts and some shells will require filtering at the DOS
end.
<p>Magic scripts are <em>EXPERIMENTAL</em> and should <em>NOT</em> be relied upon.
<p><strong>Default:</strong>
<code>	None. Magic scripts disabled.</code>
<p><strong>Example:</strong>
<code> 	magic script = user.csh</code>
<p><a name="manglecase"></a>
<p></p><dt><strong><strong>mangle case (S)</strong></strong><dd>
<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a>.
<p><a name="manglelocks"></a>
<p></p><dt><strong><strong>mangle locks (S)</strong></strong><dd>
<p>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.
<p><a name="mangledmap"></a>
<p></p><dt><strong><strong>mangled map (S)</strong></strong><dd>
<p>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 <code>".html"</code> for HTML files, whereas under
Windows/DOS <code>".htm"</code> is more commonly used.
<p>So to map <code>"html"</code> to <code>"htm"</code> you would use:
<p><code>  mangled map = (*.html *.htm)</code>
<p>One very useful case is to remove the annoying <code>";1"</code> off the ends
of filenames on some CDROMS (only visible under some UNIXs). To do
this use a map of (*;1 *).
<p><strong>default:</strong>
<code>	no mangled map</code>
<p><strong>Example:</strong>
<code>	mangled map = (*;1 *)</code>
<p><a name="manglednames"></a>
<p></p><dt><strong><strong>mangled names (S)</strong></strong><dd>
<p>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.
<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for details
on how to control the mangling process.
<p>If mangling is used then the mangling algorithm is as follows:
<p><dl>
<p><li > The first (up to) five alphanumeric characters before the
rightmost dot of the filename are preserved, forced to upper case, and
appear as the first (up to) five characters of the mangled name.
<p><li > A tilde <code>"~"</code> 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.
<p>Note that the character to use may be specified using the
<a href="smb.conf.5.html#manglingchar"><strong>"mangling char"</strong></a> option, if you don't like
<code>'~'</code>.
<p><li > The first three alphanumeric characters of the final extension
are preserved, forced to upper case and appear as the extension of the
mangled name. The final extension is defined as that part of the
original filename after the rightmost dot. If there are no dots in the
filename, the mangled name will have no extension (except in the case
of <a href="smb.conf.5.html#hidefiles"><strong>"hidden files"</strong></a> - see below).
<p><li > Files whose UNIX name begins with a dot will be presented as DOS
hidden files. The mangled name will be created as for other filenames,
but with the leading dot removed and <code>"___"</code> as its extension regardless
of actual original extension (that's three underscores).
<p></dl>
<p>The two-digit hash value consists of upper case alphanumeric
characters.
<p>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.
<p>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.
<p><strong>Default:</strong>
<code> 	mangled names = yes</code>
<p><strong>Example:</strong>
<code> 	mangled names = no</code>
<p><a name="manglingchar"></a>
<p></p><dt><strong><strong>mangling char (S)</strong></strong><dd>
<p>This controls what character is used as the <em>"magic"</em> character in
<a href="smb.conf.5.html#manglednames"><strong>name mangling</strong></a>. The default is a <code>'~'</code> but
this may interfere with some software. Use this option to set it to
whatever you prefer.
<p><strong>Default:</strong>
<code> 	mangling char = ~</code>
<p><strong>Example:</strong>
<code> 	mangling char = ^</code>
<p><a name="mangledstack"></a>
<p></p><dt><strong><strong>mangled stack (G)</strong></strong><dd>
<p>This parameter controls the number of mangled names that should be
cached in the Samba server <a href="smbd.8.html"><strong>smbd</strong></a>.
<p>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).
<p>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).
<p>It is not possible to absolutely guarantee correct long file names, so
be prepared for some surprises!
<p><strong>Default:</strong>
<code> 	mangled stack = 50</code>
<p><strong>Example:</strong>
<code> 	mangled stack = 100</code>
<p><a name="maparchive"></a>
<p></p><dt><strong><strong>map archive (S)</strong></strong><dd>
<p>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...
<p>Note that this requires the <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
parameter to be set such that owner execute bit is not masked out
(i.e. it must include 100). See the parameter <a href="smb.conf.5.html#createmask"><strong>"create
mask"</strong></a> for details.
<p><strong>Default:</strong>
<code>      map archive = yes</code>
<p><strong>Example:</strong>
<code>      map archive = no</code>
<p><a name="maphidden"></a>
<p></p><dt><strong><strong>map hidden (S)</strong></strong><dd>
<p>This controls whether DOS style hidden files should be mapped to the
UNIX world execute bit.
<p>Note that this requires the <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be
set such that the world execute bit is not masked out (i.e. it must
include 001). See the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
for details.
<p><strong>Default:</strong>
<code> 	map hidden = no</code>
<p><strong>Example:</strong>
<code> 	map hidden = yes</code>
<p><a name="mapsystem"></a>
<p></p><dt><strong><strong>map system (S)</strong></strong><dd>
<p>This controls whether DOS style system files should be mapped to the
UNIX group execute bit.
<p>Note that this requires the <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be
set such that the group execute bit is not masked out (i.e. it must
include 010). See the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
for details.
<p><strong>Default:</strong>
<code> 	map system = no</code>
<p><strong>Example:</strong>
<code> 	map system = yes</code>
<p><a name="maptoguest"></a>
<p></p><dt><strong><strong>map to guest (G)</strong></strong><dd>
<p>This parameter is only useful in <a href="smb.conf.5.html#security"><strong>security</strong></a> modes
other than <a href="smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> - i.e. user,
server, and domain.
<p>This parameter can take three different values, which tell
<a href="smbd.8.html"><strong>smbd</strong></a> what to do with user login requests that
don't match a valid UNIX user in some way.
<p>The three settings are :
<p><dl>
<p><li > <strong>"Never"</strong> - Means user login requests with an invalid password
are rejected. This is the default.
<p><li > <strong>"Bad User"</strong> - Means user logins with an invalid password are
rejected, unless the username does not exist, in which case it is
treated as a guest login and mapped into the <a href="smb.conf.5.html#guestaccount"><strong>"guest
account"</strong></a>.
<p><li > <strong>"Bad Password"</strong> - Means user logins with an invalid
password are treated as a guest login and mapped into the
<a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. Note that this can
cause problems as it means that any user incorrectly typing their
password will be silently logged on a <strong>"guest"</strong> - and 
will not know the reason they cannot access files they think
they should - there will have been no message given to them
that they got their password wrong. Helpdesk services will
<em>*hate*</em> you if you set the <strong>"map to guest"</strong> parameter
this way :-).
<p></dl>
<p>Note that this parameter is needed to set up <strong>"Guest"</strong> share
services when using <a href="smb.conf.5.html#security"><strong>security</strong></a> modes other than
share. This is because in these modes the name of the resource being
requested is <em>*not*</em> 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 <strong>"Guest"</strong> shares.
<p>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.
<p><strong>Default:</strong>
<code>	map to guest = Never</code>
  <strong>Example</strong>:
<code>	map to guest = Bad User</code>
<p><a name="maxconnections"></a>
<p></p><dt><strong><strong>max connections (S)</strong></strong><dd>
<p>This option allows the number of simultaneous connections to a service
to be limited. If <strong>"max connections"</strong> 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.
<p>Record lock files are used to implement this feature. The lock files
will be stored in the directory specified by the <a href="smb.conf.5.html#lockdirectory"><strong>"lock
directory"</strong></a> option.
<p><strong>Default:</strong>
<code>	max connections = 0</code>
<p><strong>Example:</strong>
<code>	max connections = 10</code>
<p><a name="maxdisksize"></a>
<p></p><dt><strong><strong>max disk size (G)</strong></strong><dd>
<p>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.
<p>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 <strong>"max disk size"</strong>.
<p>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.
<p>A <strong>"max disk size"</strong> of 0 means no limit.
<p><strong>Default:</strong>
<code>	max disk size = 0</code>
<p><strong>Example:</strong>
<code>	max disk size = 1000</code>
<p><a name="maxlogsize"></a>
<p></p><dt><strong><strong>max log size (G)</strong></strong><dd>
<p>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 <code>".old"</code> extension.
<p>A size of 0 means no limit.
<p><strong>Default:</strong>
<code>	max log size = 5000</code>
<p><strong>Example:</strong>
<code> 	max log size = 1000</code>
<p><a name="maxmux"></a>
<p></p><dt><strong><strong>max mux (G)</strong></strong><dd>
<p>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.
<p><strong>Default:</strong>
<code>	max mux = 50</code>
<p><a name="maxopenfiles"></a>
<p></p><dt><strong><strong>max open files (G)</strong></strong><dd>
<p>This parameter limits the maximum number of open files that one
<a href="smbd.8.html"><strong>smbd</strong></a> 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.
<p>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.
<p><strong>Default:</strong>
<code>	max open files = 10000</code>
<p><a name="maxpacket"></a>
<p></p><dt><strong><strong>max packet (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#packetsize"><strong>"packet size"</strong></a>.
<p><a name="maxttl"></a>
<p></p><dt><strong><strong>max ttl (G)</strong></strong><dd>
<p>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> what the default 'time
to live' of NetBIOS names should be (in seconds) when
<a href="nmbd.8.html"><strong>nmbd</strong></a> 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.
<p><strong>Default:</strong>
<code>	max ttl = 259200</code>
<p><a name="maxwinsttl"></a>
<p></p><dt><strong><strong>max wins ttl (G)</strong></strong><dd>
<p>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS
server <a href="smb.conf.5.html#winssupport"><strong>(wins support =true)</strong></a> what the maximum
'time to live' of NetBIOS names that <a href="nmbd.8.html"><strong>nmbd</strong></a> will
grant will be (in seconds). You should never need to change this
parameter.  The default is 6 days (518400 seconds).
<p>See also the <a href="smb.conf.5.html#minwinsttl"><strong>"min wins ttl"</strong></a> parameter.
<p><strong>Default:</strong>
<code>        max wins ttl = 518400</code>
<p><a name="maxxmit"></a>
<p></p><dt><strong><strong>max xmit (G)</strong></strong><dd>
<p>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.
<p><strong>Default:</strong>
<code>	max xmit = 65535</code>
<p><strong>Example:</strong>
<code> 	max xmit = 8192</code>
<p><a name="messagecommand"></a>
<p></p><dt><strong><strong>message command (G)</strong></strong><dd>
<p>This specifies what command to run when the server receives a WinPopup
style message.
<p>This would normally be a command that would deliver the message
somehow. How this is to be done is up to your imagination.
<p>An example is:
<p><code>   message command = csh -c 'xedit %s;rm %s' &amp;</code>
<p>This delivers the message using <strong>xedit</strong>, then removes it
afterwards. <em>NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN
IMMEDIATELY</em>. That's why I have the <code>'&amp;'</code> on the end. If it doesn't
return immediately then your PCs may freeze when sending messages
(they should recover after 30secs, hopefully).
<p>All messages are delivered as the global guest user. The command takes
the standard substitutions, although <a href="smb.conf.5.html#percentu"><strong>%u</strong></a> won't work
(<a href="smb.conf.5.html#percentU"><strong>%U</strong></a> may be better in this case).
<p>Apart from the standard substitutions, some additional ones apply. In
particular:
<p><dl>
<p><li > <code>"%s"</code> = the filename containing the message.
<p><li > <code>"%t"</code> = the destination that the message was sent to (probably the server
name).
<p><li > <code>"%f"</code> = who the message is from.
<p></dl>
<p>You could make this command send mail, or whatever else takes your
fancy. Please let us know of any really interesting ideas you have.
<p>Here's a way of sending the messages as mail to root:
<p><code>message command = /bin/mail -s 'message from %f on %m' root &lt; %s; rm %s</code>
<p>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.
<p>If you want to silently delete it then try:
<p><code>"message command = rm %s"</code>.
<p><strong>Default:</strong>
<code>	no message command</code>
<p><strong>Example:</strong>
<code>        message command = csh -c 'xedit %s;rm %s' &amp;</code>
<p><a name="minprintspace"></a>
<p></p><dt><strong><strong>min print space (S)</strong></strong><dd>
<p>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.
<p>See also the <a href="smb.conf.5.html#printing"><strong>printing</strong></a> parameter.
<p><strong>Default:</strong>
<code>	min print space = 0</code>
<p><strong>Example:</strong>
<code>	min print space = 2000</code>
<p><a name="minpasswdlength"></a>
<p></p><dt><strong><strong>min passwd length (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#minpasswordlength"><strong>"min password length"</strong></a>.
<p><a name="minpasswordlength"></a>
<p></p><dt><strong><strong>min password length (G)</strong></strong><dd>
<p>This option sets the minimum length in characters of a plaintext password
than smbd will accept when performing UNIX password changing.
<p>See also <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>,
<a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and <a href="smb.conf.5.html#passwdchatdebug"><strong>"passwd chat
debug"</strong></a>.
<p><strong>Default:</strong>
<code>	min password length = 5</code>
<p><a name="minwinsttl"></a>
<p></p><dt><strong><strong>min wins ttl (G)</strong></strong><dd>
<p>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS
server <a href="smb.conf.5.html#winssupport"><strong>(wins support = true)</strong></a> what the minimum
'time to live' of NetBIOS names that <a href="nmbd.8.html"><strong>nmbd</strong></a> will
grant will be (in seconds). You should never need to change this
parameter.  The default is 6 hours (21600 seconds).
<p><strong>Default:</strong>
<code>	min wins ttl = 21600</code>
<p><a name="nameresolveorder"></a>
<p></p><dt><strong><strong>name resolve order (G)</strong></strong><dd>
<p>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.
<p>The options are :"lmhosts", "host", "wins" and "bcast". They cause
names to be resolved as follows :
<p><dl>
<p><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file.
If the line in lmhosts has no name type attached to the NetBIOS
name (see the <a href="lmhosts.5.html"><strong>lmhosts (5)</strong></a> for details) then
any name type matches for lookup.
<p><li > <strong>host</strong> : Do a standard host name to IP address resolution,
using the system /etc/hosts, NIS, or DNS lookups. This method of name
resolution is operating system depended for instance on IRIX or
Solaris this may be controlled by the <em>/etc/nsswitch.conf</em> file).
Note that this method is only used if the NetBIOS name type being
queried is the 0x20 (server) name type, otherwise it is ignored.
<p><li > <strong>wins</strong> : Query a name with the IP address listed in the
<a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a> parameter. If no WINS server has
been specified this method will be ignored.
<p><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces
listed in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter. This is the
least reliable of the name resolution methods as it depends on the
target host being on a locally connected subnet.
<p></dl>
<p><strong>Default:</strong>
<code>	name resolve order = lmhosts host wins bcast</code>
<p><strong>Example:</strong>
<code>	name resolve order = lmhosts bcast host</code>
<p>This will cause the local lmhosts file to be examined first, followed
by a broadcast attempt, followed by a normal system hostname lookup.
<p><a name="netbiosaliases"></a>
<p></p><dt><strong><strong>netbios aliases (G)</strong></strong><dd>
<p>This is a list of NetBIOS names that <a href="nmbd.8.html"><strong>nmbd</strong></a> 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 <a href="smb.conf.5.html#localmaster"><strong>browse server</strong></a> or
<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a> 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.
<p>See also <a href="smb.conf.5.html#netbiosname"><strong>"netbios name"</strong></a>.
<p><strong>Default:</strong>
<code>	empty string (no additional names)</code>
<p><strong>Example:</strong>
<code>	netbios aliases = TEST TEST1 TEST2</code>
<p><a name="netbiosname"></a>
<p></p><dt><strong><strong>netbios name (G)</strong></strong><dd>
<p>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 <a href="smb.conf.5.html#localmaster"><strong>browse server</strong></a> or
<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a> this name (or the first component
of the hosts DNS name) will be the name that these services are
advertised under.
<p>See also <a href="smb.conf.5.html#netbiosaliases"><strong>"netbios aliases"</strong></a>.
<p><strong>Default:</strong>
<code>	Machine DNS name.</code>
<p><strong>Example:</strong>
<code>	netbios name = MYNAME</code>
<p><a name="netbiosscope"></a>
<p></p><dt><strong><strong>netbios scope (G)</strong></strong><dd>
<p>This sets the NetBIOS scope that Samba will operate under. This should
not be set unless every machine on your LAN also sets this value.
<p><a name="nishomedir"></a>
<p></p><dt><strong><strong>nis homedir (G)</strong></strong><dd>
<p>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. 
<p>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.
<p>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
<a href="smb.conf.5.html#homedirmap"><strong>"homedir map"</strong></a> and return the server listed
there.
<p>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
<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
<p><strong>Default:</strong>
<code>	nis homedir = false</code>
<p><strong>Example:</strong>
<code>	nis homedir = true</code>
<p><a name="ntaclsupport"></a>
<p></p><dt><strong><strong>nt acl support (G)</strong></strong><dd>
<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a>
will attempt to map UNIX permissions into Windows NT access control lists.
<p><strong>Default:</strong>
<code>	nt acl support = yes</code>
<p><strong>Example:</strong>
<code>	nt acl support = no</code>
<p><a name="ntpipesupport"></a>
<p></p><dt><strong><strong>nt pipe support (G)</strong></strong><dd>
<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a>
will allow Windows NT clients to connect to the NT SMB specific
<code>IPC$</code> pipes. This is a developer debugging option and can be left
alone.
<p><strong>Default:</strong>
<code>	nt pipe support = yes</code>
<p><a name="ntsmbsupport"></a>
<p></p><dt><strong><strong>nt smb support (G)</strong></strong><dd>
<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a>
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 <code>"no"</code>. This is still
being investigated. If this option is set to <code>"no"</code> 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.
<p><strong>Default:</strong>
<code>	nt support = yes</code>
<p><a name="nullpasswords"></a>
<p></p><dt><strong><strong>null passwords (G)</strong></strong><dd>
<p>Allow or disallow client access to accounts that have null passwords. 
<p>See also <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a>.
<p><strong>Default:</strong>
<code>	null passwords = no</code>
<p><strong>Example:</strong>
<code>	null passwords = yes</code>
<p><a name="olelockingcompatibility"></a>
<p></p><dt><strong><strong>ole locking compatibility (G)</strong></strong><dd>
<p>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 <code>"no"</code> means you trust your UNIX lock manager to handle such cases
correctly.
<p><strong>Default:</strong>
<code>	ole locking compatibility = yes</code>
<p><strong>Example:</strong>
<code>	ole locking compatibility = no</code>
<p><a name="onlyguest"></a>
<p></p><dt><strong><strong>only guest (S)</strong></strong><dd>
<p>A synonym for <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a>.
<p><a name="onlyuser"></a>
<p></p><dt><strong><strong>only user (S)</strong></strong><dd>
<p>This is a boolean option that controls whether connections with
usernames not in the <a href="smb.conf.5.html#user"><strong>user=</strong></a> list will be allowed. By
default this option is disabled so a client can supply a username to
be used by the server.
<p>Note that this also means Samba won't try to deduce usernames from the
service name. This can be annoying for the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a>
section. To get around this you could use "<a href="smb.conf.5.html#user"><strong>user</strong></a> =
<a href="smb.conf.5.html#percentS"><strong>%S</strong></a>" which means your <a href="smb.conf.5.html#user"><strong>"user"</strong></a> list
will be just the service name, which for home directories is the name
of the user.
<p>See also the <a href="smb.conf.5.html#user"><strong>user</strong></a> parameter.
<p><strong>Default:</strong>
<code>	only user = False</code>
<p><strong>Example:</strong>
<code>	only user = True</code>
<p><a name="oplocks"></a>
<p></p><dt><strong><strong>oplocks (S)</strong></strong><dd>
<p>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.
<p>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 <a href="smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a> parameter
for details.
<p>See also the <a href="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> and
<a href="smb.conf.5.html#level2oplocks"><strong>"level2 oplocks"</strong></a> parameters.
<p><strong>Default:</strong>
<code>	oplocks = True</code>
<p><strong>Example:</strong>
<code>	oplocks = False</code>
<p><a name="oplockbreakwaittime"></a>
<p></p><dt><strong><strong>oplock break wait time (G)</strong></strong><dd>
<p>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.
<p><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA
OPLOCK CODE</em>.
<p><strong>Default:</strong>
<code>	oplock break wait time = 10</code>
<p><a name="oplockcontentionlimit"></a>
<p></p><dt><strong><strong>oplock contention limit (S)</strong></strong><dd>
<p>This is a <em>very</em> advanced <a href="smbd.8.html"><strong>smbd</strong></a> tuning option to improve
the efficiency of the granting of oplocks under multiple client contention for the same file.
<p>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 <a href="smbd.8.html"><strong>smbd</strong></a> to
behave in a similar way to Windows NT.
<p><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA
OPLOCK CODE</em>.
<p><strong>Default:</strong>
<code> oplock contention limit = 2</code>
<p><a name="oslevel"></a>
<p></p><dt><strong><strong>os level (G)</strong></strong><dd>
<p>This integer value controls what level Samba advertises itself as for
browse elections. The value of this parameter determines whether
<a href="nmbd.8.html"><strong>nmbd</strong></a> has a chance of becoming a local master
browser for the <a href="smb.conf.5.html#workgroup"><strong>WORKGROUP</strong></a> in the local broadcast
area. The default is zero, which means <a href="nmbd.8.html"><strong>nmbd</strong></a> will
lose elections to Windows machines. See BROWSING.txt in the Samba
docs/ directory for details.
<p><strong>Default:</strong>
<code>	os level = 20</code>
<p><strong>Example:</strong>
<code>	os level = 65    ; This will win against any NT Server</code>
<p><a name="packetsize"></a>
<p></p><dt><strong><strong>packet size (G)</strong></strong><dd>
<p>This is a deprecated parameter that has no effect on the current
Samba code. It is left in the parameter list to prevent breaking
old <strong>smb.conf</strong> files.
<p><a name="panicaction"></a>
<p></p><dt><strong><strong>panic action (G)</strong></strong><dd>
<p>This is a Samba developer option that allows a system command to be
called when either <a href="smbd.8.html"><strong>smbd</strong></a> or
<a href="nmbd.8.html"><strong>nmbd</strong></a> crashes. This is usually used to draw
attention to the fact that a problem occurred.
<p><strong>Default:</strong>
<code>	panic action = &lt;empty string&gt;</code>
<p><a name="passwdchat"></a>
<p></p><dt><strong><strong>passwd chat (G)</strong></strong><dd>
<p>This string controls the <em>"chat"</em> conversation that takes places
between <a href="smbd.8.html"><strong>smbd</strong></a> and the local password changing
program to change the users password. The string describes a sequence
of response-receive pairs that <a href="smbd.8.html"><strong>smbd</strong></a> uses to
determine what to send to the <a href="smb.conf.5.html#passwdprogram"><strong>passwd</strong></a> program
and what to expect back. If the expected output is not received then
the password is not changed.
<p>This chat sequence is often quite site specific, depending on what
local methods are used for password control (such as NIS etc).
<p>The string can contain the macros <code>"%o"</code> and <code>"%n"</code> which are
substituted for the old and new passwords respectively. It can also
contain the standard macros <code>"\n"</code>, <code>"\r"</code>, <code>"\t"</code> and <code>"\s"</code>
to give line-feed, carriage-return, tab and space.
<p>The string can also contain a <code>'*'</code> which matches any sequence of
characters.
<p>Double quotes can be used to collect strings with spaces in them into
a single string.
<p>If the send string in any part of the chat sequence is a fullstop
<code>"."</code>  then no string is sent. Similarly, is the expect string is a
fullstop then no string is expected.
<p>Note that if the <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>
parameter is set to true, then this sequence is called <em>*AS ROOT*</em>
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 <code>""</code> (the empty string).
<p>See also <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>,
<a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and <a href="smb.conf.5.html#passwdchatdebug"><strong>"passwd chat
debug"</strong></a>.
<p><strong>Example:</strong> 
<pre>
 passwd chat = "*Enter OLD password*" %o\n "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*"

</pre>

<p><strong>Default:</strong>
<pre>
       passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed*
</pre>

<p><a name="passwdchatdebug"></a>
<p></p><dt><strong><strong>passwd chat debug (G)</strong></strong><dd>
<p>This boolean specifies if the passwd chat script parameter is run in
<code>"debug"</code> mode. In this mode the strings passed to and received from
the passwd chat are printed in the <a href="smbd.8.html"><strong>smbd</strong></a> log with
a <a href="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> of 100. This is a dangerous
option as it will allow plaintext passwords to be seen in the
<a href="smbd.8.html"><strong>smbd</strong></a> log. It is available to help Samba admins
debug their <a href="smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a> scripts when calling
the <a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and should be turned off
after this has been done. This parameter is off by default.
<p>See also <a href="smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a>, <a href="smb.conf.5.html#passwdprogram"><strong>"passwd
program"</strong></a>.
<p><strong>Example:</strong>
<code>     passwd chat debug = True</code>
<p><strong>Default:</strong>
<code>     passwd chat debug = False</code>
<p><a name="passwdprogram"></a>
<p></p><dt><strong><strong>passwd program (G)</strong></strong><dd>
<p>The name of a program that can be used to set UNIX user passwords.
Any occurrences of <a href="smb.conf.5.html#percentu"><strong>%u</strong></a> will be replaced with the
user name. The user name is checked for existence before calling the
password changing program.
<p>Also note that many passwd programs insist in <em>"reasonable"</em>
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.
<p><em>Note</em> that if the <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>
parameter is set to <code>"True"</code> then this program is called <em>*AS
ROOT*</em> before the SMB password in the
<a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file is changed. If this UNIX
password change fails, then <a href="smbd.8.html"><strong>smbd</strong></a> will fail to
change the SMB password also (this is by design).
<p>If the <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> parameter is
set this parameter <em>MUST USE ABSOLUTE PATHS</em> for <em>ALL</em> programs
called, and must be examined for security implications. Note that by
default <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> is set to
<code>"False"</code>.
<p>See also <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>.
<p><strong>Default:</strong>
<code>	passwd program = /bin/passwd</code>
<p><strong>Example:</strong>
<code>	passwd program = /sbin/passwd %u</code>
<p><a name="passwordlevel"></a>
<p></p><dt><strong><strong>password level (G)</strong></strong><dd>
<p>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!
<p>This parameter defines the maximum number of characters that may be
upper case in passwords.
<p>For example, say the password given was <code>"FRED"</code>. If <strong>password
level</strong> is set to 1, the following combinations would be tried if
<code>"FRED"</code> failed:
<p><code>"Fred"</code>, <code>"fred"</code>, <code>"fRed"</code>, <code>"frEd"</code>, <code>"freD"</code>
<p>If <strong>password level</strong> was set to 2, the following combinations would
also be tried: 
<p><code>"FRed"</code>, <code>"FrEd"</code>, <code>"FreD"</code>, <code>"fREd"</code>, <code>"fReD"</code>,
<code>"frED"</code>, <code>..</code>
<p>And so on.
<p>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.
<p>A value of zero will cause only two attempts to be made - the password
as is and the password in all-lower case.
<p><strong>Default:</strong>
<code>	password level = 0</code>
<p><strong>Example:</strong>
<code> 	password level = 4</code>
<p><a name="passwordserver"></a>
<p></p><dt><strong><strong>password server (G)</strong></strong><dd>
<p>By specifying the name of another SMB server (such as a WinNT box)
with this option, and using <a href="smb.conf.5.html#security"><strong>"security = domain"</strong></a> or
<a href="smb.conf.5.html#security"><strong>"security = server"</strong></a> you can get Samba to do all
its username/password validation via a remote server.
<p>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 <strong>smb.conf</strong> file.
<p>The name of the password server is looked up using the parameter
<a href="smb.conf.5.html#nameresolveorder"><strong>"name resolve order="</strong></a> and so may resolved
by any method and order described in that parameter.
<p>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. 
<p>NOTE: Using a password server means your UNIX box (running Samba) is
only as secure as your password server. <em>DO NOT CHOOSE A PASSWORD
SERVER THAT YOU DON'T COMPLETELY TRUST</em>.
<p>Never point a Samba server at itself for password serving. This will
cause a loop and could lock up your Samba server!
<p>The name of the password server takes the standard substitutions, but
probably the only useful one is <a href="smb.conf.5.html#percentm"><strong>%m</strong></a>, 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!
<p>If the <a href="smb.conf.5.html#security"><strong>"security"</strong></a> parameter is set to
<strong>"domain"</strong>, then the list of machines in this option must be a list
of Primary or Backup Domain controllers for the
<a href="smb.conf.5.html#workgroup"><strong>Domain</strong></a> or the character <code>*</code>, 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
<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> is that if you list
several hosts in the <strong>"password server"</strong> option then
<a href="smbd.8.html"><strong>smbd</strong></a> will try each in turn till it finds one
that responds. This is useful in case your primary server goes down.
<p>If the <strong>"password server"</strong> option is set to the character <code>*</code>,
then Samba will attempt to auto-locate the Primary or Backup Domain controllers
to authenticate against by doing a query for the name <code>WORKGROUP&lt;1C&gt;</code>
and then contacting each server returned in the list of IP addresses
from the <a href="smb.conf.5.html#nameresolveorder"><strong>name resolution</strong></a> source.
<p>If the <a href="smb.conf.5.html#security"><strong>"security"</strong></a> parameter is set to
<a href="smb.conf.5.html#securityequalserver"><strong>"server"</strong></a>, then there are different
restrictions that <a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>
doesn't suffer from:
<p><dl>
<p><li > You may list several password servers in the <strong>"password server"</strong>
parameter, however if an <a href="smbd.8.html"><strong>smbd</strong></a> makes a connection
to a password server, and then the password server fails, no more
users will be able to be authenticated from this
<a href="smbd.8.html"><strong>smbd</strong></a>.  This is a restriction of the SMB/CIFS
protocol when in <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode
and cannot be fixed in Samba.
<p><li > If you are using a Windows NT server as your password server then
you will have to ensure that your users are able to login from the
Samba server, as when in
<a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode the network
logon will appear to come from there rather than from the users
workstation.
<p></dl>
<p>See also the <a href="smb.conf.5.html#security"><strong>"security"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	password server = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	password server = NT-PDC, NT-BDC1, NT-BDC2</code>
<p><strong>Example:</strong>
<code>	password server = *</code>
<p><a name="path"></a>
<p></p><dt><strong><strong>path (S)</strong></strong><dd>
<p>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.
<p>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.
<p>Any occurrences of <a href="smb.conf.5.html#percentu"><strong>%u</strong></a> in the path will be replaced
with the UNIX username that the client is using on this
connection. Any occurrences of <a href="smb.conf.5.html#percentm"><strong>%m</strong></a> 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.
<p>Note that this path will be based on <a href="smb.conf.5.html#rootdir"><strong>"root dir"</strong></a> if
one was specified.
<p><strong>Default:</strong>
<code>	none</code>
<p><strong>Example:</strong>
<code>	path = /home/fred</code>
<p><a name="postexec"></a>
<p></p><dt><strong><strong>postexec (S)</strong></strong><dd>
<p>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.
<p>An interesting example may be do unmount server resources:
<p><code>postexec = /etc/umount /cdrom</code>
<p>See also <a href="smb.conf.5.html#preexec"><strong>preexec</strong></a>.
<p><strong>Default:</strong>
<code>      none (no command executed)</code>
<p><strong>Example:</strong>
<code>      postexec = echo "%u disconnected from %S from %m (%I)" &gt;&gt; /tmp/log</code>
<p><a name="postscript"></a>
<p></p><dt><strong><strong>postscript (S)</strong></strong><dd>
<p>This parameter forces a printer to interpret the print files as
postscript. This is done by adding a <code>%!</code> to the start of print output.
<p>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.
<p><strong>Default:</strong>
<code>	postscript = False</code>
<p><strong>Example:</strong>
<code>	postscript = True</code>
<p><a name="preexec"></a>
<p></p><dt><strong><strong>preexec (S)</strong></strong><dd>
<p>This option specifies a command to be run whenever the service is
connected to. It takes the usual substitutions.
<p>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:
<p><pre>

	preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' &amp;

</pre>

<p>Of course, this could get annoying after a while :-)
<p>See also <a href="smb.conf.5.html#preexecclose"><strong>preexec close</strong></a> and <a href="smb.conf.5.html#postexec"><strong>postexec</strong></a>.
<p><strong>Default:</strong>
<code>	none (no command executed)</code>
<p><strong>Example:</strong>
<code>        preexec = echo \"%u connected to %S from %m (%I)\" &gt;&gt; /tmp/log</code>
<p><a name="preexecclose"></a>
<p></p><dt><strong><strong>preexec close (S)</strong></strong><dd>
<p>This boolean option controls whether a non-zero return code from
<a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a> should close the service being connected to.
<p><strong>Default:</strong>
<code> 	preexec close = no</code>
<p><strong>Example:</strong>
<code> 	preexec close = yes</code>
<p><a name="preferredmaster"></a>
<p></p><dt><strong><strong>preferred master (G)</strong></strong><dd>
<p>This boolean parameter controls if <a href="nmbd.8.html"><strong>nmbd</strong></a> is a
preferred master browser for its workgroup.
<p>If this is set to true, on startup, <a href="nmbd.8.html"><strong>nmbd</strong></a> 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 <a href="smb.conf.5.html#domainmaster"><strong>"domain master = yes"</strong></a>, so
that <a href="nmbd.8.html"><strong>nmbd</strong></a> can guarantee becoming a domain
master.
<p>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.
<p>See also <a href="smb.conf.5.html#oslevel"><strong>os level</strong></a>.
<p><strong>Default:</strong>
<code> 	preferred master = no</code>
<p><strong>Example:</strong>
<code> 	preferred master = yes</code>
<p><a name="preferedmaster"></a>
<p></p><dt><strong><strong>prefered master (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#preferredmaster"><strong>"preferred master"</strong></a> for people
who cannot spell :-).
<p><a name="preload"></a>
<p></p><dt><strong><strong>preload</strong></strong><dd>
Synonym for <a href="smb.conf.5.html#autoservices"><strong>"auto services"</strong></a>.
<p><a name="preservecase"></a>
<p></p><dt><strong><strong>preserve case (S)</strong></strong><dd>
<p>This controls if new filenames are created with the case that the
client passes, or if they are forced to be the <code>"default"</code> case.
<p><strong>Default:</strong>
<code>       preserve case = yes</code>
<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for a
fuller discussion.
<p><a name="printcommand"></a>
<p></p><dt><strong><strong>print command (S)</strong></strong><dd>
<p>After a print job has finished spooling to a service, this command
will be used via a <code>system()</code> 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.
<p>The print command is simply a text string. It will be used verbatim,
with two exceptions: All occurrences of <code>"%s"</code> and <code>"%f"</code> will be
replaced by the appropriate spool file name, and all occurrences of
<code>"%p"</code> will be replaced by the appropriate printer name. The spool
file name is generated automatically by the server, the printer name
is discussed below.
<p>The print command <em>MUST</em> contain at least one occurrence of <code>"%s"</code>
or <code>"%f"</code> - the <code>"%p"</code> is optional. At the time a job is
submitted, if no printer name is supplied the <code>"%p"</code> will be
silently removed from the printer command.
<p>If specified in the <a href="smb.conf.5.html#global"><strong>"[global]"</strong></a> section, the print
command given will be used for any printable service that does not
have its own print command specified.
<p>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.
<p>Note that printing may fail on some UNIXs from the <code>"nobody"</code>
account. If this happens then create an alternative guest account that
can print and set the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a> in the
<a href="smb.conf.5.html#global"><strong>"[global]"</strong></a> section.
<p>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 <code>';'</code> is the usual
separator for command in shell scripts.
<p><code>print command = echo Printing %s &gt;&gt; /tmp/print.log; lpr -P %p %s; rm %s</code>
<p>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 <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a>
parameter.
<p><strong>Default:</strong>
	For <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> BSD, AIX, QNX, LPRNG or PLP :
<code>	print command = lpr -r -P%p %s</code>
<p>For <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> SYS or HPUX :
<code>	print command = lp -c -d%p %s; rm %s</code>
<p>For <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> SOFTQ :
<code>	print command = lp -d%p -s %s; rm %s</code>
<p><strong>Example:</strong>
<code> 	print command = /usr/local/samba/bin/myprintscript %p %s</code>
<p><a name="printok"></a>
<p></p><dt><strong><strong>print ok (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#printable"><strong>printable</strong></a>.
<p><a name="printable"></a>
<p></p><dt><strong><strong>printable (S)</strong></strong><dd>
<p>If this parameter is <code>"yes"</code>, then clients may open, write to and
submit spool files on the directory specified for the service.
<p>Note that a printable service will ALWAYS allow writing to the service
path (user privileges permitting) via the spooling of print data. The
<a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> parameter controls only non-printing
access to the resource.
<p><strong>Default:</strong>
<code> 	printable = no</code>
<p><strong>Example:</strong>
<code> 	printable = yes</code>
<p><a name="printcap"></a>
<p></p><dt><strong><strong>printcap (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#printcapname"><strong>printcapname</strong></a>.
<p><a name="printeradmin"></a>
<p></p><dt><strong><strong>printer admin (S)</strong></strong><dd>
<p>This is a list of users that can do anything to printers via the
remote administration interfaces offered by MSRPC (usually using a NT
workstation). Note that the root user always has admin rights.
<p><strong>Default:</strong>
<code>     printer admin = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	printer admin = admin, @staff</code>
<p><a name="printcapname"></a>
<p></p><dt><strong><strong>printcap name (G)</strong></strong><dd>
<p>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 <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> section above for
reasons why you might want to do this.
<p>On System V systems that use <strong>lpstat</strong> to list available printers you
can use <code>"printcap name = lpstat"</code> 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 <strong>"printcap name"</strong> is set to <strong>lpstat</strong> on these systems
then Samba will launch <code>"lpstat -v"</code> and attempt to parse the output
to obtain a printer list.
<p>A minimal printcap file would look something like this:
<p><pre>

	print1|My Printer 1
	print2|My Printer 2
	print3|My Printer 3
	print4|My Printer 4
	print5|My Printer 5

</pre>

<p>where the <code>'|'</code> 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.
<p><em>NOTE</em>: Under AIX the default printcap name is
<code>"/etc/qconfig"</code>. Samba will assume the file is in AIX <code>"qconfig"</code>
format if the string <code>"/qconfig"</code> appears in the printcap filename.
<p><strong>Default:</strong>
<code> 	printcap name = /etc/printcap</code>
<p><strong>Example:</strong>
<code> 	printcap name = /etc/myprintcap</code>
<p><a name="printer"></a>
<p></p><dt><strong><strong>printer (S)</strong></strong><dd>
<p>This parameter specifies the name of the printer to which print jobs
spooled through a printable service will be sent.
<p>If specified in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section, the printer
name given will be used for any printable service that does not have
its own printer name specified.
<p><strong>Default:</strong>
	none (but may be <code>"lp"</code> on many systems)
<p><strong>Example:</strong>
 	printer name = laserwriter
<p><a name="printerdriver"></a>
<p></p><dt><strong><strong>printer driver (S)</strong></strong><dd>
<p>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.
<p>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
<strong>"printer driver"</strong> 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.
<p>See also <a href="smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>.
<p><strong>Example:</strong>
	printer driver = HP LaserJet 4L
<p><a name="printerdriverfile"></a>
<p></p><dt><strong><strong>printer driver file (G)</strong></strong><dd>
<p>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 :
<p><code>SAMBA_INSTALL_DIRECTORY/lib/printers.def</code>
<p>This file is created from Windows 95 <code>"msprint.def"</code> 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.
<p><strong>Default:</strong>
<code>	None (set in compile).</code>
<p><strong>Example:</strong>
<code>	printer driver file = /usr/local/samba/printers/drivers.def</code>
<p>See also <a href="smb.conf.5.html#printerdriverlocation"><strong>"printer driver location"</strong></a>.
<p><a name="printerdriverlocation"></a>
<p></p><dt><strong><strong>printer driver location (S)</strong></strong><dd>
<p>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
<p><code>\\MACHINE\PRINTER$</code>
<p>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.
<p><strong>Default:</strong>
<code>	None</code>
<p><strong>Example:</strong>
<code>	printer driver location = \\MACHINE\PRINTER$</code>
<p>See also <a href="smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>.
<p><a name="printername"></a>
<p></p><dt><strong><strong>printer name (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#printer"><strong>printer</strong></a>.
<p><a name="printing"></a>
<p></p><dt><strong><strong>printing (S)</strong></strong><dd>
<p>This parameters controls how printer status information is interpreted
on your system. It also affects the default values for the
<a href="smb.conf.5.html#printcommand"><strong>"print command"</strong></a>, <a href="smb.conf.5.html#lpqcommand"><strong>"lpq
command"</strong></a> <a href="smb.conf.5.html#lppausecommand"><strong>"lppause command"</strong></a>,
<a href="smb.conf.5.html#lpresumecommand"><strong>"lpresume command"</strong></a>, and <a href="smb.conf.5.html#lprmcommand"><strong>"lprm
command"</strong></a> if specified in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a>
section.
<p>Currently eight printing styles are supported. They are
<strong>"printing=BSD"</strong>, <strong>"printing=AIX"</strong>, 
<strong>"printing=LPRNG"</strong>, <strong>"printing=PLP"</strong>, <strong>"printing=SYSV"</strong>, 
<strong>"printing="HPUX"</strong>, <strong>"printing=QNX"</strong>, <strong>"printing=SOFTQ"</strong>,
and <strong>"printing=CUPS"</strong>.
<p>To see what the defaults are for the other print commands when using
the various options use the <a href="testparm.1.html"><strong>"testparm"</strong></a> program.
<p>This option can be set on a per printer basis
<p>See also the discussion in the <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> section.
<p><a name="protocol"></a>
<p></p><dt><strong><strong>protocol (G)</strong></strong><dd>
<p>The value of the parameter (a string) is the highest protocol level
that will be supported by the server.
<p>Possible values are :
<p><dl>
<p><li > CORE: Earliest version. No concept of user names.
<p><li > COREPLUS: Slight improvements on CORE for efficiency.
<p><li > LANMAN1: First <em>"modern"</em> version of the protocol. Long
filename support.
<p><li > LANMAN2: Updates to Lanman1 protocol.
<p><li > NT1: Current up to date version of the protocol. Used by Windows
NT. Known as CIFS.
<p></dl>
<p>Normally this option should not be set as the automatic negotiation
phase in the SMB protocol takes care of choosing the appropriate
protocol.
<p><strong>Default:</strong>
<code>	protocol = NT1</code>
<p><strong>Example:</strong>
<code>	protocol = LANMAN1</code>
<p><a name="public"></a>
<p></p><dt><strong><strong>public (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#guestok"><strong>"guest ok"</strong></a>.
<p><a name="queuepausecommand"></a>
<p></p><dt><strong><strong>queuepause command (S)</strong></strong><dd>
<p>This parameter specifies the command to be executed on the server host
in order to pause the printerqueue.
<p>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.
<p>This command is not supported by Windows for Workgroups, but can be
issued from the Printer's window under Windows 95 &amp; NT.
<p>If a <code>"%p"</code> is given then the printername is put in its
place. Otherwise it is placed at the end of the command.
<p>Note that it is good practice to include the absolute path in the
command as the PATH may not be available to the server.
<p><strong>Default:</strong>
<code>        depends on the setting of "printing ="</code>
<p><strong>Example:</strong>
<code>      queuepause command = disable %p</code>
<p><a name="queueresumecommand"></a>
<p></p><dt><strong><strong>queueresume command (S)</strong></strong><dd>
<p>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
(<a href="smb.conf.5.html#queuepausecommand"><strong>"queuepause command</strong></a>).
<p>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.
<p>This command is not supported by Windows for Workgroups, but can be
issued from the Printer's window under Windows 95 &amp; NT.
<p>If a <code>"%p"</code> is given then the printername is put in its
place. Otherwise it is placed at the end of the command.
<p>Note that it is good practice to include the absolute path in the
command as the PATH may not be available to the server.
<p><strong>Default:</strong>
<code>        depends on the setting of "printing ="</code>
<p><strong>Example:</strong>
<code>      queuepause command = enable %p</code>
<p><a name="readbmpx"></a>
<p></p><dt><strong><strong>read bmpx (G)</strong></strong><dd>
<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a>
will support the "Read Block Multiplex" SMB. This is now rarely used
and defaults to off. You should never need to set this parameter.
<p><strong>Default:</strong>
	read bmpx = No
<p><a name="readlist"></a>
<p></p><dt><strong><strong>read list (S)</strong></strong><dd>
<p>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 <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a>
option is set to. The list can include group names using the syntax
described in the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter.
<p>See also the <a href="smb.conf.5.html#writelist"><strong>"write list"</strong></a> parameter and
the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	read list = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	read list = mary, @students</code>
<p><a name="readonly"></a>
<p></p><dt><strong><strong>read only (S)</strong></strong><dd>
<p>Note that this is an inverted synonym for
<a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a>.
<p><a name="readprediction"></a>
<p></p><dt><strong><strong>read prediction (G)</strong></strong><dd>
<p><em>NOTE</em>: This code is currently disabled in Samba2.0 and
may be removed at a later date. Hence this parameter has
no effect.
<p>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.
<p><strong>Default:</strong>
<code>	read prediction = False</code>
<p><a name="readraw"></a>
<p></p><dt><strong><strong>read raw (G)</strong></strong><dd>
<p>This parameter controls whether or not the server will support the raw
read SMB requests when transferring data to clients.
<p>If enabled, raw reads allow reads of 65535 bytes in one packet. This
typically provides a major performance benefit.
<p>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.
<p>In general this parameter should be viewed as a system tuning tool and left
severely alone. See also <a href="smb.conf.5.html#writeraw"><strong>"write raw"</strong></a>.
<p><strong>Default:</strong>
<code> 	read raw = yes</code>
<p><a name="readsize"></a>
<p></p><dt><strong><strong>read size (G)</strong></strong><dd>
<p>The option <strong>"read size"</strong> 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.
<p>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.
<p>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.
<p><strong>Default:</strong>
<code>	read size = 16384</code>
<p><strong>Example:</strong>
<code>	read size = 8192</code>
<p><a name="remoteannounce"></a>
<p></p><dt><strong><strong>remote announce (G)</strong></strong><dd>
<p>This option allows you to setup <a href="nmbd.8.html"><strong>nmbd</strong></a> to
periodically announce itself to arbitrary IP addresses with an
arbitrary workgroup name.
<p>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.
<p>For example:
<p><code>	remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF</code>
<p>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
<a href="smb.conf.5.html#workgroup"><strong>"workgroup"</strong></a> parameter is used instead.
<p>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.
<p>See the documentation file BROWSING.txt in the docs/ directory.
<p><strong>Default:</strong>
<code>	remote announce = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF</code>
<p><a name="remotebrowsesync"></a>
<p></p><dt><strong><strong>remote browse sync (G)</strong></strong><dd>
<p>This option allows you to setup <a href="nmbd.8.html"><strong>nmbd</strong></a> 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.
<p>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.
<p>For example:
<p><code>	remote browse sync = 192.168.2.255 192.168.4.255</code>
<p>the above line would cause <a href="nmbd.8.html"><strong>nmbd</strong></a> to request the
master browser on the specified subnets or addresses to synchronize
their browse lists with the local server.
<p>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.
<p><strong>Default:</strong>
<code>	remote browse sync = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	remote browse sync = 192.168.2.255 192.168.4.255</code>
<p><a name="restrictanonymous"></a>
<p></p><dt><strong><strong>restrict anonymous (G)</strong></strong><dd>
<p>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.
<p>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.
<p>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".
<p><strong>Default:</strong>
<code>     restrict anonymous = false</code>
<p><strong>Example:</strong>
<code>     restrict anonymous = true</code>
<p><a name="root"></a>
<p></p><dt><strong><strong>root (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>.
<p><a name="rootdir"></a>
<p></p><dt><strong><strong>root dir (G)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>.
<p><a name="rootdirectory"></a>
<p></p><dt><strong><strong>root directory (G)</strong></strong><dd>
<p>The server will <code>"chroot()"</code> (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
<code>".."</code> in file names to access other directories (depending on the
setting of the <a href="smb.conf.5.html#widelinks"><strong>"wide links"</strong></a> parameter).
<p>Adding a <strong>"root directory"</strong> entry other than <code>"/"</code> 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 <strong>"root
directory"</strong> option, <em>*including*</em> 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 <strong>"root
directory"</strong> 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.
<p><strong>Default:</strong>
<code>	root directory = /</code>
<p><strong>Example:</strong>
<code>	root directory = /homes/smb</code>
<p><a name="rootpostexec"></a>
<p></p><dt><strong><strong>root postexec (S)</strong></strong><dd>
<p>This is the same as the <a href="smb.conf.5.html#postexec"><strong>"postexec"</strong></a> parameter
except that the command is run as root. This is useful for unmounting
filesystems (such as cdroms) after a connection is closed.
<p>See also <a href="smb.conf.5.html#postexec"><strong>"postexec"</strong></a>.
<p><a name="rootpreexec"></a>
<p></p><dt><strong><strong>root preexec (S)</strong></strong><dd>
<p>This is the same as the <a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a> parameter except
that the command is run as root. This is useful for mounting
filesystems (such as cdroms) before a connection is finalized.
<p>See also <a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a>
and <a href="smb.conf.5.html#rootpreexecclose"><strong>"root preexec close"</strong></a>.
<p><a name="rootpreexecclose"></a>
<p></p><dt><strong><strong>root preexec close (S)</strong></strong><dd>
<p>This is the same as the <a href="smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a> parameter
except that the command is run as root.
<p>See also <a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a>, <a href="smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a>.
<p><a name="security"></a>
<p></p><dt><strong><strong>security (G)</strong></strong><dd>
<p>This option affects how clients respond to Samba and is one of the most
important settings in the <strong>smb.conf</strong> file.
<p>The option sets the <code>"security mode bit"</code> in replies to protocol
negotiations with <a href="smbd.8.html"><strong>smbd</strong></a> 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.
<p>The default is <a href="smb.conf.5.html#securityequaluser">"security=user"</a>, as this is
the most common setting needed when talking to Windows 98 and Windows
NT.
<p>The alternatives are <a href="smb.conf.5.html#securityequalshare"><strong>"security = share"</strong></a>,
<a href="smb.conf.5.html#securityequalserver"><strong>"security = server"</strong></a> or
<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>.
<p><em>*****NOTE THAT THIS DEFAULT IS DIFFERENT IN SAMBA2.0 THAN FOR
PREVIOUS VERSIONS OF SAMBA *******</em>.
<p>In previous versions of Samba the default was
<a href="smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> mainly because that was
the only option at one stage.
<p>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.
<p>If your PCs use usernames that are the same as their usernames on the
UNIX machine then you will want to use <strong>"security = user"</strong>. If you
mostly use usernames that don't exist on the UNIX box then use
<strong>"security = share"</strong>.
<p>You should also use <a href="smb.conf.5.html#securityequalshare"><strong>security=share</strong></a> 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
<a href="smb.conf.5.html#securityequaluser"><strong>security=user</strong></a>, see the <a href="smb.conf.5.html#maptoguest"><strong>"map to
guest"</strong></a>parameter for details.
<p>It is possible to use <a href="smbd.8.html"><strong>smbd</strong></a> in a <em>"hybrid
mode"</em> where it is offers both user and share level security under
different <a href="smb.conf.5.html#netbiosaliases"><strong>NetBIOS aliases</strong></a>. See the
<a href="smb.conf.5.html#netbiosaliases"><strong>NetBIOS aliases</strong></a> and the
<a href="smb.conf.5.html#include"><strong>include</strong></a> parameters for more information.
<p>The different settings will now be explained.
<p><dl>
<p><a name="securityequalshare"></a>
<p></p><dt><strong><strong>"security=share"</strong></strong><dd> When clients connect to a share level
security server then need not log onto the server with a valid
username and password before attempting to connect to a shared
resource (although modern clients such as Windows 95/98 and Windows NT
will send a logon request with a username but no password when talking
to a <strong>security=share</strong> server). Instead, the clients send
authentication information (passwords) on a per-share basis, at the
time they attempt to connect to that share.
<p>Note that <a href="smbd.8.html"><strong>smbd</strong></a> <em>*ALWAYS*</em> uses a valid UNIX
user to act on behalf of the client, even in <strong>"security=share"</strong>
level security.
<p>As clients are not required to send a username to the server
in share level security, <a href="smbd.8.html"><strong>smbd</strong></a> uses several
techniques to determine the correct UNIX user to use on behalf
of the client.
<p>A list of possible UNIX usernames to match with the given
client password is constructed using the following methods :
<p><dl>
<p><li > If the <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is set, then
all the other stages are missed and only the <a href="smb.conf.5.html#guestaccount"><strong>"guest
account"</strong></a> username is checked.
<p><li > Is a username is sent with the share connection request, then
this username (after mapping - see <a href="smb.conf.5.html#usernamemap"><strong>"username
map"</strong></a>), is added as a potential username.
<p><li > If the client did a previous <em>"logon"</em> request (the
SessionSetup SMB call) then the username sent in this SMB
will be added as a potential username.
<p><li > The name of the service the client requested is added
as a potential username.
<p><li > The NetBIOS name of the client is added to the list as a
potential username.
<p><li > Any users on the <a href="smb.conf.5.html#user"><strong>"user"</strong></a> list are added
as potential usernames.
<p></dl>
<p>If the <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> 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.
<p>If the <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is set, or no
username can be determined then if the share is marked as available to
the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>, then this guest user will
be used, otherwise access is denied.
<p>Note that it can be <em>*very*</em> confusing in share-level security as to
which UNIX username will eventually be used in granting access.
<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
VALIDATION"</strong></a>.
<p><a name="securityequaluser"></a>
<p></p><dt><strong><strong>"security=user"</strong></strong><dd>
<p>This is the default security setting in Samba2.0. With user-level
security a client must first <code>"log-on"</code> with a valid username and
password (which can be mapped using the <a href="smb.conf.5.html#usernamemap"><strong>"username
map"</strong></a> parameter). Encrypted passwords (see the
<a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter) can also
be used in this security mode. Parameters such as
<a href="smb.conf.5.html#user"><strong>"user"</strong></a> and <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a>, 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.
<p><em>Note</em> that the name of the resource being requested is
<em>*not*</em> 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 <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the
<a href="smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on
doing this.
<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
VALIDATION"</strong></a>.
<p><a name="securityequalserver"></a>
<p></p><dt><strong><strong>"security=server"</strong></strong><dd>
<p>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 <strong>"security = user"</strong>, 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.
<p><em>Note</em> that from the clients point of view <strong>"security=server"</strong> is
the same as <a href="smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only
affects how the server deals with the authentication, it does not in
any way affect what the client sees.
<p><em>Note</em> that the name of the resource being requested is
<em>*not*</em> 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 <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the
<a href="smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on
doing this.
<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
VALIDATION"</strong></a>.
<p>See also the <a href="smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> parameter.
and the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter.
<p><a name="securityequaldomain"></a>
<p></p><dt><strong><strong>"security=domain"</strong></strong><dd>
<p>This mode will only work correctly if
<a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> has been used to add this machine
into a Windows NT Domain. It expects the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted
passwords"</strong></a> parameter to be set to <code>"true"</code>. 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.
<p><em>Note</em> 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.
<p><em>Note</em> that from the clients point of view <strong>"security=domain"</strong> is
the same as <a href="smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only
affects how the server deals with the authentication, it does not in
any way affect what the client sees.
<p><em>Note</em> that the name of the resource being requested is
<em>*not*</em> 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 <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the
<a href="smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on
doing this.
<p><em>BUG:</em> There is currently a bug in the implementation of
<strong>"security=domain</strong> 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.
<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
VALIDATION"</strong></a>.
<p>See also the <a href="smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> parameter.
and the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter.
<p></dl>
<p><strong>Default:</strong>
<code> 	security = USER</code>
<p><strong>Example:</strong>
<code> 	security = DOMAIN</code>
<p><a name="securitymask"></a>
<p></p><dt><strong><strong>security mask (S)</strong></strong><dd>
<p>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.
<p>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.
<p>If not set explicitly this parameter is set to the same value as the
<a href="smb.conf.5.html#createmask"><strong>create mask</strong></a> parameter. To allow a user to
modify all the user/group/world permissions on a file, set this
parameter to 0777.
<p><em>Note</em> 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.
<p>See also the <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security
mode</strong></a>, <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security
mask</strong></a>, <a href="smb.conf.5.html#forcesecuritymode"><strong>force security
mode</strong></a> parameters.
<p><strong>Default:</strong>
<code>	security mask = &lt;same as create mask&gt;</code>
<p><strong>Example:</strong>
<code>	security mask = 0777</code>
<p><a name="serverstring"></a>
<p></p><dt><strong><strong>server string (G)</strong></strong><dd>
<p>This controls what string will show up in the printer comment box in
print manager and next to the IPC connection in <code>"net view"</code>. It can be
any string that you wish to show to your users.
<p>It also sets what will appear in browse lists next to the machine
name.
<p>A <code>"%v"</code> will be replaced with the Samba version number.
<p>A <code>"%h"</code> will be replaced with the hostname.
<p><strong>Default:</strong>
<code>	server string = Samba %v</code>
<p><strong>Example:</strong>
<code>	server string = University of GNUs Samba Server</code>
<p><a name="setdirectory"></a>
<p></p><dt><strong><strong>set directory (S)</strong></strong><dd>
<p>If <code>"set directory = no"</code>, then users of the service may not use the
setdir command to change directory.
<p>The setdir command is only implemented in the Digital Pathworks
client. See the Pathworks documentation for details.
<p><strong>Default:</strong>
<code> 	set directory = no</code>
<p><strong>Example:</strong>
<code> 	set directory = yes</code>
<p><a name="sharemodes"></a>
<p></p><dt><strong><strong>share modes (S)</strong></strong><dd>
<p>This enables or disables the honoring of the <code>"share modes"</code> during a
file open. These modes are used by clients to gain exclusive read or
write access to a file.
<p>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).
<p>The share modes that are enabled by this option are DENY_DOS,
DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB.
<p>This option gives full share compatibility and enabled by default.
<p>You should <em>*NEVER*</em> turn this parameter off as many Windows
applications will break if you do so.
<p><strong>Default:</strong>
<code>	share modes = yes</code>
<p><a name="sharedmemsize"></a>
<p></p><dt><strong><strong>shared mem size (G)</strong></strong><dd>
<p>It specifies the size of the shared memory (in bytes) to use between
<a href="smbd.8.html"><strong>smbd</strong></a> 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 <code>"ERROR
smb_shm_alloc : alloc of XX bytes failed"</code>.
<p>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.
<p><strong>Default:</strong>
<code>	shared mem size = 1048576</code>
<p><strong>Example:</strong>
<code>	shared mem size = 5242880 ; Set to 5mb for a large number of files.</code>
<p><a name="shortpreservecase"></a>
<p></p><dt><strong><strong>short preserve case (S)</strong></strong><dd>
<p>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 <code>"default"</code> case. This
option can be use with <a href="smb.conf.5.html#preservecaseoption"><strong>"preserve case
=yes"</strong></a> to permit long filenames to retain their
case, while short names are lowered. Default <em>Yes</em>.
<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>.
<p><strong>Default:</strong>
<code>	short preserve case = yes</code>
<p><a name="smbpasswdfile"></a>
<p></p><dt><strong><strong>smb passwd file (G)</strong></strong><dd>
<p>This option sets the path to the encrypted smbpasswd file.  By default
the path to the smbpasswd file is compiled into Samba.
<p><strong>Default:</strong>
<code>	smb passwd file= &lt;compiled default&gt;</code>
<p><strong>Example:</strong>
<code>	smb passwd file = /usr/samba/private/smbpasswd</code>
<p><a name="smbrun"></a>
<p></p><dt><strong><strong>smbrun (G)</strong></strong><dd>
<p>This sets the full path to the <strong>smbrun</strong> binary. This defaults to the
value in the Makefile.
<p>You must get this path right for many services to work correctly.
<p>You should not need to change this parameter so long as Samba
is installed correctly.
<p><strong>Default:</strong>
<code>	smbrun=&lt;compiled default&gt;</code>
<p><strong>Example:</strong>
<code>	smbrun = /usr/local/samba/bin/smbrun</code>
<p><a name="socketaddress"></a>
<p></p><dt><strong><strong>socket address (G)</strong></strong><dd>
<p>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.
<p>By default samba will accept connections on any address.
<p><strong>Example:</strong>
<code>	socket address = 192.168.2.20</code>
<p><a name="socketoptions"></a>
<p></p><dt><strong><strong>socket options (G)</strong></strong><dd>
<p>This option allows you to set socket options to be used when talking
with the client.
<p>Socket options are controls on the networking layer of the operating
systems which allow the connection to be tuned.
<p>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
<strong>"man setsockopt"</strong> will help).
<p>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
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
<p>Any of the supported socket options may be combined in any way you
like, as long as your OS allows it.
<p>This is the list of socket options currently settable using this
option:
<p><dl>
<p><li > SO_KEEPALIVE
<p><li > SO_REUSEADDR
<p><li > SO_BROADCAST
<p><li > TCP_NODELAY
<p><li > IPTOS_LOWDELAY
<p><li > IPTOS_THROUGHPUT
<p><li > SO_SNDBUF *
<p><li > SO_RCVBUF *
<p><li > SO_SNDLOWAT *
<p><li > SO_RCVLOWAT *
<p></dl>
<p>Those marked with a <code>*</code> 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.
<p>To specify an argument use the syntax SOME_OPTION=VALUE for example
<code>SO_SNDBUF=8192</code>. Note that you must not have any spaces before or after
the = sign.
<p>If you are on a local network then a sensible option might be
<p><code>socket options = IPTOS_LOWDELAY</code>
<p>If you have a local network then you could try:
<p><code>socket options = IPTOS_LOWDELAY TCP_NODELAY</code>
<p>If you are on a wide area network then perhaps try setting
IPTOS_THROUGHPUT. 
<p>Note that several of the options may cause your Samba server to fail
completely. Use these options with caution!
<p><strong>Default:</strong>
<code>	socket options = TCP_NODELAY</code>
<p><strong>Example:</strong>
<code>	socket options = IPTOS_LOWDELAY</code>
<p><a name="sourceenvironment"></a>
<p></p><dt><strong><strong>source environment (G)</strong></strong><dd>
<p>This parameter causes Samba to set environment variables as per the
content of the file named.
<p>The file <strong>must</strong> be owned by root and not world writable in order
to be read (this is a security check).
<p>If the value of this parameter starts with a "|" character then Samba will
treat that value as a pipe command to open and will set the environment
variables from the oput of the pipe. This command must not be world writable
and must reside in a directory that is not world writable.
<p>The contents of the file or the output of the pipe should be formatted
as the output of the standard Unix env(1) command. This is of the form :
<p>Example environment entry:
<code> SAMBA_NETBIOS_NAME=myhostname </code>
<p><strong>Default:</strong>
<code>No default value</code>
<p><strong>Examples:</strong>
<p><code>	source environment = |/etc/smb.conf.sh</code>
<p><code>	source environment = /usr/local/smb_env_vars</code>
<p><a name="ssl"></a>
<p></p><dt><strong><strong>ssl (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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 <a href="smb.conf.5.html#sslhosts"><strong>"ssl
hosts"</strong></a> and <a href="smb.conf.5.html#sslhostsresign"><strong>"ssl hosts resign"</strong></a>
whether an SSL connection will be required.
<p><strong>Default:</strong>
<code>	ssl=no</code>
  <strong>Example:</strong>
<code>	ssl=yes</code>
<p><a name="sslCAcertDir"></a>
<p></p><dt><strong><strong>ssl CA certDir (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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.
<p><strong>Default:</strong>
<code>	ssl CA certDir = /usr/local/ssl/certs</code>
<p><a name="sslCAcertFile"></a>
<p></p><dt><strong><strong>ssl CA certFile (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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.
<p><strong>Default:</strong>
<code>	ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem</code>
<p><a name="sslciphers"></a>
<p></p><dt><strong><strong>ssl ciphers (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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.
<p><a name="sslclientcert"></a>
<p></p><dt><strong><strong>ssl client cert (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>The certificate in this file is used by
<a href="smbclient.1.html"><strong>smbclient</strong></a> if it exists. It's needed if the
server requires a client certificate.
<p><strong>Default:</strong>
<code>	ssl client cert = /usr/local/ssl/certs/smbclient.pem</code>
<p><a name="sslclientkey"></a>
<p></p><dt><strong><strong>ssl client key (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>This is the private key for <a href="smbclient.1.html"><strong>smbclient</strong></a>. It's
only needed if the client should have a certificate.
<p><strong>Default:</strong>
<code>	ssl client key = /usr/local/ssl/private/smbclient.pem</code>
<p><a name="sslcompatibility"></a>
<p></p><dt><strong><strong>ssl compatibility (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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.
<p><strong>Default:</strong>
<code>	ssl compatibility = no</code>
<p><a name="sslhosts"></a>
<p></p><dt><strong><strong>ssl hosts (G)</strong></strong><dd>
<p>See <a href="smb.conf.5.html#sslhostsresign"><strong>"ssl hosts resign"</strong></a>.
<p><a name="sslhostsresign"></a>
<p></p><dt><strong><strong>ssl hosts resign (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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 <a href="smb.conf.5.html#sslhosts"><strong>"ssl hosts"</strong></a> variable lists
hosts (by IP-address, IP-address range, net group or name), only these
hosts will be forced into SSL mode. If the <strong>"ssl hosts resign"</strong>
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
<a href="smb.conf.5.html#hostsallow"><strong>"hosts allow"</strong></a> and <a href="smb.conf.5.html#hostsdeny"><strong>"hosts
deny"</strong></a> 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 <a href="smb.conf.5.html#allowhosts"><strong>"allow hosts"</strong></a> parameter for
details. The example below requires SSL connections from all hosts
outside the local net (which is 192.168.*.*).
<p><strong>Default:</strong>
<code>	ssl hosts = &lt;empty string&gt;</code>
<code>	ssl hosts resign = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	ssl hosts resign = 192.168.</code>
<p><a name="sslrequireclientcert"></a>
<p></p><dt><strong><strong>ssl require clientcert (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>If this variable is set to <code>"yes"</code>, the server will not tolerate
connections from clients that don't have a valid certificate. The
directory/file given in <a href="smb.conf.5.html#sslCAcertDir"><strong>"ssl CA certDir"</strong></a> and
<a href="smb.conf.5.html#sslCAcertFile"><strong>"ssl CA certFile"</strong></a> 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 <code>"no"</code>, clients don't need certificates. Contrary
to web applications you really <em>*should*</em> 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.
<p><strong>Default:</strong>
<code>	ssl require clientcert = no</code>
<p><a name="sslrequireservercert"></a>
<p></p><dt><strong><strong>ssl require servercert (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>If this variable is set to <code>"yes"</code>, the
<a href="smbclient.1.html"><strong>smbclient</strong></a> will request a certificate from
the server. Same as <a href="smb.conf.5.html#sslrequireclientcert"><strong>"ssl require
clientcert"</strong></a> for the server.
<p><strong>Default:</strong>
<code>	ssl require servercert = no</code>
<p><a name="sslservercert"></a>
<p></p><dt><strong><strong>ssl server cert (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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.
<p><strong>Default:</strong>
<code>	ssl server cert = &lt;empty string&gt;</code>
<p><a name="sslserverkey"></a>
<p></p><dt><strong><strong>ssl server key (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>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 <em>*must*</em> have a private key
and the certificate <em>*must*</em> match this private key.
<p><strong>Default:</strong>
<code>	ssl server key = &lt;empty string&gt;</code>
<p><a name="sslversion"></a>
<p></p><dt><strong><strong>ssl version (G)</strong></strong><dd>
<p>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 <code>"--with-ssl"</code> was given at configure time.
<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em>
enabled by default in any current binary version of Samba.
<p>This enumeration variable defines the versions of the SSL protocol
that will be used. <code>"ssl2or3"</code> allows dynamic negotiation of SSL v2
or v3, <code>"ssl2"</code> results in SSL v2, <code>"ssl3"</code> results in SSL v3 and
"tls1" results in TLS v1. TLS (Transport Layer Security) is the
(proposed?) new standard for SSL.
<p><strong>Default:</strong>
<code>	ssl version = "ssl2or3"</code>
<p><a name="statcache"></a>
<p></p><dt><strong><strong>stat cache (G)</strong></strong><dd>
<p>This parameter determines if <a href="smbd.8.html"><strong>smbd</strong></a> will use a
cache in order to speed up case insensitive name mappings. You should
never need to change this parameter.
<p><strong>Default:</strong>
<code>	stat cache = yes</code>
<p><a name="statcachesize"></a>
<p></p><dt><strong><strong>stat cache size (G)</strong></strong><dd>
<p>This parameter determines the number of entries in the <a href="smb.conf.5.html#statcache"><strong>stat
cache</strong></a>.  You should never need to change this parameter.
<p><strong>Default:</strong>
<code>	stat cache size = 50</code>
<p><a name="status"></a>
<p></p><dt><strong><strong>status (G)</strong></strong><dd>
<p>This enables or disables logging of connections to a status file that
<a href="smbstatus.1.html"><strong>smbstatus</strong></a> can read.
<p>With this disabled <a href="smbstatus.1.html"><strong>smbstatus</strong></a> won't be able
to tell you what connections are active. You should never need to
change this parameter.
<p><strong>Default:</strong>
	status = yes
<p><a name="strictlocking"></a>
<p></p><dt><strong><strong>strict locking (S)</strong></strong><dd>
<p>This is a boolean that controls the handling of file locking in the
server. When this is set to <code>"yes"</code> 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.
<p>When strict locking is <code>"no"</code> the server does file lock checks only
when the client explicitly asks for them.
<p>Well behaved clients always ask for lock checks when it is important,
so in the vast majority of cases <strong>"strict locking = no"</strong> is
preferable.
<p><strong>Default:</strong>
<code>	strict locking = no</code>
<p><strong>Example:</strong>
<code>	strict locking = yes</code>
<p><a name="strictsync"></a>
<p></p><dt><strong><strong>strict sync (S)</strong></strong><dd>
<p>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.
<p>See also the <a href="smb.conf.5.html#syncalways"><strong>"sync always"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	strict sync = no</code>
<p><strong>Example:</strong>
<code>	strict sync = yes</code>
<p><a name="stripdot"></a>
<p></p><dt><strong><strong>strip dot (G)</strong></strong><dd>
<p>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.
<p><strong>Default:</strong>
<code>	strip dot = no</code>
<p><strong>Example:</strong>
<code>	strip dot = yes</code>
<p><a name="syncalways"></a>
<p></p><dt><strong><strong>sync always (S)</strong></strong><dd>
<p>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 <a href="smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter must be
set to <code>"yes"</code> in order for this parameter to have any affect.
<p>See also the <a href="smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	sync always = no</code>
<p><strong>Example:</strong>
<code>	sync always = yes</code>
<p><a name="syslog"></a>
<p></p><dt><strong><strong>syslog (G)</strong></strong><dd>
<p>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.
<p>This paramter sets the threshold for sending messages to syslog. 
Only messages with debug level less than this value will be sent 
to syslog.
<p><strong>Default:</strong>
<code>	syslog = 1</code>
<p><a name="syslogonly"></a>
<p></p><dt><strong><strong>syslog only (G)</strong></strong><dd>
<p>If this parameter is set then Samba debug messages are logged into the
system syslog only, and not to the debug log files.
<p><strong>Default:</strong>
<code>	syslog only = no</code>
<p><a name="templatehomedir"></a>
<p></p><dt><strong><strong>template homedir (G)</strong></strong><dd>
<p>NOTE: this parameter is only available in Samba 3.0.
<p>When filling out the user information for a Windows NT user, the
<a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in
the home directory for that user.  If the string <code>%D</code> is present it is
substituted with the user's Windows NT domain name.  If the string <code>%U</code>
is present it is substituted with the user's Windows NT user name.
<p><strong>Default:</strong>
<code>     template homedir = /home/%D/%U</code>
<p><a name="templateshell"></a>
<p></p><dt><strong><strong>template shell (G)</strong></strong><dd>
<p>NOTE: this parameter is only available in Samba 3.0.
<p>When filling out the user information for a Windows NT user, the
<a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in
the login shell for that user.
<p><strong>Default:</strong>
<code>     template shell = /bin/false</code>
<p><a name="timeoffset"></a>
<p></p><dt><strong><strong>time offset (G)</strong></strong><dd>
<p>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.
<p><strong>Default:</strong>
<code>	time offset = 0</code>
<p><strong>Example:</strong>
<code>	time offset = 60</code>
<p><a name="timeserver"></a>
<p><p></p><dt><strong><strong>time server (G)</strong></strong><dd>
<p>This parameter determines if <a href="nmbd.8.html"><strong>nmbd</strong></a> advertises
itself as a time server to Windows clients. The default is False.
<p><strong>Default:</strong>
<code>	time server = False</code>
<p><strong>Example:</strong>
<code>	time server = True</code>
<p><a name="timestamplogs"></a>
<p></p><dt><strong><strong>timestamp logs (G)</strong></strong><dd>
<p>Synonym for <a href="debugtimestamp"><strong>"debug timestamp"</strong></a>.
<p><a name="unixpasswordsync"></a>
<p></p><dt><strong><strong>unix password sync (G)</strong></strong><dd>
<p>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 <a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a>
parameter is called <em>*AS ROOT*</em> - 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 <code>"false"</code>.
<p>See also <a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a>, <a href="smb.conf.5.html#passwdchat"><strong>"passwd
chat"</strong></a>.
<p><strong>Default:</strong>
<code>	unix password sync = False</code>
<p><strong>Example:</strong>
<code>	unix password sync = True</code>
<p><a name="unixrealname"></a>
<p></p><dt><strong><strong>unix realname (G)</strong></strong><dd>
<p>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.
<p><strong>Default:</strong>
<code>	unix realname = no</code>
<p><strong>Example:</strong>
<code>	unix realname = yes</code>
<p><a name="updateencrypted"></a>
<p></p><dt><strong><strong>update encrypted (G)</strong></strong><dd>
<p>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 <code>"off"</code>.
<p>In order for this parameter to work correctly the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypt
passwords"</strong></a> parameter must be set to <code>"no"</code> when
this parameter is set to <code>"yes"</code>.
<p>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.
<p><strong>Default:</strong>
<code>	update encrypted = no</code>
<p><strong>Example:</strong>
<code>	update encrypted = yes</code>
<p><a name="userhosts"></a>
<p></p><dt><strong><strong>use rhosts (G)</strong></strong><dd>
<p>If this global parameter is a true, it specifies that the UNIX users
<code>".rhosts"</code> 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.
<p>NOTE: The use of <strong>use rhosts</strong> 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
<strong>use rhosts</strong> option be only used if you really know what you are
doing.
<p><strong>Default:</strong>
<code>	use rhosts = no</code>
<p><strong>Example:</strong>
<code>	use rhosts = yes</code>
<p><a name="user"></a>
<p></p><dt><strong><strong>user (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#username"><strong>"username"</strong></a>.
<p><a name="users"></a>
<p></p><dt><strong><strong>users (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#username"><strong>"username"</strong></a>.
<p><a name="username"></a>
<p></p><dt><strong><strong>username (S)</strong></strong><dd>
<p>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).
<p>The <strong>username=</strong> 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 <code>\\server\share%user</code>
syntax instead.
<p>The <strong>username=</strong> 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.
<p>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.
<p>To restrict a service to a particular set of users you can use the
<a href="smb.conf.5.html#validusers"><strong>"valid users="</strong></a> parameter.
<p>If any of the usernames begin with a <code>'@'</code> 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.
<p>If any of the usernames begin with a <code>'+'</code> 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.
<p>If any of the usernames begin with a <code>'&amp;'</code> 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.
<p>Note that searching though a groups database can take quite some time,
and some clients may time out during the search.
<p>See the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
VALIDATION"</strong></a> for more
information on how this parameter determines access to the services.
<p><strong>Default:</strong>
<code>	The guest account if a guest service, else the name of the service.</code>
<p><strong>Examples:</strong>
<pre>

 	username = fred
 	username = fred, mary, jack, jane, @users, @pcgroup

</pre>

<p><a name="usernamelevel"></a>
<p></p><dt><strong><strong>username level (G)</strong></strong><dd>
<p>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.
<p>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 <code>"AstrangeUser"</code>.
<p><strong>Default:</strong>
<code>	username level = 0</code>
<p><strong>Example:</strong>
<code>	username level = 5</code>
<p><a name="usernamemap"></a>
<p></p><dt><strong><strong>username map (G)</strong></strong><dd>
<p>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.
<p>The map file is parsed line by line. Each line should contain a single
UNIX username on the left then a <code>'='</code> 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 <code>'*'</code> is a wildcard
and matches any name. Each line of the map file may be up to 1023
characters long.
<p>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 <code>'='</code>
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.
<p>If any line begins with a <code>'#'</code> or a <code>';'</code> then it is ignored
<p>If any line begins with an <code>'!'</code> 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 <code>'!'</code> is most
useful when you have a wildcard mapping line later in the file.
<p>For example to map from the name <code>"admin"</code> or <code>"administrator"</code> to
the UNIX name <code>"root"</code> you would use:
<p><code>	root = admin administrator</code>
<p>Or to map anyone in the UNIX group <code>"system"</code> to the UNIX name
<code>"sys"</code> you would use:
<p><code>	sys = @system</code>
<p>You can have as many mappings as you like in a username map file.
<p>If your system supports the NIS NETGROUP option then the netgroup
database is checked before the <code>/etc/group</code> database for matching
groups.
<p>You can map Windows usernames that have spaces in them by using double
quotes around the name. For example:
<p><code>	tridge = "Andrew Tridgell"</code>
<p>would map the windows username <code>"Andrew Tridgell"</code> to the unix
username tridge.
<p>The following example would map mary and fred to the unix user sys,
and map the rest to guest. Note the use of the <code>'!'</code> to tell Samba
to stop processing if it gets a match on that line.
<p><pre>

	!sys = mary fred
	guest = *

</pre>

<p>Note that the remapping is applied to all occurrences of
usernames. Thus if you connect to <code>"\\server\fred"</code> and <code>"fred"</code>
is remapped to <code>"mary"</code> then you will actually be connecting to
<code>"\\server\mary"</code> and will need to supply a password suitable for
<code>"mary"</code> not <code>"fred"</code>. The only exception to this is the username
passed to the <a href="smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> (if you have
one). The password server will receive whatever username the client
supplies without modification.
<p>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.
<p><strong>Default:</strong>
<code>	no username map</code>
<p><strong>Example:</strong>
<code>	username map = /usr/local/samba/lib/users.map</code>
<p><a name="utmp"></a>
<p></p><dt><strong><strong>utmp (S)</strong></strong><dd>
<p>This boolean parameter is only available if Samba has been configured and compiled 
with the option <code>--with-utmp</code>. If set to True then Samba will attempt
to add utmp or utmpx records (depending on the UNIX system) whenever a
connection is made to a Samba server. Sites may use this to record the
user connecting to a Samba share.
<p>See also the <a href="smb.conf.5.html#utmpdirectory"><strong>"utmp directory"</strong></a> parameter.
<p><strong>Default:</strong>
<code>utmp = False</code>
<p><strong>Example:</strong>
<code>utmp = True</code>
<p><a name="utmpdirectory"></a>
<p></p><dt><strong><strong>utmp directory(G)</strong></strong><dd>
<p>This parameter is only available if Samba has been configured and compiled
with the option <code>--with-utmp</code>. It specifies a directory pathname that is
used to store the utmp or utmpx files (depending on the UNIX system) that
record user connections to a Samba server. See also the <a href="smb.conf.5.html#utmp"><strong>"utmp"</strong></a>
parameter. By default this is not set, meaning the system will use whatever
utmp file the native system is set to use (usually /var/run/utmp on Linux).
<p><strong>Default:</strong>
<code>no utmp directory</code>
<p><strong>Example:</strong>
<code>utmp directory = /var/adm/</code>
<p><a name="winbindcachetime"></a>
<p></p><dt><strong>winbind cache time</strong><dd>
<p>NOTE: this parameter is only available in Samba 3.0.
<p>This parameter specifies the number of seconds the
<a href="winbindd.8.html"><strong>winbindd</strong></a> daemon will cache user and group
information before querying a Windows NT server again.
<p><strong>Default:</strong>
<code>     winbind cache type = 15</code>
<p><a name="winbindgid"></a>
<p></p><dt><strong>winbind gid</strong><dd>
<p>NOTE: this parameter is only available in Samba 3.0.
<p>The winbind gid parameter specifies the range of group ids that are
allocated by the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon.  This range of
group ids should have no existing local or nis groups within it as strange
conflicts can occur otherwise.
<p><strong>Default:</strong>
<code>     winbind gid = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>     winbind gid = 10000-20000</code>
<p><a name="winbinduid"></a>
<p></p><dt><strong>winbind uid</strong><dd>
<p>NOTE: this parameter is only available in Samba 3.0.
<p>The winbind uid parameter specifies the range of user ids that are
allocated by the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon.  This range of
ids should have no existing local or nis users within it as strange
conflicts can occur otherwise.
<p><strong>Default:</strong>
<code>     winbind uid = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>     winbind uid = 10000-20000</code>
<p><a name="validchars"></a>
<p></p><dt><strong><strong>valid chars (G)</strong></strong><dd>
<p>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.
<p>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.
<p>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.
<p>For example to add the single character <code>'Z'</code> to the charset (which
is a pointless thing to do as it's already there) you could do one of
the following
<p><pre>

	valid chars = Z
	valid chars = z:Z
	valid chars = 0132:0172

</pre>

<p>The last two examples above actually add two characters, and alter the
uppercase and lowercase mappings appropriately.
<p>Note that you MUST specify this parameter after the <a href="smb.conf.5.html#clientcodepage"><strong>"client
code page"</strong></a> parameter if you have both set. If
<a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> is set after the
<strong>"valid chars"</strong> parameter the <strong>"valid chars"</strong> settings will be
overwritten.
<p>See also the <a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> parameter.
<p><strong>Default:</strong>
<pre>

	Samba defaults to using a reasonable set of valid characters
	for English systems

</pre>

<p><strong>Example</strong>
<code>	valid chars = 0345:0305 0366:0326 0344:0304</code>
<p>The above example allows filenames to have the Swedish characters in
them.
<p>NOTE: It is actually quite difficult to correctly produce a <strong>"valid
chars"</strong> line for a particular system. To automate the process
<a href="mailto:tino@augsburg.net"><em>tino@augsburg.net</em></a> has written a package called <strong>"validchars"</strong>
which will automatically produce a complete <strong>"valid chars"</strong> line for
a given client system. Look in the examples/validchars/ subdirectory
of your Samba source code distribution for this package.
<p><a name="validusers"></a>
<p></p><dt><strong><strong>valid users (S)</strong></strong><dd>
<p>This is a list of users that should be allowed to login to this
service. Names starting with <code>'@'</code>, <code>'+'</code> and <code>'&amp;'</code> are
interpreted using the same rules as described in the <a href="smb.conf.5.html#invalidusers"><strong>"invalid
users"</strong></a> parameter.
<p>If this is empty (the default) then any user can login. If a username
is in both this list and the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a>
list then access is denied for that user.
<p>The current servicename is substituted for
<a href="smb.conf.5.html#percentS"><strong>"%S"</strong></a>. This is useful in the
<a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> section.
<p>See also <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a>.
<p><strong>Default:</strong>
<code>	No valid users list. (anyone can login)</code>
<p><strong>Example:</strong>
<code>	valid users = greg, @pcusers</code>
<p><a name="vetofiles"></a>
<p></p><dt><strong><strong>veto files(S)</strong></strong><dd>
<p>This is a list of files and directories that are neither visible nor
accessible.  Each entry in the list must be separated by a <code>'/'</code>,
which allows spaces to be included in the entry. <code>'*'</code> and <code>'?'</code> 
can be used to specify multiple files or directories as in DOS
wildcards.
<p>Each entry must be a unix path, not a DOS path and must <em>*not*</em> include the 
unix directory separator <code>'/'</code>.
<p>Note that the <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a> option is
applicable in vetoing files.
<p>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.
<p>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.
<p>See also <a href="smb.conf.5.html#hidefiles"><strong>"hide files"</strong></a> and <a href="smb.conf.5.html#casesensitive"><strong>"case
sensitive"</strong></a>.
<p><strong>Default:</strong>
<code>	No files or directories are vetoed.</code>
<p><strong>Examples:</strong>
<p>Example 1.
<p><pre>


    Veto any files containing the word Security, 
    any ending in .tmp, and any directory containing the
    word root.

	veto files = /*Security*/*.tmp/*root*/

</pre>

<p>Example 2.
<p><pre>

    Veto the Apple specific files that a NetAtalk server
    creates.

    veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/

</pre>

<p><a name="vetooplockfiles"></a>
<p></p><dt><strong><strong>veto oplock files (S)</strong></strong><dd>
<p>This parameter is only valid when the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a>
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
<a href="smb.conf.5.html#vetofiles"><strong>"veto files"</strong></a> parameter.
<p><strong>Default:</strong>
<code>	No files are vetoed for oplock grants.</code>
<p><strong>Examples:</strong>
<p>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 <code>".SEM"</code>. To cause Samba not to grant oplocks on these
files you would use the line (either in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a>
section or in the section for the particular NetBench share :
<p><code>     veto oplock files = /*.SEM/</code>
<p><a name="volume"></a>
<p></p><dt><strong><strong>volume (S)</strong></strong><dd>
<p>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.
<p>The default is the name of the share.
<p><a name="widelinks"></a>
<p></p><dt><strong><strong>wide links (S)</strong></strong><dd>
<p>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.
<p>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.
<p><strong>Default:</strong>
<code> 	wide links = yes</code>
<p><strong>Example:</strong>
<code> 	wide links = no</code>
<p><a name="winsproxy"></a>
<p></p><dt><strong><strong>wins proxy (G)</strong></strong><dd>
<p>This is a boolean that controls if <a href="nmbd.8.html"><strong>nmbd</strong></a> will
respond to broadcast name queries on behalf of other hosts. You may
need to set this to <code>"yes"</code> for some older clients.
<p><strong>Default:</strong>
<code>	wins proxy = no</code>
<p><a name="winsserver"></a>
<p></p><dt><strong><strong>wins server (G)</strong></strong><dd>
<p>This specifies the IP address (or DNS name: IP address for preference)
of the WINS server that <a href="nmbd.8.html"><strong>nmbd</strong></a> should register with.
If you have a WINS server on your network then you should set this to
the WINS server's IP.        
<p>You should point this at your WINS server if you have a
multi-subnetted network.
<p><em>NOTE</em>. 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.
<p>See the documentation file BROWSING.txt in the docs/ directory of your
Samba source distribution.
<p><strong>Default:</strong>
<code>	wins server = </code>
<p><strong>Example:</strong>
<code>	wins server = 192.9.200.1</code>
<p><a name="winshook"></a>
<p></p><dt><strong><strong>wins hook (G)</strong></strong><dd>
<p>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.
<p>The wins hook parameter specifies the name of a script or executable
that will be called as follows:
<p>wins_hook operation name nametype ttl IP_list
<p>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.
<p>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.
<p>The third argument is the netbios name type as a 2 digit hexadecimal
number. 
<p>The fourth argument is the TTL (time to live) for the name in seconds.
<p>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.
<p>An example script that calls the BIND dynamic DNS update program
"nsupdate" is provided in the examples directory of the Samba source
code. 
<p><a name="winssupport"></a>
<p></p><dt><strong><strong>wins support (G)</strong></strong><dd>
<p>This boolean controls if the <a href="nmbd.8.html"><strong>nmbd</strong></a> 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
<a href="nmbd.8.html"><strong>nmbd</strong></a> to be your WINS server. Note that you
should <em>*NEVER*</em> set this to true on more than one machine in your
network.
<p><strong>Default:</strong>
<code>	wins support = no</code>
<p><a name="workgroup"></a>
<p></p><dt><strong><strong>workgroup (G)</strong></strong><dd>
<p>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 <a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>
setting.
<p><strong>Default:</strong>
<code> 	set at compile time to WORKGROUP</code>
<p><strong>Example:</strong>
 	workgroup = MYGROUP
<p><a name="writable"></a>
<p></p><dt><strong><strong>writable (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> for people who can't spell :-).
<p><a name="writelist"></a>
<p></p><dt><strong><strong>write list (S)</strong></strong><dd>
<p>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 <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a>
option is set to. The list can include group names using the @group
syntax.
<p>Note that if a user is in both the read list and the write list then
they will be given write access.
<p>See also the <a href="smb.conf.5.html#readlist"><strong>"read list"</strong></a> option.
<p><strong>Default:</strong>
<code>     write list = &lt;empty string&gt;</code>
<p><strong>Example:</strong>
<code>	write list = admin, root, @staff</code>
<p><a name="writecachesize"></a>
<p></p><dt><strong><strong>write cache size (S)</strong></strong><dd>
<p>This integer parameter (new with Samba 2.0.7) if set to non-zero causes Samba to create an in-memory
cache for each oplocked file (it does <strong>not</strong> do this for non-oplocked files). All
writes that the client does not request to be flushed directly to disk will be
stored in this cache if possible. The cache is flushed onto disk when a write
comes in whose offset would not fit into the cache or when the file is closed
by the client. Reads for the file are also served from this cache if the data
is stored within it.
<p>This cache allows Samba to batch client writes into a more efficient write
size for RAID disks (ie. writes may be tuned to be the RAID stripe size) and
can improve performance on systems where the disk subsystem is a bottleneck
but there is free memory for userspace programs.
<p>The integer parameter specifies the size of this cache (per oplocked file)
in bytes.
<p><strong>Default:</strong>
<code>     write cache size = 0</code>
<p><strong>Example:</strong>
<code>	     write cache size = 262144</code>
for a 256k cache size per file.
<p><a name="writeok"></a>
<p></p><dt><strong><strong>write ok (S)</strong></strong><dd>
<p>Synonym for <a href="smb.conf.5.html#writeable"><strong>writeable</strong></a>.
<p><a name="writeraw"></a>
<p></p><dt><strong><strong>write raw (G)</strong></strong><dd>
<p>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.
<p><strong>Default:</strong>
<code> 	write raw = yes</code>
<p><a name="writeable"></a>
<p></p><dt><strong><strong>writeable</strong></strong><dd>
<p>An inverted synonym is <a href="smb.conf.5.html#readonly"><strong>"read only"</strong></a>.
<p>If this parameter is <code>"no"</code>, then users of a service may not create
or modify files in the service's directory.
<p>Note that a printable service <a href="smb.conf.5.html#printable"><strong>("printable = yes")</strong></a>
will <em>*ALWAYS*</em> allow writing to the directory (user privileges
permitting), but only via spooling operations.
<p><strong>Default:</strong>
<code> 	writeable = no</code>
<p><strong>Examples:</strong>
<pre>

 	read only = no
 	writeable = yes
 	write ok = yes

</pre>

<p></dl>
<p><a name="WARNINGS"></a>
<h2>WARNINGS</h2>
    
<p>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.
<p>On a similar note, many clients - especially DOS clients - limit
service names to eight characters. <a href="smbd.8.html"><strong>Smbd</strong></a> 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.
<p>Use of the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> and <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a>
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.
<p><a name="VERSION"></a>
<h2>VERSION</h2>
    
<p>This man page is correct for version 2.0 of the Samba suite.
<p><a name="SEEALSO"></a>
<h2>SEE ALSO</h2>
    
<p><a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>,
<a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, <a href="testparm.1.html"><strong>testparm (1)</strong></a>,
<a href="testprns.1.html"><strong>testprns (1)</strong></a>, <a href="samba.7.html"><strong>Samba</strong></a>,
<a href="nmblookup.1.html"><strong>nmblookup (1)</strong></a>, <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a>,
<a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>.
<p><a name="AUTHOR"></a>
<h2>AUTHOR</h2>
    
<p>The original Samba software and related utilities were created by
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
by the Samba Team as an Open Source project similar to the way the
Linux kernel is developed.
<p>The original Samba man pages were written by Karl Auer. The man page
sources were converted to YODL format (another excellent piece of Open
Source software, available at
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
and updated for the Samba2.0 release by Jeremy Allison.
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
list of contributors and details on how to submit bug reports,
comments etc.
</body>
</html>
generated by cgit (git 2.34.1) at 2024-11-18 04:15:09 +0000