docs/htmldocs/smb.conf.5.html

   1 <HTML
   2 ><HEAD
   3 ><TITLE
   4 >smb.conf</TITLE
   5 ><META
   6 NAME="GENERATOR"
   7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
   8 ><BODY
   9 CLASS="REFENTRY"
  10 BGCOLOR="#FFFFFF"
  11 TEXT="#000000"
  12 LINK="#0000FF"
  13 VLINK="#840084"
  14 ALINK="#0000FF"
  15 ><H1
  16 ><A
  17 NAME="SMB.CONF"
  18 >smb.conf</A
  19 ></H1
  20 ><DIV
  21 CLASS="REFNAMEDIV"
  22 ><A
  23 NAME="AEN5"
  24 ></A
  25 ><H2
  26 >Name</H2
  27 >smb.conf&nbsp;--&nbsp;The configuration file for the Samba suite</DIV
  28 ><DIV
  29 CLASS="REFSECT1"
  30 ><A
  31 NAME="AEN8"
  32 ></A
  33 ><H2
  34 >SYNOPSIS</H2
  35 ><P
  36 >The <TT
  37 CLASS="FILENAME"
  38 >smb.conf</TT
  39 > file is a configuration
  40         file for the Samba suite. <TT
  41 CLASS="FILENAME"
  42 >smb.conf</TT
  43 > contains
  44         runtime configuration information for the Samba programs. The
  45         <TT
  46 CLASS="FILENAME"
  47 >smb.conf</TT
  48 > file is designed to be configured and
  49         administered by the <A
  50 HREF="swat.8.html"
  51 TARGET="_top"
  52 ><B
  53 CLASS="COMMAND"
  54 >swat(8)</B
  55 >
  56         </A
  57 > program. The complete description of the file format and
  58         possible parameters held within are here for reference purposes.</P
  59 ></DIV
  60 ><DIV
  61 CLASS="REFSECT1"
  62 ><A
  63 NAME="AEN16"
  64 ></A
  65 ><H2
  66 >FILE FORMAT</H2
  67 ><P
  68 >The file consists of sections and parameters. A section
  69         begins with the name of the section in square brackets and continues
  70         until the next section begins. Sections contain parameters of the
  71         form</P
  72 ><P
  73 ><TT
  74 CLASS="REPLACEABLE"
  75 ><I
  76 >name</I
  77 ></TT
  78 > = <TT
  79 CLASS="REPLACEABLE"
  80 ><I
  81 >value
  82         </I
  83 ></TT
  84 ></P
  85 ><P
  86 >The file is line-based - that is, each newline-terminated
  87         line represents either a comment, a section name or a parameter.</P
  88 ><P
  89 >Section and parameter names are not case sensitive.</P
  90 ><P
  91 >Only the first equals sign in a parameter is significant.
  92         Whitespace before or after the first equals sign is discarded.
  93         Leading, trailing and internal whitespace in section and parameter
  94         names is irrelevant. Leading and trailing whitespace in a parameter
  95         value is discarded. Internal whitespace within a parameter value
  96         is retained verbatim.</P
  97 ><P
  98 >Any line beginning with a semicolon (';') or a hash ('#')
  99         character is ignored, as are lines containing only whitespace.</P
 100 ><P
 101 >Any line ending in a '\' is continued
 102         on the next line in the customary UNIX fashion.</P
 103 ><P
 104 >The values following the equals sign in parameters are all
 105         either a string (no quotes needed) or a boolean, which may be given
 106         as yes/no, 0/1 or true/false. Case is not significant in boolean
 107         values, but is preserved in string values. Some items such as
 108         create modes are numeric.</P
 109 ></DIV
 110 ><DIV
 111 CLASS="REFSECT1"
 112 ><A
 113 NAME="AEN28"
 114 ></A
 115 ><H2
 116 >SECTION DESCRIPTIONS</H2
 117 ><P
 118 >Each section in the configuration file (except for the
 119         [global] section) describes a shared resource (known
 120         as a "share"). The section name is the name of the
 121         shared resource and the parameters within the section define
 122         the shares attributes.</P
 123 ><P
 124 >There are three special sections, [global],
 125         [homes] and [printers], which are
 126         described under <EM
 127 >special sections</EM
 128 >. The
 129         following notes apply to ordinary section descriptions.</P
 130 ><P
 131 >A share consists of a directory to which access is being
 132         given plus a description of the access rights which are granted
 133         to the user of the service. Some housekeeping options are
 134         also specifiable.</P
 135 ><P
 136 >Sections are either file share services (used by the
 137         client as an extension of their native file systems) or
 138         printable services (used by the client to access print services
 139         on the host running the server).</P
 140 ><P
 141 >Sections may be designated <EM
 142 >guest</EM
 143 > services,
 144         in which case no password is required to access them. A specified
 145         UNIX <EM
 146 >guest account</EM
 147 > is used to define access
 148         privileges in this case.</P
 149 ><P
 150 >Sections other than guest services will require a password
 151         to access them. The client provides the username. As older clients
 152         only provide passwords and not usernames, you may specify a list
 153         of usernames to check against the password using the "user ="
 154         option in the share definition. For modern clients such as
 155         Windows 95/98/ME/NT/2000, this should not be necessary.</P
 156 ><P
 157 >Note that the access rights granted by the server are
 158         masked by the access rights granted to the specified or guest
 159         UNIX user by the host system. The server does not grant more
 160         access than the host system grants.</P
 161 ><P
 162 >The following sample section defines a file space share.
 163         The user has write access to the path <TT
 164 CLASS="FILENAME"
 165 >/home/bar</TT
 166 >.
 167         The share is accessed via the share name "foo":</P
 168 ><TABLE
 169 BORDER="0"
 170 BGCOLOR="#E0E0E0"
 171 WIDTH="100%"
 172 ><TR
 173 ><TD
 174 ><PRE
 175 CLASS="SCREEN"
 176 >       <TT
 177 CLASS="COMPUTEROUTPUT"
 178 >       [foo]
 179                 path = /home/bar
 180                 read only = no
 181         </TT
 182 >
 183         </PRE
 184 ></TD
 185 ></TR
 186 ></TABLE
 187 ><P
 188 >The following sample section defines a printable share.
 189         The share is readonly, but printable. That is, the only write
 190         access permitted is via calls to open, write to and close a
 191         spool file. The <EM
 192 >guest ok</EM
 193 > parameter means
 194         access will be permitted as the default guest user (specified
 195         elsewhere):</P
 196 ><TABLE
 197 BORDER="0"
 198 BGCOLOR="#E0E0E0"
 199 WIDTH="100%"
 200 ><TR
 201 ><TD
 202 ><PRE
 203 CLASS="SCREEN"
 204 >       <TT
 205 CLASS="COMPUTEROUTPUT"
 206 >       [aprinter]
 207                 path = /usr/spool/public
 208                 read only = yes
 209                 printable = yes
 210                 guest ok = yes
 211         </TT
 212 >
 213         </PRE
 214 ></TD
 215 ></TR
 216 ></TABLE
 217 ></DIV
 218 ><DIV
 219 CLASS="REFSECT1"
 220 ><A
 221 NAME="AEN48"
 222 ></A
 223 ><H2
 224 >SPECIAL SECTIONS</H2
 225 ><DIV
 226 CLASS="REFSECT2"
 227 ><A
 228 NAME="AEN50"
 229 ></A
 230 ><H3
 231 >The [global] section</H3
 232 ><P
 233 >parameters in this section apply to the server
 234                 as a whole, or are defaults for sections which do not
 235                 specifically define certain items. See the notes
 236                 under PARAMETERS for more information.</P
 237 ></DIV
 238 ><DIV
 239 CLASS="REFSECT2"
 240 ><A
 241 NAME="AEN53"
 242 ></A
 243 ><H3
 244 >The [homes] section</H3
 245 ><P
 246 >If a section called homes is included in the
 247                 configuration file, services connecting clients to their
 248                 home directories can be created on the fly by the server.</P
 249 ><P
 250 >When the connection request is made, the existing
 251                 sections are scanned. If a match is found, it is used. If no
 252                 match is found, the requested section name is treated as a
 253                 user name and looked up in the local password file. If the
 254                 name exists and the correct password has been given, a share is
 255                 created by cloning the [homes] section.</P
 256 ><P
 257 >Some modifications are then made to the newly
 258                 created share:</P
 259 ><P
 260 ></P
 261 ><UL
 262 ><LI
 263 ><P
 264 >The share name is changed from homes to
 265                 the located username.</P
 266 ></LI
 267 ><LI
 268 ><P
 269 >If no path was given, the path is set to
 270                 the user's home directory.</P
 271 ></LI
 272 ></UL
 273 ><P
 274 >If you decide to use a <EM
 275 >path =</EM
 276 > line
 277                 in your [homes] section then you may find it useful
 278                 to use the %S macro. For example :</P
 279 ><P
 280 ><TT
 281 CLASS="USERINPUT"
 282 ><B
 283 >path = /data/pchome/%S</B
 284 ></TT
 285 ></P
 286 ><P
 287 >would be useful if you have different home directories
 288                 for your PCs than for UNIX access.</P
 289 ><P
 290 >This is a fast and simple way to give a large number
 291                 of clients access to their home directories with a minimum
 292                 of fuss.</P
 293 ><P
 294 >A similar process occurs if the requested section
 295                 name is "homes", except that the share name is not
 296                 changed to that of the requesting user. This method of using
 297                 the [homes] section works well if different users share
 298                 a client PC.</P
 299 ><P
 300 >The [homes] section can specify all the parameters
 301                 a normal service section can specify, though some make more sense
 302                 than others. The following is a typical and suitable [homes]
 303                 section:</P
 304 ><TABLE
 305 BORDER="0"
 306 BGCOLOR="#E0E0E0"
 307 WIDTH="100%"
 308 ><TR
 309 ><TD
 310 ><PRE
 311 CLASS="SCREEN"
 312 >               <TT
 313 CLASS="COMPUTEROUTPUT"
 314 >               [homes]
 315                         read only = no
 316                 </TT
 317 >
 318                 </PRE
 319 ></TD
 320 ></TR
 321 ></TABLE
 322 ><P
 323 >An important point is that if guest access is specified
 324                 in the [homes] section, all home directories will be
 325                 visible to all clients <EM
 326 >without a password</EM
 327 >.
 328                 In the very unlikely event that this is actually desirable, it
 329                 would be wise to also specify <EM
 330 >read only
 331                 access</EM
 332 >.</P
 333 ><P
 334 >Note that the <EM
 335 >browseable</EM
 336 > flag for
 337                 auto home directories will be inherited from the global browseable
 338                 flag, not the [homes] browseable flag. This is useful as
 339                 it means setting <EM
 340 >browseable = no</EM
 341 > in
 342                 the [homes] section will hide the [homes] share but make
 343                 any auto home directories visible.</P
 344 ></DIV
 345 ><DIV
 346 CLASS="REFSECT2"
 347 ><A
 348 NAME="AEN79"
 349 ></A
 350 ><H3
 351 >The [printers] section</H3
 352 ><P
 353 >This section works like [homes],
 354                 but for printers.</P
 355 ><P
 356 >If a [printers] section occurs in the
 357                 configuration file, users are able to connect to any printer
 358                 specified in the local host's printcap file.</P
 359 ><P
 360 >When a connection request is made, the existing sections
 361                 are scanned. If a match is found, it is used. If no match is found,
 362                 but a [homes] section exists, it is used as described
 363                 above. Otherwise, the requested section name is treated as a
 364                 printer name and the appropriate printcap file is scanned to see
 365                 if the requested section name is a valid printer share name. If
 366                 a match is found, a new printer share is created by cloning
 367                 the [printers] section.</P
 368 ><P
 369 >A few modifications are then made to the newly created
 370                 share:</P
 371 ><P
 372 ></P
 373 ><UL
 374 ><LI
 375 ><P
 376 >The share name is set to the located printer
 377                 name</P
 378 ></LI
 379 ><LI
 380 ><P
 381 >If no printer name was given, the printer name
 382                 is set to the located printer name</P
 383 ></LI
 384 ><LI
 385 ><P
 386 >If the share does not permit guest access and
 387                 no username was given, the username is set to the located
 388                 printer name.</P
 389 ></LI
 390 ></UL
 391 ><P
 392 >Note that the [printers] service MUST be
 393                 printable - if you specify otherwise, the server will refuse
 394                 to load the configuration file.</P
 395 ><P
 396 >Typically the path specified would be that of a
 397                 world-writeable spool directory with the sticky bit set on
 398                 it. A typical [printers] entry would look like
 399                 this:</P
 400 ><TABLE
 401 BORDER="0"
 402 BGCOLOR="#E0E0E0"
 403 WIDTH="100%"
 404 ><TR
 405 ><TD
 406 ><PRE
 407 CLASS="SCREEN"
 408 ><TT
 409 CLASS="COMPUTEROUTPUT"
 410 >               [printers]
 411                         path = /usr/spool/public
 412                         guest ok = yes
 413                         printable = yes
 414                 </TT
 415 ></PRE
 416 ></TD
 417 ></TR
 418 ></TABLE
 419 ><P
 420 >All aliases given for a printer in the printcap file
 421                 are legitimate printer names as far as the server is concerned.
 422                 If your printing subsystem doesn't work like that, you will have
 423                 to set up a pseudo-printcap. This is a file consisting of one or
 424                 more lines like this:</P
 425 ><TABLE
 426 BORDER="0"
 427 BGCOLOR="#E0E0E0"
 428 WIDTH="100%"
 429 ><TR
 430 ><TD
 431 ><PRE
 432 CLASS="SCREEN"
 433 >               <TT
 434 CLASS="COMPUTEROUTPUT"
 435 >               alias|alias|alias|alias...
 436                 </TT
 437 >
 438                 </PRE
 439 ></TD
 440 ></TR
 441 ></TABLE
 442 ><P
 443 >Each alias should be an acceptable printer name for
 444                 your printing subsystem. In the [global] section, specify
 445                 the new file as your printcap.  The server will then only recognize
 446                 names found in your pseudo-printcap, which of course can contain
 447                 whatever aliases you like. The same technique could be used
 448                 simply to limit access to a subset of your local printers.</P
 449 ><P
 450 >An alias, by the way, is defined as any component of the
 451                 first entry of a printcap record. Records are separated by newlines,
 452                 components (if there are more than one) are separated by vertical
 453                 bar symbols ('|').</P
 454 ><P
 455 >NOTE: On SYSV systems which use lpstat to determine what
 456                 printers are defined on the system you may be able to use
 457                 "printcap name = lpstat" to automatically obtain a list
 458                 of printers. See the "printcap name" option
 459                 for more details.</P
 460 ></DIV
 461 ></DIV
 462 ><DIV
 463 CLASS="REFSECT1"
 464 ><A
 465 NAME="AEN102"
 466 ></A
 467 ><H2
 468 >PARAMETERS</H2
 469 ><P
 470 >parameters define the specific attributes of sections.</P
 471 ><P
 472 >Some parameters are specific to the [global] section
 473         (e.g., <EM
 474 >security</EM
 475 >).  Some parameters are usable
 476         in all sections (e.g., <EM
 477 >create mode</EM
 478 >). All others
 479         are permissible only in normal sections. For the purposes of the
 480         following descriptions the [homes] and [printers]
 481         sections will be considered normal.  The letter <EM
 482 >G</EM
 483 >
 484         in parentheses indicates that a parameter is specific to the
 485         [global] section. The letter <EM
 486 >S</EM
 487 >
 488         indicates that a parameter can be specified in a service specific
 489         section. Note that all <EM
 490 >S</EM
 491 > parameters can also be specified in
 492         the [global] section - in which case they will define
 493         the default behavior for all services.</P
 494 ><P
 495 >parameters are arranged here in alphabetical order - this may
 496         not create best bedfellows, but at least you can find them! Where
 497         there are synonyms, the preferred synonym is described, others refer
 498         to the preferred synonym.</P
 499 ></DIV
 500 ><DIV
 501 CLASS="REFSECT1"
 502 ><A
 503 NAME="AEN112"
 504 ></A
 505 ><H2
 506 >VARIABLE SUBSTITUTIONS</H2
 507 ><P
 508 >Many of the strings that are settable in the config file
 509         can take substitutions. For example the option "path =
 510         /tmp/%u" would be interpreted as "path =
 511         /tmp/john" if the user connected with the username john.</P
 512 ><P
 513 >These substitutions are mostly noted in the descriptions below,
 514         but there are some general substitutions which apply whenever they
 515         might be relevant. These are:</P
 516 ><P
 517 ></P
 518 ><DIV
 519 CLASS="VARIABLELIST"
 520 ><DL
 521 ><DT
 522 >%S</DT
 523 ><DD
 524 ><P
 525 >the name of the current service, if any.</P
 526 ></DD
 527 ><DT
 528 >%P</DT
 529 ><DD
 530 ><P
 531 >the root directory of the current service,
 532                 if any.</P
 533 ></DD
 534 ><DT
 535 >%u</DT
 536 ><DD
 537 ><P
 538 >user name of the current service, if any.</P
 539 ></DD
 540 ><DT
 541 >%g</DT
 542 ><DD
 543 ><P
 544 >primary group name of %u.</P
 545 ></DD
 546 ><DT
 547 >%U</DT
 548 ><DD
 549 ><P
 550 >session user name (the user name that the client
 551                 wanted, not necessarily the same as the one they got).</P
 552 ></DD
 553 ><DT
 554 >%G</DT
 555 ><DD
 556 ><P
 557 >primary group name of %U.</P
 558 ></DD
 559 ><DT
 560 >%H</DT
 561 ><DD
 562 ><P
 563 >the home directory of the user given
 564                 by %u.</P
 565 ></DD
 566 ><DT
 567 >%v</DT
 568 ><DD
 569 ><P
 570 >the Samba version.</P
 571 ></DD
 572 ><DT
 573 >%h</DT
 574 ><DD
 575 ><P
 576 >the Internet hostname that Samba is running
 577                 on.</P
 578 ></DD
 579 ><DT
 580 >%m</DT
 581 ><DD
 582 ><P
 583 >the NetBIOS name of the client machine
 584                 (very useful).</P
 585 ></DD
 586 ><DT
 587 >%L</DT
 588 ><DD
 589 ><P
 590 >the NetBIOS name of the server. This allows you
 591                 to change your config based on what the client calls you. Your
 592                 server can have a "dual personality".</P
 593 ><P
 594 >Note that this paramater is not available when Samba listens
 595                 on port 445, as clients no longer send this information </P
 596 ></DD
 597 ><DT
 598 >%M</DT
 599 ><DD
 600 ><P
 601 >the Internet name of the client machine.
 602                 </P
 603 ></DD
 604 ><DT
 605 >%N</DT
 606 ><DD
 607 ><P
 608 >the name of your NIS home directory server.
 609                 This is obtained from your NIS auto.map entry.  If you have
 610                 not compiled Samba with the <EM
 611 >--with-automount</EM
 612 >
 613                 option then this value will be the same as %L.</P
 614 ></DD
 615 ><DT
 616 >%p</DT
 617 ><DD
 618 ><P
 619 >the path of the service's home directory,
 620                 obtained from your NIS auto.map entry. The NIS auto.map entry
 621                 is split up as "%N:%p".</P
 622 ></DD
 623 ><DT
 624 >%R</DT
 625 ><DD
 626 ><P
 627 >the selected protocol level after
 628                 protocol negotiation. It can be one of CORE, COREPLUS,
 629                 LANMAN1, LANMAN2 or NT1.</P
 630 ></DD
 631 ><DT
 632 >%d</DT
 633 ><DD
 634 ><P
 635 >The process id of the current server
 636                 process.</P
 637 ></DD
 638 ><DT
 639 >%a</DT
 640 ><DD
 641 ><P
 642 >the architecture of the remote
 643                 machine. Only some are recognized, and those may not be
 644                 100% reliable. It currently recognizes Samba, WfWg, Win95,
 645                 WinNT and Win2k. Anything else will be known as
 646                 "UNKNOWN". If it gets it wrong then sending a level
 647                 3 log to <A
 648 HREF="mailto:samba@samba.org"
 649 TARGET="_top"
 650 >samba@samba.org
 651                 </A
 652 > should allow it to be fixed.</P
 653 ></DD
 654 ><DT
 655 >%I</DT
 656 ><DD
 657 ><P
 658 >The IP address of the client machine.</P
 659 ></DD
 660 ><DT
 661 >%T</DT
 662 ><DD
 663 ><P
 664 >the current date and time.</P
 665 ></DD
 666 ><DT
 667 >%$(<TT
 668 CLASS="REPLACEABLE"
 669 ><I
 670 >envvar</I
 671 ></TT
 672 >)</DT
 673 ><DD
 674 ><P
 675 >The value of the environment variable
 676                 <TT
 677 CLASS="REPLACEABLE"
 678 ><I
 679 >envar</I
 680 ></TT
 681 >.</P
 682 ></DD
 683 ></DL
 684 ></DIV
 685 ><P
 686 >There are some quite creative things that can be done
 687         with these substitutions and other smb.conf options.</P
 688 ></DIV
 689 ><DIV
 690 CLASS="REFSECT1"
 691 ><A
 692 NAME="AEN203"
 693 ></A
 694 ><H2
 695 >NAME MANGLING</H2
 696 ><P
 697 >Samba supports "name mangling" so that DOS and
 698         Windows clients can use files that don't conform to the 8.3 format.
 699         It can also be set to adjust the case of 8.3 format filenames.</P
 700 ><P
 701 >There are several options that control the way mangling is
 702         performed, and they are grouped here rather than listed separately.
 703         For the defaults look at the output of the testparm program. </P
 704 ><P
 705 >All of these options can be set separately for each service
 706         (or globally, of course). </P
 707 ><P
 708 >The options are: </P
 709 ><P
 710 ></P
 711 ><DIV
 712 CLASS="VARIABLELIST"
 713 ><DL
 714 ><DT
 715 >mangling method</DT
 716 ><DD
 717 ><P
 718 > controls the algorithm used for the generating
 719                 the mangled names. Can take two different values, "hash" and
 720                 "hash2". "hash" is  the default and is the algorithm that has been
 721                 used in Samba for many years. "hash2" is a newer and considered
 722                 a better algorithm (generates less collisions) in the names.
 723                 However, many Win32 applications store the
 724                 mangled names and so changing to the new algorithm must not be done
 725                 lightly as these applications may break unless reinstalled.
 726                 New installations of Samba may set the default to hash2.
 727                 Default <EM
 728 >hash</EM
 729 >.</P
 730 ></DD
 731 ><DT
 732 >mangle case = yes/no</DT
 733 ><DD
 734 ><P
 735 > controls if names that have characters that
 736                 aren't of the "default" case are mangled. For example,
 737                 if this is yes then a name like "Mail" would be mangled.
 738                 Default <EM
 739 >no</EM
 740 >.</P
 741 ></DD
 742 ><DT
 743 >case sensitive = yes/no</DT
 744 ><DD
 745 ><P
 746 >controls whether filenames are case sensitive. If
 747                 they aren't then Samba must do a filename search and match on passed
 748                 names. Default <EM
 749 >no</EM
 750 >.</P
 751 ></DD
 752 ><DT
 753 >default case = upper/lower</DT
 754 ><DD
 755 ><P
 756 >controls what the default case is for new
 757                 filenames. Default <EM
 758 >lower</EM
 759 >.</P
 760 ></DD
 761 ><DT
 762 >preserve case = yes/no</DT
 763 ><DD
 764 ><P
 765 >controls if new files are created with the
 766                 case that the client passes, or if they are forced to be the
 767                 "default" case. Default <EM
 768 >yes</EM
 769 >.
 770                 </P
 771 ></DD
 772 ><DT
 773 >short preserve case = yes/no</DT
 774 ><DD
 775 ><P
 776 >controls if new files which conform to 8.3 syntax,
 777                 that is all in upper case and of suitable length, are created
 778                 upper case, or if they are forced to be the "default"
 779                 case. This option can be use with "preserve case = yes"
 780                 to permit long filenames to retain their case, while short names
 781                 are lowercased. Default <EM
 782 >yes</EM
 783 >.</P
 784 ></DD
 785 ></DL
 786 ></DIV
 787 ><P
 788 >By default, Samba 2.2 has the same semantics as a Windows
 789         NT server, in that it is case insensitive but case preserving.</P
 790 ></DIV
 791 ><DIV
 792 CLASS="REFSECT1"
 793 ><A
 794 NAME="AEN241"
 795 ></A
 796 ><H2
 797 >NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2
 798 ><P
 799 >There are a number of ways in which a user can connect
 800         to a service. The server uses the following steps in determining
 801         if it will allow a connection to a specified service. If all the
 802         steps fail, then the connection request is rejected.  However, if one of the
 803         steps succeeds, then the following steps are not checked.</P
 804 ><P
 805 >If the service is marked "guest only = yes" and the
 806         server is running with share-level security ("security = share")
 807         then steps 1 to 5 are skipped.</P
 808 ><P
 809 ></P
 810 ><OL
 811 TYPE="1"
 812 ><LI
 813 ><P
 814 >If the client has passed a username/password
 815                 pair and that username/password pair is validated by the UNIX
 816                 system's password programs then the connection is made as that
 817                 username. Note that this includes the
 818                 \\server\service%<TT
 819 CLASS="REPLACEABLE"
 820 ><I
 821 >username</I
 822 ></TT
 823 > method of passing
 824                 a username.</P
 825 ></LI
 826 ><LI
 827 ><P
 828 >If the client has previously registered a username
 829                 with the system and now supplies a correct password for that
 830                 username then the connection is allowed.</P
 831 ></LI
 832 ><LI
 833 ><P
 834 >The client's NetBIOS name and any previously
 835                 used user names are checked against the supplied password, if
 836                 they match then the connection is allowed as the corresponding
 837                 user.</P
 838 ></LI
 839 ><LI
 840 ><P
 841 >If the client has previously validated a
 842                 username/password pair with the server and the client has passed
 843                 the validation token then that username is used. </P
 844 ></LI
 845 ><LI
 846 ><P
 847 >If a "user = " field is given in the
 848                 <TT
 849 CLASS="FILENAME"
 850 >smb.conf</TT
 851 > file for the service and the client
 852                 has supplied a password, and that password matches (according to
 853                 the UNIX system's password checking) with one of the usernames
 854                 from the "user =" field then the connection is made as
 855                 the username in the "user =" line. If one
 856                 of the username in the "user =" list begins with a
 857                 '@' then that name expands to a list of names in
 858                 the group of the same name.</P
 859 ></LI
 860 ><LI
 861 ><P
 862 >If the service is a guest service then a
 863                 connection is made as the username given in the "guest
 864                 account =" for the service, irrespective of the
 865                 supplied password.</P
 866 ></LI
 867 ></OL
 868 ></DIV
 869 ><DIV
 870 CLASS="REFSECT1"
 871 ><A
 872 NAME="AEN260"
 873 ></A
 874 ><H2
 875 >COMPLETE LIST OF GLOBAL PARAMETERS</H2
 876 ><P
 877 >Here is a list of all global parameters. See the section of
 878         each parameter for details.  Note that some are synonyms.</P
 879 ><P
 880 ></P
 881 ><UL
 882 ><LI
 883 ><P
 884 ><A
 885 HREF="#ADDPRINTERCOMMAND"
 886 ><TT
 887 CLASS="PARAMETER"
 888 ><I
 889 >add printer command</I
 890 ></TT
 891 ></A
 892 ></P
 893 ></LI
 894 ><LI
 895 ><P
 896 ><A
 897 HREF="#ADDSHARECOMMAND"
 898 ><TT
 899 CLASS="PARAMETER"
 900 ><I
 901 >add share command</I
 902 ></TT
 903 ></A
 904 ></P
 905 ></LI
 906 ><LI
 907 ><P
 908 ><A
 909 HREF="#ADDUSERSCRIPT"
 910 ><TT
 911 CLASS="PARAMETER"
 912 ><I
 913 >add user script</I
 914 ></TT
 915 ></A
 916 ></P
 917 ></LI
 918 ><LI
 919 ><P
 920 ><A
 921 HREF="#ALLOWTRUSTEDDOMAINS"
 922 ><TT
 923 CLASS="PARAMETER"
 924 ><I
 925 >allow trusted domains</I
 926 ></TT
 927 ></A
 928 ></P
 929 ></LI
 930 ><LI
 931 ><P
 932 ><A
 933 HREF="#ANNOUNCEAS"
 934 ><TT
 935 CLASS="PARAMETER"
 936 ><I
 937 >announce as</I
 938 ></TT
 939 ></A
 940 ></P
 941 ></LI
 942 ><LI
 943 ><P
 944 ><A
 945 HREF="#ANNOUNCEVERSION"
 946 ><TT
 947 CLASS="PARAMETER"
 948 ><I
 949 >announce version</I
 950 ></TT
 951 ></A
 952 ></P
 953 ></LI
 954 ><LI
 955 ><P
 956 ><A
 957 HREF="#AUTOSERVICES"
 958 ><TT
 959 CLASS="PARAMETER"
 960 ><I
 961 >auto services</I
 962 ></TT
 963 ></A
 964 ></P
 965 ></LI
 966 ><LI
 967 ><P
 968 ><A
 969 HREF="#BINDINTERFACESONLY"
 970 ><TT
 971 CLASS="PARAMETER"
 972 ><I
 973 >bind interfaces only</I
 974 ></TT
 975 ></A
 976 ></P
 977 ></LI
 978 ><LI
 979 ><P
 980 ><A
 981 HREF="#BROWSELIST"
 982 ><TT
 983 CLASS="PARAMETER"
 984 ><I
 985 >browse list</I
 986 ></TT
 987 ></A
 988 ></P
 989 ></LI
 990 ><LI
 991 ><P
 992 ><A
 993 HREF="#CHANGENOTIFYTIMEOUT"
 994 ><TT
 995 CLASS="PARAMETER"
 996 ><I
 997 >change notify timeout</I
 998 ></TT
 999 ></A
1000 ></P
1001 ></LI
1002 ><LI
1003 ><P
1004 ><A
1005 HREF="#CHANGESHARECOMMAND"
1006 ><TT
1007 CLASS="PARAMETER"
1008 ><I
1009 >change share command</I
1010 ></TT
1011 ></A
1012 ></P
1013 ></LI
1014 ><LI
1015 ><P
1016 ><A
1017 HREF="#CHARACTERSET"
1018 ><TT
1019 CLASS="PARAMETER"
1020 ><I
1021 >character set</I
1022 ></TT
1023 ></A
1024 ></P
1025 ></LI
1026 ><LI
1027 ><P
1028 ><A
1029 HREF="#CLIENTCODEPAGE"
1030 ><TT
1031 CLASS="PARAMETER"
1032 ><I
1033 >client code page</I
1034 ></TT
1035 ></A
1036 ></P
1037 ></LI
1038 ><LI
1039 ><P
1040 ><A
1041 HREF="#CODEPAGEDIRECTORY"
1042 ><TT
1043 CLASS="PARAMETER"
1044 ><I
1045 >code page directory</I
1046 ></TT
1047 ></A
1048 ></P
1049 ></LI
1050 ><LI
1051 ><P
1052 ><A
1053 HREF="#CODINGSYSTEM"
1054 ><TT
1055 CLASS="PARAMETER"
1056 ><I
1057 >coding system</I
1058 ></TT
1059 ></A
1060 ></P
1061 ></LI
1062 ><LI
1063 ><P
1064 ><A
1065 HREF="#CONFIGFILE"
1066 ><TT
1067 CLASS="PARAMETER"
1068 ><I
1069 >config file</I
1070 ></TT
1071 ></A
1072 ></P
1073 ></LI
1074 ><LI
1075 ><P
1076 ><A
1077 HREF="#DEADTIME"
1078 ><TT
1079 CLASS="PARAMETER"
1080 ><I
1081 >deadtime</I
1082 ></TT
1083 ></A
1084 ></P
1085 ></LI
1086 ><LI
1087 ><P
1088 ><A
1089 HREF="#DEBUGHIRESTIMESTAMP"
1090 ><TT
1091 CLASS="PARAMETER"
1092 ><I
1093 >debug hires timestamp</I
1094 ></TT
1095 ></A
1096 ></P
1097 ></LI
1098 ><LI
1099 ><P
1100 ><A
1101 HREF="#DEBUGPID"
1102 ><TT
1103 CLASS="PARAMETER"
1104 ><I
1105 >debug pid</I
1106 ></TT
1107 ></A
1108 ></P
1109 ></LI
1110 ><LI
1111 ><P
1112 ><A
1113 HREF="#DEBUGTIMESTAMP"
1114 ><TT
1115 CLASS="PARAMETER"
1116 ><I
1117 >debug timestamp</I
1118 ></TT
1119 ></A
1120 ></P
1121 ></LI
1122 ><LI
1123 ><P
1124 ><A
1125 HREF="#DEBUGUID"
1126 ><TT
1127 CLASS="PARAMETER"
1128 ><I
1129 >debug uid</I
1130 ></TT
1131 ></A
1132 ></P
1133 ></LI
1134 ><LI
1135 ><P
1136 ><A
1137 HREF="#DEBUGLEVEL"
1138 ><TT
1139 CLASS="PARAMETER"
1140 ><I
1141 >debuglevel</I
1142 ></TT
1143 ></A
1144 ></P
1145 ></LI
1146 ><LI
1147 ><P
1148 ><A
1149 HREF="#DEFAULT"
1150 ><TT
1151 CLASS="PARAMETER"
1152 ><I
1153 >default</I
1154 ></TT
1155 ></A
1156 ></P
1157 ></LI
1158 ><LI
1159 ><P
1160 ><A
1161 HREF="#DEFAULTSERVICE"
1162 ><TT
1163 CLASS="PARAMETER"
1164 ><I
1165 >default service</I
1166 ></TT
1167 ></A
1168 ></P
1169 ></LI
1170 ><LI
1171 ><P
1172 ><A
1173 HREF="#DELETEPRINTERCOMMAND"
1174 ><TT
1175 CLASS="PARAMETER"
1176 ><I
1177 >delete printer command</I
1178 ></TT
1179 ></A
1180 ></P
1181 ></LI
1182 ><LI
1183 ><P
1184 ><A
1185 HREF="#DELETESHARECOMMAND"
1186 ><TT
1187 CLASS="PARAMETER"
1188 ><I
1189 >delete share command</I
1190 ></TT
1191 ></A
1192 ></P
1193 ></LI
1194 ><LI
1195 ><P
1196 ><A
1197 HREF="#DELETEUSERSCRIPT"
1198 ><TT
1199 CLASS="PARAMETER"
1200 ><I
1201 >delete user script</I
1202 ></TT
1203 ></A
1204 ></P
1205 ></LI
1206 ><LI
1207 ><P
1208 ><A
1209 HREF="#DFREECOMMAND"
1210 ><TT
1211 CLASS="PARAMETER"
1212 ><I
1213 >dfree command</I
1214 ></TT
1215 ></A
1216 ></P
1217 ></LI
1218 ><LI
1219 ><P
1220 ><A
1221 HREF="#DISABLESPOOLSS"
1222 ><TT
1223 CLASS="PARAMETER"
1224 ><I
1225 >disable spoolss</I
1226 ></TT
1227 ></A
1228 ></P
1229 ></LI
1230 ><LI
1231 ><P
1232 ><A
1233 HREF="#DNSPROXY"
1234 ><TT
1235 CLASS="PARAMETER"
1236 ><I
1237 >dns proxy</I
1238 ></TT
1239 ></A
1240 ></P
1241 ></LI
1242 ><LI
1243 ><P
1244 ><A
1245 HREF="#DOMAINADMINGROUP"
1246 ><TT
1247 CLASS="PARAMETER"
1248 ><I
1249 >domain admin group</I
1250 ></TT
1251 ></A
1252 ></P
1253 ></LI
1254 ><LI
1255 ><P
1256 ><A
1257 HREF="#DOMAINGUESTGROUP"
1258 ><TT
1259 CLASS="PARAMETER"
1260 ><I
1261 >domain guest group</I
1262 ></TT
1263 ></A
1264 ></P
1265 ></LI
1266 ><LI
1267 ><P
1268 ><A
1269 HREF="#DOMAINLOGONS"
1270 ><TT
1271 CLASS="PARAMETER"
1272 ><I
1273 >domain logons</I
1274 ></TT
1275 ></A
1276 ></P
1277 ></LI
1278 ><LI
1279 ><P
1280 ><A
1281 HREF="#DOMAINMASTER"
1282 ><TT
1283 CLASS="PARAMETER"
1284 ><I
1285 >domain master</I
1286 ></TT
1287 ></A
1288 ></P
1289 ></LI
1290 ><LI
1291 ><P
1292 ><A
1293 HREF="#ENCRYPTPASSWORDS"
1294 ><TT
1295 CLASS="PARAMETER"
1296 ><I
1297 >encrypt passwords</I
1298 ></TT
1299 ></A
1300 ></P
1301 ></LI
1302 ><LI
1303 ><P
1304 ><A
1305 HREF="#ENHANCEDBROWSING"
1306 ><TT
1307 CLASS="PARAMETER"
1308 ><I
1309 >enhanced browsing</I
1310 ></TT
1311 ></A
1312 ></P
1313 ></LI
1314 ><LI
1315 ><P
1316 ><A
1317 HREF="#ENUMPORTSCOMMAND"
1318 ><TT
1319 CLASS="PARAMETER"
1320 ><I
1321 >enumports command</I
1322 ></TT
1323 ></A
1324 ></P
1325 ></LI
1326 ><LI
1327 ><P
1328 ><A
1329 HREF="#GETWDCACHE"
1330 ><TT
1331 CLASS="PARAMETER"
1332 ><I
1333 >getwd cache</I
1334 ></TT
1335 ></A
1336 ></P
1337 ></LI
1338 ><LI
1339 ><P
1340 ><A
1341 HREF="#HIDELOCALUSERS"
1342 ><TT
1343 CLASS="PARAMETER"
1344 ><I
1345 >hide local users</I
1346 ></TT
1347 ></A
1348 ></P
1349 ></LI
1350 ><LI
1351 ><P
1352 ><A
1353 HREF="#HIDEUNREADABLE"
1354 ><TT
1355 CLASS="PARAMETER"
1356 ><I
1357 >hide unreadable</I
1358 ></TT
1359 ></A
1360 ></P
1361 ></LI
1362 ><LI
1363 ><P
1364 ><A
1365 HREF="#HOMEDIRMAP"
1366 ><TT
1367 CLASS="PARAMETER"
1368 ><I
1369 >homedir map</I
1370 ></TT
1371 ></A
1372 ></P
1373 ></LI
1374 ><LI
1375 ><P
1376 ><A
1377 HREF="#HOSTMSDFS"
1378 ><TT
1379 CLASS="PARAMETER"
1380 ><I
1381 >host msdfs</I
1382 ></TT
1383 ></A
1384 ></P
1385 ></LI
1386 ><LI
1387 ><P
1388 ><A
1389 HREF="#HOSTSEQUIV"
1390 ><TT
1391 CLASS="PARAMETER"
1392 ><I
1393 >hosts equiv</I
1394 ></TT
1395 ></A
1396 ></P
1397 ></LI
1398 ><LI
1399 ><P
1400 ><A
1401 HREF="#INTERFACES"
1402 ><TT
1403 CLASS="PARAMETER"
1404 ><I
1405 >interfaces</I
1406 ></TT
1407 ></A
1408 ></P
1409 ></LI
1410 ><LI
1411 ><P
1412 ><A
1413 HREF="#KEEPALIVE"
1414 ><TT
1415 CLASS="PARAMETER"
1416 ><I
1417 >keepalive</I
1418 ></TT
1419 ></A
1420 ></P
1421 ></LI
1422 ><LI
1423 ><P
1424 ><A
1425 HREF="#KERNELOPLOCKS"
1426 ><TT
1427 CLASS="PARAMETER"
1428 ><I
1429 >kernel oplocks</I
1430 ></TT
1431 ></A
1432 ></P
1433 ></LI
1434 ><LI
1435 ><P
1436 ><A
1437 HREF="#LANMANAUTH"
1438 ><TT
1439 CLASS="PARAMETER"
1440 ><I
1441 >lanman auth</I
1442 ></TT
1443 ></A
1444 ></P
1445 ></LI
1446 ><LI
1447 ><P
1448 ><A
1449 HREF="#LARGEREADWRITE"
1450 ><TT
1451 CLASS="PARAMETER"
1452 ><I
1453 >large readwrite</I
1454 ></TT
1455 ></A
1456 ></P
1457 ></LI
1458 ><LI
1459 ><P
1460 ><A
1461 HREF="#LDAPADMINDN"
1462 ><TT
1463 CLASS="PARAMETER"
1464 ><I
1465 >ldap admin dn</I
1466 ></TT
1467 ></A
1468 ></P
1469 ></LI
1470 ><LI
1471 ><P
1472 ><A
1473 HREF="#LDAPFILTER"
1474 ><TT
1475 CLASS="PARAMETER"
1476 ><I
1477 >ldap filter</I
1478 ></TT
1479 ></A
1480 ></P
1481 ></LI
1482 ><LI
1483 ><P
1484 ><A
1485 HREF="#LDAPPORT"
1486 ><TT
1487 CLASS="PARAMETER"
1488 ><I
1489 >ldap port</I
1490 ></TT
1491 ></A
1492 ></P
1493 ></LI
1494 ><LI
1495 ><P
1496 ><A
1497 HREF="#LDAPSERVER"
1498 ><TT
1499 CLASS="PARAMETER"
1500 ><I
1501 >ldap server</I
1502 ></TT
1503 ></A
1504 ></P
1505 ></LI
1506 ><LI
1507 ><P
1508 ><A
1509 HREF="#LDAPSSL"
1510 ><TT
1511 CLASS="PARAMETER"
1512 ><I
1513 >ldap ssl</I
1514 ></TT
1515 ></A
1516 ></P
1517 ></LI
1518 ><LI
1519 ><P
1520 ><A
1521 HREF="#LDAPSUFFIX"
1522 ><TT
1523 CLASS="PARAMETER"
1524 ><I
1525 >ldap suffix</I
1526 ></TT
1527 ></A
1528 ></P
1529 ></LI
1530 ><LI
1531 ><P
1532 ><A
1533 HREF="#LMANNOUNCE"
1534 ><TT
1535 CLASS="PARAMETER"
1536 ><I
1537 >lm announce</I
1538 ></TT
1539 ></A
1540 ></P
1541 ></LI
1542 ><LI
1543 ><P
1544 ><A
1545 HREF="#LMINTERVAL"
1546 ><TT
1547 CLASS="PARAMETER"
1548 ><I
1549 >lm interval</I
1550 ></TT
1551 ></A
1552 ></P
1553 ></LI
1554 ><LI
1555 ><P
1556 ><A
1557 HREF="#LOADPRINTERS"
1558 ><TT
1559 CLASS="PARAMETER"
1560 ><I
1561 >load printers</I
1562 ></TT
1563 ></A
1564 ></P
1565 ></LI
1566 ><LI
1567 ><P
1568 ><A
1569 HREF="#LOCALMASTER"
1570 ><TT
1571 CLASS="PARAMETER"
1572 ><I
1573 >local master</I
1574 ></TT
1575 ></A
1576 ></P
1577 ></LI
1578 ><LI
1579 ><P
1580 ><A
1581 HREF="#LOCKDIR"
1582 ><TT
1583 CLASS="PARAMETER"
1584 ><I
1585 >lock dir</I
1586 ></TT
1587 ></A
1588 ></P
1589 ></LI
1590 ><LI
1591 ><P
1592 ><A
1593 HREF="#LOCKDIRECTORY"
1594 ><TT
1595 CLASS="PARAMETER"
1596 ><I
1597 >lock directory</I
1598 ></TT
1599 ></A
1600 ></P
1601 ></LI
1602 ><LI
1603 ><P
1604 ><A
1605 HREF="#LOCKSPINCOUNT"
1606 ><TT
1607 CLASS="PARAMETER"
1608 ><I
1609 >lock spin count</I
1610 ></TT
1611 ></A
1612 ></P
1613 ></LI
1614 ><LI
1615 ><P
1616 ><A
1617 HREF="#LOCKSPINTIME"
1618 ><TT
1619 CLASS="PARAMETER"
1620 ><I
1621 >lock spin time</I
1622 ></TT
1623 ></A
1624 ></P
1625 ></LI
1626 ><LI
1627 ><P
1628 ><A
1629 HREF="#PIDDIRECTORY"
1630 ><TT
1631 CLASS="PARAMETER"
1632 ><I
1633 >pid directory</I
1634 ></TT
1635 ></A
1636 ></P
1637 ></LI
1638 ><LI
1639 ><P
1640 ><A
1641 HREF="#LOGFILE"
1642 ><TT
1643 CLASS="PARAMETER"
1644 ><I
1645 >log file</I
1646 ></TT
1647 ></A
1648 ></P
1649 ></LI
1650 ><LI
1651 ><P
1652 ><A
1653 HREF="#LOGLEVEL"
1654 ><TT
1655 CLASS="PARAMETER"
1656 ><I
1657 >log level</I
1658 ></TT
1659 ></A
1660 ></P
1661 ></LI
1662 ><LI
1663 ><P
1664 ><A
1665 HREF="#LOGONDRIVE"
1666 ><TT
1667 CLASS="PARAMETER"
1668 ><I
1669 >logon drive</I
1670 ></TT
1671 ></A
1672 ></P
1673 ></LI
1674 ><LI
1675 ><P
1676 ><A
1677 HREF="#LOGONHOME"
1678 ><TT
1679 CLASS="PARAMETER"
1680 ><I
1681 >logon home</I
1682 ></TT
1683 ></A
1684 ></P
1685 ></LI
1686 ><LI
1687 ><P
1688 ><A
1689 HREF="#LOGONPATH"
1690 ><TT
1691 CLASS="PARAMETER"
1692 ><I
1693 >logon path</I
1694 ></TT
1695 ></A
1696 ></P
1697 ></LI
1698 ><LI
1699 ><P
1700 ><A
1701 HREF="#LOGONSCRIPT"
1702 ><TT
1703 CLASS="PARAMETER"
1704 ><I
1705 >logon script</I
1706 ></TT
1707 ></A
1708 ></P
1709 ></LI
1710 ><LI
1711 ><P
1712 ><A
1713 HREF="#LPQCACHETIME"
1714 ><TT
1715 CLASS="PARAMETER"
1716 ><I
1717 >lpq cache time</I
1718 ></TT
1719 ></A
1720 ></P
1721 ></LI
1722 ><LI
1723 ><P
1724 ><A
1725 HREF="#MACHINEPASSWORDTIMEOUT"
1726 ><TT
1727 CLASS="PARAMETER"
1728 ><I
1729 >machine password timeout</I
1730 ></TT
1731 ></A
1732 ></P
1733 ></LI
1734 ><LI
1735 ><P
1736 ><A
1737 HREF="#MANGLEDSTACK"
1738 ><TT
1739 CLASS="PARAMETER"
1740 ><I
1741 >mangled stack</I
1742 ></TT
1743 ></A
1744 ></P
1745 ></LI
1746 ><LI
1747 ><P
1748 ><A
1749 HREF="#MANGLINGMETHOD"
1750 ><TT
1751 CLASS="PARAMETER"
1752 ><I
1753 >mangling method</I
1754 ></TT
1755 ></A
1756 ></P
1757 ></LI
1758 ><LI
1759 ><P
1760 ><A
1761 HREF="#MAPTOGUEST"
1762 ><TT
1763 CLASS="PARAMETER"
1764 ><I
1765 >map to guest</I
1766 ></TT
1767 ></A
1768 ></P
1769 ></LI
1770 ><LI
1771 ><P
1772 ><A
1773 HREF="#MAXDISKSIZE"
1774 ><TT
1775 CLASS="PARAMETER"
1776 ><I
1777 >max disk size</I
1778 ></TT
1779 ></A
1780 ></P
1781 ></LI
1782 ><LI
1783 ><P
1784 ><A
1785 HREF="#MAXLOGSIZE"
1786 ><TT
1787 CLASS="PARAMETER"
1788 ><I
1789 >max log size</I
1790 ></TT
1791 ></A
1792 ></P
1793 ></LI
1794 ><LI
1795 ><P
1796 ><A
1797 HREF="#MAXMUX"
1798 ><TT
1799 CLASS="PARAMETER"
1800 ><I
1801 >max mux</I
1802 ></TT
1803 ></A
1804 ></P
1805 ></LI
1806 ><LI
1807 ><P
1808 ><A
1809 HREF="#MAXOPENFILES"
1810 ><TT
1811 CLASS="PARAMETER"
1812 ><I
1813 >max open files</I
1814 ></TT
1815 ></A
1816 ></P
1817 ></LI
1818 ><LI
1819 ><P
1820 ><A
1821 HREF="#MAXPROTOCOL"
1822 ><TT
1823 CLASS="PARAMETER"
1824 ><I
1825 >max protocol</I
1826 ></TT
1827 ></A
1828 ></P
1829 ></LI
1830 ><LI
1831 ><P
1832 ><A
1833 HREF="#MAXSMBDPROCESSES"
1834 ><TT
1835 CLASS="PARAMETER"
1836 ><I
1837 >max smbd processes</I
1838 ></TT
1839 ></A
1840 ></P
1841 ></LI
1842 ><LI
1843 ><P
1844 ><A
1845 HREF="#MAXTTL"
1846 ><TT
1847 CLASS="PARAMETER"
1848 ><I
1849 >max ttl</I
1850 ></TT
1851 ></A
1852 ></P
1853 ></LI
1854 ><LI
1855 ><P
1856 ><A
1857 HREF="#MAXWINSTTL"
1858 ><TT
1859 CLASS="PARAMETER"
1860 ><I
1861 >max wins ttl</I
1862 ></TT
1863 ></A
1864 ></P
1865 ></LI
1866 ><LI
1867 ><P
1868 ><A
1869 HREF="#MAXXMIT"
1870 ><TT
1871 CLASS="PARAMETER"
1872 ><I
1873 >max xmit</I
1874 ></TT
1875 ></A
1876 ></P
1877 ></LI
1878 ><LI
1879 ><P
1880 ><A
1881 HREF="#MESSAGECOMMAND"
1882 ><TT
1883 CLASS="PARAMETER"
1884 ><I
1885 >message command</I
1886 ></TT
1887 ></A
1888 ></P
1889 ></LI
1890 ><LI
1891 ><P
1892 ><A
1893 HREF="#MINPASSWDLENGTH"
1894 ><TT
1895 CLASS="PARAMETER"
1896 ><I
1897 >min passwd length</I
1898 ></TT
1899 ></A
1900 ></P
1901 ></LI
1902 ><LI
1903 ><P
1904 ><A
1905 HREF="#MINPASSWORDLENGTH"
1906 ><TT
1907 CLASS="PARAMETER"
1908 ><I
1909 >min password length</I
1910 ></TT
1911 ></A
1912 ></P
1913 ></LI
1914 ><LI
1915 ><P
1916 ><A
1917 HREF="#MINPROTOCOL"
1918 ><TT
1919 CLASS="PARAMETER"
1920 ><I
1921 >min protocol</I
1922 ></TT
1923 ></A
1924 ></P
1925 ></LI
1926 ><LI
1927 ><P
1928 ><A
1929 HREF="#MINWINSTTL"
1930 ><TT
1931 CLASS="PARAMETER"
1932 ><I
1933 >min wins ttl</I
1934 ></TT
1935 ></A
1936 ></P
1937 ></LI
1938 ><LI
1939 ><P
1940 ><A
1941 HREF="#NAMERESOLVEORDER"
1942 ><TT
1943 CLASS="PARAMETER"
1944 ><I
1945 >name resolve order</I
1946 ></TT
1947 ></A
1948 ></P
1949 ></LI
1950 ><LI
1951 ><P
1952 ><A
1953 HREF="#NETBIOSALIASES"
1954 ><TT
1955 CLASS="PARAMETER"
1956 ><I
1957 >netbios aliases</I
1958 ></TT
1959 ></A
1960 ></P
1961 ></LI
1962 ><LI
1963 ><P
1964 ><A
1965 HREF="#NETBIOSNAME"
1966 ><TT
1967 CLASS="PARAMETER"
1968 ><I
1969 >netbios name</I
1970 ></TT
1971 ></A
1972 ></P
1973 ></LI
1974 ><LI
1975 ><P
1976 ><A
1977 HREF="#NETBIOSSCOPE"
1978 ><TT
1979 CLASS="PARAMETER"
1980 ><I
1981 >netbios scope</I
1982 ></TT
1983 ></A
1984 ></P
1985 ></LI
1986 ><LI
1987 ><P
1988 ><A
1989 HREF="#NISHOMEDIR"
1990 ><TT
1991 CLASS="PARAMETER"
1992 ><I
1993 >nis homedir</I
1994 ></TT
1995 ></A
1996 ></P
1997 ></LI
1998 ><LI
1999 ><P
2000 ><A
2001 HREF="#NTPIPESUPPORT"
2002 ><TT
2003 CLASS="PARAMETER"
2004 ><I
2005 >nt pipe support</I
2006 ></TT
2007 ></A
2008 ></P
2009 ></LI
2010 ><LI
2011 ><P
2012 ><A
2013 HREF="#NTSMBSUPPORT"
2014 ><TT
2015 CLASS="PARAMETER"
2016 ><I
2017 >nt smb support</I
2018 ></TT
2019 ></A
2020 ></P
2021 ></LI
2022 ><LI
2023 ><P
2024 ><A
2025 HREF="#NTSTATUSSUPPORT"
2026 ><TT
2027 CLASS="PARAMETER"
2028 ><I
2029 >nt status support</I
2030 ></TT
2031 ></A
2032 ></P
2033 ></LI
2034 ><LI
2035 ><P
2036 ><A
2037 HREF="#NULLPASSWORDS"
2038 ><TT
2039 CLASS="PARAMETER"
2040 ><I
2041 >null passwords</I
2042 ></TT
2043 ></A
2044 ></P
2045 ></LI
2046 ><LI
2047 ><P
2048 ><A
2049 HREF="#OBEYPAMRESTRICTIONS"
2050 ><TT
2051 CLASS="PARAMETER"
2052 ><I
2053 >obey pam restrictions</I
2054 ></TT
2055 ></A
2056 ></P
2057 ></LI
2058 ><LI
2059 ><P
2060 ><A
2061 HREF="#OPLOCKBREAKWAITTIME"
2062 ><TT
2063 CLASS="PARAMETER"
2064 ><I
2065 >oplock break wait time</I
2066 ></TT
2067 ></A
2068 ></P
2069 ></LI
2070 ><LI
2071 ><P
2072 ><A
2073 HREF="#OSLEVEL"
2074 ><TT
2075 CLASS="PARAMETER"
2076 ><I
2077 >os level</I
2078 ></TT
2079 ></A
2080 ></P
2081 ></LI
2082 ><LI
2083 ><P
2084 ><A
2085 HREF="#OS2DRIVERMAP"
2086 ><TT
2087 CLASS="PARAMETER"
2088 ><I
2089 >os2 driver map</I
2090 ></TT
2091 ></A
2092 ></P
2093 ></LI
2094 ><LI
2095 ><P
2096 ><A
2097 HREF="#PAMPASSWORDCHANGE"
2098 ><TT
2099 CLASS="PARAMETER"
2100 ><I
2101 >pam password change</I
2102 ></TT
2103 ></A
2104 ></P
2105 ></LI
2106 ><LI
2107 ><P
2108 ><A
2109 HREF="#PANICACTION"
2110 ><TT
2111 CLASS="PARAMETER"
2112 ><I
2113 >panic action</I
2114 ></TT
2115 ></A
2116 ></P
2117 ></LI
2118 ><LI
2119 ><P
2120 ><A
2121 HREF="#PASSWDCHAT"
2122 ><TT
2123 CLASS="PARAMETER"
2124 ><I
2125 >passwd chat</I
2126 ></TT
2127 ></A
2128 ></P
2129 ></LI
2130 ><LI
2131 ><P
2132 ><A
2133 HREF="#PASSWDCHATDEBUG"
2134 ><TT
2135 CLASS="PARAMETER"
2136 ><I
2137 >passwd chat debug</I
2138 ></TT
2139 ></A
2140 ></P
2141 ></LI
2142 ><LI
2143 ><P
2144 ><A
2145 HREF="#PASSWDPROGRAM"
2146 ><TT
2147 CLASS="PARAMETER"
2148 ><I
2149 >passwd program</I
2150 ></TT
2151 ></A
2152 ></P
2153 ></LI
2154 ><LI
2155 ><P
2156 ><A
2157 HREF="#PASSWORDLEVEL"
2158 ><TT
2159 CLASS="PARAMETER"
2160 ><I
2161 >password level</I
2162 ></TT
2163 ></A
2164 ></P
2165 ></LI
2166 ><LI
2167 ><P
2168 ><A
2169 HREF="#PASSWORDSERVER"
2170 ><TT
2171 CLASS="PARAMETER"
2172 ><I
2173 >password server</I
2174 ></TT
2175 ></A
2176 ></P
2177 ></LI
2178 ><LI
2179 ><P
2180 ><A
2181 HREF="#PREFEREDMASTER"
2182 ><TT
2183 CLASS="PARAMETER"
2184 ><I
2185 >prefered master</I
2186 ></TT
2187 ></A
2188 ></P
2189 ></LI
2190 ><LI
2191 ><P
2192 ><A
2193 HREF="#PREFERREDMASTER"
2194 ><TT
2195 CLASS="PARAMETER"
2196 ><I
2197 >preferred master</I
2198 ></TT
2199 ></A
2200 ></P
2201 ></LI
2202 ><LI
2203 ><P
2204 ><A
2205 HREF="#PRELOAD"
2206 ><TT
2207 CLASS="PARAMETER"
2208 ><I
2209 >preload</I
2210 ></TT
2211 ></A
2212 ></P
2213 ></LI
2214 ><LI
2215 ><P
2216 ><A
2217 HREF="#PRINTCAP"
2218 ><TT
2219 CLASS="PARAMETER"
2220 ><I
2221 >printcap</I
2222 ></TT
2223 ></A
2224 ></P
2225 ></LI
2226 ><LI
2227 ><P
2228 ><A
2229 HREF="#PRINTCAPNAME"
2230 ><TT
2231 CLASS="PARAMETER"
2232 ><I
2233 >printcap name</I
2234 ></TT
2235 ></A
2236 ></P
2237 ></LI
2238 ><LI
2239 ><P
2240 ><A
2241 HREF="#PRINTERDRIVERFILE"
2242 ><TT
2243 CLASS="PARAMETER"
2244 ><I
2245 >printer driver file</I
2246 ></TT
2247 ></A
2248 ></P
2249 ></LI
2250 ><LI
2251 ><P
2252 ><A
2253 HREF="#PROTOCOL"
2254 ><TT
2255 CLASS="PARAMETER"
2256 ><I
2257 >protocol</I
2258 ></TT
2259 ></A
2260 ></P
2261 ></LI
2262 ><LI
2263 ><P
2264 ><A
2265 HREF="#READBMPX"
2266 ><TT
2267 CLASS="PARAMETER"
2268 ><I
2269 >read bmpx</I
2270 ></TT
2271 ></A
2272 ></P
2273 ></LI
2274 ><LI
2275 ><P
2276 ><A
2277 HREF="#READRAW"
2278 ><TT
2279 CLASS="PARAMETER"
2280 ><I
2281 >read raw</I
2282 ></TT
2283 ></A
2284 ></P
2285 ></LI
2286 ><LI
2287 ><P
2288 ><A
2289 HREF="#READSIZE"
2290 ><TT
2291 CLASS="PARAMETER"
2292 ><I
2293 >read size</I
2294 ></TT
2295 ></A
2296 ></P
2297 ></LI
2298 ><LI
2299 ><P
2300 ><A
2301 HREF="#REMOTEANNOUNCE"
2302 ><TT
2303 CLASS="PARAMETER"
2304 ><I
2305 >remote announce</I
2306 ></TT
2307 ></A
2308 ></P
2309 ></LI
2310 ><LI
2311 ><P
2312 ><A
2313 HREF="#REMOTEBROWSESYNC"
2314 ><TT
2315 CLASS="PARAMETER"
2316 ><I
2317 >remote browse sync</I
2318 ></TT
2319 ></A
2320 ></P
2321 ></LI
2322 ><LI
2323 ><P
2324 ><A
2325 HREF="#RESTRICTANONYMOUS"
2326 ><TT
2327 CLASS="PARAMETER"
2328 ><I
2329 >restrict anonymous</I
2330 ></TT
2331 ></A
2332 ></P
2333 ></LI
2334 ><LI
2335 ><P
2336 ><A
2337 HREF="#ROOT"
2338 ><TT
2339 CLASS="PARAMETER"
2340 ><I
2341 >root</I
2342 ></TT
2343 ></A
2344 ></P
2345 ></LI
2346 ><LI
2347 ><P
2348 ><A
2349 HREF="#ROOTDIR"
2350 ><TT
2351 CLASS="PARAMETER"
2352 ><I
2353 >root dir</I
2354 ></TT
2355 ></A
2356 ></P
2357 ></LI
2358 ><LI
2359 ><P
2360 ><A
2361 HREF="#ROOTDIRECTORY"
2362 ><TT
2363 CLASS="PARAMETER"
2364 ><I
2365 >root directory</I
2366 ></TT
2367 ></A
2368 ></P
2369 ></LI
2370 ><LI
2371 ><P
2372 ><A
2373 HREF="#SECURITY"
2374 ><TT
2375 CLASS="PARAMETER"
2376 ><I
2377 >security</I
2378 ></TT
2379 ></A
2380 ></P
2381 ></LI
2382 ><LI
2383 ><P
2384 ><A
2385 HREF="#SERVERSTRING"
2386 ><TT
2387 CLASS="PARAMETER"
2388 ><I
2389 >server string</I
2390 ></TT
2391 ></A
2392 ></P
2393 ></LI
2394 ><LI
2395 ><P
2396 ><A
2397 HREF="#SHOWADDPRINTERWIZARD"
2398 ><TT
2399 CLASS="PARAMETER"
2400 ><I
2401 >show add printer wizard</I
2402 ></TT
2403 ></A
2404 ></P
2405 ></LI
2406 ><LI
2407 ><P
2408 ><A
2409 HREF="#SMBPASSWDFILE"
2410 ><TT
2411 CLASS="PARAMETER"
2412 ><I
2413 >smb passwd file</I
2414 ></TT
2415 ></A
2416 ></P
2417 ></LI
2418 ><LI
2419 ><P
2420 ><A
2421 HREF="#SOCKETADDRESS"
2422 ><TT
2423 CLASS="PARAMETER"
2424 ><I
2425 >socket address</I
2426 ></TT
2427 ></A
2428 ></P
2429 ></LI
2430 ><LI
2431 ><P
2432 ><A
2433 HREF="#SOCKETOPTIONS"
2434 ><TT
2435 CLASS="PARAMETER"
2436 ><I
2437 >socket options</I
2438 ></TT
2439 ></A
2440 ></P
2441 ></LI
2442 ><LI
2443 ><P
2444 ><A
2445 HREF="#SOURCEENVIRONMENT"
2446 ><TT
2447 CLASS="PARAMETER"
2448 ><I
2449 >source environment</I
2450 ></TT
2451 ></A
2452 ></P
2453 ></LI
2454 ><LI
2455 ><P
2456 ><A
2457 HREF="#SSL"
2458 ><TT
2459 CLASS="PARAMETER"
2460 ><I
2461 >ssl</I
2462 ></TT
2463 ></A
2464 ></P
2465 ></LI
2466 ><LI
2467 ><P
2468 ><A
2469 HREF="#SSLCACERTDIR"
2470 ><TT
2471 CLASS="PARAMETER"
2472 ><I
2473 >ssl CA certDir</I
2474 ></TT
2475 ></A
2476 ></P
2477 ></LI
2478 ><LI
2479 ><P
2480 ><A
2481 HREF="#SSLCACERTFILE"
2482 ><TT
2483 CLASS="PARAMETER"
2484 ><I
2485 >ssl CA certFile</I
2486 ></TT
2487 ></A
2488 ></P
2489 ></LI
2490 ><LI
2491 ><P
2492 ><A
2493 HREF="#SSLCIPHERS"
2494 ><TT
2495 CLASS="PARAMETER"
2496 ><I
2497 >ssl ciphers</I
2498 ></TT
2499 ></A
2500 ></P
2501 ></LI
2502 ><LI
2503 ><P
2504 ><A
2505 HREF="#SSLCLIENTCERT"
2506 ><TT
2507 CLASS="PARAMETER"
2508 ><I
2509 >ssl client cert</I
2510 ></TT
2511 ></A
2512 ></P
2513 ></LI
2514 ><LI
2515 ><P
2516 ><A
2517 HREF="#SSLCLIENTKEY"
2518 ><TT
2519 CLASS="PARAMETER"
2520 ><I
2521 >ssl client key</I
2522 ></TT
2523 ></A
2524 ></P
2525 ></LI
2526 ><LI
2527 ><P
2528 ><A
2529 HREF="#SSLCOMPATIBILITY"
2530 ><TT
2531 CLASS="PARAMETER"
2532 ><I
2533 >ssl compatibility</I
2534 ></TT
2535 ></A
2536 ></P
2537 ></LI
2538 ><LI
2539 ><P
2540 ><A
2541 HREF="#SSLEGDSOCKET"
2542 ><TT
2543 CLASS="PARAMETER"
2544 ><I
2545 >ssl egd socket</I
2546 ></TT
2547 ></A
2548 ></P
2549 ></LI
2550 ><LI
2551 ><P
2552 ><A
2553 HREF="#SSLENTROPYBYTES"
2554 ><TT
2555 CLASS="PARAMETER"
2556 ><I
2557 >ssl entropy bytes</I
2558 ></TT
2559 ></A
2560 ></P
2561 ></LI
2562 ><LI
2563 ><P
2564 ><A
2565 HREF="#SSLENTROPYFILE"
2566 ><TT
2567 CLASS="PARAMETER"
2568 ><I
2569 >ssl entropy file</I
2570 ></TT
2571 ></A
2572 ></P
2573 ></LI
2574 ><LI
2575 ><P
2576 ><A
2577 HREF="#SSLHOSTS"
2578 ><TT
2579 CLASS="PARAMETER"
2580 ><I
2581 >ssl hosts</I
2582 ></TT
2583 ></A
2584 ></P
2585 ></LI
2586 ><LI
2587 ><P
2588 ><A
2589 HREF="#SSLHOSTSRESIGN"
2590 ><TT
2591 CLASS="PARAMETER"
2592 ><I
2593 >ssl hosts resign</I
2594 ></TT
2595 ></A
2596 ></P
2597 ></LI
2598 ><LI
2599 ><P
2600 ><A
2601 HREF="#SSLREQUIRECLIENTCERT"
2602 ><TT
2603 CLASS="PARAMETER"
2604 ><I
2605 >ssl require clientcert</I
2606 ></TT
2607 ></A
2608 ></P
2609 ></LI
2610 ><LI
2611 ><P
2612 ><A
2613 HREF="#SSLREQUIRESERVERCERT"
2614 ><TT
2615 CLASS="PARAMETER"
2616 ><I
2617 >ssl require servercert</I
2618 ></TT
2619 ></A
2620 ></P
2621 ></LI
2622 ><LI
2623 ><P
2624 ><A
2625 HREF="#SSLSERVERCERT"
2626 ><TT
2627 CLASS="PARAMETER"
2628 ><I
2629 >ssl server cert</I
2630 ></TT
2631 ></A
2632 ></P
2633 ></LI
2634 ><LI
2635 ><P
2636 ><A
2637 HREF="#SSLSERVERKEY"
2638 ><TT
2639 CLASS="PARAMETER"
2640 ><I
2641 >ssl server key</I
2642 ></TT
2643 ></A
2644 ></P
2645 ></LI
2646 ><LI
2647 ><P
2648 ><A
2649 HREF="#SSLVERSION"
2650 ><TT
2651 CLASS="PARAMETER"
2652 ><I
2653 >ssl version</I
2654 ></TT
2655 ></A
2656 ></P
2657 ></LI
2658 ><LI
2659 ><P
2660 ><A
2661 HREF="#STATCACHE"
2662 ><TT
2663 CLASS="PARAMETER"
2664 ><I
2665 >stat cache</I
2666 ></TT
2667 ></A
2668 ></P
2669 ></LI
2670 ><LI
2671 ><P
2672 ><A
2673 HREF="#STATCACHESIZE"
2674 ><TT
2675 CLASS="PARAMETER"
2676 ><I
2677 >stat cache size</I
2678 ></TT
2679 ></A
2680 ></P
2681 ></LI
2682 ><LI
2683 ><P
2684 ><A
2685 HREF="#STRIPDOT"
2686 ><TT
2687 CLASS="PARAMETER"
2688 ><I
2689 >strip dot</I
2690 ></TT
2691 ></A
2692 ></P
2693 ></LI
2694 ><LI
2695 ><P
2696 ><A
2697 HREF="#SYSLOG"
2698 ><TT
2699 CLASS="PARAMETER"
2700 ><I
2701 >syslog</I
2702 ></TT
2703 ></A
2704 ></P
2705 ></LI
2706 ><LI
2707 ><P
2708 ><A
2709 HREF="#SYSLOGONLY"
2710 ><TT
2711 CLASS="PARAMETER"
2712 ><I
2713 >syslog only</I
2714 ></TT
2715 ></A
2716 ></P
2717 ></LI
2718 ><LI
2719 ><P
2720 ><A
2721 HREF="#TEMPLATEHOMEDIR"
2722 ><TT
2723 CLASS="PARAMETER"
2724 ><I
2725 >template homedir</I
2726 ></TT
2727 ></A
2728 ></P
2729 ></LI
2730 ><LI
2731 ><P
2732 ><A
2733 HREF="#TEMPLATESHELL"
2734 ><TT
2735 CLASS="PARAMETER"
2736 ><I
2737 >template shell</I
2738 ></TT
2739 ></A
2740 ></P
2741 ></LI
2742 ><LI
2743 ><P
2744 ><A
2745 HREF="#TIMEOFFSET"
2746 ><TT
2747 CLASS="PARAMETER"
2748 ><I
2749 >time offset</I
2750 ></TT
2751 ></A
2752 ></P
2753 ></LI
2754 ><LI
2755 ><P
2756 ><A
2757 HREF="#TIMESERVER"
2758 ><TT
2759 CLASS="PARAMETER"
2760 ><I
2761 >time server</I
2762 ></TT
2763 ></A
2764 ></P
2765 ></LI
2766 ><LI
2767 ><P
2768 ><A
2769 HREF="#TIMESTAMPLOGS"
2770 ><TT
2771 CLASS="PARAMETER"
2772 ><I
2773 >timestamp logs</I
2774 ></TT
2775 ></A
2776 ></P
2777 ></LI
2778 ><LI
2779 ><P
2780 ><A
2781 HREF="#TOTALPRINTJOBS"
2782 ><TT
2783 CLASS="PARAMETER"
2784 ><I
2785 >total print jobs</I
2786 ></TT
2787 ></A
2788 ></P
2789 ></LI
2790 ><LI
2791 ><P
2792 ><A
2793 HREF="#UNIXEXTENSIONS"
2794 ><TT
2795 CLASS="PARAMETER"
2796 ><I
2797 >unix extensions</I
2798 ></TT
2799 ></A
2800 ></P
2801 ></LI
2802 ><LI
2803 ><P
2804 ><A
2805 HREF="#UNIXPASSWORDSYNC"
2806 ><TT
2807 CLASS="PARAMETER"
2808 ><I
2809 >unix password sync</I
2810 ></TT
2811 ></A
2812 ></P
2813 ></LI
2814 ><LI
2815 ><P
2816 ><A
2817 HREF="#UPDATEENCRYPTED"
2818 ><TT
2819 CLASS="PARAMETER"
2820 ><I
2821 >update encrypted</I
2822 ></TT
2823 ></A
2824 ></P
2825 ></LI
2826 ><LI
2827 ><P
2828 ><A
2829 HREF="#USEMMAP"
2830 ><TT
2831 CLASS="PARAMETER"
2832 ><I
2833 >use mmap</I
2834 ></TT
2835 ></A
2836 ></P
2837 ></LI
2838 ><LI
2839 ><P
2840 ><A
2841 HREF="#USERHOSTS"
2842 ><TT
2843 CLASS="PARAMETER"
2844 ><I
2845 >use rhosts</I
2846 ></TT
2847 ></A
2848 ></P
2849 ></LI
2850 ><LI
2851 ><P
2852 ><A
2853 HREF="#USESENDFILE"
2854 ><TT
2855 CLASS="PARAMETER"
2856 ><I
2857 >use sendfile</I
2858 ></TT
2859 ></A
2860 ></P
2861 ></LI
2862 ><LI
2863 ><P
2864 ><A
2865 HREF="#USERNAMELEVEL"
2866 ><TT
2867 CLASS="PARAMETER"
2868 ><I
2869 >username level</I
2870 ></TT
2871 ></A
2872 ></P
2873 ></LI
2874 ><LI
2875 ><P
2876 ><A
2877 HREF="#USERNAMEMAP"
2878 ><TT
2879 CLASS="PARAMETER"
2880 ><I
2881 >username map</I
2882 ></TT
2883 ></A
2884 ></P
2885 ></LI
2886 ><LI
2887 ><P
2888 ><A
2889 HREF="#UTMP"
2890 ><TT
2891 CLASS="PARAMETER"
2892 ><I
2893 >utmp</I
2894 ></TT
2895 ></A
2896 ></P
2897 ></LI
2898 ><LI
2899 ><P
2900 ><A
2901 HREF="#UTMPDIRECTORY"
2902 ><TT
2903 CLASS="PARAMETER"
2904 ><I
2905 >utmp directory</I
2906 ></TT
2907 ></A
2908 ></P
2909 ></LI
2910 ><LI
2911 ><P
2912 ><A
2913 HREF="#VALIDCHARS"
2914 ><TT
2915 CLASS="PARAMETER"
2916 ><I
2917 >valid chars</I
2918 ></TT
2919 ></A
2920 ></P
2921 ></LI
2922 ><LI
2923 ><P
2924 ><A
2925 HREF="#WINBINDCACHETIME"
2926 ><TT
2927 CLASS="PARAMETER"
2928 ><I
2929 >winbind cache time</I
2930 ></TT
2931 ></A
2932 ></P
2933 ></LI
2934 ><LI
2935 ><P
2936 ><A
2937 HREF="#WINBINDENUMUSERS"
2938 ><TT
2939 CLASS="PARAMETER"
2940 ><I
2941 >winbind enum users</I
2942 ></TT
2943 ></A
2944 ></P
2945 ></LI
2946 ><LI
2947 ><P
2948 ><A
2949 HREF="#WINBINDENUMGROUPS"
2950 ><TT
2951 CLASS="PARAMETER"
2952 ><I
2953 >winbind enum groups</I
2954 ></TT
2955 ></A
2956 ></P
2957 ></LI
2958 ><LI
2959 ><P
2960 ><A
2961 HREF="#WINBINDGID"
2962 ><TT
2963 CLASS="PARAMETER"
2964 ><I
2965 >winbind gid</I
2966 ></TT
2967 ></A
2968 ></P
2969 ></LI
2970 ><LI
2971 ><P
2972 ><A
2973 HREF="#WINBINDSEPARATOR"
2974 ><TT
2975 CLASS="PARAMETER"
2976 ><I
2977 >winbind separator</I
2978 ></TT
2979 ></A
2980 ></P
2981 ></LI
2982 ><LI
2983 ><P
2984 ><A
2985 HREF="#WINBINDUID"
2986 ><TT
2987 CLASS="PARAMETER"
2988 ><I
2989 >winbind uid</I
2990 ></TT
2991 ></A
2992 ></P
2993 ></LI
2994 ><LI
2995 ><P
2996 ><A
2997 HREF="#WINBINDUSEDEFAULTDOMAIN"
2998 ><TT
2999 CLASS="PARAMETER"
3000 ><I
3001 >winbind use default domain</I
3002 ></TT
3003 ></A
3004 ></P
3005 ></LI
3006 ><LI
3007 ><P
3008 ><A
3009 HREF="#WINSHOOK"
3010 ><TT
3011 CLASS="PARAMETER"
3012 ><I
3013 >wins hook</I
3014 ></TT
3015 ></A
3016 ></P
3017 ></LI
3018 ><LI
3019 ><P
3020 ><A
3021 HREF="#WINSPROXY"
3022 ><TT
3023 CLASS="PARAMETER"
3024 ><I
3025 >wins proxy</I
3026 ></TT
3027 ></A
3028 ></P
3029 ></LI
3030 ><LI
3031 ><P
3032 ><A
3033 HREF="#WINSSERVER"
3034 ><TT
3035 CLASS="PARAMETER"
3036 ><I
3037 >wins server</I
3038 ></TT
3039 ></A
3040 ></P
3041 ></LI
3042 ><LI
3043 ><P
3044 ><A
3045 HREF="#WINSSUPPORT"
3046 ><TT
3047 CLASS="PARAMETER"
3048 ><I
3049 >wins support</I
3050 ></TT
3051 ></A
3052 ></P
3053 ></LI
3054 ><LI
3055 ><P
3056 ><A
3057 HREF="#WORKGROUP"
3058 ><TT
3059 CLASS="PARAMETER"
3060 ><I
3061 >workgroup</I
3062 ></TT
3063 ></A
3064 ></P
3065 ></LI
3066 ><LI
3067 ><P
3068 ><A
3069 HREF="#WRITERAW"
3070 ><TT
3071 CLASS="PARAMETER"
3072 ><I
3073 >write raw</I
3074 ></TT
3075 ></A
3076 ></P
3077 ></LI
3078 ></UL
3079 ></DIV
3080 ><DIV
3081 CLASS="REFSECT1"
3082 ><A
3083 NAME="AEN996"
3084 ></A
3085 ><H2
3086 >COMPLETE LIST OF SERVICE PARAMETERS</H2
3087 ><P
3088 >Here is a list of all service parameters. See the section on
3089         each parameter for details. Note that some are synonyms.</P
3090 ><P
3091 ></P
3092 ><UL
3093 ><LI
3094 ><P
3095 ><A
3096 HREF="#ADMINUSERS"
3097 ><TT
3098 CLASS="PARAMETER"
3099 ><I
3100 >admin users</I
3101 ></TT
3102 ></A
3103 ></P
3104 ></LI
3105 ><LI
3106 ><P
3107 ><A
3108 HREF="#ALLOWHOSTS"
3109 ><TT
3110 CLASS="PARAMETER"
3111 ><I
3112 >allow hosts</I
3113 ></TT
3114 ></A
3115 ></P
3116 ></LI
3117 ><LI
3118 ><P
3119 ><A
3120 HREF="#AVAILABLE"
3121 ><TT
3122 CLASS="PARAMETER"
3123 ><I
3124 >available</I
3125 ></TT
3126 ></A
3127 ></P
3128 ></LI
3129 ><LI
3130 ><P
3131 ><A
3132 HREF="#BLOCKINGLOCKS"
3133 ><TT
3134 CLASS="PARAMETER"
3135 ><I
3136 >blocking locks</I
3137 ></TT
3138 ></A
3139 ></P
3140 ></LI
3141 ><LI
3142 ><P
3143 ><A
3144 HREF="#BLOCKSIZE"
3145 ><TT
3146 CLASS="PARAMETER"
3147 ><I
3148 >block size</I
3149 ></TT
3150 ></A
3151 ></P
3152 ></LI
3153 ><LI
3154 ><P
3155 ><A
3156 HREF="#BROWSABLE"
3157 ><TT
3158 CLASS="PARAMETER"
3159 ><I
3160 >browsable</I
3161 ></TT
3162 ></A
3163 ></P
3164 ></LI
3165 ><LI
3166 ><P
3167 ><A
3168 HREF="#BROWSEABLE"
3169 ><TT
3170 CLASS="PARAMETER"
3171 ><I
3172 >browseable</I
3173 ></TT
3174 ></A
3175 ></P
3176 ></LI
3177 ><LI
3178 ><P
3179 ><A
3180 HREF="#CASESENSITIVE"
3181 ><TT
3182 CLASS="PARAMETER"
3183 ><I
3184 >case sensitive</I
3185 ></TT
3186 ></A
3187 ></P
3188 ></LI
3189 ><LI
3190 ><P
3191 ><A
3192 HREF="#CASESIGNAMES"
3193 ><TT
3194 CLASS="PARAMETER"
3195 ><I
3196 >casesignames</I
3197 ></TT
3198 ></A
3199 ></P
3200 ></LI
3201 ><LI
3202 ><P
3203 ><A
3204 HREF="#COMMENT"
3205 ><TT
3206 CLASS="PARAMETER"
3207 ><I
3208 >comment</I
3209 ></TT
3210 ></A
3211 ></P
3212 ></LI
3213 ><LI
3214 ><P
3215 ><A
3216 HREF="#COPY"
3217 ><TT
3218 CLASS="PARAMETER"
3219 ><I
3220 >copy</I
3221 ></TT
3222 ></A
3223 ></P
3224 ></LI
3225 ><LI
3226 ><P
3227 ><A
3228 HREF="#CREATEMASK"
3229 ><TT
3230 CLASS="PARAMETER"
3231 ><I
3232 >create mask</I
3233 ></TT
3234 ></A
3235 ></P
3236 ></LI
3237 ><LI
3238 ><P
3239 ><A
3240 HREF="#CREATEMODE"
3241 ><TT
3242 CLASS="PARAMETER"
3243 ><I
3244 >create mode</I
3245 ></TT
3246 ></A
3247 ></P
3248 ></LI
3249 ><LI
3250 ><P
3251 ><A
3252 HREF="#CSCPOLICY"
3253 ><TT
3254 CLASS="PARAMETER"
3255 ><I
3256 >csc policy</I
3257 ></TT
3258 ></A
3259 ></P
3260 ></LI
3261 ><LI
3262 ><P
3263 ><A
3264 HREF="#DEFAULTCASE"
3265 ><TT
3266 CLASS="PARAMETER"
3267 ><I
3268 >default case</I
3269 ></TT
3270 ></A
3271 ></P
3272 ></LI
3273 ><LI
3274 ><P
3275 ><A
3276 HREF="#DEFAULTDEVMODE"
3277 ><TT
3278 CLASS="PARAMETER"
3279 ><I
3280 >default devmode</I
3281 ></TT
3282 ></A
3283 ></P
3284 ></LI
3285 ><LI
3286 ><P
3287 ><A
3288 HREF="#DELETEREADONLY"
3289 ><TT
3290 CLASS="PARAMETER"
3291 ><I
3292 >delete readonly</I
3293 ></TT
3294 ></A
3295 ></P
3296 ></LI
3297 ><LI
3298 ><P
3299 ><A
3300 HREF="#DELETEVETOFILES"
3301 ><TT
3302 CLASS="PARAMETER"
3303 ><I
3304 >delete veto files</I
3305 ></TT
3306 ></A
3307 ></P
3308 ></LI
3309 ><LI
3310 ><P
3311 ><A
3312 HREF="#DENYHOSTS"
3313 ><TT
3314 CLASS="PARAMETER"
3315 ><I
3316 >deny hosts</I
3317 ></TT
3318 ></A
3319 ></P
3320 ></LI
3321 ><LI
3322 ><P
3323 ><A
3324 HREF="#DIRECTORY"
3325 ><TT
3326 CLASS="PARAMETER"
3327 ><I
3328 >directory</I
3329 ></TT
3330 ></A
3331 ></P
3332 ></LI
3333 ><LI
3334 ><P
3335 ><A
3336 HREF="#DIRECTORYMASK"
3337 ><TT
3338 CLASS="PARAMETER"
3339 ><I
3340 >directory mask</I
3341 ></TT
3342 ></A
3343 ></P
3344 ></LI
3345 ><LI
3346 ><P
3347 ><A
3348 HREF="#DIRECTORYMODE"
3349 ><TT
3350 CLASS="PARAMETER"
3351 ><I
3352 >directory mode</I
3353 ></TT
3354 ></A
3355 ></P
3356 ></LI
3357 ><LI
3358 ><P
3359 ><A
3360 HREF="#DIRECTORYSECURITYMASK"
3361 ><TT
3362 CLASS="PARAMETER"
3363 ><I
3364 >directory security mask</I
3365 ></TT
3366 ></A
3367 ></P
3368 ></LI
3369 ><LI
3370 ><P
3371 ><A
3372 HREF="#DONTDESCEND"
3373 ><TT
3374 CLASS="PARAMETER"
3375 ><I
3376 >dont descend</I
3377 ></TT
3378 ></A
3379 ></P
3380 ></LI
3381 ><LI
3382 ><P
3383 ><A
3384 HREF="#DOSFILEMODE"
3385 ><TT
3386 CLASS="PARAMETER"
3387 ><I
3388 >dos filemode</I
3389 ></TT
3390 ></A
3391 ></P
3392 ></LI
3393 ><LI
3394 ><P
3395 ><A
3396 HREF="#DOSFILETIMERESOLUTION"
3397 ><TT
3398 CLASS="PARAMETER"
3399 ><I
3400 >dos filetime resolution</I
3401 ></TT
3402 ></A
3403 ></P
3404 ></LI
3405 ><LI
3406 ><P
3407 ><A
3408 HREF="#DOSFILETIMES"
3409 ><TT
3410 CLASS="PARAMETER"
3411 ><I
3412 >dos filetimes</I
3413 ></TT
3414 ></A
3415 ></P
3416 ></LI
3417 ><LI
3418 ><P
3419 ><A
3420 HREF="#EXEC"
3421 ><TT
3422 CLASS="PARAMETER"
3423 ><I
3424 >exec</I
3425 ></TT
3426 ></A
3427 ></P
3428 ></LI
3429 ><LI
3430 ><P
3431 ><A
3432 HREF="#FAKEDIRECTORYCREATETIMES"
3433 ><TT
3434 CLASS="PARAMETER"
3435 ><I
3436 >fake directory create times</I
3437 ></TT
3438 ></A
3439 ></P
3440 ></LI
3441 ><LI
3442 ><P
3443 ><A
3444 HREF="#FAKEOPLOCKS"
3445 ><TT
3446 CLASS="PARAMETER"
3447 ><I
3448 >fake oplocks</I
3449 ></TT
3450 ></A
3451 ></P
3452 ></LI
3453 ><LI
3454 ><P
3455 ><A
3456 HREF="#FOLLOWSYMLINKS"
3457 ><TT
3458 CLASS="PARAMETER"
3459 ><I
3460 >follow symlinks</I
3461 ></TT
3462 ></A
3463 ></P
3464 ></LI
3465 ><LI
3466 ><P
3467 ><A
3468 HREF="#FORCECREATEMODE"
3469 ><TT
3470 CLASS="PARAMETER"
3471 ><I
3472 >force create mode</I
3473 ></TT
3474 ></A
3475 ></P
3476 ></LI
3477 ><LI
3478 ><P
3479 ><A
3480 HREF="#FORCEDIRECTORYMODE"
3481 ><TT
3482 CLASS="PARAMETER"
3483 ><I
3484 >force directory mode</I
3485 ></TT
3486 ></A
3487 ></P
3488 ></LI
3489 ><LI
3490 ><P
3491 ><A
3492 HREF="#FORCEDIRECTORYSECURITYMODE"
3493 ><TT
3494 CLASS="PARAMETER"
3495 ><I
3496 >force directory security mode</I
3497 ></TT
3498 ></A
3499 ></P
3500 ></LI
3501 ><LI
3502 ><P
3503 ><A
3504 HREF="#FORCEGROUP"
3505 ><TT
3506 CLASS="PARAMETER"
3507 ><I
3508 >force group</I
3509 ></TT
3510 ></A
3511 ></P
3512 ></LI
3513 ><LI
3514 ><P
3515 ><A
3516 HREF="#FORCESECURITYMODE"
3517 ><TT
3518 CLASS="PARAMETER"
3519 ><I
3520 >force security mode</I
3521 ></TT
3522 ></A
3523 ></P
3524 ></LI
3525 ><LI
3526 ><P
3527 ><A
3528 HREF="#FORCEUNKNOWNACLUSER"
3529 ><TT
3530 CLASS="PARAMETER"
3531 ><I
3532 >force unknown acl user</I
3533 ></TT
3534 ></A
3535 ></P
3536 ></LI
3537 ><LI
3538 ><P
3539 ><A
3540 HREF="#FORCEUSER"
3541 ><TT
3542 CLASS="PARAMETER"
3543 ><I
3544 >force user</I
3545 ></TT
3546 ></A
3547 ></P
3548 ></LI
3549 ><LI
3550 ><P
3551 ><A
3552 HREF="#FSTYPE"
3553 ><TT
3554 CLASS="PARAMETER"
3555 ><I
3556 >fstype</I
3557 ></TT
3558 ></A
3559 ></P
3560 ></LI
3561 ><LI
3562 ><P
3563 ><A
3564 HREF="#GROUP"
3565 ><TT
3566 CLASS="PARAMETER"
3567 ><I
3568 >group</I
3569 ></TT
3570 ></A
3571 ></P
3572 ></LI
3573 ><LI
3574 ><P
3575 ><A
3576 HREF="#GUESTACCOUNT"
3577 ><TT
3578 CLASS="PARAMETER"
3579 ><I
3580 >guest account</I
3581 ></TT
3582 ></A
3583 ></P
3584 ></LI
3585 ><LI
3586 ><P
3587 ><A
3588 HREF="#GUESTOK"
3589 ><TT
3590 CLASS="PARAMETER"
3591 ><I
3592 >guest ok</I
3593 ></TT
3594 ></A
3595 ></P
3596 ></LI
3597 ><LI
3598 ><P
3599 ><A
3600 HREF="#GUESTONLY"
3601 ><TT
3602 CLASS="PARAMETER"
3603 ><I
3604 >guest only</I
3605 ></TT
3606 ></A
3607 ></P
3608 ></LI
3609 ><LI
3610 ><P
3611 ><A
3612 HREF="#HIDEDOTFILES"
3613 ><TT
3614 CLASS="PARAMETER"
3615 ><I
3616 >hide dot files</I
3617 ></TT
3618 ></A
3619 ></P
3620 ></LI
3621 ><LI
3622 ><P
3623 ><A
3624 HREF="#HIDEFILES"
3625 ><TT
3626 CLASS="PARAMETER"
3627 ><I
3628 >hide files</I
3629 ></TT
3630 ></A
3631 ></P
3632 ></LI
3633 ><LI
3634 ><P
3635 ><A
3636 HREF="#HOSTSALLOW"
3637 ><TT
3638 CLASS="PARAMETER"
3639 ><I
3640 >hosts allow</I
3641 ></TT
3642 ></A
3643 ></P
3644 ></LI
3645 ><LI
3646 ><P
3647 ><A
3648 HREF="#HOSTSDENY"
3649 ><TT
3650 CLASS="PARAMETER"
3651 ><I
3652 >hosts deny</I
3653 ></TT
3654 ></A
3655 ></P
3656 ></LI
3657 ><LI
3658 ><P
3659 ><A
3660 HREF="#INCLUDE"
3661 ><TT
3662 CLASS="PARAMETER"
3663 ><I
3664 >include</I
3665 ></TT
3666 ></A
3667 ></P
3668 ></LI
3669 ><LI
3670 ><P
3671 ><A
3672 HREF="#INHERITACLS"
3673 ><TT
3674 CLASS="PARAMETER"
3675 ><I
3676 >inherit acls</I
3677 ></TT
3678 ></A
3679 ></P
3680 ></LI
3681 ><LI
3682 ><P
3683 ><A
3684 HREF="#INHERITPERMISSIONS"
3685 ><TT
3686 CLASS="PARAMETER"
3687 ><I
3688 >inherit permissions</I
3689 ></TT
3690 ></A
3691 ></P
3692 ></LI
3693 ><LI
3694 ><P
3695 ><A
3696 HREF="#INVALIDUSERS"
3697 ><TT
3698 CLASS="PARAMETER"
3699 ><I
3700 >invalid users</I
3701 ></TT
3702 ></A
3703 ></P
3704 ></LI
3705 ><LI
3706 ><P
3707 ><A
3708 HREF="#LEVEL2OPLOCKS"
3709 ><TT
3710 CLASS="PARAMETER"
3711 ><I
3712 >level2 oplocks</I
3713 ></TT
3714 ></A
3715 ></P
3716 ></LI
3717 ><LI
3718 ><P
3719 ><A
3720 HREF="#LOCKING"
3721 ><TT
3722 CLASS="PARAMETER"
3723 ><I
3724 >locking</I
3725 ></TT
3726 ></A
3727 ></P
3728 ></LI
3729 ><LI
3730 ><P
3731 ><A
3732 HREF="#LPPAUSECOMMAND"
3733 ><TT
3734 CLASS="PARAMETER"
3735 ><I
3736 >lppause command</I
3737 ></TT
3738 ></A
3739 ></P
3740 ></LI
3741 ><LI
3742 ><P
3743 ><A
3744 HREF="#LPQCOMMAND"
3745 ><TT
3746 CLASS="PARAMETER"
3747 ><I
3748 >lpq command</I
3749 ></TT
3750 ></A
3751 ></P
3752 ></LI
3753 ><LI
3754 ><P
3755 ><A
3756 HREF="#LPRESUMECOMMAND"
3757 ><TT
3758 CLASS="PARAMETER"
3759 ><I
3760 >lpresume command</I
3761 ></TT
3762 ></A
3763 ></P
3764 ></LI
3765 ><LI
3766 ><P
3767 ><A
3768 HREF="#LPRMCOMMAND"
3769 ><TT
3770 CLASS="PARAMETER"
3771 ><I
3772 >lprm command</I
3773 ></TT
3774 ></A
3775 ></P
3776 ></LI
3777 ><LI
3778 ><P
3779 ><A
3780 HREF="#MAGICOUTPUT"
3781 ><TT
3782 CLASS="PARAMETER"
3783 ><I
3784 >magic output</I
3785 ></TT
3786 ></A
3787 ></P
3788 ></LI
3789 ><LI
3790 ><P
3791 ><A
3792 HREF="#MAGICSCRIPT"
3793 ><TT
3794 CLASS="PARAMETER"
3795 ><I
3796 >magic script</I
3797 ></TT
3798 ></A
3799 ></P
3800 ></LI
3801 ><LI
3802 ><P
3803 ><A
3804 HREF="#MANGLECASE"
3805 ><TT
3806 CLASS="PARAMETER"
3807 ><I
3808 >mangle case</I
3809 ></TT
3810 ></A
3811 ></P
3812 ></LI
3813 ><LI
3814 ><P
3815 ><A
3816 HREF="#MANGLEDMAP"
3817 ><TT
3818 CLASS="PARAMETER"
3819 ><I
3820 >mangled map</I
3821 ></TT
3822 ></A
3823 ></P
3824 ></LI
3825 ><LI
3826 ><P
3827 ><A
3828 HREF="#MANGLEDNAMES"
3829 ><TT
3830 CLASS="PARAMETER"
3831 ><I
3832 >mangled names</I
3833 ></TT
3834 ></A
3835 ></P
3836 ></LI
3837 ><LI
3838 ><P
3839 ><A
3840 HREF="#MANGLINGCHAR"
3841 ><TT
3842 CLASS="PARAMETER"
3843 ><I
3844 >mangling char</I
3845 ></TT
3846 ></A
3847 ></P
3848 ></LI
3849 ><LI
3850 ><P
3851 ><A
3852 HREF="#MAPARCHIVE"
3853 ><TT
3854 CLASS="PARAMETER"
3855 ><I
3856 >map archive</I
3857 ></TT
3858 ></A
3859 ></P
3860 ></LI
3861 ><LI
3862 ><P
3863 ><A
3864 HREF="#MAPHIDDEN"
3865 ><TT
3866 CLASS="PARAMETER"
3867 ><I
3868 >map hidden</I
3869 ></TT
3870 ></A
3871 ></P
3872 ></LI
3873 ><LI
3874 ><P
3875 ><A
3876 HREF="#MAPSYSTEM"
3877 ><TT
3878 CLASS="PARAMETER"
3879 ><I
3880 >map system</I
3881 ></TT
3882 ></A
3883 ></P
3884 ></LI
3885 ><LI
3886 ><P
3887 ><A
3888 HREF="#MAXCONNECTIONS"
3889 ><TT
3890 CLASS="PARAMETER"
3891 ><I
3892 >max connections</I
3893 ></TT
3894 ></A
3895 ></P
3896 ></LI
3897 ><LI
3898 ><P
3899 ><A
3900 HREF="#MAXPRINTJOBS"
3901 ><TT
3902 CLASS="PARAMETER"
3903 ><I
3904 >max print jobs</I
3905 ></TT
3906 ></A
3907 ></P
3908 ></LI
3909 ><LI
3910 ><P
3911 ><A
3912 HREF="#MINPRINTSPACE"
3913 ><TT
3914 CLASS="PARAMETER"
3915 ><I
3916 >min print space</I
3917 ></TT
3918 ></A
3919 ></P
3920 ></LI
3921 ><LI
3922 ><P
3923 ><A
3924 HREF="#MSDFSROOT"
3925 ><TT
3926 CLASS="PARAMETER"
3927 ><I
3928 >msdfs root</I
3929 ></TT
3930 ></A
3931 ></P
3932 ></LI
3933 ><LI
3934 ><P
3935 ><A
3936 HREF="#NTACLSUPPORT"
3937 ><TT
3938 CLASS="PARAMETER"
3939 ><I
3940 >nt acl support</I
3941 ></TT
3942 ></A
3943 ></P
3944 ></LI
3945 ><LI
3946 ><P
3947 ><A
3948 HREF="#ONLYGUEST"
3949 ><TT
3950 CLASS="PARAMETER"
3951 ><I
3952 >only guest</I
3953 ></TT
3954 ></A
3955 ></P
3956 ></LI
3957 ><LI
3958 ><P
3959 ><A
3960 HREF="#ONLYUSER"
3961 ><TT
3962 CLASS="PARAMETER"
3963 ><I
3964 >only user</I
3965 ></TT
3966 ></A
3967 ></P
3968 ></LI
3969 ><LI
3970 ><P
3971 ><A
3972 HREF="#OPLOCKCONTENTIONLIMIT"
3973 ><TT
3974 CLASS="PARAMETER"
3975 ><I
3976 >oplock contention limit</I
3977 ></TT
3978 ></A
3979 ></P
3980 ></LI
3981 ><LI
3982 ><P
3983 ><A
3984 HREF="#OPLOCKS"
3985 ><TT
3986 CLASS="PARAMETER"
3987 ><I
3988 >oplocks</I
3989 ></TT
3990 ></A
3991 ></P
3992 ></LI
3993 ><LI
3994 ><P
3995 ><A
3996 HREF="#PATH"
3997 ><TT
3998 CLASS="PARAMETER"
3999 ><I
4000 >path</I
4001 ></TT
4002 ></A
4003 ></P
4004 ></LI
4005 ><LI
4006 ><P
4007 ><A
4008 HREF="#POSIXLOCKING"
4009 ><TT
4010 CLASS="PARAMETER"
4011 ><I
4012 >posix locking</I
4013 ></TT
4014 ></A
4015 ></P
4016 ></LI
4017 ><LI
4018 ><P
4019 ><A
4020 HREF="#POSTEXEC"
4021 ><TT
4022 CLASS="PARAMETER"
4023 ><I
4024 >postexec</I
4025 ></TT
4026 ></A
4027 ></P
4028 ></LI
4029 ><LI
4030 ><P
4031 ><A
4032 HREF="#POSTSCRIPT"
4033 ><TT
4034 CLASS="PARAMETER"
4035 ><I
4036 >postscript</I
4037 ></TT
4038 ></A
4039 ></P
4040 ></LI
4041 ><LI
4042 ><P
4043 ><A
4044 HREF="#PREEXEC"
4045 ><TT
4046 CLASS="PARAMETER"
4047 ><I
4048 >preexec</I
4049 ></TT
4050 ></A
4051 ></P
4052 ></LI
4053 ><LI
4054 ><P
4055 ><A
4056 HREF="#PREEXECCLOSE"
4057 ><TT
4058 CLASS="PARAMETER"
4059 ><I
4060 >preexec close</I
4061 ></TT
4062 ></A
4063 ></P
4064 ></LI
4065 ><LI
4066 ><P
4067 ><A
4068 HREF="#PRESERVECASE"
4069 ><TT
4070 CLASS="PARAMETER"
4071 ><I
4072 >preserve case</I
4073 ></TT
4074 ></A
4075 ></P
4076 ></LI
4077 ><LI
4078 ><P
4079 ><A
4080 HREF="#PRINTCOMMAND"
4081 ><TT
4082 CLASS="PARAMETER"
4083 ><I
4084 >print command</I
4085 ></TT
4086 ></A
4087 ></P
4088 ></LI
4089 ><LI
4090 ><P
4091 ><A
4092 HREF="#PRINTOK"
4093 ><TT
4094 CLASS="PARAMETER"
4095 ><I
4096 >print ok</I
4097 ></TT
4098 ></A
4099 ></P
4100 ></LI
4101 ><LI
4102 ><P
4103 ><A
4104 HREF="#PRINTABLE"
4105 ><TT
4106 CLASS="PARAMETER"
4107 ><I
4108 >printable</I
4109 ></TT
4110 ></A
4111 ></P
4112 ></LI
4113 ><LI
4114 ><P
4115 ><A
4116 HREF="#PRINTER"
4117 ><TT
4118 CLASS="PARAMETER"
4119 ><I
4120 >printer</I
4121 ></TT
4122 ></A
4123 ></P
4124 ></LI
4125 ><LI
4126 ><P
4127 ><A
4128 HREF="#PRINTERADMIN"
4129 ><TT
4130 CLASS="PARAMETER"
4131 ><I
4132 >printer admin</I
4133 ></TT
4134 ></A
4135 ></P
4136 ></LI
4137 ><LI
4138 ><P
4139 ><A
4140 HREF="#PRINTERDRIVER"
4141 ><TT
4142 CLASS="PARAMETER"
4143 ><I
4144 >printer driver</I
4145 ></TT
4146 ></A
4147 ></P
4148 ></LI
4149 ><LI
4150 ><P
4151 ><A
4152 HREF="#PRINTERDRIVERLOCATION"
4153 ><TT
4154 CLASS="PARAMETER"
4155 ><I
4156 >printer driver location</I
4157 ></TT
4158 ></A
4159 ></P
4160 ></LI
4161 ><LI
4162 ><P
4163 ><A
4164 HREF="#PRINTERNAME"
4165 ><TT
4166 CLASS="PARAMETER"
4167 ><I
4168 >printer name</I
4169 ></TT
4170 ></A
4171 ></P
4172 ></LI
4173 ><LI
4174 ><P
4175 ><A
4176 HREF="#PRINTING"
4177 ><TT
4178 CLASS="PARAMETER"
4179 ><I
4180 >printing</I
4181 ></TT
4182 ></A
4183 ></P
4184 ></LI
4185 ><LI
4186 ><P
4187 ><A
4188 HREF="#PUBLIC"
4189 ><TT
4190 CLASS="PARAMETER"
4191 ><I
4192 >public</I
4193 ></TT
4194 ></A
4195 ></P
4196 ></LI
4197 ><LI
4198 ><P
4199 ><A
4200 HREF="#QUEUEPAUSECOMMAND"
4201 ><TT
4202 CLASS="PARAMETER"
4203 ><I
4204 >queuepause command</I
4205 ></TT
4206 ></A
4207 ></P
4208 ></LI
4209 ><LI
4210 ><P
4211 ><A
4212 HREF="#QUEUERESUMECOMMAND"
4213 ><TT
4214 CLASS="PARAMETER"
4215 ><I
4216 >queueresume command</I
4217 ></TT
4218 ></A
4219 ></P
4220 ></LI
4221 ><LI
4222 ><P
4223 ><A
4224 HREF="#READLIST"
4225 ><TT
4226 CLASS="PARAMETER"
4227 ><I
4228 >read list</I
4229 ></TT
4230 ></A
4231 ></P
4232 ></LI
4233 ><LI
4234 ><P
4235 ><A
4236 HREF="#READONLY"
4237 ><TT
4238 CLASS="PARAMETER"
4239 ><I
4240 >read only</I
4241 ></TT
4242 ></A
4243 ></P
4244 ></LI
4245 ><LI
4246 ><P
4247 ><A
4248 HREF="#ROOTPOSTEXEC"
4249 ><TT
4250 CLASS="PARAMETER"
4251 ><I
4252 >root postexec</I
4253 ></TT
4254 ></A
4255 ></P
4256 ></LI
4257 ><LI
4258 ><P
4259 ><A
4260 HREF="#ROOTPREEXEC"
4261 ><TT
4262 CLASS="PARAMETER"
4263 ><I
4264 >root preexec</I
4265 ></TT
4266 ></A
4267 ></P
4268 ></LI
4269 ><LI
4270 ><P
4271 ><A
4272 HREF="#ROOTPREEXECCLOSE"
4273 ><TT
4274 CLASS="PARAMETER"
4275 ><I
4276 >root preexec close</I
4277 ></TT
4278 ></A
4279 ></P
4280 ></LI
4281 ><LI
4282 ><P
4283 ><A
4284 HREF="#SECURITYMASK"
4285 ><TT
4286 CLASS="PARAMETER"
4287 ><I
4288 >security mask</I
4289 ></TT
4290 ></A
4291 ></P
4292 ></LI
4293 ><LI
4294 ><P
4295 ><A
4296 HREF="#SETDIRECTORY"
4297 ><TT
4298 CLASS="PARAMETER"
4299 ><I
4300 >set directory</I
4301 ></TT
4302 ></A
4303 ></P
4304 ></LI
4305 ><LI
4306 ><P
4307 ><A
4308 HREF="#SHAREMODES"
4309 ><TT
4310 CLASS="PARAMETER"
4311 ><I
4312 >share modes</I
4313 ></TT
4314 ></A
4315 ></P
4316 ></LI
4317 ><LI
4318 ><P
4319 ><A
4320 HREF="#SHORTPRESERVECASE"
4321 ><TT
4322 CLASS="PARAMETER"
4323 ><I
4324 >short preserve case</I
4325 ></TT
4326 ></A
4327 ></P
4328 ></LI
4329 ><LI
4330 ><P
4331 ><A
4332 HREF="#STATUS"
4333 ><TT
4334 CLASS="PARAMETER"
4335 ><I
4336 >status</I
4337 ></TT
4338 ></A
4339 ></P
4340 ></LI
4341 ><LI
4342 ><P
4343 ><A
4344 HREF="#STRICTALLOCATE"
4345 ><TT
4346 CLASS="PARAMETER"
4347 ><I
4348 >strict allocate</I
4349 ></TT
4350 ></A
4351 ></P
4352 ></LI
4353 ><LI
4354 ><P
4355 ><A
4356 HREF="#STRICTLOCKING"
4357 ><TT
4358 CLASS="PARAMETER"
4359 ><I
4360 >strict locking</I
4361 ></TT
4362 ></A
4363 ></P
4364 ></LI
4365 ><LI
4366 ><P
4367 ><A
4368 HREF="#STRICTSYNC"
4369 ><TT
4370 CLASS="PARAMETER"
4371 ><I
4372 >strict sync</I
4373 ></TT
4374 ></A
4375 ></P
4376 ></LI
4377 ><LI
4378 ><P
4379 ><A
4380 HREF="#SYNCALWAYS"
4381 ><TT
4382 CLASS="PARAMETER"
4383 ><I
4384 >sync always</I
4385 ></TT
4386 ></A
4387 ></P
4388 ></LI
4389 ><LI
4390 ><P
4391 ><A
4392 HREF="#USECLIENTDRIVER"
4393 ><TT
4394 CLASS="PARAMETER"
4395 ><I
4396 >use client driver</I
4397 ></TT
4398 ></A
4399 ></P
4400 ></LI
4401 ><LI
4402 ><P
4403 ><A
4404 HREF="#USER"
4405 ><TT
4406 CLASS="PARAMETER"
4407 ><I
4408 >user</I
4409 ></TT
4410 ></A
4411 ></P
4412 ></LI
4413 ><LI
4414 ><P
4415 ><A
4416 HREF="#USERNAME"
4417 ><TT
4418 CLASS="PARAMETER"
4419 ><I
4420 >username</I
4421 ></TT
4422 ></A
4423 ></P
4424 ></LI
4425 ><LI
4426 ><P
4427 ><A
4428 HREF="#USERS"
4429 ><TT
4430 CLASS="PARAMETER"
4431 ><I
4432 >users</I
4433 ></TT
4434 ></A
4435 ></P
4436 ></LI
4437 ><LI
4438 ><P
4439 ><A
4440 HREF="#VALIDUSERS"
4441 ><TT
4442 CLASS="PARAMETER"
4443 ><I
4444 >valid users</I
4445 ></TT
4446 ></A
4447 ></P
4448 ></LI
4449 ><LI
4450 ><P
4451 ><A
4452 HREF="#VETOFILES"
4453 ><TT
4454 CLASS="PARAMETER"
4455 ><I
4456 >veto files</I
4457 ></TT
4458 ></A
4459 ></P
4460 ></LI
4461 ><LI
4462 ><P
4463 ><A
4464 HREF="#VETOOPLOCKFILES"
4465 ><TT
4466 CLASS="PARAMETER"
4467 ><I
4468 >veto oplock files</I
4469 ></TT
4470 ></A
4471 ></P
4472 ></LI
4473 ><LI
4474 ><P
4475 ><A
4476 HREF="#VFSOBJECT"
4477 ><TT
4478 CLASS="PARAMETER"
4479 ><I
4480 >vfs object</I
4481 ></TT
4482 ></A
4483 ></P
4484 ></LI
4485 ><LI
4486 ><P
4487 ><A
4488 HREF="#VFSOPTIONS"
4489 ><TT
4490 CLASS="PARAMETER"
4491 ><I
4492 >vfs options</I
4493 ></TT
4494 ></A
4495 ></P
4496 ></LI
4497 ><LI
4498 ><P
4499 ><A
4500 HREF="#VOLUME"
4501 ><TT
4502 CLASS="PARAMETER"
4503 ><I
4504 >volume</I
4505 ></TT
4506 ></A
4507 ></P
4508 ></LI
4509 ><LI
4510 ><P
4511 ><A
4512 HREF="#WIDELINKS"
4513 ><TT
4514 CLASS="PARAMETER"
4515 ><I
4516 >wide links</I
4517 ></TT
4518 ></A
4519 ></P
4520 ></LI
4521 ><LI
4522 ><P
4523 ><A
4524 HREF="#WRITABLE"
4525 ><TT
4526 CLASS="PARAMETER"
4527 ><I
4528 >writable</I
4529 ></TT
4530 ></A
4531 ></P
4532 ></LI
4533 ><LI
4534 ><P
4535 ><A
4536 HREF="#WRITECACHESIZE"
4537 ><TT
4538 CLASS="PARAMETER"
4539 ><I
4540 >write cache size</I
4541 ></TT
4542 ></A
4543 ></P
4544 ></LI
4545 ><LI
4546 ><P
4547 ><A
4548 HREF="#WRITELIST"
4549 ><TT
4550 CLASS="PARAMETER"
4551 ><I
4552 >write list</I
4553 ></TT
4554 ></A
4555 ></P
4556 ></LI
4557 ><LI
4558 ><P
4559 ><A
4560 HREF="#WRITEOK"
4561 ><TT
4562 CLASS="PARAMETER"
4563 ><I
4564 >write ok</I
4565 ></TT
4566 ></A
4567 ></P
4568 ></LI
4569 ><LI
4570 ><P
4571 ><A
4572 HREF="#WRITEABLE"
4573 ><TT
4574 CLASS="PARAMETER"
4575 ><I
4576 >writeable</I
4577 ></TT
4578 ></A
4579 ></P
4580 ></LI
4581 ></UL
4582 ></DIV
4583 ><DIV
4584 CLASS="REFSECT1"
4585 ><A
4586 NAME="AEN1496"
4587 ></A
4588 ><H2
4589 >EXPLANATION OF EACH PARAMETER</H2
4590 ><P
4591 ></P
4592 ><DIV
4593 CLASS="VARIABLELIST"
4594 ><DL
4595 ><DT
4596 ><A
4597 NAME="ADDPRINTERCOMMAND"
4598 ></A
4599 >add printer command (G)</DT
4600 ><DD
4601 ><P
4602 >With the introduction of MS-RPC based printing
4603                 support for Windows NT/2000 clients in Samba 2.2, The MS Add
4604                 Printer Wizard (APW) icon is now also available in the
4605                 "Printers..." folder displayed a share listing.  The APW
4606                 allows for printers to be add remotely to a Samba or Windows
4607                 NT/2000 print server.</P
4608 ><P
4609 >For a Samba host this means that the printer must be
4610                 physically added to the underlying printing system.  The <TT
4611 CLASS="PARAMETER"
4612 ><I
4613 >add
4614                 printer command</I
4615 ></TT
4616 > defines a script to be run which
4617                 will perform the necessary operations for adding the printer
4618                 to the print system and to add the appropriate service definition
4619                 to the  <TT
4620 CLASS="FILENAME"
4621 >smb.conf</TT
4622 > file in order that it can be
4623                 shared by <A
4624 HREF="smbd.8.html"
4625 TARGET="_top"
4626 ><B
4627 CLASS="COMMAND"
4628 >smbd(8)</B
4629 >
4630                 </A
4631 >.</P
4632 ><P
4633 >The <TT
4634 CLASS="PARAMETER"
4635 ><I
4636 >add printer command</I
4637 ></TT
4638 > is
4639                 automatically invoked with the following parameter (in
4640                 order:</P
4641 ><P
4642 ></P
4643 ><UL
4644 ><LI
4645 ><P
4646 ><TT
4647 CLASS="PARAMETER"
4648 ><I
4649 >printer name</I
4650 ></TT
4651 ></P
4652 ></LI
4653 ><LI
4654 ><P
4655 ><TT
4656 CLASS="PARAMETER"
4657 ><I
4658 >share name</I
4659 ></TT
4660 ></P
4661 ></LI
4662 ><LI
4663 ><P
4664 ><TT
4665 CLASS="PARAMETER"
4666 ><I
4667 >port name</I
4668 ></TT
4669 ></P
4670 ></LI
4671 ><LI
4672 ><P
4673 ><TT
4674 CLASS="PARAMETER"
4675 ><I
4676 >driver name</I
4677 ></TT
4678 ></P
4679 ></LI
4680 ><LI
4681 ><P
4682 ><TT
4683 CLASS="PARAMETER"
4684 ><I
4685 >location</I
4686 ></TT
4687 ></P
4688 ></LI
4689 ><LI
4690 ><P
4691 ><TT
4692 CLASS="PARAMETER"
4693 ><I
4694 >Windows 9x driver location</I
4695 ></TT
4696 >
4697                         </P
4698 ></LI
4699 ></UL
4700 ><P
4701 >All parameters are filled in from the PRINTER_INFO_2 structure sent
4702                 by the Windows NT/2000 client with one exception.  The "Windows 9x
4703                 driver location" parameter is included for backwards compatibility
4704                 only.  The remaining fields in the structure are generated from answers
4705                 to the APW questions.</P
4706 ><P
4707 >Once the <TT
4708 CLASS="PARAMETER"
4709 ><I
4710 >add printer command</I
4711 ></TT
4712 > has
4713                 been executed, <B
4714 CLASS="COMMAND"
4715 >smbd</B
4716 > will reparse the <TT
4717 CLASS="FILENAME"
4718 >               smb.conf</TT
4719 > to determine if the share defined by the APW
4720                 exists.  If the sharename is still invalid, then <B
4721 CLASS="COMMAND"
4722 >smbd
4723                 </B
4724 > will return an ACCESS_DENIED error to the client.</P
4725 ><P
4726 >See also <A
4727 HREF="#DELETEPRINTERCOMMAND"
4728 ><TT
4729 CLASS="PARAMETER"
4730 ><I
4731 >               delete printer command</I
4732 ></TT
4733 ></A
4734 >, <A
4735 HREF="#PRINTING"
4736 ><TT
4737 CLASS="PARAMETER"
4738 ><I
4739 >printing</I
4740 ></TT
4741 ></A
4742 >,
4743                 <A
4744 HREF="#SHOWADDPRINTERWIZARD"
4745 ><TT
4746 CLASS="PARAMETER"
4747 ><I
4748 >show add
4749                 printer wizard</I
4750 ></TT
4751 ></A
4752 ></P
4753 ><P
4754 >Default: <EM
4755 >none</EM
4756 ></P
4757 ><P
4758 >Example: <B
4759 CLASS="COMMAND"
4760 >addprinter command = /usr/bin/addprinter
4761                 </B
4762 ></P
4763 ></DD
4764 ><DT
4765 ><A
4766 NAME="ADDSHARECOMMAND"
4767 ></A
4768 >add share command (G)</DT
4769 ><DD
4770 ><P
4771 >Samba 2.2.0 introduced the ability to dynamically
4772                 add and delete shares via the Windows NT 4.0 Server Manager.  The
4773                 <TT
4774 CLASS="PARAMETER"
4775 ><I
4776 >add share command</I
4777 ></TT
4778 > is used to define an
4779                 external program or script which will add a new service definition
4780                 to <TT
4781 CLASS="FILENAME"
4782 >smb.conf</TT
4783 >.  In order to successfully
4784                 execute the <TT
4785 CLASS="PARAMETER"
4786 ><I
4787 >add share command</I
4788 ></TT
4789 >, <B
4790 CLASS="COMMAND"
4791 >smbd</B
4792 >
4793                 requires that the administrator be connected using a root account (i.e.
4794                 uid == 0).
4795                 </P
4796 ><P
4797 >               When executed, <B
4798 CLASS="COMMAND"
4799 >smbd</B
4800 > will automatically invoke the
4801                 <TT
4802 CLASS="PARAMETER"
4803 ><I
4804 >add share command</I
4805 ></TT
4806 > with four parameters.
4807                 </P
4808 ><P
4809 ></P
4810 ><UL
4811 ><LI
4812 ><P
4813 ><TT
4814 CLASS="PARAMETER"
4815 ><I
4816 >configFile</I
4817 ></TT
4818 > - the location
4819                         of the global <TT
4820 CLASS="FILENAME"
4821 >smb.conf</TT
4822 > file.
4823                         </P
4824 ></LI
4825 ><LI
4826 ><P
4827 ><TT
4828 CLASS="PARAMETER"
4829 ><I
4830 >shareName</I
4831 ></TT
4832 > - the name of the new
4833                         share.
4834                         </P
4835 ></LI
4836 ><LI
4837 ><P
4838 ><TT
4839 CLASS="PARAMETER"
4840 ><I
4841 >pathName</I
4842 ></TT
4843 > - path to an **existing**
4844                         directory on disk.
4845                         </P
4846 ></LI
4847 ><LI
4848 ><P
4849 ><TT
4850 CLASS="PARAMETER"
4851 ><I
4852 >comment</I
4853 ></TT
4854 > - comment string to associate
4855                         with the new share.
4856                         </P
4857 ></LI
4858 ></UL
4859 ><P
4860 >               This parameter is only used for add file shares.  To add printer shares,
4861                 see the <A
4862 HREF="#ADDPRINTERCOMMAND"
4863 ><TT
4864 CLASS="PARAMETER"
4865 ><I
4866 >add printer
4867                 command</I
4868 ></TT
4869 ></A
4870 >.
4871                 </P
4872 ><P
4873 >               See also <A
4874 HREF="#CHANGESHARECOMMAND"
4875 ><TT
4876 CLASS="PARAMETER"
4877 ><I
4878 >change share
4879                 command</I
4880 ></TT
4881 ></A
4882 >, <A
4883 HREF="#DELETESHARECOMMAND"
4884 ><TT
4885 CLASS="PARAMETER"
4886 ><I
4887 >delete share
4888                 command</I
4889 ></TT
4890 ></A
4891 >.
4892                 </P
4893 ><P
4894 >Default: <EM
4895 >none</EM
4896 ></P
4897 ><P
4898 >Example: <B
4899 CLASS="COMMAND"
4900 >add share command = /usr/local/bin/addshare</B
4901 ></P
4902 ></DD
4903 ><DT
4904 ><A
4905 NAME="ADDUSERSCRIPT"
4906 ></A
4907 >add user script (G)</DT
4908 ><DD
4909 ><P
4910 >This is the full pathname to a script that will
4911                 be run <EM
4912 >AS ROOT</EM
4913 > by <A
4914 HREF="smbd.8.html"
4915 TARGET="_top"
4916 >smbd(8)
4917                 </A
4918 > under special circumstances described below.</P
4919 ><P
4920 >Normally, a Samba server requires that UNIX users are
4921                 created for all users accessing files on this server. For sites
4922                 that use Windows NT account databases as their primary user database
4923                 creating these users and keeping the user list in sync with the
4924                 Windows NT PDC is an onerous task. This option allows <A
4925 HREF="smbd.8.html"
4926 TARGET="_top"
4927 >smbd</A
4928 > to create the required UNIX users
4929                 <EM
4930 >ON DEMAND</EM
4931 > when a user accesses the Samba server.</P
4932 ><P
4933 >In order to use this option, <A
4934 HREF="smbd.8.html"
4935 TARGET="_top"
4936 >smbd</A
4937 >
4938                 must <EM
4939 >NOT</EM
4940 > be set to <TT
4941 CLASS="PARAMETER"
4942 ><I
4943 >security = share</I
4944 ></TT
4945 >
4946                 and <TT
4947 CLASS="PARAMETER"
4948 ><I
4949 >add user script</I
4950 ></TT
4951 >
4952                 must be set to a full pathname for a script that will create a UNIX
4953                 user given one argument of <TT
4954 CLASS="PARAMETER"
4955 ><I
4956 >%u</I
4957 ></TT
4958 >, which expands into
4959                 the UNIX user name to create.</P
4960 ><P
4961 >When the Windows user attempts to access the Samba server,
4962                 at login (session setup in the SMB protocol) time, <A
4963 HREF="smbd.8.html"
4964 TARGET="_top"
4965 >               smbd</A
4966 > contacts the <TT
4967 CLASS="PARAMETER"
4968 ><I
4969 >password server</I
4970 ></TT
4971 > and
4972                 attempts to authenticate the given user with the given password. If the
4973                 authentication succeeds then <B
4974 CLASS="COMMAND"
4975 >smbd</B
4976 >
4977                 attempts to find a UNIX user in the UNIX password database to map the
4978                 Windows user into. If this lookup fails, and <TT
4979 CLASS="PARAMETER"
4980 ><I
4981 >add user script
4982                 </I
4983 ></TT
4984 > is set then <B
4985 CLASS="COMMAND"
4986 >smbd</B
4987 > will
4988                 call the specified script <EM
4989 >AS ROOT</EM
4990 >, expanding
4991                 any <TT
4992 CLASS="PARAMETER"
4993 ><I
4994 >%u</I
4995 ></TT
4996 > argument to be the user name to create.</P
4997 ><P
4998 >If this script successfully creates the user then <B
4999 CLASS="COMMAND"
5000 >smbd
5001                 </B
5002 > will continue on as though the UNIX user
5003                 already existed. In this way, UNIX users are dynamically created to
5004                 match existing Windows NT accounts.</P
5005 ><P
5006 >See also <A
5007 HREF="#SECURITY"
5008 ><TT
5009 CLASS="PARAMETER"
5010 ><I
5011 >               security</I
5012 ></TT
5013 ></A
5014 >, <A
5015 HREF="#PASSWORDSERVER"
5016 >               <TT
5017 CLASS="PARAMETER"
5018 ><I
5019 >password server</I
5020 ></TT
5021 ></A
5022 >,
5023                 <A
5024 HREF="#DELETEUSERSCRIPT"
5025 ><TT
5026 CLASS="PARAMETER"
5027 ><I
5028 >delete user
5029                 script</I
5030 ></TT
5031 ></A
5032 >.</P
5033 ><P
5034 >Default: <B
5035 CLASS="COMMAND"
5036 >add user script = &#60;empty string&#62;
5037                 </B
5038 ></P
5039 ><P
5040 >Example: <B
5041 CLASS="COMMAND"
5042 >add user script = /usr/local/samba/bin/add_user
5043                 %u</B
5044 ></P
5045 ></DD
5046 ><DT
5047 ><A
5048 NAME="ADMINUSERS"
5049 ></A
5050 >admin users (S)</DT
5051 ><DD
5052 ><P
5053 >This is a list of users who will be granted
5054                 administrative privileges on the share. This means that they
5055                 will do all file operations as the super-user (root).</P
5056 ><P
5057 >You should use this option very carefully, as any user in
5058                 this list will be able to do anything they like on the share,
5059                 irrespective of file permissions.</P
5060 ><P
5061 >Default: <EM
5062 >no admin users</EM
5063 ></P
5064 ><P
5065 >Example: <B
5066 CLASS="COMMAND"
5067 >admin users = jason</B
5068 ></P
5069 ></DD
5070 ><DT
5071 ><A
5072 NAME="ALLOWHOSTS"
5073 ></A
5074 >allow hosts (S)</DT
5075 ><DD
5076 ><P
5077 >Synonym for <A
5078 HREF="#HOSTSALLOW"
5079 >               <TT
5080 CLASS="PARAMETER"
5081 ><I
5082 >hosts allow</I
5083 ></TT
5084 ></A
5085 >.</P
5086 ></DD
5087 ><DT
5088 ><A
5089 NAME="ALLOWTRUSTEDDOMAINS"
5090 ></A
5091 >allow trusted domains (G)</DT
5092 ><DD
5093 ><P
5094 >This option only takes effect when the <A
5095 HREF="#SECURITY"
5096 ><TT
5097 CLASS="PARAMETER"
5098 ><I
5099 >security</I
5100 ></TT
5101 ></A
5102 > option is set to
5103                 <TT
5104 CLASS="CONSTANT"
5105 >server</TT
5106 > or <TT
5107 CLASS="CONSTANT"
5108 >domain</TT
5109 >.
5110                 If it is set to no, then attempts to connect to a resource from
5111                 a domain or workgroup other than the one which <A
5112 HREF="smbd.8.html"
5113 TARGET="_top"
5114 >smbd</A
5115 > is running
5116                 in will fail, even if that domain is trusted by the remote server
5117                 doing the authentication.</P
5118 ><P
5119 >This is useful if you only want your Samba server to
5120                 serve resources to users in the domain it is a member of. As
5121                 an example, suppose that there are two domains DOMA and DOMB.  DOMB
5122                 is trusted by DOMA, which contains the Samba server.  Under normal
5123                 circumstances, a user with an account in DOMB can then access the
5124                 resources of a UNIX account with the same account name on the
5125                 Samba server even if they do not have an account in DOMA.  This
5126                 can make implementing a security boundary difficult.</P
5127 ><P
5128 >Default: <B
5129 CLASS="COMMAND"
5130 >allow trusted domains = yes</B
5131 ></P
5132 ></DD
5133 ><DT
5134 ><A
5135 NAME="ANNOUNCEAS"
5136 ></A
5137 >announce as (G)</DT
5138 ><DD
5139 ><P
5140 >This specifies what type of server
5141                 <A
5142 HREF="nmbd.8.html"
5143 TARGET="_top"
5144 ><B
5145 CLASS="COMMAND"
5146 >nmbd</B
5147 ></A
5148 >
5149                 will announce itself as, to a network neighborhood browse
5150                 list. By default this is set to Windows NT. The valid options
5151                 are : "NT Server" (which can also be written as "NT"),
5152                 "NT Workstation", "Win95" or "WfW" meaning Windows NT Server,
5153                 Windows NT Workstation, Windows 95 and Windows for Workgroups
5154                 respectively. Do not change this parameter unless you have a
5155                 specific need to stop Samba appearing as an NT server as this
5156                 may prevent Samba servers from participating as browser servers
5157                 correctly.</P
5158 ><P
5159 >Default: <B
5160 CLASS="COMMAND"
5161 >announce as = NT Server</B
5162 ></P
5163 ><P
5164 >Example: <B
5165 CLASS="COMMAND"
5166 >announce as = Win95</B
5167 ></P
5168 ></DD
5169 ><DT
5170 ><A
5171 NAME="ANNOUNCEVERSION"
5172 ></A
5173 >announce version (G)</DT
5174 ><DD
5175 ><P
5176 >This specifies the major and minor version numbers
5177                 that nmbd will use when announcing itself as a server. The default
5178                 is 4.5.  Do not change this parameter unless you have a specific
5179                 need to set a Samba server to be a downlevel server.</P
5180 ><P
5181 >Default: <B
5182 CLASS="COMMAND"
5183 >announce version = 4.5</B
5184 ></P
5185 ><P
5186 >Example: <B
5187 CLASS="COMMAND"
5188 >announce version = 2.0</B
5189 ></P
5190 ></DD
5191 ><DT
5192 ><A
5193 NAME="AUTOSERVICES"
5194 ></A
5195 >auto services (G)</DT
5196 ><DD
5197 ><P
5198 >This is a synonym for the <A
5199 HREF="#PRELOAD"
5200 >               <TT
5201 CLASS="PARAMETER"
5202 ><I
5203 >preload</I
5204 ></TT
5205 ></A
5206 >.</P
5207 ></DD
5208 ><DT
5209 ><A
5210 NAME="AVAILABLE"
5211 ></A
5212 >available (S)</DT
5213 ><DD
5214 ><P
5215 >This parameter lets you "turn off" a service. If
5216                 <TT
5217 CLASS="PARAMETER"
5218 ><I
5219 >available = no</I
5220 ></TT
5221 >, then <EM
5222 >ALL</EM
5223 >
5224                 attempts to connect to the service will fail. Such failures are
5225                 logged.</P
5226 ><P
5227 >Default: <B
5228 CLASS="COMMAND"
5229 >available = yes</B
5230 ></P
5231 ></DD
5232 ><DT
5233 ><A
5234 NAME="BINDINTERFACESONLY"
5235 ></A
5236 >bind interfaces only (G)</DT
5237 ><DD
5238 ><P
5239 >This global parameter allows the Samba admin
5240                 to limit what interfaces on a machine will serve SMB requests. If
5241                 affects file service <A
5242 HREF="smbd.8.html"
5243 TARGET="_top"
5244 >smbd(8)</A
5245 > and
5246                 name service <A
5247 HREF="nmbd.8.html"
5248 TARGET="_top"
5249 >nmbd(8)</A
5250 > in slightly
5251                 different ways.</P
5252 ><P
5253 >For name service it causes <B
5254 CLASS="COMMAND"
5255 >nmbd</B
5256 > to bind
5257                 to ports 137 and 138 on the interfaces listed in the <A
5258 HREF="#INTERFACES"
5259 >interfaces</A
5260 > parameter. <B
5261 CLASS="COMMAND"
5262 >nmbd
5263                 </B
5264 > also binds to the "all addresses" interface (0.0.0.0)
5265                 on ports 137 and 138 for the purposes of reading broadcast messages.
5266                 If this option is not set then <B
5267 CLASS="COMMAND"
5268 >nmbd</B
5269 > will service
5270                 name requests on all of these sockets. If <TT
5271 CLASS="PARAMETER"
5272 ><I
5273 >bind interfaces
5274                 only</I
5275 ></TT
5276 > is set then <B
5277 CLASS="COMMAND"
5278 >nmbd</B
5279 > will check the
5280                 source address of any packets coming in on the broadcast sockets
5281                 and discard any that don't match the broadcast addresses of the
5282                 interfaces in the <TT
5283 CLASS="PARAMETER"
5284 ><I
5285 >interfaces</I
5286 ></TT
5287 > parameter list.
5288                 As unicast packets are received on the other sockets it allows
5289                 <B
5290 CLASS="COMMAND"
5291 >nmbd</B
5292 > to refuse to serve names to machines that
5293                 send packets that arrive through any interfaces not listed in the
5294                 <TT
5295 CLASS="PARAMETER"
5296 ><I
5297 >interfaces</I
5298 ></TT
5299 > list.  IP Source address spoofing
5300                 does defeat this simple check, however so it must not be used
5301                 seriously as a security feature for <B
5302 CLASS="COMMAND"
5303 >nmbd</B
5304 >.</P
5305 ><P
5306 >For file service it causes <A
5307 HREF="smbd.8.html"
5308 TARGET="_top"
5309 >smbd(8)</A
5310 >
5311                 to bind only to the interface list given in the <A
5312 HREF="#INTERFACES"
5313 >               interfaces</A
5314 > parameter. This restricts the networks that
5315                 <B
5316 CLASS="COMMAND"
5317 >smbd</B
5318 > will serve to packets coming in those
5319                 interfaces.  Note that you should not use this parameter for machines
5320                 that are serving PPP or other intermittent or non-broadcast network
5321                 interfaces as it will not cope with non-permanent interfaces.</P
5322 ><P
5323 >If <TT
5324 CLASS="PARAMETER"
5325 ><I
5326 >bind interfaces only</I
5327 ></TT
5328 > is set then
5329                 unless the network address <EM
5330 >127.0.0.1</EM
5331 > is added
5332                 to the <TT
5333 CLASS="PARAMETER"
5334 ><I
5335 >interfaces</I
5336 ></TT
5337 > parameter list <A
5338 HREF="smbpasswd.8.html"
5339 TARGET="_top"
5340 ><B
5341 CLASS="COMMAND"
5342 >smbpasswd(8)</B
5343 ></A
5344 >
5345                 and <A
5346 HREF="swat.8.html"
5347 TARGET="_top"
5348 ><B
5349 CLASS="COMMAND"
5350 >swat(8)</B
5351 ></A
5352 > may
5353                 not work as expected due to the reasons covered below.</P
5354 ><P
5355 >To change a users SMB password, the <B
5356 CLASS="COMMAND"
5357 >smbpasswd</B
5358 >
5359                 by default connects to the <EM
5360 >localhost - 127.0.0.1</EM
5361 >
5362                 address as an SMB client to issue the password change request. If
5363                 <TT
5364 CLASS="PARAMETER"
5365 ><I
5366 >bind interfaces only</I
5367 ></TT
5368 > is set then unless the
5369                 network address <EM
5370 >127.0.0.1</EM
5371 > is added to the
5372                 <TT
5373 CLASS="PARAMETER"
5374 ><I
5375 >interfaces</I
5376 ></TT
5377 > parameter list then <B
5378 CLASS="COMMAND"
5379 >               smbpasswd</B
5380 > will fail to connect in it's default mode.
5381                 <B
5382 CLASS="COMMAND"
5383 >smbpasswd</B
5384 > can be forced to use the primary IP interface
5385                 of the local host by using its <A
5386 HREF="smbpasswd.8.html#minusr"
5387 TARGET="_top"
5388 >               <TT
5389 CLASS="PARAMETER"
5390 ><I
5391 >-r <TT
5392 CLASS="REPLACEABLE"
5393 ><I
5394 >remote machine</I
5395 ></TT
5396 ></I
5397 ></TT
5398 >
5399                 </A
5400 > parameter, with <TT
5401 CLASS="REPLACEABLE"
5402 ><I
5403 >remote machine</I
5404 ></TT
5405 > set
5406                 to the IP name of the primary interface of the local host.</P
5407 ><P
5408 >The <B
5409 CLASS="COMMAND"
5410 >swat</B
5411 > status page tries to connect with
5412                 <B
5413 CLASS="COMMAND"
5414 >smbd</B
5415 > and <B
5416 CLASS="COMMAND"
5417 >nmbd</B
5418 > at the address
5419                 <EM
5420 >127.0.0.1</EM
5421 > to determine if they are running.
5422                 Not adding <EM
5423 >127.0.0.1</EM
5424 >  will cause <B
5425 CLASS="COMMAND"
5426 >               smbd</B
5427 > and <B
5428 CLASS="COMMAND"
5429 >nmbd</B
5430 > to always show
5431                 "not running" even if they really are.  This can prevent <B
5432 CLASS="COMMAND"
5433 >               swat</B
5434 > from starting/stopping/restarting <B
5435 CLASS="COMMAND"
5436 >smbd</B
5437 >
5438                 and <B
5439 CLASS="COMMAND"
5440 >nmbd</B
5441 >.</P
5442 ><P
5443 >Default: <B
5444 CLASS="COMMAND"
5445 >bind interfaces only = no</B
5446 ></P
5447 ></DD
5448 ><DT
5449 ><A
5450 NAME="BLOCKSIZE"
5451 ></A
5452 >block size (S)</DT
5453 ><DD
5454 ><P
5455 >This parameter controls the behavior of <A
5456 HREF="smbd.8.html"
5457 TARGET="_top"
5458 >smbd(8)</A
5459 > when reporting disk free sizes.
5460                 By default, this reports a disk block size of 1024 bytes.</P
5461 ><P
5462 >Changing this parameter may have some effect on the
5463                 efficiency of client writes, this is not yet confirmed. This
5464                 parameter was added to allow advanced administrators to change
5465                 it (usually to a higher value) and test the effect it has on
5466                 client write performance without re-compiling the code. As this
5467                 is an experimental option it may be removed in a future release.
5468                 </P
5469 ><P
5470 >Changing this option does not change the disk free reporting
5471                 size, just the block size unit reported to the client.</P
5472 ><P
5473 >Default: <B
5474 CLASS="COMMAND"
5475 >block size = 1024</B
5476 ></P
5477 ><P
5478 >Example: <B
5479 CLASS="COMMAND"
5480 >block size = 65536</B
5481 ></P
5482 ></DD
5483 ><DT
5484 ><A
5485 NAME="BLOCKINGLOCKS"
5486 ></A
5487 >blocking locks (S)</DT
5488 ><DD
5489 ><P
5490 >This parameter controls the behavior of <A
5491 HREF="smbd.8.html"
5492 TARGET="_top"
5493 >smbd(8)</A
5494 > when given a request by a client
5495                 to obtain a byte range lock on a region of an open file, and the
5496                 request has a time limit associated with it.</P
5497 ><P
5498 >If this parameter is set and the lock range requested
5499                 cannot be immediately satisfied, Samba 2.2 will internally
5500                 queue the lock request, and periodically attempt to obtain
5501                 the lock until the timeout period expires.</P
5502 ><P
5503 >If this parameter is set to <TT
5504 CLASS="CONSTANT"
5505 >no</TT
5506 >, then
5507                 Samba 2.2 will behave as previous versions of Samba would and
5508                 will fail the lock request immediately if the lock range
5509                 cannot be obtained.</P
5510 ><P
5511 >Default: <B
5512 CLASS="COMMAND"
5513 >blocking locks = yes</B
5514 ></P
5515 ></DD
5516 ><DT
5517 ><A
5518 NAME="BROWSABLE"
5519 ></A
5520 >browsable (S)</DT
5521 ><DD
5522 ><P
5523 >See the <A
5524 HREF="#BROWSEABLE"
5525 ><TT
5526 CLASS="PARAMETER"
5527 ><I
5528 >               browseable</I
5529 ></TT
5530 ></A
5531 >.</P
5532 ></DD
5533 ><DT
5534 ><A
5535 NAME="BROWSELIST"
5536 ></A
5537 >browse list (G)</DT
5538 ><DD
5539 ><P
5540 >This controls whether <A
5541 HREF="smbd.8.html"
5542 TARGET="_top"
5543 >               <B
5544 CLASS="COMMAND"
5545 >smbd(8)</B
5546 ></A
5547 > will serve a browse list to
5548                 a client doing a <B
5549 CLASS="COMMAND"
5550 >NetServerEnum</B
5551 > call. Normally
5552                 set to <TT
5553 CLASS="CONSTANT"
5554 >yes</TT
5555 >. You should never need to change
5556                 this.</P
5557 ><P
5558 >Default: <B
5559 CLASS="COMMAND"
5560 >browse list = yes</B
5561 ></P
5562 ></DD
5563 ><DT
5564 ><A
5565 NAME="BROWSEABLE"
5566 ></A
5567 >browseable (S)</DT
5568 ><DD
5569 ><P
5570 >This controls whether this share is seen in
5571                 the list of available shares in a net view and in the browse list.</P
5572 ><P
5573 >Default: <B
5574 CLASS="COMMAND"
5575 >browseable = yes</B
5576 ></P
5577 ></DD
5578 ><DT
5579 ><A
5580 NAME="CASESENSITIVE"
5581 ></A
5582 >case sensitive (S)</DT
5583 ><DD
5584 ><P
5585 >See the discussion in the section <A
5586 HREF="#AEN203"
5587 >NAME MANGLING</A
5588 >.</P
5589 ><P
5590 >Default: <B
5591 CLASS="COMMAND"
5592 >case sensitive = no</B
5593 ></P
5594 ></DD
5595 ><DT
5596 ><A
5597 NAME="CASESIGNAMES"
5598 ></A
5599 >casesignames (S)</DT
5600 ><DD
5601 ><P
5602 >Synonym for <A
5603 HREF="#CASESENSITIVE"
5604 >case
5605                 sensitive</A
5606 >.</P
5607 ></DD
5608 ><DT
5609 ><A
5610 NAME="CHANGENOTIFYTIMEOUT"
5611 ></A
5612 >change notify timeout (G)</DT
5613 ><DD
5614 ><P
5615 >This SMB allows a client to tell a server to
5616                 "watch" a particular directory for any changes and only reply to
5617                 the SMB request when a change has occurred. Such constant scanning of
5618                 a directory is expensive under UNIX, hence an <A
5619 HREF="smbd.8.html"
5620 TARGET="_top"
5621 >               <B
5622 CLASS="COMMAND"
5623 >smbd(8)</B
5624 ></A
5625 > daemon only performs such a scan
5626                 on each requested directory once every <TT
5627 CLASS="PARAMETER"
5628 ><I
5629 >change notify
5630                 timeout</I
5631 ></TT
5632 > seconds.</P
5633 ><P
5634 >Default: <B
5635 CLASS="COMMAND"
5636 >change notify timeout = 60</B
5637 ></P
5638 ><P
5639 >Example: <B
5640 CLASS="COMMAND"
5641 >change notify timeout = 300</B
5642 ></P
5643 ><P
5644 >Would change the scan time to every 5 minutes.</P
5645 ></DD
5646 ><DT
5647 ><A
5648 NAME="CHANGESHARECOMMAND"
5649 ></A
5650 >change share command (G)</DT
5651 ><DD
5652 ><P
5653 >Samba 2.2.0 introduced the ability to dynamically
5654                 add and delete shares via the Windows NT 4.0 Server Manager.  The
5655                 <TT
5656 CLASS="PARAMETER"
5657 ><I
5658 >change share command</I
5659 ></TT
5660 > is used to define an
5661                 external program or script which will modify an existing service definition
5662                 in <TT
5663 CLASS="FILENAME"
5664 >smb.conf</TT
5665 >.  In order to successfully
5666                 execute the <TT
5667 CLASS="PARAMETER"
5668 ><I
5669 >change share command</I
5670 ></TT
5671 >, <B
5672 CLASS="COMMAND"
5673 >smbd</B
5674 >
5675                 requires that the administrator be connected using a root account (i.e.
5676                 uid == 0).
5677                 </P
5678 ><P
5679 >               When executed, <B
5680 CLASS="COMMAND"
5681 >smbd</B
5682 > will automatically invoke the
5683                 <TT
5684 CLASS="PARAMETER"
5685 ><I
5686 >change share command</I
5687 ></TT
5688 > with four parameters.
5689                 </P
5690 ><P
5691 ></P
5692 ><UL
5693 ><LI
5694 ><P
5695 ><TT
5696 CLASS="PARAMETER"
5697 ><I
5698 >configFile</I
5699 ></TT
5700 > - the location
5701                         of the global <TT
5702 CLASS="FILENAME"
5703 >smb.conf</TT
5704 > file.
5705                         </P
5706 ></LI
5707 ><LI
5708 ><P
5709 ><TT
5710 CLASS="PARAMETER"
5711 ><I
5712 >shareName</I
5713 ></TT
5714 > - the name of the new
5715                         share.
5716                         </P
5717 ></LI
5718 ><LI
5719 ><P
5720 ><TT
5721 CLASS="PARAMETER"
5722 ><I
5723 >pathName</I
5724 ></TT
5725 > - path to an **existing**
5726                         directory on disk.
5727                         </P
5728 ></LI
5729 ><LI
5730 ><P
5731 ><TT
5732 CLASS="PARAMETER"
5733 ><I
5734 >comment</I
5735 ></TT
5736 > - comment string to associate
5737                         with the new share.
5738                         </P
5739 ></LI
5740 ></UL
5741 ><P
5742 >               This parameter is only used modify existing file shares definitions.  To modify
5743                 printer shares, use the "Printers..." folder as seen when browsing the Samba host.
5744                 </P
5745 ><P
5746 >               See also <A
5747 HREF="#ADDSHARECOMMAND"
5748 ><TT
5749 CLASS="PARAMETER"
5750 ><I
5751 >add share
5752                 command</I
5753 ></TT
5754 ></A
5755 >, <A
5756 HREF="#DELETESHARECOMMAND"
5757 ><TT
5758 CLASS="PARAMETER"
5759 ><I
5760 >delete
5761                 share command</I
5762 ></TT
5763 ></A
5764 >.
5765                 </P
5766 ><P
5767 >Default: <EM
5768 >none</EM
5769 ></P
5770 ><P
5771 >Example: <B
5772 CLASS="COMMAND"
5773 >change share command = /usr/local/bin/addshare</B
5774 ></P
5775 ></DD
5776 ><DT
5777 ><A
5778 NAME="CHARACTERSET"
5779 ></A
5780 >character set (G)</DT
5781 ><DD
5782 ><P
5783 >This allows <A
5784 HREF="smbd.8.html"
5785 TARGET="_top"
5786 >smbd</A
5787 > to map incoming filenames
5788                 from a DOS Code page (see the <A
5789 HREF="#CLIENTCODEPAGE"
5790 >client
5791                 code page</A
5792 > parameter) to several built in UNIX character sets.
5793                 The built in code page translations are:</P
5794 ><P
5795 ></P
5796 ><UL
5797 ><LI
5798 ><P
5799 ><TT
5800 CLASS="CONSTANT"
5801 >ISO8859-1</TT
5802 > : Western European
5803                         UNIX character set. The parameter <TT
5804 CLASS="PARAMETER"
5805 ><I
5806 >client code page</I
5807 ></TT
5808 >
5809                         <EM
5810 >MUST</EM
5811 > be set to code page 850 if the
5812                         <TT
5813 CLASS="PARAMETER"
5814 ><I
5815 >character set</I
5816 ></TT
5817 > parameter is set to
5818                         <TT
5819 CLASS="CONSTANT"
5820 >ISO8859-1</TT
5821 > in order for the conversion to the
5822                         UNIX character set to be done correctly.</P
5823 ></LI
5824 ><LI
5825 ><P
5826 ><TT
5827 CLASS="CONSTANT"
5828 >ISO8859-2</TT
5829 > : Eastern European
5830                         UNIX character set. The parameter <TT
5831 CLASS="PARAMETER"
5832 ><I
5833 >client code page
5834                         </I
5835 ></TT
5836 > <EM
5837 >MUST</EM
5838 > be set to code page 852 if
5839                         the <TT
5840 CLASS="PARAMETER"
5841 ><I
5842 > character set</I
5843 ></TT
5844 > parameter is set
5845                         to <TT
5846 CLASS="CONSTANT"
5847 >ISO8859-2</TT
5848 > in order for the conversion
5849                         to the UNIX character set to be done correctly. </P
5850 ></LI
5851 ><LI
5852 ><P
5853 ><TT
5854 CLASS="CONSTANT"
5855 >ISO8859-5</TT
5856 > : Russian Cyrillic
5857                         UNIX character set. The parameter <TT
5858 CLASS="PARAMETER"
5859 ><I
5860 >client code page
5861                         </I
5862 ></TT
5863 > <EM
5864 >MUST</EM
5865 > be set to code page
5866                         866 if the <TT
5867 CLASS="PARAMETER"
5868 ><I
5869 >character set </I
5870 ></TT
5871 > parameter is
5872                         set to <TT
5873 CLASS="CONSTANT"
5874 >ISO8859-5</TT
5875 > in order for the conversion
5876                         to the UNIX character set to be done correctly. </P
5877 ></LI
5878 ><LI
5879 ><P
5880 ><TT
5881 CLASS="CONSTANT"
5882 >ISO8859-7</TT
5883 > : Greek UNIX
5884                         character set. The parameter <TT
5885 CLASS="PARAMETER"
5886 ><I
5887 >client code page
5888                         </I
5889 ></TT
5890 > <EM
5891 >MUST</EM
5892 > be set to code page
5893                         737 if the <TT
5894 CLASS="PARAMETER"
5895 ><I
5896 >character set</I
5897 ></TT
5898 > parameter is
5899                         set to <TT
5900 CLASS="CONSTANT"
5901 >ISO8859-7</TT
5902 > in order for the conversion
5903                         to the UNIX character set to be done correctly.</P
5904 ></LI
5905 ><LI
5906 ><P
5907 ><TT
5908 CLASS="CONSTANT"
5909 >KOI8-R</TT
5910 > : Alternate mapping
5911                         for Russian Cyrillic UNIX character set. The parameter
5912                         <TT
5913 CLASS="PARAMETER"
5914 ><I
5915 >client code page</I
5916 ></TT
5917 > <EM
5918 >MUST</EM
5919 >
5920                         be set to code page 866 if the <TT
5921 CLASS="PARAMETER"
5922 ><I
5923 >character set</I
5924 ></TT
5925 >
5926                         parameter is set to <TT
5927 CLASS="CONSTANT"
5928 >KOI8-R</TT
5929 > in order for the
5930                         conversion to the UNIX character set to be done correctly.</P
5931 ></LI
5932 ></UL
5933 ><P
5934 ><EM
5935 >BUG</EM
5936 >. These MSDOS code page to UNIX character
5937                 set mappings should be dynamic, like the loading of MS DOS code pages,
5938                 not static.</P
5939 ><P
5940 >Normally this parameter is not set, meaning no filename
5941                 translation is done.</P
5942 ><P
5943 >Default: <B
5944 CLASS="COMMAND"
5945 >character set = &#60;empty string&#62;</B
5946 ></P
5947 ><P
5948 >Example: <B
5949 CLASS="COMMAND"
5950 >character set = ISO8859-1</B
5951 ></P
5952 ></DD
5953 ><DT
5954 ><A
5955 NAME="CLIENTCODEPAGE"
5956 ></A
5957 >client code page (G)</DT
5958 ><DD
5959 ><P
5960 >This parameter specifies the DOS code page
5961                 that the clients accessing Samba are using. To determine what code
5962                 page a Windows or DOS client is using, open a DOS command prompt
5963                 and type the command <B
5964 CLASS="COMMAND"
5965 >chcp</B
5966 >. This will output
5967                 the code page. The default for USA MS-DOS, Windows 95, and
5968                 Windows NT releases is code page 437. The default for western
5969                 European releases of the above operating systems is code page 850.</P
5970 ><P
5971 >This parameter tells <A
5972 HREF="smbd.8.html"
5973 TARGET="_top"
5974 >smbd(8)</A
5975 >
5976                 which of the <TT
5977 CLASS="FILENAME"
5978 >codepage.<TT
5979 CLASS="REPLACEABLE"
5980 ><I
5981 >XXX</I
5982 ></TT
5983 >
5984                 </TT
5985 > files to dynamically load on startup. These files,
5986                 described more fully in the manual page <A
5987 HREF="make_smbcodepage.1.html"
5988 TARGET="_top"
5989 >               <B
5990 CLASS="COMMAND"
5991 >make_smbcodepage(1)</B
5992 ></A
5993 >, tell <B
5994 CLASS="COMMAND"
5995 >               smbd</B
5996 > how to map lower to upper case characters to provide
5997                 the case insensitivity of filenames that Windows clients expect.</P
5998 ><P
5999 >Samba currently ships with the following code page files :</P
6000 ><P
6001 ></P
6002 ><UL
6003 ><LI
6004 ><P
6005 >Code Page 437 - MS-DOS Latin US</P
6006 ></LI
6007 ><LI
6008 ><P
6009 >Code Page 737 - Windows '95 Greek</P
6010 ></LI
6011 ><LI
6012 ><P
6013 >Code Page 850 - MS-DOS Latin 1</P
6014 ></LI
6015 ><LI
6016 ><P
6017 >Code Page 852 - MS-DOS Latin 2</P
6018 ></LI
6019 ><LI
6020 ><P
6021 >Code Page 861 - MS-DOS Icelandic</P
6022 ></LI
6023 ><LI
6024 ><P
6025 >Code Page 866 - MS-DOS Cyrillic</P
6026 ></LI
6027 ><LI
6028 ><P
6029 >Code Page 932 - MS-DOS Japanese SJIS</P
6030 ></LI
6031 ><LI
6032 ><P
6033 >Code Page 936 - MS-DOS Simplified Chinese</P
6034 ></LI
6035 ><LI
6036 ><P
6037 >Code Page 949 - MS-DOS Korean Hangul</P
6038 ></LI
6039 ><LI
6040 ><P
6041 >Code Page 950 - MS-DOS Traditional Chinese</P
6042 ></LI
6043 ></UL
6044 ><P
6045 >Thus this parameter may have any of the values 437, 737, 850, 852,
6046                 861, 932, 936, 949, or 950.  If you don't find the codepage you need,
6047                 read the comments in one of the other codepage files and the
6048                 <B
6049 CLASS="COMMAND"
6050 >make_smbcodepage(1)</B
6051 > man page and write one. Please
6052                 remember to donate it back to the Samba user community.</P
6053 ><P
6054 >This parameter co-operates with the <TT
6055 CLASS="PARAMETER"
6056 ><I
6057 >valid
6058                 chars</I
6059 ></TT
6060 > parameter in determining what characters are
6061                 valid in filenames and how capitalization is done. If you set both
6062                 this parameter and the <TT
6063 CLASS="PARAMETER"
6064 ><I
6065 >valid chars</I
6066 ></TT
6067 > parameter
6068                 the <TT
6069 CLASS="PARAMETER"
6070 ><I
6071 >client code page</I
6072 ></TT
6073 > parameter
6074                 <EM
6075 >MUST</EM
6076 > be set before the <TT
6077 CLASS="PARAMETER"
6078 ><I
6079 >valid
6080                 chars</I
6081 ></TT
6082 > parameter in the <TT
6083 CLASS="FILENAME"
6084 >smb.conf</TT
6085 >
6086                 file. The <TT
6087 CLASS="PARAMETER"
6088 ><I
6089 >valid chars</I
6090 ></TT
6091 > string will then
6092                 augment the character settings in the <TT
6093 CLASS="PARAMETER"
6094 ><I
6095 >client code page</I
6096 ></TT
6097 >
6098                 parameter.</P
6099 ><P
6100 >If not set, <TT
6101 CLASS="PARAMETER"
6102 ><I
6103 >client code page</I
6104 ></TT
6105 > defaults
6106                 to 850.</P
6107 ><P
6108 >See also : <A
6109 HREF="#VALIDCHARS"
6110 ><TT
6111 CLASS="PARAMETER"
6112 ><I
6113 >valid
6114                 chars</I
6115 ></TT
6116 ></A
6117 >, <A
6118 HREF="#CODEPAGEDIRECTORY"
6119 >               <TT
6120 CLASS="PARAMETER"
6121 ><I
6122 >code page directory</I
6123 ></TT
6124 ></A
6125 ></P
6126 ><P
6127 >Default: <B
6128 CLASS="COMMAND"
6129 >client code page = 850</B
6130 ></P
6131 ><P
6132 >Example: <B
6133 CLASS="COMMAND"
6134 >client code page = 936</B
6135 ></P
6136 ></DD
6137 ><DT
6138 ><A
6139 NAME="CODEPAGEDIRECTORY"
6140 ></A
6141 >code page directory (G)</DT
6142 ><DD
6143 ><P
6144 >Define the location of the various client code page
6145                 files.</P
6146 ><P
6147 >See also <A
6148 HREF="#CLIENTCODEPAGE"
6149 ><TT
6150 CLASS="PARAMETER"
6151 ><I
6152 >client
6153                 code page</I
6154 ></TT
6155 ></A
6156 ></P
6157 ><P
6158 >Default: <B
6159 CLASS="COMMAND"
6160 >code page directory = ${prefix}/lib/codepages
6161                 </B
6162 ></P
6163 ><P
6164 >Example: <B
6165 CLASS="COMMAND"
6166 >code page directory = /usr/share/samba/codepages
6167                 </B
6168 ></P
6169 ></DD
6170 ><DT
6171 ><A
6172 NAME="CODINGSYSTEM"
6173 ></A
6174 >coding system (G)</DT
6175 ><DD
6176 ><P
6177 >This parameter is used to determine how incoming
6178                 Shift-JIS Japanese characters are mapped from the incoming <A
6179 HREF="#CLIENTCODEPAGE"
6180 ><TT
6181 CLASS="PARAMETER"
6182 ><I
6183 >client code page</I
6184 ></TT
6185 >
6186                 </A
6187 > used by the client, into file names in the UNIX filesystem.
6188                 Only useful if <TT
6189 CLASS="PARAMETER"
6190 ><I
6191 >client code page</I
6192 ></TT
6193 > is set to
6194                 932 (Japanese Shift-JIS).  The options are :</P
6195 ><P
6196 ></P
6197 ><UL
6198 ><LI
6199 ><P
6200 ><TT
6201 CLASS="CONSTANT"
6202 >SJIS</TT
6203 >  - Shift-JIS. Does no
6204                         conversion of the incoming filename.</P
6205 ></LI
6206 ><LI
6207 ><P
6208 ><TT
6209 CLASS="CONSTANT"
6210 >JIS8, J8BB, J8BH, J8@B,
6211                         J8@J, J8@H </TT
6212 > - Convert from incoming Shift-JIS to eight
6213                         bit JIS code with different shift-in, shift out codes.</P
6214 ></LI
6215 ><LI
6216 ><P
6217 ><TT
6218 CLASS="CONSTANT"
6219 >JIS7, J7BB, J7BH, J7@B, J7@J,
6220                         J7@H </TT
6221 > - Convert from incoming Shift-JIS to seven bit
6222                         JIS code with different shift-in, shift out codes.</P
6223 ></LI
6224 ><LI
6225 ><P
6226 ><TT
6227 CLASS="CONSTANT"
6228 >JUNET, JUBB, JUBH, JU@B, JU@J, JU@H </TT
6229 >
6230                         - Convert from incoming Shift-JIS to JUNET code with different shift-in,
6231                         shift out codes.</P
6232 ></LI
6233 ><LI
6234 ><P
6235 ><TT
6236 CLASS="CONSTANT"
6237 >EUC</TT
6238 > - Convert an incoming
6239                         Shift-JIS character to EUC code.</P
6240 ></LI
6241 ><LI
6242 ><P
6243 ><TT
6244 CLASS="CONSTANT"
6245 >HEX</TT
6246 > - Convert an incoming
6247                         Shift-JIS character to a 3 byte hex representation, i.e.
6248                         <TT
6249 CLASS="CONSTANT"
6250 >:AB</TT
6251 >.</P
6252 ></LI
6253 ><LI
6254 ><P
6255 ><TT
6256 CLASS="CONSTANT"
6257 >CAP</TT
6258 > - Convert an incoming
6259                         Shift-JIS character to the 3 byte hex representation used by
6260                         the Columbia AppleTalk Program (CAP), i.e. <TT
6261 CLASS="CONSTANT"
6262 >:AB</TT
6263 >.
6264                         This is used for compatibility between Samba and CAP.</P
6265 ></LI
6266 ></UL
6267 ><P
6268 >Default: <B
6269 CLASS="COMMAND"
6270 >coding system = &#60;empty value&#62;</B
6271 >
6272                 </P
6273 ></DD
6274 ><DT
6275 ><A
6276 NAME="COMMENT"
6277 ></A
6278 >comment (S)</DT
6279 ><DD
6280 ><P
6281 >This is a text field that is seen next to a share
6282                 when a client does a queries the server, either via the network
6283                 neighborhood or via <B
6284 CLASS="COMMAND"
6285 >net view</B
6286 > to list what shares
6287                 are available.</P
6288 ><P
6289 >If you want to set the string that is displayed next to the
6290                 machine name then see the <A
6291 HREF="#SERVERSTRING"
6292 ><TT
6293 CLASS="PARAMETER"
6294 ><I
6295 >               server string</I
6296 ></TT
6297 ></A
6298 > parameter.</P
6299 ><P
6300 >Default: <EM
6301 >No comment string</EM
6302 ></P
6303 ><P
6304 >Example: <B
6305 CLASS="COMMAND"
6306 >comment = Fred's Files</B
6307 ></P
6308 ></DD
6309 ><DT
6310 ><A
6311 NAME="CONFIGFILE"
6312 ></A
6313 >config file (G)</DT
6314 ><DD
6315 ><P
6316 >This allows you to override the config file
6317                 to use, instead of the default (usually <TT
6318 CLASS="FILENAME"
6319 >smb.conf</TT
6320 >).
6321                 There is a chicken and egg problem here as this option is set
6322                 in the config file!</P
6323 ><P
6324 >For this reason, if the name of the config file has changed
6325                 when the parameters are loaded then it will reload them from
6326                 the new config file.</P
6327 ><P
6328 >This option takes the usual substitutions, which can
6329                 be very useful.</P
6330 ><P
6331 >If the config file doesn't exist then it won't be loaded
6332                 (allowing you to special case the config files of just a few
6333                 clients).</P
6334 ><P
6335 >Example: <B
6336 CLASS="COMMAND"
6337 >config file = /usr/local/samba/lib/smb.conf.%m
6338                 </B
6339 ></P
6340 ></DD
6341 ><DT
6342 ><A
6343 NAME="COPY"
6344 ></A
6345 >copy (S)</DT
6346 ><DD
6347 ><P
6348 >This parameter allows you to "clone" service
6349                 entries. The specified service is simply duplicated under the
6350                 current service's name. Any parameters specified in the current
6351                 section will override those in the section being copied.</P
6352 ><P
6353 >This feature lets you set up a 'template' service and
6354                 create similar services easily. Note that the service being
6355                 copied must occur earlier in the configuration file than the
6356                 service doing the copying.</P
6357 ><P
6358 >Default: <EM
6359 >no value</EM
6360 ></P
6361 ><P
6362 >Example: <B
6363 CLASS="COMMAND"
6364 >copy = otherservice</B
6365 ></P
6366 ></DD
6367 ><DT
6368 ><A
6369 NAME="CREATEMASK"
6370 ></A
6371 >create mask (S)</DT
6372 ><DD
6373 ><P
6374 >A synonym for this parameter is
6375                 <A
6376 HREF="#CREATEMODE"
6377 ><TT
6378 CLASS="PARAMETER"
6379 ><I
6380 >create mode</I
6381 ></TT
6382 >
6383                 </A
6384 >.</P
6385 ><P
6386 >When a file is created, the necessary permissions are
6387                 calculated according to the mapping from DOS modes to UNIX
6388                 permissions, and the resulting UNIX mode is then bit-wise 'AND'ed
6389                 with this parameter. This parameter may be thought of as a bit-wise
6390                 MASK for the UNIX modes of a file. Any bit <EM
6391 >not</EM
6392 >
6393                 set here will be removed from the modes set on a file when it is
6394                 created.</P
6395 ><P
6396 >The default value of this parameter removes the
6397                 'group' and 'other' write and execute bits from the UNIX modes.</P
6398 ><P
6399 >Following this Samba will bit-wise 'OR' the UNIX mode created
6400                 from this parameter with the value of the <A
6401 HREF="#FORCECREATEMODE"
6402 ><TT
6403 CLASS="PARAMETER"
6404 ><I
6405 >force create mode</I
6406 ></TT
6407 ></A
6408 >
6409                 parameter which is set to 000 by default.</P
6410 ><P
6411 >This parameter does not affect directory modes. See the
6412                 parameter <A
6413 HREF="#DIRECTORYMODE"
6414 ><TT
6415 CLASS="PARAMETER"
6416 ><I
6417 >directory mode
6418                 </I
6419 ></TT
6420 ></A
6421 > for details.</P
6422 ><P
6423 >See also the <A
6424 HREF="#FORCECREATEMODE"
6425 ><TT
6426 CLASS="PARAMETER"
6427 ><I
6428 >force
6429                 create mode</I
6430 ></TT
6431 ></A
6432 > parameter for forcing particular mode
6433                 bits to be set on created files. See also the <A
6434 HREF="#DIRECTORYMODE"
6435 >               <TT
6436 CLASS="PARAMETER"
6437 ><I
6438 >directory mode</I
6439 ></TT
6440 ></A
6441 > parameter for masking
6442                 mode bits on created directories.  See also the <A
6443 HREF="#INHERITPERMISSIONS"
6444 >               <TT
6445 CLASS="PARAMETER"
6446 ><I
6447 >inherit permissions</I
6448 ></TT
6449 ></A
6450 > parameter.</P
6451 ><P
6452 >Note that this parameter does not apply to permissions
6453                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
6454                 a mask on access control lists also, they need to set the <A
6455 HREF="#SECURITYMASK"
6456 ><TT
6457 CLASS="PARAMETER"
6458 ><I
6459 >security mask</I
6460 ></TT
6461 ></A
6462 >.</P
6463 ><P
6464 >Default: <B
6465 CLASS="COMMAND"
6466 >create mask = 0744</B
6467 ></P
6468 ><P
6469 >Example: <B
6470 CLASS="COMMAND"
6471 >create mask = 0775</B
6472 ></P
6473 ></DD
6474 ><DT
6475 ><A
6476 NAME="CREATEMODE"
6477 ></A
6478 >create mode (S)</DT
6479 ><DD
6480 ><P
6481 >This is a synonym for <A
6482 HREF="#CREATEMASK"
6483 ><TT
6484 CLASS="PARAMETER"
6485 ><I
6486 >               create mask</I
6487 ></TT
6488 ></A
6489 >.</P
6490 ></DD
6491 ><DT
6492 ><A
6493 NAME="CSCPOLICY"
6494 ></A
6495 >csc policy (S)</DT
6496 ><DD
6497 ><P
6498 >This stands for <EM
6499 >client-side caching
6500                 policy</EM
6501 >, and specifies how clients capable of offline
6502                 caching will cache the files in the share. The valid values
6503                 are: manual, documents, programs, disable.</P
6504 ><P
6505 >These values correspond to those used on Windows
6506                 servers.</P
6507 ><P
6508 >For example, shares containing roaming profiles can have
6509                 offline caching disabled using <B
6510 CLASS="COMMAND"
6511 >csc policy = disable
6512                 </B
6513 >.</P
6514 ><P
6515 >Default: <B
6516 CLASS="COMMAND"
6517 >csc policy = manual</B
6518 ></P
6519 ><P
6520 >Example: <B
6521 CLASS="COMMAND"
6522 >csc policy = programs</B
6523 ></P
6524 ></DD
6525 ><DT
6526 ><A
6527 NAME="DEADTIME"
6528 ></A
6529 >deadtime (G)</DT
6530 ><DD
6531 ><P
6532 >The value of the parameter (a decimal integer)
6533                 represents the number of minutes of inactivity before a connection
6534                 is considered dead, and it is disconnected. The deadtime only takes
6535                 effect if the number of open files is zero.</P
6536 ><P
6537 >This is useful to stop a server's resources being
6538                 exhausted by a large number of inactive connections.</P
6539 ><P
6540 >Most clients have an auto-reconnect feature when a
6541                 connection is broken so in most cases this parameter should be
6542                 transparent to users.</P
6543 ><P
6544 >Using this parameter with a timeout of a few minutes
6545                 is recommended for most systems.</P
6546 ><P
6547 >A deadtime of zero indicates that no auto-disconnection
6548                 should be performed.</P
6549 ><P
6550 >Default: <B
6551 CLASS="COMMAND"
6552 >deadtime = 0</B
6553 ></P
6554 ><P
6555 >Example: <B
6556 CLASS="COMMAND"
6557 >deadtime = 15</B
6558 ></P
6559 ></DD
6560 ><DT
6561 ><A
6562 NAME="DEBUGHIRESTIMESTAMP"
6563 ></A
6564 >debug hires timestamp (G)</DT
6565 ><DD
6566 ><P
6567 >Sometimes the timestamps in the log messages
6568                 are needed with a resolution of higher that seconds, this
6569                 boolean parameter adds microsecond resolution to the timestamp
6570                 message header when turned on.</P
6571 ><P
6572 >Note that the parameter <A
6573 HREF="#DEBUGTIMESTAMP"
6574 ><TT
6575 CLASS="PARAMETER"
6576 ><I
6577 >               debug timestamp</I
6578 ></TT
6579 ></A
6580 > must be on for this to have an
6581                 effect.</P
6582 ><P
6583 >Default: <B
6584 CLASS="COMMAND"
6585 >debug hires timestamp = no</B
6586 ></P
6587 ></DD
6588 ><DT
6589 ><A
6590 NAME="DEBUGPID"
6591 ></A
6592 >debug pid (G)</DT
6593 ><DD
6594 ><P
6595 >When using only one log file for more then one
6596                 forked <A
6597 HREF="smbd.8.html"
6598 TARGET="_top"
6599 >smbd</A
6600 >-process there may be hard to follow which process
6601                 outputs which message. This boolean parameter is adds the process-id
6602                 to the timestamp message headers in the logfile when turned on.</P
6603 ><P
6604 >Note that the parameter <A
6605 HREF="#DEBUGTIMESTAMP"
6606 ><TT
6607 CLASS="PARAMETER"
6608 ><I
6609 >               debug timestamp</I
6610 ></TT
6611 ></A
6612 > must be on for this to have an
6613                 effect.</P
6614 ><P
6615 >Default: <B
6616 CLASS="COMMAND"
6617 >debug pid = no</B
6618 ></P
6619 ></DD
6620 ><DT
6621 ><A
6622 NAME="DEBUGTIMESTAMP"
6623 ></A
6624 >debug timestamp (G)</DT
6625 ><DD
6626 ><P
6627 >Samba 2.2 debug log messages are timestamped
6628                 by default. If you are running at a high <A
6629 HREF="#DEBUGLEVEL"
6630 >               <TT
6631 CLASS="PARAMETER"
6632 ><I
6633 >debug level</I
6634 ></TT
6635 ></A
6636 > these timestamps
6637                 can be distracting. This boolean parameter allows timestamping
6638                 to be turned off.</P
6639 ><P
6640 >Default: <B
6641 CLASS="COMMAND"
6642 >debug timestamp = yes</B
6643 ></P
6644 ></DD
6645 ><DT
6646 ><A
6647 NAME="DEBUGUID"
6648 ></A
6649 >debug uid (G)</DT
6650 ><DD
6651 ><P
6652 >Samba is sometimes run as root and sometime
6653                 run as the connected user, this boolean parameter inserts the
6654                 current euid, egid, uid and gid to the timestamp message headers
6655                 in the log file if turned on.</P
6656 ><P
6657 >Note that the parameter <A
6658 HREF="#DEBUGTIMESTAMP"
6659 ><TT
6660 CLASS="PARAMETER"
6661 ><I
6662 >               debug timestamp</I
6663 ></TT
6664 ></A
6665 > must be on for this to have an
6666                 effect.</P
6667 ><P
6668 >Default: <B
6669 CLASS="COMMAND"
6670 >debug uid = no</B
6671 ></P
6672 ></DD
6673 ><DT
6674 ><A
6675 NAME="DEBUGLEVEL"
6676 ></A
6677 >debuglevel (G)</DT
6678 ><DD
6679 ><P
6680 >Synonym for <A
6681 HREF="#LOGLEVEL"
6682 ><TT
6683 CLASS="PARAMETER"
6684 ><I
6685 >               log level</I
6686 ></TT
6687 ></A
6688 >.</P
6689 ></DD
6690 ><DT
6691 ><A
6692 NAME="DEFAULT"
6693 ></A
6694 >default (G)</DT
6695 ><DD
6696 ><P
6697 >A synonym for <A
6698 HREF="#DEFAULTSERVICE"
6699 ><TT
6700 CLASS="PARAMETER"
6701 ><I
6702 >               default service</I
6703 ></TT
6704 ></A
6705 >.</P
6706 ></DD
6707 ><DT
6708 ><A
6709 NAME="DEFAULTCASE"
6710 ></A
6711 >default case (S)</DT
6712 ><DD
6713 ><P
6714 >See the section on <A
6715 HREF="#AEN203"
6716 >               NAME MANGLING</A
6717 >. Also note the <A
6718 HREF="#SHORTPRESERVECASE"
6719 >               <TT
6720 CLASS="PARAMETER"
6721 ><I
6722 >short preserve case</I
6723 ></TT
6724 ></A
6725 > parameter.</P
6726 ><P
6727 >Default: <B
6728 CLASS="COMMAND"
6729 >default case = lower</B
6730 ></P
6731 ></DD
6732 ><DT
6733 ><A
6734 NAME="DEFAULTDEVMODE"
6735 ></A
6736 >default devmode (S)</DT
6737 ><DD
6738 ><P
6739 >This parameter is only applicable to <A
6740 HREF="#PRINTOK"
6741 >printable</A
6742 > services.  When smbd is serving
6743                 Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
6744                 server has a Device Mode which defines things such as paper size and
6745                 orientation and duplex settings.  The device mode can only correctly be
6746                 generated by the printer driver itself (which can only be executed on a
6747                 Win32 platform).  Because smbd is unable to execute the driver code
6748                 to generate the device mode, the default behavior is to set this field
6749                 to NULL.
6750                 </P
6751 ><P
6752 >Most problems with serving printer drivers to Windows NT/2k/XP clients
6753                 can be traced to a problem with the generated device mode.  Certain drivers
6754                 will do things such as crashing the client's Explorer.exe with a NULL devmode.
6755                 However, other printer drivers can cause the client's spooler service
6756                 (spoolsv.exe) to die if the devmode was not created by the driver itself
6757                 (i.e. smbd generates a default devmode).
6758                 </P
6759 ><P
6760 >This parameter should be used with care and tested with the printer
6761                 driver in question.  It is better to leave the device mode to NULL
6762                 and let the Windows client set the correct values.  Because drivers do not
6763                 do this all the time, setting <B
6764 CLASS="COMMAND"
6765 >default devmode = yes</B
6766 >
6767                 will instruct smbd to generate a default one.
6768                 </P
6769 ><P
6770 >For more information on Windows NT/2k printing and Device Modes,
6771                 see the <A
6772 HREF="http://msdn.microsoft.com/"
6773 TARGET="_top"
6774 >MSDN documentation</A
6775 >.
6776                 </P
6777 ><P
6778 >Default: <B
6779 CLASS="COMMAND"
6780 >default devmode = no</B
6781 ></P
6782 ></DD
6783 ><DT
6784 ><A
6785 NAME="DEFAULTSERVICE"
6786 ></A
6787 >default service (G)</DT
6788 ><DD
6789 ><P
6790 >This parameter specifies the name of a service
6791                 which will be connected to if the service actually requested cannot
6792                 be found. Note that the square brackets are <EM
6793 >NOT</EM
6794 >
6795                 given in the parameter value (see example below).</P
6796 ><P
6797 >There is no default value for this parameter. If this
6798                 parameter is not given, attempting to connect to a nonexistent
6799                 service results in an error.</P
6800 ><P
6801 >Typically the default service would be a <A
6802 HREF="#GUESTOK"
6803 >               <TT
6804 CLASS="PARAMETER"
6805 ><I
6806 >guest ok</I
6807 ></TT
6808 ></A
6809 >, <A
6810 HREF="#READONLY"
6811 >               <TT
6812 CLASS="PARAMETER"
6813 ><I
6814 >read-only</I
6815 ></TT
6816 ></A
6817 > service.</P
6818 ><P
6819 >Also note that the apparent service name will be changed
6820                 to equal that of the requested service, this is very useful as it
6821                 allows you to use macros like <TT
6822 CLASS="PARAMETER"
6823 ><I
6824 >%S</I
6825 ></TT
6826 > to make
6827                 a wildcard service.</P
6828 ><P
6829 >Note also that any "_" characters in the name of the service
6830                 used in the default service will get mapped to a "/". This allows for
6831                 interesting things.</P
6832 ><P
6833 >Example:</P
6834 ><P
6835 ><TABLE
6836 BORDER="0"
6837 BGCOLOR="#E0E0E0"
6838 WIDTH="90%"
6839 ><TR
6840 ><TD
6841 ><PRE
6842 CLASS="PROGRAMLISTING"
6843 >[global]
6844         default service = pub
6845
6846 [pub]
6847         path = /%S
6848                 </PRE
6849 ></TD
6850 ></TR
6851 ></TABLE
6852 ></P
6853 ></DD
6854 ><DT
6855 ><A
6856 NAME="DELETEPRINTERCOMMAND"
6857 ></A
6858 >delete printer command (G)</DT
6859 ><DD
6860 ><P
6861 >With the introduction of MS-RPC based printer
6862                 support for Windows NT/2000 clients in Samba 2.2, it is now
6863                 possible to delete printer at run time by issuing the
6864                 DeletePrinter() RPC call.</P
6865 ><P
6866 >For a Samba host this means that the printer must be
6867                 physically deleted from underlying printing system.  The <TT
6868 CLASS="PARAMETER"
6869 ><I
6870 >               deleteprinter command</I
6871 ></TT
6872 > defines a script to be run which
6873                 will perform the necessary operations for removing the printer
6874                 from the print system and from <TT
6875 CLASS="FILENAME"
6876 >smb.conf</TT
6877 >.
6878                 </P
6879 ><P
6880 >The <TT
6881 CLASS="PARAMETER"
6882 ><I
6883 >delete printer command</I
6884 ></TT
6885 > is
6886                 automatically called with only one parameter: <TT
6887 CLASS="PARAMETER"
6888 ><I
6889 >               "printer name"</I
6890 ></TT
6891 >.</P
6892 ><P
6893 >Once the <TT
6894 CLASS="PARAMETER"
6895 ><I
6896 >delete printer command</I
6897 ></TT
6898 > has
6899                 been executed, <B
6900 CLASS="COMMAND"
6901 >smbd</B
6902 > will reparse the <TT
6903 CLASS="FILENAME"
6904 >               smb.conf</TT
6905 > to associated printer no longer exists.
6906                 If the sharename is still valid, then <B
6907 CLASS="COMMAND"
6908 >smbd
6909                 </B
6910 > will return an ACCESS_DENIED error to the client.</P
6911 ><P
6912 >See also <A
6913 HREF="#ADDPRINTERCOMMAND"
6914 ><TT
6915 CLASS="PARAMETER"
6916 ><I
6917 >               add printer command</I
6918 ></TT
6919 ></A
6920 >, <A
6921 HREF="#PRINTING"
6922 ><TT
6923 CLASS="PARAMETER"
6924 ><I
6925 >printing</I
6926 ></TT
6927 ></A
6928 >,
6929                 <A
6930 HREF="#SHOWADDPRINTERWIZARD"
6931 ><TT
6932 CLASS="PARAMETER"
6933 ><I
6934 >show add
6935                 printer wizard</I
6936 ></TT
6937 ></A
6938 ></P
6939 ><P
6940 >Default: <EM
6941 >none</EM
6942 ></P
6943 ><P
6944 >Example: <B
6945 CLASS="COMMAND"
6946 >deleteprinter command = /usr/bin/removeprinter
6947                 </B
6948 ></P
6949 ></DD
6950 ><DT
6951 ><A
6952 NAME="DELETEREADONLY"
6953 ></A
6954 >delete readonly (S)</DT
6955 ><DD
6956 ><P
6957 >This parameter allows readonly files to be deleted.
6958                 This is not normal DOS semantics, but is allowed by UNIX.</P
6959 ><P
6960 >This option may be useful for running applications such
6961                 as rcs, where UNIX file ownership prevents changing file
6962                 permissions, and DOS semantics prevent deletion of a read only file.</P
6963 ><P
6964 >Default: <B
6965 CLASS="COMMAND"
6966 >delete readonly = no</B
6967 ></P
6968 ></DD
6969 ><DT
6970 ><A
6971 NAME="DELETESHARECOMMAND"
6972 ></A
6973 >delete share command (G)</DT
6974 ><DD
6975 ><P
6976 >Samba 2.2.0 introduced the ability to dynamically
6977                 add and delete shares via the Windows NT 4.0 Server Manager.  The
6978                 <TT
6979 CLASS="PARAMETER"
6980 ><I
6981 >delete share command</I
6982 ></TT
6983 > is used to define an
6984                 external program or script which will remove an existing service
6985                 definition from <TT
6986 CLASS="FILENAME"
6987 >smb.conf</TT
6988 >.  In order to successfully
6989                 execute the <TT
6990 CLASS="PARAMETER"
6991 ><I
6992 >delete share command</I
6993 ></TT
6994 >, <B
6995 CLASS="COMMAND"
6996 >smbd</B
6997 >
6998                 requires that the administrator be connected using a root account (i.e.
6999                 uid == 0).
7000                 </P
7001 ><P
7002 >               When executed, <B
7003 CLASS="COMMAND"
7004 >smbd</B
7005 > will automatically invoke the
7006                 <TT
7007 CLASS="PARAMETER"
7008 ><I
7009 >delete share command</I
7010 ></TT
7011 > with two parameters.
7012                 </P
7013 ><P
7014 ></P
7015 ><UL
7016 ><LI
7017 ><P
7018 ><TT
7019 CLASS="PARAMETER"
7020 ><I
7021 >configFile</I
7022 ></TT
7023 > - the location
7024                         of the global <TT
7025 CLASS="FILENAME"
7026 >smb.conf</TT
7027 > file.
7028                         </P
7029 ></LI
7030 ><LI
7031 ><P
7032 ><TT
7033 CLASS="PARAMETER"
7034 ><I
7035 >shareName</I
7036 ></TT
7037 > - the name of
7038                         the existing service.
7039                         </P
7040 ></LI
7041 ></UL
7042 ><P
7043 >               This parameter is only used to remove file shares.  To delete printer shares,
7044                 see the <A
7045 HREF="#DELETEPRINTERCOMMAND"
7046 ><TT
7047 CLASS="PARAMETER"
7048 ><I
7049 >delete printer
7050                 command</I
7051 ></TT
7052 ></A
7053 >.
7054                 </P
7055 ><P
7056 >               See also <A
7057 HREF="#ADDSHARECOMMAND"
7058 ><TT
7059 CLASS="PARAMETER"
7060 ><I
7061 >add share
7062                 command</I
7063 ></TT
7064 ></A
7065 >, <A
7066 HREF="#CHANGESHARECOMMAND"
7067 ><TT
7068 CLASS="PARAMETER"
7069 ><I
7070 >change
7071                 share command</I
7072 ></TT
7073 ></A
7074 >.
7075                 </P
7076 ><P
7077 >Default: <EM
7078 >none</EM
7079 ></P
7080 ><P
7081 >Example: <B
7082 CLASS="COMMAND"
7083 >delete share command = /usr/local/bin/delshare</B
7084 ></P
7085 ></DD
7086 ><DT
7087 ><A
7088 NAME="DELETEUSERSCRIPT"
7089 ></A
7090 >delete user script (G)</DT
7091 ><DD
7092 ><P
7093 >This is the full pathname to a script that will
7094                 be run <EM
7095 >AS ROOT</EM
7096 > by <A
7097 HREF="smbd.8.html"
7098 TARGET="_top"
7099 >               <B
7100 CLASS="COMMAND"
7101 >smbd(8)</B
7102 ></A
7103 > under special circumstances
7104                 described below.</P
7105 ><P
7106 >Normally, a Samba server requires that UNIX users are
7107                 created for all users accessing files on this server. For sites
7108                 that use Windows NT account databases as their primary user database
7109                 creating these users and keeping the user list in sync with the
7110                 Windows NT PDC is an onerous task. This option allows <B
7111 CLASS="COMMAND"
7112 >               smbd</B
7113 > to delete the required UNIX users <EM
7114 >ON
7115                 DEMAND</EM
7116 > when a user accesses the Samba server and the
7117                 Windows NT user no longer exists.</P
7118 ><P
7119 >In order to use this option, <B
7120 CLASS="COMMAND"
7121 >smbd</B
7122 > must be
7123                 set to <TT
7124 CLASS="PARAMETER"
7125 ><I
7126 >security = domain</I
7127 ></TT
7128 > or <TT
7129 CLASS="PARAMETER"
7130 ><I
7131 >security =
7132                 user</I
7133 ></TT
7134 > and <TT
7135 CLASS="PARAMETER"
7136 ><I
7137 >delete user script</I
7138 ></TT
7139 >
7140                 must be set to a full pathname for a script
7141                 that will delete a UNIX user given one argument of <TT
7142 CLASS="PARAMETER"
7143 ><I
7144 >%u</I
7145 ></TT
7146 >,
7147                 which expands into the UNIX user name to delete.</P
7148 ><P
7149 >When the Windows user attempts to access the Samba server,
7150                 at <EM
7151 >login</EM
7152 > (session setup in the SMB protocol)
7153                 time, <B
7154 CLASS="COMMAND"
7155 >smbd</B
7156 > contacts the <A
7157 HREF="#PASSWORDSERVER"
7158 >               <TT
7159 CLASS="PARAMETER"
7160 ><I
7161 >password server</I
7162 ></TT
7163 ></A
7164 > and attempts to authenticate
7165                 the given user with the given password. If the authentication fails
7166                 with the specific Domain error code meaning that the user no longer
7167                 exists then <B
7168 CLASS="COMMAND"
7169 >smbd</B
7170 > attempts to find a UNIX user in
7171                 the UNIX password database that matches the Windows user account. If
7172                 this lookup succeeds, and <TT
7173 CLASS="PARAMETER"
7174 ><I
7175 >delete user script</I
7176 ></TT
7177 > is
7178                 set then <B
7179 CLASS="COMMAND"
7180 >smbd</B
7181 > will all the specified script
7182                 <EM
7183 >AS ROOT</EM
7184 >, expanding any <TT
7185 CLASS="PARAMETER"
7186 ><I
7187 >%u</I
7188 ></TT
7189 >
7190                 argument to be the user name to delete.</P
7191 ><P
7192 >This script should delete the given UNIX username. In this way,
7193                 UNIX users are dynamically deleted to match existing Windows NT
7194                 accounts.</P
7195 ><P
7196 >See also <A
7197 HREF="#SECURITYEQUALSDOMAIN"
7198 >security = domain</A
7199 >,
7200                 <A
7201 HREF="#PASSWORDSERVER"
7202 ><TT
7203 CLASS="PARAMETER"
7204 ><I
7205 >password server</I
7206 ></TT
7207 >
7208                 </A
7209 >, <A
7210 HREF="#ADDUSERSCRIPT"
7211 ><TT
7212 CLASS="PARAMETER"
7213 ><I
7214 >add user script</I
7215 ></TT
7216 >
7217                 </A
7218 >.</P
7219 ><P
7220 >Default: <B
7221 CLASS="COMMAND"
7222 >delete user script = &#60;empty string&#62;
7223                 </B
7224 ></P
7225 ><P
7226 >Example: <B
7227 CLASS="COMMAND"
7228 >delete user script = /usr/local/samba/bin/del_user
7229                 %u</B
7230 ></P
7231 ></DD
7232 ><DT
7233 ><A
7234 NAME="DELETEVETOFILES"
7235 ></A
7236 >delete veto files (S)</DT
7237 ><DD
7238 ><P
7239 >This option is used when Samba is attempting to
7240                 delete a directory that contains one or more vetoed directories
7241                 (see the <A
7242 HREF="#VETOFILES"
7243 ><TT
7244 CLASS="PARAMETER"
7245 ><I
7246 >veto files</I
7247 ></TT
7248 ></A
7249 >
7250                 option).  If this option is set to <TT
7251 CLASS="CONSTANT"
7252 >no</TT
7253 > (the default) then if a vetoed
7254                 directory contains any non-vetoed files or directories then the
7255                 directory delete will fail. This is usually what you want.</P
7256 ><P
7257 >If this option is set to <TT
7258 CLASS="CONSTANT"
7259 >yes</TT
7260 >, then Samba
7261                 will attempt to recursively delete any files and directories within
7262                 the vetoed directory. This can be useful for integration with file
7263                 serving systems such as NetAtalk which create meta-files within
7264                 directories you might normally veto DOS/Windows users from seeing
7265                 (e.g. <TT
7266 CLASS="FILENAME"
7267 >.AppleDouble</TT
7268 >)</P
7269 ><P
7270 >Setting <B
7271 CLASS="COMMAND"
7272 >delete veto files = yes</B
7273 > allows these
7274                 directories to be  transparently deleted when the parent directory
7275                 is deleted (so long as the user has permissions to do so).</P
7276 ><P
7277 >See also the <A
7278 HREF="#VETOFILES"
7279 ><TT
7280 CLASS="PARAMETER"
7281 ><I
7282 >veto
7283                 files</I
7284 ></TT
7285 ></A
7286 > parameter.</P
7287 ><P
7288 >Default: <B
7289 CLASS="COMMAND"
7290 >delete veto files = no</B
7291 ></P
7292 ></DD
7293 ><DT
7294 ><A
7295 NAME="DENYHOSTS"
7296 ></A
7297 >deny hosts (S)</DT
7298 ><DD
7299 ><P
7300 >Synonym for <A
7301 HREF="#HOSTSDENY"
7302 ><TT
7303 CLASS="PARAMETER"
7304 ><I
7305 >hosts
7306                 deny</I
7307 ></TT
7308 ></A
7309 >.</P
7310 ></DD
7311 ><DT
7312 ><A
7313 NAME="DFREECOMMAND"
7314 ></A
7315 >dfree command (G)</DT
7316 ><DD
7317 ><P
7318 >The <TT
7319 CLASS="PARAMETER"
7320 ><I
7321 >dfree command</I
7322 ></TT
7323 > setting should
7324                 only be used on systems where a problem occurs with the internal
7325                 disk space calculations. This has been known to happen with Ultrix,
7326                 but may occur with other operating systems. The symptom that was
7327                 seen was an error of "Abort Retry Ignore" at the end of each
7328                 directory listing.</P
7329 ><P
7330 >This setting allows the replacement of the internal routines to
7331                 calculate the total disk space and amount available with an external
7332                 routine. The example below gives a possible script that might fulfill
7333                 this function.</P
7334 ><P
7335 >The external program will be passed a single parameter indicating
7336                 a directory in the filesystem being queried. This will typically consist
7337                 of the string <TT
7338 CLASS="FILENAME"
7339 >./</TT
7340 >. The script should return two
7341                 integers in ASCII. The first should be the total disk space in blocks,
7342                 and the second should be the number of available blocks. An optional
7343                 third return value can give the block size in bytes. The default
7344                 blocksize is 1024 bytes.</P
7345 ><P
7346 >Note: Your script should <EM
7347 >NOT</EM
7348 > be setuid or
7349                 setgid and should be owned by (and writeable only by) root!</P
7350 ><P
7351 >Default: <EM
7352 >By default internal routines for
7353                 determining the disk capacity and remaining space will be used.
7354                 </EM
7355 ></P
7356 ><P
7357 >Example: <B
7358 CLASS="COMMAND"
7359 >dfree command = /usr/local/samba/bin/dfree
7360                 </B
7361 ></P
7362 ><P
7363 >Where the script dfree (which must be made executable) could be:</P
7364 ><P
7365 ><TABLE
7366 BORDER="0"
7367 BGCOLOR="#E0E0E0"
7368 WIDTH="90%"
7369 ><TR
7370 ><TD
7371 ><PRE
7372 CLASS="PROGRAMLISTING"
7373 >
7374                 #!/bin/sh
7375                 df $1 | tail -1 | awk '{print $2" "$4}'
7376                 </PRE
7377 ></TD
7378 ></TR
7379 ></TABLE
7380 ></P
7381 ><P
7382 >or perhaps (on Sys V based systems):</P
7383 ><P
7384 ><TABLE
7385 BORDER="0"
7386 BGCOLOR="#E0E0E0"
7387 WIDTH="90%"
7388 ><TR
7389 ><TD
7390 ><PRE
7391 CLASS="PROGRAMLISTING"
7392 >
7393                 #!/bin/sh
7394                 /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
7395                 </PRE
7396 ></TD
7397 ></TR
7398 ></TABLE
7399 ></P
7400 ><P
7401 >Note that you may have to replace the command names
7402                 with full path names on some systems.</P
7403 ></DD
7404 ><DT
7405 ><A
7406 NAME="DIRECTORY"
7407 ></A
7408 >directory (S)</DT
7409 ><DD
7410 ><P
7411 >Synonym for <A
7412 HREF="#PATH"
7413 ><TT
7414 CLASS="PARAMETER"
7415 ><I
7416 >path
7417                 </I
7418 ></TT
7419 ></A
7420 >.</P
7421 ></DD
7422 ><DT
7423 ><A
7424 NAME="DIRECTORYMASK"
7425 ></A
7426 >directory mask (S)</DT
7427 ><DD
7428 ><P
7429 >This parameter is the octal modes which are
7430                 used when converting DOS modes to UNIX modes when creating UNIX
7431                 directories.</P
7432 ><P
7433 >When a directory is created, the necessary permissions are
7434                 calculated according to the mapping from DOS modes to UNIX permissions,
7435                 and the resulting UNIX mode is then bit-wise 'AND'ed with this
7436                 parameter. This parameter may be thought of as a bit-wise MASK for
7437                 the UNIX modes of a directory. Any bit <EM
7438 >not</EM
7439 > set
7440                 here will be removed from the modes set on a directory when it is
7441                 created.</P
7442 ><P
7443 >The default value of this parameter removes the 'group'
7444                 and 'other' write bits from the UNIX mode, allowing only the
7445                 user who owns the directory to modify it.</P
7446 ><P
7447 >Following this Samba will bit-wise 'OR' the UNIX mode
7448                 created from this parameter with the value of the <A
7449 HREF="#FORCEDIRECTORYMODE"
7450 ><TT
7451 CLASS="PARAMETER"
7452 ><I
7453 >force directory mode
7454                 </I
7455 ></TT
7456 ></A
7457 > parameter. This parameter is set to 000 by
7458                 default (i.e. no extra mode bits are added).</P
7459 ><P
7460 >Note that this parameter does not apply to permissions
7461                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
7462                 a mask on access control lists also, they need to set the <A
7463 HREF="#DIRECTORYSECURITYMASK"
7464 ><TT
7465 CLASS="PARAMETER"
7466 ><I
7467 >directory security mask</I
7468 ></TT
7469 ></A
7470 >.</P
7471 ><P
7472 >See the <A
7473 HREF="#FORCEDIRECTORYMODE"
7474 ><TT
7475 CLASS="PARAMETER"
7476 ><I
7477 >force
7478                 directory mode</I
7479 ></TT
7480 ></A
7481 > parameter to cause particular mode
7482                 bits to always be set on created directories.</P
7483 ><P
7484 >See also the <A
7485 HREF="#CREATEMODE"
7486 ><TT
7487 CLASS="PARAMETER"
7488 ><I
7489 >create mode
7490                 </I
7491 ></TT
7492 ></A
7493 > parameter for masking mode bits on created files,
7494                 and the <A
7495 HREF="#DIRECTORYSECURITYMASK"
7496 ><TT
7497 CLASS="PARAMETER"
7498 ><I
7499 >directory
7500                 security mask</I
7501 ></TT
7502 ></A
7503 > parameter.</P
7504 ><P
7505 >Also refer to the <A
7506 HREF="#INHERITPERMISSIONS"
7507 ><TT
7508 CLASS="PARAMETER"
7509 ><I
7510 >               inherit permissions</I
7511 ></TT
7512 ></A
7513 > parameter.</P
7514 ><P
7515 >Default: <B
7516 CLASS="COMMAND"
7517 >directory mask = 0755</B
7518 ></P
7519 ><P
7520 >Example: <B
7521 CLASS="COMMAND"
7522 >directory mask = 0775</B
7523 ></P
7524 ></DD
7525 ><DT
7526 ><A
7527 NAME="DIRECTORYMODE"
7528 ></A
7529 >directory mode (S)</DT
7530 ><DD
7531 ><P
7532 >Synonym for <A
7533 HREF="#DIRECTORYMASK"
7534 ><TT
7535 CLASS="PARAMETER"
7536 ><I
7537 >               directory mask</I
7538 ></TT
7539 ></A
7540 ></P
7541 ></DD
7542 ><DT
7543 ><A
7544 NAME="DIRECTORYSECURITYMASK"
7545 ></A
7546 >directory security mask (S)</DT
7547 ><DD
7548 ><P
7549 >This parameter controls what UNIX permission bits
7550                 can be modified when a Windows NT client is manipulating the UNIX
7551                 permission on a directory using the native NT security dialog
7552                 box.</P
7553 ><P
7554 >This parameter is applied as a mask (AND'ed with) to
7555                 the changed permission bits, thus preventing any bits not in
7556                 this mask from being modified. Essentially, zero bits in this
7557                 mask may be treated as a set of bits the user is not allowed
7558                 to change.</P
7559 ><P
7560 >If not set explicitly this parameter is set to 0777
7561                 meaning a user is allowed to modify all the user/group/world
7562                 permissions on a directory.</P
7563 ><P
7564 ><EM
7565 >Note</EM
7566 > that users who can access the
7567                 Samba server through other means can easily bypass this restriction,
7568                 so it is primarily useful for standalone "appliance" systems.
7569                 Administrators of most normal systems will probably want to leave
7570                 it as the default of <TT
7571 CLASS="CONSTANT"
7572 >0777</TT
7573 >.</P
7574 ><P
7575 >See also the <A
7576 HREF="#FORCEDIRECTORYSECURITYMODE"
7577 ><TT
7578 CLASS="PARAMETER"
7579 ><I
7580 >               force directory security mode</I
7581 ></TT
7582 ></A
7583 >, <A
7584 HREF="#SECURITYMASK"
7585 ><TT
7586 CLASS="PARAMETER"
7587 ><I
7588 >security mask</I
7589 ></TT
7590 ></A
7591 >,
7592                 <A
7593 HREF="#FORCESECURITYMODE"
7594 ><TT
7595 CLASS="PARAMETER"
7596 ><I
7597 >force security mode
7598                 </I
7599 ></TT
7600 ></A
7601 > parameters.</P
7602 ><P
7603 >Default: <B
7604 CLASS="COMMAND"
7605 >directory security mask = 0777</B
7606 ></P
7607 ><P
7608 >Example: <B
7609 CLASS="COMMAND"
7610 >directory security mask = 0700</B
7611 ></P
7612 ></DD
7613 ><DT
7614 ><A
7615 NAME="DISABLESPOOLSS"
7616 ></A
7617 >disable spoolss (G)</DT
7618 ><DD
7619 ><P
7620 >Enabling this parameter will disables Samba's support
7621                 for the SPOOLSS set of MS-RPC's and will yield identical behavior
7622                 as Samba 2.0.x.  Windows NT/2000 clients will downgrade to using
7623                 Lanman style printing commands. Windows 9x/ME will be uneffected by
7624                 the parameter. However, this will also disable the ability to upload
7625                 printer drivers to a Samba server via the Windows NT Add Printer
7626                 Wizard or by using the NT printer properties dialog window.  It will
7627                 also disable the capability of Windows NT/2000 clients to download
7628                 print drivers from the Samba host upon demand.
7629                 <EM
7630 >Be very careful about enabling this parameter.</EM
7631 >
7632                 </P
7633 ><P
7634 >See also <A
7635 HREF="#USECLIENTDRIVER"
7636 >use client driver</A
7637 >
7638                 </P
7639 ><P
7640 >Default : <B
7641 CLASS="COMMAND"
7642 >disable spoolss = no</B
7643 ></P
7644 ></DD
7645 ><DT
7646 ><A
7647 NAME="DNSPROXY"
7648 ></A
7649 >dns proxy (G)</DT
7650 ><DD
7651 ><P
7652 >Specifies that <A
7653 HREF="nmbd.8.html"
7654 TARGET="_top"
7655 >nmbd(8)</A
7656 >
7657                 when acting as a WINS server and finding that a NetBIOS name has not
7658                 been registered, should treat the NetBIOS name word-for-word as a DNS
7659                 name and do a lookup with the DNS server for that name on behalf of
7660                 the name-querying client.</P
7661 ><P
7662 >Note that the maximum length for a NetBIOS name is 15
7663                 characters, so the DNS name (or DNS alias) can likewise only be
7664                 15 characters, maximum.</P
7665 ><P
7666 ><B
7667 CLASS="COMMAND"
7668 >nmbd</B
7669 > spawns a second copy of itself to do the
7670                 DNS name lookup requests, as doing a name lookup is a blocking
7671                 action.</P
7672 ><P
7673 >See also the parameter <A
7674 HREF="#WINSSUPPORT"
7675 ><TT
7676 CLASS="PARAMETER"
7677 ><I
7678 >               wins support</I
7679 ></TT
7680 ></A
7681 >.</P
7682 ><P
7683 >Default: <B
7684 CLASS="COMMAND"
7685 >dns proxy = yes</B
7686 ></P
7687 ></DD
7688 ><DT
7689 ><A
7690 NAME="DOMAINADMINGROUP"
7691 ></A
7692 >domain admin group (G)</DT
7693 ><DD
7694 ><P
7695 >This parameter is intended as a temporary solution
7696                 to enable users to be a member of the "Domain Admins" group when
7697                 a Samba host is acting as a PDC.  A complete solution will be provided
7698                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7699                 Please note that this parameter has a somewhat confusing name.  It
7700                 accepts a list of usernames and of group names in standard
7701                 <TT
7702 CLASS="FILENAME"
7703 >smb.conf</TT
7704 >       notation.
7705                 </P
7706 ><P
7707 >See also <A
7708 HREF="#DOMAINGUESTGROUP"
7709 ><TT
7710 CLASS="PARAMETER"
7711 ><I
7712 >domain
7713                 guest group</I
7714 ></TT
7715 ></A
7716 >, <A
7717 HREF="#DOMAINLOGONS"
7718 ><TT
7719 CLASS="PARAMETER"
7720 ><I
7721 >domain
7722                 logons</I
7723 ></TT
7724 ></A
7725 >
7726                 </P
7727 ><P
7728 >Default: <EM
7729 >no domain administrators</EM
7730 ></P
7731 ><P
7732 >Example: <B
7733 CLASS="COMMAND"
7734 >domain admin group = root @wheel</B
7735 ></P
7736 ></DD
7737 ><DT
7738 ><A
7739 NAME="DOMAINGUESTGROUP"
7740 ></A
7741 >domain guest group (G)</DT
7742 ><DD
7743 ><P
7744 >This parameter is intended as a temporary solution
7745                 to enable users to be a member of the "Domain Guests" group when
7746                 a Samba host is acting as a PDC.  A complete solution will be provided
7747                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7748                 Please note that this parameter has a somewhat confusing name.  It
7749                 accepts a list of usernames and of group names in standard
7750                 <TT
7751 CLASS="FILENAME"
7752 >smb.conf</TT
7753 >       notation.
7754                 </P
7755 ><P
7756 >See also <A
7757 HREF="#DOMAINADMINGROUP"
7758 ><TT
7759 CLASS="PARAMETER"
7760 ><I
7761 >domain
7762                 admin group</I
7763 ></TT
7764 ></A
7765 >, <A
7766 HREF="#DOMAINLOGONS"
7767 ><TT
7768 CLASS="PARAMETER"
7769 ><I
7770 >domain
7771                 logons</I
7772 ></TT
7773 ></A
7774 >
7775                 </P
7776 ><P
7777 >Default: <EM
7778 >no domain guests</EM
7779 ></P
7780 ><P
7781 >Example: <B
7782 CLASS="COMMAND"
7783 >domain guest group = nobody @guest</B
7784 ></P
7785 ></DD
7786 ><DT
7787 ><A
7788 NAME="DOMAINLOGONS"
7789 ></A
7790 >domain logons (G)</DT
7791 ><DD
7792 ><P
7793 >If set to <TT
7794 CLASS="CONSTANT"
7795 >yes</TT
7796 >, the Samba server will serve
7797                 Windows 95/98 Domain logons for the <A
7798 HREF="#WORKGROUP"
7799 >               <TT
7800 CLASS="PARAMETER"
7801 ><I
7802 >workgroup</I
7803 ></TT
7804 ></A
7805 > it is in. Samba 2.2 also
7806                 has limited capability to act as a domain controller for Windows
7807                 NT 4 Domains.  For more details on setting up this feature see
7808                 the Samba-PDC-HOWTO included in the <TT
7809 CLASS="FILENAME"
7810 >htmldocs/</TT
7811 >
7812                 directory shipped with the source code.</P
7813 ><P
7814 >Default: <B
7815 CLASS="COMMAND"
7816 >domain logons = no</B
7817 ></P
7818 ></DD
7819 ><DT
7820 ><A
7821 NAME="DOMAINMASTER"
7822 ></A
7823 >domain master (G)</DT
7824 ><DD
7825 ><P
7826 >Tell <A
7827 HREF="nmbd.8.html"
7828 TARGET="_top"
7829 ><B
7830 CLASS="COMMAND"
7831 >               nmbd(8)</B
7832 ></A
7833 > to enable WAN-wide browse list
7834                 collation. Setting this option causes <B
7835 CLASS="COMMAND"
7836 >nmbd</B
7837 > to
7838                 claim a special domain specific NetBIOS name that identifies
7839                 it as a domain master browser for its given <A
7840 HREF="#WORKGROUP"
7841 >               <TT
7842 CLASS="PARAMETER"
7843 ><I
7844 >workgroup</I
7845 ></TT
7846 ></A
7847 >. Local master browsers
7848                 in the same <TT
7849 CLASS="PARAMETER"
7850 ><I
7851 >workgroup</I
7852 ></TT
7853 > on broadcast-isolated
7854                 subnets will give this <B
7855 CLASS="COMMAND"
7856 >nmbd</B
7857 > their local browse lists,
7858                 and then ask <A
7859 HREF="smbd.8.html"
7860 TARGET="_top"
7861 ><B
7862 CLASS="COMMAND"
7863 >smbd(8)</B
7864 ></A
7865 >
7866                 for a complete copy of the browse list for the whole wide area
7867                 network.  Browser clients will then contact their local master browser,
7868                 and will receive the domain-wide browse list, instead of just the list
7869                 for their broadcast-isolated subnet.</P
7870 ><P
7871 >Note that Windows NT Primary Domain Controllers expect to be
7872                 able to claim this <TT
7873 CLASS="PARAMETER"
7874 ><I
7875 >workgroup</I
7876 ></TT
7877 > specific special
7878                 NetBIOS name that identifies them as domain master browsers for
7879                 that <TT
7880 CLASS="PARAMETER"
7881 ><I
7882 >workgroup</I
7883 ></TT
7884 > by default (i.e. there is no
7885                 way to prevent a Windows NT PDC from attempting to do this). This
7886                 means that if this parameter is set and <B
7887 CLASS="COMMAND"
7888 >nmbd</B
7889 > claims
7890                 the special name for a <TT
7891 CLASS="PARAMETER"
7892 ><I
7893 >workgroup</I
7894 ></TT
7895 > before a Windows
7896                 NT PDC is able to do so then cross subnet browsing will behave
7897                 strangely and may fail.</P
7898 ><P
7899 >If <A
7900 HREF="#DOMAINLOGONS"
7901 ><B
7902 CLASS="COMMAND"
7903 >domain logons = yes</B
7904 >
7905                 </A
7906 >, then the default behavior is to enable the <TT
7907 CLASS="PARAMETER"
7908 ><I
7909 >domain
7910                 master</I
7911 ></TT
7912 > parameter.  If <TT
7913 CLASS="PARAMETER"
7914 ><I
7915 >domain logons</I
7916 ></TT
7917 > is
7918                 not enabled (the default setting), then neither will <TT
7919 CLASS="PARAMETER"
7920 ><I
7921 >domain
7922                 master</I
7923 ></TT
7924 > be enabled by default.</P
7925 ><P
7926 >Default: <B
7927 CLASS="COMMAND"
7928 >domain master = auto</B
7929 ></P
7930 ></DD
7931 ><DT
7932 ><A
7933 NAME="DONTDESCEND"
7934 ></A
7935 >dont descend (S)</DT
7936 ><DD
7937 ><P
7938 >There are certain directories on some systems
7939                 (e.g., the <TT
7940 CLASS="FILENAME"
7941 >/proc</TT
7942 > tree under Linux) that are either not
7943                 of interest to clients or are infinitely deep (recursive). This
7944                 parameter allows you to specify a comma-delimited list of directories
7945                 that the server should always show as empty.</P
7946 ><P
7947 >Note that Samba can be very fussy about the exact format
7948                 of the "dont descend" entries. For example you may need <TT
7949 CLASS="FILENAME"
7950 >               ./proc</TT
7951 > instead of just <TT
7952 CLASS="FILENAME"
7953 >/proc</TT
7954 >.
7955                 Experimentation is the best policy :-)  </P
7956 ><P
7957 >Default: <EM
7958 >none (i.e., all directories are OK
7959                 to descend)</EM
7960 ></P
7961 ><P
7962 >Example: <B
7963 CLASS="COMMAND"
7964 >dont descend = /proc,/dev</B
7965 ></P
7966 ></DD
7967 ><DT
7968 ><A
7969 NAME="DOSFILEMODE"
7970 ></A
7971 >dos filemode (S)</DT
7972 ><DD
7973 ><P
7974 > The default behavior in Samba is to provide
7975                 UNIX-like behavior where only the owner of a file/directory is
7976                 able to change the permissions on it.  However, this behavior
7977                 is often confusing to  DOS/Windows users.  Enabling this parameter
7978                 allows a user who has write access to the file (by whatever
7979                 means) to modify the permissions on it.  Note that a user
7980                 belonging to the group owning the file will not be allowed to
7981                 change permissions if the group is only granted read access.
7982                 Ownership of the file/directory is not changed, only the permissions
7983                 are modified.</P
7984 ><P
7985 >Default: <B
7986 CLASS="COMMAND"
7987 >dos filemode = no</B
7988 ></P
7989 ></DD
7990 ><DT
7991 ><A
7992 NAME="DOSFILETIMERESOLUTION"
7993 ></A
7994 >dos filetime resolution (S)</DT
7995 ><DD
7996 ><P
7997 >Under the DOS and Windows FAT filesystem, the finest
7998                 granularity on time resolution is two seconds. Setting this parameter
7999                 for a share causes Samba to round the reported time down to the
8000                 nearest two second boundary when a query call that requires one second
8001                 resolution is made to <A
8002 HREF="smbd.8.html"
8003 TARGET="_top"
8004 ><B
8005 CLASS="COMMAND"
8006 >smbd(8)</B
8007 >
8008                 </A
8009 >.</P
8010 ><P
8011 >This option is mainly used as a compatibility option for Visual
8012                 C++ when used against Samba shares. If oplocks are enabled on a
8013                 share, Visual C++ uses two different time reading calls to check if a
8014                 file has changed since it was last read. One of these calls uses a
8015                 one-second granularity, the other uses a two second granularity. As
8016                 the two second call rounds any odd second down, then if the file has a
8017                 timestamp of an odd number of seconds then the two timestamps will not
8018                 match and Visual C++ will keep reporting the file has changed. Setting
8019                 this option causes the two timestamps to match, and Visual C++ is
8020                 happy.</P
8021 ><P
8022 >Default: <B
8023 CLASS="COMMAND"
8024 >dos filetime resolution = no</B
8025 ></P
8026 ></DD
8027 ><DT
8028 ><A
8029 NAME="DOSFILETIMES"
8030 ></A
8031 >dos filetimes (S)</DT
8032 ><DD
8033 ><P
8034 >Under DOS and Windows, if a user can write to a
8035                 file they can change the timestamp on it. Under POSIX semantics,
8036                 only the owner of the file or root may change the timestamp. By
8037                 default, Samba runs with POSIX semantics and refuses to change the
8038                 timestamp on a file if the user <B
8039 CLASS="COMMAND"
8040 >smbd</B
8041 > is acting
8042                 on behalf of is not the file owner. Setting this option to <TT
8043 CLASS="CONSTANT"
8044 >               yes</TT
8045 > allows DOS semantics and <A
8046 HREF="smbd.8.html"
8047 TARGET="_top"
8048 >smbd</A
8049 > will change the file
8050                 timestamp as DOS requires.</P
8051 ><P
8052 >Default: <B
8053 CLASS="COMMAND"
8054 >dos filetimes = no</B
8055 ></P
8056 ></DD
8057 ><DT
8058 ><A
8059 NAME="ENCRYPTPASSWORDS"
8060 ></A
8061 >encrypt passwords (G)</DT
8062 ><DD
8063 ><P
8064 >This boolean controls whether encrypted passwords
8065                 will be negotiated with the client. Note that Windows NT 4.0 SP3 and
8066                 above and also Windows 98 will by default expect encrypted passwords
8067                 unless a registry entry is changed. To use encrypted passwords in
8068                 Samba see the file ENCRYPTION.txt in the Samba documentation
8069                 directory <TT
8070 CLASS="FILENAME"
8071 >docs/</TT
8072 > shipped with the source code.</P
8073 ><P
8074 >In order for encrypted passwords to work correctly
8075                 <A
8076 HREF="smbd.8.html"
8077 TARGET="_top"
8078 ><B
8079 CLASS="COMMAND"
8080 >smbd(8)</B
8081 ></A
8082 > must either
8083                 have access to a local <A
8084 HREF="smbpasswd.5.html"
8085 TARGET="_top"
8086 ><TT
8087 CLASS="FILENAME"
8088 >smbpasswd(5)
8089                 </TT
8090 ></A
8091 > file (see the <A
8092 HREF="smbpasswd.8.html"
8093 TARGET="_top"
8094 ><B
8095 CLASS="COMMAND"
8096 >               smbpasswd(8)</B
8097 ></A
8098 > program for information on how to set up
8099                 and maintain this file), or set the <A
8100 HREF="#SECURITY"
8101 >security = [server|domain]</A
8102 > parameter which
8103                 causes <B
8104 CLASS="COMMAND"
8105 >smbd</B
8106 > to authenticate against another
8107                 server.</P
8108 ><P
8109 >Default: <B
8110 CLASS="COMMAND"
8111 >encrypt passwords = no</B
8112 ></P
8113 ></DD
8114 ><DT
8115 ><A
8116 NAME="ENHANCEDBROWSING"
8117 ></A
8118 >enhanced browsing (G)</DT
8119 ><DD
8120 ><P
8121 >This option enables a couple of enhancements to
8122                 cross-subnet browse propagation that have been added in Samba
8123                 but which are not standard in Microsoft implementations.
8124                 </P
8125 ><P
8126 >The first enhancement to browse propagation consists of a regular
8127                 wildcard query to a Samba WINS server for all Domain Master Browsers,
8128                 followed by a browse synchronization with each of the returned
8129                 DMBs. The second enhancement consists of a regular randomised browse
8130                 synchronization with all currently known DMBs.</P
8131 ><P
8132 >You may wish to disable this option if you have a problem with empty
8133                 workgroups not disappearing from browse lists. Due to the restrictions
8134                 of the browse protocols these enhancements can cause a empty workgroup
8135                 to stay around forever which can be annoying.</P
8136 ><P
8137 >In general you should leave this option enabled as it makes
8138                 cross-subnet browse propagation much more reliable.</P
8139 ><P
8140 >Default: <B
8141 CLASS="COMMAND"
8142 >enhanced browsing = yes</B
8143 ></P
8144 ></DD
8145 ><DT
8146 ><A
8147 NAME="ENUMPORTSCOMMAND"
8148 ></A
8149 >enumports command (G)</DT
8150 ><DD
8151 ><P
8152 >The concept of a "port" is fairly foreign
8153                 to UNIX hosts.  Under Windows NT/2000 print servers, a port
8154                 is associated with a port monitor and generally takes the form of
8155                 a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
8156                 (i.e. LPD Port Monitor, etc...).  By default, Samba has only one
8157                 port defined--<TT
8158 CLASS="CONSTANT"
8159 >"Samba Printer Port"</TT
8160 >.  Under
8161                 Windows NT/2000, all printers must have a valid port name.
8162                 If you wish to have a list of ports displayed (<B
8163 CLASS="COMMAND"
8164 >smbd
8165                 </B
8166 > does not use a port name for anything) other than
8167                 the default <TT
8168 CLASS="CONSTANT"
8169 >"Samba Printer Port"</TT
8170 >, you
8171                 can define <TT
8172 CLASS="PARAMETER"
8173 ><I
8174 >enumports command</I
8175 ></TT
8176 > to point to
8177                 a program which should generate a list of ports, one per line,
8178                 to standard output.  This listing will then be used in response
8179                 to the level 1 and 2 EnumPorts() RPC.</P
8180 ><P
8181 >Default: <EM
8182 >no enumports command</EM
8183 ></P
8184 ><P
8185 >Example: <B
8186 CLASS="COMMAND"
8187 >enumports command = /usr/bin/listports
8188                 </B
8189 ></P
8190 ></DD
8191 ><DT
8192 ><A
8193 NAME="EXEC"
8194 ></A
8195 >exec (S)</DT
8196 ><DD
8197 ><P
8198 >This is a synonym for <A
8199 HREF="#PREEXEC"
8200 >               <TT
8201 CLASS="PARAMETER"
8202 ><I
8203 >preexec</I
8204 ></TT
8205 ></A
8206 >.</P
8207 ></DD
8208 ><DT
8209 ><A
8210 NAME="FAKEDIRECTORYCREATETIMES"
8211 ></A
8212 >fake directory create times (S)</DT
8213 ><DD
8214 ><P
8215 >NTFS and Windows VFAT file systems keep a create
8216                 time for all files and directories. This is not the same as the
8217                 ctime - status change time - that Unix keeps, so Samba by default
8218                 reports the earliest of the various times Unix does keep. Setting
8219                 this parameter for a share causes Samba to always report midnight
8220                 1-1-1980 as the create time for directories.</P
8221 ><P
8222 >This option is mainly used as a compatibility option for
8223                 Visual C++ when used against Samba shares. Visual C++ generated
8224                 makefiles have the object directory as a dependency for each object
8225                 file, and a make rule to create the directory. Also, when NMAKE
8226                 compares timestamps it uses the creation time when examining a
8227                 directory. Thus the object directory will be created if it does not
8228                 exist, but once it does exist it will always have an earlier
8229                 timestamp than the object files it contains.</P
8230 ><P
8231 >However, Unix time semantics mean that the create time
8232                 reported by Samba will be updated whenever a file is created or
8233                 or deleted in the directory.  NMAKE finds all object files in
8234                 the object directory.  The timestamp of the last one built is then
8235                 compared to the timestamp of the object directory.  If the
8236                 directory's timestamp if newer, then all object files
8237                 will be rebuilt.  Enabling this option
8238                 ensures directories always predate their contents and an NMAKE build
8239                 will proceed as expected.</P
8240 ><P
8241 >Default: <B
8242 CLASS="COMMAND"
8243 >fake directory create times = no</B
8244 ></P
8245 ></DD
8246 ><DT
8247 ><A
8248 NAME="FAKEOPLOCKS"
8249 ></A
8250 >fake oplocks (S)</DT
8251 ><DD
8252 ><P
8253 >Oplocks are the way that SMB clients get permission
8254                 from a server to locally cache file operations. If a server grants
8255                 an oplock (opportunistic lock) then the client is free to assume
8256                 that it is the only one accessing the file and it will aggressively
8257                 cache file data. With some oplock types the client may even cache
8258                 file open/close operations. This can give enormous performance benefits.
8259                 </P
8260 ><P
8261 >When you set <B
8262 CLASS="COMMAND"
8263 >fake oplocks = yes</B
8264 >, <A
8265 HREF="smbd.8.html"
8266 TARGET="_top"
8267 ><B
8268 CLASS="COMMAND"
8269 >smbd(8)</B
8270 ></A
8271 > will
8272                 always grant oplock requests no matter how many clients are using
8273                 the file.</P
8274 ><P
8275 >It is generally much better to use the real <A
8276 HREF="#OPLOCKS"
8277 ><TT
8278 CLASS="PARAMETER"
8279 ><I
8280 >oplocks</I
8281 ></TT
8282 ></A
8283 > support rather
8284                 than this parameter.</P
8285 ><P
8286 >If you enable this option on all read-only shares or
8287                 shares that you know will only be accessed from one client at a
8288                 time such as physically read-only media like CDROMs, you will see
8289                 a big performance improvement on many operations. If you enable
8290                 this option on shares where multiple clients may be accessing the
8291                 files read-write at the same time you can get data corruption. Use
8292                 this option carefully!</P
8293 ><P
8294 >Default: <B
8295 CLASS="COMMAND"
8296 >fake oplocks = no</B
8297 ></P
8298 ></DD
8299 ><DT
8300 ><A
8301 NAME="FOLLOWSYMLINKS"
8302 ></A
8303 >follow symlinks (S)</DT
8304 ><DD
8305 ><P
8306 >This parameter allows the Samba administrator
8307                 to stop <A
8308 HREF="smbd.8.html"
8309 TARGET="_top"
8310 ><B
8311 CLASS="COMMAND"
8312 >smbd(8)</B
8313 ></A
8314 >
8315                 from following symbolic links in a particular share. Setting this
8316                 parameter to <TT
8317 CLASS="CONSTANT"
8318 >no</TT
8319 > prevents any file or directory
8320                 that is a symbolic link from being followed (the user will get an
8321                 error).  This option is very useful to stop users from adding a
8322                 symbolic link to <TT
8323 CLASS="FILENAME"
8324 >/etc/passwd</TT
8325 > in their home
8326                 directory for instance.  However it will slow filename lookups
8327                 down slightly.</P
8328 ><P
8329 >This option is enabled (i.e. <B
8330 CLASS="COMMAND"
8331 >smbd</B
8332 > will
8333                 follow symbolic links) by default.</P
8334 ><P
8335 >Default: <B
8336 CLASS="COMMAND"
8337 >follow symlinks = yes</B
8338 ></P
8339 ></DD
8340 ><DT
8341 ><A
8342 NAME="FORCECREATEMODE"
8343 ></A
8344 >force create mode (S)</DT
8345 ><DD
8346 ><P
8347 >This parameter specifies a set of UNIX mode bit
8348                 permissions that will <EM
8349 >always</EM
8350 > be set on a
8351                 file created by Samba. This is done by bitwise 'OR'ing these bits onto
8352                 the mode bits of a file that is being created or having its
8353                 permissions changed. The default for this parameter is (in octal)
8354                 000. The modes in this parameter are bitwise 'OR'ed onto the file
8355                 mode after the mask set in the <TT
8356 CLASS="PARAMETER"
8357 ><I
8358 >create mask</I
8359 ></TT
8360 >
8361                 parameter is applied.</P
8362 ><P
8363 >See also the parameter <A
8364 HREF="#CREATEMASK"
8365 ><TT
8366 CLASS="PARAMETER"
8367 ><I
8368 >create
8369                 mask</I
8370 ></TT
8371 ></A
8372 > for details on masking mode bits on files.</P
8373 ><P
8374 >See also the <A
8375 HREF="#INHERITPERMISSIONS"
8376 ><TT
8377 CLASS="PARAMETER"
8378 ><I
8379 >inherit
8380                 permissions</I
8381 ></TT
8382 ></A
8383 > parameter.</P
8384 ><P
8385 >Default: <B
8386 CLASS="COMMAND"
8387 >force create mode = 000</B
8388 ></P
8389 ><P
8390 >Example: <B
8391 CLASS="COMMAND"
8392 >force create mode = 0755</B
8393 ></P
8394 ><P
8395 >would force all created files to have read and execute
8396                 permissions set for 'group' and 'other' as well as the
8397                 read/write/execute bits set for the 'user'.</P
8398 ></DD
8399 ><DT
8400 ><A
8401 NAME="FORCEDIRECTORYMODE"
8402 ></A
8403 >force directory mode (S)</DT
8404 ><DD
8405 ><P
8406 >This parameter specifies a set of UNIX mode bit
8407                 permissions that will <EM
8408 >always</EM
8409 > be set on a directory
8410                 created by Samba. This is done by bitwise 'OR'ing these bits onto the
8411                 mode bits of a directory that is being created. The default for this
8412                 parameter is (in octal) 0000 which will not add any extra permission
8413                 bits to a created directory. This operation is done after the mode
8414                 mask in the parameter <TT
8415 CLASS="PARAMETER"
8416 ><I
8417 >directory mask</I
8418 ></TT
8419 > is
8420                 applied.</P
8421 ><P
8422 >See also the parameter <A
8423 HREF="#DIRECTORYMASK"
8424 ><TT
8425 CLASS="PARAMETER"
8426 ><I
8427 >               directory mask</I
8428 ></TT
8429 ></A
8430 > for details on masking mode bits
8431                 on created directories.</P
8432 ><P
8433 >See also the <A
8434 HREF="#INHERITPERMISSIONS"
8435 ><TT
8436 CLASS="PARAMETER"
8437 ><I
8438 >               inherit permissions</I
8439 ></TT
8440 ></A
8441 > parameter.</P
8442 ><P
8443 >Default: <B
8444 CLASS="COMMAND"
8445 >force directory mode = 000</B
8446 ></P
8447 ><P
8448 >Example: <B
8449 CLASS="COMMAND"
8450 >force directory mode = 0755</B
8451 ></P
8452 ><P
8453 >would force all created directories to have read and execute
8454                 permissions set for 'group' and 'other' as well as the
8455                 read/write/execute bits set for the 'user'.</P
8456 ></DD
8457 ><DT
8458 ><A
8459 NAME="FORCEDIRECTORYSECURITYMODE"
8460 ></A
8461 >force directory
8462                 security mode (S)</DT
8463 ><DD
8464 ><P
8465 >This parameter controls what UNIX permission bits
8466                 can be modified when a Windows NT client is manipulating the UNIX
8467                 permission on a directory using the native NT security dialog box.</P
8468 ><P
8469 >This parameter is applied as a mask (OR'ed with) to the
8470                 changed permission bits, thus forcing any bits in this mask that
8471                 the user may have modified to be on. Essentially, one bits in this
8472                 mask may be treated as a set of bits that, when modifying security
8473                 on a directory, the user has always set to be 'on'.</P
8474 ><P
8475 >If not set explicitly this parameter is 000, which
8476                 allows a user to modify all the user/group/world permissions on a
8477                 directory without restrictions.</P
8478 ><P
8479 ><EM
8480 >Note</EM
8481 > that users who can access the
8482                 Samba server through other means can easily bypass this restriction,
8483                 so it is primarily useful for standalone "appliance" systems.
8484                 Administrators of most normal systems will probably want to leave
8485                 it set as 0000.</P
8486 ><P
8487 >See also the <A
8488 HREF="#DIRECTORYSECURITYMASK"
8489 ><TT
8490 CLASS="PARAMETER"
8491 ><I
8492 >               directory security mask</I
8493 ></TT
8494 ></A
8495 >, <A
8496 HREF="#SECURITYMASK"
8497 >               <TT
8498 CLASS="PARAMETER"
8499 ><I
8500 >security mask</I
8501 ></TT
8502 ></A
8503 >,
8504                 <A
8505 HREF="#FORCESECURITYMODE"
8506 ><TT
8507 CLASS="PARAMETER"
8508 ><I
8509 >force security mode
8510                 </I
8511 ></TT
8512 ></A
8513 > parameters.</P
8514 ><P
8515 >Default: <B
8516 CLASS="COMMAND"
8517 >force directory security mode = 0</B
8518 ></P
8519 ><P
8520 >Example: <B
8521 CLASS="COMMAND"
8522 >force directory security mode = 700</B
8523 ></P
8524 ></DD
8525 ><DT
8526 ><A
8527 NAME="FORCEGROUP"
8528 ></A
8529 >force group (S)</DT
8530 ><DD
8531 ><P
8532 >This specifies a UNIX group name that will be
8533                 assigned as the default primary group for all users connecting
8534                 to this service. This is useful for sharing files by ensuring
8535                 that all access to files on service will use the named group for
8536                 their permissions checking. Thus, by assigning permissions for this
8537                 group to the files and directories within this service the Samba
8538                 administrator can restrict or allow sharing of these files.</P
8539 ><P
8540 >In Samba 2.0.5 and above this parameter has extended
8541                 functionality in the following way. If the group name listed here
8542                 has a '+' character prepended to it then the current user accessing
8543                 the share only has the primary group default assigned to this group
8544                 if they are already assigned as a member of that group. This allows
8545                 an administrator to decide that only users who are already in a
8546                 particular group will create files with group ownership set to that
8547                 group. This gives a finer granularity of ownership assignment. For
8548                 example, the setting <TT
8549 CLASS="FILENAME"
8550 >force group = +sys</TT
8551 > means
8552                 that only users who are already in group sys will have their default
8553                 primary group assigned to sys when accessing this Samba share. All
8554                 other users will retain their ordinary primary group.</P
8555 ><P
8556 >If the <A
8557 HREF="#FORCEUSER"
8558 ><TT
8559 CLASS="PARAMETER"
8560 ><I
8561 >force user
8562                 </I
8563 ></TT
8564 ></A
8565 > parameter is also set the group specified in
8566                 <TT
8567 CLASS="PARAMETER"
8568 ><I
8569 >force group</I
8570 ></TT
8571 > will override the primary group
8572                 set in <TT
8573 CLASS="PARAMETER"
8574 ><I
8575 >force user</I
8576 ></TT
8577 >.</P
8578 ><P
8579 >See also <A
8580 HREF="#FORCEUSER"
8581 ><TT
8582 CLASS="PARAMETER"
8583 ><I
8584 >force
8585                 user</I
8586 ></TT
8587 ></A
8588 >.</P
8589 ><P
8590 >Default: <EM
8591 >no forced group</EM
8592 ></P
8593 ><P
8594 >Example: <B
8595 CLASS="COMMAND"
8596 >force group = agroup</B
8597 ></P
8598 ></DD
8599 ><DT
8600 ><A
8601 NAME="FORCESECURITYMODE"
8602 ></A
8603 >force security mode (S)</DT
8604 ><DD
8605 ><P
8606 >This parameter controls what UNIX permission
8607                 bits can be modified when a Windows NT client is manipulating
8608                 the UNIX permission on a file using the native NT security dialog
8609                 box.</P
8610 ><P
8611 >This parameter is applied as a mask (OR'ed with) to the
8612                 changed permission bits, thus forcing any bits in this mask that
8613                 the user may have modified to be on. Essentially, one bits in this
8614                 mask may be treated as a set of bits that, when modifying security
8615                 on a file, the user has always set to be 'on'.</P
8616 ><P
8617 >If not set explicitly this parameter is set to 0,
8618                 and allows a user to modify all the user/group/world permissions on a file,
8619                 with no restrictions.</P
8620 ><P
8621 ><EM
8622 >Note</EM
8623 > that users who can access
8624                 the Samba server through other means can easily bypass this restriction,
8625                 so it is primarily useful for standalone "appliance" systems.
8626                 Administrators of most normal systems will probably want to leave
8627                 this set to 0000.</P
8628 ><P
8629 >See also the <A
8630 HREF="#FORCEDIRECTORYSECURITYMODE"
8631 ><TT
8632 CLASS="PARAMETER"
8633 ><I
8634 >               force directory security mode</I
8635 ></TT
8636 ></A
8637 >,
8638                 <A
8639 HREF="#DIRECTORYSECURITYMASK"
8640 ><TT
8641 CLASS="PARAMETER"
8642 ><I
8643 >directory security
8644                 mask</I
8645 ></TT
8646 ></A
8647 >, <A
8648 HREF="#SECURITYMASK"
8649 ><TT
8650 CLASS="PARAMETER"
8651 ><I
8652 >               security mask</I
8653 ></TT
8654 ></A
8655 > parameters.</P
8656 ><P
8657 >Default: <B
8658 CLASS="COMMAND"
8659 >force security mode = 0</B
8660 ></P
8661 ><P
8662 >Example: <B
8663 CLASS="COMMAND"
8664 >force security mode = 700</B
8665 ></P
8666 ></DD
8667 ><DT
8668 ><A
8669 NAME="FORCEUNKNOWNACLUSER"
8670 ></A
8671 >force unknown acl user (S)</DT
8672 ><DD
8673 ><P
8674 >If this parameter is set, a Windows NT ACL that contains
8675                 an unknown SID (security descriptor, or representation of a user or group id)
8676                 as the owner or group owner of the file will be silently mapped into the
8677                 current UNIX uid or gid of the currently connected user.</P
8678 ><P
8679 >This is designed to allow Windows NT clients to copy files and
8680                 folders containing ACLs that were created locally on the client machine
8681                 and contain users local to that machine only (no domain users) to be
8682                 copied to a Samba server (usually with XCOPY /O) and have the unknown
8683                 userid and groupid of the file owner map to the current connected user.
8684                 This can only be fixed correctly when winbindd allows arbitrary mapping
8685                 from any Windows NT SID to a UNIX uid or gid.</P
8686 ><P
8687 >Try using this parameter when XCOPY /O gives an ACCESS_DENIED error.
8688                 </P
8689 ><P
8690 >See also <A
8691 HREF="#FORCEGROUP"
8692 ><TT
8693 CLASS="PARAMETER"
8694 ><I
8695 >force group
8696                 </I
8697 ></TT
8698 ></A
8699 ></P
8700 ><P
8701 >Default: <EM
8702 >False</EM
8703 ></P
8704 ><P
8705 >Example: <B
8706 CLASS="COMMAND"
8707 >force unknown acl user = yes</B
8708 ></P
8709 ></DD
8710 ><DT
8711 ><A
8712 NAME="FORCEUSER"
8713 ></A
8714 >force user (S)</DT
8715 ><DD
8716 ><P
8717 >This specifies a UNIX user name that will be
8718                 assigned as the default user for all users connecting to this service.
8719                 This is useful for sharing files. You should also use it carefully
8720                 as using it incorrectly can cause security problems.</P
8721 ><P
8722 >This user name only gets used once a connection is established.
8723                 Thus clients still need to connect as a valid user and supply a
8724                 valid password. Once connected, all file operations will be performed
8725                 as the "forced user", no matter what username the client connected
8726                 as.  This can be very useful.</P
8727 ><P
8728 >In Samba 2.0.5 and above this parameter also causes the
8729                 primary group of the forced user to be used as the primary group
8730                 for all file activity. Prior to 2.0.5 the primary group was left
8731                 as the primary group of the connecting user (this was a bug).</P
8732 ><P
8733 >See also <A
8734 HREF="#FORCEGROUP"
8735 ><TT
8736 CLASS="PARAMETER"
8737 ><I
8738 >force group
8739                 </I
8740 ></TT
8741 ></A
8742 ></P
8743 ><P
8744 >Default: <EM
8745 >no forced user</EM
8746 ></P
8747 ><P
8748 >Example: <B
8749 CLASS="COMMAND"
8750 >force user = auser</B
8751 ></P
8752 ></DD
8753 ><DT
8754 ><A
8755 NAME="FSTYPE"
8756 ></A
8757 >fstype (S)</DT
8758 ><DD
8759 ><P
8760 >This parameter allows the administrator to
8761                 configure the string that specifies the type of filesystem a share
8762                 is using that is reported by <A
8763 HREF="smbd.8.html"
8764 TARGET="_top"
8765 ><B
8766 CLASS="COMMAND"
8767 >smbd(8)
8768                 </B
8769 ></A
8770 > when a client queries the filesystem type
8771                 for a share. The default type is <TT
8772 CLASS="CONSTANT"
8773 >NTFS</TT
8774 > for
8775                 compatibility with Windows NT but this can be changed to other
8776                 strings such as <TT
8777 CLASS="CONSTANT"
8778 >Samba</TT
8779 > or <TT
8780 CLASS="CONSTANT"
8781 >FAT
8782                 </TT
8783 > if required.</P
8784 ><P
8785 >Default: <B
8786 CLASS="COMMAND"
8787 >fstype = NTFS</B
8788 ></P
8789 ><P
8790 >Example: <B
8791 CLASS="COMMAND"
8792 >fstype = Samba</B
8793 ></P
8794 ></DD
8795 ><DT
8796 ><A
8797 NAME="GETWDCACHE"
8798 ></A
8799 >getwd cache (G)</DT
8800 ><DD
8801 ><P
8802 >This is a tuning option. When this is enabled a
8803                 caching algorithm will be used to reduce the time taken for getwd()
8804                 calls. This can have a significant impact on performance, especially
8805                 when the <A
8806 HREF="#WIDELINKS"
8807 ><TT
8808 CLASS="PARAMETER"
8809 ><I
8810 >wide links</I
8811 ></TT
8812 >
8813                 </A
8814 >parameter is set to <TT
8815 CLASS="CONSTANT"
8816 >no</TT
8817 >.</P
8818 ><P
8819 >Default: <B
8820 CLASS="COMMAND"
8821 >getwd cache = yes</B
8822 ></P
8823 ></DD
8824 ><DT
8825 ><A
8826 NAME="GROUP"
8827 ></A
8828 >group (S)</DT
8829 ><DD
8830 ><P
8831 >Synonym for <A
8832 HREF="#FORCEGROUP"
8833 ><TT
8834 CLASS="PARAMETER"
8835 ><I
8836 >force
8837                 group</I
8838 ></TT
8839 ></A
8840 >.</P
8841 ></DD
8842 ><DT
8843 ><A
8844 NAME="GUESTACCOUNT"
8845 ></A
8846 >guest account (S)</DT
8847 ><DD
8848 ><P
8849 >This is a username which will be used for access
8850                 to services which are specified as <A
8851 HREF="#GUESTOK"
8852 ><TT
8853 CLASS="PARAMETER"
8854 ><I
8855 >               guest ok</I
8856 ></TT
8857 ></A
8858 > (see below). Whatever privileges this
8859                 user has will be available to any client connecting to the guest service.
8860                 Typically this user will exist in the password file, but will not
8861                 have a valid login. The user account "ftp" is often a good choice
8862                 for this parameter. If a username is specified in a given service,
8863                 the specified username overrides this one.</P
8864 ><P
8865 >One some systems the default guest account "nobody" may not
8866                 be able to print. Use another account in this case. You should test
8867                 this by trying to log in as your guest user (perhaps by using the
8868                 <B
8869 CLASS="COMMAND"
8870 >su -</B
8871 > command) and trying to print using the
8872                 system print command such as <B
8873 CLASS="COMMAND"
8874 >lpr(1)</B
8875 > or <B
8876 CLASS="COMMAND"
8877 >               lp(1)</B
8878 >.</P
8879 ><P
8880 >Default: <EM
8881 >specified at compile time, usually
8882                 "nobody"</EM
8883 ></P
8884 ><P
8885 >Example: <B
8886 CLASS="COMMAND"
8887 >guest account = ftp</B
8888 ></P
8889 ></DD
8890 ><DT
8891 ><A
8892 NAME="GUESTOK"
8893 ></A
8894 >guest ok (S)</DT
8895 ><DD
8896 ><P
8897 >If this parameter is <TT
8898 CLASS="CONSTANT"
8899 >yes</TT
8900 > for
8901                 a service, then no password is required to connect to the service.
8902                 Privileges will be those of the <A
8903 HREF="#GUESTACCOUNT"
8904 ><TT
8905 CLASS="PARAMETER"
8906 ><I
8907 >               guest account</I
8908 ></TT
8909 ></A
8910 >.</P
8911 ><P
8912 >See the section below on <A
8913 HREF="#SECURITY"
8914 ><TT
8915 CLASS="PARAMETER"
8916 ><I
8917 >               security</I
8918 ></TT
8919 ></A
8920 > for more information about this option.
8921                 </P
8922 ><P
8923 >Default: <B
8924 CLASS="COMMAND"
8925 >guest ok = no</B
8926 ></P
8927 ></DD
8928 ><DT
8929 ><A
8930 NAME="GUESTONLY"
8931 ></A
8932 >guest only (S)</DT
8933 ><DD
8934 ><P
8935 >If this parameter is <TT
8936 CLASS="CONSTANT"
8937 >yes</TT
8938 > for
8939                 a service, then only guest connections to the service are permitted.
8940                 This parameter will have no effect if <A
8941 HREF="#GUESTOK"
8942 >               <TT
8943 CLASS="PARAMETER"
8944 ><I
8945 >guest ok</I
8946 ></TT
8947 ></A
8948 > is not set for the service.</P
8949 ><P
8950 >See the section below on <A
8951 HREF="#SECURITY"
8952 ><TT
8953 CLASS="PARAMETER"
8954 ><I
8955 >               security</I
8956 ></TT
8957 ></A
8958 > for more information about this option.
8959                 </P
8960 ><P
8961 >Default: <B
8962 CLASS="COMMAND"
8963 >guest only = no</B
8964 ></P
8965 ></DD
8966 ><DT
8967 ><A
8968 NAME="HIDEDOTFILES"
8969 ></A
8970 >hide dot files (S)</DT
8971 ><DD
8972 ><P
8973 >This is a boolean parameter that controls whether
8974                 files starting with a dot appear as hidden files.</P
8975 ><P
8976 >Default: <B
8977 CLASS="COMMAND"
8978 >hide dot files = yes</B
8979 ></P
8980 ></DD
8981 ><DT
8982 ><A
8983 NAME="HIDEFILES"
8984 ></A
8985 >hide files(S)</DT
8986 ><DD
8987 ><P
8988 >This is a list of files or directories that are not
8989                 visible but are accessible.  The DOS 'hidden' attribute is applied
8990                 to any files or directories that match.</P
8991 ><P
8992 >Each entry in the list must be separated by a '/',
8993                 which allows spaces to be included in the entry.  '*'
8994                 and '?' can be used to specify multiple files or directories
8995                 as in DOS wildcards.</P
8996 ><P
8997 >Each entry must be a Unix path, not a DOS path and must
8998                 not include the Unix directory separator '/'.</P
8999 ><P
9000 >Note that the case sensitivity option is applicable
9001                 in hiding files.</P
9002 ><P
9003 >Setting this parameter will affect the performance of Samba,
9004                 as it will be forced to check all files and directories for a match
9005                 as they are scanned.</P
9006 ><P
9007 >See also <A
9008 HREF="#HIDEDOTFILES"
9009 ><TT
9010 CLASS="PARAMETER"
9011 ><I
9012 >hide
9013                 dot files</I
9014 ></TT
9015 ></A
9016 >, <A
9017 HREF="#VETOFILES"
9018 ><TT
9019 CLASS="PARAMETER"
9020 ><I
9021 >               veto files</I
9022 ></TT
9023 ></A
9024 > and <A
9025 HREF="#CASESENSITIVE"
9026 >               <TT
9027 CLASS="PARAMETER"
9028 ><I
9029 >case sensitive</I
9030 ></TT
9031 ></A
9032 >.</P
9033 ><P
9034 >Default: <EM
9035 >no file are hidden</EM
9036 ></P
9037 ><P
9038 >Example: <B
9039 CLASS="COMMAND"
9040 >hide files =
9041                 /.*/DesktopFolderDB/TrashFor%m/resource.frk/</B
9042 ></P
9043 ><P
9044 >The above example is based on files that the Macintosh
9045                 SMB client (DAVE) available from <A
9046 HREF="http://www.thursby.com"
9047 TARGET="_top"
9048 >
9049                 Thursby</A
9050 > creates for internal use, and also still hides
9051                 all files beginning with a dot.</P
9052 ></DD
9053 ><DT
9054 ><A
9055 NAME="HIDELOCALUSERS"
9056 ></A
9057 >hide local users(G)</DT
9058 ><DD
9059 ><P
9060 >This parameter toggles the hiding of local UNIX
9061                 users (root, wheel, floppy, etc) from remote clients.</P
9062 ><P
9063 >Default: <B
9064 CLASS="COMMAND"
9065 >hide local users = no</B
9066 ></P
9067 ></DD
9068 ><DT
9069 ><A
9070 NAME="HIDEUNREADABLE"
9071 ></A
9072 >hide unreadable (S)</DT
9073 ><DD
9074 ><P
9075 >This parameter prevents clients from seeing the
9076                 existance of files that cannot be read. Defaults to off.</P
9077 ><P
9078 >Default: <B
9079 CLASS="COMMAND"
9080 >hide unreadable = no</B
9081 ></P
9082 ></DD
9083 ><DT
9084 ><A
9085 NAME="HOMEDIRMAP"
9086 ></A
9087 >homedir map (G)</DT
9088 ><DD
9089 ><P
9090 >If<A
9091 HREF="#NISHOMEDIR"
9092 ><TT
9093 CLASS="PARAMETER"
9094 ><I
9095 >nis homedir
9096                 </I
9097 ></TT
9098 ></A
9099 > is <TT
9100 CLASS="CONSTANT"
9101 >yes</TT
9102 >, and <A
9103 HREF="smbd.8.html"
9104 TARGET="_top"
9105 ><B
9106 CLASS="COMMAND"
9107 >smbd(8)</B
9108 ></A
9109 > is also acting
9110                 as a Win95/98 <TT
9111 CLASS="PARAMETER"
9112 ><I
9113 >logon server</I
9114 ></TT
9115 > then this parameter
9116                 specifies the NIS (or YP) map from which the server for the user's
9117                 home directory should be extracted.  At present, only the Sun
9118                 auto.home map format is understood. The form of the map is:</P
9119 ><P
9120 ><B
9121 CLASS="COMMAND"
9122 >username       server:/some/file/system</B
9123 ></P
9124 ><P
9125 >and the program will extract the servername from before
9126                 the first ':'.  There should probably be a better parsing system
9127                 that copes with different map formats and also Amd (another
9128                 automounter) maps.</P
9129 ><P
9130 ><EM
9131 >NOTE :</EM
9132 >A working NIS client is required on
9133                 the system for this option to work.</P
9134 ><P
9135 >See also <A
9136 HREF="#NISHOMEDIR"
9137 ><TT
9138 CLASS="PARAMETER"
9139 ><I
9140 >nis homedir</I
9141 ></TT
9142 >
9143                 </A
9144 >, <A
9145 HREF="#DOMAINLOGONS"
9146 ><TT
9147 CLASS="PARAMETER"
9148 ><I
9149 >domain logons</I
9150 ></TT
9151 >
9152                 </A
9153 >.</P
9154 ><P
9155 >Default: <B
9156 CLASS="COMMAND"
9157 >homedir map = &#60;empty string&#62;</B
9158 ></P
9159 ><P
9160 >Example: <B
9161 CLASS="COMMAND"
9162 >homedir map = amd.homedir</B
9163 ></P
9164 ></DD
9165 ><DT
9166 ><A
9167 NAME="HOSTMSDFS"
9168 ></A
9169 >host msdfs (G)</DT
9170 ><DD
9171 ><P
9172 >This boolean parameter is only available
9173                 if Samba has been configured and compiled with the <B
9174 CLASS="COMMAND"
9175 >               --with-msdfs</B
9176 > option. If set to <TT
9177 CLASS="CONSTANT"
9178 >yes</TT
9179 >,
9180                 Samba will act as a Dfs server, and  allow Dfs-aware clients
9181                 to browse Dfs trees hosted on the server.</P
9182 ><P
9183 >See also the <A
9184 HREF="#MSDFSROOT"
9185 ><TT
9186 CLASS="PARAMETER"
9187 ><I
9188 >               msdfs root</I
9189 ></TT
9190 ></A
9191 > share  level  parameter.  For
9192                 more  information  on  setting  up a Dfs tree on Samba,
9193                 refer to <A
9194 HREF="msdfs_setup.html"
9195 TARGET="_top"
9196 >msdfs_setup.html</A
9197 >.
9198                 </P
9199 ><P
9200 >Default: <B
9201 CLASS="COMMAND"
9202 >host msdfs = no</B
9203 ></P
9204 ></DD
9205 ><DT
9206 ><A
9207 NAME="HOSTSALLOW"
9208 ></A
9209 >hosts allow (S)</DT
9210 ><DD
9211 ><P
9212 >A synonym for this parameter is <TT
9213 CLASS="PARAMETER"
9214 ><I
9215 >allow
9216                 hosts</I
9217 ></TT
9218 >.</P
9219 ><P
9220 >This parameter is a comma, space, or tab delimited
9221                 set of hosts which are permitted to access a service.</P
9222 ><P
9223 >If specified in the [global] section then it will
9224                 apply to all services, regardless of whether the individual
9225                 service has a different setting.</P
9226 ><P
9227 >You can specify the hosts by name or IP number. For
9228                 example, you could restrict access to only the hosts on a
9229                 Class C subnet with something like <B
9230 CLASS="COMMAND"
9231 >allow hosts = 150.203.5.
9232                 </B
9233 >. The full syntax of the list is described in the man
9234                 page <TT
9235 CLASS="FILENAME"
9236 >hosts_access(5)</TT
9237 >. Note that this man
9238                 page may not be present on your system, so a brief description will
9239                 be given here also.</P
9240 ><P
9241 >Note that the localhost address 127.0.0.1 will always
9242                 be allowed access unless specifically denied by a <A
9243 HREF="#HOSTSDENY"
9244 ><TT
9245 CLASS="PARAMETER"
9246 ><I
9247 >hosts deny</I
9248 ></TT
9249 ></A
9250 > option.</P
9251 ><P
9252 >You can also specify hosts by network/netmask pairs and
9253                 by netgroup names if your system supports netgroups. The
9254                 <EM
9255 >EXCEPT</EM
9256 > keyword can also be used to limit a
9257                 wildcard list. The following examples may provide some help:</P
9258 ><P
9259 >Example 1: allow all IPs in 150.203.*.*; except one</P
9260 ><P
9261 ><B
9262 CLASS="COMMAND"
9263 >hosts allow = 150.203. EXCEPT 150.203.6.66</B
9264 ></P
9265 ><P
9266 >Example 2: allow hosts that match the given network/netmask</P
9267 ><P
9268 ><B
9269 CLASS="COMMAND"
9270 >hosts allow = 150.203.15.0/255.255.255.0</B
9271 ></P
9272 ><P
9273 >Example 3: allow a couple of hosts</P
9274 ><P
9275 ><B
9276 CLASS="COMMAND"
9277 >hosts allow = lapland, arvidsjaur</B
9278 ></P
9279 ><P
9280 >Example 4: allow only hosts in NIS netgroup "foonet", but
9281                 deny access from one particular host</P
9282 ><P
9283 ><B
9284 CLASS="COMMAND"
9285 >hosts allow = @foonet</B
9286 ></P
9287 ><P
9288 ><B
9289 CLASS="COMMAND"
9290 >hosts deny = pirate</B
9291 ></P
9292 ><P
9293 >Note that access still requires suitable user-level passwords.</P
9294 ><P
9295 >See <A
9296 HREF="testparm.1.html"
9297 TARGET="_top"
9298 ><B
9299 CLASS="COMMAND"
9300 >testparm(1)</B
9301 >
9302                 </A
9303 > for a way of testing your host access to see if it does
9304                 what you expect.</P
9305 ><P
9306 >Default: <EM
9307 >none (i.e., all hosts permitted access)
9308                 </EM
9309 ></P
9310 ><P
9311 >Example: <B
9312 CLASS="COMMAND"
9313 >allow hosts = 150.203.5. myhost.mynet.edu.au
9314                 </B
9315 ></P
9316 ></DD
9317 ><DT
9318 ><A
9319 NAME="HOSTSDENY"
9320 ></A
9321 >hosts deny (S)</DT
9322 ><DD
9323 ><P
9324 >The opposite of <TT
9325 CLASS="PARAMETER"
9326 ><I
9327 >hosts allow</I
9328 ></TT
9329 >
9330                 - hosts listed here are <EM
9331 >NOT</EM
9332 > permitted access to
9333                 services unless the specific services have their own lists to override
9334                 this one. Where the lists conflict, the <TT
9335 CLASS="PARAMETER"
9336 ><I
9337 >allow</I
9338 ></TT
9339 >
9340                 list takes precedence.</P
9341 ><P
9342 >Default: <EM
9343 >none (i.e., no hosts specifically excluded)
9344                 </EM
9345 ></P
9346 ><P
9347 >Example: <B
9348 CLASS="COMMAND"
9349 >hosts deny = 150.203.4. badhost.mynet.edu.au
9350                 </B
9351 ></P
9352 ></DD
9353 ><DT
9354 ><A
9355 NAME="HOSTSEQUIV"
9356 ></A
9357 >hosts equiv (G)</DT
9358 ><DD
9359 ><P
9360 >If this global parameter is a non-null string,
9361                 it specifies the name of a file to read for the names of hosts
9362                 and users who will be allowed access without specifying a password.
9363                 </P
9364 ><P
9365 >This is not be confused with <A
9366 HREF="#HOSTSALLOW"
9367 >               <TT
9368 CLASS="PARAMETER"
9369 ><I
9370 >hosts allow</I
9371 ></TT
9372 ></A
9373 > which is about hosts
9374                 access to services and is more useful for guest services. <TT
9375 CLASS="PARAMETER"
9376 ><I
9377 >               hosts equiv</I
9378 ></TT
9379 > may be useful for NT clients which will
9380                 not supply passwords to Samba.</P
9381 ><P
9382 ><EM
9383 >NOTE :</EM
9384 > The use of <TT
9385 CLASS="PARAMETER"
9386 ><I
9387 >hosts equiv
9388                 </I
9389 ></TT
9390 > can be a major security hole. This is because you are
9391                 trusting the PC to supply the correct username. It is very easy to
9392                 get a PC to supply a false username. I recommend that the
9393                 <TT
9394 CLASS="PARAMETER"
9395 ><I
9396 >hosts equiv</I
9397 ></TT
9398 > option be only used if you really
9399                 know what you are doing, or perhaps on a home network where you trust
9400                 your spouse and kids. And only if you <EM
9401 >really</EM
9402 > trust
9403                 them :-).</P
9404 ><P
9405 >Default: <EM
9406 >no host equivalences</EM
9407 ></P
9408 ><P
9409 >Example: <B
9410 CLASS="COMMAND"
9411 >hosts equiv = /etc/hosts.equiv</B
9412 ></P
9413 ></DD
9414 ><DT
9415 ><A
9416 NAME="INCLUDE"
9417 ></A
9418 >include (G)</DT
9419 ><DD
9420 ><P
9421 >This allows you to include one config file
9422                 inside another.  The file is included literally, as though typed
9423                 in place.</P
9424 ><P
9425 >It takes the standard substitutions, except <TT
9426 CLASS="PARAMETER"
9427 ><I
9428 >%u
9429                 </I
9430 ></TT
9431 >, <TT
9432 CLASS="PARAMETER"
9433 ><I
9434 >%P</I
9435 ></TT
9436 > and <TT
9437 CLASS="PARAMETER"
9438 ><I
9439 >%S</I
9440 ></TT
9441 >.
9442                 </P
9443 ><P
9444 >Default: <EM
9445 >no file included</EM
9446 ></P
9447 ><P
9448 >Example: <B
9449 CLASS="COMMAND"
9450 >include = /usr/local/samba/lib/admin_smb.conf
9451                 </B
9452 ></P
9453 ></DD
9454 ><DT
9455 ><A
9456 NAME="INHERITACLS"
9457 ></A
9458 >inherit acls (S)</DT
9459 ><DD
9460 ><P
9461 >This parameter can be used to ensure
9462                 that if default acls exist on parent directories,
9463                 they are always honored when creating a subdirectory.
9464                 The default behavior is to use the mode specified
9465                 when creating the directory.  Enabling this option
9466                 sets the mode to 0777, thus guaranteeing that
9467                 default directory acls are propagated.
9468                 </P
9469 ><P
9470 >Default: <B
9471 CLASS="COMMAND"
9472 >inherit acls = no</B
9473 >
9474                 </P
9475 ></DD
9476 ><DT
9477 ><A
9478 NAME="INHERITPERMISSIONS"
9479 ></A
9480 >inherit permissions (S)</DT
9481 ><DD
9482 ><P
9483 >The permissions on new files and directories
9484                 are normally governed by <A
9485 HREF="#CREATEMASK"
9486 ><TT
9487 CLASS="PARAMETER"
9488 ><I
9489 >               create mask</I
9490 ></TT
9491 ></A
9492 >, <A
9493 HREF="#DIRECTORYMASK"
9494 >               <TT
9495 CLASS="PARAMETER"
9496 ><I
9497 >directory mask</I
9498 ></TT
9499 ></A
9500 >, <A
9501 HREF="#FORCECREATEMODE"
9502 ><TT
9503 CLASS="PARAMETER"
9504 ><I
9505 >force create mode</I
9506 ></TT
9507 >
9508                 </A
9509 > and <A
9510 HREF="#FORCEDIRECTORYMODE"
9511 ><TT
9512 CLASS="PARAMETER"
9513 ><I
9514 >force
9515                 directory mode</I
9516 ></TT
9517 ></A
9518 > but the boolean inherit
9519                 permissions parameter overrides this.</P
9520 ><P
9521 >New directories inherit the mode of the parent directory,
9522                 including bits such as setgid.</P
9523 ><P
9524 >New files inherit their read/write bits from the parent
9525                 directory.  Their execute bits continue to be determined by
9526                 <A
9527 HREF="#MAPARCHIVE"
9528 ><TT
9529 CLASS="PARAMETER"
9530 ><I
9531 >map archive</I
9532 ></TT
9533 >
9534                 </A
9535 >, <A
9536 HREF="#MAPHIDDEN"
9537 ><TT
9538 CLASS="PARAMETER"
9539 ><I
9540 >map hidden</I
9541 ></TT
9542 >
9543                 </A
9544 > and <A
9545 HREF="#MAPSYSTEM"
9546 ><TT
9547 CLASS="PARAMETER"
9548 ><I
9549 >map system</I
9550 ></TT
9551 >
9552                 </A
9553 > as usual.</P
9554 ><P
9555 >Note that the setuid bit is <EM
9556 >never</EM
9557 > set via
9558                 inheritance (the code explicitly prohibits this).</P
9559 ><P
9560 >This can be particularly useful on large systems with
9561                 many users, perhaps several thousand, to allow a single [homes]
9562                 share to be used flexibly by each user.</P
9563 ><P
9564 >See also <A
9565 HREF="#CREATEMASK"
9566 ><TT
9567 CLASS="PARAMETER"
9568 ><I
9569 >create mask
9570                 </I
9571 ></TT
9572 ></A
9573 >, <A
9574 HREF="#DIRECTORYMASK"
9575 ><TT
9576 CLASS="PARAMETER"
9577 ><I
9578 >               directory mask</I
9579 ></TT
9580 ></A
9581 >, <A
9582 HREF="#FORCECREATEMODE"
9583 >               <TT
9584 CLASS="PARAMETER"
9585 ><I
9586 >force create mode</I
9587 ></TT
9588 ></A
9589 > and <A
9590 HREF="#FORCEDIRECTORYMODE"
9591 ><TT
9592 CLASS="PARAMETER"
9593 ><I
9594 >force directory mode</I
9595 ></TT
9596 >
9597                 </A
9598 >.</P
9599 ><P
9600 >Default: <B
9601 CLASS="COMMAND"
9602 >inherit permissions = no</B
9603 ></P
9604 ></DD
9605 ><DT
9606 ><A
9607 NAME="INTERFACES"
9608 ></A
9609 >interfaces (G)</DT
9610 ><DD
9611 ><P
9612 >This option allows you to override the default
9613                 network interfaces list that Samba will use for browsing, name
9614                 registration and other NBT traffic. By default Samba will query
9615                 the kernel for the list of all active interfaces and use any
9616                 interfaces except 127.0.0.1 that are broadcast capable.</P
9617 ><P
9618 >The option takes a list of interface strings. Each string
9619                 can be in any of the following forms:</P
9620 ><P
9621 ></P
9622 ><UL
9623 ><LI
9624 ><P
9625 >a network interface name (such as eth0).
9626                         This may include shell-like wildcards so eth* will match
9627                         any interface starting with the substring "eth"</P
9628 ></LI
9629 ><LI
9630 ><P
9631 >an IP address. In this case the netmask is
9632                         determined from the list of interfaces obtained from the
9633                         kernel</P
9634 ></LI
9635 ><LI
9636 ><P
9637 >an IP/mask pair. </P
9638 ></LI
9639 ><LI
9640 ><P
9641 >a broadcast/mask pair.</P
9642 ></LI
9643 ></UL
9644 ><P
9645 >The "mask" parameters can either be a bit length (such
9646                 as 24 for a C class network) or a full netmask in dotted
9647                 decimal form.</P
9648 ><P
9649 >The "IP" parameters above can either be a full dotted
9650                 decimal IP address or a hostname which will be looked up via
9651                 the OS's normal hostname resolution mechanisms.</P
9652 ><P
9653 >For example, the following line:</P
9654 ><P
9655 ><B
9656 CLASS="COMMAND"
9657 >interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
9658                 </B
9659 ></P
9660 ><P
9661 >would configure three network interfaces corresponding
9662                 to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10.
9663                 The netmasks of the latter two interfaces would be set to 255.255.255.0.</P
9664 ><P
9665 >See also <A
9666 HREF="#BINDINTERFACESONLY"
9667 ><TT
9668 CLASS="PARAMETER"
9669 ><I
9670 >bind
9671                 interfaces only</I
9672 ></TT
9673 ></A
9674 >.</P
9675 ><P
9676 >Default: <EM
9677 >all active interfaces except 127.0.0.1
9678                 that are broadcast capable</EM
9679 ></P
9680 ></DD
9681 ><DT
9682 ><A
9683 NAME="INVALIDUSERS"
9684 ></A
9685 >invalid users (S)</DT
9686 ><DD
9687 ><P
9688 >This is a list of users that should not be allowed
9689                 to login to this service. This is really a <EM
9690 >paranoid</EM
9691 >
9692                 check to absolutely ensure an improper setting does not breach
9693                 your security.</P
9694 ><P
9695 >A name starting with a '@' is interpreted as an NIS
9696                 netgroup first (if your system supports NIS), and then as a UNIX
9697                 group if the name was not found in the NIS netgroup database.</P
9698 ><P
9699 >A name starting with '+' is interpreted only
9700                 by looking in the UNIX group database. A name starting with
9701                 '&#38;' is interpreted only by looking in the NIS netgroup database
9702                 (this requires NIS to be working on your system). The characters
9703                 '+' and '&#38;' may be used at the start of the name in either order
9704                 so the value <TT
9705 CLASS="PARAMETER"
9706 ><I
9707 >+&#38;group</I
9708 ></TT
9709 > means check the
9710                 UNIX group database, followed by the NIS netgroup database, and
9711                 the value <TT
9712 CLASS="PARAMETER"
9713 ><I
9714 >&#38;+group</I
9715 ></TT
9716 > means check the NIS
9717                 netgroup database, followed by the UNIX group database (the
9718                 same as the '@' prefix).</P
9719 ><P
9720 >The current servicename is substituted for <TT
9721 CLASS="PARAMETER"
9722 ><I
9723 >%S</I
9724 ></TT
9725 >.
9726                 This is useful in the [homes] section.</P
9727 ><P
9728 >See also <A
9729 HREF="#VALIDUSERS"
9730 ><TT
9731 CLASS="PARAMETER"
9732 ><I
9733 >valid users
9734                 </I
9735 ></TT
9736 ></A
9737 >.</P
9738 ><P
9739 >Default: <EM
9740 >no invalid users</EM
9741 ></P
9742 ><P
9743 >Example: <B
9744 CLASS="COMMAND"
9745 >invalid users = root fred admin @wheel
9746                 </B
9747 ></P
9748 ></DD
9749 ><DT
9750 ><A
9751 NAME="KEEPALIVE"
9752 ></A
9753 >keepalive (G)</DT
9754 ><DD
9755 ><P
9756 >The value of the parameter (an integer) represents
9757                 the number of seconds between <TT
9758 CLASS="PARAMETER"
9759 ><I
9760 >keepalive</I
9761 ></TT
9762 >
9763                 packets. If this parameter is zero, no keepalive packets will be
9764                 sent. Keepalive packets, if sent, allow the server to tell whether
9765                 a client is still present and responding.</P
9766 ><P
9767 >Keepalives should, in general, not be needed if the socket
9768                 being used has the SO_KEEPALIVE attribute set on it (see <A
9769 HREF="#SOCKETOPTIONS"
9770 ><TT
9771 CLASS="PARAMETER"
9772 ><I
9773 >socket options</I
9774 ></TT
9775 ></A
9776 >).
9777                 Basically you should only use this option if you strike difficulties.</P
9778 ><P
9779 >Default: <B
9780 CLASS="COMMAND"
9781 >keepalive = 300</B
9782 ></P
9783 ><P
9784 >Example: <B
9785 CLASS="COMMAND"
9786 >keepalive = 600</B
9787 ></P
9788 ></DD
9789 ><DT
9790 ><A
9791 NAME="KERNELOPLOCKS"
9792 ></A
9793 >kernel oplocks (G)</DT
9794 ><DD
9795 ><P
9796 >For UNIXes that support kernel based <A
9797 HREF="#OPLOCKS"
9798 ><TT
9799 CLASS="PARAMETER"
9800 ><I
9801 >oplocks</I
9802 ></TT
9803 ></A
9804 >
9805                 (currently only IRIX and the Linux 2.4 kernel), this parameter
9806                 allows the use of them to be turned on or off.</P
9807 ><P
9808 >Kernel oplocks support allows Samba <TT
9809 CLASS="PARAMETER"
9810 ><I
9811 >oplocks
9812                 </I
9813 ></TT
9814 > to be broken whenever a local UNIX process or NFS operation
9815                 accesses a file that <A
9816 HREF="smbd.8.html"
9817 TARGET="_top"
9818 ><B
9819 CLASS="COMMAND"
9820 >smbd(8)</B
9821 >
9822                 </A
9823 > has oplocked. This allows complete data consistency between
9824                 SMB/CIFS, NFS and local file access (and is a <EM
9825 >very</EM
9826 >
9827                 cool feature :-).</P
9828 ><P
9829 >This parameter defaults to <TT
9830 CLASS="CONSTANT"
9831 >on</TT
9832 >, but is translated
9833                 to a no-op on systems that no not have the necessary kernel support.
9834                 You should never need to touch this parameter.</P
9835 ><P
9836 >See also the <A
9837 HREF="#OPLOCKS"
9838 ><TT
9839 CLASS="PARAMETER"
9840 ><I
9841 >oplocks</I
9842 ></TT
9843 >
9844                 </A
9845 > and <A
9846 HREF="#LEVEL2OPLOCKS"
9847 ><TT
9848 CLASS="PARAMETER"
9849 ><I
9850 >level2 oplocks
9851                 </I
9852 ></TT
9853 ></A
9854 > parameters.</P
9855 ><P
9856 >Default: <B
9857 CLASS="COMMAND"
9858 >kernel oplocks = yes</B
9859 ></P
9860 ></DD
9861 ><DT
9862 ><A
9863 NAME="LANMANAUTH"
9864 ></A
9865 >lanman auth (G)</DT
9866 ><DD
9867 ><P
9868 >This parameter determines whether or not <A
9869 HREF="smbd.8.html"
9870 TARGET="_top"
9871 >smbd</A
9872 > will
9873                 attempt to authenticate users using the LANMAN password hash.
9874                 If disabled, only clients which support NT password hashes (e.g. Windows
9875                 NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS
9876                 network client) will be able to connect to the Samba host.</P
9877 ><P
9878 >Default : <B
9879 CLASS="COMMAND"
9880 >lanman auth = yes</B
9881 ></P
9882 ></DD
9883 ><DT
9884 ><A
9885 NAME="LARGEREADWRITE"
9886 ></A
9887 >large readwrite (G)</DT
9888 ><DD
9889 ><P
9890 >This parameter determines whether or not <A
9891 HREF="smbd.8.html"
9892 TARGET="_top"
9893 >smbd</A
9894 >
9895                 supports the new 64k streaming read and write varient SMB requests introduced
9896                 with Windows 2000. Note that due to Windows 2000 client redirector bugs
9897                 this requires Samba to be running on a 64-bit capable operating system such
9898                 as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with
9899                 Windows 2000 clients. Defaults to off. Not as tested as some other Samba
9900                 code paths.
9901                 </P
9902 ><P
9903 >Default : <B
9904 CLASS="COMMAND"
9905 >large readwrite = no</B
9906 ></P
9907 ></DD
9908 ><DT
9909 ><A
9910 NAME="LDAPADMINDN"
9911 ></A
9912 >ldap admin dn (G)</DT
9913 ><DD
9914 ><P
9915 >This parameter is only available if Samba has been
9916                 configure to include the <B
9917 CLASS="COMMAND"
9918 >--with-ldapsam</B
9919 > option
9920                 at compile time. This option should be considered experimental and
9921                 under active development.
9922                 </P
9923 ><P
9924 >               The <TT
9925 CLASS="PARAMETER"
9926 ><I
9927 >ldap admin dn</I
9928 ></TT
9929 > defines the Distinguished
9930                 Name (DN) name used by Samba to contact the <A
9931 HREF="#LDAPSERVER"
9932 >ldap
9933                 server</A
9934 > when retreiving user account information. The <TT
9935 CLASS="PARAMETER"
9936 ><I
9937 >ldap
9938                 admin dn</I
9939 ></TT
9940 > is used in conjunction with the admin dn password
9941                 stored in the <TT
9942 CLASS="FILENAME"
9943 >private/secrets.tdb</TT
9944 > file.  See the
9945                 <A
9946 HREF="smbpasswd.8.html"
9947 TARGET="_top"
9948 ><B
9949 CLASS="COMMAND"
9950 >smbpasswd(8)</B
9951 ></A
9952 > man
9953                 page for more information on how to accmplish this.
9954                 </P
9955 ><P
9956 >Default : <EM
9957 >none</EM
9958 ></P
9959 ></DD
9960 ><DT
9961 ><A
9962 NAME="LDAPFILTER"
9963 ></A
9964 >ldap filter (G)</DT
9965 ><DD
9966 ><P
9967 >This parameter is only available if Samba has been
9968                 configure to include the <B
9969 CLASS="COMMAND"
9970 >--with-ldapsam</B
9971 > option
9972                 at compile time. This option should be considered experimental and
9973                 under active development.
9974                 </P
9975 ><P
9976 >               This parameter specifies the RFC 2254 compliant LDAP search filter.
9977                 The default is to match the login name with the <TT
9978 CLASS="CONSTANT"
9979 >uid</TT
9980 >
9981                 attribute for all entries matching the <TT
9982 CLASS="CONSTANT"
9983 >sambaAccount</TT
9984 >
9985                 objectclass.  Note that this filter should only return one entry.
9986                 </P
9987 ><P
9988 >Default : <B
9989 CLASS="COMMAND"
9990 >ldap filter = (&#38;(uid=%u)(objectclass=sambaAccount))</B
9991 ></P
9992 ></DD
9993 ><DT
9994 ><A
9995 NAME="LDAPPORT"
9996 ></A
9997 >ldap port (G)</DT
9998 ><DD
9999 ><P
10000 >This parameter is only available if Samba has been
10001                 configure to include the <B
10002 CLASS="COMMAND"
10003 >--with-ldapsam</B
10004 > option
10005                 at compile time. This option should be considered experimental and
10006                 under active development.
10007                 </P
10008 ><P
10009 >               This option is used to control the tcp port number used to contact
10010                 the <A
10011 HREF="#LDAPSERVER"
10012 ><TT
10013 CLASS="PARAMETER"
10014 ><I
10015 >ldap server</I
10016 ></TT
10017 ></A
10018 >.
10019                 The default is to use the stand LDAPS port 636.
10020                 </P
10021 ><P
10022 >See Also: <A
10023 HREF="#LDAPSSL"
10024 >ldap ssl</A
10025 >
10026                 </P
10027 ><P
10028 >Default : <B
10029 CLASS="COMMAND"
10030 >ldap port = 636 ; if ldap ssl = on</B
10031 ></P
10032 ><P
10033 >Default : <B
10034 CLASS="COMMAND"
10035 >ldap port = 389 ; if ldap ssl = off</B
10036 ></P
10037 ></DD
10038 ><DT
10039 ><A
10040 NAME="LDAPSERVER"
10041 ></A
10042 >ldap server (G)</DT
10043 ><DD
10044 ><P
10045 >This parameter is only available if Samba has been
10046                 configure to include the <B
10047 CLASS="COMMAND"
10048 >--with-ldapsam</B
10049 > option
10050                 at compile time. This option should be considered experimental and
10051                 under active development.
10052                 </P
10053 ><P
10054 >               This parameter should contains the FQDN of the ldap directory
10055                 server which should be queried to locate user account information.
10056                 </P
10057 ><P
10058 >Default : <B
10059 CLASS="COMMAND"
10060 >ldap server = localhost</B
10061 ></P
10062 ></DD
10063 ><DT
10064 ><A
10065 NAME="LDAPSSL"
10066 ></A
10067 >ldap ssl (G)</DT
10068 ><DD
10069 ><P
10070 >This parameter is only available if Samba has been
10071                 configure to include the <B
10072 CLASS="COMMAND"
10073 >--with-ldapsam</B
10074 > option
10075                 at compile time. This option should be considered experimental and
10076                 under active development.
10077                 </P
10078 ><P
10079 >               This option is used to define whether or not Samba should
10080                 use SSL when connecting to the <A
10081 HREF="#LDAPSERVER"
10082 ><TT
10083 CLASS="PARAMETER"
10084 ><I
10085 >ldap
10086                 server</I
10087 ></TT
10088 ></A
10089 >.  This is <EM
10090 >NOT</EM
10091 > related to
10092                 Samba SSL support which is enabled by specifying the
10093                 <B
10094 CLASS="COMMAND"
10095 >--with-ssl</B
10096 > option to the <TT
10097 CLASS="FILENAME"
10098 >configure</TT
10099 >
10100                 script (see <A
10101 HREF="#SSL"
10102 ><TT
10103 CLASS="PARAMETER"
10104 ><I
10105 >ssl</I
10106 ></TT
10107 ></A
10108 >).
10109                 </P
10110 ><P
10111 >               The <TT
10112 CLASS="PARAMETER"
10113 ><I
10114 >ldap ssl</I
10115 ></TT
10116 > can be set to one of three values:
10117                 (a) <TT
10118 CLASS="CONSTANT"
10119 >on</TT
10120 > - Always use SSL when contacting the
10121                 <TT
10122 CLASS="PARAMETER"
10123 ><I
10124 >ldap   server</I
10125 ></TT
10126 >, (b) <TT
10127 CLASS="CONSTANT"
10128 >off</TT
10129 > -
10130                 Never use SSL when querying the directory, or (c) <TT
10131 CLASS="CONSTANT"
10132 >start_tls</TT
10133 >
10134                 - Use the LDAPv3 StartTLS extended operation
10135                 (RFC2830) for communicating with the directory server.
10136                 </P
10137 ><P
10138 >Default : <B
10139 CLASS="COMMAND"
10140 >ldap ssl = on</B
10141 ></P
10142 ></DD
10143 ><DT
10144 ><A
10145 NAME="LDAPSUFFIX"
10146 ></A
10147 >ldap suffix (G)</DT
10148 ><DD
10149 ><P
10150 >This parameter is only available if Samba has been
10151                 configure to include the <B
10152 CLASS="COMMAND"
10153 >--with-ldapsam</B
10154 > option
10155                 at compile time. This option should be considered experimental and
10156                 under active development.
10157                 </P
10158 ><P
10159 >Default : <EM
10160 >none</EM
10161 ></P
10162 ></DD
10163 ><DT
10164 ><A
10165 NAME="LEVEL2OPLOCKS"
10166 ></A
10167 >level2 oplocks (S)</DT
10168 ><DD
10169 ><P
10170 >This parameter controls whether Samba supports
10171                 level2 (read-only) oplocks on a share.</P
10172 ><P
10173 >Level2, or read-only oplocks allow Windows NT clients
10174                 that have an oplock on a file to downgrade from a read-write oplock
10175                 to a read-only oplock once a second client opens the file (instead
10176                 of releasing all oplocks on a second open, as in traditional,
10177                 exclusive oplocks). This allows all openers of the file that
10178                 support level2 oplocks to cache the file for read-ahead only (ie.
10179                 they may not cache writes or lock requests) and increases performance
10180                 for many accesses of files that are not commonly written (such as
10181                 application .EXE files).</P
10182 ><P
10183 >Once one of the clients which have a read-only oplock
10184                 writes to the file all clients are notified (no reply is needed
10185                 or waited for) and told to break their oplocks to "none" and
10186                 delete any read-ahead caches.</P
10187 ><P
10188 >It is recommended that this parameter be turned on
10189                 to speed access to shared executables.</P
10190 ><P
10191 >For more discussions on level2 oplocks see the CIFS spec.</P
10192 ><P
10193 >Currently, if <A
10194 HREF="#KERNELOPLOCKS"
10195 ><TT
10196 CLASS="PARAMETER"
10197 ><I
10198 >kernel
10199                 oplocks</I
10200 ></TT
10201 ></A
10202 > are supported then level2 oplocks are
10203                 not granted (even if this parameter is set to <TT
10204 CLASS="CONSTANT"
10205 >yes</TT
10206 >).
10207                 Note also, the <A
10208 HREF="#OPLOCKS"
10209 ><TT
10210 CLASS="PARAMETER"
10211 ><I
10212 >oplocks</I
10213 ></TT
10214 >
10215                 </A
10216 > parameter must be set to <TT
10217 CLASS="CONSTANT"
10218 >yes</TT
10219 > on this share in order for
10220                 this parameter to have any effect.</P
10221 ><P
10222 >See also the <A
10223 HREF="#OPLOCKS"
10224 ><TT
10225 CLASS="PARAMETER"
10226 ><I
10227 >oplocks</I
10228 ></TT
10229 >
10230                 </A
10231 > and <A
10232 HREF="#OPLOCKS"
10233 ><TT
10234 CLASS="PARAMETER"
10235 ><I
10236 >kernel oplocks</I
10237 ></TT
10238 >
10239                 </A
10240 > parameters.</P
10241 ><P
10242 >Default: <B
10243 CLASS="COMMAND"
10244 >level2 oplocks = yes</B
10245 ></P
10246 ></DD
10247 ><DT
10248 ><A
10249 NAME="LMANNOUNCE"
10250 ></A
10251 >lm announce (G)</DT
10252 ><DD
10253 ><P
10254 >This parameter determines if <A
10255 HREF="nmbd.8.html"
10256 TARGET="_top"
10257 >               <B
10258 CLASS="COMMAND"
10259 >nmbd(8)</B
10260 ></A
10261 > will produce Lanman announce
10262                 broadcasts that are needed by OS/2 clients in order for them to see
10263                 the Samba server in their browse list. This parameter can have three
10264                 values, <TT
10265 CLASS="CONSTANT"
10266 >yes</TT
10267 >, <TT
10268 CLASS="CONSTANT"
10269 >no</TT
10270 >, or
10271                 <TT
10272 CLASS="CONSTANT"
10273 >auto</TT
10274 >. The default is <TT
10275 CLASS="CONSTANT"
10276 >auto</TT
10277 >.
10278                 If set to <TT
10279 CLASS="CONSTANT"
10280 >no</TT
10281 > Samba will never produce these
10282                 broadcasts. If set to <TT
10283 CLASS="CONSTANT"
10284 >yes</TT
10285 > Samba will produce
10286                 Lanman announce broadcasts at a frequency set by the parameter
10287                 <TT
10288 CLASS="PARAMETER"
10289 ><I
10290 >lm interval</I
10291 ></TT
10292 >. If set to <TT
10293 CLASS="CONSTANT"
10294 >auto</TT
10295 >
10296                 Samba will not send Lanman announce broadcasts by default but will
10297                 listen for them. If it hears such a broadcast on the wire it will
10298                 then start sending them at a frequency set by the parameter
10299                 <TT
10300 CLASS="PARAMETER"
10301 ><I
10302 >lm interval</I
10303 ></TT
10304 >.</P
10305 ><P
10306 >See also <A
10307 HREF="#LMINTERVAL"
10308 ><TT
10309 CLASS="PARAMETER"
10310 ><I
10311 >lm interval
10312                 </I
10313 ></TT
10314 ></A
10315 >.</P
10316 ><P
10317 >Default: <B
10318 CLASS="COMMAND"
10319 >lm announce = auto</B
10320 ></P
10321 ><P
10322 >Example: <B
10323 CLASS="COMMAND"
10324 >lm announce = yes</B
10325 ></P
10326 ></DD
10327 ><DT
10328 ><A
10329 NAME="LMINTERVAL"
10330 ></A
10331 >lm interval (G)</DT
10332 ><DD
10333 ><P
10334 >If Samba is set to produce Lanman announce
10335                 broadcasts needed by OS/2 clients (see the <A
10336 HREF="#LMANNOUNCE"
10337 >               <TT
10338 CLASS="PARAMETER"
10339 ><I
10340 >lm announce</I
10341 ></TT
10342 ></A
10343 > parameter) then this
10344                 parameter defines the frequency in seconds with which they will be
10345                 made.  If this is set to zero then no Lanman announcements will be
10346                 made despite the setting of the <TT
10347 CLASS="PARAMETER"
10348 ><I
10349 >lm announce</I
10350 ></TT
10351 >
10352                 parameter.</P
10353 ><P
10354 >See also <A
10355 HREF="#LMANNOUNCE"
10356 ><TT
10357 CLASS="PARAMETER"
10358 ><I
10359 >lm
10360                 announce</I
10361 ></TT
10362 ></A
10363 >.</P
10364 ><P
10365 >Default: <B
10366 CLASS="COMMAND"
10367 >lm interval = 60</B
10368 ></P
10369 ><P
10370 >Example: <B
10371 CLASS="COMMAND"
10372 >lm interval = 120</B
10373 ></P
10374 ></DD
10375 ><DT
10376 ><A
10377 NAME="LOADPRINTERS"
10378 ></A
10379 >load printers (G)</DT
10380 ><DD
10381 ><P
10382 >A boolean variable that controls whether all
10383                 printers in the printcap will be loaded for browsing by default.
10384                 See the <A
10385 HREF="#AEN79"
10386 >printers</A
10387 > section for
10388                 more details.</P
10389 ><P
10390 >Default: <B
10391 CLASS="COMMAND"
10392 >load printers = yes</B
10393 ></P
10394 ></DD
10395 ><DT
10396 ><A
10397 NAME="LOCALMASTER"
10398 ></A
10399 >local master (G)</DT
10400 ><DD
10401 ><P
10402 >This option allows <A
10403 HREF="nmbd.8.html"
10404 TARGET="_top"
10405 ><B
10406 CLASS="COMMAND"
10407 >               nmbd(8)</B
10408 ></A
10409 > to try and become a local master browser
10410                 on a subnet. If set to <TT
10411 CLASS="CONSTANT"
10412 >no</TT
10413 > then <B
10414 CLASS="COMMAND"
10415 >               nmbd</B
10416 > will not attempt to become a local master browser
10417                 on a subnet and will also lose in all browsing elections. By
10418                 default this value is set to <TT
10419 CLASS="CONSTANT"
10420 >yes</TT
10421 >. Setting this value to <TT
10422 CLASS="CONSTANT"
10423 >yes</TT
10424 > doesn't
10425                 mean that Samba will <EM
10426 >become</EM
10427 > the local master
10428                 browser on a subnet, just that <B
10429 CLASS="COMMAND"
10430 >nmbd</B
10431 > will <EM
10432 >               participate</EM
10433 > in elections for local master browser.</P
10434 ><P
10435 >Setting this value to <TT
10436 CLASS="CONSTANT"
10437 >no</TT
10438 > will cause <B
10439 CLASS="COMMAND"
10440 >nmbd</B
10441 >
10442                 <EM
10443 >never</EM
10444 > to become a local master browser.</P
10445 ><P
10446 >Default: <B
10447 CLASS="COMMAND"
10448 >local master = yes</B
10449 ></P
10450 ></DD
10451 ><DT
10452 ><A
10453 NAME="LOCKDIR"
10454 ></A
10455 >lock dir (G)</DT
10456 ><DD
10457 ><P
10458 >Synonym for <A
10459 HREF="#LOCKDIRECTORY"
10460 ><TT
10461 CLASS="PARAMETER"
10462 ><I
10463 >               lock directory</I
10464 ></TT
10465 ></A
10466 >.</P
10467 ></DD
10468 ><DT
10469 ><A
10470 NAME="LOCKDIRECTORY"
10471 ></A
10472 >lock directory (G)</DT
10473 ><DD
10474 ><P
10475 >This option specifies the directory where lock
10476                 files will be placed.  The lock files are used to implement the
10477                 <A
10478 HREF="#MAXCONNECTIONS"
10479 ><TT
10480 CLASS="PARAMETER"
10481 ><I
10482 >max connections</I
10483 ></TT
10484 >
10485                 </A
10486 > option.</P
10487 ><P
10488 >Default: <B
10489 CLASS="COMMAND"
10490 >lock directory = ${prefix}/var/locks</B
10491 ></P
10492 ><P
10493 >Example: <B
10494 CLASS="COMMAND"
10495 >lock directory = /var/run/samba/locks</B
10496 >
10497                 </P
10498 ></DD
10499 ><DT
10500 ><A
10501 NAME="LOCKSPINCOUNT"
10502 ></A
10503 >lock spin count (G)</DT
10504 ><DD
10505 ><P
10506 >This parameter controls the number of times
10507                 that smbd should attempt to gain a byte range lock on the
10508                 behalf of a client request.  Experiments have shown that
10509                 Windows 2k servers do not reply with a failure if the lock
10510                 could not be immediately granted, but try a few more times
10511                 in case the lock could later be aquired.  This behavior
10512                 is used to support PC database formats such as MS Access
10513                 and FoxPro.
10514                 </P
10515 ><P
10516 >Default: <B
10517 CLASS="COMMAND"
10518 >lock spin count = 2</B
10519 >
10520                 </P
10521 ></DD
10522 ><DT
10523 ><A
10524 NAME="LOCKSPINTIME"
10525 ></A
10526 >lock spin time (G)</DT
10527 ><DD
10528 ><P
10529 >The time in microseconds that smbd should
10530                 pause before attempting to gain a failed lock.  See
10531                 <A
10532 HREF="#LOCKSPINCOUNT"
10533 ><TT
10534 CLASS="PARAMETER"
10535 ><I
10536 >lock spin
10537                 count</I
10538 ></TT
10539 ></A
10540 > for more details.
10541                 </P
10542 ><P
10543 >Default: <B
10544 CLASS="COMMAND"
10545 >lock spin time = 10</B
10546 >
10547                 </P
10548 ></DD
10549 ><DT
10550 ><A
10551 NAME="LOCKING"
10552 ></A
10553 >locking (S)</DT
10554 ><DD
10555 ><P
10556 >This controls whether or not locking will be
10557                 performed by the server in response to lock requests from the
10558                 client.</P
10559 ><P
10560 >If <B
10561 CLASS="COMMAND"
10562 >locking = no</B
10563 >, all lock and unlock
10564                 requests will appear to succeed and all lock queries will report
10565                 that the file in question is available for locking.</P
10566 ><P
10567 >If <B
10568 CLASS="COMMAND"
10569 >locking = yes</B
10570 >, real locking will be performed
10571                 by the server.</P
10572 ><P
10573 >This option <EM
10574 >may</EM
10575 > be useful for read-only
10576                 filesystems which <EM
10577 >may</EM
10578 > not need locking (such as
10579                 CDROM drives), although setting this parameter of <TT
10580 CLASS="CONSTANT"
10581 >no</TT
10582 >
10583                 is not really recommended even in this case.</P
10584 ><P
10585 >Be careful about disabling locking either globally or in a
10586                 specific service, as lack of locking may result in data corruption.
10587                 You should never need to set this parameter.</P
10588 ><P
10589 >Default: <B
10590 CLASS="COMMAND"
10591 >locking = yes</B
10592 ></P
10593 ></DD
10594 ><DT
10595 ><A
10596 NAME="LOGFILE"
10597 ></A
10598 >log file (G)</DT
10599 ><DD
10600 ><P
10601 >This option allows you to override the name
10602                 of the Samba log file (also known as the debug file).</P
10603 ><P
10604 >This option takes the standard substitutions, allowing
10605                 you to have separate log files for each user or machine.</P
10606 ><P
10607 >Example: <B
10608 CLASS="COMMAND"
10609 >log file = /usr/local/samba/var/log.%m
10610                 </B
10611 ></P
10612 ></DD
10613 ><DT
10614 ><A
10615 NAME="LOGLEVEL"
10616 ></A
10617 >log level (G)</DT
10618 ><DD
10619 ><P
10620 >The value of the parameter (an integer) allows
10621                 the debug level (logging level) to be specified in the
10622                 <TT
10623 CLASS="FILENAME"
10624 >smb.conf</TT
10625 > file. This is to give greater
10626                 flexibility in the configuration of the system.</P
10627 ><P
10628 >The default will be the log level specified on
10629                 the command line or level zero if none was specified.</P
10630 ><P
10631 >Example: <B
10632 CLASS="COMMAND"
10633 >log level = 3</B
10634 ></P
10635 ></DD
10636 ><DT
10637 ><A
10638 NAME="LOGONDRIVE"
10639 ></A
10640 >logon drive (G)</DT
10641 ><DD
10642 ><P
10643 >This parameter specifies the local path to
10644                 which the home directory will be connected (see <A
10645 HREF="#LOGONHOME"
10646 ><TT
10647 CLASS="PARAMETER"
10648 ><I
10649 >logon home</I
10650 ></TT
10651 ></A
10652 >)
10653                 and is only used by NT Workstations. </P
10654 ><P
10655 >Note that this option is only useful if Samba is set up as a
10656                 logon server.</P
10657 ><P
10658 >Default: <B
10659 CLASS="COMMAND"
10660 >logon drive = z:</B
10661 ></P
10662 ><P
10663 >Example: <B
10664 CLASS="COMMAND"
10665 >logon drive = h:</B
10666 ></P
10667 ></DD
10668 ><DT
10669 ><A
10670 NAME="LOGONHOME"
10671 ></A
10672 >logon home (G)</DT
10673 ><DD
10674 ><P
10675 >This parameter specifies the home directory
10676                 location when a Win95/98 or NT Workstation logs into a Samba PDC.
10677                 It allows you to do </P
10678 ><P
10679 ><TT
10680 CLASS="PROMPT"
10681 >C:\&#62; </TT
10682 ><TT
10683 CLASS="USERINPUT"
10684 ><B
10685 >NET USE H: /HOME</B
10686 ></TT
10687 >
10688                 </P
10689 ><P
10690 >from a command prompt, for example.</P
10691 ><P
10692 >This option takes the standard substitutions, allowing
10693                 you to have separate logon scripts for each user or machine.</P
10694 ><P
10695 >This parameter can be used with Win9X workstations to ensure
10696                 that roaming profiles are stored in a subdirectory of the user's
10697                 home directory.  This is done in the following way:</P
10698 ><P
10699 ><B
10700 CLASS="COMMAND"
10701 >logon home = \\%N\%U\profile</B
10702 ></P
10703 ><P
10704 >This tells Samba to return the above string, with
10705                 substitutions made when a client requests the info, generally
10706                 in a NetUserGetInfo request.  Win9X clients truncate the info to
10707                 \\server\share when a user does <B
10708 CLASS="COMMAND"
10709 >net use /home</B
10710 >
10711                 but use the whole string when dealing with profiles.</P
10712 ><P
10713 >Note that in prior versions of Samba, the <A
10714 HREF="#LOGONPATH"
10715 >               <TT
10716 CLASS="PARAMETER"
10717 ><I
10718 >logon path</I
10719 ></TT
10720 ></A
10721 > was returned rather than
10722                 <TT
10723 CLASS="PARAMETER"
10724 ><I
10725 >logon home</I
10726 ></TT
10727 >.  This broke <B
10728 CLASS="COMMAND"
10729 >net use
10730                 /home</B
10731 > but allowed profiles outside the home directory.
10732                 The current implementation is correct, and can be used for
10733                 profiles if you use the above trick.</P
10734 ><P
10735 >This option is only useful if Samba is set up as a logon
10736                 server.</P
10737 ><P
10738 >Default: <B
10739 CLASS="COMMAND"
10740 >logon home = "\\%N\%U"</B
10741 ></P
10742 ><P
10743 >Example: <B
10744 CLASS="COMMAND"
10745 >logon home = "\\remote_smb_server\%U"</B
10746 >
10747                 </P
10748 ></DD
10749 ><DT
10750 ><A
10751 NAME="LOGONPATH"
10752 ></A
10753 >logon path (G)</DT
10754 ><DD
10755 ><P
10756 >This parameter specifies the home directory
10757                 where roaming profiles (NTuser.dat etc files for Windows NT) are
10758                 stored.  Contrary to previous versions of these manual pages, it has
10759                 nothing to do with Win 9X roaming profiles.  To find out how to
10760                 handle roaming profiles for Win 9X system, see the <A
10761 HREF="#LOGONHOME"
10762 >               <TT
10763 CLASS="PARAMETER"
10764 ><I
10765 >logon home</I
10766 ></TT
10767 ></A
10768 > parameter.</P
10769 ><P
10770 >This option takes the standard substitutions, allowing you
10771                 to have separate logon scripts for each user or machine.  It also
10772                 specifies the directory from which the "Application Data",
10773                 (<TT
10774 CLASS="FILENAME"
10775 >desktop</TT
10776 >, <TT
10777 CLASS="FILENAME"
10778 >start menu</TT
10779 >,
10780                 <TT
10781 CLASS="FILENAME"
10782 >network neighborhood</TT
10783 >, <TT
10784 CLASS="FILENAME"
10785 >programs</TT
10786 >
10787                 and other folders, and their contents, are loaded and displayed on
10788                 your Windows NT client.</P
10789 ><P
10790 >The share and the path must be readable by the user for
10791                 the preferences and directories to be loaded onto the Windows NT
10792                 client.  The share must be writeable when the user logs in for the first
10793                 time, in order that the Windows NT client can create the NTuser.dat
10794                 and other directories.</P
10795 ><P
10796 >Thereafter, the directories and any of the contents can,
10797                 if required, be made read-only.  It is not advisable that the
10798                 NTuser.dat file be made read-only - rename it to NTuser.man to
10799                 achieve the desired effect (a <EM
10800 >MAN</EM
10801 >datory
10802                 profile). </P
10803 ><P
10804 >Windows clients can sometimes maintain a connection to
10805                 the [homes] share, even though there is no user logged in.
10806                 Therefore, it is vital that the logon path does not include a
10807                 reference to the homes share (i.e. setting this parameter to
10808                 \%N\%U\profile_path will cause problems).</P
10809 ><P
10810 >This option takes the standard substitutions, allowing
10811                 you to have separate logon scripts for each user or machine.</P
10812 ><P
10813 >Note that this option is only useful if Samba is set up
10814                 as a logon server.</P
10815 ><P
10816 >Default: <B
10817 CLASS="COMMAND"
10818 >logon path = \\%N\%U\profile</B
10819 ></P
10820 ><P
10821 >Example: <B
10822 CLASS="COMMAND"
10823 >logon path = \\PROFILESERVER\PROFILE\%U</B
10824 ></P
10825 ></DD
10826 ><DT
10827 ><A
10828 NAME="LOGONSCRIPT"
10829 ></A
10830 >logon script (G)</DT
10831 ><DD
10832 ><P
10833 >This parameter specifies the batch file (.bat) or
10834                 NT command file (.cmd) to be downloaded and run on a machine when
10835                 a user successfully logs in.  The file must contain the DOS
10836                 style CR/LF line endings. Using a DOS-style editor to create the
10837                 file is recommended.</P
10838 ><P
10839 >The script must be a relative path to the [netlogon]
10840                 service.  If the [netlogon] service specifies a <A
10841 HREF="#PATH"
10842 >               <TT
10843 CLASS="PARAMETER"
10844 ><I
10845 >path</I
10846 ></TT
10847 ></A
10848 > of <TT
10849 CLASS="FILENAME"
10850 >/usr/local/samba/netlogon
10851                 </TT
10852 >, and <B
10853 CLASS="COMMAND"
10854 >logon script = STARTUP.BAT</B
10855 >, then
10856                 the file that will be downloaded is:</P
10857 ><P
10858 ><TT
10859 CLASS="FILENAME"
10860 >/usr/local/samba/netlogon/STARTUP.BAT</TT
10861 ></P
10862 ><P
10863 >The contents of the batch file are entirely your choice.  A
10864                 suggested command would be to add <B
10865 CLASS="COMMAND"
10866 >NET TIME \\SERVER /SET
10867                 /YES</B
10868 >, to force every machine to synchronize clocks with
10869                 the same time server.  Another use would be to add <B
10870 CLASS="COMMAND"
10871 >NET USE
10872                 U: \\SERVER\UTILS</B
10873 > for commonly used utilities, or <B
10874 CLASS="COMMAND"
10875 >               NET USE Q: \\SERVER\ISO9001_QA</B
10876 > for example.</P
10877 ><P
10878 >Note that it is particularly important not to allow write
10879                 access to the [netlogon] share, or to grant users write permission
10880                 on the batch files in a secure environment, as this would allow
10881                 the batch files to be arbitrarily modified and security to be
10882                 breached.</P
10883 ><P
10884 >This option takes the standard substitutions, allowing you
10885                 to have separate logon scripts for each user or machine.</P
10886 ><P
10887 >This option is only useful if Samba is set up as a logon
10888                 server.</P
10889 ><P
10890 >Default: <EM
10891 >no logon script defined</EM
10892 ></P
10893 ><P
10894 >Example: <B
10895 CLASS="COMMAND"
10896 >logon script = scripts\%U.bat</B
10897 ></P
10898 ></DD
10899 ><DT
10900 ><A
10901 NAME="LPPAUSECOMMAND"
10902 ></A
10903 >lppause command (S)</DT
10904 ><DD
10905 ><P
10906 >This parameter specifies the command to be
10907                 executed on the server host in order to stop printing or spooling
10908                 a specific print job.</P
10909 ><P
10910 >This command should be a program or script which takes
10911                 a printer name and job number to pause the print job. One way
10912                 of implementing this is by using job priorities, where jobs
10913                 having a too low priority won't be sent to the printer.</P
10914 ><P
10915 >If a <TT
10916 CLASS="PARAMETER"
10917 ><I
10918 >%p</I
10919 ></TT
10920 > is given then the printer name
10921                 is put in its place. A <TT
10922 CLASS="PARAMETER"
10923 ><I
10924 >%j</I
10925 ></TT
10926 > is replaced with
10927                 the job number (an integer).  On HPUX (see <TT
10928 CLASS="PARAMETER"
10929 ><I
10930 >printing=hpux
10931                 </I
10932 ></TT
10933 >), if the <TT
10934 CLASS="PARAMETER"
10935 ><I
10936 >-p%p</I
10937 ></TT
10938 > option is added
10939                 to the lpq command, the job will show up with the correct status, i.e.
10940                 if the job priority is lower than the set fence priority it will
10941                 have the PAUSED status, whereas if  the priority is equal or higher it
10942                 will have the SPOOLED or PRINTING status.</P
10943 ><P
10944 >Note that it is good practice to include the absolute path
10945                 in the lppause command as the PATH may not be available to the server.</P
10946 ><P
10947 >See also the <A
10948 HREF="#PRINTING"
10949 ><TT
10950 CLASS="PARAMETER"
10951 ><I
10952 >printing
10953                 </I
10954 ></TT
10955 ></A
10956 > parameter.</P
10957 ><P
10958 >Default: Currently no default value is given to
10959                 this string, unless the value of the <TT
10960 CLASS="PARAMETER"
10961 ><I
10962 >printing</I
10963 ></TT
10964 >
10965                 parameter is <TT
10966 CLASS="CONSTANT"
10967 >SYSV</TT
10968 >, in which case the default is :</P
10969 ><P
10970 ><B
10971 CLASS="COMMAND"
10972 >lp -i %p-%j -H hold</B
10973 ></P
10974 ><P
10975 >or if the value of the <TT
10976 CLASS="PARAMETER"
10977 ><I
10978 >printing</I
10979 ></TT
10980 > parameter
10981                 is <TT
10982 CLASS="CONSTANT"
10983 >SOFTQ</TT
10984 >, then the default is:</P
10985 ><P
10986 ><B
10987 CLASS="COMMAND"
10988 >qstat -s -j%j -h</B
10989 ></P
10990 ><P
10991 >Example for HPUX: <B
10992 CLASS="COMMAND"
10993 >lppause command = /usr/bin/lpalt
10994                 %p-%j -p0</B
10995 ></P
10996 ></DD
10997 ><DT
10998 ><A
10999 NAME="LPQCACHETIME"
11000 ></A
11001 >lpq cache time (G)</DT
11002 ><DD
11003 ><P
11004 >This controls how long lpq info will be cached
11005                 for to prevent the <B
11006 CLASS="COMMAND"
11007 >lpq</B
11008 > command being called too
11009                 often. A separate cache is kept for each variation of the <B
11010 CLASS="COMMAND"
11011 >               lpq</B
11012 > command used by the system, so if you use different
11013                 <B
11014 CLASS="COMMAND"
11015 >lpq</B
11016 > commands for different users then they won't
11017                 share cache information.</P
11018 ><P
11019 >The cache files are stored in <TT
11020 CLASS="FILENAME"
11021 >/tmp/lpq.xxxx</TT
11022 >
11023                 where xxxx is a hash of the <B
11024 CLASS="COMMAND"
11025 >lpq</B
11026 > command in use.</P
11027 ><P
11028 >The default is 10 seconds, meaning that the cached results
11029                 of a previous identical <B
11030 CLASS="COMMAND"
11031 >lpq</B
11032 > command will be used
11033                 if the cached data is less than 10 seconds old. A large value may
11034                 be advisable if your <B
11035 CLASS="COMMAND"
11036 >lpq</B
11037 > command is very slow.</P
11038 ><P
11039 >A value of 0 will disable caching completely.</P
11040 ><P
11041 >See also the <A
11042 HREF="#PRINTING"
11043 ><TT
11044 CLASS="PARAMETER"
11045 ><I
11046 >printing
11047                 </I
11048 ></TT
11049 ></A
11050 > parameter.</P
11051 ><P
11052 >Default: <B
11053 CLASS="COMMAND"
11054 >lpq cache time = 10</B
11055 ></P
11056 ><P
11057 >Example: <B
11058 CLASS="COMMAND"
11059 >lpq cache time = 30</B
11060 ></P
11061 ></DD
11062 ><DT
11063 ><A
11064 NAME="LPQCOMMAND"
11065 ></A
11066 >lpq command (S)</DT
11067 ><DD
11068 ><P
11069 >This parameter specifies the command to be
11070                 executed on the server host in order to obtain <B
11071 CLASS="COMMAND"
11072 >lpq
11073                 </B
11074 >-style printer status information.</P
11075 ><P
11076 >This command should be a program or script which
11077                 takes a printer name as its only parameter and outputs printer
11078                 status information.</P
11079 ><P
11080 >Currently nine styles of printer status information
11081                 are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ.
11082                 This covers most UNIX systems. You control which type is expected
11083                 using the <TT
11084 CLASS="PARAMETER"
11085 ><I
11086 >printing =</I
11087 ></TT
11088 > option.</P
11089 ><P
11090 >Some clients (notably Windows for Workgroups) may not
11091                 correctly send the connection number for the printer they are
11092                 requesting status information about. To get around this, the
11093                 server reports on the first printer service connected to by the
11094                 client. This only happens if the connection number sent is invalid.</P
11095 ><P
11096 >If a <TT
11097 CLASS="PARAMETER"
11098 ><I
11099 >%p</I
11100 ></TT
11101 > is given then the printer name
11102                 is put in its place. Otherwise it is placed at the end of the
11103                 command.</P
11104 ><P
11105 >Note that it is good practice to include the absolute path
11106                 in the <TT
11107 CLASS="PARAMETER"
11108 ><I
11109 >lpq command</I
11110 ></TT
11111 > as the <TT
11112 CLASS="ENVAR"
11113 >$PATH
11114                 </TT
11115 > may not be available to the server.  When compiled with
11116                 the CUPS libraries, no <TT
11117 CLASS="PARAMETER"
11118 ><I
11119 >lpq command</I
11120 ></TT
11121 > is
11122                 needed because smbd will make a library call to obtain the
11123                 print queue listing.</P
11124 ><P
11125 >See also the <A
11126 HREF="#PRINTING"
11127 ><TT
11128 CLASS="PARAMETER"
11129 ><I
11130 >printing
11131                 </I
11132 ></TT
11133 ></A
11134 > parameter.</P
11135 ><P
11136 >Default: <EM
11137 >depends on the setting of <TT
11138 CLASS="PARAMETER"
11139 ><I
11140 >               printing</I
11141 ></TT
11142 ></EM
11143 ></P
11144 ><P
11145 >Example: <B
11146 CLASS="COMMAND"
11147 >lpq command = /usr/bin/lpq -P%p</B
11148 ></P
11149 ></DD
11150 ><DT
11151 ><A
11152 NAME="LPRESUMECOMMAND"
11153 ></A
11154 >lpresume command (S)</DT
11155 ><DD
11156 ><P
11157 >This parameter specifies the command to be
11158                 executed on the server host in order to restart or continue
11159                 printing or spooling a specific print job.</P
11160 ><P
11161 >This command should be a program or script which takes
11162                 a printer name and job number to resume the print job. See
11163                 also the <A
11164 HREF="#LPPAUSECOMMAND"
11165 ><TT
11166 CLASS="PARAMETER"
11167 ><I
11168 >lppause command
11169                 </I
11170 ></TT
11171 ></A
11172 > parameter.</P
11173 ><P
11174 >If a <TT
11175 CLASS="PARAMETER"
11176 ><I
11177 >%p</I
11178 ></TT
11179 > is given then the printer name
11180                 is put in its place. A <TT
11181 CLASS="PARAMETER"
11182 ><I
11183 >%j</I
11184 ></TT
11185 > is replaced with
11186                 the job number (an integer).</P
11187 ><P
11188 >Note that it is good practice to include the absolute path
11189                 in the <TT
11190 CLASS="PARAMETER"
11191 ><I
11192 >lpresume command</I
11193 ></TT
11194 > as the PATH may not
11195                 be available to the server.</P
11196 ><P
11197 >See also the <A
11198 HREF="#PRINTING"
11199 ><TT
11200 CLASS="PARAMETER"
11201 ><I
11202 >printing
11203                 </I
11204 ></TT
11205 ></A
11206 > parameter.</P
11207 ><P
11208 >Default: Currently no default value is given
11209                 to this string, unless the value of the <TT
11210 CLASS="PARAMETER"
11211 ><I
11212 >printing</I
11213 ></TT
11214 >
11215                 parameter is <TT
11216 CLASS="CONSTANT"
11217 >SYSV</TT
11218 >, in which case the default is :</P
11219 ><P
11220 ><B
11221 CLASS="COMMAND"
11222 >lp -i %p-%j -H resume</B
11223 ></P
11224 ><P
11225 >or if the value of the <TT
11226 CLASS="PARAMETER"
11227 ><I
11228 >printing</I
11229 ></TT
11230 > parameter
11231                 is <TT
11232 CLASS="CONSTANT"
11233 >SOFTQ</TT
11234 >, then the default is:</P
11235 ><P
11236 ><B
11237 CLASS="COMMAND"
11238 >qstat -s -j%j -r</B
11239 ></P
11240 ><P
11241 >Example for HPUX: <B
11242 CLASS="COMMAND"
11243 >lpresume command = /usr/bin/lpalt
11244                 %p-%j -p2</B
11245 ></P
11246 ></DD
11247 ><DT
11248 ><A
11249 NAME="LPRMCOMMAND"
11250 ></A
11251 >lprm command (S)</DT
11252 ><DD
11253 ><P
11254 >This parameter specifies the command to be
11255                 executed on the server host in order to delete a print job.</P
11256 ><P
11257 >This command should be a program or script which takes
11258                 a printer name and job number, and deletes the print job.</P
11259 ><P
11260 >If a <TT
11261 CLASS="PARAMETER"
11262 ><I
11263 >%p</I
11264 ></TT
11265 > is given then the printer name
11266                 is put in its place. A <TT
11267 CLASS="PARAMETER"
11268 ><I
11269 >%j</I
11270 ></TT
11271 > is replaced with
11272                 the job number (an integer).</P
11273 ><P
11274 >Note that it is good practice to include the absolute
11275                 path in the <TT
11276 CLASS="PARAMETER"
11277 ><I
11278 >lprm command</I
11279 ></TT
11280 > as the PATH may not be
11281                 available to the server.</P
11282 ><P
11283 >See also the <A
11284 HREF="#PRINTING"
11285 ><TT
11286 CLASS="PARAMETER"
11287 ><I
11288 >printing
11289                 </I
11290 ></TT
11291 ></A
11292 > parameter.</P
11293 ><P
11294 >Default: <EM
11295 >depends on the setting of <TT
11296 CLASS="PARAMETER"
11297 ><I
11298 >printing
11299                 </I
11300 ></TT
11301 ></EM
11302 ></P
11303 ><P
11304 >Example 1: <B
11305 CLASS="COMMAND"
11306 >lprm command = /usr/bin/lprm -P%p %j
11307                 </B
11308 ></P
11309 ><P
11310 >Example 2: <B
11311 CLASS="COMMAND"
11312 >lprm command = /usr/bin/cancel %p-%j
11313                 </B
11314 ></P
11315 ></DD
11316 ><DT
11317 ><A
11318 NAME="MACHINEPASSWORDTIMEOUT"
11319 ></A
11320 >machine password timeout (G)</DT
11321 ><DD
11322 ><P
11323 >If a Samba server is a member of a Windows
11324                 NT Domain (see the <A
11325 HREF="#SECURITYEQUALSDOMAIN"
11326 >security = domain</A
11327 >)
11328                 parameter) then periodically a running <A
11329 HREF="smbd.8.html"
11330 TARGET="_top"
11331 >               smbd(8)</A
11332 > process will try and change the MACHINE ACCOUNT
11333                 PASSWORD stored in the TDB called <TT
11334 CLASS="FILENAME"
11335 >private/secrets.tdb
11336                 </TT
11337 >.  This parameter specifies how often this password
11338                 will be changed, in seconds. The default is one week (expressed in
11339                 seconds), the same as a Windows NT Domain member server.</P
11340 ><P
11341 >See also <A
11342 HREF="smbpasswd.8.html"
11343 TARGET="_top"
11344 ><B
11345 CLASS="COMMAND"
11346 >smbpasswd(8)
11347                 </B
11348 ></A
11349 >, and the <A
11350 HREF="#SECURITYEQUALSDOMAIN"
11351 >               security = domain</A
11352 >) parameter.</P
11353 ><P
11354 >Default: <B
11355 CLASS="COMMAND"
11356 >machine password timeout = 604800</B
11357 ></P
11358 ></DD
11359 ><DT
11360 ><A
11361 NAME="MAGICOUTPUT"
11362 ></A
11363 >magic output (S)</DT
11364 ><DD
11365 ><P
11366 >This parameter specifies the name of a file
11367                 which will contain output created by a magic script (see the
11368                 <A
11369 HREF="#MAGICSCRIPT"
11370 ><TT
11371 CLASS="PARAMETER"
11372 ><I
11373 >magic script</I
11374 ></TT
11375 ></A
11376 >
11377                 parameter below).</P
11378 ><P
11379 >Warning: If two clients use the same <TT
11380 CLASS="PARAMETER"
11381 ><I
11382 >magic script
11383                 </I
11384 ></TT
11385 > in the same directory the output file content
11386                 is undefined.</P
11387 ><P
11388 >Default: <B
11389 CLASS="COMMAND"
11390 >magic output = &#60;magic script name&#62;.out
11391                 </B
11392 ></P
11393 ><P
11394 >Example: <B
11395 CLASS="COMMAND"
11396 >magic output = myfile.txt</B
11397 ></P
11398 ></DD
11399 ><DT
11400 ><A
11401 NAME="MAGICSCRIPT"
11402 ></A
11403 >magic script (S)</DT
11404 ><DD
11405 ><P
11406 >This parameter specifies the name of a file which,
11407                 if opened, will be executed by the server when the file is closed.
11408                 This allows a UNIX script to be sent to the Samba host and
11409                 executed on behalf of the connected user.</P
11410 ><P
11411 >Scripts executed in this way will be deleted upon
11412                 completion assuming that the user has the appropriate level
11413                 of privilege and the file permissions allow the deletion.</P
11414 ><P
11415 >If the script generates output, output will be sent to
11416                 the file specified by the <A
11417 HREF="#MAGICOUTPUT"
11418 ><TT
11419 CLASS="PARAMETER"
11420 ><I
11421 >               magic output</I
11422 ></TT
11423 ></A
11424 > parameter (see above).</P
11425 ><P
11426 >Note that some shells are unable to interpret scripts
11427                 containing CR/LF instead of CR as
11428                 the end-of-line marker. Magic scripts must be executable
11429                 <EM
11430 >as is</EM
11431 > on the host, which for some hosts and
11432                 some shells will require filtering at the DOS end.</P
11433 ><P
11434 >Magic scripts are <EM
11435 >EXPERIMENTAL</EM
11436 > and
11437                 should <EM
11438 >NOT</EM
11439 > be relied upon.</P
11440 ><P
11441 >Default: <EM
11442 >None. Magic scripts disabled.</EM
11443 ></P
11444 ><P
11445 >Example: <B
11446 CLASS="COMMAND"
11447 >magic script = user.csh</B
11448 ></P
11449 ></DD
11450 ><DT
11451 ><A
11452 NAME="MANGLECASE"
11453 ></A
11454 >mangle case (S)</DT
11455 ><DD
11456 ><P
11457 >See the section on <A
11458 HREF="#AEN203"
11459 >               NAME MANGLING</A
11460 ></P
11461 ><P
11462 >Default: <B
11463 CLASS="COMMAND"
11464 >mangle case = no</B
11465 ></P
11466 ></DD
11467 ><DT
11468 ><A
11469 NAME="MANGLEDMAP"
11470 ></A
11471 >mangled map (S)</DT
11472 ><DD
11473 ><P
11474 >This is for those who want to directly map UNIX
11475                 file names which cannot be represented on Windows/DOS.  The mangling
11476                 of names is not always what is needed.  In particular you may have
11477                 documents with file extensions that differ between DOS and UNIX.
11478                 For example, under UNIX it is common to use <TT
11479 CLASS="FILENAME"
11480 >.html</TT
11481 >
11482                 for HTML files, whereas under Windows/DOS <TT
11483 CLASS="FILENAME"
11484 >.htm</TT
11485 >
11486                 is more commonly used.</P
11487 ><P
11488 >So to map <TT
11489 CLASS="FILENAME"
11490 >html</TT
11491 > to <TT
11492 CLASS="FILENAME"
11493 >htm</TT
11494 >
11495                 you would use:</P
11496 ><P
11497 ><B
11498 CLASS="COMMAND"
11499 >mangled map = (*.html *.htm)</B
11500 ></P
11501 ><P
11502 >One very useful case is to remove the annoying <TT
11503 CLASS="FILENAME"
11504 >;1
11505                 </TT
11506 > off the ends of filenames on some CDROMs (only visible
11507                 under some UNIXes). To do this use a map of (*;1 *;).</P
11508 ><P
11509 >Default: <EM
11510 >no mangled map</EM
11511 ></P
11512 ><P
11513 >Example: <B
11514 CLASS="COMMAND"
11515 >mangled map = (*;1 *;)</B
11516 ></P
11517 ></DD
11518 ><DT
11519 ><A
11520 NAME="MANGLEDNAMES"
11521 ></A
11522 >mangled names (S)</DT
11523 ><DD
11524 ><P
11525 >This controls whether non-DOS names under UNIX
11526                 should be mapped to DOS-compatible names ("mangled") and made visible,
11527                 or whether non-DOS names should simply be ignored.</P
11528 ><P
11529 >See the section on <A
11530 HREF="#AEN203"
11531 >               NAME MANGLING</A
11532 > for details on how to control the mangling process.</P
11533 ><P
11534 >If mangling algorithm "hash" is used then the mangling algorithm is as follows:</P
11535 ><P
11536 ></P
11537 ><UL
11538 ><LI
11539 ><P
11540 >The first (up to) five alphanumeric characters
11541                         before the rightmost dot of the filename are preserved, forced
11542                         to upper case, and appear as the first (up to) five characters
11543                         of the mangled name.</P
11544 ></LI
11545 ><LI
11546 ><P
11547 >A tilde "~" is appended to the first part of the mangled
11548                         name, followed by a two-character unique sequence, based on the
11549                         original root name (i.e., the original filename minus its final
11550                         extension). The final extension is included in the hash calculation
11551                         only if it contains any upper case characters or is longer than three
11552                         characters.</P
11553 ><P
11554 >Note that the character to use may be specified using
11555                         the <A
11556 HREF="#MANGLINGCHAR"
11557 ><TT
11558 CLASS="PARAMETER"
11559 ><I
11560 >mangling char</I
11561 ></TT
11562 >
11563                         </A
11564 > option, if you don't like '~'.</P
11565 ></LI
11566 ><LI
11567 ><P
11568 >The first three alphanumeric characters of the final
11569                         extension are preserved, forced to upper case and appear as the
11570                         extension of the mangled name. The final extension is defined as that
11571                         part of the original filename after the rightmost dot. If there are no
11572                         dots in the filename, the mangled name will have no extension (except
11573                         in the case of "hidden files" - see below).</P
11574 ></LI
11575 ><LI
11576 ><P
11577 >Files whose UNIX name begins with a dot will be
11578                         presented as DOS hidden files. The mangled name will be created as
11579                         for other filenames, but with the leading dot removed and "___" as
11580                         its extension regardless of actual original extension (that's three
11581                         underscores).</P
11582 ></LI
11583 ></UL
11584 ><P
11585 >The two-digit hash value consists of upper case
11586                 alphanumeric characters.</P
11587 ><P
11588 >This algorithm can cause name collisions only if files
11589                 in a directory share the same first five alphanumeric characters.
11590                 The probability of such a clash is 1/1300.</P
11591 ><P
11592 >If mangling algorithm "hash2" is used then the mangling algorithm is as follows:</P
11593 ><P
11594 ></P
11595 ><UL
11596 ><LI
11597 ><P
11598 >The first alphanumeric character
11599                         before the rightmost dot of the filename is preserved, forced
11600                         to upper case, and appears as the first character of the mangled name.
11601                         </P
11602 ></LI
11603 ><LI
11604 ><P
11605 >A base63 hash of 5 characters is generated and the
11606                         first 4 characters of that hash are appended to the first character.
11607                         </P
11608 ></LI
11609 ><LI
11610 ><P
11611 >A tilde "~" is appended to the first part of the mangled
11612                         name, followed by the final character of the base36 hash of the name.
11613                         </P
11614 ><P
11615 >Note that the character to use may be specified using
11616                         the <A
11617 HREF="#MANGLINGCHAR"
11618 ><TT
11619 CLASS="PARAMETER"
11620 ><I
11621 >mangling char</I
11622 ></TT
11623 >
11624                         </A
11625 > option, if you don't like '~'.</P
11626 ></LI
11627 ><LI
11628 ><P
11629 >The first three alphanumeric characters of the final
11630                         extension are preserved, forced to upper case and appear as the
11631                         extension of the mangled name. The final extension is defined as that
11632                         part of the original filename after the rightmost dot. If there are no
11633                         dots in the filename, the mangled name will have no extension (except
11634                         in the case of "hidden files" - see below).</P
11635 ></LI
11636 ><LI
11637 ><P
11638 >Files whose UNIX name begins with a dot will be
11639                         presented as DOS hidden files. The mangled name will be created as
11640                         for other filenames, but with the leading dot removed and "___" as
11641                         its extension regardless of actual original extension (that's three
11642                         underscores).</P
11643 ></LI
11644 ></UL
11645 ><P
11646 >The name mangling (if enabled) allows a file to be
11647                 copied between UNIX directories from Windows/DOS while retaining
11648                 the long UNIX filename. UNIX files can be renamed to a new extension
11649                 from Windows/DOS and will retain the same basename. Mangled names
11650                 do not change between sessions.</P
11651 ><P
11652 >Default: <B
11653 CLASS="COMMAND"
11654 >mangled names = yes</B
11655 ></P
11656 ></DD
11657 ><DT
11658 ><A
11659 NAME="MANGLEDSTACK"
11660 ></A
11661 >mangled stack (G)</DT
11662 ><DD
11663 ><P
11664 >This parameter controls the number of mangled names
11665                 that should be cached in the Samba server <A
11666 HREF="smbd.8.html"
11667 TARGET="_top"
11668 >               smbd(8)</A
11669 >.</P
11670 ><P
11671 >This stack is a list of recently mangled base names
11672                 (extensions are only maintained if they are longer than 3 characters
11673                 or contains upper case characters).</P
11674 ><P
11675 >The larger this value, the more likely it is that mangled
11676                 names can be successfully converted to correct long UNIX names.
11677                 However, large stack sizes will slow most directory accesses. Smaller
11678                 stacks save memory in the server (each stack element costs 256 bytes).
11679                 </P
11680 ><P
11681 >It is not possible to absolutely guarantee correct long
11682                 filenames, so be prepared for some surprises!</P
11683 ><P
11684 >Default: <B
11685 CLASS="COMMAND"
11686 >mangled stack = 50</B
11687 ></P
11688 ><P
11689 >Example: <B
11690 CLASS="COMMAND"
11691 >mangled stack = 100</B
11692 ></P
11693 ></DD
11694 ><DT
11695 ><A
11696 NAME="MANGLINGCHAR"
11697 ></A
11698 >mangling char (S)</DT
11699 ><DD
11700 ><P
11701 >This controls what character is used as
11702                 the <EM
11703 >magic</EM
11704 > character in <A
11705 HREF="#AEN203"
11706 >name mangling</A
11707 >. The default is a '~'
11708                 but this may interfere with some software. Use this option to set
11709                 it to whatever you prefer.</P
11710 ><P
11711 >Default: <B
11712 CLASS="COMMAND"
11713 >mangling char = ~</B
11714 ></P
11715 ><P
11716 >Example: <B
11717 CLASS="COMMAND"
11718 >mangling char = ^</B
11719 ></P
11720 ></DD
11721 ><DT
11722 ><A
11723 NAME="MANGLINGMETHOD"
11724 ></A
11725 >mangling mathod(G)</DT
11726 ><DD
11727 ><P
11728 > controls the algorithm used for the generating
11729                 the mangled names. Can take two different values, "hash" and
11730                 "hash2". "hash" is  the default and is the algorithm that has been
11731                 used in Samba for many years. "hash2" is a newer and considered
11732                 a better algorithm (generates less collisions) in the names.
11733                 However, many Win32 applications store the mangled names and so
11734                 changing to the new algorithm must not be done
11735                 lightly as these applications may break unless reinstalled.
11736                 New installations of Samba may set the default to hash2.</P
11737 ><P
11738 >Default: <B
11739 CLASS="COMMAND"
11740 >mangling method = hash</B
11741 ></P
11742 ><P
11743 >Example: <B
11744 CLASS="COMMAND"
11745 >mangling method = hash2</B
11746 ></P
11747 ></DD
11748 ><DT
11749 ><A
11750 NAME="MAPARCHIVE"
11751 ></A
11752 >map archive (S)</DT
11753 ><DD
11754 ><P
11755 >This controls whether the DOS archive attribute
11756                 should be mapped to the UNIX owner execute bit.  The DOS archive bit
11757                 is set when a file has been modified since its last backup.  One
11758                 motivation for this option it to keep Samba/your PC from making
11759                 any file it touches from becoming executable under UNIX.  This can
11760                 be quite annoying for shared source code, documents, etc...</P
11761 ><P
11762 >Note that this requires the <TT
11763 CLASS="PARAMETER"
11764 ><I
11765 >create mask</I
11766 ></TT
11767 >
11768                 parameter to be set such that owner execute bit is not masked out
11769                 (i.e. it must include 100). See the parameter <A
11770 HREF="#CREATEMASK"
11771 >               <TT
11772 CLASS="PARAMETER"
11773 ><I
11774 >create mask</I
11775 ></TT
11776 ></A
11777 > for details.</P
11778 ><P
11779 >Default: <B
11780 CLASS="COMMAND"
11781 >map archive = yes</B
11782 ></P
11783 ></DD
11784 ><DT
11785 ><A
11786 NAME="MAPHIDDEN"
11787 ></A
11788 >map hidden (S)</DT
11789 ><DD
11790 ><P
11791 >This controls whether DOS style hidden files
11792                 should be mapped to the UNIX world execute bit.</P
11793 ><P
11794 >Note that this requires the <TT
11795 CLASS="PARAMETER"
11796 ><I
11797 >create mask</I
11798 ></TT
11799 >
11800                 to be set such that the world execute bit is not masked out (i.e.
11801                 it must include 001). See the parameter <A
11802 HREF="#CREATEMASK"
11803 >               <TT
11804 CLASS="PARAMETER"
11805 ><I
11806 >create mask</I
11807 ></TT
11808 ></A
11809 > for details.</P
11810 ><P
11811 >Default: <B
11812 CLASS="COMMAND"
11813 >map hidden = no</B
11814 ></P
11815 ></DD
11816 ><DT
11817 ><A
11818 NAME="MAPSYSTEM"
11819 ></A
11820 >map system (S)</DT
11821 ><DD
11822 ><P
11823 >This controls whether DOS style system files
11824                 should be mapped to the UNIX group execute bit.</P
11825 ><P
11826 >Note that this requires the <TT
11827 CLASS="PARAMETER"
11828 ><I
11829 >create mask</I
11830 ></TT
11831 >
11832                 to be set such that the group execute bit is not masked out (i.e.
11833                 it must include 010). See the parameter <A
11834 HREF="#CREATEMASK"
11835 >               <TT
11836 CLASS="PARAMETER"
11837 ><I
11838 >create mask</I
11839 ></TT
11840 ></A
11841 > for details.</P
11842 ><P
11843 >Default: <B
11844 CLASS="COMMAND"
11845 >map system = no</B
11846 ></P
11847 ></DD
11848 ><DT
11849 ><A
11850 NAME="MAPTOGUEST"
11851 ></A
11852 >map to guest (G)</DT
11853 ><DD
11854 ><P
11855 >This parameter is only useful in <A
11856 HREF="#SECURITY"
11857 >               security</A
11858 > modes other than <TT
11859 CLASS="PARAMETER"
11860 ><I
11861 >security = share</I
11862 ></TT
11863 >
11864                 - i.e. <TT
11865 CLASS="CONSTANT"
11866 >user</TT
11867 >, <TT
11868 CLASS="CONSTANT"
11869 >server</TT
11870 >,
11871                 and <TT
11872 CLASS="CONSTANT"
11873 >domain</TT
11874 >.</P
11875 ><P
11876 >This parameter can take three different values, which tell
11877                 <A
11878 HREF="smbd.8.html"
11879 TARGET="_top"
11880 >smbd(8)</A
11881 > what to do with user
11882                 login requests that don't match a valid UNIX user in some way.</P
11883 ><P
11884 >The three settings are :</P
11885 ><P
11886 ></P
11887 ><UL
11888 ><LI
11889 ><P
11890 ><TT
11891 CLASS="CONSTANT"
11892 >Never</TT
11893 > - Means user login
11894                         requests with an invalid password are rejected. This is the
11895                         default.</P
11896 ></LI
11897 ><LI
11898 ><P
11899 ><TT
11900 CLASS="CONSTANT"
11901 >Bad User</TT
11902 > - Means user
11903                         logins with an invalid password are rejected, unless the username
11904                         does not exist, in which case it is treated as a guest login and
11905                         mapped into the <A
11906 HREF="#GUESTACCOUNT"
11907 ><TT
11908 CLASS="PARAMETER"
11909 ><I
11910 >                       guest account</I
11911 ></TT
11912 ></A
11913 >.</P
11914 ></LI
11915 ><LI
11916 ><P
11917 ><TT
11918 CLASS="CONSTANT"
11919 >Bad Password</TT
11920 > - Means user logins
11921                         with an invalid password are treated as a guest login and mapped
11922                         into the <A
11923 HREF="#GUESTACCOUNT"
11924 >guest account</A
11925 >. Note that
11926                         this can cause problems as it means that any user incorrectly typing
11927                         their password will be silently logged on as "guest" - and
11928                         will not know the reason they cannot access files they think
11929                         they should - there will have been no message given to them
11930                         that they got their password wrong. Helpdesk services will
11931                         <EM
11932 >hate</EM
11933 > you if you set the <TT
11934 CLASS="PARAMETER"
11935 ><I
11936 >map to
11937                         guest</I
11938 ></TT
11939 > parameter this way :-).</P
11940 ></LI
11941 ></UL
11942 ><P
11943 >Note that this parameter is needed to set up "Guest"
11944                 share services when using <TT
11945 CLASS="PARAMETER"
11946 ><I
11947 >security</I
11948 ></TT
11949 > modes other than
11950                 share. This is because in these modes the name of the resource being
11951                 requested is <EM
11952 >not</EM
11953 > sent to the server until after
11954                 the server has successfully authenticated the client so the server
11955                 cannot make authentication decisions at the correct time (connection
11956                 to the share) for "Guest" shares.</P
11957 ><P
11958 >For people familiar with the older Samba releases, this
11959                 parameter maps to the old compile-time setting of the <TT
11960 CLASS="CONSTANT"
11961 >               GUEST_SESSSETUP</TT
11962 > value in local.h.</P
11963 ><P
11964 >Default: <B
11965 CLASS="COMMAND"
11966 >map to guest = Never</B
11967 ></P
11968 ><P
11969 >Example: <B
11970 CLASS="COMMAND"
11971 >map to guest = Bad User</B
11972 ></P
11973 ></DD
11974 ><DT
11975 ><A
11976 NAME="MAXCONNECTIONS"
11977 ></A
11978 >max connections (S)</DT
11979 ><DD
11980 ><P
11981 >This option allows the number of simultaneous
11982                 connections to a service to be limited. If <TT
11983 CLASS="PARAMETER"
11984 ><I
11985 >max connections
11986                 </I
11987 ></TT
11988 > is greater than 0 then connections will be refused if
11989                 this number of connections to the service are already open. A value
11990                 of zero mean an unlimited number of connections may be made.</P
11991 ><P
11992 >Record lock files are used to implement this feature. The
11993                 lock files will be stored in the directory specified by the <A
11994 HREF="#LOCKDIRECTORY"
11995 ><TT
11996 CLASS="PARAMETER"
11997 ><I
11998 >lock directory</I
11999 ></TT
12000 ></A
12001 >
12002                 option.</P
12003 ><P
12004 >Default: <B
12005 CLASS="COMMAND"
12006 >max connections = 0</B
12007 ></P
12008 ><P
12009 >Example: <B
12010 CLASS="COMMAND"
12011 >max connections = 10</B
12012 ></P
12013 ></DD
12014 ><DT
12015 ><A
12016 NAME="MAXDISKSIZE"
12017 ></A
12018 >max disk size (G)</DT
12019 ><DD
12020 ><P
12021 >This option allows you to put an upper limit
12022                 on the apparent size of disks. If you set this option to 100
12023                 then all shares will appear to be not larger than 100 MB in
12024                 size.</P
12025 ><P
12026 >Note that this option does not limit the amount of
12027                 data you can put on the disk. In the above case you could still
12028                 store much more than 100 MB on the disk, but if a client ever asks
12029                 for the amount of free disk space or the total disk size then the
12030                 result will be bounded by the amount specified in <TT
12031 CLASS="PARAMETER"
12032 ><I
12033 >max
12034                 disk size</I
12035 ></TT
12036 >.</P
12037 ><P
12038 >This option is primarily useful to work around bugs
12039                 in some pieces of software that can't handle very large disks,
12040                 particularly disks over 1GB in size.</P
12041 ><P
12042 >A <TT
12043 CLASS="PARAMETER"
12044 ><I
12045 >max disk size</I
12046 ></TT
12047 > of 0 means no limit.</P
12048 ><P
12049 >Default: <B
12050 CLASS="COMMAND"
12051 >max disk size = 0</B
12052 ></P
12053 ><P
12054 >Example: <B
12055 CLASS="COMMAND"
12056 >max disk size = 1000</B
12057 ></P
12058 ></DD
12059 ><DT
12060 ><A
12061 NAME="MAXLOGSIZE"
12062 ></A
12063 >max log size (G)</DT
12064 ><DD
12065 ><P
12066 >This option (an integer in kilobytes) specifies
12067                 the max size the log file should grow to. Samba periodically checks
12068                 the size and if it is exceeded it will rename the file, adding
12069                 a <TT
12070 CLASS="FILENAME"
12071 >.old</TT
12072 > extension.</P
12073 ><P
12074 >A size of 0 means no limit.</P
12075 ><P
12076 >Default: <B
12077 CLASS="COMMAND"
12078 >max log size = 5000</B
12079 ></P
12080 ><P
12081 >Example: <B
12082 CLASS="COMMAND"
12083 >max log size = 1000</B
12084 ></P
12085 ></DD
12086 ><DT
12087 ><A
12088 NAME="MAXMUX"
12089 ></A
12090 >max mux (G)</DT
12091 ><DD
12092 ><P
12093 >This option controls the maximum number of
12094                 outstanding simultaneous SMB operations that Samba tells the client
12095                 it will allow. You should never need to set this parameter.</P
12096 ><P
12097 >Default: <B
12098 CLASS="COMMAND"
12099 >max mux = 50</B
12100 ></P
12101 ></DD
12102 ><DT
12103 ><A
12104 NAME="MAXOPENFILES"
12105 ></A
12106 >max open files (G)</DT
12107 ><DD
12108 ><P
12109 >This parameter limits the maximum number of
12110                 open files that one <A
12111 HREF="smbd.8.html"
12112 TARGET="_top"
12113 >smbd(8)</A
12114 > file
12115                 serving process may have open for a client at any one time. The
12116                 default for this parameter is set very high (10,000) as Samba uses
12117                 only one bit per unopened file.</P
12118 ><P
12119 >The limit of the number of open files is usually set
12120                 by the UNIX per-process file descriptor limit rather than
12121                 this parameter so you should never need to touch this parameter.</P
12122 ><P
12123 >Default: <B
12124 CLASS="COMMAND"
12125 >max open files = 10000</B
12126 ></P
12127 ></DD
12128 ><DT
12129 ><A
12130 NAME="MAXPRINTJOBS"
12131 ></A
12132 >max print jobs (S)</DT
12133 ><DD
12134 ><P
12135 >This parameter limits the maximum number of
12136                 jobs allowable in a Samba printer queue at any given moment.
12137                 If this number is exceeded, <A
12138 HREF="smbd.8.html"
12139 TARGET="_top"
12140 ><B
12141 CLASS="COMMAND"
12142 >               smbd(8)</B
12143 ></A
12144 > will remote "Out of Space" to the client.
12145                 See all <A
12146 HREF="#TOTALPRINTJOBS"
12147 ><TT
12148 CLASS="PARAMETER"
12149 ><I
12150 >total
12151                 print jobs</I
12152 ></TT
12153 ></A
12154 >.
12155                 </P
12156 ><P
12157 >Default: <B
12158 CLASS="COMMAND"
12159 >max print jobs = 1000</B
12160 ></P
12161 ><P
12162 >Example: <B
12163 CLASS="COMMAND"
12164 >max print jobs = 5000</B
12165 ></P
12166 ></DD
12167 ><DT
12168 ><A
12169 NAME="MAXPROTOCOL"
12170 ></A
12171 >max protocol (G)</DT
12172 ><DD
12173 ><P
12174 >The value of the parameter (a string) is the highest
12175                 protocol level that will be supported by the server.</P
12176 ><P
12177 >Possible values are :</P
12178 ><P
12179 ></P
12180 ><UL
12181 ><LI
12182 ><P
12183 ><TT
12184 CLASS="CONSTANT"
12185 >CORE</TT
12186 >: Earliest version. No
12187                         concept of user names.</P
12188 ></LI
12189 ><LI
12190 ><P
12191 ><TT
12192 CLASS="CONSTANT"
12193 >COREPLUS</TT
12194 >: Slight improvements on
12195                         CORE for efficiency.</P
12196 ></LI
12197 ><LI
12198 ><P
12199 ><TT
12200 CLASS="CONSTANT"
12201 >LANMAN1</TT
12202 >: First <EM
12203 >                       modern</EM
12204 > version of the protocol. Long filename
12205                         support.</P
12206 ></LI
12207 ><LI
12208 ><P
12209 ><TT
12210 CLASS="CONSTANT"
12211 >LANMAN2</TT
12212 >: Updates to Lanman1 protocol.
12213                         </P
12214 ></LI
12215 ><LI
12216 ><P
12217 ><TT
12218 CLASS="CONSTANT"
12219 >NT1</TT
12220 >: Current up to date version of
12221                         the protocol. Used by Windows NT. Known as CIFS.</P
12222 ></LI
12223 ></UL
12224 ><P
12225 >Normally this option should not be set as the automatic
12226                 negotiation phase in the SMB protocol takes care of choosing
12227                 the appropriate protocol.</P
12228 ><P
12229 >See also <A
12230 HREF="#MINPROTOCOL"
12231 ><TT
12232 CLASS="PARAMETER"
12233 ><I
12234 >min
12235                 protocol</I
12236 ></TT
12237 ></A
12238 ></P
12239 ><P
12240 >Default: <B
12241 CLASS="COMMAND"
12242 >max protocol = NT1</B
12243 ></P
12244 ><P
12245 >Example: <B
12246 CLASS="COMMAND"
12247 >max protocol = LANMAN1</B
12248 ></P
12249 ></DD
12250 ><DT
12251 ><A
12252 NAME="MAXSMBDPROCESSES"
12253 ></A
12254 >max smbd processes (G)</DT
12255 ><DD
12256 ><P
12257 >This parameter limits the maximum number of
12258                 <A
12259 HREF="smbd.8.html"
12260 TARGET="_top"
12261 ><B
12262 CLASS="COMMAND"
12263 >smbd(8)</B
12264 ></A
12265 >
12266                 processes concurrently running on a system and is intended
12267                 as a stopgap to prevent degrading service to clients in the event
12268                 that the server has insufficient resources to handle more than this
12269                 number of connections.  Remember that under normal operating
12270                 conditions, each user will have an <A
12271 HREF="smbd.8.html"
12272 TARGET="_top"
12273 >smbd</A
12274 > associated with him or her
12275                 to handle connections to all shares from a given host.
12276                 </P
12277 ><P
12278 >Default: <B
12279 CLASS="COMMAND"
12280 >max smbd processes = 0</B
12281 >   ## no limit</P
12282 ><P
12283 >Example: <B
12284 CLASS="COMMAND"
12285 >max smbd processes = 1000</B
12286 ></P
12287 ></DD
12288 ><DT
12289 ><A
12290 NAME="MAXTTL"
12291 ></A
12292 >max ttl (G)</DT
12293 ><DD
12294 ><P
12295 >This option tells <A
12296 HREF="nmbd.8.html"
12297 TARGET="_top"
12298 >nmbd(8)</A
12299 >
12300                 what the default 'time to live' of NetBIOS names should be (in seconds)
12301                 when <B
12302 CLASS="COMMAND"
12303 >nmbd</B
12304 > is requesting a name using either a
12305                 broadcast packet or from a WINS server. You should never need to
12306                 change this parameter. The default is 3 days.</P
12307 ><P
12308 >Default: <B
12309 CLASS="COMMAND"
12310 >max ttl = 259200</B
12311 ></P
12312 ></DD
12313 ><DT
12314 ><A
12315 NAME="MAXWINSTTL"
12316 ></A
12317 >max wins ttl (G)</DT
12318 ><DD
12319 ><P
12320 >This option tells <A
12321 HREF="nmbd.8.html"
12322 TARGET="_top"
12323 >nmbd(8)
12324                 </A
12325 > when acting as a WINS server (<A
12326 HREF="#WINSSUPPORT"
12327 >               <TT
12328 CLASS="PARAMETER"
12329 ><I
12330 >wins support = yes</I
12331 ></TT
12332 ></A
12333 >) what the maximum
12334                 'time to live' of NetBIOS names that <B
12335 CLASS="COMMAND"
12336 >nmbd</B
12337 >
12338                 will grant will be (in seconds). You should never need to change this
12339                 parameter.  The default is 6 days (518400 seconds).</P
12340 ><P
12341 >See also the <A
12342 HREF="#MINWINSTTL"
12343 ><TT
12344 CLASS="PARAMETER"
12345 ><I
12346 >min
12347                 wins ttl</I
12348 ></TT
12349 ></A
12350 > parameter.</P
12351 ><P
12352 >Default: <B
12353 CLASS="COMMAND"
12354 >max wins ttl = 518400</B
12355 ></P
12356 ></DD
12357 ><DT
12358 ><A
12359 NAME="MAXXMIT"
12360 ></A
12361 >max xmit (G)</DT
12362 ><DD
12363 ><P
12364 >This option controls the maximum packet size
12365                 that will be negotiated by Samba. The default is 65535, which
12366                 is the maximum. In some cases you may find you get better performance
12367                 with a smaller value. A value below 2048 is likely to cause problems.
12368                 </P
12369 ><P
12370 >Default: <B
12371 CLASS="COMMAND"
12372 >max xmit = 65535</B
12373 ></P
12374 ><P
12375 >Example: <B
12376 CLASS="COMMAND"
12377 >max xmit = 8192</B
12378 ></P
12379 ></DD
12380 ><DT
12381 ><A
12382 NAME="MESSAGECOMMAND"
12383 ></A
12384 >message command (G)</DT
12385 ><DD
12386 ><P
12387 >This specifies what command to run when the
12388                 server receives a WinPopup style message.</P
12389 ><P
12390 >This would normally be a command that would
12391                 deliver the message somehow. How this is to be done is
12392                 up to your imagination.</P
12393 ><P
12394 >An example is:</P
12395 ><P
12396 ><B
12397 CLASS="COMMAND"
12398 >message command = csh -c 'xedit %s;rm %s' &#38;</B
12399 >
12400                 </P
12401 ><P
12402 >This delivers the message using <B
12403 CLASS="COMMAND"
12404 >xedit</B
12405 >, then
12406                 removes it afterwards. <EM
12407 >NOTE THAT IT IS VERY IMPORTANT
12408                 THAT THIS COMMAND RETURN IMMEDIATELY</EM
12409 >. That's why I
12410                 have the '&#38;' on the end. If it doesn't return immediately then
12411                 your PCs may freeze when sending messages (they should recover
12412                 after 30 seconds, hopefully).</P
12413 ><P
12414 >All messages are delivered as the global guest user.
12415                 The command takes the standard substitutions, although <TT
12416 CLASS="PARAMETER"
12417 ><I
12418 >               %u</I
12419 ></TT
12420 > won't work (<TT
12421 CLASS="PARAMETER"
12422 ><I
12423 >%U</I
12424 ></TT
12425 > may be better
12426                 in this case).</P
12427 ><P
12428 >Apart from the standard substitutions, some additional
12429                 ones apply. In particular:</P
12430 ><P
12431 ></P
12432 ><UL
12433 ><LI
12434 ><P
12435 ><TT
12436 CLASS="PARAMETER"
12437 ><I
12438 >%s</I
12439 ></TT
12440 > = the filename containing
12441                         the message.</P
12442 ></LI
12443 ><LI
12444 ><P
12445 ><TT
12446 CLASS="PARAMETER"
12447 ><I
12448 >%t</I
12449 ></TT
12450 > = the destination that
12451                         the message was sent to (probably the server name).</P
12452 ></LI
12453 ><LI
12454 ><P
12455 ><TT
12456 CLASS="PARAMETER"
12457 ><I
12458 >%f</I
12459 ></TT
12460 > = who the message
12461                         is from.</P
12462 ></LI
12463 ></UL
12464 ><P
12465 >You could make this command send mail, or whatever else
12466                 takes your fancy. Please let us know of any really interesting
12467                 ideas you have.</P
12468 ><P
12469 >Here's a way of sending the messages as mail to root:</P
12470 ><P
12471 ><B
12472 CLASS="COMMAND"
12473 >message command = /bin/mail -s 'message from %f on
12474                 %m' root &#60; %s; rm %s</B
12475 ></P
12476 ><P
12477 >If you don't have a message command then the message
12478                 won't be delivered and Samba will tell the sender there was
12479                 an error. Unfortunately WfWg totally ignores the error code
12480                 and carries on regardless, saying that the message was delivered.
12481                 </P
12482 ><P
12483 >If you want to silently delete it then try:</P
12484 ><P
12485 ><B
12486 CLASS="COMMAND"
12487 >message command = rm %s</B
12488 ></P
12489 ><P
12490 >Default: <EM
12491 >no message command</EM
12492 ></P
12493 ><P
12494 >Example: <B
12495 CLASS="COMMAND"
12496 >message command = csh -c 'xedit %s;
12497                 rm %s' &#38;</B
12498 ></P
12499 ></DD
12500 ><DT
12501 ><A
12502 NAME="MINPASSWDLENGTH"
12503 ></A
12504 >min passwd length (G)</DT
12505 ><DD
12506 ><P
12507 >Synonym for <A
12508 HREF="#MINPASSWORDLENGTH"
12509 >               <TT
12510 CLASS="PARAMETER"
12511 ><I
12512 >min password length</I
12513 ></TT
12514 ></A
12515 >.</P
12516 ></DD
12517 ><DT
12518 ><A
12519 NAME="MINPASSWORDLENGTH"
12520 ></A
12521 >min password length (G)</DT
12522 ><DD
12523 ><P
12524 >This option sets the minimum length in characters
12525                 of a plaintext password that <B
12526 CLASS="COMMAND"
12527 >smbd</B
12528 > will accept when performing
12529                 UNIX password changing.</P
12530 ><P
12531 >See also <A
12532 HREF="#UNIXPASSWORDSYNC"
12533 ><TT
12534 CLASS="PARAMETER"
12535 ><I
12536 >unix
12537                 password sync</I
12538 ></TT
12539 ></A
12540 >, <A
12541 HREF="#PASSWDPROGRAM"
12542 >               <TT
12543 CLASS="PARAMETER"
12544 ><I
12545 >passwd program</I
12546 ></TT
12547 ></A
12548 > and <A
12549 HREF="#PASSWDCHATDEBUG"
12550 ><TT
12551 CLASS="PARAMETER"
12552 ><I
12553 >passwd chat debug</I
12554 ></TT
12555 >
12556                 </A
12557 >.</P
12558 ><P
12559 >Default: <B
12560 CLASS="COMMAND"
12561 >min password length = 5</B
12562 ></P
12563 ></DD
12564 ><DT
12565 ><A
12566 NAME="MINPRINTSPACE"
12567 ></A
12568 >min print space (S)</DT
12569 ><DD
12570 ><P
12571 >This sets the minimum amount of free disk
12572                 space that must be available before a user will be able to spool
12573                 a print job. It is specified in kilobytes. The default is 0, which
12574                 means a user can always spool a print job.</P
12575 ><P
12576 >See also the <A
12577 HREF="#PRINTING"
12578 ><TT
12579 CLASS="PARAMETER"
12580 ><I
12581 >printing
12582                 </I
12583 ></TT
12584 ></A
12585 > parameter.</P
12586 ><P
12587 >Default: <B
12588 CLASS="COMMAND"
12589 >min print space = 0</B
12590 ></P
12591 ><P
12592 >Example: <B
12593 CLASS="COMMAND"
12594 >min print space = 2000</B
12595 ></P
12596 ></DD
12597 ><DT
12598 ><A
12599 NAME="MINPROTOCOL"
12600 ></A
12601 >min protocol (G)</DT
12602 ><DD
12603 ><P
12604 >The value of the parameter (a string) is the
12605                 lowest SMB protocol dialect than Samba will support.  Please refer
12606                 to the <A
12607 HREF="#MAXPROTOCOL"
12608 ><TT
12609 CLASS="PARAMETER"
12610 ><I
12611 >max protocol</I
12612 ></TT
12613 ></A
12614 >
12615                 parameter for a list of valid protocol names and a brief description
12616                 of each.  You may also wish to refer to the C source code in
12617                 <TT
12618 CLASS="FILENAME"
12619 >source/smbd/negprot.c</TT
12620 > for a listing of known protocol
12621                 dialects supported by clients.</P
12622 ><P
12623 >If you are viewing this parameter as a security measure, you should
12624                 also refer to the <A
12625 HREF="#LANMANAUTH"
12626 ><TT
12627 CLASS="PARAMETER"
12628 ><I
12629 >lanman
12630                 auth</I
12631 ></TT
12632 ></A
12633 > parameter.  Otherwise, you should never need
12634                 to change this parameter.</P
12635 ><P
12636 >Default : <B
12637 CLASS="COMMAND"
12638 >min protocol = CORE</B
12639 ></P
12640 ><P
12641 >Example : <B
12642 CLASS="COMMAND"
12643 >min protocol = NT1</B
12644 >  # disable DOS
12645                 clients</P
12646 ></DD
12647 ><DT
12648 ><A
12649 NAME="MINWINSTTL"
12650 ></A
12651 >min wins ttl (G)</DT
12652 ><DD
12653 ><P
12654 >This option tells <A
12655 HREF="nmbd.8.html"
12656 TARGET="_top"
12657 >nmbd(8)</A
12658 >
12659                 when acting as a WINS server (<A
12660 HREF="#WINSSUPPORT"
12661 ><TT
12662 CLASS="PARAMETER"
12663 ><I
12664 >               wins support = yes</I
12665 ></TT
12666 ></A
12667 >) what the minimum 'time to live'
12668                 of NetBIOS names that <B
12669 CLASS="COMMAND"
12670 >nmbd</B
12671 > will grant will be (in
12672                 seconds). You should never need to change this parameter.  The default
12673                 is 6 hours (21600 seconds).</P
12674 ><P
12675 >Default: <B
12676 CLASS="COMMAND"
12677 >min wins ttl = 21600</B
12678 ></P
12679 ></DD
12680 ><DT
12681 ><A
12682 NAME="MSDFSROOT"
12683 ></A
12684 >msdfs root (S)</DT
12685 ><DD
12686 ><P
12687 >This boolean parameter is only available if
12688                 Samba is configured  and  compiled with the <B
12689 CLASS="COMMAND"
12690 >               --with-msdfs</B
12691 > option.  If set to <TT
12692 CLASS="CONSTANT"
12693 >yes</TT
12694 >,
12695                 Samba treats the share as a Dfs root and  allows clients to browse
12696                 the distributed file system tree rooted at the share directory.
12697                 Dfs links are specified  in  the share directory by symbolic
12698                 links of the form <TT
12699 CLASS="FILENAME"
12700 >msdfs:serverA\shareA,serverB\shareB
12701                 </TT
12702 > and so on.  For more information on setting up a Dfs tree
12703                 on Samba,  refer to <A
12704 HREF="msdfs_setup.html"
12705 TARGET="_top"
12706 >msdfs_setup.html
12707                 </A
12708 >.</P
12709 ><P
12710 >See also <A
12711 HREF="#HOSTMSDFS"
12712 ><TT
12713 CLASS="PARAMETER"
12714 ><I
12715 >host msdfs
12716                 </I
12717 ></TT
12718 ></A
12719 ></P
12720 ><P
12721 >Default: <B
12722 CLASS="COMMAND"
12723 >msdfs root = no</B
12724 ></P
12725 ></DD
12726 ><DT
12727 ><A
12728 NAME="NAMERESOLVEORDER"
12729 ></A
12730 >name resolve order (G)</DT
12731 ><DD
12732 ><P
12733 >This option is used by the programs in the Samba
12734                 suite to determine what naming services to use and in what order
12735                 to resolve host names to IP addresses. The option takes a space
12736                 separated string of name resolution options.</P
12737 ><P
12738 >The options are :"lmhosts", "host", "wins" and "bcast". They
12739                 cause names to be resolved as follows :</P
12740 ><P
12741 ></P
12742 ><UL
12743 ><LI
12744 ><P
12745 ><TT
12746 CLASS="CONSTANT"
12747 >lmhosts</TT
12748 > : Lookup an IP
12749                         address in the Samba lmhosts file. If the line in lmhosts has
12750                         no name type attached to the NetBIOS name (see the <A
12751 HREF="lmhosts.5.html"
12752 TARGET="_top"
12753 >lmhosts(5)</A
12754 > for details) then
12755                         any name type matches for lookup.</P
12756 ></LI
12757 ><LI
12758 ><P
12759 ><TT
12760 CLASS="CONSTANT"
12761 >host</TT
12762 > : Do a standard host
12763                         name to IP address resolution, using the system <TT
12764 CLASS="FILENAME"
12765 >/etc/hosts
12766                         </TT
12767 >, NIS, or DNS lookups. This method of name resolution
12768                         is operating system depended for instance on IRIX or Solaris this
12769                         may be controlled by the <TT
12770 CLASS="FILENAME"
12771 >/etc/nsswitch.conf</TT
12772 >
12773                         file.  Note that this method is only used if the NetBIOS name
12774                         type being queried is the 0x20 (server) name type, otherwise
12775                         it is ignored.</P
12776 ></LI
12777 ><LI
12778 ><P
12779 ><TT
12780 CLASS="CONSTANT"
12781 >wins</TT
12782 > : Query a name with
12783                         the IP address listed in the <A
12784 HREF="#WINSSERVER"
12785 ><TT
12786 CLASS="PARAMETER"
12787 ><I
12788 >                       wins server</I
12789 ></TT
12790 ></A
12791 > parameter.  If no WINS server has
12792                         been specified this method will be ignored.</P
12793 ></LI
12794 ><LI
12795 ><P
12796 ><TT
12797 CLASS="CONSTANT"
12798 >bcast</TT
12799 > : Do a broadcast on
12800                         each of the known local interfaces listed in the <A
12801 HREF="#INTERFACES"
12802 ><TT
12803 CLASS="PARAMETER"
12804 ><I
12805 >interfaces</I
12806 ></TT
12807 ></A
12808 >
12809                         parameter. This is the least reliable of the name resolution
12810                         methods as it depends on the target host being on a locally
12811                         connected subnet.</P
12812 ></LI
12813 ></UL
12814 ><P
12815 >Default: <B
12816 CLASS="COMMAND"
12817 >name resolve order = lmhosts host wins bcast
12818                 </B
12819 ></P
12820 ><P
12821 >Example: <B
12822 CLASS="COMMAND"
12823 >name resolve order = lmhosts bcast host
12824                 </B
12825 ></P
12826 ><P
12827 >This will cause the local lmhosts file to be examined
12828                 first, followed by a broadcast attempt, followed by a normal
12829                 system hostname lookup.</P
12830 ></DD
12831 ><DT
12832 ><A
12833 NAME="NETBIOSALIASES"
12834 ></A
12835 >netbios aliases (G)</DT
12836 ><DD
12837 ><P
12838 >This is a list of NetBIOS names that <A
12839 HREF="nmbd.8.html"
12840 TARGET="_top"
12841 >nmbd(8)</A
12842 > will advertise as additional
12843                 names by which the Samba server is known. This allows one machine
12844                 to appear in browse lists under multiple names. If a machine is
12845                 acting as a browse server or logon server none
12846                 of these names will be advertised as either browse server or logon
12847                 servers, only the primary name of the machine will be advertised
12848                 with these capabilities.</P
12849 ><P
12850 >See also <A
12851 HREF="#NETBIOSNAME"
12852 ><TT
12853 CLASS="PARAMETER"
12854 ><I
12855 >netbios
12856                 name</I
12857 ></TT
12858 ></A
12859 >.</P
12860 ><P
12861 >Default: <EM
12862 >empty string (no additional names)</EM
12863 ></P
12864 ><P
12865 >Example: <B
12866 CLASS="COMMAND"
12867 >netbios aliases = TEST TEST1 TEST2</B
12868 ></P
12869 ></DD
12870 ><DT
12871 ><A
12872 NAME="NETBIOSNAME"
12873 ></A
12874 >netbios name (G)</DT
12875 ><DD
12876 ><P
12877 >This sets the NetBIOS name by which a Samba
12878                 server is known. By default it is the same as the first component
12879                 of the host's DNS name. If a machine is a browse server or
12880                 logon server this name (or the first component
12881                 of the hosts DNS name) will be the name that these services are
12882                 advertised under.</P
12883 ><P
12884 >See also <A
12885 HREF="#NETBIOSALIASES"
12886 ><TT
12887 CLASS="PARAMETER"
12888 ><I
12889 >netbios
12890                 aliases</I
12891 ></TT
12892 ></A
12893 >.</P
12894 ><P
12895 >Default: <EM
12896 >machine DNS name</EM
12897 ></P
12898 ><P
12899 >Example: <B
12900 CLASS="COMMAND"
12901 >netbios name = MYNAME</B
12902 ></P
12903 ></DD
12904 ><DT
12905 ><A
12906 NAME="NETBIOSSCOPE"
12907 ></A
12908 >netbios scope (G)</DT
12909 ><DD
12910 ><P
12911 >This sets the NetBIOS scope that Samba will
12912                 operate under. This should not be set unless every machine
12913                 on your LAN also sets this value.</P
12914 ></DD
12915 ><DT
12916 ><A
12917 NAME="NISHOMEDIR"
12918 ></A
12919 >nis homedir (G)</DT
12920 ><DD
12921 ><P
12922 >Get the home share server from a NIS map. For
12923                 UNIX systems that use an automounter, the user's home directory
12924                 will often be mounted on a workstation on demand from a remote
12925                 server. </P
12926 ><P
12927 >When the Samba logon server is not the actual home directory
12928                 server, but is mounting the home directories via NFS then two
12929                 network hops would be required to access the users home directory
12930                 if the logon server told the client to use itself as the SMB server
12931                 for home directories (one over SMB and one over NFS). This can
12932                 be very slow.</P
12933 ><P
12934 >This option allows Samba to return the home share as
12935                 being on a different server to the logon server and as
12936                 long as a Samba daemon is running on the home directory server,
12937                 it will be mounted on the Samba client directly from the directory
12938                 server. When Samba is returning the home share to the client, it
12939                 will consult the NIS map specified in <A
12940 HREF="#HOMEDIRMAP"
12941 >               <TT
12942 CLASS="PARAMETER"
12943 ><I
12944 >homedir map</I
12945 ></TT
12946 ></A
12947 > and return the server
12948                 listed there.</P
12949 ><P
12950 >Note that for this option to work there must be a working
12951                 NIS system and the Samba server with this option must also
12952                 be a logon server.</P
12953 ><P
12954 >Default: <B
12955 CLASS="COMMAND"
12956 >nis homedir = no</B
12957 ></P
12958 ></DD
12959 ><DT
12960 ><A
12961 NAME="NTACLSUPPORT"
12962 ></A
12963 >nt acl support (S)</DT
12964 ><DD
12965 ><P
12966 >This boolean parameter controls whether
12967                 <A
12968 HREF="smbd.8.html"
12969 TARGET="_top"
12970 >smbd(8)</A
12971 > will attempt to map
12972                 UNIX permissions into Windows NT access control lists.
12973                 This parameter was formally a global parameter in releases
12974                 prior to 2.2.2.</P
12975 ><P
12976 >Default: <B
12977 CLASS="COMMAND"
12978 >nt acl support = yes</B
12979 ></P
12980 ></DD
12981 ><DT
12982 ><A
12983 NAME="NTPIPESUPPORT"
12984 ></A
12985 >nt pipe support (G)</DT
12986 ><DD
12987 ><P
12988 >This boolean parameter controls whether
12989                 <A
12990 HREF="smbd.8.html"
12991 TARGET="_top"
12992 >smbd(8)</A
12993 > will allow Windows NT
12994                 clients to connect to the NT SMB specific <TT
12995 CLASS="CONSTANT"
12996 >IPC$</TT
12997 >
12998                 pipes. This is a developer debugging option and can be left
12999                 alone.</P
13000 ><P
13001 >Default: <B
13002 CLASS="COMMAND"
13003 >nt pipe support = yes</B
13004 ></P
13005 ></DD
13006 ><DT
13007 ><A
13008 NAME="NTSMBSUPPORT"
13009 ></A
13010 >nt smb support (G)</DT
13011 ><DD
13012 ><P
13013 >This boolean parameter controls whether <A
13014 HREF="smbd.8.html"
13015 TARGET="_top"
13016 >smbd(8)</A
13017 > will negotiate NT specific SMB
13018                 support with Windows NT/2k/XP clients. Although this is a developer
13019                 debugging option and should be left alone, benchmarking has discovered
13020                 that Windows NT clients give faster performance with this option
13021                 set to <TT
13022 CLASS="CONSTANT"
13023 >no</TT
13024 >. This is still being investigated.
13025                 If this option is set to <TT
13026 CLASS="CONSTANT"
13027 >no</TT
13028 > then Samba offers
13029                 exactly the same SMB calls that versions prior to Samba 2.0 offered.
13030                 This information may be of use if any users are having problems
13031                 with NT SMB support.</P
13032 ><P
13033 >You should not need to ever disable this parameter.</P
13034 ><P
13035 >Default: <B
13036 CLASS="COMMAND"
13037 >nt smb support = yes</B
13038 ></P
13039 ></DD
13040 ><DT
13041 ><A
13042 NAME="NTSTATUSSUPPORT"
13043 ></A
13044 >nt status support (G)</DT
13045 ><DD
13046 ><P
13047 >This boolean parameter controls whether <A
13048 HREF="smbd.8.html"
13049 TARGET="_top"
13050 >smbd(8)</A
13051 > will negotiate NT specific status
13052                 support with Windows NT/2k/XP clients. This is a developer
13053                 debugging option and should be left alone.
13054                 If this option is set to <TT
13055 CLASS="CONSTANT"
13056 >no</TT
13057 > then Samba offers
13058                 exactly the same DOS error codes that versions prior to Samba 2.2.3
13059                 reported.</P
13060 ><P
13061 >You should not need to ever disable this parameter.</P
13062 ><P
13063 >Default: <B
13064 CLASS="COMMAND"
13065 >nt status support = yes</B
13066 ></P
13067 ></DD
13068 ><DT
13069 ><A
13070 NAME="NULLPASSWORDS"
13071 ></A
13072 >null passwords (G)</DT
13073 ><DD
13074 ><P
13075 >Allow or disallow client access to accounts
13076                 that have null passwords. </P
13077 ><P
13078 >See also <A
13079 HREF="smbpasswd.5.html"
13080 TARGET="_top"
13081 >smbpasswd (5)</A
13082 >.</P
13083 ><P
13084 >Default: <B
13085 CLASS="COMMAND"
13086 >null passwords = no</B
13087 ></P
13088 ></DD
13089 ><DT
13090 ><A
13091 NAME="OBEYPAMRESTRICTIONS"
13092 ></A
13093 >obey pam restrictions (G)</DT
13094 ><DD
13095 ><P
13096 >When Samba 2.2 is configured to enable PAM support
13097                 (i.e. --with-pam), this parameter will control whether or not Samba
13098                 should obey PAM's account and session management directives.  The
13099                 default behavior is to use PAM for clear text authentication only
13100                 and to ignore any account or session management.  Note that Samba
13101                 always ignores PAM for authentication in the case of <A
13102 HREF="#ENCRYPTPASSWORDS"
13103 ><TT
13104 CLASS="PARAMETER"
13105 ><I
13106 >encrypt passwords = yes</I
13107 ></TT
13108 >
13109                 </A
13110 >.  The reason is that PAM modules cannot support the challenge/response
13111                 authentication mechanism needed in the presence of SMB password encryption.
13112                 </P
13113 ><P
13114 >Default: <B
13115 CLASS="COMMAND"
13116 >obey pam restrictions = no</B
13117 ></P
13118 ></DD
13119 ><DT
13120 ><A
13121 NAME="ONLYUSER"
13122 ></A
13123 >only user (S)</DT
13124 ><DD
13125 ><P
13126 >This is a boolean option that controls whether
13127                 connections with usernames not in the <TT
13128 CLASS="PARAMETER"
13129 ><I
13130 >user</I
13131 ></TT
13132 >
13133                 list will be allowed. By default this option is disabled so that a
13134                 client can supply a username to be used by the server.  Enabling
13135                 this parameter will force the server to only user the login
13136                 names from the <TT
13137 CLASS="PARAMETER"
13138 ><I
13139 >user</I
13140 ></TT
13141 > list and is only really
13142                 useful in <A
13143 HREF="#SECURITYEQUALSSHARE"
13144 >shave level</A
13145 >
13146                 security.</P
13147 ><P
13148 >Note that this also means Samba won't try to deduce
13149                 usernames from the service name. This can be annoying for
13150                 the [homes] section. To get around this you could use <B
13151 CLASS="COMMAND"
13152 >user =
13153                 %S</B
13154 > which means your <TT
13155 CLASS="PARAMETER"
13156 ><I
13157 >user</I
13158 ></TT
13159 > list
13160                 will be just the service name, which for home directories is the
13161                 name of the user.</P
13162 ><P
13163 >See also the <A
13164 HREF="#USER"
13165 ><TT
13166 CLASS="PARAMETER"
13167 ><I
13168 >user</I
13169 ></TT
13170 >
13171                 </A
13172 > parameter.</P
13173 ><P
13174 >Default: <B
13175 CLASS="COMMAND"
13176 >only user = no</B
13177 ></P
13178 ></DD
13179 ><DT
13180 ><A
13181 NAME="ONLYGUEST"
13182 ></A
13183 >only guest (S)</DT
13184 ><DD
13185 ><P
13186 >A synonym for <A
13187 HREF="#GUESTONLY"
13188 ><TT
13189 CLASS="PARAMETER"
13190 ><I
13191 >               guest only</I
13192 ></TT
13193 ></A
13194 >.</P
13195 ></DD
13196 ><DT
13197 ><A
13198 NAME="OPLOCKBREAKWAITTIME"
13199 ></A
13200 >oplock break wait time (G)</DT
13201 ><DD
13202 ><P
13203 >This is a tuning parameter added due to bugs in
13204                 both Windows 9x and WinNT. If Samba responds to a client too
13205                 quickly when that client issues an SMB that can cause an oplock
13206                 break request, then the network client can fail and not respond
13207                 to the break request. This tuning parameter (which is set in milliseconds)
13208                 is the amount of time Samba will wait before sending an oplock break
13209                 request to such (broken) clients.</P
13210 ><P
13211 ><EM
13212 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
13213                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
13214 >.</P
13215 ><P
13216 >Default: <B
13217 CLASS="COMMAND"
13218 >oplock break wait time = 0</B
13219 ></P
13220 ></DD
13221 ><DT
13222 ><A
13223 NAME="OPLOCKCONTENTIONLIMIT"
13224 ></A
13225 >oplock contention limit (S)</DT
13226 ><DD
13227 ><P
13228 >This is a <EM
13229 >very</EM
13230 > advanced
13231                 <A
13232 HREF="smbd.8.html"
13233 TARGET="_top"
13234 >smbd(8)</A
13235 > tuning option to
13236                 improve the efficiency of the granting of oplocks under multiple
13237                 client contention for the same file.</P
13238 ><P
13239 >In brief it specifies a number, which causes <A
13240 HREF="smbd.8.html"
13241 TARGET="_top"
13242 >smbd</A
13243 > not to
13244                 grant an oplock even when requested if the approximate number of
13245                 clients contending for an oplock on the same file goes over this
13246                 limit. This causes <B
13247 CLASS="COMMAND"
13248 >smbd</B
13249 > to behave in a similar
13250                 way to Windows NT.</P
13251 ><P
13252 ><EM
13253 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
13254                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
13255 >.</P
13256 ><P
13257 >Default: <B
13258 CLASS="COMMAND"
13259 >oplock contention limit = 2</B
13260 ></P
13261 ></DD
13262 ><DT
13263 ><A
13264 NAME="OPLOCKS"
13265 ></A
13266 >oplocks (S)</DT
13267 ><DD
13268 ><P
13269 >This boolean option tells <B
13270 CLASS="COMMAND"
13271 >smbd</B
13272 > whether to
13273                 issue oplocks (opportunistic locks) to file open requests on this
13274                 share. The oplock code can dramatically (approx. 30% or more) improve
13275                 the speed of access to files on Samba servers. It allows the clients
13276                 to aggressively cache files locally and you may want to disable this
13277                 option for unreliable network environments (it is turned on by
13278                 default in Windows NT Servers).  For more information see the file
13279                 <TT
13280 CLASS="FILENAME"
13281 >Speed.txt</TT
13282 > in the Samba <TT
13283 CLASS="FILENAME"
13284 >docs/</TT
13285 >
13286                 directory.</P
13287 ><P
13288 >Oplocks may be selectively turned off on certain files with a
13289                 share. See the <A
13290 HREF="#VETOOPLOCKFILES"
13291 ><TT
13292 CLASS="PARAMETER"
13293 ><I
13294 >               veto oplock files</I
13295 ></TT
13296 ></A
13297 > parameter. On some systems
13298                 oplocks are recognized by the underlying operating system. This
13299                 allows data synchronization between all access to oplocked files,
13300                 whether it be via Samba or NFS or a local UNIX process. See the
13301                 <TT
13302 CLASS="PARAMETER"
13303 ><I
13304 >kernel oplocks</I
13305 ></TT
13306 > parameter for details.</P
13307 ><P
13308 >See also the <A
13309 HREF="#KERNELOPLOCKS"
13310 ><TT
13311 CLASS="PARAMETER"
13312 ><I
13313 >kernel
13314                 oplocks</I
13315 ></TT
13316 ></A
13317 > and <A
13318 HREF="#LEVEL2OPLOCKS"
13319 ><TT
13320 CLASS="PARAMETER"
13321 ><I
13322 >               level2 oplocks</I
13323 ></TT
13324 ></A
13325 > parameters.</P
13326 ><P
13327 >Default: <B
13328 CLASS="COMMAND"
13329 >oplocks = yes</B
13330 ></P
13331 ></DD
13332 ><DT
13333 ><A
13334 NAME="OSLEVEL"
13335 ></A
13336 >os level (G)</DT
13337 ><DD
13338 ><P
13339 >This integer value controls what level Samba
13340                 advertises itself as for browse elections. The value of this
13341                 parameter determines whether <A
13342 HREF="nmbd.8.html"
13343 TARGET="_top"
13344 >nmbd(8)</A
13345 >
13346                 has a chance of becoming a local master browser for the <TT
13347 CLASS="PARAMETER"
13348 ><I
13349 >               WORKGROUP</I
13350 ></TT
13351 > in the local broadcast area.</P
13352 ><P
13353 ><EM
13354 >Note :</EM
13355 >By default, Samba will win
13356                 a local master browsing election over all Microsoft operating
13357                 systems except a Windows NT 4.0/2000 Domain Controller.  This
13358                 means that a misconfigured Samba host can effectively isolate
13359                 a subnet for browsing purposes.  See <TT
13360 CLASS="FILENAME"
13361 >BROWSING.txt
13362                 </TT
13363 > in the Samba <TT
13364 CLASS="FILENAME"
13365 >docs/</TT
13366 > directory
13367                 for details.</P
13368 ><P
13369 >Default: <B
13370 CLASS="COMMAND"
13371 >os level = 20</B
13372 ></P
13373 ><P
13374 >Example: <B
13375 CLASS="COMMAND"
13376 >os level = 65 </B
13377 ></P
13378 ></DD
13379 ><DT
13380 ><A
13381 NAME="OS2DRIVERMAP"
13382 ></A
13383 >os2 driver map (G)</DT
13384 ><DD
13385 ><P
13386 >The parameter is used to define the absolute
13387                 path to a file containing a mapping of Windows NT printer driver
13388                 names to OS/2 printer driver names.  The format is:</P
13389 ><P
13390 >&#60;nt driver name&#62; = &#60;os2 driver
13391                 name&#62;.&#60;device name&#62;</P
13392 ><P
13393 >For example, a valid entry using the HP LaserJet 5
13394                 printer driver would appear as <B
13395 CLASS="COMMAND"
13396 >HP LaserJet 5L = LASERJET.HP
13397                 LaserJet 5L</B
13398 >.</P
13399 ><P
13400 >The need for the file is due to the printer driver namespace
13401                 problem described in the <A
13402 HREF="printer_driver2.html"
13403 TARGET="_top"
13404 >Samba
13405                 Printing HOWTO</A
13406 >.  For more details on OS/2 clients, please
13407                 refer to the <A
13408 HREF="OS2-Client-HOWTO.html"
13409 TARGET="_top"
13410 >OS2-Client-HOWTO
13411                 </A
13412 > containing in the Samba documentation.</P
13413 ><P
13414 >Default: <B
13415 CLASS="COMMAND"
13416 >os2 driver map = &#60;empty string&#62;
13417                 </B
13418 ></P
13419 ></DD
13420 ><DT
13421 ><A
13422 NAME="PAMPASSWORDCHANGE"
13423 ></A
13424 >pam password change (G)</DT
13425 ><DD
13426 ><P
13427 >With the addition of better PAM support in Samba 2.2,
13428                 this parameter, it is possible to use PAM's password change control
13429                 flag for Samba.  If enabled, then PAM will be used for password
13430                 changes when requested by an SMB client instead of the program listed in
13431                 <A
13432 HREF="#PASSWDPROGRAM"
13433 ><TT
13434 CLASS="PARAMETER"
13435 ><I
13436 >passwd program</I
13437 ></TT
13438 ></A
13439 >.
13440                 It should be possible to enable this without changing your
13441                 <A
13442 HREF="#PASSWDCHAT"
13443 ><TT
13444 CLASS="PARAMETER"
13445 ><I
13446 >passwd chat</I
13447 ></TT
13448 ></A
13449 >
13450                 parameter for most setups.
13451                 </P
13452 ><P
13453 >Default: <B
13454 CLASS="COMMAND"
13455 >pam password change = no</B
13456 ></P
13457 ></DD
13458 ><DT
13459 ><A
13460 NAME="PANICACTION"
13461 ></A
13462 >panic action (G)</DT
13463 ><DD
13464 ><P
13465 >This is a Samba developer option that allows a
13466                 system command to be called when either <A
13467 HREF="smbd.8.html"
13468 TARGET="_top"
13469 >               smbd(8)</A
13470 > or <A
13471 HREF="nmbd.8.html"
13472 TARGET="_top"
13473 >nmbd(8)</A
13474 >
13475                 crashes. This is usually used to draw attention to the fact that
13476                 a problem occurred.</P
13477 ><P
13478 >Default: <B
13479 CLASS="COMMAND"
13480 >panic action = &#60;empty string&#62;</B
13481 ></P
13482 ><P
13483 >Example: <B
13484 CLASS="COMMAND"
13485 >panic action = "/bin/sleep 90000"</B
13486 ></P
13487 ></DD
13488 ><DT
13489 ><A
13490 NAME="PASSWDCHAT"
13491 ></A
13492 >passwd chat (G)</DT
13493 ><DD
13494 ><P
13495 >This string controls the <EM
13496 >"chat"</EM
13497 >
13498                 conversation that takes places between <A
13499 HREF="smbd.8.html"
13500 TARGET="_top"
13501 >smbd</A
13502 > and the local password changing
13503                 program to change the user's password. The string describes a
13504                 sequence of response-receive pairs that <A
13505 HREF="smbd.8.html"
13506 TARGET="_top"
13507 >               smbd(8)</A
13508 > uses to determine what to send to the
13509                 <A
13510 HREF="#PASSWDPROGRAM"
13511 ><TT
13512 CLASS="PARAMETER"
13513 ><I
13514 >passwd program</I
13515 ></TT
13516 >
13517                 </A
13518 > and what to expect back. If the expected output is not
13519                 received then the password is not changed.</P
13520 ><P
13521 >This chat sequence is often quite site specific, depending
13522                 on what local methods are used for password control (such as NIS
13523                 etc).</P
13524 ><P
13525 >Note that this parameter only is only used if the <A
13526 HREF="#UNIXPASSWORDSYNC"
13527 ><TT
13528 CLASS="PARAMETER"
13529 ><I
13530 >unix
13531                 password sync</I
13532 ></TT
13533 ></A
13534 > parameter is set to <TT
13535 CLASS="CONSTANT"
13536 >yes</TT
13537 >. This
13538                 sequence is then called <EM
13539 >AS ROOT</EM
13540 > when the SMB password
13541                 in the smbpasswd file is being changed, without access to the old
13542                 password cleartext. This means that root must be able to reset the user's password
13543                 without knowing the text of the previous password. In the presence of NIS/YP,
13544                 this means that the <A
13545 HREF="#PASSWDPROGRAM"
13546 >passwd program</A
13547 > must be
13548                 executed on the NIS master.
13549                 </P
13550 ><P
13551 >The string can contain the macro <TT
13552 CLASS="PARAMETER"
13553 ><I
13554 >%n</I
13555 ></TT
13556 > which is substituted
13557                 for the new password.  The chat sequence can also contain the standard
13558                 macros <TT
13559 CLASS="CONSTANT"
13560 >\n</TT
13561 >, <TT
13562 CLASS="CONSTANT"
13563 >\r</TT
13564 >, <TT
13565 CLASS="CONSTANT"
13566 >               \t</TT
13567 > and <TT
13568 CLASS="CONSTANT"
13569 >\s</TT
13570 > to give line-feed,
13571                 carriage-return, tab and space.  The chat sequence string can also contain
13572                 a '*' which matches any sequence of characters.
13573                 Double quotes can be used to collect strings with spaces
13574                 in them into a single string.</P
13575 ><P
13576 >If the send string in any part of the chat sequence
13577                 is a full stop ".",  then no string is sent. Similarly,
13578                 if the expect string is a full stop then no string is expected.</P
13579 ><P
13580 >If the <A
13581 HREF="#PAMPASSWORDCHANGE"
13582 ><TT
13583 CLASS="PARAMETER"
13584 ><I
13585 >pam
13586                 password change</I
13587 ></TT
13588 ></A
13589 > parameter is set to <TT
13590 CLASS="CONSTANT"
13591 >yes</TT
13592 >, the chat pairs
13593                 may be matched in any order, and success is determined by the PAM result,
13594                 not any particular output. The \n macro is ignored for PAM conversions.
13595                 </P
13596 ><P
13597 >See also <A
13598 HREF="#UNIXPASSWORDSYNC"
13599 ><TT
13600 CLASS="PARAMETER"
13601 ><I
13602 >unix password
13603                 sync</I
13604 ></TT
13605 ></A
13606 >, <A
13607 HREF="#PASSWDPROGRAM"
13608 ><TT
13609 CLASS="PARAMETER"
13610 ><I
13611 >               passwd program</I
13612 ></TT
13613 ></A
13614 > ,<A
13615 HREF="#PASSWDCHATDEBUG"
13616 >               <TT
13617 CLASS="PARAMETER"
13618 ><I
13619 >passwd chat debug</I
13620 ></TT
13621 ></A
13622 > and <A
13623 HREF="#PAMPASSWORDCHANGE"
13624 >               <TT
13625 CLASS="PARAMETER"
13626 ><I
13627 >pam password change</I
13628 ></TT
13629 ></A
13630 >.</P
13631 ><P
13632 >Default: <B
13633 CLASS="COMMAND"
13634 >passwd chat = *new*password* %n\n
13635                 *new*password* %n\n *changed*</B
13636 ></P
13637 ><P
13638 >Example: <B
13639 CLASS="COMMAND"
13640 >passwd chat = "*Enter OLD password*" %o\n
13641                 "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password
13642                 changed*"</B
13643 ></P
13644 ></DD
13645 ><DT
13646 ><A
13647 NAME="PASSWDCHATDEBUG"
13648 ></A
13649 >passwd chat debug (G)</DT
13650 ><DD
13651 ><P
13652 >This boolean specifies if the passwd chat script
13653                 parameter is run in <EM
13654 >debug</EM
13655 > mode. In this mode the
13656                 strings passed to and received from the passwd chat are printed
13657                 in the <A
13658 HREF="smbd.8.html"
13659 TARGET="_top"
13660 >smbd(8)</A
13661 > log with a
13662                 <A
13663 HREF="#DEBUGLEVEL"
13664 ><TT
13665 CLASS="PARAMETER"
13666 ><I
13667 >debug level</I
13668 ></TT
13669 ></A
13670 >
13671                 of 100. This is a dangerous option as it will allow plaintext passwords
13672                 to be seen in the <B
13673 CLASS="COMMAND"
13674 >smbd</B
13675 > log. It is available to help
13676                 Samba admins debug their <TT
13677 CLASS="PARAMETER"
13678 ><I
13679 >passwd chat</I
13680 ></TT
13681 > scripts
13682                 when calling the <TT
13683 CLASS="PARAMETER"
13684 ><I
13685 >passwd program</I
13686 ></TT
13687 > and should
13688                 be turned off after this has been done. This option has no effect if the
13689                 <A
13690 HREF="#PAMPASSWORDCHANGE"
13691 ><TT
13692 CLASS="PARAMETER"
13693 ><I
13694 >pam password change</I
13695 ></TT
13696 ></A
13697 >
13698                 paramter is set. This parameter is off by default.</P
13699 ><P
13700 >See also <A
13701 HREF="#PASSWDCHAT"
13702 ><TT
13703 CLASS="PARAMETER"
13704 ><I
13705 >passwd chat</I
13706 ></TT
13707 >
13708                 </A
13709 >, <A
13710 HREF="#PAMPASSWORDCHANGE"
13711 ><TT
13712 CLASS="PARAMETER"
13713 ><I
13714 >pam password change</I
13715 ></TT
13716 >
13717                 </A
13718 >, <A
13719 HREF="#PASSWDPROGRAM"
13720 ><TT
13721 CLASS="PARAMETER"
13722 ><I
13723 >passwd program</I
13724 ></TT
13725 >
13726                 </A
13727 >.</P
13728 ><P
13729 >Default: <B
13730 CLASS="COMMAND"
13731 >passwd chat debug = no</B
13732 ></P
13733 ></DD
13734 ><DT
13735 ><A
13736 NAME="PASSWDPROGRAM"
13737 ></A
13738 >passwd program (G)</DT
13739 ><DD
13740 ><P
13741 >The name of a program that can be used to set
13742                 UNIX user passwords.  Any occurrences of <TT
13743 CLASS="PARAMETER"
13744 ><I
13745 >%u</I
13746 ></TT
13747 >
13748                 will be replaced with the user name. The user name is checked for
13749                 existence before calling the password changing program.</P
13750 ><P
13751 >Also note that many passwd programs insist in <EM
13752 >reasonable
13753                 </EM
13754 > passwords, such as a minimum length, or the inclusion
13755                 of mixed case chars and digits. This can pose a problem as some clients
13756                 (such as Windows for Workgroups) uppercase the password before sending
13757                 it.</P
13758 ><P
13759 ><EM
13760 >Note</EM
13761 > that if the <TT
13762 CLASS="PARAMETER"
13763 ><I
13764 >unix
13765                 password sync</I
13766 ></TT
13767 > parameter is set to <TT
13768 CLASS="CONSTANT"
13769 >yes
13770                 </TT
13771 > then this program is called <EM
13772 >AS ROOT</EM
13773 >
13774                 before the SMB password in the <A
13775 HREF="smbpasswd.5.html"
13776 TARGET="_top"
13777 >smbpasswd(5)
13778                 </A
13779 > file is changed. If this UNIX password change fails, then
13780                 <B
13781 CLASS="COMMAND"
13782 >smbd</B
13783 > will fail to change the SMB password also
13784                 (this is by design).</P
13785 ><P
13786 >If the <TT
13787 CLASS="PARAMETER"
13788 ><I
13789 >unix password sync</I
13790 ></TT
13791 > parameter
13792                 is set this parameter <EM
13793 >MUST USE ABSOLUTE PATHS</EM
13794 >
13795                 for <EM
13796 >ALL</EM
13797 > programs called, and must be examined
13798                 for security implications. Note that by default <TT
13799 CLASS="PARAMETER"
13800 ><I
13801 >unix
13802                 password sync</I
13803 ></TT
13804 > is set to <TT
13805 CLASS="CONSTANT"
13806 >no</TT
13807 >.</P
13808 ><P
13809 >See also <A
13810 HREF="#UNIXPASSWORDSYNC"
13811 ><TT
13812 CLASS="PARAMETER"
13813 ><I
13814 >unix
13815                 password sync</I
13816 ></TT
13817 ></A
13818 >.</P
13819 ><P
13820 >Default: <B
13821 CLASS="COMMAND"
13822 >passwd program = /bin/passwd</B
13823 ></P
13824 ><P
13825 >Example: <B
13826 CLASS="COMMAND"
13827 >passwd program = /sbin/npasswd %u</B
13828 >
13829                 </P
13830 ></DD
13831 ><DT
13832 ><A
13833 NAME="PASSWORDLEVEL"
13834 ></A
13835 >password level (G)</DT
13836 ><DD
13837 ><P
13838 >Some client/server combinations have difficulty
13839                 with mixed-case passwords.  One offending client is Windows for
13840                 Workgroups, which for some reason forces passwords to upper
13841                 case when using the LANMAN1 protocol, but leaves them alone when
13842                 using COREPLUS!  Another problem child is the Windows 95/98
13843                 family of operating systems.  These clients upper case clear
13844                 text passwords even when NT LM 0.12 selected by the protocol
13845                 negotiation request/response.</P
13846 ><P
13847 >This parameter defines the maximum number of characters
13848                 that may be upper case in passwords.</P
13849 ><P
13850 >For example, say the password given was "FRED". If <TT
13851 CLASS="PARAMETER"
13852 ><I
13853 >               password level</I
13854 ></TT
13855 > is set to 1, the following combinations
13856                 would be tried if "FRED" failed:</P
13857 ><P
13858 >"Fred", "fred", "fRed", "frEd","freD"</P
13859 ><P
13860 >If <TT
13861 CLASS="PARAMETER"
13862 ><I
13863 >password level</I
13864 ></TT
13865 > was set to 2,
13866                 the following combinations would also be tried: </P
13867 ><P
13868 >"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</P
13869 ><P
13870 >And so on.</P
13871 ><P
13872 >The higher value this parameter is set to the more likely
13873                 it is that a mixed case password will be matched against a single
13874                 case password. However, you should be aware that use of this
13875                 parameter reduces security and increases the time taken to
13876                 process a new connection.</P
13877 ><P
13878 >A value of zero will cause only two attempts to be
13879                 made - the password as is and the password in all-lower case.</P
13880 ><P
13881 >Default: <B
13882 CLASS="COMMAND"
13883 >password level = 0</B
13884 ></P
13885 ><P
13886 >Example: <B
13887 CLASS="COMMAND"
13888 >password level = 4</B
13889 ></P
13890 ></DD
13891 ><DT
13892 ><A
13893 NAME="PASSWORDSERVER"
13894 ></A
13895 >password server (G)</DT
13896 ><DD
13897 ><P
13898 >By specifying the name of another SMB server (such
13899                 as a WinNT box) with this option, and using <B
13900 CLASS="COMMAND"
13901 >security = domain
13902                 </B
13903 > or <B
13904 CLASS="COMMAND"
13905 >security = server</B
13906 > you can get Samba
13907                 to do all its username/password validation via a remote server.</P
13908 ><P
13909 >This option sets the name of the password server to use.
13910                 It must be a NetBIOS name, so if the machine's NetBIOS name is
13911                 different from its Internet name then you may have to add its NetBIOS
13912                 name to the lmhosts  file which is stored in the same directory
13913                 as the <TT
13914 CLASS="FILENAME"
13915 >smb.conf</TT
13916 > file.</P
13917 ><P
13918 >The name of the password server is looked up using the
13919                 parameter <A
13920 HREF="#NAMERESOLVEORDER"
13921 ><TT
13922 CLASS="PARAMETER"
13923 ><I
13924 >name
13925                 resolve order</I
13926 ></TT
13927 ></A
13928 > and so may resolved
13929                 by any method and order described in that parameter.</P
13930 ><P
13931 >The password server much be a machine capable of using
13932                 the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in
13933                 user level security mode.</P
13934 ><P
13935 ><EM
13936 >NOTE:</EM
13937 > Using a password server
13938                 means your UNIX box (running Samba) is only as secure as your
13939                 password server. <EM
13940 >DO NOT CHOOSE A PASSWORD SERVER THAT
13941                 YOU DON'T COMPLETELY TRUST</EM
13942 >.</P
13943 ><P
13944 >Never point a Samba server at itself for password
13945                 serving. This will cause a loop and could lock up your Samba
13946                 server!</P
13947 ><P
13948 >The name of the password server takes the standard
13949                 substitutions, but probably the only useful one is <TT
13950 CLASS="PARAMETER"
13951 ><I
13952 >%m
13953                 </I
13954 ></TT
13955 >, which means the Samba server will use the incoming
13956                 client as the password server. If you use this then you better
13957                 trust your clients, and you had better restrict them with hosts allow!</P
13958 ><P
13959 >If the <TT
13960 CLASS="PARAMETER"
13961 ><I
13962 >security</I
13963 ></TT
13964 > parameter is set to
13965                 <TT
13966 CLASS="CONSTANT"
13967 >domain</TT
13968 >, then the list of machines in this
13969                 option must be a list of Primary or Backup Domain controllers for the
13970                 Domain or the character '*', as the Samba server is effectively
13971                 in that domain, and will use cryptographically authenticated RPC calls
13972                 to authenticate the user logging on. The advantage of using <B
13973 CLASS="COMMAND"
13974 >               security = domain</B
13975 > is that if you list several hosts in the
13976                 <TT
13977 CLASS="PARAMETER"
13978 ><I
13979 >password server</I
13980 ></TT
13981 > option then <B
13982 CLASS="COMMAND"
13983 >smbd
13984                 </B
13985 > will try each in turn till it finds one that responds. This
13986                 is useful in case your primary server goes down.</P
13987 ><P
13988 >If the <TT
13989 CLASS="PARAMETER"
13990 ><I
13991 >password server</I
13992 ></TT
13993 > option is set
13994                 to the character '*', then Samba will attempt to auto-locate the
13995                 Primary or Backup Domain controllers to authenticate against by
13996                 doing a query for the name <TT
13997 CLASS="CONSTANT"
13998 >WORKGROUP&#60;1C&#62;</TT
13999 >
14000                 and then contacting each server returned in the list of IP
14001                 addresses from the name resolution source. </P
14002 ><P
14003 >If the <TT
14004 CLASS="PARAMETER"
14005 ><I
14006 >security</I
14007 ></TT
14008 > parameter is
14009                 set to <TT
14010 CLASS="CONSTANT"
14011 >server</TT
14012 >, then there are different
14013                 restrictions that <B
14014 CLASS="COMMAND"
14015 >security = domain</B
14016 > doesn't
14017                 suffer from:</P
14018 ><P
14019 ></P
14020 ><UL
14021 ><LI
14022 ><P
14023 >You may list several password servers in
14024                         the <TT
14025 CLASS="PARAMETER"
14026 ><I
14027 >password server</I
14028 ></TT
14029 > parameter, however if an
14030                         <B
14031 CLASS="COMMAND"
14032 >smbd</B
14033 > makes a connection to a password server,
14034                         and then the password server fails, no more users will be able
14035                         to be authenticated from this <B
14036 CLASS="COMMAND"
14037 >smbd</B
14038 >.  This is a
14039                         restriction of the SMB/CIFS protocol when in <B
14040 CLASS="COMMAND"
14041 >security = server
14042                         </B
14043 > mode and cannot be fixed in Samba.</P
14044 ></LI
14045 ><LI
14046 ><P
14047 >If you are using a Windows NT server as your
14048                         password server then you will have to ensure that your users
14049                         are able to login from the Samba server, as when in <B
14050 CLASS="COMMAND"
14051 >                       security = server</B
14052 >  mode the network logon will appear to
14053                         come from there rather than from the users workstation.</P
14054 ></LI
14055 ></UL
14056 ><P
14057 >See also the <A
14058 HREF="#SECURITY"
14059 ><TT
14060 CLASS="PARAMETER"
14061 ><I
14062 >security
14063                 </I
14064 ></TT
14065 ></A
14066 > parameter.</P
14067 ><P
14068 >Default: <B
14069 CLASS="COMMAND"
14070 >password server = &#60;empty string&#62;</B
14071 >
14072                 </P
14073 ><P
14074 >Example: <B
14075 CLASS="COMMAND"
14076 >password server = NT-PDC, NT-BDC1, NT-BDC2
14077                 </B
14078 ></P
14079 ><P
14080 >Example: <B
14081 CLASS="COMMAND"
14082 >password server = *</B
14083 ></P
14084 ></DD
14085 ><DT
14086 ><A
14087 NAME="PATH"
14088 ></A
14089 >path (S)</DT
14090 ><DD
14091 ><P
14092 >This parameter specifies a directory to which
14093                 the user of the service is to be given access. In the case of
14094                 printable services, this is where print data will spool prior to
14095                 being submitted to the host for printing.</P
14096 ><P
14097 >For a printable service offering guest access, the service
14098                 should be readonly and the path should be world-writeable and
14099                 have the sticky bit set. This is not mandatory of course, but
14100                 you probably won't get the results you expect if you do
14101                 otherwise.</P
14102 ><P
14103 >Any occurrences of <TT
14104 CLASS="PARAMETER"
14105 ><I
14106 >%u</I
14107 ></TT
14108 > in the path
14109                 will be replaced with the UNIX username that the client is using
14110                 on this connection. Any occurrences of <TT
14111 CLASS="PARAMETER"
14112 ><I
14113 >%m</I
14114 ></TT
14115 >
14116                 will be replaced by the NetBIOS name of the machine they are
14117                 connecting from. These replacements are very useful for setting
14118                 up pseudo home directories for users.</P
14119 ><P
14120 >Note that this path will be based on <A
14121 HREF="#ROOTDIR"
14122 >               <TT
14123 CLASS="PARAMETER"
14124 ><I
14125 >root dir</I
14126 ></TT
14127 ></A
14128 > if one was specified.</P
14129 ><P
14130 >Default: <EM
14131 >none</EM
14132 ></P
14133 ><P
14134 >Example: <B
14135 CLASS="COMMAND"
14136 >path = /home/fred</B
14137 ></P
14138 ></DD
14139 ><DT
14140 ><A
14141 NAME="PIDDIRECTORY"
14142 ></A
14143 >pid directory (G)</DT
14144 ><DD
14145 ><P
14146 >This option specifies the directory where pid
14147                 files will be placed.  </P
14148 ><P
14149 >Default: <B
14150 CLASS="COMMAND"
14151 >pid directory = ${prefix}/var/locks</B
14152 ></P
14153 ><P
14154 >Example: <B
14155 CLASS="COMMAND"
14156 >pid directory = /var/run/</B
14157 >
14158                 </P
14159 ></DD
14160 ><DT
14161 ><A
14162 NAME="POSIXLOCKING"
14163 ></A
14164 >posix locking (S)</DT
14165 ><DD
14166 ><P
14167 >The <A
14168 HREF="smbd.8.html"
14169 TARGET="_top"
14170 ><B
14171 CLASS="COMMAND"
14172 >smbd(8)</B
14173 ></A
14174 >
14175                 daemon maintains an database of file locks obtained by SMB clients.
14176                 The default behavior is to map this internal database to POSIX
14177                 locks.  This means that file locks obtained by SMB clients are
14178                 consistent with those seen by POSIX compliant applications accessing
14179                 the files via a non-SMB method (e.g. NFS or local file access).
14180                 You should never need to disable this parameter.</P
14181 ><P
14182 >Default: <B
14183 CLASS="COMMAND"
14184 >posix locking = yes</B
14185 ></P
14186 ></DD
14187 ><DT
14188 ><A
14189 NAME="POSTEXEC"
14190 ></A
14191 >postexec (S)</DT
14192 ><DD
14193 ><P
14194 >This option specifies a command to be run
14195                 whenever the service is disconnected. It takes the usual
14196                 substitutions. The command may be run as the root on some
14197                 systems.</P
14198 ><P
14199 >An interesting example may be to unmount server
14200                 resources:</P
14201 ><P
14202 ><B
14203 CLASS="COMMAND"
14204 >postexec = /etc/umount /cdrom</B
14205 ></P
14206 ><P
14207 >See also <A
14208 HREF="#PREEXEC"
14209 ><TT
14210 CLASS="PARAMETER"
14211 ><I
14212 >preexec</I
14213 ></TT
14214 >
14215                 </A
14216 >.</P
14217 ><P
14218 >Default: <EM
14219 >none (no command executed)</EM
14220 >
14221                 </P
14222 ><P
14223 >Example: <B
14224 CLASS="COMMAND"
14225 >postexec = echo \"%u disconnected from %S
14226                 from %m (%I)\" &#62;&#62; /tmp/log</B
14227 ></P
14228 ></DD
14229 ><DT
14230 ><A
14231 NAME="POSTSCRIPT"
14232 ></A
14233 >postscript (S)</DT
14234 ><DD
14235 ><P
14236 >This parameter forces a printer to interpret
14237                 the print files as PostScript. This is done by adding a <TT
14238 CLASS="CONSTANT"
14239 >%!
14240                 </TT
14241 > to the start of print output.</P
14242 ><P
14243 >This is most useful when you have lots of PCs that persist
14244                 in putting a control-D at the start of print jobs, which then
14245                 confuses your printer.</P
14246 ><P
14247 >Default: <B
14248 CLASS="COMMAND"
14249 >postscript = no</B
14250 ></P
14251 ></DD
14252 ><DT
14253 ><A
14254 NAME="PREEXEC"
14255 ></A
14256 >preexec (S)</DT
14257 ><DD
14258 ><P
14259 >This option specifies a command to be run whenever
14260                 the service is connected to. It takes the usual substitutions.</P
14261 ><P
14262 >An interesting example is to send the users a welcome
14263                 message every time they log in. Maybe a message of the day? Here
14264                 is an example:</P
14265 ><P
14266 ><B
14267 CLASS="COMMAND"
14268 >preexec = csh -c 'echo \"Welcome to %S!\" |
14269                  /usr/local/samba/bin/smbclient -M %m -I %I' &#38; </B
14270 ></P
14271 ><P
14272 >Of course, this could get annoying after a while :-)</P
14273 ><P
14274 >See also <A
14275 HREF="#PREEXECCLOSE"
14276 ><TT
14277 CLASS="PARAMETER"
14278 ><I
14279 >preexec close
14280                 </I
14281 ></TT
14282 ></A
14283 > and <A
14284 HREF="#POSTEXEC"
14285 ><TT
14286 CLASS="PARAMETER"
14287 ><I
14288 >postexec
14289                 </I
14290 ></TT
14291 ></A
14292 >.</P
14293 ><P
14294 >Default: <EM
14295 >none (no command executed)</EM
14296 ></P
14297 ><P
14298 >Example: <B
14299 CLASS="COMMAND"
14300 >preexec = echo \"%u connected to %S from %m
14301                 (%I)\" &#62;&#62; /tmp/log</B
14302 ></P
14303 ></DD
14304 ><DT
14305 ><A
14306 NAME="PREEXECCLOSE"
14307 ></A
14308 >preexec close (S)</DT
14309 ><DD
14310 ><P
14311 >This boolean option controls whether a non-zero
14312                 return code from <A
14313 HREF="#PREEXEC"
14314 ><TT
14315 CLASS="PARAMETER"
14316 ><I
14317 >preexec
14318                 </I
14319 ></TT
14320 ></A
14321 > should close the service being connected to.</P
14322 ><P
14323 >Default: <B
14324 CLASS="COMMAND"
14325 >preexec close = no</B
14326 ></P
14327 ></DD
14328 ><DT
14329 ><A
14330 NAME="PREFERREDMASTER"
14331 ></A
14332 >preferred master (G)</DT
14333 ><DD
14334 ><P
14335 >This boolean parameter controls if <A
14336 HREF="nmbd.8.html"
14337 TARGET="_top"
14338 >nmbd(8)</A
14339 > is a preferred master browser
14340                 for its workgroup.</P
14341 ><P
14342 >If this is set to <TT
14343 CLASS="CONSTANT"
14344 >yes</TT
14345 >, on startup, <B
14346 CLASS="COMMAND"
14347 >nmbd</B
14348 >
14349                 will force an election, and it will have a slight advantage in
14350                 winning the election.  It is recommended that this parameter is
14351                 used in conjunction with <B
14352 CLASS="COMMAND"
14353 ><A
14354 HREF="#DOMAINMASTER"
14355 ><TT
14356 CLASS="PARAMETER"
14357 ><I
14358 >               domain master</I
14359 ></TT
14360 ></A
14361 > = yes</B
14362 >, so that <B
14363 CLASS="COMMAND"
14364 >               nmbd</B
14365 > can guarantee becoming a domain master.</P
14366 ><P
14367 >Use this option with caution, because if there are several
14368                 hosts (whether Samba servers, Windows 95 or NT) that are preferred
14369                 master browsers on the same subnet, they will each periodically
14370                 and continuously attempt to become the local master browser.
14371                 This will result in unnecessary broadcast traffic and reduced browsing
14372                 capabilities.</P
14373 ><P
14374 >See also <A
14375 HREF="#OSLEVEL"
14376 ><TT
14377 CLASS="PARAMETER"
14378 ><I
14379 >os level</I
14380 ></TT
14381 >
14382                 </A
14383 >.</P
14384 ><P
14385 >Default: <B
14386 CLASS="COMMAND"
14387 >preferred master = auto</B
14388 ></P
14389 ></DD
14390 ><DT
14391 ><A
14392 NAME="PREFEREDMASTER"
14393 ></A
14394 >prefered master (G)</DT
14395 ><DD
14396 ><P
14397 >Synonym for <A
14398 HREF="#PREFERREDMASTER"
14399 ><TT
14400 CLASS="PARAMETER"
14401 ><I
14402 >               preferred master</I
14403 ></TT
14404 ></A
14405 > for people who cannot spell :-).</P
14406 ></DD
14407 ><DT
14408 ><A
14409 NAME="PRELOAD"
14410 ></A
14411 >preload</DT
14412 ><DD
14413 ><P
14414 >This is a list of services that you want to be
14415                 automatically added to the browse lists. This is most useful
14416                 for homes and printers services that would otherwise not be
14417                 visible.</P
14418 ><P
14419 >Note that if you just want all printers in your
14420                 printcap file loaded then the <A
14421 HREF="#LOADPRINTERS"
14422 >               <TT
14423 CLASS="PARAMETER"
14424 ><I
14425 >load printers</I
14426 ></TT
14427 ></A
14428 > option is easier.</P
14429 ><P
14430 >Default: <EM
14431 >no preloaded services</EM
14432 ></P
14433 ><P
14434 >Example: <B
14435 CLASS="COMMAND"
14436 >preload = fred lp colorlp</B
14437 ></P
14438 ></DD
14439 ><DT
14440 ><A
14441 NAME="PRESERVECASE"
14442 ></A
14443 >preserve case (S)</DT
14444 ><DD
14445 ><P
14446 > This controls if new filenames are created
14447                 with the case that the client passes, or if they are forced to
14448                 be the <A
14449 HREF="#DEFAULTCASE"
14450 ><TT
14451 CLASS="PARAMETER"
14452 ><I
14453 >default case
14454                 </I
14455 ></TT
14456 ></A
14457 >.</P
14458 ><P
14459 >Default: <B
14460 CLASS="COMMAND"
14461 >preserve case = yes</B
14462 ></P
14463 ><P
14464 >See the section on <A
14465 HREF="#AEN203"
14466 >NAME
14467                 MANGLING</A
14468 > for a fuller discussion.</P
14469 ></DD
14470 ><DT
14471 ><A
14472 NAME="PRINTCOMMAND"
14473 ></A
14474 >print command (S)</DT
14475 ><DD
14476 ><P
14477 >After a print job has finished spooling to
14478                 a service, this command will be used via a <B
14479 CLASS="COMMAND"
14480 >system()</B
14481 >
14482                 call to process the spool file. Typically the command specified will
14483                 submit the spool file to the host's printing subsystem, but there
14484                 is no requirement that this be the case. The server will not remove
14485                 the spool file, so whatever command you specify should remove the
14486                 spool file when it has been processed, otherwise you will need to
14487                 manually remove old spool files.</P
14488 ><P
14489 >The print command is simply a text string. It will be used
14490                 verbatim after macro substitutions have been made:</P
14491 ><P
14492 >s, %p - the path to the spool
14493                 file name</P
14494 ><P
14495 >%p - the appropriate printer
14496                 name</P
14497 ><P
14498 >%J - the job
14499                 name as transmitted by the client.</P
14500 ><P
14501 >%c - The number of printed pages
14502                 of the spooled job (if known).</P
14503 ><P
14504 >%z - the size of the spooled
14505                 print job (in bytes)</P
14506 ><P
14507 >The print command <EM
14508 >MUST</EM
14509 > contain at least
14510                 one occurrence of <TT
14511 CLASS="PARAMETER"
14512 ><I
14513 >%s</I
14514 ></TT
14515 > or <TT
14516 CLASS="PARAMETER"
14517 ><I
14518 >%f
14519                 </I
14520 ></TT
14521 > - the <TT
14522 CLASS="PARAMETER"
14523 ><I
14524 >%p</I
14525 ></TT
14526 > is optional. At the time
14527                 a job is submitted, if no printer name is supplied the <TT
14528 CLASS="PARAMETER"
14529 ><I
14530 >%p
14531                 </I
14532 ></TT
14533 > will be silently removed from the printer command.</P
14534 ><P
14535 >If specified in the [global] section, the print command given
14536                 will be used for any printable service that does not have its own
14537                 print command specified.</P
14538 ><P
14539 >If there is neither a specified print command for a
14540                 printable service nor a global print command, spool files will
14541                 be created but not processed and (most importantly) not removed.</P
14542 ><P
14543 >Note that printing may fail on some UNIXes from the
14544                 <TT
14545 CLASS="CONSTANT"
14546 >nobody</TT
14547 > account. If this happens then create
14548                 an alternative guest account that can print and set the <A
14549 HREF="#GUESTACCOUNT"
14550 ><TT
14551 CLASS="PARAMETER"
14552 ><I
14553 >guest account</I
14554 ></TT
14555 ></A
14556 >
14557                 in the [global] section.</P
14558 ><P
14559 >You can form quite complex print commands by realizing
14560                 that they are just passed to a shell. For example the following
14561                 will log a print job, print the file, then remove it. Note that
14562                 ';' is the usual separator for command in shell scripts.</P
14563 ><P
14564 ><B
14565 CLASS="COMMAND"
14566 >print command = echo Printing %s &#62;&#62;
14567                 /tmp/print.log; lpr -P %p %s; rm %s</B
14568 ></P
14569 ><P
14570 >You may have to vary this command considerably depending
14571                 on how you normally print files on your system. The default for
14572                 the parameter varies depending on the setting of the <A
14573 HREF="#PRINTING"
14574 >               <TT
14575 CLASS="PARAMETER"
14576 ><I
14577 >printing</I
14578 ></TT
14579 ></A
14580 > parameter.</P
14581 ><P
14582 >Default: For <B
14583 CLASS="COMMAND"
14584 >printing = BSD, AIX, QNX, LPRNG
14585                 or PLP :</B
14586 ></P
14587 ><P
14588 ><B
14589 CLASS="COMMAND"
14590 >print command = lpr -r -P%p %s</B
14591 ></P
14592 ><P
14593 >For <B
14594 CLASS="COMMAND"
14595 >printing = SYSV or HPUX :</B
14596 ></P
14597 ><P
14598 ><B
14599 CLASS="COMMAND"
14600 >print command = lp -c -d%p %s; rm %s</B
14601 ></P
14602 ><P
14603 >For <B
14604 CLASS="COMMAND"
14605 >printing = SOFTQ :</B
14606 ></P
14607 ><P
14608 ><B
14609 CLASS="COMMAND"
14610 >print command = lp -d%p -s %s; rm %s</B
14611 ></P
14612 ><P
14613 >For printing = CUPS :   If SAMBA is compiled against
14614                 libcups, then <A
14615 HREF="#PRINTING"
14616 >printcap = cups</A
14617 >
14618                 uses the CUPS API to
14619                 submit jobs, etc.  Otherwise it maps to the System V
14620                 commands with the -oraw option for printing, i.e. it
14621                 uses <B
14622 CLASS="COMMAND"
14623 >lp -c -d%p -oraw; rm %s</B
14624 >.
14625                 With <B
14626 CLASS="COMMAND"
14627 >printing = cups</B
14628 >,
14629                 and if SAMBA is compiled against libcups, any manually
14630                 set print command will be ignored.</P
14631 ><P
14632 >Example: <B
14633 CLASS="COMMAND"
14634 >print command = /usr/local/samba/bin/myprintscript
14635                 %p %s</B
14636 ></P
14637 ></DD
14638 ><DT
14639 ><A
14640 NAME="PRINTOK"
14641 ></A
14642 >print ok (S)</DT
14643 ><DD
14644 ><P
14645 >Synonym for <A
14646 HREF="#PRINTABLE"
14647 >               <TT
14648 CLASS="PARAMETER"
14649 ><I
14650 >printable</I
14651 ></TT
14652 ></A
14653 >.</P
14654 ></DD
14655 ><DT
14656 ><A
14657 NAME="PRINTABLE"
14658 ></A
14659 >printable (S)</DT
14660 ><DD
14661 ><P
14662 >If this parameter is <TT
14663 CLASS="CONSTANT"
14664 >yes</TT
14665 >, then
14666                 clients may open, write to and submit spool files on the directory
14667                 specified for the service. </P
14668 ><P
14669 >Note that a printable service will ALWAYS allow writing
14670                 to the service path (user privileges permitting) via the spooling
14671                 of print data. The <A
14672 HREF="#READONLY"
14673 ><TT
14674 CLASS="PARAMETER"
14675 ><I
14676 >read only
14677                 </I
14678 ></TT
14679 ></A
14680 > parameter controls only non-printing access to
14681                 the resource.</P
14682 ><P
14683 >Default: <B
14684 CLASS="COMMAND"
14685 >printable = no</B
14686 ></P
14687 ></DD
14688 ><DT
14689 ><A
14690 NAME="PRINTCAP"
14691 ></A
14692 >printcap (G)</DT
14693 ><DD
14694 ><P
14695 >Synonym for    <A
14696 HREF="#PRINTCAPNAME"
14697 ><TT
14698 CLASS="PARAMETER"
14699 ><I
14700 >               printcap name</I
14701 ></TT
14702 ></A
14703 >.</P
14704 ></DD
14705 ><DT
14706 ><A
14707 NAME="PRINTCAPNAME"
14708 ></A
14709 >printcap name (G)</DT
14710 ><DD
14711 ><P
14712 >This parameter may be used to override the
14713                 compiled-in default printcap name used by the server (usually <TT
14714 CLASS="FILENAME"
14715 >               /etc/printcap</TT
14716 >). See the discussion of the <A
14717 HREF="#AEN79"
14718 >[printers]</A
14719 > section above for reasons
14720                 why you might want to do this.</P
14721 ><P
14722 >To use the CUPS printing interface set <B
14723 CLASS="COMMAND"
14724 >printcap name = cups
14725                 </B
14726 >. This should be supplemented by an addtional setting
14727                 <A
14728 HREF="#PRINTING"
14729 >printing = cups</A
14730 > in the [global]
14731                 section.  <B
14732 CLASS="COMMAND"
14733 >printcap name = cups</B
14734 > will use the
14735                 "dummy" printcap created by CUPS, as specified in your CUPS
14736                 configuration file.
14737                 </P
14738 ><P
14739 >On System V systems that use <B
14740 CLASS="COMMAND"
14741 >lpstat</B
14742 > to
14743                 list available printers you can use <B
14744 CLASS="COMMAND"
14745 >printcap name = lpstat
14746                 </B
14747 > to automatically obtain lists of available printers. This
14748                 is the default for systems that define SYSV at configure time in
14749                 Samba (this includes most System V based systems). If <TT
14750 CLASS="PARAMETER"
14751 ><I
14752 >               printcap name</I
14753 ></TT
14754 > is set to <B
14755 CLASS="COMMAND"
14756 >lpstat</B
14757 > on
14758                 these systems then Samba will launch <B
14759 CLASS="COMMAND"
14760 >lpstat -v</B
14761 > and
14762                 attempt to parse the output to obtain a printer list.</P
14763 ><P
14764 >A minimal printcap file would look something like this:</P
14765 ><P
14766 ><TABLE
14767 BORDER="0"
14768 BGCOLOR="#E0E0E0"
14769 WIDTH="90%"
14770 ><TR
14771 ><TD
14772 ><PRE
14773 CLASS="PROGRAMLISTING"
14774 >               print1|My Printer 1
14775                 print2|My Printer 2
14776                 print3|My Printer 3
14777                 print4|My Printer 4
14778                 print5|My Printer 5
14779                 </PRE
14780 ></TD
14781 ></TR
14782 ></TABLE
14783 ></P
14784 ><P
14785 >where the '|' separates aliases of a printer. The fact
14786                 that the second alias has a space in it gives a hint to Samba
14787                 that it's a comment.</P
14788 ><P
14789 ><EM
14790 >NOTE</EM
14791 >: Under AIX the default printcap
14792                 name is <TT
14793 CLASS="FILENAME"
14794 >/etc/qconfig</TT
14795 >. Samba will assume the
14796                 file is in AIX <TT
14797 CLASS="FILENAME"
14798 >qconfig</TT
14799 > format if the string
14800                 <TT
14801 CLASS="FILENAME"
14802 >qconfig</TT
14803 > appears in the printcap filename.</P
14804 ><P
14805 >Default: <B
14806 CLASS="COMMAND"
14807 >printcap name = /etc/printcap</B
14808 ></P
14809 ><P
14810 >Example: <B
14811 CLASS="COMMAND"
14812 >printcap name = /etc/myprintcap</B
14813 ></P
14814 ></DD
14815 ><DT
14816 ><A
14817 NAME="PRINTERADMIN"
14818 ></A
14819 >printer admin (S)</DT
14820 ><DD
14821 ><P
14822 >This is a list of users that can do anything to
14823                 printers via the remote administration interfaces offered by MS-RPC
14824                 (usually using a NT workstation). Note that the root user always
14825                 has admin rights.</P
14826 ><P
14827 >Default: <B
14828 CLASS="COMMAND"
14829 >printer admin = &#60;empty string&#62;</B
14830 >
14831                 </P
14832 ><P
14833 >Example: <B
14834 CLASS="COMMAND"
14835 >printer admin = admin, @staff</B
14836 ></P
14837 ></DD
14838 ><DT
14839 ><A
14840 NAME="PRINTERDRIVER"
14841 ></A
14842 >printer driver (S)</DT
14843 ><DD
14844 ><P
14845 ><EM
14846 >Note :</EM
14847 >This is a deprecated
14848                 parameter and will be removed in the next major release
14849                 following version 2.2.  Please see the instructions in
14850                 the <A
14851 HREF="printer_driver2.html"
14852 TARGET="_top"
14853 >Samba 2.2. Printing
14854                 HOWTO</A
14855 > for more information
14856                 on the new method of loading printer drivers onto a Samba server.
14857                 </P
14858 ><P
14859 >This option allows you to control the string
14860                 that clients receive when they ask the server for the printer driver
14861                 associated with a printer. If you are using Windows95 or Windows NT
14862                 then you can use this to automate the setup of printers on your
14863                 system.</P
14864 ><P
14865 >You need to set this parameter to the exact string (case
14866                 sensitive) that describes the appropriate printer driver for your
14867                 system. If you don't know the exact string to use then you should
14868                 first try with no <A
14869 HREF="#PRINTERDRIVER"
14870 ><TT
14871 CLASS="PARAMETER"
14872 ><I
14873 >               printer driver</I
14874 ></TT
14875 ></A
14876 > option set and the client will
14877                 give you a list of printer drivers. The appropriate strings are
14878                 shown in a scroll box after you have chosen the printer manufacturer.</P
14879 ><P
14880 >See also <A
14881 HREF="#PRINTERDRIVERFILE"
14882 ><TT
14883 CLASS="PARAMETER"
14884 ><I
14885 >printer
14886                 driver file</I
14887 ></TT
14888 ></A
14889 >.</P
14890 ><P
14891 >Example: <B
14892 CLASS="COMMAND"
14893 >printer driver = HP LaserJet 4L</B
14894 ></P
14895 ></DD
14896 ><DT
14897 ><A
14898 NAME="PRINTERDRIVERFILE"
14899 ></A
14900 >printer driver file (G)</DT
14901 ><DD
14902 ><P
14903 ><EM
14904 >Note :</EM
14905 >This is a deprecated
14906                 parameter and will be removed in the next major release
14907                 following version 2.2.  Please see the instructions in
14908                 the <A
14909 HREF="printer_driver2.html"
14910 TARGET="_top"
14911 >Samba 2.2. Printing
14912                 HOWTO</A
14913 > for more information
14914                 on the new method of loading printer drivers onto a Samba server.
14915                 </P
14916 ><P
14917 >This parameter tells Samba where the printer driver
14918                 definition file, used when serving drivers to Windows 95 clients, is
14919                 to be found. If this is not set, the default is :</P
14920 ><P
14921 ><TT
14922 CLASS="FILENAME"
14923 ><TT
14924 CLASS="REPLACEABLE"
14925 ><I
14926 >SAMBA_INSTALL_DIRECTORY</I
14927 ></TT
14928 >
14929                 /lib/printers.def</TT
14930 ></P
14931 ><P
14932 >This file is created from Windows 95 <TT
14933 CLASS="FILENAME"
14934 >msprint.inf
14935                 </TT
14936 > files found on the Windows 95 client system. For more
14937                 details on setting up serving of printer drivers to Windows 95
14938                 clients, see the outdated documentation file in the <TT
14939 CLASS="FILENAME"
14940 >docs/</TT
14941 >
14942                 directory, <TT
14943 CLASS="FILENAME"
14944 >PRINTER_DRIVER.txt</TT
14945 >.</P
14946 ><P
14947 >See also <A
14948 HREF="#PRINTERDRIVERLOCATION"
14949 ><TT
14950 CLASS="PARAMETER"
14951 ><I
14952 >               printer driver location</I
14953 ></TT
14954 ></A
14955 >.</P
14956 ><P
14957 >Default: <EM
14958 >None (set in compile).</EM
14959 ></P
14960 ><P
14961 >Example: <B
14962 CLASS="COMMAND"
14963 >printer driver file =
14964                 /usr/local/samba/printers/drivers.def</B
14965 ></P
14966 ></DD
14967 ><DT
14968 ><A
14969 NAME="PRINTERDRIVERLOCATION"
14970 ></A
14971 >printer driver location (S)</DT
14972 ><DD
14973 ><P
14974 ><EM
14975 >Note :</EM
14976 >This is a deprecated
14977                 parameter and will be removed in the next major release
14978                 following version 2.2.  Please see the instructions in
14979                 the <A
14980 HREF="printer_driver2.html"
14981 TARGET="_top"
14982 >Samba 2.2. Printing
14983                 HOWTO</A
14984 > for more information
14985                 on the new method of loading printer drivers onto a Samba server.
14986                 </P
14987 ><P
14988 >This parameter tells clients of a particular printer
14989                 share where to find the printer driver files for the automatic
14990                 installation of drivers for Windows 95 machines. If Samba is set up
14991                 to serve printer drivers to Windows 95 machines, this should be set to</P
14992 ><P
14993 ><B
14994 CLASS="COMMAND"
14995 >\\MACHINE\PRINTER$</B
14996 ></P
14997 ><P
14998 >Where MACHINE is the NetBIOS name of your Samba server,
14999                 and PRINTER$ is a share you set up for serving printer driver
15000                 files. For more details on setting this up see the outdated documentation
15001                 file in the <TT
15002 CLASS="FILENAME"
15003 >docs/</TT
15004 > directory, <TT
15005 CLASS="FILENAME"
15006 >               PRINTER_DRIVER.txt</TT
15007 >.</P
15008 ><P
15009 >See also <A
15010 HREF="#PRINTERDRIVERFILE"
15011 ><TT
15012 CLASS="PARAMETER"
15013 ><I
15014 >               printer driver file</I
15015 ></TT
15016 ></A
15017 >.</P
15018 ><P
15019 >Default: <B
15020 CLASS="COMMAND"
15021 >none</B
15022 ></P
15023 ><P
15024 >Example: <B
15025 CLASS="COMMAND"
15026 >printer driver location = \\MACHINE\PRINTER$
15027                 </B
15028 ></P
15029 ></DD
15030 ><DT
15031 ><A
15032 NAME="PRINTERNAME"
15033 ></A
15034 >printer name (S)</DT
15035 ><DD
15036 ><P
15037 >This parameter specifies the name of the printer
15038                 to which print jobs spooled through a printable service will be sent.</P
15039 ><P
15040 >If specified in the [global] section, the printer
15041                 name given will be used for any printable service that does
15042                 not have its own printer name specified.</P
15043 ><P
15044 >Default: <EM
15045 >none (but may be <TT
15046 CLASS="CONSTANT"
15047 >lp</TT
15048 >
15049                 on many systems)</EM
15050 ></P
15051 ><P
15052 >Example: <B
15053 CLASS="COMMAND"
15054 >printer name = laserwriter</B
15055 ></P
15056 ></DD
15057 ><DT
15058 ><A
15059 NAME="PRINTER"
15060 ></A
15061 >printer (S)</DT
15062 ><DD
15063 ><P
15064 >Synonym for <A
15065 HREF="#PRINTERNAME"
15066 ><TT
15067 CLASS="PARAMETER"
15068 ><I
15069 >               printer name</I
15070 ></TT
15071 ></A
15072 >.</P
15073 ></DD
15074 ><DT
15075 ><A
15076 NAME="PRINTING"
15077 ></A
15078 >printing (S)</DT
15079 ><DD
15080 ><P
15081 >This parameters controls how printer status
15082                 information is interpreted on your system. It also affects the
15083                 default values for the <TT
15084 CLASS="PARAMETER"
15085 ><I
15086 >print command</I
15087 ></TT
15088 >,
15089                 <TT
15090 CLASS="PARAMETER"
15091 ><I
15092 >lpq command</I
15093 ></TT
15094 >, <TT
15095 CLASS="PARAMETER"
15096 ><I
15097 >lppause command
15098                 </I
15099 ></TT
15100 >, <TT
15101 CLASS="PARAMETER"
15102 ><I
15103 >lpresume command</I
15104 ></TT
15105 >, and
15106                 <TT
15107 CLASS="PARAMETER"
15108 ><I
15109 >lprm command</I
15110 ></TT
15111 > if specified in the
15112                 [global] section.</P
15113 ><P
15114 >Currently nine printing styles are supported. They are
15115                 <TT
15116 CLASS="CONSTANT"
15117 >BSD</TT
15118 >, <TT
15119 CLASS="CONSTANT"
15120 >AIX</TT
15121 >,
15122                 <TT
15123 CLASS="CONSTANT"
15124 >LPRNG</TT
15125 >, <TT
15126 CLASS="CONSTANT"
15127 >PLP</TT
15128 >,
15129                 <TT
15130 CLASS="CONSTANT"
15131 >SYSV</TT
15132 >, <TT
15133 CLASS="CONSTANT"
15134 >HPUX</TT
15135 >,
15136                 <TT
15137 CLASS="CONSTANT"
15138 >QNX</TT
15139 >, <TT
15140 CLASS="CONSTANT"
15141 >SOFTQ</TT
15142 >,
15143                 and <TT
15144 CLASS="CONSTANT"
15145 >CUPS</TT
15146 >.</P
15147 ><P
15148 >To see what the defaults are for the other print
15149                 commands when using the various options use the <A
15150 HREF="testparm.1.html"
15151 TARGET="_top"
15152 >testparm(1)</A
15153 > program.</P
15154 ><P
15155 >This option can be set on a per printer basis</P
15156 ><P
15157 >See also the discussion in the <A
15158 HREF="#AEN79"
15159 >               [printers]</A
15160 > section.</P
15161 ></DD
15162 ><DT
15163 ><A
15164 NAME="PROTOCOL"
15165 ></A
15166 >protocol (G)</DT
15167 ><DD
15168 ><P
15169 >Synonym for <A
15170 HREF="#MAXPROTOCOL"
15171 >               <TT
15172 CLASS="PARAMETER"
15173 ><I
15174 >max protocol</I
15175 ></TT
15176 ></A
15177 >.</P
15178 ></DD
15179 ><DT
15180 ><A
15181 NAME="PUBLIC"
15182 ></A
15183 >public (S)</DT
15184 ><DD
15185 ><P
15186 >Synonym for <A
15187 HREF="#GUESTOK"
15188 ><TT
15189 CLASS="PARAMETER"
15190 ><I
15191 >guest
15192                 ok</I
15193 ></TT
15194 ></A
15195 >.</P
15196 ></DD
15197 ><DT
15198 ><A
15199 NAME="QUEUEPAUSECOMMAND"
15200 ></A
15201 >queuepause command (S)</DT
15202 ><DD
15203 ><P
15204 >This parameter specifies the command to be
15205                 executed on the server host in order to pause the printer queue.</P
15206 ><P
15207 >This command should be a program or script which takes
15208                 a printer name as its only parameter and stops the printer queue,
15209                 such that no longer jobs are submitted to the printer.</P
15210 ><P
15211 >This command is not supported by Windows for Workgroups,
15212                 but can be issued from the Printers window under Windows 95
15213                 and NT.</P
15214 ><P
15215 >If a <TT
15216 CLASS="PARAMETER"
15217 ><I
15218 >%p</I
15219 ></TT
15220 > is given then the printer name
15221                 is put in its place. Otherwise it is placed at the end of the command.
15222                 </P
15223 ><P
15224 >Note that it is good practice to include the absolute
15225                 path in the command as the PATH may not be available to the
15226                 server.</P
15227 ><P
15228 >Default: <EM
15229 >depends on the setting of <TT
15230 CLASS="PARAMETER"
15231 ><I
15232 >printing
15233                 </I
15234 ></TT
15235 ></EM
15236 ></P
15237 ><P
15238 >Example: <B
15239 CLASS="COMMAND"
15240 >queuepause command = disable %p</B
15241 ></P
15242 ></DD
15243 ><DT
15244 ><A
15245 NAME="QUEUERESUMECOMMAND"
15246 ></A
15247 >queueresume command (S)</DT
15248 ><DD
15249 ><P
15250 >This parameter specifies the command to be
15251                 executed on the server host in order to resume the printer queue. It
15252                 is the command to undo the behavior that is caused by the
15253                 previous parameter (<A
15254 HREF="#QUEUEPAUSECOMMAND"
15255 ><TT
15256 CLASS="PARAMETER"
15257 ><I
15258 >               queuepause command</I
15259 ></TT
15260 ></A
15261 >).</P
15262 ><P
15263 >This command should be a program or script which takes
15264                 a printer name as its only parameter and resumes the printer queue,
15265                 such that queued jobs are resubmitted to the printer.</P
15266 ><P
15267 >This command is not supported by Windows for Workgroups,
15268                 but can be issued from the Printers window under Windows 95
15269                 and NT.</P
15270 ><P
15271 >If a <TT
15272 CLASS="PARAMETER"
15273 ><I
15274 >%p</I
15275 ></TT
15276 > is given then the printer name
15277                 is put in its place. Otherwise it is placed at the end of the
15278                 command.</P
15279 ><P
15280 >Note that it is good practice to include the absolute
15281                 path in the command as the PATH may not be available to the
15282                 server.</P
15283 ><P
15284 >Default: <EM
15285 >depends on the setting of <A
15286 HREF="#PRINTING"
15287 ><TT
15288 CLASS="PARAMETER"
15289 ><I
15290 >printing</I
15291 ></TT
15292 ></A
15293 ></EM
15294 >
15295                 </P
15296 ><P
15297 >Example: <B
15298 CLASS="COMMAND"
15299 >queuepause command = enable %p
15300                 </B
15301 ></P
15302 ></DD
15303 ><DT
15304 ><A
15305 NAME="READBMPX"
15306 ></A
15307 >read bmpx (G)</DT
15308 ><DD
15309 ><P
15310 >This boolean parameter controls whether <A
15311 HREF="smbd.8.html"
15312 TARGET="_top"
15313 >smbd(8)</A
15314 > will support the "Read
15315                 Block Multiplex" SMB. This is now rarely used and defaults to
15316                 <TT
15317 CLASS="CONSTANT"
15318 >no</TT
15319 >. You should never need to set this
15320                 parameter.</P
15321 ><P
15322 >Default: <B
15323 CLASS="COMMAND"
15324 >read bmpx = no</B
15325 ></P
15326 ></DD
15327 ><DT
15328 ><A
15329 NAME="READLIST"
15330 ></A
15331 >read list (S)</DT
15332 ><DD
15333 ><P
15334 >This is a list of users that are given read-only
15335                 access to a service. If the connecting user is in this list then
15336                 they will not be given write access, no matter what the <A
15337 HREF="#READONLY"
15338 ><TT
15339 CLASS="PARAMETER"
15340 ><I
15341 >read only</I
15342 ></TT
15343 ></A
15344 >
15345                 option is set to. The list can include group names using the
15346                 syntax described in the <A
15347 HREF="#INVALIDUSERS"
15348 ><TT
15349 CLASS="PARAMETER"
15350 ><I
15351 >               invalid users</I
15352 ></TT
15353 ></A
15354 > parameter.</P
15355 ><P
15356 >See also the <A
15357 HREF="#WRITELIST"
15358 ><TT
15359 CLASS="PARAMETER"
15360 ><I
15361 >               write list</I
15362 ></TT
15363 ></A
15364 > parameter and the <A
15365 HREF="#INVALIDUSERS"
15366 ><TT
15367 CLASS="PARAMETER"
15368 ><I
15369 >invalid users</I
15370 ></TT
15371 >
15372                 </A
15373 > parameter.</P
15374 ><P
15375 >Default: <B
15376 CLASS="COMMAND"
15377 >read list = &#60;empty string&#62;</B
15378 ></P
15379 ><P
15380 >Example: <B
15381 CLASS="COMMAND"
15382 >read list = mary, @students</B
15383 ></P
15384 ></DD
15385 ><DT
15386 ><A
15387 NAME="READONLY"
15388 ></A
15389 >read only (S)</DT
15390 ><DD
15391 ><P
15392 >An inverted synonym is <A
15393 HREF="#WRITEABLE"
15394 >               <TT
15395 CLASS="PARAMETER"
15396 ><I
15397 >writeable</I
15398 ></TT
15399 ></A
15400 >.</P
15401 ><P
15402 >If this parameter is <TT
15403 CLASS="CONSTANT"
15404 >yes</TT
15405 >, then users
15406                 of a service may not create or modify files in the service's
15407                 directory.</P
15408 ><P
15409 >Note that a printable service (<B
15410 CLASS="COMMAND"
15411 >printable = yes</B
15412 >)
15413                 will <EM
15414 >ALWAYS</EM
15415 > allow writing to the directory
15416                 (user privileges permitting), but only via spooling operations.</P
15417 ><P
15418 >Default: <B
15419 CLASS="COMMAND"
15420 >read only = yes</B
15421 ></P
15422 ></DD
15423 ><DT
15424 ><A
15425 NAME="READRAW"
15426 ></A
15427 >read raw (G)</DT
15428 ><DD
15429 ><P
15430 >This parameter controls whether or not the server
15431                 will support the raw read SMB requests when transferring data
15432                 to clients.</P
15433 ><P
15434 >If enabled, raw reads allow reads of 65535 bytes in
15435                 one packet. This typically provides a major performance benefit.
15436                 </P
15437 ><P
15438 >However, some clients either negotiate the allowable
15439                 block size incorrectly or are incapable of supporting larger block
15440                 sizes, and for these clients you may need to disable raw reads.</P
15441 ><P
15442 >In general this parameter should be viewed as a system tuning
15443                 tool and left severely alone. See also <A
15444 HREF="#WRITERAW"
15445 >               <TT
15446 CLASS="PARAMETER"
15447 ><I
15448 >write raw</I
15449 ></TT
15450 ></A
15451 >.</P
15452 ><P
15453 >Default: <B
15454 CLASS="COMMAND"
15455 >read raw = yes</B
15456 ></P
15457 ></DD
15458 ><DT
15459 ><A
15460 NAME="READSIZE"
15461 ></A
15462 >read size (G)</DT
15463 ><DD
15464 ><P
15465 >The option <TT
15466 CLASS="PARAMETER"
15467 ><I
15468 >read size</I
15469 ></TT
15470 >
15471                 affects the overlap of disk reads/writes with network reads/writes.
15472                 If the amount of data being transferred in several of the SMB
15473                 commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger
15474                 than this value then the server begins writing the data before it
15475                 has received the whole packet from the network, or in the case of
15476                 SMBreadbraw, it begins writing to the network before all the data
15477                 has been read from disk.</P
15478 ><P
15479 >This overlapping works best when the speeds of disk and
15480                 network access are similar, having very little effect when the
15481                 speed of one is much greater than the other.</P
15482 ><P
15483 >The default value is 16384, but very little experimentation
15484                 has been done yet to determine the optimal value, and it is likely
15485                 that the best value will vary greatly between systems anyway.
15486                 A value over 65536 is pointless and will cause you to allocate
15487                 memory unnecessarily.</P
15488 ><P
15489 >Default: <B
15490 CLASS="COMMAND"
15491 >read size = 16384</B
15492 ></P
15493 ><P
15494 >Example: <B
15495 CLASS="COMMAND"
15496 >read size = 8192</B
15497 ></P
15498 ></DD
15499 ><DT
15500 ><A
15501 NAME="REMOTEANNOUNCE"
15502 ></A
15503 >remote announce (G)</DT
15504 ><DD
15505 ><P
15506 >This option allows you to setup <A
15507 HREF="nmbd.8.html"
15508 TARGET="_top"
15509 >nmbd(8)</A
15510 > to periodically announce itself
15511                 to arbitrary IP addresses with an arbitrary workgroup name.</P
15512 ><P
15513 >This is useful if you want your Samba server to appear
15514                 in a remote workgroup for which the normal browse propagation
15515                 rules don't work. The remote workgroup can be anywhere that you
15516                 can send IP packets to.</P
15517 ><P
15518 >For example:</P
15519 ><P
15520 ><B
15521 CLASS="COMMAND"
15522 >remote announce = 192.168.2.255/SERVERS
15523                 192.168.4.255/STAFF</B
15524 ></P
15525 ><P
15526 >the above line would cause <B
15527 CLASS="COMMAND"
15528 >nmbd</B
15529 > to announce itself
15530                 to the two given IP addresses using the given workgroup names.
15531                 If you leave out the workgroup name then the one given in
15532                 the <A
15533 HREF="#WORKGROUP"
15534 ><TT
15535 CLASS="PARAMETER"
15536 ><I
15537 >workgroup</I
15538 ></TT
15539 ></A
15540 >
15541                 parameter is used instead.</P
15542 ><P
15543 >The IP addresses you choose would normally be the broadcast
15544                 addresses of the remote networks, but can also be the IP addresses
15545                 of known browse masters if your network config is that stable.</P
15546 ><P
15547 >See the documentation file <TT
15548 CLASS="FILENAME"
15549 >BROWSING.txt</TT
15550 >
15551                 in the <TT
15552 CLASS="FILENAME"
15553 >docs/</TT
15554 > directory.</P
15555 ><P
15556 >Default: <B
15557 CLASS="COMMAND"
15558 >remote announce = &#60;empty string&#62;
15559                 </B
15560 ></P
15561 ></DD
15562 ><DT
15563 ><A
15564 NAME="REMOTEBROWSESYNC"
15565 ></A
15566 >remote browse sync (G)</DT
15567 ><DD
15568 ><P
15569 >This option allows you to setup <A
15570 HREF="nmbd.8.html"
15571 TARGET="_top"
15572 >nmbd(8)</A
15573 > to periodically request
15574                 synchronization of browse lists with the master browser of a Samba
15575                 server that is on a remote segment. This option will allow you to
15576                 gain browse lists for multiple workgroups across routed networks. This
15577                 is done in a manner that does not work with any non-Samba servers.</P
15578 ><P
15579 >This is useful if you want your Samba server and all local
15580                 clients to appear in a remote workgroup for which the normal browse
15581                 propagation rules don't work. The remote workgroup can be anywhere
15582                 that you can send IP packets to.</P
15583 ><P
15584 >For example:</P
15585 ><P
15586 ><B
15587 CLASS="COMMAND"
15588 >remote browse sync = 192.168.2.255 192.168.4.255
15589                 </B
15590 ></P
15591 ><P
15592 >the above line would cause <B
15593 CLASS="COMMAND"
15594 >nmbd</B
15595 > to request
15596                 the master browser on the specified subnets or addresses to
15597                 synchronize their browse lists with the local server.</P
15598 ><P
15599 >The IP addresses you choose would normally be the broadcast
15600                 addresses of the remote networks, but can also be the IP addresses
15601                 of known browse masters if your network config is that stable. If
15602                 a machine IP address is given Samba makes NO attempt to validate
15603                 that the remote machine is available, is listening, nor that it
15604                 is in fact the browse master on its segment.</P
15605 ><P
15606 >Default: <B
15607 CLASS="COMMAND"
15608 >remote browse sync = &#60;empty string&#62;
15609                 </B
15610 ></P
15611 ></DD
15612 ><DT
15613 ><A
15614 NAME="RESTRICTANONYMOUS"
15615 ></A
15616 >restrict anonymous (G)</DT
15617 ><DD
15618 ><P
15619 >This is a boolean parameter.  If it is <TT
15620 CLASS="CONSTANT"
15621 >yes</TT
15622 >, then
15623                 anonymous access to the server will be restricted, namely in the
15624                 case where the server is expecting the client to send a username,
15625                 but it doesn't.  Setting it to <TT
15626 CLASS="CONSTANT"
15627 >yes</TT
15628 > will force these anonymous
15629                 connections to be denied, and the client will be required to always
15630                 supply a username and password when connecting. Use of this parameter
15631                 is only recommended for homogeneous NT client environments.</P
15632 ><P
15633 >This parameter makes the use of macro expansions that rely
15634                 on the username (%U, %G, etc) consistent.  NT 4.0
15635                 likes to use anonymous connections when refreshing the share list,
15636                 and this is a way to work around that.</P
15637 ><P
15638 >When restrict anonymous is <TT
15639 CLASS="CONSTANT"
15640 >yes</TT
15641 >, all anonymous connections
15642                 are denied no matter what they are for.  This can effect the ability
15643                 of a machine to access the Samba Primary Domain Controller to revalidate
15644                 its machine account after someone else has logged on the client
15645                 interactively.  The NT client will display a message saying that
15646                 the machine's account in  the domain doesn't exist or the password is
15647                 bad.  The best way to deal  with this is to reboot NT client machines
15648                 between interactive logons,  using "Shutdown and Restart", rather
15649                 than "Close all programs and logon as a different user".</P
15650 ><P
15651 >Default: <B
15652 CLASS="COMMAND"
15653 >restrict anonymous = no</B
15654 ></P
15655 ></DD
15656 ><DT
15657 ><A
15658 NAME="ROOT"
15659 ></A
15660 >root (G)</DT
15661 ><DD
15662 ><P
15663 >Synonym for <A
15664 HREF="#ROOTDIRECTORY"
15665 >               <TT
15666 CLASS="PARAMETER"
15667 ><I
15668 >root directory"</I
15669 ></TT
15670 ></A
15671 >.</P
15672 ></DD
15673 ><DT
15674 ><A
15675 NAME="ROOTDIR"
15676 ></A
15677 >root dir (G)</DT
15678 ><DD
15679 ><P
15680 >Synonym for <A
15681 HREF="#ROOTDIRECTORY"
15682 >               <TT
15683 CLASS="PARAMETER"
15684 ><I
15685 >root directory"</I
15686 ></TT
15687 ></A
15688 >.</P
15689 ></DD
15690 ><DT
15691 ><A
15692 NAME="ROOTDIRECTORY"
15693 ></A
15694 >root directory (G)</DT
15695 ><DD
15696 ><P
15697 >The server will <B
15698 CLASS="COMMAND"
15699 >chroot()</B
15700 > (i.e.
15701                 Change its root directory) to this directory on startup. This is
15702                 not strictly necessary for secure operation. Even without it the
15703                 server will deny access to files not in one of the service entries.
15704                 It may also check for, and deny access to, soft links to other
15705                 parts of the filesystem, or attempts to use ".." in file names
15706                 to access other directories (depending on the setting of the <A
15707 HREF="#WIDELINKS"
15708 ><TT
15709 CLASS="PARAMETER"
15710 ><I
15711 >wide links</I
15712 ></TT
15713 ></A
15714 >
15715                 parameter).</P
15716 ><P
15717 >Adding a <TT
15718 CLASS="PARAMETER"
15719 ><I
15720 >root directory</I
15721 ></TT
15722 > entry other
15723                 than "/" adds an extra level of security, but at a price. It
15724                 absolutely ensures that no access is given to files not in the
15725                 sub-tree specified in the <TT
15726 CLASS="PARAMETER"
15727 ><I
15728 >root directory</I
15729 ></TT
15730 >
15731                 option, <EM
15732 >including</EM
15733 > some files needed for
15734                 complete operation of the server. To maintain full operability
15735                 of the server you will need to mirror some system files
15736                 into the <TT
15737 CLASS="PARAMETER"
15738 ><I
15739 >root directory</I
15740 ></TT
15741 > tree. In particular
15742                 you will need to mirror <TT
15743 CLASS="FILENAME"
15744 >/etc/passwd</TT
15745 > (or a
15746                 subset of it), and any binaries or configuration files needed for
15747                 printing (if required). The set of files that must be mirrored is
15748                 operating system dependent.</P
15749 ><P
15750 >Default: <B
15751 CLASS="COMMAND"
15752 >root directory = /</B
15753 ></P
15754 ><P
15755 >Example: <B
15756 CLASS="COMMAND"
15757 >root directory = /homes/smb</B
15758 ></P
15759 ></DD
15760 ><DT
15761 ><A
15762 NAME="ROOTPOSTEXEC"
15763 ></A
15764 >root postexec (S)</DT
15765 ><DD
15766 ><P
15767 >This is the same as the <TT
15768 CLASS="PARAMETER"
15769 ><I
15770 >postexec</I
15771 ></TT
15772 >
15773                 parameter except that the command is run as root. This
15774                 is useful for unmounting filesystems
15775                 (such as CDROMs) after a connection is closed.</P
15776 ><P
15777 >See also <A
15778 HREF="#POSTEXEC"
15779 ><TT
15780 CLASS="PARAMETER"
15781 ><I
15782 >               postexec</I
15783 ></TT
15784 ></A
15785 >.</P
15786 ><P
15787 >Default: <B
15788 CLASS="COMMAND"
15789 >root postexec = &#60;empty string&#62;
15790                 </B
15791 ></P
15792 ></DD
15793 ><DT
15794 ><A
15795 NAME="ROOTPREEXEC"
15796 ></A
15797 >root preexec (S)</DT
15798 ><DD
15799 ><P
15800 >This is the same as the <TT
15801 CLASS="PARAMETER"
15802 ><I
15803 >preexec</I
15804 ></TT
15805 >
15806                 parameter except that the command is run as root. This
15807                 is useful for mounting filesystems (such as CDROMs) when a
15808                 connection is opened.</P
15809 ><P
15810 >See also <A
15811 HREF="#PREEXEC"
15812 ><TT
15813 CLASS="PARAMETER"
15814 ><I
15815 >               preexec</I
15816 ></TT
15817 ></A
15818 > and <A
15819 HREF="#PREEXECCLOSE"
15820 >               <TT
15821 CLASS="PARAMETER"
15822 ><I
15823 >preexec close</I
15824 ></TT
15825 ></A
15826 >.</P
15827 ><P
15828 >Default: <B
15829 CLASS="COMMAND"
15830 >root preexec = &#60;empty string&#62;
15831                 </B
15832 ></P
15833 ></DD
15834 ><DT
15835 ><A
15836 NAME="ROOTPREEXECCLOSE"
15837 ></A
15838 >root preexec close (S)</DT
15839 ><DD
15840 ><P
15841 >This is the same as the <TT
15842 CLASS="PARAMETER"
15843 ><I
15844 >preexec close
15845                 </I
15846 ></TT
15847 > parameter except that the command is run as root.</P
15848 ><P
15849 >See also <A
15850 HREF="#PREEXEC"
15851 ><TT
15852 CLASS="PARAMETER"
15853 ><I
15854 >               preexec</I
15855 ></TT
15856 ></A
15857 > and <A
15858 HREF="#PREEXECCLOSE"
15859 >               <TT
15860 CLASS="PARAMETER"
15861 ><I
15862 >preexec close</I
15863 ></TT
15864 ></A
15865 >.</P
15866 ><P
15867 >Default: <B
15868 CLASS="COMMAND"
15869 >root preexec close = no</B
15870 ></P
15871 ></DD
15872 ><DT
15873 ><A
15874 NAME="SECURITY"
15875 ></A
15876 >security (G)</DT
15877 ><DD
15878 ><P
15879 >This option affects how clients respond to
15880                 Samba and is one of the most important settings in the <TT
15881 CLASS="FILENAME"
15882 >               smb.conf</TT
15883 > file.</P
15884 ><P
15885 >The option sets the "security mode bit" in replies to
15886                 protocol negotiations with <A
15887 HREF="smbd.8.html"
15888 TARGET="_top"
15889 >smbd(8)
15890                 </A
15891 > to turn share level security on or off. Clients decide
15892                 based on this bit whether (and how) to transfer user and password
15893                 information to the server.</P
15894 ><P
15895 >The default is <B
15896 CLASS="COMMAND"
15897 >security = user</B
15898 >, as this is
15899                 the most common setting needed when talking to Windows 98 and
15900                 Windows NT.</P
15901 ><P
15902 >The alternatives are <B
15903 CLASS="COMMAND"
15904 >security = share</B
15905 >,
15906                 <B
15907 CLASS="COMMAND"
15908 >security = server</B
15909 > or <B
15910 CLASS="COMMAND"
15911 >security = domain
15912                 </B
15913 >.</P
15914 ><P
15915 >In versions of Samba prior to 2.0.0, the default was
15916                 <B
15917 CLASS="COMMAND"
15918 >security = share</B
15919 > mainly because that was
15920                 the only option at one stage.</P
15921 ><P
15922 >There is a bug in WfWg that has relevance to this
15923                 setting. When in user or server level security a WfWg client
15924                 will totally ignore the password you type in the "connect
15925                 drive" dialog box. This makes it very difficult (if not impossible)
15926                 to connect to a Samba service as anyone except the user that
15927                 you are logged into WfWg as.</P
15928 ><P
15929 >If your PCs use usernames that are the same as their
15930                 usernames on the UNIX machine then you will want to use
15931                 <B
15932 CLASS="COMMAND"
15933 >security = user</B
15934 >. If you mostly use usernames
15935                 that don't exist on the UNIX box then use <B
15936 CLASS="COMMAND"
15937 >security =
15938                 share</B
15939 >.</P
15940 ><P
15941 >You should also use <B
15942 CLASS="COMMAND"
15943 >security = share</B
15944 > if you
15945                 want to mainly setup shares without a password (guest shares). This
15946                 is commonly used for a shared printer server. It is more difficult
15947                 to setup guest shares with <B
15948 CLASS="COMMAND"
15949 >security = user</B
15950 >, see
15951                 the <A
15952 HREF="#MAPTOGUEST"
15953 ><TT
15954 CLASS="PARAMETER"
15955 ><I
15956 >map to guest</I
15957 ></TT
15958 >
15959                 </A
15960 >parameter for details.</P
15961 ><P
15962 >It is possible to use <B
15963 CLASS="COMMAND"
15964 >smbd</B
15965 > in a <EM
15966 >               hybrid mode</EM
15967 > where it is offers both user and share
15968                 level security under different <A
15969 HREF="#NETBIOSALIASES"
15970 >               <TT
15971 CLASS="PARAMETER"
15972 ><I
15973 >NetBIOS aliases</I
15974 ></TT
15975 ></A
15976 >. </P
15977 ><P
15978 >The different settings will now be explained.</P
15979 ><P
15980 ><A
15981 NAME="SECURITYEQUALSSHARE"
15982 ></A
15983 ><EM
15984 >SECURITY = SHARE
15985                 </EM
15986 ></P
15987 ><P
15988 >When clients connect to a share level security server they
15989                 need not log onto the server with a valid username and password before
15990                 attempting to connect to a shared resource (although modern clients
15991                 such as Windows 95/98 and Windows NT will send a logon request with
15992                 a username but no password when talking to a <B
15993 CLASS="COMMAND"
15994 >security = share
15995                 </B
15996 > server). Instead, the clients send authentication information
15997                 (passwords) on a per-share basis, at the time they attempt to connect
15998                 to that share.</P
15999 ><P
16000 >Note that <B
16001 CLASS="COMMAND"
16002 >smbd</B
16003 > <EM
16004 >ALWAYS</EM
16005 >
16006                 uses a valid UNIX user to act on behalf of the client, even in
16007                 <B
16008 CLASS="COMMAND"
16009 >security = share</B
16010 > level security.</P
16011 ><P
16012 >As clients are not required to send a username to the server
16013                 in share level security, <B
16014 CLASS="COMMAND"
16015 >smbd</B
16016 > uses several
16017                 techniques to determine the correct UNIX user to use on behalf
16018                 of the client.</P
16019 ><P
16020 >A list of possible UNIX usernames to match with the given
16021                 client password is constructed using the following methods :</P
16022 ><P
16023 ></P
16024 ><UL
16025 ><LI
16026 ><P
16027 >If the <A
16028 HREF="#GUESTONLY"
16029 ><TT
16030 CLASS="PARAMETER"
16031 ><I
16032 >guest
16033                         only</I
16034 ></TT
16035 ></A
16036 > parameter is set, then all the other
16037                         stages are missed and only the <A
16038 HREF="#GUESTACCOUNT"
16039 >                       <TT
16040 CLASS="PARAMETER"
16041 ><I
16042 >guest account</I
16043 ></TT
16044 ></A
16045 > username is checked.
16046                         </P
16047 ></LI
16048 ><LI
16049 ><P
16050 >Is a username is sent with the share connection
16051                         request, then this username (after mapping - see <A
16052 HREF="#USERNAMEMAP"
16053 ><TT
16054 CLASS="PARAMETER"
16055 ><I
16056 >username map</I
16057 ></TT
16058 ></A
16059 >),
16060                         is added as a potential username.</P
16061 ></LI
16062 ><LI
16063 ><P
16064 >If the client did a previous <EM
16065 >logon
16066                         </EM
16067 > request (the SessionSetup SMB call) then the
16068                         username sent in this SMB will be added as a potential username.
16069                         </P
16070 ></LI
16071 ><LI
16072 ><P
16073 >The name of the service the client requested is
16074                         added as a potential username.</P
16075 ></LI
16076 ><LI
16077 ><P
16078 >The NetBIOS name of the client is added to
16079                         the list as a potential username.</P
16080 ></LI
16081 ><LI
16082 ><P
16083 >Any users on the <A
16084 HREF="#USER"
16085 ><TT
16086 CLASS="PARAMETER"
16087 ><I
16088 >                       user</I
16089 ></TT
16090 ></A
16091 > list are added as potential usernames.
16092                         </P
16093 ></LI
16094 ></UL
16095 ><P
16096 >If the <TT
16097 CLASS="PARAMETER"
16098 ><I
16099 >guest only</I
16100 ></TT
16101 > parameter is
16102                 not set, then this list is then tried with the supplied password.
16103                 The first user for whom the password matches will be used as the
16104                 UNIX user.</P
16105 ><P
16106 >If the <TT
16107 CLASS="PARAMETER"
16108 ><I
16109 >guest only</I
16110 ></TT
16111 > parameter is
16112                 set, or no username can be determined then if the share is marked
16113                 as available to the <TT
16114 CLASS="PARAMETER"
16115 ><I
16116 >guest account</I
16117 ></TT
16118 >, then this
16119                 guest user will be used, otherwise access is denied.</P
16120 ><P
16121 >Note that it can be <EM
16122 >very</EM
16123 > confusing
16124                 in share-level security as to which UNIX username will eventually
16125                 be used in granting access.</P
16126 ><P
16127 >See also the section <A
16128 HREF="#AEN241"
16129 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16130 >.</P
16131 ><P
16132 ><A
16133 NAME="SECURITYEQUALSUSER"
16134 ></A
16135 ><EM
16136 >SECURITY = USER
16137                 </EM
16138 ></P
16139 ><P
16140 >This is the default security setting in Samba 2.2.
16141                 With user-level security a client must first "log-on" with a
16142                 valid username and password (which can be mapped using the <A
16143 HREF="#USERNAMEMAP"
16144 ><TT
16145 CLASS="PARAMETER"
16146 ><I
16147 >username map</I
16148 ></TT
16149 ></A
16150 >
16151                 parameter). Encrypted passwords (see the <A
16152 HREF="#ENCRYPTPASSWORDS"
16153 >               <TT
16154 CLASS="PARAMETER"
16155 ><I
16156 >encrypted passwords</I
16157 ></TT
16158 ></A
16159 > parameter) can also
16160                 be used in this security mode. Parameters such as <A
16161 HREF="#USER"
16162 >               <TT
16163 CLASS="PARAMETER"
16164 ><I
16165 >user</I
16166 ></TT
16167 ></A
16168 > and <A
16169 HREF="#GUESTONLY"
16170 >               <TT
16171 CLASS="PARAMETER"
16172 ><I
16173 >guest only</I
16174 ></TT
16175 ></A
16176 > if set        are then applied and
16177                 may change the UNIX user to use on this connection, but only after
16178                 the user has been successfully authenticated.</P
16179 ><P
16180 ><EM
16181 >Note</EM
16182 > that the name of the resource being
16183                 requested is <EM
16184 >not</EM
16185 > sent to the server until after
16186                 the server has successfully authenticated the client. This is why
16187                 guest shares don't work in user level security without allowing
16188                 the server to automatically map unknown users into the <A
16189 HREF="#GUESTACCOUNT"
16190 ><TT
16191 CLASS="PARAMETER"
16192 ><I
16193 >guest account</I
16194 ></TT
16195 ></A
16196 >.
16197                 See the <A
16198 HREF="#MAPTOGUEST"
16199 ><TT
16200 CLASS="PARAMETER"
16201 ><I
16202 >map to guest</I
16203 ></TT
16204 >
16205                 </A
16206 > parameter for details on doing this.</P
16207 ><P
16208 >See also the section <A
16209 HREF="#AEN241"
16210 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16211 >.</P
16212 ><P
16213 ><A
16214 NAME="SECURITYEQUALSSERVER"
16215 ></A
16216 ><EM
16217 >SECURITY = SERVER
16218                 </EM
16219 ></P
16220 ><P
16221 >In this mode Samba will try to validate the username/password
16222                 by passing it to another SMB server, such as an NT box. If this
16223                 fails it will revert to <B
16224 CLASS="COMMAND"
16225 >security = user</B
16226 >, but note
16227                 that if encrypted passwords have been negotiated then Samba cannot
16228                 revert back to checking the UNIX password file, it must have a valid
16229                 <TT
16230 CLASS="FILENAME"
16231 >smbpasswd</TT
16232 > file to check users against. See the
16233                 documentation file in the <TT
16234 CLASS="FILENAME"
16235 >docs/</TT
16236 > directory
16237                 <TT
16238 CLASS="FILENAME"
16239 >ENCRYPTION.txt</TT
16240 > for details on how to set this
16241                 up.</P
16242 ><P
16243 ><EM
16244 >Note</EM
16245 > that from the client's point of
16246                 view <B
16247 CLASS="COMMAND"
16248 >security = server</B
16249 > is the same as <B
16250 CLASS="COMMAND"
16251 >               security = user</B
16252 >.  It only affects how the server deals
16253                 with the authentication, it does not in any way affect what the
16254                 client sees.</P
16255 ><P
16256 ><EM
16257 >Note</EM
16258 > that the name of the resource being
16259                 requested is <EM
16260 >not</EM
16261 > sent to the server until after
16262                 the server has successfully authenticated the client. This is why
16263                 guest shares don't work in user level security without allowing
16264                 the server to automatically map unknown users into the <A
16265 HREF="#GUESTACCOUNT"
16266 ><TT
16267 CLASS="PARAMETER"
16268 ><I
16269 >guest account</I
16270 ></TT
16271 ></A
16272 >.
16273                 See the <A
16274 HREF="#MAPTOGUEST"
16275 ><TT
16276 CLASS="PARAMETER"
16277 ><I
16278 >map to guest</I
16279 ></TT
16280 >
16281                 </A
16282 > parameter for details on doing this.</P
16283 ><P
16284 >See also the section <A
16285 HREF="#AEN241"
16286 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16287 >.</P
16288 ><P
16289 >See also the <A
16290 HREF="#PASSWORDSERVER"
16291 ><TT
16292 CLASS="PARAMETER"
16293 ><I
16294 >password
16295                 server</I
16296 ></TT
16297 ></A
16298 > parameter and the <A
16299 HREF="#ENCRYPTPASSWORDS"
16300 ><TT
16301 CLASS="PARAMETER"
16302 ><I
16303 >encrypted passwords</I
16304 ></TT
16305 >
16306                 </A
16307 > parameter.</P
16308 ><P
16309 ><A
16310 NAME="SECURITYEQUALSDOMAIN"
16311 ></A
16312 ><EM
16313 >SECURITY = DOMAIN
16314                 </EM
16315 ></P
16316 ><P
16317 >This mode will only work correctly if <A
16318 HREF="smbpasswd.8.html"
16319 TARGET="_top"
16320 >smbpasswd(8)</A
16321 > has been used to add this
16322                 machine into a Windows NT Domain. It expects the <A
16323 HREF="#ENCRYPTPASSWORDS"
16324 ><TT
16325 CLASS="PARAMETER"
16326 ><I
16327 >encrypted passwords</I
16328 ></TT
16329 >
16330                 </A
16331 > parameter to be set to <TT
16332 CLASS="CONSTANT"
16333 >yes</TT
16334 >. In this
16335                 mode Samba will try to validate the username/password by passing
16336                 it to a Windows NT Primary or Backup Domain Controller, in exactly
16337                 the same way that a Windows NT Server would do.</P
16338 ><P
16339 ><EM
16340 >Note</EM
16341 > that a valid UNIX user must still
16342                 exist as well as the account on the Domain Controller to allow
16343                 Samba to have a valid UNIX account to map file access to.</P
16344 ><P
16345 ><EM
16346 >Note</EM
16347 > that from the client's point
16348                 of view <B
16349 CLASS="COMMAND"
16350 >security = domain</B
16351 > is the same as <B
16352 CLASS="COMMAND"
16353 >security = user
16354                 </B
16355 >. It only affects how the server deals with the authentication,
16356                 it does not in any way affect what the client sees.</P
16357 ><P
16358 ><EM
16359 >Note</EM
16360 > that the name of the resource being
16361                 requested is <EM
16362 >not</EM
16363 > sent to the server until after
16364                 the server has successfully authenticated the client. This is why
16365                 guest shares don't work in user level security without allowing
16366                 the server to automatically map unknown users into the <A
16367 HREF="#GUESTACCOUNT"
16368 ><TT
16369 CLASS="PARAMETER"
16370 ><I
16371 >guest account</I
16372 ></TT
16373 ></A
16374 >.
16375                 See the <A
16376 HREF="#MAPTOGUEST"
16377 ><TT
16378 CLASS="PARAMETER"
16379 ><I
16380 >map to guest</I
16381 ></TT
16382 >
16383                 </A
16384 > parameter for details on doing this.</P
16385 ><P
16386 ><EM
16387 >BUG:</EM
16388 > There is currently a bug in the
16389                 implementation of <B
16390 CLASS="COMMAND"
16391 >security = domain</B
16392 > with respect
16393                 to multi-byte character set usernames. The communication with a
16394                 Domain Controller must be done in UNICODE and Samba currently
16395                 does not widen multi-byte user names to UNICODE correctly, thus
16396                 a multi-byte username will not be recognized correctly at the
16397                 Domain Controller. This issue will be addressed in a future release.</P
16398 ><P
16399 >See also the section <A
16400 HREF="#AEN241"
16401 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16402 >.</P
16403 ><P
16404 >See also the <A
16405 HREF="#PASSWORDSERVER"
16406 ><TT
16407 CLASS="PARAMETER"
16408 ><I
16409 >password
16410                 server</I
16411 ></TT
16412 ></A
16413 > parameter and the <A
16414 HREF="#ENCRYPTPASSWORDS"
16415 ><TT
16416 CLASS="PARAMETER"
16417 ><I
16418 >encrypted passwords</I
16419 ></TT
16420 >
16421                 </A
16422 > parameter.</P
16423 ><P
16424 >Default: <B
16425 CLASS="COMMAND"
16426 >security = USER</B
16427 ></P
16428 ><P
16429 >Example: <B
16430 CLASS="COMMAND"
16431 >security = DOMAIN</B
16432 ></P
16433 ></DD
16434 ><DT
16435 ><A
16436 NAME="SECURITYMASK"
16437 ></A
16438 >security mask (S)</DT
16439 ><DD
16440 ><P
16441 >This parameter controls what UNIX permission
16442                 bits can be modified when a Windows NT client is manipulating
16443                 the UNIX permission on a file using the native NT security
16444                 dialog box.</P
16445 ><P
16446 >This parameter is applied as a mask (AND'ed with) to
16447                 the changed permission bits, thus preventing any bits not in
16448                 this mask from being modified. Essentially, zero bits in this
16449                 mask may be treated as a set of bits the user is not allowed
16450                 to change.</P
16451 ><P
16452 >If not set explicitly this parameter is 0777, allowing
16453                 a user to modify all the user/group/world permissions on a file.
16454                 </P
16455 ><P
16456 ><EM
16457 >Note</EM
16458 > that users who can access the
16459                 Samba server through other means can easily bypass this
16460                 restriction, so it is primarily useful for standalone
16461                 "appliance" systems.  Administrators of most normal systems will
16462                 probably want to leave it set to <TT
16463 CLASS="CONSTANT"
16464 >0777</TT
16465 >.</P
16466 ><P
16467 >See also the <A
16468 HREF="#FORCEDIRECTORYSECURITYMODE"
16469 >               <TT
16470 CLASS="PARAMETER"
16471 ><I
16472 >force directory security mode</I
16473 ></TT
16474 ></A
16475 >,
16476                 <A
16477 HREF="#DIRECTORYSECURITYMASK"
16478 ><TT
16479 CLASS="PARAMETER"
16480 ><I
16481 >directory
16482                 security mask</I
16483 ></TT
16484 ></A
16485 >, <A
16486 HREF="#FORCESECURITYMODE"
16487 >               <TT
16488 CLASS="PARAMETER"
16489 ><I
16490 >force security mode</I
16491 ></TT
16492 ></A
16493 > parameters.</P
16494 ><P
16495 >Default: <B
16496 CLASS="COMMAND"
16497 >security mask = 0777</B
16498 ></P
16499 ><P
16500 >Example: <B
16501 CLASS="COMMAND"
16502 >security mask = 0770</B
16503 ></P
16504 ></DD
16505 ><DT
16506 ><A
16507 NAME="SERVERSTRING"
16508 ></A
16509 >server string (G)</DT
16510 ><DD
16511 ><P
16512 >This controls what string will show up in the
16513                 printer comment box in print manager and next to the IPC connection
16514                 in <B
16515 CLASS="COMMAND"
16516 >net view</B
16517 >. It can be any string that you wish
16518                 to show to your users.</P
16519 ><P
16520 >It also sets what will appear in browse lists next
16521                 to the machine name.</P
16522 ><P
16523 >A <TT
16524 CLASS="PARAMETER"
16525 ><I
16526 >%v</I
16527 ></TT
16528 > will be replaced with the Samba
16529                 version number.</P
16530 ><P
16531 >A <TT
16532 CLASS="PARAMETER"
16533 ><I
16534 >%h</I
16535 ></TT
16536 > will be replaced with the
16537                 hostname.</P
16538 ><P
16539 >Default: <B
16540 CLASS="COMMAND"
16541 >server string = Samba %v</B
16542 ></P
16543 ><P
16544 >Example: <B
16545 CLASS="COMMAND"
16546 >server string = University of GNUs Samba
16547                 Server</B
16548 ></P
16549 ></DD
16550 ><DT
16551 ><A
16552 NAME="SETDIRECTORY"
16553 ></A
16554 >set directory (S)</DT
16555 ><DD
16556 ><P
16557 >If <B
16558 CLASS="COMMAND"
16559 >set directory = no</B
16560 >, then
16561                 users of the service may not use the setdir command to change
16562                 directory.</P
16563 ><P
16564 >The <B
16565 CLASS="COMMAND"
16566 >setdir</B
16567 > command is only implemented
16568                 in the Digital Pathworks client. See the Pathworks documentation
16569                 for details.</P
16570 ><P
16571 >Default: <B
16572 CLASS="COMMAND"
16573 >set directory = no</B
16574 ></P
16575 ></DD
16576 ><DT
16577 ><A
16578 NAME="SHAREMODES"
16579 ></A
16580 >share modes (S)</DT
16581 ><DD
16582 ><P
16583 >This enables or disables the honoring of
16584                 the <TT
16585 CLASS="PARAMETER"
16586 ><I
16587 >share modes</I
16588 ></TT
16589 > during a file open. These
16590                 modes are used by clients to gain exclusive read or write access
16591                 to a file.</P
16592 ><P
16593 >These open modes are not directly supported by UNIX, so
16594                 they are simulated using shared memory, or lock files if your
16595                 UNIX doesn't support shared memory (almost all do).</P
16596 ><P
16597 >The share modes that are enabled by this option are
16598                 <TT
16599 CLASS="CONSTANT"
16600 >DENY_DOS</TT
16601 >, <TT
16602 CLASS="CONSTANT"
16603 >DENY_ALL</TT
16604 >,
16605                 <TT
16606 CLASS="CONSTANT"
16607 >DENY_READ</TT
16608 >, <TT
16609 CLASS="CONSTANT"
16610 >DENY_WRITE</TT
16611 >,
16612                 <TT
16613 CLASS="CONSTANT"
16614 >DENY_NONE</TT
16615 > and <TT
16616 CLASS="CONSTANT"
16617 >DENY_FCB</TT
16618 >.
16619                 </P
16620 ><P
16621 >This option gives full share compatibility and enabled
16622                 by default.</P
16623 ><P
16624 >You should <EM
16625 >NEVER</EM
16626 > turn this parameter
16627                 off as many Windows applications will break if you do so.</P
16628 ><P
16629 >Default: <B
16630 CLASS="COMMAND"
16631 >share modes = yes</B
16632 ></P
16633 ></DD
16634 ><DT
16635 ><A
16636 NAME="SHORTPRESERVECASE"
16637 ></A
16638 >short preserve case (S)</DT
16639 ><DD
16640 ><P
16641 >This boolean parameter controls if new files
16642                 which conform to 8.3 syntax, that is all in upper case and of
16643                 suitable length, are created upper case, or if they are forced
16644                 to be the <A
16645 HREF="#DEFAULTCASE"
16646 ><TT
16647 CLASS="PARAMETER"
16648 ><I
16649 >default case
16650                 </I
16651 ></TT
16652 ></A
16653 >. This  option can be use with <A
16654 HREF="#PRESERVECASE"
16655 ><B
16656 CLASS="COMMAND"
16657 >preserve case = yes</B
16658 >
16659                 </A
16660 > to permit long filenames to retain their case, while short
16661                 names are lowered. </P
16662 ><P
16663 >See the section on <A
16664 HREF="#AEN203"
16665 >               NAME MANGLING</A
16666 >.</P
16667 ><P
16668 >Default: <B
16669 CLASS="COMMAND"
16670 >short preserve case = yes</B
16671 ></P
16672 ></DD
16673 ><DT
16674 ><A
16675 NAME="SHOWADDPRINTERWIZARD"
16676 ></A
16677 >show add printer wizard (G)</DT
16678 ><DD
16679 ><P
16680 >With the introduction of MS-RPC based printing support
16681                 for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will
16682                 appear on Samba hosts in the share listing.  Normally this folder will
16683                 contain an icon for the MS Add Printer Wizard (APW).  However, it is
16684                 possible to disable this feature regardless of the level of privilege
16685                 of the connected user.</P
16686 ><P
16687 >Under normal circumstances, the Windows NT/2000 client will
16688                 open a handle on the printer server with OpenPrinterEx() asking for
16689                 Administrator privileges.  If the user does not have administrative
16690                 access on the print server (i.e is not root or a member of the
16691                 <TT
16692 CLASS="PARAMETER"
16693 ><I
16694 >printer admin</I
16695 ></TT
16696 > group), the OpenPrinterEx()
16697                 call fails and the client makes another open call with a request for
16698                 a lower privilege level.  This should succeed, however the APW
16699                 icon will not be displayed.</P
16700 ><P
16701 >Disabling the <TT
16702 CLASS="PARAMETER"
16703 ><I
16704 >show add printer wizard</I
16705 ></TT
16706 >
16707                 parameter will always cause the OpenPrinterEx() on the server
16708                 to fail.  Thus the APW icon will never be displayed. <EM
16709 >               Note :</EM
16710 >This does not prevent the same user from having
16711                 administrative privilege on an individual printer.</P
16712 ><P
16713 >See also <A
16714 HREF="#ADDPRINTERCOMMAND"
16715 ><TT
16716 CLASS="PARAMETER"
16717 ><I
16718 >addprinter
16719                 command</I
16720 ></TT
16721 ></A
16722 >, <A
16723 HREF="#DELETEPRINTERCOMMAND"
16724 >               <TT
16725 CLASS="PARAMETER"
16726 ><I
16727 >deleteprinter command</I
16728 ></TT
16729 ></A
16730 >, <A
16731 HREF="#PRINTERADMIN"
16732 ><TT
16733 CLASS="PARAMETER"
16734 ><I
16735 >printer admin</I
16736 ></TT
16737 ></A
16738 ></P
16739 ><P
16740 >Default :<B
16741 CLASS="COMMAND"
16742 >show add printer wizard = yes</B
16743 ></P
16744 ></DD
16745 ><DT
16746 ><A
16747 NAME="SMBPASSWDFILE"
16748 ></A
16749 >smb passwd file (G)</DT
16750 ><DD
16751 ><P
16752 >This option sets the path to the encrypted
16753                 smbpasswd file.  By default the path to the smbpasswd file
16754                 is compiled into Samba.</P
16755 ><P
16756 >Default: <B
16757 CLASS="COMMAND"
16758 >smb passwd file = ${prefix}/private/smbpasswd
16759                 </B
16760 ></P
16761 ><P
16762 >Example: <B
16763 CLASS="COMMAND"
16764 >smb passwd file = /etc/samba/smbpasswd
16765                 </B
16766 ></P
16767 ></DD
16768 ><DT
16769 ><A
16770 NAME="SOCKETADDRESS"
16771 ></A
16772 >socket address (G)</DT
16773 ><DD
16774 ><P
16775 >This option allows you to control what
16776                 address Samba will listen for connections on. This is used to
16777                 support multiple virtual interfaces on the one server, each
16778                 with a different configuration.</P
16779 ><P
16780 >By default Samba will accept connections on any
16781                 address.</P
16782 ><P
16783 >Example: <B
16784 CLASS="COMMAND"
16785 >socket address = 192.168.2.20</B
16786 >
16787                 </P
16788 ></DD
16789 ><DT
16790 ><A
16791 NAME="SOCKETOPTIONS"
16792 ></A
16793 >socket options (G)</DT
16794 ><DD
16795 ><P
16796 >This option allows you to set socket options
16797                 to be used when talking with the client.</P
16798 ><P
16799 >Socket options are controls on the networking layer
16800                 of the operating systems which allow the connection to be
16801                 tuned.</P
16802 ><P
16803 >This option will typically be used to tune your Samba
16804                 server for optimal performance for your local network. There is
16805                 no way that Samba can know what the optimal parameters are for
16806                 your net, so you must experiment and choose them yourself. We
16807                 strongly suggest you read the appropriate documentation for your
16808                 operating system first (perhaps <B
16809 CLASS="COMMAND"
16810 >man setsockopt</B
16811 >
16812                 will help).</P
16813 ><P
16814 >You may find that on some systems Samba will say
16815                 "Unknown socket option" when you supply an option. This means you
16816                 either incorrectly  typed it or you need to add an include file
16817                 to includes.h for your OS.  If the latter is the case please
16818                 send the patch to <A
16819 HREF="mailto:samba@samba.org"
16820 TARGET="_top"
16821 >               samba@samba.org</A
16822 >.</P
16823 ><P
16824 >Any of the supported socket options may be combined
16825                 in any way you like, as long as your OS allows it.</P
16826 ><P
16827 >This is the list of socket options currently settable
16828                 using this option:</P
16829 ><P
16830 ></P
16831 ><UL
16832 ><LI
16833 ><P
16834 >SO_KEEPALIVE</P
16835 ></LI
16836 ><LI
16837 ><P
16838 >SO_REUSEADDR</P
16839 ></LI
16840 ><LI
16841 ><P
16842 >SO_BROADCAST</P
16843 ></LI
16844 ><LI
16845 ><P
16846 >TCP_NODELAY</P
16847 ></LI
16848 ><LI
16849 ><P
16850 >IPTOS_LOWDELAY</P
16851 ></LI
16852 ><LI
16853 ><P
16854 >IPTOS_THROUGHPUT</P
16855 ></LI
16856 ><LI
16857 ><P
16858 >SO_SNDBUF *</P
16859 ></LI
16860 ><LI
16861 ><P
16862 >SO_RCVBUF *</P
16863 ></LI
16864 ><LI
16865 ><P
16866 >SO_SNDLOWAT *</P
16867 ></LI
16868 ><LI
16869 ><P
16870 >SO_RCVLOWAT *</P
16871 ></LI
16872 ></UL
16873 ><P
16874 >Those marked with a <EM
16875 >'*'</EM
16876 > take an integer
16877                 argument. The others can optionally take a 1 or 0 argument to enable
16878                 or disable the option, by default they will be enabled if you
16879                 don't specify 1 or 0.</P
16880 ><P
16881 >To specify an argument use the syntax SOME_OPTION = VALUE
16882                 for example <B
16883 CLASS="COMMAND"
16884 >SO_SNDBUF = 8192</B
16885 >. Note that you must
16886                 not have any spaces before or after the = sign.</P
16887 ><P
16888 >If you are on a local network then a sensible option
16889                 might be</P
16890 ><P
16891 ><B
16892 CLASS="COMMAND"
16893 >socket options = IPTOS_LOWDELAY</B
16894 ></P
16895 ><P
16896 >If you have a local network then you could try:</P
16897 ><P
16898 ><B
16899 CLASS="COMMAND"
16900 >socket options = IPTOS_LOWDELAY TCP_NODELAY</B
16901 ></P
16902 ><P
16903 >If you are on a wide area network then perhaps try
16904                 setting IPTOS_THROUGHPUT. </P
16905 ><P
16906 >Note that several of the options may cause your Samba
16907                 server to fail completely. Use these options with caution!</P
16908 ><P
16909 >Default: <B
16910 CLASS="COMMAND"
16911 >socket options = TCP_NODELAY</B
16912 ></P
16913 ><P
16914 >Example: <B
16915 CLASS="COMMAND"
16916 >socket options = IPTOS_LOWDELAY</B
16917 ></P
16918 ></DD
16919 ><DT
16920 ><A
16921 NAME="SOURCEENVIRONMENT"
16922 ></A
16923 >source environment (G)</DT
16924 ><DD
16925 ><P
16926 >This parameter causes Samba to set environment
16927                 variables as per the content of the file named.</P
16928 ><P
16929 >If the value of this parameter starts with a "|" character
16930                 then Samba will treat that value as a pipe command to open and
16931                 will set the environment variables from the output of the pipe.</P
16932 ><P
16933 >The contents of the file or the output of the pipe should
16934                 be formatted as the output of the standard Unix <B
16935 CLASS="COMMAND"
16936 >env(1)
16937                 </B
16938 > command. This is of the form :</P
16939 ><P
16940 >Example environment entry:</P
16941 ><P
16942 ><B
16943 CLASS="COMMAND"
16944 >SAMBA_NETBIOS_NAME = myhostname</B
16945 ></P
16946 ><P
16947 >Default: <EM
16948 >No default value</EM
16949 ></P
16950 ><P
16951 >Examples: <B
16952 CLASS="COMMAND"
16953 >source environment = |/etc/smb.conf.sh
16954                 </B
16955 ></P
16956 ><P
16957 >Example: <B
16958 CLASS="COMMAND"
16959 >source environment =
16960                 /usr/local/smb_env_vars</B
16961 ></P
16962 ></DD
16963 ><DT
16964 ><A
16965 NAME="SSL"
16966 ></A
16967 >ssl (G)</DT
16968 ><DD
16969 ><P
16970 >This variable is part of SSL-enabled Samba. This
16971                 is only available if the SSL libraries have been compiled on your
16972                 system and the configure option <B
16973 CLASS="COMMAND"
16974 >--with-ssl</B
16975 > was
16976                 given at configure time.</P
16977 ><P
16978 >This variable enables or disables the entire SSL mode. If
16979                 it is set to <TT
16980 CLASS="CONSTANT"
16981 >no</TT
16982 >, the SSL-enabled Samba behaves
16983                 exactly like the non-SSL Samba. If set to <TT
16984 CLASS="CONSTANT"
16985 >yes</TT
16986 >,
16987                 it depends on the variables <A
16988 HREF="#SSLHOSTS"
16989 ><TT
16990 CLASS="PARAMETER"
16991 ><I
16992 >               ssl hosts</I
16993 ></TT
16994 ></A
16995 > and <A
16996 HREF="#SSLHOSTSRESIGN"
16997 >               <TT
16998 CLASS="PARAMETER"
16999 ><I
17000 >ssl hosts resign</I
17001 ></TT
17002 ></A
17003 > whether an SSL
17004                 connection will be required.</P
17005 ><P
17006 >Default: <B
17007 CLASS="COMMAND"
17008 >ssl = no</B
17009 ></P
17010 ></DD
17011 ><DT
17012 ><A
17013 NAME="SSLCACERTDIR"
17014 ></A
17015 >ssl CA certDir (G)</DT
17016 ><DD
17017 ><P
17018 >This variable is part of SSL-enabled Samba. This
17019                 is only available if the SSL libraries have been compiled on your
17020                 system and the configure option <B
17021 CLASS="COMMAND"
17022 >--with-ssl</B
17023 > was
17024                 given at configure time.</P
17025 ><P
17026 >This variable defines where to look up the Certification
17027                 Authorities. The given directory should contain one file for
17028                 each CA that Samba will trust.  The file name must be the hash
17029                 value over the "Distinguished Name" of the CA. How this directory
17030                 is set up is explained later in this document. All files within the
17031                 directory that don't fit into this naming scheme are ignored. You
17032                 don't need this variable if you don't verify client certificates.</P
17033 ><P
17034 >Default: <B
17035 CLASS="COMMAND"
17036 >ssl CA certDir = /usr/local/ssl/certs
17037                 </B
17038 ></P
17039 ></DD
17040 ><DT
17041 ><A
17042 NAME="SSLCACERTFILE"
17043 ></A
17044 >ssl CA certFile (G)</DT
17045 ><DD
17046 ><P
17047 >This variable is part of SSL-enabled Samba. This
17048                 is only available if the SSL libraries have been compiled on your
17049                 system and the configure option <B
17050 CLASS="COMMAND"
17051 >--with-ssl</B
17052 > was
17053                 given at configure time.</P
17054 ><P
17055 >This variable is a second way to define the trusted CAs.
17056                 The certificates of the trusted CAs are collected in one big
17057                 file and this variable points to the file. You will probably
17058                 only use one of the two ways to define your CAs. The first choice is
17059                 preferable if you have many CAs or want to be flexible, the second
17060                 is preferable if you only have one CA and want to keep things
17061                 simple (you won't need to create the hashed file names). You
17062                 don't need this variable if you don't verify client certificates.</P
17063 ><P
17064 >Default: <B
17065 CLASS="COMMAND"
17066 >ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem
17067                 </B
17068 ></P
17069 ></DD
17070 ><DT
17071 ><A
17072 NAME="SSLCIPHERS"
17073 ></A
17074 >ssl ciphers (G)</DT
17075 ><DD
17076 ><P
17077 >This variable is part of SSL-enabled Samba. This
17078                 is only available if the SSL libraries have been compiled on your
17079                 system and the configure option <B
17080 CLASS="COMMAND"
17081 >--with-ssl</B
17082 > was
17083                 given at configure time.</P
17084 ><P
17085 >This variable defines the ciphers that should be offered
17086                 during SSL negotiation. You should not set this variable unless
17087                 you know what you are doing.</P
17088 ></DD
17089 ><DT
17090 ><A
17091 NAME="SSLCLIENTCERT"
17092 ></A
17093 >ssl client cert (G)</DT
17094 ><DD
17095 ><P
17096 >This variable is part of SSL-enabled Samba. This
17097                 is only available if the SSL libraries have been compiled on your
17098                 system and the configure option <B
17099 CLASS="COMMAND"
17100 >--with-ssl</B
17101 > was
17102                 given at configure time.</P
17103 ><P
17104 >The certificate in this file is used by <A
17105 HREF="smbclient.1.html"
17106 TARGET="_top"
17107 >               <B
17108 CLASS="COMMAND"
17109 >smbclient(1)</B
17110 ></A
17111 > if it exists. It's needed
17112                 if the server requires a client certificate.</P
17113 ><P
17114 >Default: <B
17115 CLASS="COMMAND"
17116 >ssl client cert = /usr/local/ssl/certs/smbclient.pem
17117                 </B
17118 ></P
17119 ></DD
17120 ><DT
17121 ><A
17122 NAME="SSLCLIENTKEY"
17123 ></A
17124 >ssl client key (G)</DT
17125 ><DD
17126 ><P
17127 >This variable is part of SSL-enabled Samba. This
17128                 is only available if the SSL libraries have been compiled on your
17129                 system and the configure option <B
17130 CLASS="COMMAND"
17131 >--with-ssl</B
17132 > was
17133                 given at configure time.</P
17134 ><P
17135 >This is the private key for <A
17136 HREF="smbclient.1.html"
17137 TARGET="_top"
17138 >               <B
17139 CLASS="COMMAND"
17140 >smbclient(1)</B
17141 ></A
17142 >. It's only needed if the
17143                 client should have a certificate. </P
17144 ><P
17145 >Default: <B
17146 CLASS="COMMAND"
17147 >ssl client key = /usr/local/ssl/private/smbclient.pem
17148                 </B
17149 ></P
17150 ></DD
17151 ><DT
17152 ><A
17153 NAME="SSLCOMPATIBILITY"
17154 ></A
17155 >ssl compatibility (G)</DT
17156 ><DD
17157 ><P
17158 >This variable is part of SSL-enabled Samba. This
17159                 is only available if the SSL libraries have been compiled on your
17160                 system and the configure option <B
17161 CLASS="COMMAND"
17162 >--with-ssl</B
17163 > was
17164                 given at configure time.</P
17165 ><P
17166 >This variable defines whether OpenSSL should be configured
17167                 for bug compatibility with other SSL implementations. This is
17168                 probably not desirable because currently no clients with SSL
17169                 implementations other than OpenSSL exist.</P
17170 ><P
17171 >Default: <B
17172 CLASS="COMMAND"
17173 >ssl compatibility = no</B
17174 ></P
17175 ></DD
17176 ><DT
17177 ><A
17178 NAME="SSLEGDSOCKET"
17179 ></A
17180 >ssl egd socket (G)</DT
17181 ><DD
17182 ><P
17183 >This variable is part of SSL-enabled Samba. This
17184                 is only available if the SSL libraries have been compiled on your
17185                 system and the configure option <B
17186 CLASS="COMMAND"
17187 >--with-ssl</B
17188 > was
17189                 given at configure time.</P
17190 ><P
17191 >               This option is used to define the location of the communiation socket of
17192                 an EGD or PRNGD daemon, from which entropy can be retrieved. This option
17193                 can be used instead of or together with the <A
17194 HREF="#SSLENTROPYFILE"
17195 ><TT
17196 CLASS="PARAMETER"
17197 ><I
17198 >ssl entropy file</I
17199 ></TT
17200 ></A
17201 >
17202                 directive. 255 bytes of entropy will be retrieved from the daemon.
17203                 </P
17204 ><P
17205 >Default: <EM
17206 >none</EM
17207 ></P
17208 ></DD
17209 ><DT
17210 ><A
17211 NAME="SSLENTROPYBYTES"
17212 ></A
17213 >ssl entropy bytes (G)</DT
17214 ><DD
17215 ><P
17216 >This variable is part of SSL-enabled Samba. This
17217                 is only available if the SSL libraries have been compiled on your
17218                 system and the configure option <B
17219 CLASS="COMMAND"
17220 >--with-ssl</B
17221 > was
17222                 given at configure time.</P
17223 ><P
17224 >               This parameter is used to define the number of bytes which should
17225                 be read from the <A
17226 HREF="#SSLENTROPYFILE"
17227 ><TT
17228 CLASS="PARAMETER"
17229 ><I
17230 >ssl entropy
17231                 file</I
17232 ></TT
17233 ></A
17234 > If a -1 is specified, the entire file will
17235                 be read.
17236                 </P
17237 ><P
17238 >Default: <B
17239 CLASS="COMMAND"
17240 >ssl entropy bytes = 255</B
17241 ></P
17242 ></DD
17243 ><DT
17244 ><A
17245 NAME="SSLENTROPYFILE"
17246 ></A
17247 >ssl entropy file (G)</DT
17248 ><DD
17249 ><P
17250 >This variable is part of SSL-enabled Samba. This
17251                 is only available if the SSL libraries have been compiled on your
17252                 system and the configure option <B
17253 CLASS="COMMAND"
17254 >--with-ssl</B
17255 > was
17256                 given at configure time.</P
17257 ><P
17258 >               This parameter is used to specify a file from which processes will
17259                 read "random bytes" on startup.  In order to seed the internal pseudo
17260                 random number generator, entropy must be provided. On system with a
17261                 <TT
17262 CLASS="FILENAME"
17263 >/dev/urandom</TT
17264 > device file, the processes
17265                 will retrieve its entropy from the kernel. On systems without kernel
17266                 entropy support, a file can be supplied that will be read on startup
17267                 and that will be used to seed the PRNG.
17268                 </P
17269 ><P
17270 >Default: <EM
17271 >none</EM
17272 ></P
17273 ></DD
17274 ><DT
17275 ><A
17276 NAME="SSLHOSTS"
17277 ></A
17278 >ssl hosts (G)</DT
17279 ><DD
17280 ><P
17281 >See <A
17282 HREF="#SSLHOSTSRESIGN"
17283 ><TT
17284 CLASS="PARAMETER"
17285 ><I
17286 >               ssl hosts resign</I
17287 ></TT
17288 ></A
17289 >.</P
17290 ></DD
17291 ><DT
17292 ><A
17293 NAME="SSLHOSTSRESIGN"
17294 ></A
17295 >ssl hosts resign (G)</DT
17296 ><DD
17297 ><P
17298 >This variable is part of SSL-enabled Samba. This
17299                 is only available if the SSL libraries have been compiled on your
17300                 system and the configure option <B
17301 CLASS="COMMAND"
17302 >--with-ssl</B
17303 > was
17304                 given at configure time.</P
17305 ><P
17306 >These two variables define whether Samba will go
17307                 into SSL mode or not. If none of them is defined, Samba will
17308                 allow only SSL connections. If the <A
17309 HREF="#SSLHOSTS"
17310 >               <TT
17311 CLASS="PARAMETER"
17312 ><I
17313 >ssl hosts</I
17314 ></TT
17315 ></A
17316 > variable lists
17317                 hosts (by IP-address, IP-address range, net group or name),
17318                 only these hosts will be forced into SSL mode. If the <TT
17319 CLASS="PARAMETER"
17320 ><I
17321 >               ssl hosts resign</I
17322 ></TT
17323 > variable lists hosts, only these
17324                 hosts will <EM
17325 >NOT</EM
17326 > be forced into SSL mode. The syntax for these two
17327                 variables is the same as for the <A
17328 HREF="#HOSTSALLOW"
17329 ><TT
17330 CLASS="PARAMETER"
17331 ><I
17332 >               hosts allow</I
17333 ></TT
17334 ></A
17335 > and <A
17336 HREF="#HOSTSDENY"
17337 >               <TT
17338 CLASS="PARAMETER"
17339 ><I
17340 >hosts deny</I
17341 ></TT
17342 ></A
17343 > pair of variables, only
17344                 that the subject of the decision is different: It's not the access
17345                 right but whether SSL is used or not. </P
17346 ><P
17347 >The example below requires SSL connections from all hosts
17348                 outside the local net (which is 192.168.*.*).</P
17349 ><P
17350 >Default: <B
17351 CLASS="COMMAND"
17352 >ssl hosts = &#60;empty string&#62;</B
17353 ></P
17354 ><P
17355 ><B
17356 CLASS="COMMAND"
17357 >ssl hosts resign = &#60;empty string&#62;</B
17358 ></P
17359 ><P
17360 >Example: <B
17361 CLASS="COMMAND"
17362 >ssl hosts resign = 192.168.</B
17363 ></P
17364 ></DD
17365 ><DT
17366 ><A
17367 NAME="SSLREQUIRECLIENTCERT"
17368 ></A
17369 >ssl require clientcert (G)</DT
17370 ><DD
17371 ><P
17372 >This variable is part of SSL-enabled Samba. This
17373                 is only available if the SSL libraries have been compiled on your
17374                 system and the configure option <B
17375 CLASS="COMMAND"
17376 >--with-ssl</B
17377 > was
17378                 given at configure time.</P
17379 ><P
17380 >If this variable is set to <TT
17381 CLASS="CONSTANT"
17382 >yes</TT
17383 >, the
17384                 server will not tolerate connections from clients that don't
17385                 have a valid certificate. The directory/file given in <A
17386 HREF="#SSLCACERTDIR"
17387 ><TT
17388 CLASS="PARAMETER"
17389 ><I
17390 >ssl CA certDir</I
17391 ></TT
17392 >
17393                 </A
17394 > and <A
17395 HREF="#SSLCACERTFILE"
17396 ><TT
17397 CLASS="PARAMETER"
17398 ><I
17399 >ssl CA certFile
17400                 </I
17401 ></TT
17402 ></A
17403 > will be used to look up the CAs that issued
17404                 the client's certificate. If the certificate can't be verified
17405                 positively, the connection will be terminated.  If this variable
17406                 is set to <TT
17407 CLASS="CONSTANT"
17408 >no</TT
17409 >, clients don't need certificates.
17410                 Contrary to web applications you really <EM
17411 >should</EM
17412 >
17413                 require client certificates. In the web environment the client's
17414                 data is sensitive (credit card numbers) and the server must prove
17415                 to be trustworthy. In a file server environment the server's data
17416                 will be sensitive and the clients must prove to be trustworthy.</P
17417 ><P
17418 >Default: <B
17419 CLASS="COMMAND"
17420 >ssl require clientcert = no</B
17421 ></P
17422 ></DD
17423 ><DT
17424 ><A
17425 NAME="SSLREQUIRESERVERCERT"
17426 ></A
17427 >ssl require servercert (G)</DT
17428 ><DD
17429 ><P
17430 >This variable is part of SSL-enabled Samba. This
17431                 is only available if the SSL libraries have been compiled on your
17432                 system and the configure option <B
17433 CLASS="COMMAND"
17434 >--with-ssl</B
17435 > was
17436                 given at configure time.</P
17437 ><P
17438 >If this variable is set to <TT
17439 CLASS="CONSTANT"
17440 >yes</TT
17441 >, the
17442                 <A
17443 HREF="smbclient.1.html"
17444 TARGET="_top"
17445 ><B
17446 CLASS="COMMAND"
17447 >smbclient(1)</B
17448 >
17449                 </A
17450 > will request a certificate from the server. Same as
17451                 <A
17452 HREF="#SSLREQUIRECLIENTCERT"
17453 ><TT
17454 CLASS="PARAMETER"
17455 ><I
17456 >ssl require
17457                 clientcert</I
17458 ></TT
17459 ></A
17460 > for the server.</P
17461 ><P
17462 >Default: <B
17463 CLASS="COMMAND"
17464 >ssl require servercert = no</B
17465 >
17466                 </P
17467 ></DD
17468 ><DT
17469 ><A
17470 NAME="SSLSERVERCERT"
17471 ></A
17472 >ssl server cert (G)</DT
17473 ><DD
17474 ><P
17475 >This variable is part of SSL-enabled Samba. This
17476                 is only available if the SSL libraries have been compiled on your
17477                 system and the configure option <B
17478 CLASS="COMMAND"
17479 >--with-ssl</B
17480 > was
17481                 given at configure time.</P
17482 ><P
17483 >This is the file containing the server's certificate.
17484                 The server <EM
17485 >must</EM
17486 > have a certificate. The
17487                 file may also contain the server's private key. See later for
17488                 how certificates and private keys are created.</P
17489 ><P
17490 >Default: <B
17491 CLASS="COMMAND"
17492 >ssl server cert = &#60;empty string&#62;
17493                 </B
17494 ></P
17495 ></DD
17496 ><DT
17497 ><A
17498 NAME="SSLSERVERKEY"
17499 ></A
17500 >ssl server key (G)</DT
17501 ><DD
17502 ><P
17503 >This variable is part of SSL-enabled Samba. This
17504                 is only available if the SSL libraries have been compiled on your
17505                 system and the configure option <B
17506 CLASS="COMMAND"
17507 >--with-ssl</B
17508 > was
17509                 given at configure time.</P
17510 ><P
17511 >This file contains the private key of the server. If
17512                 this variable is not defined, the key is looked up in the
17513                 certificate file (it may be appended to the certificate).
17514                 The server <EM
17515 >must</EM
17516 > have a private key
17517                 and the certificate <EM
17518 >must</EM
17519 >
17520                 match this private key.</P
17521 ><P
17522 >Default: <B
17523 CLASS="COMMAND"
17524 >ssl server key = &#60;empty string&#62;
17525                 </B
17526 ></P
17527 ></DD
17528 ><DT
17529 ><A
17530 NAME="SSLVERSION"
17531 ></A
17532 >ssl version (G)</DT
17533 ><DD
17534 ><P
17535 >This variable is part of SSL-enabled Samba. This
17536                 is only available if the SSL libraries have been compiled on your
17537                 system and the configure option <B
17538 CLASS="COMMAND"
17539 >--with-ssl</B
17540 > was
17541                 given at configure time.</P
17542 ><P
17543 >This enumeration variable defines the versions of the
17544                 SSL protocol that will be used. <TT
17545 CLASS="CONSTANT"
17546 >ssl2or3</TT
17547 > allows
17548                 dynamic negotiation of SSL v2 or v3, <TT
17549 CLASS="CONSTANT"
17550 >ssl2</TT
17551 > results
17552                 in SSL v2, <TT
17553 CLASS="CONSTANT"
17554 >ssl3</TT
17555 > results in SSL v3 and
17556                 <TT
17557 CLASS="CONSTANT"
17558 >tls1</TT
17559 > results in TLS v1. TLS (Transport Layer
17560                 Security) is the new standard for SSL.</P
17561 ><P
17562 >Default: <B
17563 CLASS="COMMAND"
17564 >ssl version = "ssl2or3"</B
17565 ></P
17566 ></DD
17567 ><DT
17568 ><A
17569 NAME="STATCACHE"
17570 ></A
17571 >stat cache (G)</DT
17572 ><DD
17573 ><P
17574 >This parameter determines if <A
17575 HREF="smbd.8.html"
17576 TARGET="_top"
17577 >smbd(8)</A
17578 > will use a cache in order to
17579                 speed up case insensitive name mappings. You should never need
17580                 to change this parameter.</P
17581 ><P
17582 >Default: <B
17583 CLASS="COMMAND"
17584 >stat cache = yes</B
17585 ></P
17586 ></DD
17587 ><DT
17588 ><A
17589 NAME="STATCACHESIZE"
17590 ></A
17591 >stat cache size (G)</DT
17592 ><DD
17593 ><P
17594 >This parameter determines the number of
17595                 entries in the <TT
17596 CLASS="PARAMETER"
17597 ><I
17598 >stat cache</I
17599 ></TT
17600 >.  You should
17601                 never need to change this parameter.</P
17602 ><P
17603 >Default: <B
17604 CLASS="COMMAND"
17605 >stat cache size = 50</B
17606 ></P
17607 ></DD
17608 ><DT
17609 ><A
17610 NAME="STATUS"
17611 ></A
17612 >status (G)</DT
17613 ><DD
17614 ><P
17615 >This enables or disables logging of connections
17616                 to a status file that <A
17617 HREF="smbstatus.1.html"
17618 TARGET="_top"
17619 >smbstatus(1)</A
17620 >
17621                 can read.</P
17622 ><P
17623 >With this disabled <B
17624 CLASS="COMMAND"
17625 >smbstatus</B
17626 > won't be able
17627                 to tell you what connections are active. You should never need to
17628                 change this parameter.</P
17629 ><P
17630 >Default: <B
17631 CLASS="COMMAND"
17632 >status = yes</B
17633 ></P
17634 ></DD
17635 ><DT
17636 ><A
17637 NAME="STRICTALLOCATE"
17638 ></A
17639 >strict allocate (S)</DT
17640 ><DD
17641 ><P
17642 >This is a boolean that controls the handling of
17643                 disk space allocation in the server. When this is set to <TT
17644 CLASS="CONSTANT"
17645 >yes</TT
17646 >
17647                 the server will change from UNIX behaviour of not committing real
17648                 disk storage blocks when a file is extended to the Windows behaviour
17649                 of actually forcing the disk system to allocate real storage blocks
17650                 when a file is created or extended to be a given size. In UNIX
17651                 terminology this means that Samba will stop creating sparse files.
17652                 This can be slow on some systems.</P
17653 ><P
17654 >When strict allocate is <TT
17655 CLASS="CONSTANT"
17656 >no</TT
17657 > the server does sparse
17658                 disk block allocation when a file is extended.</P
17659 ><P
17660 >Setting this to <TT
17661 CLASS="CONSTANT"
17662 >yes</TT
17663 > can help Samba return
17664                 out of quota messages on systems that are restricting the disk quota
17665                 of users.</P
17666 ><P
17667 >Default: <B
17668 CLASS="COMMAND"
17669 >strict allocate = no</B
17670 ></P
17671 ></DD
17672 ><DT
17673 ><A
17674 NAME="STRICTLOCKING"
17675 ></A
17676 >strict locking (S)</DT
17677 ><DD
17678 ><P
17679 >This is a boolean that controls the handling of
17680                 file locking in the server. When this is set to <TT
17681 CLASS="CONSTANT"
17682 >yes</TT
17683 >
17684                 the server will check every read and write access for file locks, and
17685                 deny access if locks exist. This can be slow on some systems.</P
17686 ><P
17687 >When strict locking is <TT
17688 CLASS="CONSTANT"
17689 >no</TT
17690 > the server does file
17691                 lock checks only when the client explicitly asks for them.</P
17692 ><P
17693 >Well-behaved clients always ask for lock checks when it
17694                 is important, so in the vast majority of cases <B
17695 CLASS="COMMAND"
17696 >strict
17697                 locking = no</B
17698 > is preferable.</P
17699 ><P
17700 >Default: <B
17701 CLASS="COMMAND"
17702 >strict locking = no</B
17703 ></P
17704 ></DD
17705 ><DT
17706 ><A
17707 NAME="STRICTSYNC"
17708 ></A
17709 >strict sync (S)</DT
17710 ><DD
17711 ><P
17712 >Many Windows applications (including the Windows
17713                 98 explorer shell) seem to confuse flushing buffer contents to
17714                 disk with doing a sync to disk. Under UNIX, a sync call forces
17715                 the process to be suspended until the kernel has ensured that
17716                 all outstanding data in kernel disk buffers has been safely stored
17717                 onto stable storage. This is very slow and should only be done
17718                 rarely. Setting this parameter to <TT
17719 CLASS="CONSTANT"
17720 >no</TT
17721 > (the
17722                 default) means that <A
17723 HREF="smbd.8.html"
17724 TARGET="_top"
17725 >smbd</A
17726 > ignores the Windows applications requests for
17727                 a sync call. There is only a possibility of losing data if the
17728                 operating system itself that Samba is running on crashes, so there is
17729                 little danger in this default setting. In addition, this fixes many
17730                 performance problems that people have reported with the new Windows98
17731                 explorer shell file copies.</P
17732 ><P
17733 >See also the <A
17734 HREF="#SYNCALWAYS"
17735 ><TT
17736 CLASS="PARAMETER"
17737 ><I
17738 >sync
17739                 always&#62;</I
17740 ></TT
17741 ></A
17742 > parameter.</P
17743 ><P
17744 >Default: <B
17745 CLASS="COMMAND"
17746 >strict sync = no</B
17747 ></P
17748 ></DD
17749 ><DT
17750 ><A
17751 NAME="STRIPDOT"
17752 ></A
17753 >strip dot (G)</DT
17754 ><DD
17755 ><P
17756 >This parameter is now unused in Samba (2.2.5 and above).
17757                 It used strip trailing dots off UNIX filenames but was not correctly implmented.
17758                 In Samba 2.2.5 and above UNIX filenames ending in a dot are invalid Windows long
17759                 filenames (as they are in Windows NT and above) and are mangled to 8.3 before
17760                 being returned to a client.</P
17761 ><P
17762 >Default: <B
17763 CLASS="COMMAND"
17764 >strip dot = no</B
17765 ></P
17766 ></DD
17767 ><DT
17768 ><A
17769 NAME="SYNCALWAYS"
17770 ></A
17771 >sync always (S)</DT
17772 ><DD
17773 ><P
17774 >This is a boolean parameter that controls
17775                 whether writes will always be written to stable storage before
17776                 the write call returns. If this is <TT
17777 CLASS="CONSTANT"
17778 >no</TT
17779 > then the server will be
17780                 guided by the client's request in each write call (clients can
17781                 set a bit indicating that a particular write should be synchronous).
17782                 If this is <TT
17783 CLASS="CONSTANT"
17784 >yes</TT
17785 > then every write will be followed by a <B
17786 CLASS="COMMAND"
17787 >fsync()
17788                 </B
17789 > call to ensure the data is written to disk. Note that
17790                 the <TT
17791 CLASS="PARAMETER"
17792 ><I
17793 >strict sync</I
17794 ></TT
17795 > parameter must be set to
17796                 <TT
17797 CLASS="CONSTANT"
17798 >yes</TT
17799 > in order for this parameter to have
17800                 any affect.</P
17801 ><P
17802 >See also the <A
17803 HREF="#STRICTSYNC"
17804 ><TT
17805 CLASS="PARAMETER"
17806 ><I
17807 >strict
17808                 sync</I
17809 ></TT
17810 ></A
17811 > parameter.</P
17812 ><P
17813 >Default: <B
17814 CLASS="COMMAND"
17815 >sync always = no</B
17816 ></P
17817 ></DD
17818 ><DT
17819 ><A
17820 NAME="SYSLOG"
17821 ></A
17822 >syslog (G)</DT
17823 ><DD
17824 ><P
17825 >This parameter maps how Samba debug messages
17826                 are logged onto the system syslog logging levels. Samba debug
17827                 level zero maps onto syslog <TT
17828 CLASS="CONSTANT"
17829 >LOG_ERR</TT
17830 >, debug
17831                 level one maps onto <TT
17832 CLASS="CONSTANT"
17833 >LOG_WARNING</TT
17834 >, debug level
17835                 two maps onto <TT
17836 CLASS="CONSTANT"
17837 >LOG_NOTICE</TT
17838 >, debug level three
17839                 maps onto LOG_INFO. All higher levels are mapped to <TT
17840 CLASS="CONSTANT"
17841 >               LOG_DEBUG</TT
17842 >.</P
17843 ><P
17844 >This parameter sets the threshold for sending messages
17845                 to syslog.  Only messages with debug level less than this value
17846                 will be sent to syslog.</P
17847 ><P
17848 >Default: <B
17849 CLASS="COMMAND"
17850 >syslog = 1</B
17851 ></P
17852 ></DD
17853 ><DT
17854 ><A
17855 NAME="SYSLOGONLY"
17856 ></A
17857 >syslog only (G)</DT
17858 ><DD
17859 ><P
17860 >If this parameter is set then Samba debug
17861                 messages are logged into the system syslog only, and not to
17862                 the debug log files.</P
17863 ><P
17864 >Default: <B
17865 CLASS="COMMAND"
17866 >syslog only = no</B
17867 ></P
17868 ></DD
17869 ><DT
17870 ><A
17871 NAME="TEMPLATEHOMEDIR"
17872 ></A
17873 >template homedir (G)</DT
17874 ><DD
17875 ><P
17876 >When filling out the user information for a Windows NT
17877                 user, the <A
17878 HREF="winbindd.8.html"
17879 TARGET="_top"
17880 >winbindd(8)</A
17881 > daemon
17882                 uses this parameter to fill in the home directory for that user.
17883                 If the string <TT
17884 CLASS="PARAMETER"
17885 ><I
17886 >%D</I
17887 ></TT
17888 > is present it is substituted
17889                 with the user's Windows NT domain name.  If the string <TT
17890 CLASS="PARAMETER"
17891 ><I
17892 >%U
17893                 </I
17894 ></TT
17895 > is present it is substituted with the user's Windows
17896                 NT user name.</P
17897 ><P
17898 >Default: <B
17899 CLASS="COMMAND"
17900 >template homedir = /home/%D/%U</B
17901 ></P
17902 ></DD
17903 ><DT
17904 ><A
17905 NAME="TEMPLATESHELL"
17906 ></A
17907 >template shell (G)</DT
17908 ><DD
17909 ><P
17910 >When filling out the user information for a Windows NT
17911                 user, the <A
17912 HREF="winbindd.8.html"
17913 TARGET="_top"
17914 >winbindd(8)</A
17915 > daemon
17916                 uses this parameter to fill in the login shell for that user.</P
17917 ><P
17918 >Default: <B
17919 CLASS="COMMAND"
17920 >template shell = /bin/false</B
17921 ></P
17922 ></DD
17923 ><DT
17924 ><A
17925 NAME="TIMEOFFSET"
17926 ></A
17927 >time offset (G)</DT
17928 ><DD
17929 ><P
17930 >This parameter is a setting in minutes to add
17931                 to the normal GMT to local time conversion. This is useful if
17932                 you are serving a lot of PCs that have incorrect daylight
17933                 saving time handling.</P
17934 ><P
17935 >Default: <B
17936 CLASS="COMMAND"
17937 >time offset = 0</B
17938 ></P
17939 ><P
17940 >Example: <B
17941 CLASS="COMMAND"
17942 >time offset = 60</B
17943 ></P
17944 ></DD
17945 ><DT
17946 ><A
17947 NAME="TIMESERVER"
17948 ></A
17949 >time server (G)</DT
17950 ><DD
17951 ><P
17952 >This parameter determines if <A
17953 HREF="nmbd.8.html"
17954 TARGET="_top"
17955 >
17956                 nmbd(8)</A
17957 > advertises itself as a time server to Windows
17958                 clients.</P
17959 ><P
17960 >Default: <B
17961 CLASS="COMMAND"
17962 >time server = no</B
17963 ></P
17964 ></DD
17965 ><DT
17966 ><A
17967 NAME="TIMESTAMPLOGS"
17968 ></A
17969 >timestamp logs (G)</DT
17970 ><DD
17971 ><P
17972 >Synonym for <A
17973 HREF="#DEBUGTIMESTAMP"
17974 ><TT
17975 CLASS="PARAMETER"
17976 ><I
17977 >               debug timestamp</I
17978 ></TT
17979 ></A
17980 >.</P
17981 ></DD
17982 ><DT
17983 ><A
17984 NAME="TOTALPRINTJOBS"
17985 ></A
17986 >total print jobs (G)</DT
17987 ><DD
17988 ><P
17989 >This parameter accepts an integer value which defines
17990                 a limit on the maximum number of print jobs that will be accepted
17991                 system wide at any given time.  If a print job is submitted
17992                 by a client which will exceed this number, then <A
17993 HREF="smbd.8.html"
17994 TARGET="_top"
17995 >smbd</A
17996 > will return an
17997                 error indicating that no space is available on the server.  The
17998                 default value of 0 means that no such limit exists.  This parameter
17999                 can be used to prevent a server from exceeding its capacity and is
18000                 designed as a printing throttle.  See also
18001                 <A
18002 HREF="#MAXPRINTJOBS"
18003 ><TT
18004 CLASS="PARAMETER"
18005 ><I
18006 >max print jobs</I
18007 ></TT
18008 ></A
18009 >.
18010                 </P
18011 ><P
18012 >Default: <B
18013 CLASS="COMMAND"
18014 >total print jobs = 0</B
18015 ></P
18016 ><P
18017 >Example: <B
18018 CLASS="COMMAND"
18019 >total print jobs = 5000</B
18020 ></P
18021 ></DD
18022 ><DT
18023 ><A
18024 NAME="UNIXEXTENSIONS"
18025 ></A
18026 >unix extensions(G)</DT
18027 ><DD
18028 ><P
18029 >This boolean parameter controls whether Samba
18030                 implments the CIFS UNIX extensions, as defined by HP.
18031                 These extensions enable Samba to better serve UNIX CIFS clients
18032                 by supporting features such as symbolic links, hard links, etc...
18033                 These extensions require a similarly enabled client, and are of
18034                 no current use to Windows clients.</P
18035 ><P
18036 >Default: <B
18037 CLASS="COMMAND"
18038 >unix extensions = no</B
18039 ></P
18040 ></DD
18041 ><DT
18042 ><A
18043 NAME="UNIXPASSWORDSYNC"
18044 ></A
18045 >unix password sync (G)</DT
18046 ><DD
18047 ><P
18048 >This boolean parameter controls whether Samba
18049                 attempts to synchronize the UNIX password with the SMB password
18050                 when the encrypted SMB password in the smbpasswd file is changed.
18051                 If this is set to <TT
18052 CLASS="CONSTANT"
18053 >yes</TT
18054 > the program specified in the <TT
18055 CLASS="PARAMETER"
18056 ><I
18057 >passwd
18058                 program</I
18059 ></TT
18060 >parameter is called <EM
18061 >AS ROOT</EM
18062 > -
18063                 to allow the new UNIX password to be set without access to the
18064                 old UNIX password (as the SMB password change code has no
18065                 access to the old password cleartext, only the new).</P
18066 ><P
18067 >See also <A
18068 HREF="#PASSWDPROGRAM"
18069 ><TT
18070 CLASS="PARAMETER"
18071 ><I
18072 >passwd
18073                 program</I
18074 ></TT
18075 ></A
18076 >, <A
18077 HREF="#PASSWDCHAT"
18078 ><TT
18079 CLASS="PARAMETER"
18080 ><I
18081 >               passwd chat</I
18082 ></TT
18083 ></A
18084 >.</P
18085 ><P
18086 >Default: <B
18087 CLASS="COMMAND"
18088 >unix password sync = no</B
18089 ></P
18090 ></DD
18091 ><DT
18092 ><A
18093 NAME="UPDATEENCRYPTED"
18094 ></A
18095 >update encrypted (G)</DT
18096 ><DD
18097 ><P
18098 >This boolean parameter allows a user logging
18099                 on with a plaintext password to have their encrypted (hashed)
18100                 password in the smbpasswd file to be updated automatically as
18101                 they log on. This option allows a site to migrate from plaintext
18102                 password authentication (users authenticate with plaintext
18103                 password over the wire, and are checked against a UNIX account
18104                 database) to encrypted password authentication (the SMB
18105                 challenge/response authentication mechanism) without forcing
18106                 all users to re-enter their passwords via smbpasswd at the time the
18107                 change is made. This is a convenience option to allow the change over
18108                 to encrypted passwords to be made over a longer period. Once all users
18109                 have encrypted representations of their passwords in the smbpasswd
18110                 file this parameter should be set to <TT
18111 CLASS="CONSTANT"
18112 >no</TT
18113 >.</P
18114 ><P
18115 >In order for this parameter to work correctly the <A
18116 HREF="#ENCRYPTPASSWORDS"
18117 ><TT
18118 CLASS="PARAMETER"
18119 ><I
18120 >encrypt passwords</I
18121 ></TT
18122 >
18123                 </A
18124 > parameter must be set to <TT
18125 CLASS="CONSTANT"
18126 >no</TT
18127 > when
18128                 this parameter is set to <TT
18129 CLASS="CONSTANT"
18130 >yes</TT
18131 >.</P
18132 ><P
18133 >Note that even when this parameter is set a user
18134                 authenticating to <B
18135 CLASS="COMMAND"
18136 >smbd</B
18137 > must still enter a valid
18138                 password in order to connect correctly, and to update their hashed
18139                 (smbpasswd) passwords.</P
18140 ><P
18141 >Default: <B
18142 CLASS="COMMAND"
18143 >update encrypted = no</B
18144 ></P
18145 ></DD
18146 ><DT
18147 ><A
18148 NAME="USECLIENTDRIVER"
18149 ></A
18150 >use client driver (S)</DT
18151 ><DD
18152 ><P
18153 >This parameter applies only to Windows NT/2000
18154                 clients.  It has no affect on Windows 95/98/ME clients.  When
18155                 serving a printer to Windows NT/2000 clients without first installing
18156                 a valid printer driver on the Samba host, the client will be required
18157                 to install a local printer driver.  From this point on, the client
18158                 will treat the print as a local printer and not a network printer
18159                 connection.  This is much the same behavior that will occur
18160                 when <B
18161 CLASS="COMMAND"
18162 >disable spoolss = yes</B
18163 >.  </P
18164 ><P
18165 >The differentiating
18166                 factor is that under normal circumstances, the NT/2000 client will
18167                 attempt to open the network printer using MS-RPC.  The problem is that
18168                 because the client considers the printer to be local, it will attempt
18169                 to issue the OpenPrinterEx() call requesting access rights associated
18170                 with the logged on user. If the user possesses local administator rights
18171                 but not root privilegde on the Samba host (often the case), the OpenPrinterEx()
18172                 call will fail.  The result is that the client will now display an "Access
18173                 Denied; Unable to connect" message in the printer queue window (even though
18174                 jobs may successfully be printed).  </P
18175 ><P
18176 >If this parameter is enabled for a printer, then any attempt
18177                 to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
18178                 to PRINTER_ACCESS_USE instead.  Thus allowing the OpenPrinterEx()
18179                 call to succeed.  <EM
18180 >This parameter MUST not be able enabled
18181                 on a print share which has valid print driver installed on the Samba
18182                 server.</EM
18183 ></P
18184 ><P
18185 >See also <A
18186 HREF="#DISABLESPOOLSS"
18187 >disable spoolss</A
18188 >
18189                 </P
18190 ><P
18191 >Default: <B
18192 CLASS="COMMAND"
18193 >use client driver = no</B
18194 ></P
18195 ></DD
18196 ><DT
18197 ><A
18198 NAME="USEMMAP"
18199 ></A
18200 >use mmap (G)</DT
18201 ><DD
18202 ><P
18203 >This global parameter determines if the tdb internals of Samba can
18204                 depend on mmap working correctly on the running system. Samba requires a coherent
18205                 mmap/read-write system memory cache. Currently only HPUX does not have such a
18206                 coherent cache, and so this parameter is set to <TT
18207 CLASS="CONSTANT"
18208 >no</TT
18209 > by
18210                 default on HPUX. On all other systems this parameter should be left alone. This
18211                 parameter is provided to help the Samba developers track down problems with
18212                 the tdb internal code.
18213                 </P
18214 ><P
18215 >Default: <B
18216 CLASS="COMMAND"
18217 >use mmap = yes</B
18218 ></P
18219 ></DD
18220 ><DT
18221 ><A
18222 NAME="USERHOSTS"
18223 ></A
18224 >use rhosts (G)</DT
18225 ><DD
18226 ><P
18227 >If this global parameter is <TT
18228 CLASS="CONSTANT"
18229 >yes</TT
18230 >, it specifies
18231                 that the UNIX user's <TT
18232 CLASS="FILENAME"
18233 >.rhosts</TT
18234 > file in their home directory
18235                 will be read to find the names of hosts and users who will be allowed
18236                 access without specifying a password.</P
18237 ><P
18238 ><EM
18239 >NOTE:</EM
18240 > The use of <TT
18241 CLASS="PARAMETER"
18242 ><I
18243 >use rhosts
18244                 </I
18245 ></TT
18246 > can be a major security hole. This is because you are
18247                 trusting the PC to supply the correct username. It is very easy to
18248                 get a PC to supply a false username. I recommend that the <TT
18249 CLASS="PARAMETER"
18250 ><I
18251 >               use rhosts</I
18252 ></TT
18253 > option be only used if you really know what
18254                 you are doing.</P
18255 ><P
18256 >Default: <B
18257 CLASS="COMMAND"
18258 >use rhosts = no</B
18259 ></P
18260 ></DD
18261 ><DT
18262 ><A
18263 NAME="USESENDFILE"
18264 ></A
18265 >use sendfile (S)</DT
18266 ><DD
18267 ><P
18268 >If this parameter is <TT
18269 CLASS="CONSTANT"
18270 >yes</TT
18271 >, and Samba
18272                 was built with the --with-sendfile-support option, and the underlying operating
18273                 system supports sendfile system call, then some SMB read calls (mainly ReadAndX
18274                 and ReadRaw) will use the more efficient sendfile system call for files that
18275                 are exclusively oplocked. This may make more efficient use of the system CPU's
18276                 and cause Samba to be faster. This is off by default as it's effects are unknown
18277                 as yet.
18278                 </P
18279 ><P
18280 >Default: <B
18281 CLASS="COMMAND"
18282 >use sendfile = no</B
18283 ></P
18284 ></DD
18285 ><DT
18286 ><A
18287 NAME="USER"
18288 ></A
18289 >user (S)</DT
18290 ><DD
18291 ><P
18292 >Synonym for <A
18293 HREF="#USERNAME"
18294 ><TT
18295 CLASS="PARAMETER"
18296 ><I
18297 >               username</I
18298 ></TT
18299 ></A
18300 >.</P
18301 ></DD
18302 ><DT
18303 ><A
18304 NAME="USERS"
18305 ></A
18306 >users (S)</DT
18307 ><DD
18308 ><P
18309 >Synonym for <A
18310 HREF="#USERNAME"
18311 ><TT
18312 CLASS="PARAMETER"
18313 ><I
18314 >               username</I
18315 ></TT
18316 ></A
18317 >.</P
18318 ></DD
18319 ><DT
18320 ><A
18321 NAME="USERNAME"
18322 ></A
18323 >username (S)</DT
18324 ><DD
18325 ><P
18326 >Multiple users may be specified in a comma-delimited
18327                 list, in which case the supplied password will be tested against
18328                 each username in turn (left to right).</P
18329 ><P
18330 >The <TT
18331 CLASS="PARAMETER"
18332 ><I
18333 >username</I
18334 ></TT
18335 > line is needed only when
18336                 the PC is unable to supply its own username. This is the case
18337                 for the COREPLUS protocol or where your users have different WfWg
18338                 usernames to UNIX usernames. In both these cases you may also be
18339                 better using the \\server\share%user syntax instead.</P
18340 ><P
18341 >The <TT
18342 CLASS="PARAMETER"
18343 ><I
18344 >username</I
18345 ></TT
18346 > line is not a great
18347                 solution in many cases as it means Samba will try to validate
18348                 the supplied password against each of the usernames in the
18349                 <TT
18350 CLASS="PARAMETER"
18351 ><I
18352 >username</I
18353 ></TT
18354 > line in turn. This is slow and
18355                 a bad idea for lots of users in case of duplicate passwords.
18356                 You may get timeouts or security breaches using this parameter
18357                 unwisely.</P
18358 ><P
18359 >Samba relies on the underlying UNIX security. This
18360                 parameter does not restrict who can login, it just offers hints
18361                 to the Samba server as to what usernames might correspond to the
18362                 supplied password. Users can login as whoever they please and
18363                 they will be able to do no more damage than if they started a
18364                 telnet session. The daemon runs as the user that they log in as,
18365                 so they cannot do anything that user cannot do.</P
18366 ><P
18367 >To restrict a service to a particular set of users you
18368                 can use the <A
18369 HREF="#VALIDUSERS"
18370 ><TT
18371 CLASS="PARAMETER"
18372 ><I
18373 >valid users
18374                 </I
18375 ></TT
18376 ></A
18377 > parameter.</P
18378 ><P
18379 >If any of the usernames begin with a '@' then the name
18380                 will be looked up first in the NIS netgroups list (if Samba
18381                 is compiled with netgroup support), followed by a lookup in
18382                 the UNIX groups database and will expand to a list of all users
18383                 in the group of that name.</P
18384 ><P
18385 >If any of the usernames begin with a '+' then the name
18386                 will be looked up only in the UNIX groups database and will
18387                 expand to a list of all users in the group of that name.</P
18388 ><P
18389 >If any of the usernames begin with a '&#38;'then the name
18390                 will be looked up only in the NIS netgroups database (if Samba
18391                 is compiled with netgroup support) and will expand to a list
18392                 of all users in the netgroup group of that name.</P
18393 ><P
18394 >Note that searching though a groups database can take
18395                 quite some time, and some clients may time out during the
18396                 search.</P
18397 ><P
18398 >See the section <A
18399 HREF="#AEN241"
18400 >NOTE ABOUT
18401                 USERNAME/PASSWORD VALIDATION</A
18402 > for more information on how
18403                 this parameter determines access to the services.</P
18404 ><P
18405 >Default: <B
18406 CLASS="COMMAND"
18407 >The guest account if a guest service,
18408                 else &#60;empty string&#62;.</B
18409 ></P
18410 ><P
18411 >Examples:<B
18412 CLASS="COMMAND"
18413 >username = fred, mary, jack, jane,
18414                 @users, @pcgroup</B
18415 ></P
18416 ></DD
18417 ><DT
18418 ><A
18419 NAME="USERNAMELEVEL"
18420 ></A
18421 >username level (G)</DT
18422 ><DD
18423 ><P
18424 >This option helps Samba to try and 'guess' at
18425                 the real UNIX username, as many DOS clients send an all-uppercase
18426                 username. By default Samba tries all lowercase, followed by the
18427                 username with the first letter capitalized, and fails if the
18428                 username is not found on the UNIX machine.</P
18429 ><P
18430 >If this parameter is set to non-zero the behavior changes.
18431                 This parameter is a number that specifies the number of uppercase
18432                 combinations to try while trying to determine the UNIX user name. The
18433                 higher the number the more combinations will be tried, but the slower
18434                 the discovery of usernames will be. Use this parameter when you have
18435                 strange usernames on your UNIX machine, such as <TT
18436 CLASS="CONSTANT"
18437 >AstrangeUser
18438                 </TT
18439 >.</P
18440 ><P
18441 >Default: <B
18442 CLASS="COMMAND"
18443 >username level = 0</B
18444 ></P
18445 ><P
18446 >Example: <B
18447 CLASS="COMMAND"
18448 >username level = 5</B
18449 ></P
18450 ></DD
18451 ><DT
18452 ><A
18453 NAME="USERNAMEMAP"
18454 ></A
18455 >username map (G)</DT
18456 ><DD
18457 ><P
18458 >This option allows you to specify a file containing
18459                 a mapping of usernames from the clients to the server. This can be
18460                 used for several purposes. The most common is to map usernames
18461                 that users use on DOS or Windows machines to those that the UNIX
18462                 box uses. The other is to map multiple users to a single username
18463                 so that they can more easily share files.</P
18464 ><P
18465 >The map file is parsed line by line. Each line should
18466                 contain a single UNIX username on the left then a '=' followed
18467                 by a list of usernames on the right. The list of usernames on the
18468                 right may contain names of the form @group in which case they
18469                 will match any UNIX username in that group. The special client
18470                 name '*' is a wildcard and matches any name. Each line of the
18471                 map file may be up to 1023 characters long.</P
18472 ><P
18473 >The file is processed on each line by taking the
18474                 supplied username and comparing it with each username on the right
18475                 hand side of the '=' signs. If the supplied name matches any of
18476                 the names on the right hand side then it is replaced with the name
18477                 on the left. Processing then continues with the next line.</P
18478 ><P
18479 >If any line begins with a '#' or a ';' then it is
18480                 ignored</P
18481 ><P
18482 >If any line begins with an '!' then the processing
18483                 will stop after that line if a mapping was done by the line.
18484                 Otherwise mapping continues with every line being processed.
18485                 Using '!' is most useful when you have a wildcard mapping line
18486                 later in the file.</P
18487 ><P
18488 >For example to map from the name <TT
18489 CLASS="CONSTANT"
18490 >admin</TT
18491 >
18492                 or <TT
18493 CLASS="CONSTANT"
18494 >administrator</TT
18495 > to the UNIX name <TT
18496 CLASS="CONSTANT"
18497 >               root</TT
18498 > you would use:</P
18499 ><P
18500 ><B
18501 CLASS="COMMAND"
18502 >root = admin administrator</B
18503 ></P
18504 ><P
18505 >Or to map anyone in the UNIX group <TT
18506 CLASS="CONSTANT"
18507 >system</TT
18508 >
18509                 to the UNIX name <TT
18510 CLASS="CONSTANT"
18511 >sys</TT
18512 > you would use:</P
18513 ><P
18514 ><B
18515 CLASS="COMMAND"
18516 >sys = @system</B
18517 ></P
18518 ><P
18519 >You can have as many mappings as you like in a username
18520                 map file.</P
18521 ><P
18522 >If your system supports the NIS NETGROUP option then
18523                 the netgroup database is checked before the <TT
18524 CLASS="FILENAME"
18525 >/etc/group
18526                 </TT
18527 > database for matching groups.</P
18528 ><P
18529 >You can map Windows usernames that have spaces in them
18530                  by using double quotes around the name. For example:</P
18531 ><P
18532 ><B
18533 CLASS="COMMAND"
18534 >tridge = "Andrew Tridgell"</B
18535 ></P
18536 ><P
18537 >would map the windows username "Andrew Tridgell" to the
18538                 unix username "tridge".</P
18539 ><P
18540 >The following example would map mary and fred to the
18541                 unix user sys, and map the rest to guest. Note the use of the
18542                 '!' to tell Samba to stop processing if it gets a match on
18543                 that line.</P
18544 ><P
18545 ><TABLE
18546 BORDER="0"
18547 BGCOLOR="#E0E0E0"
18548 WIDTH="90%"
18549 ><TR
18550 ><TD
18551 ><PRE
18552 CLASS="PROGRAMLISTING"
18553 >               !sys = mary fred
18554                 guest = *
18555                 </PRE
18556 ></TD
18557 ></TR
18558 ></TABLE
18559 ></P
18560 ><P
18561 >Note that the remapping is applied to all occurrences
18562                 of usernames. Thus if you connect to \\server\fred and <TT
18563 CLASS="CONSTANT"
18564 >               fred</TT
18565 > is remapped to <TT
18566 CLASS="CONSTANT"
18567 >mary</TT
18568 > then you
18569                 will actually be connecting to \\server\mary and will need to
18570                 supply a password suitable for <TT
18571 CLASS="CONSTANT"
18572 >mary</TT
18573 > not
18574                 <TT
18575 CLASS="CONSTANT"
18576 >fred</TT
18577 >. The only exception to this is the
18578                 username passed to the <A
18579 HREF="#PASSWORDSERVER"
18580 ><TT
18581 CLASS="PARAMETER"
18582 ><I
18583 >               password server</I
18584 ></TT
18585 ></A
18586 > (if you have one). The password
18587                 server will receive whatever username the client supplies without
18588                 modification.</P
18589 ><P
18590 >Also note that no reverse mapping is done. The main effect
18591                 this has is with printing. Users who have been mapped may have
18592                 trouble deleting print jobs as PrintManager under WfWg will think
18593                 they don't own the print job.</P
18594 ><P
18595 >Default: <EM
18596 >no username map</EM
18597 ></P
18598 ><P
18599 >Example: <B
18600 CLASS="COMMAND"
18601 >username map = /usr/local/samba/lib/users.map
18602                 </B
18603 ></P
18604 ></DD
18605 ><DT
18606 ><A
18607 NAME="UTMP"
18608 ></A
18609 >utmp (G)</DT
18610 ><DD
18611 ><P
18612 >This boolean parameter is only available if
18613                 Samba has been configured and compiled  with the option <B
18614 CLASS="COMMAND"
18615 >               --with-utmp</B
18616 >. If set to <TT
18617 CLASS="CONSTANT"
18618 >yes</TT
18619 > then Samba will attempt
18620                 to add utmp or utmpx records (depending on the UNIX system) whenever a
18621                 connection is made to a Samba server. Sites may use this to record the
18622                 user connecting to a Samba share.</P
18623 ><P
18624 >See also the <A
18625 HREF="#UTMPDIRECTORY"
18626 ><TT
18627 CLASS="PARAMETER"
18628 ><I
18629 >               utmp directory</I
18630 ></TT
18631 ></A
18632 > parameter.</P
18633 ><P
18634 >Default: <B
18635 CLASS="COMMAND"
18636 >utmp = no</B
18637 ></P
18638 ></DD
18639 ><DT
18640 ><A
18641 NAME="UTMPDIRECTORY"
18642 ></A
18643 >utmp directory(G)</DT
18644 ><DD
18645 ><P
18646 >This parameter is only available if Samba has
18647                 been configured and compiled with the option <B
18648 CLASS="COMMAND"
18649 >               --with-utmp</B
18650 >. It specifies a directory pathname that is
18651                 used to store the utmp or utmpx files (depending on the UNIX system) that
18652                 record user connections to a Samba server. See also the <A
18653 HREF="#UTMP"
18654 >               <TT
18655 CLASS="PARAMETER"
18656 ><I
18657 >utmp</I
18658 ></TT
18659 ></A
18660 > parameter. By default this is
18661                 not set, meaning the system will use whatever utmp file the
18662                 native system is set to use (usually
18663                 <TT
18664 CLASS="FILENAME"
18665 >/var/run/utmp</TT
18666 > on Linux).</P
18667 ><P
18668 >Default: <EM
18669 >no utmp directory</EM
18670 ></P
18671 ></DD
18672 ><DT
18673 ><A
18674 NAME="VALIDCHARS"
18675 ></A
18676 >valid chars (G)</DT
18677 ><DD
18678 ><P
18679 >The option allows you to specify additional
18680                 characters that should be considered valid by the server in
18681                 filenames. This is particularly useful for national character
18682                 sets, such as adding u-umlaut or a-ring.</P
18683 ><P
18684 >The option takes a list of characters in either integer
18685                 or character form with spaces between them. If you give two
18686                 characters with a colon between them then it will be taken as
18687                 an lowercase:uppercase pair.</P
18688 ><P
18689 >If you have an editor capable of entering the characters
18690                 into the config file then it is probably easiest to use this
18691                 method. Otherwise you can specify the characters in octal,
18692                 decimal or hexadecimal form using the usual C notation.</P
18693 ><P
18694 >For example to add the single character 'Z' to the charset
18695                 (which is a pointless thing to do as it's already there) you could
18696                 do one of the following</P
18697 ><P
18698 ><TABLE
18699 BORDER="0"
18700 BGCOLOR="#E0E0E0"
18701 WIDTH="90%"
18702 ><TR
18703 ><TD
18704 ><PRE
18705 CLASS="PROGRAMLISTING"
18706 >               valid chars = Z
18707                 valid chars = z:Z
18708                 valid chars = 0132:0172
18709                 </PRE
18710 ></TD
18711 ></TR
18712 ></TABLE
18713 ></P
18714 ><P
18715 >The last two examples above actually add two characters,
18716                 and alter the uppercase and lowercase mappings appropriately.</P
18717 ><P
18718 >Note that you <EM
18719 >MUST</EM
18720 > specify this parameter
18721                 after the <TT
18722 CLASS="PARAMETER"
18723 ><I
18724 >client code page</I
18725 ></TT
18726 > parameter if you
18727                 have both set. If <TT
18728 CLASS="PARAMETER"
18729 ><I
18730 >client code page</I
18731 ></TT
18732 > is set after
18733                 the <TT
18734 CLASS="PARAMETER"
18735 ><I
18736 >valid chars</I
18737 ></TT
18738 > parameter the <TT
18739 CLASS="PARAMETER"
18740 ><I
18741 >valid
18742                 chars</I
18743 ></TT
18744 > settings will be overwritten.</P
18745 ><P
18746 >See also the <A
18747 HREF="#CLIENTCODEPAGE"
18748 ><TT
18749 CLASS="PARAMETER"
18750 ><I
18751 >client
18752                 code page</I
18753 ></TT
18754 ></A
18755 > parameter.</P
18756 ><P
18757 >Default: <EM
18758 >Samba defaults to using a reasonable set
18759                 of valid characters for English systems</EM
18760 ></P
18761 ><P
18762 >Example: <B
18763 CLASS="COMMAND"
18764 >valid chars = 0345:0305 0366:0326 0344:0304
18765                 </B
18766 ></P
18767 ><P
18768 >The above example allows filenames to have the Swedish
18769                 characters in them.</P
18770 ><P
18771 ><EM
18772 >NOTE:</EM
18773 > It is actually quite difficult to
18774                 correctly produce a <TT
18775 CLASS="PARAMETER"
18776 ><I
18777 >valid chars</I
18778 ></TT
18779 > line for
18780                 a particular system. To automate the process <A
18781 HREF="mailto:tino@augsburg.net"
18782 TARGET="_top"
18783 >tino@augsburg.net</A
18784 > has written
18785                 a package called <B
18786 CLASS="COMMAND"
18787 >validchars</B
18788 > which will automatically
18789                 produce a complete <TT
18790 CLASS="PARAMETER"
18791 ><I
18792 >valid chars</I
18793 ></TT
18794 > line for
18795                 a given client system. Look in the <TT
18796 CLASS="FILENAME"
18797 >examples/validchars/
18798                 </TT
18799 > subdirectory of your Samba source code distribution
18800                 for this package.</P
18801 ></DD
18802 ><DT
18803 ><A
18804 NAME="VALIDUSERS"
18805 ></A
18806 >valid users (S)</DT
18807 ><DD
18808 ><P
18809 >This is a list of users that should be allowed
18810                 to login to this service. Names starting with '@', '+' and  '&#38;'
18811                 are interpreted using the same rules as described in the
18812                 <TT
18813 CLASS="PARAMETER"
18814 ><I
18815 >invalid users</I
18816 ></TT
18817 > parameter.</P
18818 ><P
18819 >If this is empty (the default) then any user can login.
18820                 If a username is in both this list and the <TT
18821 CLASS="PARAMETER"
18822 ><I
18823 >invalid
18824                 users</I
18825 ></TT
18826 > list then access is denied for that user.</P
18827 ><P
18828 >The current servicename is substituted for <TT
18829 CLASS="PARAMETER"
18830 ><I
18831 >%S
18832                 </I
18833 ></TT
18834 >. This is useful in the [homes] section.</P
18835 ><P
18836 >See also <A
18837 HREF="#INVALIDUSERS"
18838 ><TT
18839 CLASS="PARAMETER"
18840 ><I
18841 >invalid users
18842                 </I
18843 ></TT
18844 ></A
18845 ></P
18846 ><P
18847 >Default: <EM
18848 >No valid users list (anyone can login)
18849                 </EM
18850 ></P
18851 ><P
18852 >Example: <B
18853 CLASS="COMMAND"
18854 >valid users = greg, @pcusers</B
18855 ></P
18856 ></DD
18857 ><DT
18858 ><A
18859 NAME="VETOFILES"
18860 ></A
18861 >veto files(S)</DT
18862 ><DD
18863 ><P
18864 >This is a list of files and directories that
18865                 are neither visible nor accessible.  Each entry in the list must
18866                 be separated by a '/', which allows spaces to be included
18867                 in the entry. '*' and '?' can be used to specify multiple files
18868                 or directories as in DOS wildcards.</P
18869 ><P
18870 >Each entry must be a unix path, not a DOS path and
18871                 must <EM
18872 >not</EM
18873 > include the  unix directory
18874                 separator '/'.</P
18875 ><P
18876 >Note that the <TT
18877 CLASS="PARAMETER"
18878 ><I
18879 >case sensitive</I
18880 ></TT
18881 > option
18882                 is applicable in vetoing files.</P
18883 ><P
18884 >One feature of the veto files parameter that it
18885                 is important to be aware of is Samba's behaviour when
18886                 trying to delete a directory. If a directory that is
18887                 to be deleted contains nothing but veto files this
18888                 deletion will <EM
18889 >fail</EM
18890 > unless you also set
18891                 the <TT
18892 CLASS="PARAMETER"
18893 ><I
18894 >delete veto files</I
18895 ></TT
18896 > parameter to
18897                 <TT
18898 CLASS="PARAMETER"
18899 ><I
18900 >yes</I
18901 ></TT
18902 >.</P
18903 ><P
18904 >Setting this parameter will affect the performance
18905                 of Samba, as it will be forced to check all files and directories
18906                 for a match as they are scanned.</P
18907 ><P
18908 >See also <A
18909 HREF="#HIDEFILES"
18910 ><TT
18911 CLASS="PARAMETER"
18912 ><I
18913 >hide files
18914                 </I
18915 ></TT
18916 ></A
18917 > and <A
18918 HREF="#CASESENSITIVE"
18919 ><TT
18920 CLASS="PARAMETER"
18921 ><I
18922 >               case sensitive</I
18923 ></TT
18924 ></A
18925 >.</P
18926 ><P
18927 >Default: <EM
18928 >No files or directories are vetoed.
18929                 </EM
18930 ></P
18931 ><P
18932 >Examples:<TABLE
18933 BORDER="0"
18934 BGCOLOR="#E0E0E0"
18935 WIDTH="90%"
18936 ><TR
18937 ><TD
18938 ><PRE
18939 CLASS="PROGRAMLISTING"
18940 >; Veto any files containing the word Security,
18941 ; any ending in .tmp, and any directory containing the
18942 ; word root.
18943 veto files = /*Security*/*.tmp/*root*/
18944
18945 ; Veto the Apple specific files that a NetAtalk server
18946 ; creates.
18947 veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/</PRE
18948 ></TD
18949 ></TR
18950 ></TABLE
18951 ></P
18952 ></DD
18953 ><DT
18954 ><A
18955 NAME="VETOOPLOCKFILES"
18956 ></A
18957 >veto oplock files (S)</DT
18958 ><DD
18959 ><P
18960 >This parameter is only valid when the <A
18961 HREF="#OPLOCKS"
18962 ><TT
18963 CLASS="PARAMETER"
18964 ><I
18965 >oplocks</I
18966 ></TT
18967 ></A
18968 >
18969                 parameter is turned on for a share. It allows the Samba administrator
18970                 to selectively turn off the granting of oplocks on selected files that
18971                 match a wildcarded list, similar to the wildcarded list used in the
18972                 <A
18973 HREF="#VETOFILES"
18974 ><TT
18975 CLASS="PARAMETER"
18976 ><I
18977 >veto files</I
18978 ></TT
18979 ></A
18980 >
18981                 parameter.</P
18982 ><P
18983 >Default: <EM
18984 >No files are vetoed for oplock
18985                 grants</EM
18986 ></P
18987 ><P
18988 >You might want to do this on files that you know will
18989                 be heavily contended for by clients. A good example of this
18990                 is in the NetBench SMB benchmark program, which causes heavy
18991                 client contention for files ending in <TT
18992 CLASS="FILENAME"
18993 >.SEM</TT
18994 >.
18995                 To cause Samba not to grant oplocks on these files you would use
18996                 the line (either in the [global] section or in the section for
18997                 the particular NetBench share :</P
18998 ><P
18999 >Example: <B
19000 CLASS="COMMAND"
19001 >veto oplock files = /*.SEM/
19002                 </B
19003 ></P
19004 ></DD
19005 ><DT
19006 ><A
19007 NAME="VFSOBJECT"
19008 ></A
19009 >vfs object (S)</DT
19010 ><DD
19011 ><P
19012 >This parameter specifies a shared object file that
19013                 is used for Samba VFS I/O operations.  By default, normal
19014                 disk I/O operations are used but these can be overloaded
19015                 with a VFS object.  The Samba VFS layer is new to Samba 2.2 and
19016                 must be enabled at compile time with --with-vfs.</P
19017 ><P
19018 >Default : <EM
19019 >no value</EM
19020 ></P
19021 ></DD
19022 ><DT
19023 ><A
19024 NAME="VFSOPTIONS"
19025 ></A
19026 >vfs options (S)</DT
19027 ><DD
19028 ><P
19029 >This parameter allows parameters to be passed
19030                 to the vfs layer at initialization time.  The Samba VFS layer
19031                 is new to Samba 2.2 and must be enabled at compile time
19032                 with --with-vfs.  See also <A
19033 HREF="#VFSOBJECT"
19034 ><TT
19035 CLASS="PARAMETER"
19036 ><I
19037 >               vfs object</I
19038 ></TT
19039 ></A
19040 >.</P
19041 ><P
19042 >Default : <EM
19043 >no value</EM
19044 ></P
19045 ></DD
19046 ><DT
19047 ><A
19048 NAME="VOLUME"
19049 ></A
19050 >volume (S)</DT
19051 ><DD
19052 ><P
19053 > This allows you to override the volume label
19054                 returned for a share. Useful for CDROMs with installation programs
19055                 that insist on a particular volume label.</P
19056 ><P
19057 >Default: <EM
19058 >the name of the share</EM
19059 ></P
19060 ></DD
19061 ><DT
19062 ><A
19063 NAME="WIDELINKS"
19064 ></A
19065 >wide links (S)</DT
19066 ><DD
19067 ><P
19068 >This parameter controls whether or not links
19069                 in the UNIX file system may be followed by the server. Links
19070                 that point to areas within the directory tree exported by the
19071                 server are always allowed; this parameter controls access only
19072                 to areas that are outside the directory tree being exported.</P
19073 ><P
19074 >Note that setting this parameter can have a negative
19075                 effect on your server performance due to the extra system calls
19076                 that Samba has to  do in order to perform the link checks.</P
19077 ><P
19078 >Default: <B
19079 CLASS="COMMAND"
19080 >wide links = yes</B
19081 ></P
19082 ></DD
19083 ><DT
19084 ><A
19085 NAME="WINBINDCACHETIME"
19086 ></A
19087 >winbind cache time (G)</DT
19088 ><DD
19089 ><P
19090 >This parameter specifies the number of seconds the
19091                 <A
19092 HREF="winbindd.8.html"
19093 TARGET="_top"
19094 >winbindd(8)</A
19095 > daemon will cache
19096                 user and group information before querying a Windows NT server
19097                 again.</P
19098 ><P
19099 >Default: <B
19100 CLASS="COMMAND"
19101 >winbind cache type = 15</B
19102 ></P
19103 ></DD
19104 ><DT
19105 ><A
19106 NAME="WINBINDENUMUSERS"
19107 ></A
19108 >winbind enum users (G)</DT
19109 ><DD
19110 ><P
19111 >On large installations using
19112                 <A
19113 HREF="winbindd.8.html"
19114 TARGET="_top"
19115 >winbindd(8)</A
19116 > it may be
19117                 necessary to suppress the enumeration of users through the
19118                 <B
19119 CLASS="COMMAND"
19120 > setpwent()</B
19121 >,
19122                 <B
19123 CLASS="COMMAND"
19124 >getpwent()</B
19125 > and
19126                 <B
19127 CLASS="COMMAND"
19128 >endpwent()</B
19129 > group of system calls.  If
19130                 the <TT
19131 CLASS="PARAMETER"
19132 ><I
19133 >winbind enum users</I
19134 ></TT
19135 > parameter is
19136                 <TT
19137 CLASS="CONSTANT"
19138 >no</TT
19139 >, calls to the <B
19140 CLASS="COMMAND"
19141 >getpwent</B
19142 > system call
19143                 will not return any data. </P
19144 ><P
19145 ><EM
19146 >Warning:</EM
19147 > Turning off user
19148                 enumeration may cause some programs to behave oddly.  For
19149                 example, the finger program relies on having access to the
19150                 full user list when searching for matching
19151                 usernames. </P
19152 ><P
19153 >Default: <B
19154 CLASS="COMMAND"
19155 >winbind enum users = yes </B
19156 ></P
19157 ></DD
19158 ><DT
19159 ><A
19160 NAME="WINBINDENUMGROUPS"
19161 ></A
19162 >winbind enum groups (G)</DT
19163 ><DD
19164 ><P
19165 >On large installations using
19166                 <A
19167 HREF="winbindd.8.html"
19168 TARGET="_top"
19169 >winbindd(8)</A
19170 > it may be
19171                 necessary to suppress the enumeration of groups through the
19172                 <B
19173 CLASS="COMMAND"
19174 > setgrent()</B
19175 >,
19176                 <B
19177 CLASS="COMMAND"
19178 >getgrent()</B
19179 > and
19180                 <B
19181 CLASS="COMMAND"
19182 >endgrent()</B
19183 > group of system calls.  If
19184                 the <TT
19185 CLASS="PARAMETER"
19186 ><I
19187 >winbind enum groups</I
19188 ></TT
19189 > parameter is
19190                 <TT
19191 CLASS="CONSTANT"
19192 >no</TT
19193 >, calls to the <B
19194 CLASS="COMMAND"
19195 >getgrent()</B
19196 > system
19197                 call will not return any data. </P
19198 ><P
19199 ><EM
19200 >Warning:</EM
19201 > Turning off group
19202                 enumeration may cause some programs to behave oddly.
19203                 </P
19204 ><P
19205 >Default: <B
19206 CLASS="COMMAND"
19207 >winbind enum groups = yes </B
19208 >
19209                 </P
19210 ></DD
19211 ><DT
19212 ><A
19213 NAME="WINBINDGID"
19214 ></A
19215 >winbind gid (G)</DT
19216 ><DD
19217 ><P
19218 >The winbind gid parameter specifies the range of group
19219                 ids that are allocated by the <A
19220 HREF="winbindd.8.html"
19221 TARGET="_top"
19222 >               winbindd(8)</A
19223 > daemon.  This range of group ids should have no
19224                 existing local or NIS groups within it as strange conflicts can
19225                 occur otherwise.</P
19226 ><P
19227 >Default: <B
19228 CLASS="COMMAND"
19229 >winbind gid = &#60;empty string&#62;
19230                 </B
19231 ></P
19232 ><P
19233 >Example: <B
19234 CLASS="COMMAND"
19235 >winbind gid = 10000-20000</B
19236 ></P
19237 ></DD
19238 ><DT
19239 ><A
19240 NAME="WINBINDSEPARATOR"
19241 ></A
19242 >winbind separator (G)</DT
19243 ><DD
19244 ><P
19245 >This parameter allows an admin to define the character
19246                 used when listing a username of the form of <TT
19247 CLASS="REPLACEABLE"
19248 ><I
19249 >DOMAIN
19250                 </I
19251 ></TT
19252 >\<TT
19253 CLASS="REPLACEABLE"
19254 ><I
19255 >user</I
19256 ></TT
19257 >.  This parameter
19258                 is only applicable when using the <TT
19259 CLASS="FILENAME"
19260 >pam_winbind.so</TT
19261 >
19262                 and <TT
19263 CLASS="FILENAME"
19264 >nss_winbind.so</TT
19265 > modules for UNIX services.
19266                 </P
19267 ><P
19268 >Please note that setting this parameter to + causes problems
19269                 with group membership at least on glibc systems, as the character +
19270                 is used as a special character for NIS in /etc/group.</P
19271 ><P
19272 >Default: <B
19273 CLASS="COMMAND"
19274 >winbind separator = '\'</B
19275 ></P
19276 ><P
19277 >Example: <B
19278 CLASS="COMMAND"
19279 >winbind separator = +</B
19280 ></P
19281 ></DD
19282 ><DT
19283 ><A
19284 NAME="WINBINDUID"
19285 ></A
19286 >winbind uid (G)</DT
19287 ><DD
19288 ><P
19289 >The winbind gid parameter specifies the range of group
19290                 ids that are allocated by the <A
19291 HREF="winbindd.8.html"
19292 TARGET="_top"
19293 >               winbindd(8)</A
19294 > daemon.  This range of ids should have no
19295                 existing local or NIS users within it as strange conflicts can
19296                 occur otherwise.</P
19297 ><P
19298 >Default: <B
19299 CLASS="COMMAND"
19300 >winbind uid = &#60;empty string&#62;
19301                 </B
19302 ></P
19303 ><P
19304 >Example: <B
19305 CLASS="COMMAND"
19306 >winbind uid = 10000-20000</B
19307 ></P
19308 ></DD
19309 ><DT
19310 >winbind use default domain, <A
19311 NAME="WINBINDUSEDEFAULTDOMAIN"
19312 ></A
19313 >winbind use default domain</DT
19314 ><DD
19315 ><P
19316 >This parameter specifies whether the <A
19317 HREF="winbindd.8.html"
19318 TARGET="_top"
19319 >               winbindd(8)</A
19320 >
19321                 daemon should operate on users without domain component in their username.
19322                 Users without a domain component are treated as is part of the winbindd server's
19323                 own domain.  While this does not benifit Windows users, it makes SSH, FTP and e-mail
19324                 function in a way much closer to the way they would in a native unix system.</P
19325 ><P
19326 >Default: <B
19327 CLASS="COMMAND"
19328 >winbind use default domain = &#60;no&#62;
19329                 </B
19330 ></P
19331 ><P
19332 >Example: <B
19333 CLASS="COMMAND"
19334 >winbind use default domain = yes</B
19335 ></P
19336 ></DD
19337 ><DT
19338 ><A
19339 NAME="WINSHOOK"
19340 ></A
19341 >wins hook (G)</DT
19342 ><DD
19343 ><P
19344 >When Samba is running as a WINS server this
19345                 allows you to call an external program for all changes to the
19346                 WINS database. The primary use for this option is to allow the
19347                 dynamic update of external name resolution databases such as
19348                 dynamic DNS.</P
19349 ><P
19350 >The wins hook parameter specifies the name of a script
19351                 or executable that will be called as follows:</P
19352 ><P
19353 ><B
19354 CLASS="COMMAND"
19355 >wins_hook operation name nametype ttl IP_list
19356                 </B
19357 ></P
19358 ><P
19359 ></P
19360 ><UL
19361 ><LI
19362 ><P
19363 >The first argument is the operation and is one
19364                         of "add", "delete", or "refresh". In most cases the operation can
19365                         be ignored as the rest of the parameters provide sufficient
19366                         information. Note that "refresh" may sometimes be called when the
19367                         name has not previously been added, in that case it should be treated
19368                         as an add.</P
19369 ></LI
19370 ><LI
19371 ><P
19372 >The second argument is the NetBIOS name. If the
19373                         name is not a legal name then the wins hook is not called.
19374                         Legal names contain only  letters, digits, hyphens, underscores
19375                         and periods.</P
19376 ></LI
19377 ><LI
19378 ><P
19379 >The third argument is the NetBIOS name
19380                         type as a 2 digit hexadecimal number. </P
19381 ></LI
19382 ><LI
19383 ><P
19384 >The fourth argument is the TTL (time to live)
19385                         for the name in seconds.</P
19386 ></LI
19387 ><LI
19388 ><P
19389 >The fifth and subsequent arguments are the IP
19390                         addresses currently registered for that name. If this list is
19391                         empty then the name should be deleted.</P
19392 ></LI
19393 ></UL
19394 ><P
19395 >An example script that calls the BIND dynamic DNS update
19396                 program <B
19397 CLASS="COMMAND"
19398 >nsupdate</B
19399 > is provided in the examples
19400                 directory of the Samba source code. </P
19401 ></DD
19402 ><DT
19403 ><A
19404 NAME="WINSPROXY"
19405 ></A
19406 >wins proxy (G)</DT
19407 ><DD
19408 ><P
19409 >This is a boolean that controls if <A
19410 HREF="nmbd.8.html"
19411 TARGET="_top"
19412 >nmbd(8)</A
19413 > will respond to broadcast name
19414                 queries on behalf of  other hosts. You may need to set this
19415                 to <TT
19416 CLASS="CONSTANT"
19417 >yes</TT
19418 > for some older clients.</P
19419 ><P
19420 >Default: <B
19421 CLASS="COMMAND"
19422 >wins proxy = no</B
19423 ></P
19424 ></DD
19425 ><DT
19426 ><A
19427 NAME="WINSSERVER"
19428 ></A
19429 >wins server (G)</DT
19430 ><DD
19431 ><P
19432 >This specifies the IP address (or DNS name: IP
19433                 address for preference) of the WINS server that <A
19434 HREF="nmbd.8.html"
19435 TARGET="_top"
19436 >               nmbd(8)</A
19437 > should register with. If you have a WINS server on
19438                 your network then you should set this to the WINS server's IP.</P
19439 ><P
19440 >You should point this at your WINS server if you have a
19441                 multi-subnetted network.</P
19442 ><P
19443 ><EM
19444 >NOTE</EM
19445 >. You need to set up Samba to point
19446                 to a WINS server if you have multiple subnets and wish cross-subnet
19447                 browsing to work correctly.</P
19448 ><P
19449 >See the documentation file <TT
19450 CLASS="FILENAME"
19451 >BROWSING.txt</TT
19452 >
19453                 in the docs/ directory of your Samba source distribution.</P
19454 ><P
19455 >Default: <EM
19456 >not enabled</EM
19457 ></P
19458 ><P
19459 >Example: <B
19460 CLASS="COMMAND"
19461 >wins server = 192.9.200.1</B
19462 ></P
19463 ></DD
19464 ><DT
19465 ><A
19466 NAME="WINSSUPPORT"
19467 ></A
19468 >wins support (G)</DT
19469 ><DD
19470 ><P
19471 >This boolean controls if the <A
19472 HREF="nmbd.8.html"
19473 TARGET="_top"
19474 >
19475                 nmbd(8)</A
19476 > process in Samba will act as a WINS server. You should
19477                 not set this to <TT
19478 CLASS="CONSTANT"
19479 >yes</TT
19480 > unless you have a multi-subnetted network and
19481                 you wish a particular <B
19482 CLASS="COMMAND"
19483 >nmbd</B
19484 > to be your WINS server.
19485                 Note that you should <EM
19486 >NEVER</EM
19487 > set this to <TT
19488 CLASS="CONSTANT"
19489 >yes</TT
19490 >
19491                 on more than one machine in your network.</P
19492 ><P
19493 >Default: <B
19494 CLASS="COMMAND"
19495 >wins support = no</B
19496 ></P
19497 ></DD
19498 ><DT
19499 ><A
19500 NAME="WORKGROUP"
19501 ></A
19502 >workgroup (G)</DT
19503 ><DD
19504 ><P
19505 >This controls what workgroup your server will
19506                 appear to be in when queried by clients. Note that this parameter
19507                 also controls the Domain name used with the <A
19508 HREF="#SECURITYEQUALSDOMAIN"
19509 ><B
19510 CLASS="COMMAND"
19511 >security = domain</B
19512 ></A
19513 >
19514                 setting.</P
19515 ><P
19516 >Default: <EM
19517 >set at compile time to WORKGROUP</EM
19518 ></P
19519 ><P
19520 >Example: <B
19521 CLASS="COMMAND"
19522 >workgroup = MYGROUP</B
19523 ></P
19524 ></DD
19525 ><DT
19526 ><A
19527 NAME="WRITABLE"
19528 ></A
19529 >writable (S)</DT
19530 ><DD
19531 ><P
19532 >Synonym for <A
19533 HREF="#WRITEABLE"
19534 ><TT
19535 CLASS="PARAMETER"
19536 ><I
19537 >               writeable</I
19538 ></TT
19539 ></A
19540 > for people who can't spell :-).</P
19541 ></DD
19542 ><DT
19543 ><A
19544 NAME="WRITECACHESIZE"
19545 ></A
19546 >write cache size (S)</DT
19547 ><DD
19548 ><P
19549 >If this integer parameter is set to non-zero value,
19550                 Samba will create an in-memory cache for each oplocked file
19551                 (it does <EM
19552 >not</EM
19553 > do this for
19554                 non-oplocked files). All writes that the client does not request
19555                 to be flushed directly to disk will be stored in this cache if possible.
19556                 The cache is flushed onto disk when a write comes in whose offset
19557                 would not fit into the cache or when the file is closed by the client.
19558                 Reads for the file are also served from this cache if the data is stored
19559                 within it.</P
19560 ><P
19561 >This cache allows Samba to batch client writes into a more
19562                 efficient write size for RAID disks (i.e. writes may be tuned to
19563                 be the RAID stripe size) and can improve performance on systems
19564                 where the disk subsystem is a bottleneck but there is free
19565                 memory for userspace programs.</P
19566 ><P
19567 >The integer parameter specifies the size of this cache
19568                 (per oplocked file) in bytes.</P
19569 ><P
19570 >Default: <B
19571 CLASS="COMMAND"
19572 >write cache size = 0</B
19573 ></P
19574 ><P
19575 >Example: <B
19576 CLASS="COMMAND"
19577 >write cache size = 262144</B
19578 ></P
19579 ><P
19580 >for a 256k cache size per file.</P
19581 ></DD
19582 ><DT
19583 ><A
19584 NAME="WRITELIST"
19585 ></A
19586 >write list (S)</DT
19587 ><DD
19588 ><P
19589 >This is a list of users that are given read-write
19590                 access to a service. If the connecting user is in this list then
19591                 they will be given write access, no matter what the <A
19592 HREF="#READONLY"
19593 ><TT
19594 CLASS="PARAMETER"
19595 ><I
19596 >read only</I
19597 ></TT
19598 ></A
19599 >
19600                 option is set to. The list can include group names using the
19601                 @group syntax.</P
19602 ><P
19603 >Note that if a user is in both the read list and the
19604                 write list then they will be given write access.</P
19605 ><P
19606 >See also the <A
19607 HREF="#READLIST"
19608 ><TT
19609 CLASS="PARAMETER"
19610 ><I
19611 >read list
19612                 </I
19613 ></TT
19614 ></A
19615 > option.</P
19616 ><P
19617 >Default: <B
19618 CLASS="COMMAND"
19619 >write list = &#60;empty string&#62;
19620                 </B
19621 ></P
19622 ><P
19623 >Example: <B
19624 CLASS="COMMAND"
19625 >write list = admin, root, @staff
19626                 </B
19627 ></P
19628 ></DD
19629 ><DT
19630 ><A
19631 NAME="WRITEOK"
19632 ></A
19633 >write ok (S)</DT
19634 ><DD
19635 ><P
19636 >Inverted synonym for <A
19637 HREF="#READONLY"
19638 ><TT
19639 CLASS="PARAMETER"
19640 ><I
19641 >               read only</I
19642 ></TT
19643 ></A
19644 >.</P
19645 ></DD
19646 ><DT
19647 ><A
19648 NAME="WRITERAW"
19649 ></A
19650 >write raw (G)</DT
19651 ><DD
19652 ><P
19653 >This parameter controls whether or not the server
19654                 will support raw write SMB's when transferring data from clients.
19655                 You should never need to change this parameter.</P
19656 ><P
19657 >Default: <B
19658 CLASS="COMMAND"
19659 >write raw = yes</B
19660 ></P
19661 ></DD
19662 ><DT
19663 ><A
19664 NAME="WRITEABLE"
19665 ></A
19666 >writeable (S)</DT
19667 ><DD
19668 ><P
19669 >Inverted synonym for <A
19670 HREF="#READONLY"
19671 ><TT
19672 CLASS="PARAMETER"
19673 ><I
19674 >               read only</I
19675 ></TT
19676 ></A
19677 >.</P
19678 ></DD
19679 ></DL
19680 ></DIV
19681 ></DIV
19682 ><DIV
19683 CLASS="REFSECT1"
19684 ><A
19685 NAME="AEN6223"
19686 ></A
19687 ><H2
19688 >WARNINGS</H2
19689 ><P
19690 >Although the configuration file permits service names
19691         to contain spaces, your client software may not. Spaces will
19692         be ignored in comparisons anyway, so it shouldn't be a
19693         problem - but be aware of the possibility.</P
19694 ><P
19695 >On a similar note, many clients - especially DOS clients -
19696         limit service names to eight characters. <A
19697 HREF="smbd.8.html"
19698 TARGET="_top"
19699 >smbd(8)
19700         </A
19701 > has no such limitation, but attempts to connect from such
19702         clients will fail if they truncate the service names.  For this reason
19703         you should probably keep your service names down to eight characters
19704         in length.</P
19705 ><P
19706 >Use of the [homes] and [printers] special sections make life
19707         for an administrator easy, but the various combinations of default
19708         attributes can be tricky. Take extreme care when designing these
19709         sections. In particular, ensure that the permissions on spool
19710         directories are correct.</P
19711 ></DIV
19712 ><DIV
19713 CLASS="REFSECT1"
19714 ><A
19715 NAME="AEN6229"
19716 ></A
19717 ><H2
19718 >VERSION</H2
19719 ><P
19720 >This man page is correct for version 2.2 of
19721         the Samba suite.</P
19722 ></DIV
19723 ><DIV
19724 CLASS="REFSECT1"
19725 ><A
19726 NAME="AEN6232"
19727 ></A
19728 ><H2
19729 >SEE ALSO</H2
19730 ><P
19731 ><A
19732 HREF="samba.7.html"
19733 TARGET="_top"
19734 >samba(7)</A
19735 >,
19736         <A
19737 HREF="smbpasswd.8.html"
19738 TARGET="_top"
19739 ><B
19740 CLASS="COMMAND"
19741 >smbpasswd(8)</B
19742 ></A
19743 >,
19744         <A
19745 HREF="swat.8.html"
19746 TARGET="_top"
19747 ><B
19748 CLASS="COMMAND"
19749 >swat(8)</B
19750 ></A
19751 >,
19752         <A
19753 HREF="smbd.8.html"
19754 TARGET="_top"
19755 ><B
19756 CLASS="COMMAND"
19757 >smbd(8)</B
19758 ></A
19759 >,
19760         <A
19761 HREF="nmbd.8.html"
19762 TARGET="_top"
19763 ><B
19764 CLASS="COMMAND"
19765 >nmbd(8)</B
19766 ></A
19767 >,
19768         <A
19769 HREF="smbclient.1.html"
19770 TARGET="_top"
19771 ><B
19772 CLASS="COMMAND"
19773 >smbclient(1)</B
19774 ></A
19775 >,
19776         <A
19777 HREF="nmblookup.1.html"
19778 TARGET="_top"
19779 ><B
19780 CLASS="COMMAND"
19781 >nmblookup(1)</B
19782 ></A
19783 >,
19784         <A
19785 HREF="testparm.1.html"
19786 TARGET="_top"
19787 ><B
19788 CLASS="COMMAND"
19789 >testparm(1)</B
19790 ></A
19791 >,
19792         <A
19793 HREF="testprns.1.html"
19794 TARGET="_top"
19795 ><B
19796 CLASS="COMMAND"
19797 >testprns(1)</B
19798 ></A
19799 >
19800         </P
19801 ></DIV
19802 ><DIV
19803 CLASS="REFSECT1"
19804 ><A
19805 NAME="AEN6252"
19806 ></A
19807 ><H2
19808 >AUTHOR</H2
19809 ><P
19810 >The original Samba software and related utilities
19811         were created by Andrew Tridgell. Samba is now developed
19812         by the Samba Team as an Open Source project similar
19813         to the way the Linux kernel is developed.</P
19814 ><P
19815 >The original Samba man pages were written by Karl Auer.
19816         The man page sources were converted to YODL format (another
19817         excellent piece of Open Source software, available at
19818         <A
19819 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
19820 TARGET="_top"
19821 >       ftp://ftp.icce.rug.nl/pub/unix/</A
19822 >) and updated for the Samba 2.0
19823         release by Jeremy Allison.  The conversion to DocBook for
19824         Samba 2.2 was done by Gerald Carter</P
19825 ></DIV
19826 ></BODY
19827 ></HTML
19828 >