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                 writeable = true
 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                 writeable = false
 209                 printable = true
 210                 guest ok = true
 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                         writeable = yes
 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 ></DD
 594 ><DT
 595 >%M</DT
 596 ><DD
 597 ><P
 598 >the Internet name of the client machine.
 599                 </P
 600 ></DD
 601 ><DT
 602 >%N</DT
 603 ><DD
 604 ><P
 605 >the name of your NIS home directory server.
 606                 This is obtained from your NIS auto.map entry.  If you have
 607                 not compiled Samba with the <EM
 608 >--with-automount</EM
 609 >
 610                 option then this value will be the same as %L.</P
 611 ></DD
 612 ><DT
 613 >%p</DT
 614 ><DD
 615 ><P
 616 >the path of the service's home directory,
 617                 obtained from your NIS auto.map entry. The NIS auto.map entry
 618                 is split up as "%N:%p".</P
 619 ></DD
 620 ><DT
 621 >%R</DT
 622 ><DD
 623 ><P
 624 >the selected protocol level after
 625                 protocol negotiation. It can be one of CORE, COREPLUS,
 626                 LANMAN1, LANMAN2 or NT1.</P
 627 ></DD
 628 ><DT
 629 >%d</DT
 630 ><DD
 631 ><P
 632 >The process id of the current server
 633                 process.</P
 634 ></DD
 635 ><DT
 636 >%a</DT
 637 ><DD
 638 ><P
 639 >the architecture of the remote
 640                 machine. Only some are recognized, and those may not be
 641                 100% reliable. It currently recognizes Samba, WfWg,
 642                 WinNT and Win95. Anything else will be known as
 643                 "UNKNOWN". If it gets it wrong then sending a level
 644                 3 log to <A
 645 HREF="mailto:samba@samba.org"
 646 TARGET="_top"
 647 >samba@samba.org
 648                 </A
 649 > should allow it to be fixed.</P
 650 ></DD
 651 ><DT
 652 >%I</DT
 653 ><DD
 654 ><P
 655 >The IP address of the client machine.</P
 656 ></DD
 657 ><DT
 658 >%T</DT
 659 ><DD
 660 ><P
 661 >the current date and time.</P
 662 ></DD
 663 ><DT
 664 >%$(<TT
 665 CLASS="REPLACEABLE"
 666 ><I
 667 >envvar</I
 668 ></TT
 669 >)</DT
 670 ><DD
 671 ><P
 672 >The value of the environment variable
 673                 <TT
 674 CLASS="REPLACEABLE"
 675 ><I
 676 >envar</I
 677 ></TT
 678 >.</P
 679 ></DD
 680 ></DL
 681 ></DIV
 682 ><P
 683 >There are some quite creative things that can be done
 684         with these substitutions and other smb.conf options.</P
 685 ></DIV
 686 ><DIV
 687 CLASS="REFSECT1"
 688 ><A
 689 NAME="AEN202"
 690 ></A
 691 ><H2
 692 >NAME MANGLING</H2
 693 ><P
 694 >Samba supports "name mangling" so that DOS and
 695         Windows clients can use files that don't conform to the 8.3 format.
 696         It can also be set to adjust the case of 8.3 format filenames.</P
 697 ><P
 698 >There are several options that control the way mangling is
 699         performed, and they are grouped here rather than listed separately.
 700         For the defaults look at the output of the testparm program. </P
 701 ><P
 702 >All of these options can be set separately for each service
 703         (or globally, of course). </P
 704 ><P
 705 >The options are: </P
 706 ><P
 707 ></P
 708 ><DIV
 709 CLASS="VARIABLELIST"
 710 ><DL
 711 ><DT
 712 >mangle case = yes/no</DT
 713 ><DD
 714 ><P
 715 > controls if names that have characters that
 716                 aren't of the "default" case are mangled. For example,
 717                 if this is yes then a name like "Mail" would be mangled.
 718                 Default <EM
 719 >no</EM
 720 >.</P
 721 ></DD
 722 ><DT
 723 >case sensitive = yes/no</DT
 724 ><DD
 725 ><P
 726 >controls whether filenames are case sensitive. If
 727                 they aren't then Samba must do a filename search and match on passed
 728                 names. Default <EM
 729 >no</EM
 730 >.</P
 731 ></DD
 732 ><DT
 733 >default case = upper/lower</DT
 734 ><DD
 735 ><P
 736 >controls what the default case is for new
 737                 filenames. Default <EM
 738 >lower</EM
 739 >.</P
 740 ></DD
 741 ><DT
 742 >preserve case = yes/no</DT
 743 ><DD
 744 ><P
 745 >controls if new files are created with the
 746                 case that the client passes, or if they are forced to be the
 747                 "default" case. Default <EM
 748 >yes</EM
 749 >.
 750                 </P
 751 ></DD
 752 ><DT
 753 >short preserve case = yes/no</DT
 754 ><DD
 755 ><P
 756 >controls if new files which conform to 8.3 syntax,
 757                 that is all in upper case and of suitable length, are created
 758                 upper case, or if they are forced to be the "default"
 759                 case. This option can be use with "preserve case = yes"
 760                 to permit long filenames to retain their case, while short names
 761                 are lowercased. Default <EM
 762 >yes</EM
 763 >.</P
 764 ></DD
 765 ></DL
 766 ></DIV
 767 ><P
 768 >By default, Samba 2.2 has the same semantics as a Windows
 769         NT server, in that it is case insensitive but case preserving.</P
 770 ></DIV
 771 ><DIV
 772 CLASS="REFSECT1"
 773 ><A
 774 NAME="AEN235"
 775 ></A
 776 ><H2
 777 >NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2
 778 ><P
 779 >There are a number of ways in which a user can connect
 780         to a service. The server uses the following steps in determining
 781         if it will allow a connection to a specified service. If all the
 782         steps fail, then the connection request is rejected.  However, if one of the
 783         steps succeeds, then the following steps are not checked.</P
 784 ><P
 785 >If the service is marked "guest only = yes" then
 786         steps 1 to 5 are skipped.</P
 787 ><P
 788 ></P
 789 ><OL
 790 TYPE="1"
 791 ><LI
 792 ><P
 793 >If the client has passed a username/password
 794                 pair and that username/password pair is validated by the UNIX
 795                 system's password programs then the connection is made as that
 796                 username. Note that this includes the
 797                 \\server\service%<TT
 798 CLASS="REPLACEABLE"
 799 ><I
 800 >username</I
 801 ></TT
 802 > method of passing
 803                 a username.</P
 804 ></LI
 805 ><LI
 806 ><P
 807 >If the client has previously registered a username
 808                 with the system and now supplies a correct password for that
 809                 username then the connection is allowed.</P
 810 ></LI
 811 ><LI
 812 ><P
 813 >The client's NetBIOS name and any previously
 814                 used user names are checked against the supplied password, if
 815                 they match then the connection is allowed as the corresponding
 816                 user.</P
 817 ></LI
 818 ><LI
 819 ><P
 820 >If the client has previously validated a
 821                 username/password pair with the server and the client has passed
 822                 the validation token then that username is used. </P
 823 ></LI
 824 ><LI
 825 ><P
 826 >If a "user = " field is given in the
 827                 <TT
 828 CLASS="FILENAME"
 829 >smb.conf</TT
 830 > file for the service and the client
 831                 has supplied a password, and that password matches (according to
 832                 the UNIX system's password checking) with one of the usernames
 833                 from the "user =" field then the connection is made as
 834                 the username in the "user =" line. If one
 835                 of the username in the "user =" list begins with a
 836                 '@' then that name expands to a list of names in
 837                 the group of the same name.</P
 838 ></LI
 839 ><LI
 840 ><P
 841 >If the service is a guest service then a
 842                 connection is made as the username given in the "guest
 843                 account =" for the service, irrespective of the
 844                 supplied password.</P
 845 ></LI
 846 ></OL
 847 ></DIV
 848 ><DIV
 849 CLASS="REFSECT1"
 850 ><A
 851 NAME="AEN254"
 852 ></A
 853 ><H2
 854 >COMPLETE LIST OF GLOBAL PARAMETERS</H2
 855 ><P
 856 >Here is a list of all global parameters. See the section of
 857         each parameter for details.  Note that some are synonyms.</P
 858 ><P
 859 ></P
 860 ><UL
 861 ><LI
 862 ><P
 863 ><A
 864 HREF="#ABORTSHUTDOWNSCRIPT"
 865 ><TT
 866 CLASS="PARAMETER"
 867 ><I
 868 >abort shutdown script</I
 869 ></TT
 870 ></A
 871 ></P
 872 ></LI
 873 ><LI
 874 ><P
 875 ><A
 876 HREF="#ADDPRINTERCOMMAND"
 877 ><TT
 878 CLASS="PARAMETER"
 879 ><I
 880 >add printer command</I
 881 ></TT
 882 ></A
 883 ></P
 884 ></LI
 885 ><LI
 886 ><P
 887 ><A
 888 HREF="#ADDSHARECOMMAND"
 889 ><TT
 890 CLASS="PARAMETER"
 891 ><I
 892 >add share command</I
 893 ></TT
 894 ></A
 895 ></P
 896 ></LI
 897 ><LI
 898 ><P
 899 ><A
 900 HREF="#ADDUSERSCRIPT"
 901 ><TT
 902 CLASS="PARAMETER"
 903 ><I
 904 >add user script</I
 905 ></TT
 906 ></A
 907 ></P
 908 ></LI
 909 ><LI
 910 ><P
 911 ><A
 912 HREF="#ADDMACHINESCRIPT"
 913 ><TT
 914 CLASS="PARAMETER"
 915 ><I
 916 >add machine script</I
 917 ></TT
 918 ></A
 919 ></P
 920 ></LI
 921 ><LI
 922 ><P
 923 ><A
 924 HREF="#ALLOWTRUSTEDDOMAINS"
 925 ><TT
 926 CLASS="PARAMETER"
 927 ><I
 928 >allow trusted domains</I
 929 ></TT
 930 ></A
 931 ></P
 932 ></LI
 933 ><LI
 934 ><P
 935 ><A
 936 HREF="#ANNOUNCEAS"
 937 ><TT
 938 CLASS="PARAMETER"
 939 ><I
 940 >announce as</I
 941 ></TT
 942 ></A
 943 ></P
 944 ></LI
 945 ><LI
 946 ><P
 947 ><A
 948 HREF="#ANNOUNCEVERSION"
 949 ><TT
 950 CLASS="PARAMETER"
 951 ><I
 952 >announce version</I
 953 ></TT
 954 ></A
 955 ></P
 956 ></LI
 957 ><LI
 958 ><P
 959 ><A
 960 HREF="#AUTOSERVICES"
 961 ><TT
 962 CLASS="PARAMETER"
 963 ><I
 964 >auto services</I
 965 ></TT
 966 ></A
 967 ></P
 968 ></LI
 969 ><LI
 970 ><P
 971 ><A
 972 HREF="#BINDINTERFACESONLY"
 973 ><TT
 974 CLASS="PARAMETER"
 975 ><I
 976 >bind interfaces only</I
 977 ></TT
 978 ></A
 979 ></P
 980 ></LI
 981 ><LI
 982 ><P
 983 ><A
 984 HREF="#BROWSELIST"
 985 ><TT
 986 CLASS="PARAMETER"
 987 ><I
 988 >browse list</I
 989 ></TT
 990 ></A
 991 ></P
 992 ></LI
 993 ><LI
 994 ><P
 995 ><A
 996 HREF="#CHANGENOTIFYTIMEOUT"
 997 ><TT
 998 CLASS="PARAMETER"
 999 ><I
1000 >change notify timeout</I
1001 ></TT
1002 ></A
1003 ></P
1004 ></LI
1005 ><LI
1006 ><P
1007 ><A
1008 HREF="#CHANGESHARECOMMAND"
1009 ><TT
1010 CLASS="PARAMETER"
1011 ><I
1012 >change share command</I
1013 ></TT
1014 ></A
1015 ></P
1016 ></LI
1017 ><LI
1018 ><P
1019 ><A
1020 HREF="#CHARACTERSET"
1021 ><TT
1022 CLASS="PARAMETER"
1023 ><I
1024 >character set</I
1025 ></TT
1026 ></A
1027 ></P
1028 ></LI
1029 ><LI
1030 ><P
1031 ><A
1032 HREF="#CLIENTCODEPAGE"
1033 ><TT
1034 CLASS="PARAMETER"
1035 ><I
1036 >client code page</I
1037 ></TT
1038 ></A
1039 ></P
1040 ></LI
1041 ><LI
1042 ><P
1043 ><A
1044 HREF="#CODEPAGEDIRECTORY"
1045 ><TT
1046 CLASS="PARAMETER"
1047 ><I
1048 >code page directory</I
1049 ></TT
1050 ></A
1051 ></P
1052 ></LI
1053 ><LI
1054 ><P
1055 ><A
1056 HREF="#CODINGSYSTEM"
1057 ><TT
1058 CLASS="PARAMETER"
1059 ><I
1060 >coding system</I
1061 ></TT
1062 ></A
1063 ></P
1064 ></LI
1065 ><LI
1066 ><P
1067 ><A
1068 HREF="#CONFIGFILE"
1069 ><TT
1070 CLASS="PARAMETER"
1071 ><I
1072 >config file</I
1073 ></TT
1074 ></A
1075 ></P
1076 ></LI
1077 ><LI
1078 ><P
1079 ><A
1080 HREF="#DEADTIME"
1081 ><TT
1082 CLASS="PARAMETER"
1083 ><I
1084 >deadtime</I
1085 ></TT
1086 ></A
1087 ></P
1088 ></LI
1089 ><LI
1090 ><P
1091 ><A
1092 HREF="#DEBUGHIRESTIMESTAMP"
1093 ><TT
1094 CLASS="PARAMETER"
1095 ><I
1096 >debug hires timestamp</I
1097 ></TT
1098 ></A
1099 ></P
1100 ></LI
1101 ><LI
1102 ><P
1103 ><A
1104 HREF="#DEBUGPID"
1105 ><TT
1106 CLASS="PARAMETER"
1107 ><I
1108 >debug pid</I
1109 ></TT
1110 ></A
1111 ></P
1112 ></LI
1113 ><LI
1114 ><P
1115 ><A
1116 HREF="#DEBUGTIMESTAMP"
1117 ><TT
1118 CLASS="PARAMETER"
1119 ><I
1120 >debug timestamp</I
1121 ></TT
1122 ></A
1123 ></P
1124 ></LI
1125 ><LI
1126 ><P
1127 ><A
1128 HREF="#DEBUGUID"
1129 ><TT
1130 CLASS="PARAMETER"
1131 ><I
1132 >debug uid</I
1133 ></TT
1134 ></A
1135 ></P
1136 ></LI
1137 ><LI
1138 ><P
1139 ><A
1140 HREF="#DEBUGLEVEL"
1141 ><TT
1142 CLASS="PARAMETER"
1143 ><I
1144 >debuglevel</I
1145 ></TT
1146 ></A
1147 ></P
1148 ></LI
1149 ><LI
1150 ><P
1151 ><A
1152 HREF="#DEFAULT"
1153 ><TT
1154 CLASS="PARAMETER"
1155 ><I
1156 >default</I
1157 ></TT
1158 ></A
1159 ></P
1160 ></LI
1161 ><LI
1162 ><P
1163 ><A
1164 HREF="#DEFAULTSERVICE"
1165 ><TT
1166 CLASS="PARAMETER"
1167 ><I
1168 >default service</I
1169 ></TT
1170 ></A
1171 ></P
1172 ></LI
1173 ><LI
1174 ><P
1175 ><A
1176 HREF="#DELETEPRINTERCOMMAND"
1177 ><TT
1178 CLASS="PARAMETER"
1179 ><I
1180 >delete printer command</I
1181 ></TT
1182 ></A
1183 ></P
1184 ></LI
1185 ><LI
1186 ><P
1187 ><A
1188 HREF="#DELETESHARECOMMAND"
1189 ><TT
1190 CLASS="PARAMETER"
1191 ><I
1192 >delete share command</I
1193 ></TT
1194 ></A
1195 ></P
1196 ></LI
1197 ><LI
1198 ><P
1199 ><A
1200 HREF="#DELETEUSERSCRIPT"
1201 ><TT
1202 CLASS="PARAMETER"
1203 ><I
1204 >delete user script</I
1205 ></TT
1206 ></A
1207 ></P
1208 ></LI
1209 ><LI
1210 ><P
1211 ><A
1212 HREF="#DFREECOMMAND"
1213 ><TT
1214 CLASS="PARAMETER"
1215 ><I
1216 >dfree command</I
1217 ></TT
1218 ></A
1219 ></P
1220 ></LI
1221 ><LI
1222 ><P
1223 ><A
1224 HREF="#DISABLESPOOLSS"
1225 ><TT
1226 CLASS="PARAMETER"
1227 ><I
1228 >disable spoolss</I
1229 ></TT
1230 ></A
1231 ></P
1232 ></LI
1233 ><LI
1234 ><P
1235 ><A
1236 HREF="#DNSPROXY"
1237 ><TT
1238 CLASS="PARAMETER"
1239 ><I
1240 >dns proxy</I
1241 ></TT
1242 ></A
1243 ></P
1244 ></LI
1245 ><LI
1246 ><P
1247 ><A
1248 HREF="#DOMAINADMINGROUP"
1249 ><TT
1250 CLASS="PARAMETER"
1251 ><I
1252 >domain admin group</I
1253 ></TT
1254 ></A
1255 ></P
1256 ></LI
1257 ><LI
1258 ><P
1259 ><A
1260 HREF="#DOMAINGUESTGROUP"
1261 ><TT
1262 CLASS="PARAMETER"
1263 ><I
1264 >domain guest group</I
1265 ></TT
1266 ></A
1267 ></P
1268 ></LI
1269 ><LI
1270 ><P
1271 ><A
1272 HREF="#DOMAINLOGONS"
1273 ><TT
1274 CLASS="PARAMETER"
1275 ><I
1276 >domain logons</I
1277 ></TT
1278 ></A
1279 ></P
1280 ></LI
1281 ><LI
1282 ><P
1283 ><A
1284 HREF="#DOMAINMASTER"
1285 ><TT
1286 CLASS="PARAMETER"
1287 ><I
1288 >domain master</I
1289 ></TT
1290 ></A
1291 ></P
1292 ></LI
1293 ><LI
1294 ><P
1295 ><A
1296 HREF="#ENCRYPTPASSWORDS"
1297 ><TT
1298 CLASS="PARAMETER"
1299 ><I
1300 >encrypt passwords</I
1301 ></TT
1302 ></A
1303 ></P
1304 ></LI
1305 ><LI
1306 ><P
1307 ><A
1308 HREF="#ENHANCEDBROWSING"
1309 ><TT
1310 CLASS="PARAMETER"
1311 ><I
1312 >enhanced browsing</I
1313 ></TT
1314 ></A
1315 ></P
1316 ></LI
1317 ><LI
1318 ><P
1319 ><A
1320 HREF="#ENUMPORTSCOMMAND"
1321 ><TT
1322 CLASS="PARAMETER"
1323 ><I
1324 >enumports command</I
1325 ></TT
1326 ></A
1327 ></P
1328 ></LI
1329 ><LI
1330 ><P
1331 ><A
1332 HREF="#GETWDCACHE"
1333 ><TT
1334 CLASS="PARAMETER"
1335 ><I
1336 >getwd cache</I
1337 ></TT
1338 ></A
1339 ></P
1340 ></LI
1341 ><LI
1342 ><P
1343 ><A
1344 HREF="#HIDELOCALUSERS"
1345 ><TT
1346 CLASS="PARAMETER"
1347 ><I
1348 >hide local users</I
1349 ></TT
1350 ></A
1351 ></P
1352 ></LI
1353 ><LI
1354 ><P
1355 ><A
1356 HREF="#HIDEUNREADABLE"
1357 ><TT
1358 CLASS="PARAMETER"
1359 ><I
1360 >hide unreadable</I
1361 ></TT
1362 ></A
1363 ></P
1364 ></LI
1365 ><LI
1366 ><P
1367 ><A
1368 HREF="#HOMEDIRMAP"
1369 ><TT
1370 CLASS="PARAMETER"
1371 ><I
1372 >homedir map</I
1373 ></TT
1374 ></A
1375 ></P
1376 ></LI
1377 ><LI
1378 ><P
1379 ><A
1380 HREF="#HOSTMSDFS"
1381 ><TT
1382 CLASS="PARAMETER"
1383 ><I
1384 >host msdfs</I
1385 ></TT
1386 ></A
1387 ></P
1388 ></LI
1389 ><LI
1390 ><P
1391 ><A
1392 HREF="#HOSTSEQUIV"
1393 ><TT
1394 CLASS="PARAMETER"
1395 ><I
1396 >hosts equiv</I
1397 ></TT
1398 ></A
1399 ></P
1400 ></LI
1401 ><LI
1402 ><P
1403 ><A
1404 HREF="#INTERFACES"
1405 ><TT
1406 CLASS="PARAMETER"
1407 ><I
1408 >interfaces</I
1409 ></TT
1410 ></A
1411 ></P
1412 ></LI
1413 ><LI
1414 ><P
1415 ><A
1416 HREF="#KEEPALIVE"
1417 ><TT
1418 CLASS="PARAMETER"
1419 ><I
1420 >keepalive</I
1421 ></TT
1422 ></A
1423 ></P
1424 ></LI
1425 ><LI
1426 ><P
1427 ><A
1428 HREF="#KERNELOPLOCKS"
1429 ><TT
1430 CLASS="PARAMETER"
1431 ><I
1432 >kernel oplocks</I
1433 ></TT
1434 ></A
1435 ></P
1436 ></LI
1437 ><LI
1438 ><P
1439 ><A
1440 HREF="#LANMANAUTH"
1441 ><TT
1442 CLASS="PARAMETER"
1443 ><I
1444 >lanman auth</I
1445 ></TT
1446 ></A
1447 ></P
1448 ></LI
1449 ><LI
1450 ><P
1451 ><A
1452 HREF="#LARGEREADWRITE"
1453 ><TT
1454 CLASS="PARAMETER"
1455 ><I
1456 >large readwrite</I
1457 ></TT
1458 ></A
1459 ></P
1460 ></LI
1461 ><LI
1462 ><P
1463 ><A
1464 HREF="#LMANNOUNCE"
1465 ><TT
1466 CLASS="PARAMETER"
1467 ><I
1468 >lm announce</I
1469 ></TT
1470 ></A
1471 ></P
1472 ></LI
1473 ><LI
1474 ><P
1475 ><A
1476 HREF="#LMINTERVAL"
1477 ><TT
1478 CLASS="PARAMETER"
1479 ><I
1480 >lm interval</I
1481 ></TT
1482 ></A
1483 ></P
1484 ></LI
1485 ><LI
1486 ><P
1487 ><A
1488 HREF="#LOADPRINTERS"
1489 ><TT
1490 CLASS="PARAMETER"
1491 ><I
1492 >load printers</I
1493 ></TT
1494 ></A
1495 ></P
1496 ></LI
1497 ><LI
1498 ><P
1499 ><A
1500 HREF="#LOCALMASTER"
1501 ><TT
1502 CLASS="PARAMETER"
1503 ><I
1504 >local master</I
1505 ></TT
1506 ></A
1507 ></P
1508 ></LI
1509 ><LI
1510 ><P
1511 ><A
1512 HREF="#LOCKDIR"
1513 ><TT
1514 CLASS="PARAMETER"
1515 ><I
1516 >lock dir</I
1517 ></TT
1518 ></A
1519 ></P
1520 ></LI
1521 ><LI
1522 ><P
1523 ><A
1524 HREF="#LOCKDIRECTORY"
1525 ><TT
1526 CLASS="PARAMETER"
1527 ><I
1528 >lock directory</I
1529 ></TT
1530 ></A
1531 ></P
1532 ></LI
1533 ><LI
1534 ><P
1535 ><A
1536 HREF="#LOGFILE"
1537 ><TT
1538 CLASS="PARAMETER"
1539 ><I
1540 >log file</I
1541 ></TT
1542 ></A
1543 ></P
1544 ></LI
1545 ><LI
1546 ><P
1547 ><A
1548 HREF="#LOGLEVEL"
1549 ><TT
1550 CLASS="PARAMETER"
1551 ><I
1552 >log level</I
1553 ></TT
1554 ></A
1555 ></P
1556 ></LI
1557 ><LI
1558 ><P
1559 ><A
1560 HREF="#LOGONDRIVE"
1561 ><TT
1562 CLASS="PARAMETER"
1563 ><I
1564 >logon drive</I
1565 ></TT
1566 ></A
1567 ></P
1568 ></LI
1569 ><LI
1570 ><P
1571 ><A
1572 HREF="#LOGONHOME"
1573 ><TT
1574 CLASS="PARAMETER"
1575 ><I
1576 >logon home</I
1577 ></TT
1578 ></A
1579 ></P
1580 ></LI
1581 ><LI
1582 ><P
1583 ><A
1584 HREF="#LOGONPATH"
1585 ><TT
1586 CLASS="PARAMETER"
1587 ><I
1588 >logon path</I
1589 ></TT
1590 ></A
1591 ></P
1592 ></LI
1593 ><LI
1594 ><P
1595 ><A
1596 HREF="#LOGONSCRIPT"
1597 ><TT
1598 CLASS="PARAMETER"
1599 ><I
1600 >logon script</I
1601 ></TT
1602 ></A
1603 ></P
1604 ></LI
1605 ><LI
1606 ><P
1607 ><A
1608 HREF="#LPQCACHETIME"
1609 ><TT
1610 CLASS="PARAMETER"
1611 ><I
1612 >lpq cache time</I
1613 ></TT
1614 ></A
1615 ></P
1616 ></LI
1617 ><LI
1618 ><P
1619 ><A
1620 HREF="#MACHINEPASSWORDTIMEOUT"
1621 ><TT
1622 CLASS="PARAMETER"
1623 ><I
1624 >machine password timeout</I
1625 ></TT
1626 ></A
1627 ></P
1628 ></LI
1629 ><LI
1630 ><P
1631 ><A
1632 HREF="#MANGLEDSTACK"
1633 ><TT
1634 CLASS="PARAMETER"
1635 ><I
1636 >mangled stack</I
1637 ></TT
1638 ></A
1639 ></P
1640 ></LI
1641 ><LI
1642 ><P
1643 ><A
1644 HREF="#MAPTOGUEST"
1645 ><TT
1646 CLASS="PARAMETER"
1647 ><I
1648 >map to guest</I
1649 ></TT
1650 ></A
1651 ></P
1652 ></LI
1653 ><LI
1654 ><P
1655 ><A
1656 HREF="#MAXDISKSIZE"
1657 ><TT
1658 CLASS="PARAMETER"
1659 ><I
1660 >max disk size</I
1661 ></TT
1662 ></A
1663 ></P
1664 ></LI
1665 ><LI
1666 ><P
1667 ><A
1668 HREF="#MAXLOGSIZE"
1669 ><TT
1670 CLASS="PARAMETER"
1671 ><I
1672 >max log size</I
1673 ></TT
1674 ></A
1675 ></P
1676 ></LI
1677 ><LI
1678 ><P
1679 ><A
1680 HREF="#MAXMUX"
1681 ><TT
1682 CLASS="PARAMETER"
1683 ><I
1684 >max mux</I
1685 ></TT
1686 ></A
1687 ></P
1688 ></LI
1689 ><LI
1690 ><P
1691 ><A
1692 HREF="#MAXOPENFILES"
1693 ><TT
1694 CLASS="PARAMETER"
1695 ><I
1696 >max open files</I
1697 ></TT
1698 ></A
1699 ></P
1700 ></LI
1701 ><LI
1702 ><P
1703 ><A
1704 HREF="#MAXPROTOCOL"
1705 ><TT
1706 CLASS="PARAMETER"
1707 ><I
1708 >max protocol</I
1709 ></TT
1710 ></A
1711 ></P
1712 ></LI
1713 ><LI
1714 ><P
1715 ><A
1716 HREF="#MAXSMBDPROCESSES"
1717 ><TT
1718 CLASS="PARAMETER"
1719 ><I
1720 >max smbd processes</I
1721 ></TT
1722 ></A
1723 ></P
1724 ></LI
1725 ><LI
1726 ><P
1727 ><A
1728 HREF="#MAXTTL"
1729 ><TT
1730 CLASS="PARAMETER"
1731 ><I
1732 >max ttl</I
1733 ></TT
1734 ></A
1735 ></P
1736 ></LI
1737 ><LI
1738 ><P
1739 ><A
1740 HREF="#MAXWINSTTL"
1741 ><TT
1742 CLASS="PARAMETER"
1743 ><I
1744 >max wins ttl</I
1745 ></TT
1746 ></A
1747 ></P
1748 ></LI
1749 ><LI
1750 ><P
1751 ><A
1752 HREF="#MAXXMIT"
1753 ><TT
1754 CLASS="PARAMETER"
1755 ><I
1756 >max xmit</I
1757 ></TT
1758 ></A
1759 ></P
1760 ></LI
1761 ><LI
1762 ><P
1763 ><A
1764 HREF="#MESSAGECOMMAND"
1765 ><TT
1766 CLASS="PARAMETER"
1767 ><I
1768 >message command</I
1769 ></TT
1770 ></A
1771 ></P
1772 ></LI
1773 ><LI
1774 ><P
1775 ><A
1776 HREF="#MINPASSWDLENGTH"
1777 ><TT
1778 CLASS="PARAMETER"
1779 ><I
1780 >min passwd length</I
1781 ></TT
1782 ></A
1783 ></P
1784 ></LI
1785 ><LI
1786 ><P
1787 ><A
1788 HREF="#MINPASSWORDLENGTH"
1789 ><TT
1790 CLASS="PARAMETER"
1791 ><I
1792 >min password length</I
1793 ></TT
1794 ></A
1795 ></P
1796 ></LI
1797 ><LI
1798 ><P
1799 ><A
1800 HREF="#MINPROTOCOL"
1801 ><TT
1802 CLASS="PARAMETER"
1803 ><I
1804 >min protocol</I
1805 ></TT
1806 ></A
1807 ></P
1808 ></LI
1809 ><LI
1810 ><P
1811 ><A
1812 HREF="#MINWINSTTL"
1813 ><TT
1814 CLASS="PARAMETER"
1815 ><I
1816 >min wins ttl</I
1817 ></TT
1818 ></A
1819 ></P
1820 ></LI
1821 ><LI
1822 ><P
1823 ><A
1824 HREF="#NAMERESOLVEORDER"
1825 ><TT
1826 CLASS="PARAMETER"
1827 ><I
1828 >name resolve order</I
1829 ></TT
1830 ></A
1831 ></P
1832 ></LI
1833 ><LI
1834 ><P
1835 ><A
1836 HREF="#NETBIOSALIASES"
1837 ><TT
1838 CLASS="PARAMETER"
1839 ><I
1840 >netbios aliases</I
1841 ></TT
1842 ></A
1843 ></P
1844 ></LI
1845 ><LI
1846 ><P
1847 ><A
1848 HREF="#NETBIOSNAME"
1849 ><TT
1850 CLASS="PARAMETER"
1851 ><I
1852 >netbios name</I
1853 ></TT
1854 ></A
1855 ></P
1856 ></LI
1857 ><LI
1858 ><P
1859 ><A
1860 HREF="#NETBIOSSCOPE"
1861 ><TT
1862 CLASS="PARAMETER"
1863 ><I
1864 >netbios scope</I
1865 ></TT
1866 ></A
1867 ></P
1868 ></LI
1869 ><LI
1870 ><P
1871 ><A
1872 HREF="#NISHOMEDIR"
1873 ><TT
1874 CLASS="PARAMETER"
1875 ><I
1876 >nis homedir</I
1877 ></TT
1878 ></A
1879 ></P
1880 ></LI
1881 ><LI
1882 ><P
1883 ><A
1884 HREF="#NTACLSUPPORT"
1885 ><TT
1886 CLASS="PARAMETER"
1887 ><I
1888 >nt acl support</I
1889 ></TT
1890 ></A
1891 ></P
1892 ></LI
1893 ><LI
1894 ><P
1895 ><A
1896 HREF="#NTPIPESUPPORT"
1897 ><TT
1898 CLASS="PARAMETER"
1899 ><I
1900 >nt pipe support</I
1901 ></TT
1902 ></A
1903 ></P
1904 ></LI
1905 ><LI
1906 ><P
1907 ><A
1908 HREF="#NTSMBSUPPORT"
1909 ><TT
1910 CLASS="PARAMETER"
1911 ><I
1912 >nt smb support</I
1913 ></TT
1914 ></A
1915 ></P
1916 ></LI
1917 ><LI
1918 ><P
1919 ><A
1920 HREF="#NULLPASSWORDS"
1921 ><TT
1922 CLASS="PARAMETER"
1923 ><I
1924 >null passwords</I
1925 ></TT
1926 ></A
1927 ></P
1928 ></LI
1929 ><LI
1930 ><P
1931 ><A
1932 HREF="#OBEYPAMRESTRICTIONS"
1933 ><TT
1934 CLASS="PARAMETER"
1935 ><I
1936 >obey pam restrictions</I
1937 ></TT
1938 ></A
1939 ></P
1940 ></LI
1941 ><LI
1942 ><P
1943 ><A
1944 HREF="#OPLOCKBREAKWAITTIME"
1945 ><TT
1946 CLASS="PARAMETER"
1947 ><I
1948 >oplock break wait time</I
1949 ></TT
1950 ></A
1951 ></P
1952 ></LI
1953 ><LI
1954 ><P
1955 ><A
1956 HREF="#OSLEVEL"
1957 ><TT
1958 CLASS="PARAMETER"
1959 ><I
1960 >os level</I
1961 ></TT
1962 ></A
1963 ></P
1964 ></LI
1965 ><LI
1966 ><P
1967 ><A
1968 HREF="#OS2DRIVERMAP"
1969 ><TT
1970 CLASS="PARAMETER"
1971 ><I
1972 >os2 driver map</I
1973 ></TT
1974 ></A
1975 ></P
1976 ></LI
1977 ><LI
1978 ><P
1979 ><A
1980 HREF="#PAMPASSWORDCHANGE"
1981 ><TT
1982 CLASS="PARAMETER"
1983 ><I
1984 >pam password change</I
1985 ></TT
1986 ></A
1987 ></P
1988 ></LI
1989 ><LI
1990 ><P
1991 ><A
1992 HREF="#PANICACTION"
1993 ><TT
1994 CLASS="PARAMETER"
1995 ><I
1996 >panic action</I
1997 ></TT
1998 ></A
1999 ></P
2000 ></LI
2001 ><LI
2002 ><P
2003 ><A
2004 HREF="#PASSWDCHAT"
2005 ><TT
2006 CLASS="PARAMETER"
2007 ><I
2008 >passwd chat</I
2009 ></TT
2010 ></A
2011 ></P
2012 ></LI
2013 ><LI
2014 ><P
2015 ><A
2016 HREF="#PASSWDCHATDEBUG"
2017 ><TT
2018 CLASS="PARAMETER"
2019 ><I
2020 >passwd chat debug</I
2021 ></TT
2022 ></A
2023 ></P
2024 ></LI
2025 ><LI
2026 ><P
2027 ><A
2028 HREF="#PASSWDPROGRAM"
2029 ><TT
2030 CLASS="PARAMETER"
2031 ><I
2032 >passwd program</I
2033 ></TT
2034 ></A
2035 ></P
2036 ></LI
2037 ><LI
2038 ><P
2039 ><A
2040 HREF="#PASSWORDLEVEL"
2041 ><TT
2042 CLASS="PARAMETER"
2043 ><I
2044 >password level</I
2045 ></TT
2046 ></A
2047 ></P
2048 ></LI
2049 ><LI
2050 ><P
2051 ><A
2052 HREF="#PASSWORDSERVER"
2053 ><TT
2054 CLASS="PARAMETER"
2055 ><I
2056 >password server</I
2057 ></TT
2058 ></A
2059 ></P
2060 ></LI
2061 ><LI
2062 ><P
2063 ><A
2064 HREF="#PREFEREDMASTER"
2065 ><TT
2066 CLASS="PARAMETER"
2067 ><I
2068 >prefered master</I
2069 ></TT
2070 ></A
2071 ></P
2072 ></LI
2073 ><LI
2074 ><P
2075 ><A
2076 HREF="#PREFERREDMASTER"
2077 ><TT
2078 CLASS="PARAMETER"
2079 ><I
2080 >preferred master</I
2081 ></TT
2082 ></A
2083 ></P
2084 ></LI
2085 ><LI
2086 ><P
2087 ><A
2088 HREF="#PRELOAD"
2089 ><TT
2090 CLASS="PARAMETER"
2091 ><I
2092 >preload</I
2093 ></TT
2094 ></A
2095 ></P
2096 ></LI
2097 ><LI
2098 ><P
2099 ><A
2100 HREF="#PRINTCAP"
2101 ><TT
2102 CLASS="PARAMETER"
2103 ><I
2104 >printcap</I
2105 ></TT
2106 ></A
2107 ></P
2108 ></LI
2109 ><LI
2110 ><P
2111 ><A
2112 HREF="#PRINTCAPNAME"
2113 ><TT
2114 CLASS="PARAMETER"
2115 ><I
2116 >printcap name</I
2117 ></TT
2118 ></A
2119 ></P
2120 ></LI
2121 ><LI
2122 ><P
2123 ><A
2124 HREF="#PRINTERDRIVERFILE"
2125 ><TT
2126 CLASS="PARAMETER"
2127 ><I
2128 >printer driver file</I
2129 ></TT
2130 ></A
2131 ></P
2132 ></LI
2133 ><LI
2134 ><P
2135 ><A
2136 HREF="#PROTOCOL"
2137 ><TT
2138 CLASS="PARAMETER"
2139 ><I
2140 >protocol</I
2141 ></TT
2142 ></A
2143 ></P
2144 ></LI
2145 ><LI
2146 ><P
2147 ><A
2148 HREF="#READBMPX"
2149 ><TT
2150 CLASS="PARAMETER"
2151 ><I
2152 >read bmpx</I
2153 ></TT
2154 ></A
2155 ></P
2156 ></LI
2157 ><LI
2158 ><P
2159 ><A
2160 HREF="#READRAW"
2161 ><TT
2162 CLASS="PARAMETER"
2163 ><I
2164 >read raw</I
2165 ></TT
2166 ></A
2167 ></P
2168 ></LI
2169 ><LI
2170 ><P
2171 ><A
2172 HREF="#READSIZE"
2173 ><TT
2174 CLASS="PARAMETER"
2175 ><I
2176 >read size</I
2177 ></TT
2178 ></A
2179 ></P
2180 ></LI
2181 ><LI
2182 ><P
2183 ><A
2184 HREF="#REMOTEANNOUNCE"
2185 ><TT
2186 CLASS="PARAMETER"
2187 ><I
2188 >remote announce</I
2189 ></TT
2190 ></A
2191 ></P
2192 ></LI
2193 ><LI
2194 ><P
2195 ><A
2196 HREF="#REMOTEBROWSESYNC"
2197 ><TT
2198 CLASS="PARAMETER"
2199 ><I
2200 >remote browse sync</I
2201 ></TT
2202 ></A
2203 ></P
2204 ></LI
2205 ><LI
2206 ><P
2207 ><A
2208 HREF="#RESTRICTANONYMOUS"
2209 ><TT
2210 CLASS="PARAMETER"
2211 ><I
2212 >restrict anonymous</I
2213 ></TT
2214 ></A
2215 ></P
2216 ></LI
2217 ><LI
2218 ><P
2219 ><A
2220 HREF="#ROOT"
2221 ><TT
2222 CLASS="PARAMETER"
2223 ><I
2224 >root</I
2225 ></TT
2226 ></A
2227 ></P
2228 ></LI
2229 ><LI
2230 ><P
2231 ><A
2232 HREF="#ROOTDIR"
2233 ><TT
2234 CLASS="PARAMETER"
2235 ><I
2236 >root dir</I
2237 ></TT
2238 ></A
2239 ></P
2240 ></LI
2241 ><LI
2242 ><P
2243 ><A
2244 HREF="#ROOTDIRECTORY"
2245 ><TT
2246 CLASS="PARAMETER"
2247 ><I
2248 >root directory</I
2249 ></TT
2250 ></A
2251 ></P
2252 ></LI
2253 ><LI
2254 ><P
2255 ><A
2256 HREF="#SECURITY"
2257 ><TT
2258 CLASS="PARAMETER"
2259 ><I
2260 >security</I
2261 ></TT
2262 ></A
2263 ></P
2264 ></LI
2265 ><LI
2266 ><P
2267 ><A
2268 HREF="#SERVERSTRING"
2269 ><TT
2270 CLASS="PARAMETER"
2271 ><I
2272 >server string</I
2273 ></TT
2274 ></A
2275 ></P
2276 ></LI
2277 ><LI
2278 ><P
2279 ><A
2280 HREF="#SHOWADDPRINTERWIZARD"
2281 ><TT
2282 CLASS="PARAMETER"
2283 ><I
2284 >show add printer wizard</I
2285 ></TT
2286 ></A
2287 ></P
2288 ></LI
2289 ><LI
2290 ><P
2291 ><A
2292 HREF="#SHUTDOWNSCRIPT"
2293 ><TT
2294 CLASS="PARAMETER"
2295 ><I
2296 >shutdown script</I
2297 ></TT
2298 ></A
2299 ></P
2300 ></LI
2301 ><LI
2302 ><P
2303 ><A
2304 HREF="#SMBPASSWDFILE"
2305 ><TT
2306 CLASS="PARAMETER"
2307 ><I
2308 >smb passwd file</I
2309 ></TT
2310 ></A
2311 ></P
2312 ></LI
2313 ><LI
2314 ><P
2315 ><A
2316 HREF="#SOCKETADDRESS"
2317 ><TT
2318 CLASS="PARAMETER"
2319 ><I
2320 >socket address</I
2321 ></TT
2322 ></A
2323 ></P
2324 ></LI
2325 ><LI
2326 ><P
2327 ><A
2328 HREF="#SOCKETOPTIONS"
2329 ><TT
2330 CLASS="PARAMETER"
2331 ><I
2332 >socket options</I
2333 ></TT
2334 ></A
2335 ></P
2336 ></LI
2337 ><LI
2338 ><P
2339 ><A
2340 HREF="#SOURCEENVIRONMENT"
2341 ><TT
2342 CLASS="PARAMETER"
2343 ><I
2344 >source environment</I
2345 ></TT
2346 ></A
2347 ></P
2348 ></LI
2349 ><LI
2350 ><P
2351 ><A
2352 HREF="#SSL"
2353 ><TT
2354 CLASS="PARAMETER"
2355 ><I
2356 >ssl</I
2357 ></TT
2358 ></A
2359 ></P
2360 ></LI
2361 ><LI
2362 ><P
2363 ><A
2364 HREF="#SSLCACERTDIR"
2365 ><TT
2366 CLASS="PARAMETER"
2367 ><I
2368 >ssl CA certDir</I
2369 ></TT
2370 ></A
2371 ></P
2372 ></LI
2373 ><LI
2374 ><P
2375 ><A
2376 HREF="#SSLCACERTFILE"
2377 ><TT
2378 CLASS="PARAMETER"
2379 ><I
2380 >ssl CA certFile</I
2381 ></TT
2382 ></A
2383 ></P
2384 ></LI
2385 ><LI
2386 ><P
2387 ><A
2388 HREF="#SSLCIPHERS"
2389 ><TT
2390 CLASS="PARAMETER"
2391 ><I
2392 >ssl ciphers</I
2393 ></TT
2394 ></A
2395 ></P
2396 ></LI
2397 ><LI
2398 ><P
2399 ><A
2400 HREF="#SSLCLIENTCERT"
2401 ><TT
2402 CLASS="PARAMETER"
2403 ><I
2404 >ssl client cert</I
2405 ></TT
2406 ></A
2407 ></P
2408 ></LI
2409 ><LI
2410 ><P
2411 ><A
2412 HREF="#SSLCLIENTKEY"
2413 ><TT
2414 CLASS="PARAMETER"
2415 ><I
2416 >ssl client key</I
2417 ></TT
2418 ></A
2419 ></P
2420 ></LI
2421 ><LI
2422 ><P
2423 ><A
2424 HREF="#SSLCOMPATIBILITY"
2425 ><TT
2426 CLASS="PARAMETER"
2427 ><I
2428 >ssl compatibility</I
2429 ></TT
2430 ></A
2431 ></P
2432 ></LI
2433 ><LI
2434 ><P
2435 ><A
2436 HREF="#SSLHOSTS"
2437 ><TT
2438 CLASS="PARAMETER"
2439 ><I
2440 >ssl hosts</I
2441 ></TT
2442 ></A
2443 ></P
2444 ></LI
2445 ><LI
2446 ><P
2447 ><A
2448 HREF="#SSLHOSTSRESIGN"
2449 ><TT
2450 CLASS="PARAMETER"
2451 ><I
2452 >ssl hosts resign</I
2453 ></TT
2454 ></A
2455 ></P
2456 ></LI
2457 ><LI
2458 ><P
2459 ><A
2460 HREF="#SSLREQUIRECLIENTCERT"
2461 ><TT
2462 CLASS="PARAMETER"
2463 ><I
2464 >ssl require clientcert</I
2465 ></TT
2466 ></A
2467 ></P
2468 ></LI
2469 ><LI
2470 ><P
2471 ><A
2472 HREF="#SSLREQUIRESERVERCERT"
2473 ><TT
2474 CLASS="PARAMETER"
2475 ><I
2476 >ssl require servercert</I
2477 ></TT
2478 ></A
2479 ></P
2480 ></LI
2481 ><LI
2482 ><P
2483 ><A
2484 HREF="#SSLSERVERCERT"
2485 ><TT
2486 CLASS="PARAMETER"
2487 ><I
2488 >ssl server cert</I
2489 ></TT
2490 ></A
2491 ></P
2492 ></LI
2493 ><LI
2494 ><P
2495 ><A
2496 HREF="#SSLSERVERKEY"
2497 ><TT
2498 CLASS="PARAMETER"
2499 ><I
2500 >ssl server key</I
2501 ></TT
2502 ></A
2503 ></P
2504 ></LI
2505 ><LI
2506 ><P
2507 ><A
2508 HREF="#SSLVERSION"
2509 ><TT
2510 CLASS="PARAMETER"
2511 ><I
2512 >ssl version</I
2513 ></TT
2514 ></A
2515 ></P
2516 ></LI
2517 ><LI
2518 ><P
2519 ><A
2520 HREF="#STATCACHE"
2521 ><TT
2522 CLASS="PARAMETER"
2523 ><I
2524 >stat cache</I
2525 ></TT
2526 ></A
2527 ></P
2528 ></LI
2529 ><LI
2530 ><P
2531 ><A
2532 HREF="#STATCACHESIZE"
2533 ><TT
2534 CLASS="PARAMETER"
2535 ><I
2536 >stat cache size</I
2537 ></TT
2538 ></A
2539 ></P
2540 ></LI
2541 ><LI
2542 ><P
2543 ><A
2544 HREF="#STRIPDOT"
2545 ><TT
2546 CLASS="PARAMETER"
2547 ><I
2548 >strip dot</I
2549 ></TT
2550 ></A
2551 ></P
2552 ></LI
2553 ><LI
2554 ><P
2555 ><A
2556 HREF="#SYSLOG"
2557 ><TT
2558 CLASS="PARAMETER"
2559 ><I
2560 >syslog</I
2561 ></TT
2562 ></A
2563 ></P
2564 ></LI
2565 ><LI
2566 ><P
2567 ><A
2568 HREF="#SYSLOGONLY"
2569 ><TT
2570 CLASS="PARAMETER"
2571 ><I
2572 >syslog only</I
2573 ></TT
2574 ></A
2575 ></P
2576 ></LI
2577 ><LI
2578 ><P
2579 ><A
2580 HREF="#TEMPLATEHOMEDIR"
2581 ><TT
2582 CLASS="PARAMETER"
2583 ><I
2584 >template homedir</I
2585 ></TT
2586 ></A
2587 ></P
2588 ></LI
2589 ><LI
2590 ><P
2591 ><A
2592 HREF="#TEMPLATESHELL"
2593 ><TT
2594 CLASS="PARAMETER"
2595 ><I
2596 >template shell</I
2597 ></TT
2598 ></A
2599 ></P
2600 ></LI
2601 ><LI
2602 ><P
2603 ><A
2604 HREF="#TIMEOFFSET"
2605 ><TT
2606 CLASS="PARAMETER"
2607 ><I
2608 >time offset</I
2609 ></TT
2610 ></A
2611 ></P
2612 ></LI
2613 ><LI
2614 ><P
2615 ><A
2616 HREF="#TIMESERVER"
2617 ><TT
2618 CLASS="PARAMETER"
2619 ><I
2620 >time server</I
2621 ></TT
2622 ></A
2623 ></P
2624 ></LI
2625 ><LI
2626 ><P
2627 ><A
2628 HREF="#TIMESTAMPLOGS"
2629 ><TT
2630 CLASS="PARAMETER"
2631 ><I
2632 >timestamp logs</I
2633 ></TT
2634 ></A
2635 ></P
2636 ></LI
2637 ><LI
2638 ><P
2639 ><A
2640 HREF="#TOTALPRINTJOBS"
2641 ><TT
2642 CLASS="PARAMETER"
2643 ><I
2644 >total print jobs</I
2645 ></TT
2646 ></A
2647 ></P
2648 ></LI
2649 ><LI
2650 ><P
2651 ><A
2652 HREF="#UNIXPASSWORDSYNC"
2653 ><TT
2654 CLASS="PARAMETER"
2655 ><I
2656 >unix password sync</I
2657 ></TT
2658 ></A
2659 ></P
2660 ></LI
2661 ><LI
2662 ><P
2663 ><A
2664 HREF="#UPDATEENCRYPTED"
2665 ><TT
2666 CLASS="PARAMETER"
2667 ><I
2668 >update encrypted</I
2669 ></TT
2670 ></A
2671 ></P
2672 ></LI
2673 ><LI
2674 ><P
2675 ><A
2676 HREF="#USERHOSTS"
2677 ><TT
2678 CLASS="PARAMETER"
2679 ><I
2680 >use rhosts</I
2681 ></TT
2682 ></A
2683 ></P
2684 ></LI
2685 ><LI
2686 ><P
2687 ><A
2688 HREF="#USERNAMELEVEL"
2689 ><TT
2690 CLASS="PARAMETER"
2691 ><I
2692 >username level</I
2693 ></TT
2694 ></A
2695 ></P
2696 ></LI
2697 ><LI
2698 ><P
2699 ><A
2700 HREF="#USERNAMEMAP"
2701 ><TT
2702 CLASS="PARAMETER"
2703 ><I
2704 >username map</I
2705 ></TT
2706 ></A
2707 ></P
2708 ></LI
2709 ><LI
2710 ><P
2711 ><A
2712 HREF="#UTMP"
2713 ><TT
2714 CLASS="PARAMETER"
2715 ><I
2716 >utmp</I
2717 ></TT
2718 ></A
2719 ></P
2720 ></LI
2721 ><LI
2722 ><P
2723 ><A
2724 HREF="#UTMPDIRECTORY"
2725 ><TT
2726 CLASS="PARAMETER"
2727 ><I
2728 >utmp directory</I
2729 ></TT
2730 ></A
2731 ></P
2732 ></LI
2733 ><LI
2734 ><P
2735 ><A
2736 HREF="#VALIDCHARS"
2737 ><TT
2738 CLASS="PARAMETER"
2739 ><I
2740 >valid chars</I
2741 ></TT
2742 ></A
2743 ></P
2744 ></LI
2745 ><LI
2746 ><P
2747 ><A
2748 HREF="#WINBINDCACHETIME"
2749 ><TT
2750 CLASS="PARAMETER"
2751 ><I
2752 >winbind cache time</I
2753 ></TT
2754 ></A
2755 ></P
2756 ></LI
2757 ><LI
2758 ><P
2759 ><A
2760 HREF="#WINBINDGID"
2761 ><TT
2762 CLASS="PARAMETER"
2763 ><I
2764 >winbind gid</I
2765 ></TT
2766 ></A
2767 ></P
2768 ></LI
2769 ><LI
2770 ><P
2771 ><A
2772 HREF="#WINBINDSEPARATOR"
2773 ><TT
2774 CLASS="PARAMETER"
2775 ><I
2776 >winbind separator</I
2777 ></TT
2778 ></A
2779 ></P
2780 ></LI
2781 ><LI
2782 ><P
2783 ><A
2784 HREF="#WINBINDUID"
2785 ><TT
2786 CLASS="PARAMETER"
2787 ><I
2788 >winbind uid</I
2789 ></TT
2790 ></A
2791 ></P
2792 ></LI
2793 ><LI
2794 ><P
2795 ><A
2796 HREF="#WINSHOOK"
2797 ><TT
2798 CLASS="PARAMETER"
2799 ><I
2800 >wins hook</I
2801 ></TT
2802 ></A
2803 ></P
2804 ></LI
2805 ><LI
2806 ><P
2807 ><A
2808 HREF="#WINSPROXY"
2809 ><TT
2810 CLASS="PARAMETER"
2811 ><I
2812 >wins proxy</I
2813 ></TT
2814 ></A
2815 ></P
2816 ></LI
2817 ><LI
2818 ><P
2819 ><A
2820 HREF="#WINSSERVER"
2821 ><TT
2822 CLASS="PARAMETER"
2823 ><I
2824 >wins server</I
2825 ></TT
2826 ></A
2827 ></P
2828 ></LI
2829 ><LI
2830 ><P
2831 ><A
2832 HREF="#WINSSUPPORT"
2833 ><TT
2834 CLASS="PARAMETER"
2835 ><I
2836 >wins support</I
2837 ></TT
2838 ></A
2839 ></P
2840 ></LI
2841 ><LI
2842 ><P
2843 ><A
2844 HREF="#WORKGROUP"
2845 ><TT
2846 CLASS="PARAMETER"
2847 ><I
2848 >workgroup</I
2849 ></TT
2850 ></A
2851 ></P
2852 ></LI
2853 ><LI
2854 ><P
2855 ><A
2856 HREF="#WRITERAW"
2857 ><TT
2858 CLASS="PARAMETER"
2859 ><I
2860 >write raw</I
2861 ></TT
2862 ></A
2863 ></P
2864 ></LI
2865 ></UL
2866 ></DIV
2867 ><DIV
2868 CLASS="REFSECT1"
2869 ><A
2870 NAME="AEN926"
2871 ></A
2872 ><H2
2873 >COMPLETE LIST OF SERVICE PARAMETERS</H2
2874 ><P
2875 >Here is a list of all service parameters. See the section on
2876         each parameter for details. Note that some are synonyms.</P
2877 ><P
2878 ></P
2879 ><UL
2880 ><LI
2881 ><P
2882 ><A
2883 HREF="#ADMINUSERS"
2884 ><TT
2885 CLASS="PARAMETER"
2886 ><I
2887 >admin users</I
2888 ></TT
2889 ></A
2890 ></P
2891 ></LI
2892 ><LI
2893 ><P
2894 ><A
2895 HREF="#ALLOWHOSTS"
2896 ><TT
2897 CLASS="PARAMETER"
2898 ><I
2899 >allow hosts</I
2900 ></TT
2901 ></A
2902 ></P
2903 ></LI
2904 ><LI
2905 ><P
2906 ><A
2907 HREF="#AVAILABLE"
2908 ><TT
2909 CLASS="PARAMETER"
2910 ><I
2911 >available</I
2912 ></TT
2913 ></A
2914 ></P
2915 ></LI
2916 ><LI
2917 ><P
2918 ><A
2919 HREF="#BLOCKINGLOCKS"
2920 ><TT
2921 CLASS="PARAMETER"
2922 ><I
2923 >blocking locks</I
2924 ></TT
2925 ></A
2926 ></P
2927 ></LI
2928 ><LI
2929 ><P
2930 ><A
2931 HREF="#BROWSABLE"
2932 ><TT
2933 CLASS="PARAMETER"
2934 ><I
2935 >browsable</I
2936 ></TT
2937 ></A
2938 ></P
2939 ></LI
2940 ><LI
2941 ><P
2942 ><A
2943 HREF="#BROWSEABLE"
2944 ><TT
2945 CLASS="PARAMETER"
2946 ><I
2947 >browseable</I
2948 ></TT
2949 ></A
2950 ></P
2951 ></LI
2952 ><LI
2953 ><P
2954 ><A
2955 HREF="#CASESENSITIVE"
2956 ><TT
2957 CLASS="PARAMETER"
2958 ><I
2959 >case sensitive</I
2960 ></TT
2961 ></A
2962 ></P
2963 ></LI
2964 ><LI
2965 ><P
2966 ><A
2967 HREF="#CASESIGNAMES"
2968 ><TT
2969 CLASS="PARAMETER"
2970 ><I
2971 >casesignames</I
2972 ></TT
2973 ></A
2974 ></P
2975 ></LI
2976 ><LI
2977 ><P
2978 ><A
2979 HREF="#COMMENT"
2980 ><TT
2981 CLASS="PARAMETER"
2982 ><I
2983 >comment</I
2984 ></TT
2985 ></A
2986 ></P
2987 ></LI
2988 ><LI
2989 ><P
2990 ><A
2991 HREF="#COPY"
2992 ><TT
2993 CLASS="PARAMETER"
2994 ><I
2995 >copy</I
2996 ></TT
2997 ></A
2998 ></P
2999 ></LI
3000 ><LI
3001 ><P
3002 ><A
3003 HREF="#CREATEMASK"
3004 ><TT
3005 CLASS="PARAMETER"
3006 ><I
3007 >create mask</I
3008 ></TT
3009 ></A
3010 ></P
3011 ></LI
3012 ><LI
3013 ><P
3014 ><A
3015 HREF="#CREATEMODE"
3016 ><TT
3017 CLASS="PARAMETER"
3018 ><I
3019 >create mode</I
3020 ></TT
3021 ></A
3022 ></P
3023 ></LI
3024 ><LI
3025 ><P
3026 ><A
3027 HREF="#DEFAULTCASE"
3028 ><TT
3029 CLASS="PARAMETER"
3030 ><I
3031 >default case</I
3032 ></TT
3033 ></A
3034 ></P
3035 ></LI
3036 ><LI
3037 ><P
3038 ><A
3039 HREF="#DELETEREADONLY"
3040 ><TT
3041 CLASS="PARAMETER"
3042 ><I
3043 >delete readonly</I
3044 ></TT
3045 ></A
3046 ></P
3047 ></LI
3048 ><LI
3049 ><P
3050 ><A
3051 HREF="#DELETEVETOFILES"
3052 ><TT
3053 CLASS="PARAMETER"
3054 ><I
3055 >delete veto files</I
3056 ></TT
3057 ></A
3058 ></P
3059 ></LI
3060 ><LI
3061 ><P
3062 ><A
3063 HREF="#DENYHOSTS"
3064 ><TT
3065 CLASS="PARAMETER"
3066 ><I
3067 >deny hosts</I
3068 ></TT
3069 ></A
3070 ></P
3071 ></LI
3072 ><LI
3073 ><P
3074 ><A
3075 HREF="#DIRECTORY"
3076 ><TT
3077 CLASS="PARAMETER"
3078 ><I
3079 >directory</I
3080 ></TT
3081 ></A
3082 ></P
3083 ></LI
3084 ><LI
3085 ><P
3086 ><A
3087 HREF="#DIRECTORYMASK"
3088 ><TT
3089 CLASS="PARAMETER"
3090 ><I
3091 >directory mask</I
3092 ></TT
3093 ></A
3094 ></P
3095 ></LI
3096 ><LI
3097 ><P
3098 ><A
3099 HREF="#DIRECTORYMODE"
3100 ><TT
3101 CLASS="PARAMETER"
3102 ><I
3103 >directory mode</I
3104 ></TT
3105 ></A
3106 ></P
3107 ></LI
3108 ><LI
3109 ><P
3110 ><A
3111 HREF="#DIRECTORYSECURITYMASK"
3112 ><TT
3113 CLASS="PARAMETER"
3114 ><I
3115 >directory security mask</I
3116 ></TT
3117 ></A
3118 ></P
3119 ></LI
3120 ><LI
3121 ><P
3122 ><A
3123 HREF="#DONTDESCEND"
3124 ><TT
3125 CLASS="PARAMETER"
3126 ><I
3127 >dont descend</I
3128 ></TT
3129 ></A
3130 ></P
3131 ></LI
3132 ><LI
3133 ><P
3134 ><A
3135 HREF="#DOSFILEMODE"
3136 ><TT
3137 CLASS="PARAMETER"
3138 ><I
3139 >dos filemode</I
3140 ></TT
3141 ></A
3142 ></P
3143 ></LI
3144 ><LI
3145 ><P
3146 ><A
3147 HREF="#DOSFILETIMERESOLUTION"
3148 ><TT
3149 CLASS="PARAMETER"
3150 ><I
3151 >dos filetime resolution</I
3152 ></TT
3153 ></A
3154 ></P
3155 ></LI
3156 ><LI
3157 ><P
3158 ><A
3159 HREF="#DOSFILETIMES"
3160 ><TT
3161 CLASS="PARAMETER"
3162 ><I
3163 >dos filetimes</I
3164 ></TT
3165 ></A
3166 ></P
3167 ></LI
3168 ><LI
3169 ><P
3170 ><A
3171 HREF="#EXEC"
3172 ><TT
3173 CLASS="PARAMETER"
3174 ><I
3175 >exec</I
3176 ></TT
3177 ></A
3178 ></P
3179 ></LI
3180 ><LI
3181 ><P
3182 ><A
3183 HREF="#FAKEDIRECTORYCREATETIMES"
3184 ><TT
3185 CLASS="PARAMETER"
3186 ><I
3187 >fake directory create times</I
3188 ></TT
3189 ></A
3190 ></P
3191 ></LI
3192 ><LI
3193 ><P
3194 ><A
3195 HREF="#FAKEOPLOCKS"
3196 ><TT
3197 CLASS="PARAMETER"
3198 ><I
3199 >fake oplocks</I
3200 ></TT
3201 ></A
3202 ></P
3203 ></LI
3204 ><LI
3205 ><P
3206 ><A
3207 HREF="#FOLLOWSYMLINKS"
3208 ><TT
3209 CLASS="PARAMETER"
3210 ><I
3211 >follow symlinks</I
3212 ></TT
3213 ></A
3214 ></P
3215 ></LI
3216 ><LI
3217 ><P
3218 ><A
3219 HREF="#FORCECREATEMODE"
3220 ><TT
3221 CLASS="PARAMETER"
3222 ><I
3223 >force create mode</I
3224 ></TT
3225 ></A
3226 ></P
3227 ></LI
3228 ><LI
3229 ><P
3230 ><A
3231 HREF="#FORCEDIRECTORYMODE"
3232 ><TT
3233 CLASS="PARAMETER"
3234 ><I
3235 >force directory mode</I
3236 ></TT
3237 ></A
3238 ></P
3239 ></LI
3240 ><LI
3241 ><P
3242 ><A
3243 HREF="#FORCEDIRECTORYSECURITYMODE"
3244 ><TT
3245 CLASS="PARAMETER"
3246 ><I
3247 >force directory security mode</I
3248 ></TT
3249 ></A
3250 ></P
3251 ></LI
3252 ><LI
3253 ><P
3254 ><A
3255 HREF="#FORCEGROUP"
3256 ><TT
3257 CLASS="PARAMETER"
3258 ><I
3259 >force group</I
3260 ></TT
3261 ></A
3262 ></P
3263 ></LI
3264 ><LI
3265 ><P
3266 ><A
3267 HREF="#FORCESECURITYMODE"
3268 ><TT
3269 CLASS="PARAMETER"
3270 ><I
3271 >force security mode</I
3272 ></TT
3273 ></A
3274 ></P
3275 ></LI
3276 ><LI
3277 ><P
3278 ><A
3279 HREF="#FORCEUSER"
3280 ><TT
3281 CLASS="PARAMETER"
3282 ><I
3283 >force user</I
3284 ></TT
3285 ></A
3286 ></P
3287 ></LI
3288 ><LI
3289 ><P
3290 ><A
3291 HREF="#FSTYPE"
3292 ><TT
3293 CLASS="PARAMETER"
3294 ><I
3295 >fstype</I
3296 ></TT
3297 ></A
3298 ></P
3299 ></LI
3300 ><LI
3301 ><P
3302 ><A
3303 HREF="#GROUP"
3304 ><TT
3305 CLASS="PARAMETER"
3306 ><I
3307 >group</I
3308 ></TT
3309 ></A
3310 ></P
3311 ></LI
3312 ><LI
3313 ><P
3314 ><A
3315 HREF="#GUESTACCOUNT"
3316 ><TT
3317 CLASS="PARAMETER"
3318 ><I
3319 >guest account</I
3320 ></TT
3321 ></A
3322 ></P
3323 ></LI
3324 ><LI
3325 ><P
3326 ><A
3327 HREF="#GUESTOK"
3328 ><TT
3329 CLASS="PARAMETER"
3330 ><I
3331 >guest ok</I
3332 ></TT
3333 ></A
3334 ></P
3335 ></LI
3336 ><LI
3337 ><P
3338 ><A
3339 HREF="#GUESTONLY"
3340 ><TT
3341 CLASS="PARAMETER"
3342 ><I
3343 >guest only</I
3344 ></TT
3345 ></A
3346 ></P
3347 ></LI
3348 ><LI
3349 ><P
3350 ><A
3351 HREF="#HIDEDOTFILES"
3352 ><TT
3353 CLASS="PARAMETER"
3354 ><I
3355 >hide dot files</I
3356 ></TT
3357 ></A
3358 ></P
3359 ></LI
3360 ><LI
3361 ><P
3362 ><A
3363 HREF="#HIDEFILES"
3364 ><TT
3365 CLASS="PARAMETER"
3366 ><I
3367 >hide files</I
3368 ></TT
3369 ></A
3370 ></P
3371 ></LI
3372 ><LI
3373 ><P
3374 ><A
3375 HREF="#HOSTSALLOW"
3376 ><TT
3377 CLASS="PARAMETER"
3378 ><I
3379 >hosts allow</I
3380 ></TT
3381 ></A
3382 ></P
3383 ></LI
3384 ><LI
3385 ><P
3386 ><A
3387 HREF="#HOSTSDENY"
3388 ><TT
3389 CLASS="PARAMETER"
3390 ><I
3391 >hosts deny</I
3392 ></TT
3393 ></A
3394 ></P
3395 ></LI
3396 ><LI
3397 ><P
3398 ><A
3399 HREF="#INCLUDE"
3400 ><TT
3401 CLASS="PARAMETER"
3402 ><I
3403 >include</I
3404 ></TT
3405 ></A
3406 ></P
3407 ></LI
3408 ><LI
3409 ><P
3410 ><A
3411 HREF="#INHERITPERMISSIONS"
3412 ><TT
3413 CLASS="PARAMETER"
3414 ><I
3415 >inherit permissions</I
3416 ></TT
3417 ></A
3418 ></P
3419 ></LI
3420 ><LI
3421 ><P
3422 ><A
3423 HREF="#INVALIDUSERS"
3424 ><TT
3425 CLASS="PARAMETER"
3426 ><I
3427 >invalid users</I
3428 ></TT
3429 ></A
3430 ></P
3431 ></LI
3432 ><LI
3433 ><P
3434 ><A
3435 HREF="#LEVEL2OPLOCKS"
3436 ><TT
3437 CLASS="PARAMETER"
3438 ><I
3439 >level2 oplocks</I
3440 ></TT
3441 ></A
3442 ></P
3443 ></LI
3444 ><LI
3445 ><P
3446 ><A
3447 HREF="#LOCKING"
3448 ><TT
3449 CLASS="PARAMETER"
3450 ><I
3451 >locking</I
3452 ></TT
3453 ></A
3454 ></P
3455 ></LI
3456 ><LI
3457 ><P
3458 ><A
3459 HREF="#LPPAUSECOMMAND"
3460 ><TT
3461 CLASS="PARAMETER"
3462 ><I
3463 >lppause command</I
3464 ></TT
3465 ></A
3466 ></P
3467 ></LI
3468 ><LI
3469 ><P
3470 ><A
3471 HREF="#LPQCOMMAND"
3472 ><TT
3473 CLASS="PARAMETER"
3474 ><I
3475 >lpq command</I
3476 ></TT
3477 ></A
3478 ></P
3479 ></LI
3480 ><LI
3481 ><P
3482 ><A
3483 HREF="#LPRESUMECOMMAND"
3484 ><TT
3485 CLASS="PARAMETER"
3486 ><I
3487 >lpresume command</I
3488 ></TT
3489 ></A
3490 ></P
3491 ></LI
3492 ><LI
3493 ><P
3494 ><A
3495 HREF="#LPRMCOMMAND"
3496 ><TT
3497 CLASS="PARAMETER"
3498 ><I
3499 >lprm command</I
3500 ></TT
3501 ></A
3502 ></P
3503 ></LI
3504 ><LI
3505 ><P
3506 ><A
3507 HREF="#MAGICOUTPUT"
3508 ><TT
3509 CLASS="PARAMETER"
3510 ><I
3511 >magic output</I
3512 ></TT
3513 ></A
3514 ></P
3515 ></LI
3516 ><LI
3517 ><P
3518 ><A
3519 HREF="#MAGICSCRIPT"
3520 ><TT
3521 CLASS="PARAMETER"
3522 ><I
3523 >magic script</I
3524 ></TT
3525 ></A
3526 ></P
3527 ></LI
3528 ><LI
3529 ><P
3530 ><A
3531 HREF="#MANGLECASE"
3532 ><TT
3533 CLASS="PARAMETER"
3534 ><I
3535 >mangle case</I
3536 ></TT
3537 ></A
3538 ></P
3539 ></LI
3540 ><LI
3541 ><P
3542 ><A
3543 HREF="#MANGLEDMAP"
3544 ><TT
3545 CLASS="PARAMETER"
3546 ><I
3547 >mangled map</I
3548 ></TT
3549 ></A
3550 ></P
3551 ></LI
3552 ><LI
3553 ><P
3554 ><A
3555 HREF="#MANGLEDNAMES"
3556 ><TT
3557 CLASS="PARAMETER"
3558 ><I
3559 >mangled names</I
3560 ></TT
3561 ></A
3562 ></P
3563 ></LI
3564 ><LI
3565 ><P
3566 ><A
3567 HREF="#MANGLINGCHAR"
3568 ><TT
3569 CLASS="PARAMETER"
3570 ><I
3571 >mangling char</I
3572 ></TT
3573 ></A
3574 ></P
3575 ></LI
3576 ><LI
3577 ><P
3578 ><A
3579 HREF="#MAPARCHIVE"
3580 ><TT
3581 CLASS="PARAMETER"
3582 ><I
3583 >map archive</I
3584 ></TT
3585 ></A
3586 ></P
3587 ></LI
3588 ><LI
3589 ><P
3590 ><A
3591 HREF="#MAPHIDDEN"
3592 ><TT
3593 CLASS="PARAMETER"
3594 ><I
3595 >map hidden</I
3596 ></TT
3597 ></A
3598 ></P
3599 ></LI
3600 ><LI
3601 ><P
3602 ><A
3603 HREF="#MAPSYSTEM"
3604 ><TT
3605 CLASS="PARAMETER"
3606 ><I
3607 >map system</I
3608 ></TT
3609 ></A
3610 ></P
3611 ></LI
3612 ><LI
3613 ><P
3614 ><A
3615 HREF="#MAXCONNECTIONS"
3616 ><TT
3617 CLASS="PARAMETER"
3618 ><I
3619 >max connections</I
3620 ></TT
3621 ></A
3622 ></P
3623 ></LI
3624 ><LI
3625 ><P
3626 ><A
3627 HREF="#MAXPRINTJOBS"
3628 ><TT
3629 CLASS="PARAMETER"
3630 ><I
3631 >max print jobs</I
3632 ></TT
3633 ></A
3634 ></P
3635 ></LI
3636 ><LI
3637 ><P
3638 ><A
3639 HREF="#MINPRINTSPACE"
3640 ><TT
3641 CLASS="PARAMETER"
3642 ><I
3643 >min print space</I
3644 ></TT
3645 ></A
3646 ></P
3647 ></LI
3648 ><LI
3649 ><P
3650 ><A
3651 HREF="#MSDFSROOT"
3652 ><TT
3653 CLASS="PARAMETER"
3654 ><I
3655 >msdfs root</I
3656 ></TT
3657 ></A
3658 ></P
3659 ></LI
3660 ><LI
3661 ><P
3662 ><A
3663 HREF="#ONLYGUEST"
3664 ><TT
3665 CLASS="PARAMETER"
3666 ><I
3667 >only guest</I
3668 ></TT
3669 ></A
3670 ></P
3671 ></LI
3672 ><LI
3673 ><P
3674 ><A
3675 HREF="#ONLYUSER"
3676 ><TT
3677 CLASS="PARAMETER"
3678 ><I
3679 >only user</I
3680 ></TT
3681 ></A
3682 ></P
3683 ></LI
3684 ><LI
3685 ><P
3686 ><A
3687 HREF="#OPLOCKCONTENTIONLIMIT"
3688 ><TT
3689 CLASS="PARAMETER"
3690 ><I
3691 >oplock contention limit</I
3692 ></TT
3693 ></A
3694 ></P
3695 ></LI
3696 ><LI
3697 ><P
3698 ><A
3699 HREF="#OPLOCKS"
3700 ><TT
3701 CLASS="PARAMETER"
3702 ><I
3703 >oplocks</I
3704 ></TT
3705 ></A
3706 ></P
3707 ></LI
3708 ><LI
3709 ><P
3710 ><A
3711 HREF="#PATH"
3712 ><TT
3713 CLASS="PARAMETER"
3714 ><I
3715 >path</I
3716 ></TT
3717 ></A
3718 ></P
3719 ></LI
3720 ><LI
3721 ><P
3722 ><A
3723 HREF="#POSIXLOCKING"
3724 ><TT
3725 CLASS="PARAMETER"
3726 ><I
3727 >posix locking</I
3728 ></TT
3729 ></A
3730 ></P
3731 ></LI
3732 ><LI
3733 ><P
3734 ><A
3735 HREF="#POSTEXEC"
3736 ><TT
3737 CLASS="PARAMETER"
3738 ><I
3739 >postexec</I
3740 ></TT
3741 ></A
3742 ></P
3743 ></LI
3744 ><LI
3745 ><P
3746 ><A
3747 HREF="#POSTSCRIPT"
3748 ><TT
3749 CLASS="PARAMETER"
3750 ><I
3751 >postscript</I
3752 ></TT
3753 ></A
3754 ></P
3755 ></LI
3756 ><LI
3757 ><P
3758 ><A
3759 HREF="#PREEXEC"
3760 ><TT
3761 CLASS="PARAMETER"
3762 ><I
3763 >preexec</I
3764 ></TT
3765 ></A
3766 ></P
3767 ></LI
3768 ><LI
3769 ><P
3770 ><A
3771 HREF="#PREEXECCLOSE"
3772 ><TT
3773 CLASS="PARAMETER"
3774 ><I
3775 >preexec close</I
3776 ></TT
3777 ></A
3778 ></P
3779 ></LI
3780 ><LI
3781 ><P
3782 ><A
3783 HREF="#PRESERVECASE"
3784 ><TT
3785 CLASS="PARAMETER"
3786 ><I
3787 >preserve case</I
3788 ></TT
3789 ></A
3790 ></P
3791 ></LI
3792 ><LI
3793 ><P
3794 ><A
3795 HREF="#PRINTCOMMAND"
3796 ><TT
3797 CLASS="PARAMETER"
3798 ><I
3799 >print command</I
3800 ></TT
3801 ></A
3802 ></P
3803 ></LI
3804 ><LI
3805 ><P
3806 ><A
3807 HREF="#PRINTOK"
3808 ><TT
3809 CLASS="PARAMETER"
3810 ><I
3811 >print ok</I
3812 ></TT
3813 ></A
3814 ></P
3815 ></LI
3816 ><LI
3817 ><P
3818 ><A
3819 HREF="#PRINTABLE"
3820 ><TT
3821 CLASS="PARAMETER"
3822 ><I
3823 >printable</I
3824 ></TT
3825 ></A
3826 ></P
3827 ></LI
3828 ><LI
3829 ><P
3830 ><A
3831 HREF="#PRINTER"
3832 ><TT
3833 CLASS="PARAMETER"
3834 ><I
3835 >printer</I
3836 ></TT
3837 ></A
3838 ></P
3839 ></LI
3840 ><LI
3841 ><P
3842 ><A
3843 HREF="#PRINTERADMIN"
3844 ><TT
3845 CLASS="PARAMETER"
3846 ><I
3847 >printer admin</I
3848 ></TT
3849 ></A
3850 ></P
3851 ></LI
3852 ><LI
3853 ><P
3854 ><A
3855 HREF="#PRINTERDRIVER"
3856 ><TT
3857 CLASS="PARAMETER"
3858 ><I
3859 >printer driver</I
3860 ></TT
3861 ></A
3862 ></P
3863 ></LI
3864 ><LI
3865 ><P
3866 ><A
3867 HREF="#PRINTERDRIVERLOCATION"
3868 ><TT
3869 CLASS="PARAMETER"
3870 ><I
3871 >printer driver location</I
3872 ></TT
3873 ></A
3874 ></P
3875 ></LI
3876 ><LI
3877 ><P
3878 ><A
3879 HREF="#PRINTERNAME"
3880 ><TT
3881 CLASS="PARAMETER"
3882 ><I
3883 >printer name</I
3884 ></TT
3885 ></A
3886 ></P
3887 ></LI
3888 ><LI
3889 ><P
3890 ><A
3891 HREF="#PRINTING"
3892 ><TT
3893 CLASS="PARAMETER"
3894 ><I
3895 >printing</I
3896 ></TT
3897 ></A
3898 ></P
3899 ></LI
3900 ><LI
3901 ><P
3902 ><A
3903 HREF="#PUBLIC"
3904 ><TT
3905 CLASS="PARAMETER"
3906 ><I
3907 >public</I
3908 ></TT
3909 ></A
3910 ></P
3911 ></LI
3912 ><LI
3913 ><P
3914 ><A
3915 HREF="#QUEUEPAUSECOMMAND"
3916 ><TT
3917 CLASS="PARAMETER"
3918 ><I
3919 >queuepause command</I
3920 ></TT
3921 ></A
3922 ></P
3923 ></LI
3924 ><LI
3925 ><P
3926 ><A
3927 HREF="#QUEUERESUMECOMMAND"
3928 ><TT
3929 CLASS="PARAMETER"
3930 ><I
3931 >queueresume command</I
3932 ></TT
3933 ></A
3934 ></P
3935 ></LI
3936 ><LI
3937 ><P
3938 ><A
3939 HREF="#READLIST"
3940 ><TT
3941 CLASS="PARAMETER"
3942 ><I
3943 >read list</I
3944 ></TT
3945 ></A
3946 ></P
3947 ></LI
3948 ><LI
3949 ><P
3950 ><A
3951 HREF="#READONLY"
3952 ><TT
3953 CLASS="PARAMETER"
3954 ><I
3955 >read only</I
3956 ></TT
3957 ></A
3958 ></P
3959 ></LI
3960 ><LI
3961 ><P
3962 ><A
3963 HREF="#ROOTPOSTEXEC"
3964 ><TT
3965 CLASS="PARAMETER"
3966 ><I
3967 >root postexec</I
3968 ></TT
3969 ></A
3970 ></P
3971 ></LI
3972 ><LI
3973 ><P
3974 ><A
3975 HREF="#ROOTPREEXEC"
3976 ><TT
3977 CLASS="PARAMETER"
3978 ><I
3979 >root preexec</I
3980 ></TT
3981 ></A
3982 ></P
3983 ></LI
3984 ><LI
3985 ><P
3986 ><A
3987 HREF="#ROOTPREEXECCLOSE"
3988 ><TT
3989 CLASS="PARAMETER"
3990 ><I
3991 >root preexec close</I
3992 ></TT
3993 ></A
3994 ></P
3995 ></LI
3996 ><LI
3997 ><P
3998 ><A
3999 HREF="#SECURITYMASK"
4000 ><TT
4001 CLASS="PARAMETER"
4002 ><I
4003 >security mask</I
4004 ></TT
4005 ></A
4006 ></P
4007 ></LI
4008 ><LI
4009 ><P
4010 ><A
4011 HREF="#SETDIRECTORY"
4012 ><TT
4013 CLASS="PARAMETER"
4014 ><I
4015 >set directory</I
4016 ></TT
4017 ></A
4018 ></P
4019 ></LI
4020 ><LI
4021 ><P
4022 ><A
4023 HREF="#SHORTPRESERVECASE"
4024 ><TT
4025 CLASS="PARAMETER"
4026 ><I
4027 >short preserve case</I
4028 ></TT
4029 ></A
4030 ></P
4031 ></LI
4032 ><LI
4033 ><P
4034 ><A
4035 HREF="#STATUS"
4036 ><TT
4037 CLASS="PARAMETER"
4038 ><I
4039 >status</I
4040 ></TT
4041 ></A
4042 ></P
4043 ></LI
4044 ><LI
4045 ><P
4046 ><A
4047 HREF="#STRICTLOCKING"
4048 ><TT
4049 CLASS="PARAMETER"
4050 ><I
4051 >strict locking</I
4052 ></TT
4053 ></A
4054 ></P
4055 ></LI
4056 ><LI
4057 ><P
4058 ><A
4059 HREF="#STRICTSYNC"
4060 ><TT
4061 CLASS="PARAMETER"
4062 ><I
4063 >strict sync</I
4064 ></TT
4065 ></A
4066 ></P
4067 ></LI
4068 ><LI
4069 ><P
4070 ><A
4071 HREF="#SYNCALWAYS"
4072 ><TT
4073 CLASS="PARAMETER"
4074 ><I
4075 >sync always</I
4076 ></TT
4077 ></A
4078 ></P
4079 ></LI
4080 ><LI
4081 ><P
4082 ><A
4083 HREF="#USECLIENTDRIVER"
4084 ><TT
4085 CLASS="PARAMETER"
4086 ><I
4087 >use client driver</I
4088 ></TT
4089 ></A
4090 ></P
4091 ></LI
4092 ><LI
4093 ><P
4094 ><A
4095 HREF="#USER"
4096 ><TT
4097 CLASS="PARAMETER"
4098 ><I
4099 >user</I
4100 ></TT
4101 ></A
4102 ></P
4103 ></LI
4104 ><LI
4105 ><P
4106 ><A
4107 HREF="#USERNAME"
4108 ><TT
4109 CLASS="PARAMETER"
4110 ><I
4111 >username</I
4112 ></TT
4113 ></A
4114 ></P
4115 ></LI
4116 ><LI
4117 ><P
4118 ><A
4119 HREF="#USERS"
4120 ><TT
4121 CLASS="PARAMETER"
4122 ><I
4123 >users</I
4124 ></TT
4125 ></A
4126 ></P
4127 ></LI
4128 ><LI
4129 ><P
4130 ><A
4131 HREF="#VALIDUSERS"
4132 ><TT
4133 CLASS="PARAMETER"
4134 ><I
4135 >valid users</I
4136 ></TT
4137 ></A
4138 ></P
4139 ></LI
4140 ><LI
4141 ><P
4142 ><A
4143 HREF="#VETOFILES"
4144 ><TT
4145 CLASS="PARAMETER"
4146 ><I
4147 >veto files</I
4148 ></TT
4149 ></A
4150 ></P
4151 ></LI
4152 ><LI
4153 ><P
4154 ><A
4155 HREF="#VETOOPLOCKFILES"
4156 ><TT
4157 CLASS="PARAMETER"
4158 ><I
4159 >veto oplock files</I
4160 ></TT
4161 ></A
4162 ></P
4163 ></LI
4164 ><LI
4165 ><P
4166 ><A
4167 HREF="#VFSOBJECT"
4168 ><TT
4169 CLASS="PARAMETER"
4170 ><I
4171 >vfs object</I
4172 ></TT
4173 ></A
4174 ></P
4175 ></LI
4176 ><LI
4177 ><P
4178 ><A
4179 HREF="#VFSOPTIONS"
4180 ><TT
4181 CLASS="PARAMETER"
4182 ><I
4183 >vfs options</I
4184 ></TT
4185 ></A
4186 ></P
4187 ></LI
4188 ><LI
4189 ><P
4190 ><A
4191 HREF="#VOLUME"
4192 ><TT
4193 CLASS="PARAMETER"
4194 ><I
4195 >volume</I
4196 ></TT
4197 ></A
4198 ></P
4199 ></LI
4200 ><LI
4201 ><P
4202 ><A
4203 HREF="#WIDELINKS"
4204 ><TT
4205 CLASS="PARAMETER"
4206 ><I
4207 >wide links</I
4208 ></TT
4209 ></A
4210 ></P
4211 ></LI
4212 ><LI
4213 ><P
4214 ><A
4215 HREF="#WRITABLE"
4216 ><TT
4217 CLASS="PARAMETER"
4218 ><I
4219 >writable</I
4220 ></TT
4221 ></A
4222 ></P
4223 ></LI
4224 ><LI
4225 ><P
4226 ><A
4227 HREF="#WRITECACHESIZE"
4228 ><TT
4229 CLASS="PARAMETER"
4230 ><I
4231 >write cache size</I
4232 ></TT
4233 ></A
4234 ></P
4235 ></LI
4236 ><LI
4237 ><P
4238 ><A
4239 HREF="#WRITELIST"
4240 ><TT
4241 CLASS="PARAMETER"
4242 ><I
4243 >write list</I
4244 ></TT
4245 ></A
4246 ></P
4247 ></LI
4248 ><LI
4249 ><P
4250 ><A
4251 HREF="#WRITEOK"
4252 ><TT
4253 CLASS="PARAMETER"
4254 ><I
4255 >write ok</I
4256 ></TT
4257 ></A
4258 ></P
4259 ></LI
4260 ><LI
4261 ><P
4262 ><A
4263 HREF="#WRITEABLE"
4264 ><TT
4265 CLASS="PARAMETER"
4266 ><I
4267 >writeable</I
4268 ></TT
4269 ></A
4270 ></P
4271 ></LI
4272 ></UL
4273 ></DIV
4274 ><DIV
4275 CLASS="REFSECT1"
4276 ><A
4277 NAME="AEN1394"
4278 ></A
4279 ><H2
4280 >EXPLANATION OF EACH PARAMETER</H2
4281 ><P
4282 ></P
4283 ><DIV
4284 CLASS="VARIABLELIST"
4285 ><DL
4286 ><DT
4287 ><A
4288 NAME="ABORTSHUTDOWNSCRIPT"
4289 ></A
4290 >abort shutdown script (G)</DT
4291 ><DD
4292 ><P
4293 ><EM
4294 >This parameter only exists in the HEAD cvs branch</EM
4295 >
4296                 This a full path name to a script called by
4297                 <A
4298 HREF="smbd.8.html"
4299 TARGET="_top"
4300 ><B
4301 CLASS="COMMAND"
4302 >smbd(8)</B
4303 ></A
4304 >  that
4305                 should stop a shutdown procedure issued by the <A
4306 HREF="#SHUTDOWNSCRIPT"
4307 ><TT
4308 CLASS="PARAMETER"
4309 ><I
4310 >shutdown script</I
4311 ></TT
4312 ></A
4313 >.</P
4314 ><P
4315 >This command will be run as user.</P
4316 ><P
4317 >Default: <EM
4318 >None</EM
4319 >.</P
4320 ><P
4321 >Example: <B
4322 CLASS="COMMAND"
4323 >abort shutdown script = /sbin/shutdown -c</B
4324 ></P
4325 ></DD
4326 ><DT
4327 ><A
4328 NAME="ADDPRINTERCOMMAND"
4329 ></A
4330 >add printer command (G)</DT
4331 ><DD
4332 ><P
4333 >With the introduction of MS-RPC based printing
4334                 support for Windows NT/2000 clients in Samba 2.2, The MS Add
4335                 Printer Wizard (APW) icon is now also available in the
4336                 "Printers..." folder displayed a share listing.  The APW
4337                 allows for printers to be add remotely to a Samba or Windows
4338                 NT/2000 print server.</P
4339 ><P
4340 >For a Samba host this means that the printer must be
4341                 physically added to the underlying printing system.  The <TT
4342 CLASS="PARAMETER"
4343 ><I
4344 >add
4345                 printer command</I
4346 ></TT
4347 > defines a script to be run which
4348                 will perform the necessary operations for adding the printer
4349                 to the print system and to add the appropriate service definition
4350                 to the  <TT
4351 CLASS="FILENAME"
4352 >smb.conf</TT
4353 > file in order that it can be
4354                 shared by <A
4355 HREF="smbd.8.html"
4356 TARGET="_top"
4357 ><B
4358 CLASS="COMMAND"
4359 >smbd(8)</B
4360 >
4361                 </A
4362 >.</P
4363 ><P
4364 >The <TT
4365 CLASS="PARAMETER"
4366 ><I
4367 >add printer command</I
4368 ></TT
4369 > is
4370                 automatically invoked with the following parameter (in
4371                 order:</P
4372 ><P
4373 ></P
4374 ><UL
4375 ><LI
4376 ><P
4377 ><TT
4378 CLASS="PARAMETER"
4379 ><I
4380 >printer name</I
4381 ></TT
4382 ></P
4383 ></LI
4384 ><LI
4385 ><P
4386 ><TT
4387 CLASS="PARAMETER"
4388 ><I
4389 >share name</I
4390 ></TT
4391 ></P
4392 ></LI
4393 ><LI
4394 ><P
4395 ><TT
4396 CLASS="PARAMETER"
4397 ><I
4398 >port name</I
4399 ></TT
4400 ></P
4401 ></LI
4402 ><LI
4403 ><P
4404 ><TT
4405 CLASS="PARAMETER"
4406 ><I
4407 >driver name</I
4408 ></TT
4409 ></P
4410 ></LI
4411 ><LI
4412 ><P
4413 ><TT
4414 CLASS="PARAMETER"
4415 ><I
4416 >location</I
4417 ></TT
4418 ></P
4419 ></LI
4420 ><LI
4421 ><P
4422 ><TT
4423 CLASS="PARAMETER"
4424 ><I
4425 >Windows 9x driver location</I
4426 ></TT
4427 >
4428                         </P
4429 ></LI
4430 ></UL
4431 ><P
4432 >All parameters are filled in from the PRINTER_INFO_2 structure sent
4433                 by the Windows NT/2000 client with one exception.  The "Windows 9x
4434                 driver location" parameter is included for backwards compatibility
4435                 only.  The remaining fields in the structure are generated from answers
4436                 to the APW questions.</P
4437 ><P
4438 >Once the <TT
4439 CLASS="PARAMETER"
4440 ><I
4441 >add printer command</I
4442 ></TT
4443 > has
4444                 been executed, <B
4445 CLASS="COMMAND"
4446 >smbd</B
4447 > will reparse the <TT
4448 CLASS="FILENAME"
4449 >               smb.conf</TT
4450 > to determine if the share defined by the APW
4451                 exists.  If the sharename is still invalid, then <B
4452 CLASS="COMMAND"
4453 >smbd
4454                 </B
4455 > will return an ACCESS_DENIED error to the client.</P
4456 ><P
4457 >See also <A
4458 HREF="#DELETEPRINTERCOMMAND"
4459 ><TT
4460 CLASS="PARAMETER"
4461 ><I
4462 >               delete printer command</I
4463 ></TT
4464 ></A
4465 >, <A
4466 HREF="#PRINTING"
4467 ><TT
4468 CLASS="PARAMETER"
4469 ><I
4470 >printing</I
4471 ></TT
4472 ></A
4473 >,
4474                 <A
4475 HREF="#SHOWADDPRINTERWIZARD"
4476 ><TT
4477 CLASS="PARAMETER"
4478 ><I
4479 >show add
4480                 printer wizard</I
4481 ></TT
4482 ></A
4483 ></P
4484 ><P
4485 >Default: <EM
4486 >none</EM
4487 ></P
4488 ><P
4489 >Example: <B
4490 CLASS="COMMAND"
4491 >addprinter command = /usr/bin/addprinter
4492                 </B
4493 ></P
4494 ></DD
4495 ><DT
4496 ><A
4497 NAME="ADDSHARECOMMAND"
4498 ></A
4499 >add share command (G)</DT
4500 ><DD
4501 ><P
4502 >Samba 2.2.0 introduced the ability to dynamically
4503                 add and delete shares via the Windows NT 4.0 Server Manager.  The
4504                 <TT
4505 CLASS="PARAMETER"
4506 ><I
4507 >add share command</I
4508 ></TT
4509 > is used to define an
4510                 external program or script which will add a new service definition
4511                 to <TT
4512 CLASS="FILENAME"
4513 >smb.conf</TT
4514 >.  In order to successfully
4515                 execute the <TT
4516 CLASS="PARAMETER"
4517 ><I
4518 >add share command</I
4519 ></TT
4520 >, <B
4521 CLASS="COMMAND"
4522 >smbd</B
4523 >
4524                 requires that the administrator be connected using a root account (i.e.
4525                 uid == 0).
4526                 </P
4527 ><P
4528 >               When executed, <B
4529 CLASS="COMMAND"
4530 >smbd</B
4531 > will automatically invoke the
4532                 <TT
4533 CLASS="PARAMETER"
4534 ><I
4535 >add share command</I
4536 ></TT
4537 > with four parameters.
4538                 </P
4539 ><P
4540 ></P
4541 ><UL
4542 ><LI
4543 ><P
4544 ><TT
4545 CLASS="PARAMETER"
4546 ><I
4547 >configFile</I
4548 ></TT
4549 > - the location
4550                         of the global <TT
4551 CLASS="FILENAME"
4552 >smb.conf</TT
4553 > file.
4554                         </P
4555 ></LI
4556 ><LI
4557 ><P
4558 ><TT
4559 CLASS="PARAMETER"
4560 ><I
4561 >shareName</I
4562 ></TT
4563 > - the name of the new
4564                         share.
4565                         </P
4566 ></LI
4567 ><LI
4568 ><P
4569 ><TT
4570 CLASS="PARAMETER"
4571 ><I
4572 >pathName</I
4573 ></TT
4574 > - path to an **existing**
4575                         directory on disk.
4576                         </P
4577 ></LI
4578 ><LI
4579 ><P
4580 ><TT
4581 CLASS="PARAMETER"
4582 ><I
4583 >comment</I
4584 ></TT
4585 > - comment string to associate
4586                         with the new share.
4587                         </P
4588 ></LI
4589 ></UL
4590 ><P
4591 >               This parameter is only used for add file shares.  To add printer shares,
4592                 see the <A
4593 HREF="#ADDPRINTERCOMMAND"
4594 ><TT
4595 CLASS="PARAMETER"
4596 ><I
4597 >add printer
4598                 command</I
4599 ></TT
4600 ></A
4601 >.
4602                 </P
4603 ><P
4604 >               See also <A
4605 HREF="#CHANGESHARECOMMAND"
4606 ><TT
4607 CLASS="PARAMETER"
4608 ><I
4609 >change share
4610                 command</I
4611 ></TT
4612 ></A
4613 >, <A
4614 HREF="#DELETESHARECOMMAND"
4615 ><TT
4616 CLASS="PARAMETER"
4617 ><I
4618 >delete share
4619                 command</I
4620 ></TT
4621 ></A
4622 >.
4623                 </P
4624 ><P
4625 >Default: <EM
4626 >none</EM
4627 ></P
4628 ><P
4629 >Example: <B
4630 CLASS="COMMAND"
4631 >add share command = /usr/local/bin/addshare</B
4632 ></P
4633 ></DD
4634 ><DT
4635 ><A
4636 NAME="ADDMACHINESCRIPT"
4637 ></A
4638 >add machine script (G)</DT
4639 ><DD
4640 ><P
4641 >This is the full pathname to a script that will
4642                 be run by <A
4643 HREF="smbd.8.html"
4644 TARGET="_top"
4645 >smbd(8)</A
4646 >  when a machine is added
4647                 to it's domain using the administrator username and password method. </P
4648 ><P
4649 >This option is only required when using sam back-ends tied to the
4650                 Unix uid method of RID calculation such as smbpasswd.  This option is only
4651                 available in Samba 3.0.</P
4652 ><P
4653 >Default: <B
4654 CLASS="COMMAND"
4655 >add machine script = &#60;empty string&#62;
4656                 </B
4657 ></P
4658 ><P
4659 >Example: <B
4660 CLASS="COMMAND"
4661 >add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
4662                 </B
4663 ></P
4664 ></DD
4665 ><DT
4666 ><A
4667 NAME="ADDUSERSCRIPT"
4668 ></A
4669 >add user script (G)</DT
4670 ><DD
4671 ><P
4672 >This is the full pathname to a script that will
4673                 be run <EM
4674 >AS ROOT</EM
4675 > by <A
4676 HREF="smbd.8.html"
4677 TARGET="_top"
4678 >smbd(8)
4679                 </A
4680 > under special circumstances described below.</P
4681 ><P
4682 >Normally, a Samba server requires that UNIX users are
4683                 created for all users accessing files on this server. For sites
4684                 that use Windows NT account databases as their primary user database
4685                 creating these users and keeping the user list in sync with the
4686                 Windows NT PDC is an onerous task. This option allows <A
4687 HREF="smbd.8.html"
4688 TARGET="_top"
4689 >smbd</A
4690 > to create the required UNIX users
4691                 <EM
4692 >ON DEMAND</EM
4693 > when a user accesses the Samba server.</P
4694 ><P
4695 >In order to use this option, <A
4696 HREF="smbd.8.html"
4697 TARGET="_top"
4698 >smbd</A
4699 >
4700                 must be set to <TT
4701 CLASS="PARAMETER"
4702 ><I
4703 >security = server</I
4704 ></TT
4705 > or <TT
4706 CLASS="PARAMETER"
4707 ><I
4708 >               security = domain</I
4709 ></TT
4710 > and <TT
4711 CLASS="PARAMETER"
4712 ><I
4713 >add user script</I
4714 ></TT
4715 >
4716                 must be set to a full pathname for a script that will create a UNIX
4717                 user given one argument of <TT
4718 CLASS="PARAMETER"
4719 ><I
4720 >%u</I
4721 ></TT
4722 >, which expands into
4723                 the UNIX user name to create.</P
4724 ><P
4725 >When the Windows user attempts to access the Samba server,
4726                 at login (session setup in the SMB protocol) time, <A
4727 HREF="smbd.8.html"
4728 TARGET="_top"
4729 >               smbd</A
4730 > contacts the <TT
4731 CLASS="PARAMETER"
4732 ><I
4733 >password server</I
4734 ></TT
4735 > and
4736                 attempts to authenticate the given user with the given password. If the
4737                 authentication succeeds then <B
4738 CLASS="COMMAND"
4739 >smbd</B
4740 >
4741                 attempts to find a UNIX user in the UNIX password database to map the
4742                 Windows user into. If this lookup fails, and <TT
4743 CLASS="PARAMETER"
4744 ><I
4745 >add user script
4746                 </I
4747 ></TT
4748 > is set then <B
4749 CLASS="COMMAND"
4750 >smbd</B
4751 > will
4752                 call the specified script <EM
4753 >AS ROOT</EM
4754 >, expanding
4755                 any <TT
4756 CLASS="PARAMETER"
4757 ><I
4758 >%u</I
4759 ></TT
4760 > argument to be the user name to create.</P
4761 ><P
4762 >If this script successfully creates the user then <B
4763 CLASS="COMMAND"
4764 >smbd
4765                 </B
4766 > will continue on as though the UNIX user
4767                 already existed. In this way, UNIX users are dynamically created to
4768                 match existing Windows NT accounts.</P
4769 ><P
4770 >See also <A
4771 HREF="#SECURITY"
4772 ><TT
4773 CLASS="PARAMETER"
4774 ><I
4775 >               security</I
4776 ></TT
4777 ></A
4778 >, <A
4779 HREF="#PASSWORDSERVER"
4780 >               <TT
4781 CLASS="PARAMETER"
4782 ><I
4783 >password server</I
4784 ></TT
4785 ></A
4786 >,
4787                 <A
4788 HREF="#DELETEUSERSCRIPT"
4789 ><TT
4790 CLASS="PARAMETER"
4791 ><I
4792 >delete user
4793                 script</I
4794 ></TT
4795 ></A
4796 >.</P
4797 ><P
4798 >Default: <B
4799 CLASS="COMMAND"
4800 >add user script = &#60;empty string&#62;
4801                 </B
4802 ></P
4803 ><P
4804 >Example: <B
4805 CLASS="COMMAND"
4806 >add user script = /usr/local/samba/bin/add_user
4807                 %u</B
4808 ></P
4809 ></DD
4810 ><DT
4811 ><A
4812 NAME="ADMINUSERS"
4813 ></A
4814 >admin users (S)</DT
4815 ><DD
4816 ><P
4817 >This is a list of users who will be granted
4818                 administrative privileges on the share. This means that they
4819                 will do all file operations as the super-user (root).</P
4820 ><P
4821 >You should use this option very carefully, as any user in
4822                 this list will be able to do anything they like on the share,
4823                 irrespective of file permissions.</P
4824 ><P
4825 >Default: <EM
4826 >no admin users</EM
4827 ></P
4828 ><P
4829 >Example: <B
4830 CLASS="COMMAND"
4831 >admin users = jason</B
4832 ></P
4833 ></DD
4834 ><DT
4835 ><A
4836 NAME="ALLOWHOSTS"
4837 ></A
4838 >allow hosts (S)</DT
4839 ><DD
4840 ><P
4841 >Synonym for <A
4842 HREF="#HOSTSALLOW"
4843 >               <TT
4844 CLASS="PARAMETER"
4845 ><I
4846 >hosts allow</I
4847 ></TT
4848 ></A
4849 >.</P
4850 ></DD
4851 ><DT
4852 ><A
4853 NAME="ALLOWTRUSTEDDOMAINS"
4854 ></A
4855 >allow trusted domains (G)</DT
4856 ><DD
4857 ><P
4858 >This option only takes effect when the <A
4859 HREF="#SECURITY"
4860 ><TT
4861 CLASS="PARAMETER"
4862 ><I
4863 >security</I
4864 ></TT
4865 ></A
4866 > option is set to
4867                 <TT
4868 CLASS="CONSTANT"
4869 >server</TT
4870 > or <TT
4871 CLASS="CONSTANT"
4872 >domain</TT
4873 >.
4874                 If it is set to no, then attempts to connect to a resource from
4875                 a domain or workgroup other than the one which <A
4876 HREF="smbd.8.html"
4877 TARGET="_top"
4878 >smbd</A
4879 > is running
4880                 in will fail, even if that domain is trusted by the remote server
4881                 doing the authentication.</P
4882 ><P
4883 >This is useful if you only want your Samba server to
4884                 serve resources to users in the domain it is a member of. As
4885                 an example, suppose that there are two domains DOMA and DOMB.  DOMB
4886                 is trusted by DOMA, which contains the Samba server.  Under normal
4887                 circumstances, a user with an account in DOMB can then access the
4888                 resources of a UNIX account with the same account name on the
4889                 Samba server even if they do not have an account in DOMA.  This
4890                 can make implementing a security boundary difficult.</P
4891 ><P
4892 >Default: <B
4893 CLASS="COMMAND"
4894 >allow trusted domains = yes</B
4895 ></P
4896 ></DD
4897 ><DT
4898 ><A
4899 NAME="ANNOUNCEAS"
4900 ></A
4901 >announce as (G)</DT
4902 ><DD
4903 ><P
4904 >This specifies what type of server
4905                 <A
4906 HREF="nmbd.8.html"
4907 TARGET="_top"
4908 ><B
4909 CLASS="COMMAND"
4910 >nmbd</B
4911 ></A
4912 >
4913                 will announce itself as, to a network neighborhood browse
4914                 list. By default this is set to Windows NT. The valid options
4915                 are : "NT Server" (which can also be written as "NT"),
4916                 "NT Workstation", "Win95" or "WfW" meaning Windows NT Server,
4917                 Windows NT Workstation, Windows 95 and Windows for Workgroups
4918                 respectively. Do not change this parameter unless you have a
4919                 specific need to stop Samba appearing as an NT server as this
4920                 may prevent Samba servers from participating as browser servers
4921                 correctly.</P
4922 ><P
4923 >Default: <B
4924 CLASS="COMMAND"
4925 >announce as = NT Server</B
4926 ></P
4927 ><P
4928 >Example: <B
4929 CLASS="COMMAND"
4930 >announce as = Win95</B
4931 ></P
4932 ></DD
4933 ><DT
4934 ><A
4935 NAME="ANNOUNCEVERSION"
4936 ></A
4937 >announce version (G)</DT
4938 ><DD
4939 ><P
4940 >This specifies the major and minor version numbers
4941                 that nmbd will use when announcing itself as a server. The default
4942                 is 4.2.  Do not change this parameter unless you have a specific
4943                 need to set a Samba server to be a downlevel server.</P
4944 ><P
4945 >Default: <B
4946 CLASS="COMMAND"
4947 >announce version = 4.5</B
4948 ></P
4949 ><P
4950 >Example: <B
4951 CLASS="COMMAND"
4952 >announce version = 2.0</B
4953 ></P
4954 ></DD
4955 ><DT
4956 ><A
4957 NAME="AUTOSERVICES"
4958 ></A
4959 >auto services (G)</DT
4960 ><DD
4961 ><P
4962 >This is a synonym for the <A
4963 HREF="#PRELOAD"
4964 >               <TT
4965 CLASS="PARAMETER"
4966 ><I
4967 >preload</I
4968 ></TT
4969 ></A
4970 >.</P
4971 ></DD
4972 ><DT
4973 ><A
4974 NAME="AVAILABLE"
4975 ></A
4976 >available (S)</DT
4977 ><DD
4978 ><P
4979 >This parameter lets you "turn off" a service. If
4980                 <TT
4981 CLASS="PARAMETER"
4982 ><I
4983 >available = no</I
4984 ></TT
4985 >, then <EM
4986 >ALL</EM
4987 >
4988                 attempts to connect to the service will fail. Such failures are
4989                 logged.</P
4990 ><P
4991 >Default: <B
4992 CLASS="COMMAND"
4993 >available = yes</B
4994 ></P
4995 ></DD
4996 ><DT
4997 ><A
4998 NAME="BINDINTERFACESONLY"
4999 ></A
5000 >bind interfaces only (G)</DT
5001 ><DD
5002 ><P
5003 >This global parameter allows the Samba admin
5004                 to limit what interfaces on a machine will serve SMB requests. If
5005                 affects file service <A
5006 HREF="smbd.8.html"
5007 TARGET="_top"
5008 >smbd(8)</A
5009 > and
5010                 name service <A
5011 HREF="nmbd.8.html"
5012 TARGET="_top"
5013 >nmbd(8)</A
5014 > in slightly
5015                 different ways.</P
5016 ><P
5017 >For name service it causes <B
5018 CLASS="COMMAND"
5019 >nmbd</B
5020 > to bind
5021                 to ports 137 and 138 on the interfaces listed in the <A
5022 HREF="#INTERFACES"
5023 >interfaces</A
5024 > parameter. <B
5025 CLASS="COMMAND"
5026 >nmbd
5027                 </B
5028 > also binds to the "all addresses" interface (0.0.0.0)
5029                 on ports 137 and 138 for the purposes of reading broadcast messages.
5030                 If this option is not set then <B
5031 CLASS="COMMAND"
5032 >nmbd</B
5033 > will service
5034                 name requests on all of these sockets. If <TT
5035 CLASS="PARAMETER"
5036 ><I
5037 >bind interfaces
5038                 only</I
5039 ></TT
5040 > is set then <B
5041 CLASS="COMMAND"
5042 >nmbd</B
5043 > will check the
5044                 source address of any packets coming in on the broadcast sockets
5045                 and discard any that don't match the broadcast addresses of the
5046                 interfaces in the <TT
5047 CLASS="PARAMETER"
5048 ><I
5049 >interfaces</I
5050 ></TT
5051 > parameter list.
5052                 As unicast packets are received on the other sockets it allows
5053                 <B
5054 CLASS="COMMAND"
5055 >nmbd</B
5056 > to refuse to serve names to machines that
5057                 send packets that arrive through any interfaces not listed in the
5058                 <TT
5059 CLASS="PARAMETER"
5060 ><I
5061 >interfaces</I
5062 ></TT
5063 > list.  IP Source address spoofing
5064                 does defeat this simple check, however so it must not be used
5065                 seriously as a security feature for <B
5066 CLASS="COMMAND"
5067 >nmbd</B
5068 >.</P
5069 ><P
5070 >For file service it causes <A
5071 HREF="smbd.8.html"
5072 TARGET="_top"
5073 >smbd(8)</A
5074 >
5075                 to bind only to the interface list given in the <A
5076 HREF="#INTERFACES"
5077 >               interfaces</A
5078 > parameter. This restricts the networks that
5079                 <B
5080 CLASS="COMMAND"
5081 >smbd</B
5082 > will serve to packets coming in those
5083                 interfaces.  Note that you should not use this parameter for machines
5084                 that are serving PPP or other intermittent or non-broadcast network
5085                 interfaces as it will not cope with non-permanent interfaces.</P
5086 ><P
5087 >If <TT
5088 CLASS="PARAMETER"
5089 ><I
5090 >bind interfaces only</I
5091 ></TT
5092 > is set then
5093                 unless the network address <EM
5094 >127.0.0.1</EM
5095 > is added
5096                 to the <TT
5097 CLASS="PARAMETER"
5098 ><I
5099 >interfaces</I
5100 ></TT
5101 > parameter list <A
5102 HREF="smbpasswd.8.html"
5103 TARGET="_top"
5104 ><B
5105 CLASS="COMMAND"
5106 >smbpasswd(8)</B
5107 ></A
5108 >
5109                 and <A
5110 HREF="swat.8.html"
5111 TARGET="_top"
5112 ><B
5113 CLASS="COMMAND"
5114 >swat(8)</B
5115 ></A
5116 > may
5117                 not work as expected due to the reasons covered below.</P
5118 ><P
5119 >To change a users SMB password, the <B
5120 CLASS="COMMAND"
5121 >smbpasswd</B
5122 >
5123                 by default connects to the <EM
5124 >localhost - 127.0.0.1</EM
5125 >
5126                 address as an SMB client to issue the password change request. If
5127                 <TT
5128 CLASS="PARAMETER"
5129 ><I
5130 >bind interfaces only</I
5131 ></TT
5132 > is set then unless the
5133                 network address <EM
5134 >127.0.0.1</EM
5135 > is added to the
5136                 <TT
5137 CLASS="PARAMETER"
5138 ><I
5139 >interfaces</I
5140 ></TT
5141 > parameter list then <B
5142 CLASS="COMMAND"
5143 >               smbpasswd</B
5144 > will fail to connect in it's default mode.
5145                 <B
5146 CLASS="COMMAND"
5147 >smbpasswd</B
5148 > can be forced to use the primary IP interface
5149                 of the local host by using its <A
5150 HREF="smbpasswd.8.html#minusr"
5151 TARGET="_top"
5152 >               <TT
5153 CLASS="PARAMETER"
5154 ><I
5155 >-r <TT
5156 CLASS="REPLACEABLE"
5157 ><I
5158 >remote machine</I
5159 ></TT
5160 ></I
5161 ></TT
5162 >
5163                 </A
5164 > parameter, with <TT
5165 CLASS="REPLACEABLE"
5166 ><I
5167 >remote machine</I
5168 ></TT
5169 > set
5170                 to the IP name of the primary interface of the local host.</P
5171 ><P
5172 >The <B
5173 CLASS="COMMAND"
5174 >swat</B
5175 > status page tries to connect with
5176                 <B
5177 CLASS="COMMAND"
5178 >smbd</B
5179 > and <B
5180 CLASS="COMMAND"
5181 >nmbd</B
5182 > at the address
5183                 <EM
5184 >127.0.0.1</EM
5185 > to determine if they are running.
5186                 Not adding <EM
5187 >127.0.0.1</EM
5188 >  will cause <B
5189 CLASS="COMMAND"
5190 >               smbd</B
5191 > and <B
5192 CLASS="COMMAND"
5193 >nmbd</B
5194 > to always show
5195                 "not running" even if they really are.  This can prevent <B
5196 CLASS="COMMAND"
5197 >               swat</B
5198 > from starting/stopping/restarting <B
5199 CLASS="COMMAND"
5200 >smbd</B
5201 >
5202                 and <B
5203 CLASS="COMMAND"
5204 >nmbd</B
5205 >.</P
5206 ><P
5207 >Default: <B
5208 CLASS="COMMAND"
5209 >bind interfaces only = no</B
5210 ></P
5211 ></DD
5212 ><DT
5213 ><A
5214 NAME="BLOCKINGLOCKS"
5215 ></A
5216 >blocking locks (S)</DT
5217 ><DD
5218 ><P
5219 >This parameter controls the behavior of <A
5220 HREF="smbd.8.html"
5221 TARGET="_top"
5222 >smbd(8)</A
5223 > when given a request by a client
5224                 to obtain a byte range lock on a region of an open file, and the
5225                 request has a time limit associated with it.</P
5226 ><P
5227 >If this parameter is set and the lock range requested
5228                 cannot be immediately satisfied, Samba 2.2 will internally
5229                 queue the lock request, and periodically attempt to obtain
5230                 the lock until the timeout period expires.</P
5231 ><P
5232 >If this parameter is set to <TT
5233 CLASS="CONSTANT"
5234 >false</TT
5235 >, then
5236                 Samba 2.2 will behave as previous versions of Samba would and
5237                 will fail the lock request immediately if the lock range
5238                 cannot be obtained.</P
5239 ><P
5240 >Default: <B
5241 CLASS="COMMAND"
5242 >blocking locks = yes</B
5243 ></P
5244 ></DD
5245 ><DT
5246 ><A
5247 NAME="BROWSABLE"
5248 ></A
5249 >browsable (S)</DT
5250 ><DD
5251 ><P
5252 >See the <A
5253 HREF="#BROWSEABLE"
5254 ><TT
5255 CLASS="PARAMETER"
5256 ><I
5257 >               browseable</I
5258 ></TT
5259 ></A
5260 >.</P
5261 ></DD
5262 ><DT
5263 ><A
5264 NAME="BROWSELIST"
5265 ></A
5266 >browse list (G)</DT
5267 ><DD
5268 ><P
5269 >This controls whether <A
5270 HREF="smbd.8.html"
5271 TARGET="_top"
5272 >               <B
5273 CLASS="COMMAND"
5274 >smbd(8)</B
5275 ></A
5276 > will serve a browse list to
5277                 a client doing a <B
5278 CLASS="COMMAND"
5279 >NetServerEnum</B
5280 > call. Normally
5281                 set to <TT
5282 CLASS="CONSTANT"
5283 >true</TT
5284 >. You should never need to change
5285                 this.</P
5286 ><P
5287 >Default: <B
5288 CLASS="COMMAND"
5289 >browse list = yes</B
5290 ></P
5291 ></DD
5292 ><DT
5293 ><A
5294 NAME="BROWSEABLE"
5295 ></A
5296 >browseable (S)</DT
5297 ><DD
5298 ><P
5299 >This controls whether this share is seen in
5300                 the list of available shares in a net view and in the browse list.</P
5301 ><P
5302 >Default: <B
5303 CLASS="COMMAND"
5304 >browseable = yes</B
5305 ></P
5306 ></DD
5307 ><DT
5308 ><A
5309 NAME="CASESENSITIVE"
5310 ></A
5311 >case sensitive (S)</DT
5312 ><DD
5313 ><P
5314 >See the discussion in the section <A
5315 HREF="#AEN202"
5316 >NAME MANGLING</A
5317 >.</P
5318 ><P
5319 >Default: <B
5320 CLASS="COMMAND"
5321 >case sensitive = no</B
5322 ></P
5323 ></DD
5324 ><DT
5325 ><A
5326 NAME="CASESIGNAMES"
5327 ></A
5328 >casesignames (S)</DT
5329 ><DD
5330 ><P
5331 >Synonym for <A
5332 HREF="#CASESENSITIVE"
5333 >case
5334                 sensitive</A
5335 >.</P
5336 ></DD
5337 ><DT
5338 ><A
5339 NAME="CHANGENOTIFYTIMEOUT"
5340 ></A
5341 >change notify timeout (G)</DT
5342 ><DD
5343 ><P
5344 >This SMB allows a client to tell a server to
5345                 "watch" a particular directory for any changes and only reply to
5346                 the SMB request when a change has occurred. Such constant scanning of
5347                 a directory is expensive under UNIX, hence an <A
5348 HREF="smbd.8.html"
5349 TARGET="_top"
5350 >               <B
5351 CLASS="COMMAND"
5352 >smbd(8)</B
5353 ></A
5354 > daemon only performs such a scan
5355                 on each requested directory once every <TT
5356 CLASS="PARAMETER"
5357 ><I
5358 >change notify
5359                 timeout</I
5360 ></TT
5361 > seconds.</P
5362 ><P
5363 >Default: <B
5364 CLASS="COMMAND"
5365 >change notify timeout = 60</B
5366 ></P
5367 ><P
5368 >Example: <B
5369 CLASS="COMMAND"
5370 >change notify timeout = 300</B
5371 ></P
5372 ><P
5373 >Would change the scan time to every 5 minutes.</P
5374 ></DD
5375 ><DT
5376 ><A
5377 NAME="CHANGESHARECOMMAND"
5378 ></A
5379 >change share command (G)</DT
5380 ><DD
5381 ><P
5382 >Samba 2.2.0 introduced the ability to dynamically
5383                 add and delete shares via the Windows NT 4.0 Server Manager.  The
5384                 <TT
5385 CLASS="PARAMETER"
5386 ><I
5387 >change share command</I
5388 ></TT
5389 > is used to define an
5390                 external program or script which will modify an existing service definition
5391                 in <TT
5392 CLASS="FILENAME"
5393 >smb.conf</TT
5394 >.  In order to successfully
5395                 execute the <TT
5396 CLASS="PARAMETER"
5397 ><I
5398 >change share command</I
5399 ></TT
5400 >, <B
5401 CLASS="COMMAND"
5402 >smbd</B
5403 >
5404                 requires that the administrator be connected using a root account (i.e.
5405                 uid == 0).
5406                 </P
5407 ><P
5408 >               When executed, <B
5409 CLASS="COMMAND"
5410 >smbd</B
5411 > will automatically invoke the
5412                 <TT
5413 CLASS="PARAMETER"
5414 ><I
5415 >change share command</I
5416 ></TT
5417 > with four parameters.
5418                 </P
5419 ><P
5420 ></P
5421 ><UL
5422 ><LI
5423 ><P
5424 ><TT
5425 CLASS="PARAMETER"
5426 ><I
5427 >configFile</I
5428 ></TT
5429 > - the location
5430                         of the global <TT
5431 CLASS="FILENAME"
5432 >smb.conf</TT
5433 > file.
5434                         </P
5435 ></LI
5436 ><LI
5437 ><P
5438 ><TT
5439 CLASS="PARAMETER"
5440 ><I
5441 >shareName</I
5442 ></TT
5443 > - the name of the new
5444                         share.
5445                         </P
5446 ></LI
5447 ><LI
5448 ><P
5449 ><TT
5450 CLASS="PARAMETER"
5451 ><I
5452 >pathName</I
5453 ></TT
5454 > - path to an **existing**
5455                         directory on disk.
5456                         </P
5457 ></LI
5458 ><LI
5459 ><P
5460 ><TT
5461 CLASS="PARAMETER"
5462 ><I
5463 >comment</I
5464 ></TT
5465 > - comment string to associate
5466                         with the new share.
5467                         </P
5468 ></LI
5469 ></UL
5470 ><P
5471 >               This parameter is only used modify existing file shares definitions.  To modify
5472                 printer shares, use the "Printers..." folder as seen when browsing the Samba host.
5473                 </P
5474 ><P
5475 >               See also <A
5476 HREF="#ADDSHARECOMMAND"
5477 ><TT
5478 CLASS="PARAMETER"
5479 ><I
5480 >add share
5481                 command</I
5482 ></TT
5483 ></A
5484 >, <A
5485 HREF="#DELETESHARECOMMAND"
5486 ><TT
5487 CLASS="PARAMETER"
5488 ><I
5489 >delete
5490                 share command</I
5491 ></TT
5492 ></A
5493 >.
5494                 </P
5495 ><P
5496 >Default: <EM
5497 >none</EM
5498 ></P
5499 ><P
5500 >Example: <B
5501 CLASS="COMMAND"
5502 >change share command = /usr/local/bin/addshare</B
5503 ></P
5504 ></DD
5505 ><DT
5506 ><A
5507 NAME="CHARACTERSET"
5508 ></A
5509 >character set (G)</DT
5510 ><DD
5511 ><P
5512 >This allows <A
5513 HREF="smbd.8.html"
5514 TARGET="_top"
5515 >smbd</A
5516 > to map incoming filenames
5517                 from a DOS Code page (see the <A
5518 HREF="#CLIENTCODEPAGE"
5519 >client
5520                 code page</A
5521 > parameter) to several built in UNIX character sets.
5522                 The built in code page translations are:</P
5523 ><P
5524 ></P
5525 ><UL
5526 ><LI
5527 ><P
5528 ><TT
5529 CLASS="CONSTANT"
5530 >ISO8859-1</TT
5531 > : Western European
5532                         UNIX character set. The parameter <TT
5533 CLASS="PARAMETER"
5534 ><I
5535 >client code page</I
5536 ></TT
5537 >
5538                         <EM
5539 >MUST</EM
5540 > be set to code page 850 if the
5541                         <TT
5542 CLASS="PARAMETER"
5543 ><I
5544 >character set</I
5545 ></TT
5546 > parameter is set to
5547                         <TT
5548 CLASS="CONSTANT"
5549 >ISO8859-1</TT
5550 > in order for the conversion to the
5551                         UNIX character set to be done correctly.</P
5552 ></LI
5553 ><LI
5554 ><P
5555 ><TT
5556 CLASS="CONSTANT"
5557 >ISO8859-2</TT
5558 > : Eastern European
5559                         UNIX character set. The parameter <TT
5560 CLASS="PARAMETER"
5561 ><I
5562 >client code page
5563                         </I
5564 ></TT
5565 > <EM
5566 >MUST</EM
5567 > be set to code page 852 if
5568                         the <TT
5569 CLASS="PARAMETER"
5570 ><I
5571 > character set</I
5572 ></TT
5573 > parameter is set
5574                         to <TT
5575 CLASS="CONSTANT"
5576 >ISO8859-2</TT
5577 > in order for the conversion
5578                         to the UNIX character set to be done correctly. </P
5579 ></LI
5580 ><LI
5581 ><P
5582 ><TT
5583 CLASS="CONSTANT"
5584 >ISO8859-5</TT
5585 > : Russian Cyrillic
5586                         UNIX character set. The parameter <TT
5587 CLASS="PARAMETER"
5588 ><I
5589 >client code page
5590                         </I
5591 ></TT
5592 > <EM
5593 >MUST</EM
5594 > be set to code page
5595                         866 if the <TT
5596 CLASS="PARAMETER"
5597 ><I
5598 >character set </I
5599 ></TT
5600 > parameter is
5601                         set to <TT
5602 CLASS="CONSTANT"
5603 >ISO8859-5</TT
5604 > in order for the conversion
5605                         to the UNIX character set to be done correctly. </P
5606 ></LI
5607 ><LI
5608 ><P
5609 ><TT
5610 CLASS="CONSTANT"
5611 >ISO8859-7</TT
5612 > : Greek UNIX
5613                         character set. The parameter <TT
5614 CLASS="PARAMETER"
5615 ><I
5616 >client code page
5617                         </I
5618 ></TT
5619 > <EM
5620 >MUST</EM
5621 > be set to code page
5622                         737 if the <TT
5623 CLASS="PARAMETER"
5624 ><I
5625 >character set</I
5626 ></TT
5627 > parameter is
5628                         set to <TT
5629 CLASS="CONSTANT"
5630 >ISO8859-7</TT
5631 > in order for the conversion
5632                         to the UNIX character set to be done correctly.</P
5633 ></LI
5634 ><LI
5635 ><P
5636 ><TT
5637 CLASS="CONSTANT"
5638 >KOI8-R</TT
5639 > : Alternate mapping
5640                         for Russian Cyrillic UNIX character set. The parameter
5641                         <TT
5642 CLASS="PARAMETER"
5643 ><I
5644 >client code page</I
5645 ></TT
5646 > <EM
5647 >MUST</EM
5648 >
5649                         be set to code page 866 if the <TT
5650 CLASS="PARAMETER"
5651 ><I
5652 >character set</I
5653 ></TT
5654 >
5655                         parameter is set to <TT
5656 CLASS="CONSTANT"
5657 >KOI8-R</TT
5658 > in order for the
5659                         conversion to the UNIX character set to be done correctly.</P
5660 ></LI
5661 ></UL
5662 ><P
5663 ><EM
5664 >BUG</EM
5665 >. These MSDOS code page to UNIX character
5666                 set mappings should be dynamic, like the loading of MS DOS code pages,
5667                 not static.</P
5668 ><P
5669 >Normally this parameter is not set, meaning no filename
5670                 translation is done.</P
5671 ><P
5672 >Default: <B
5673 CLASS="COMMAND"
5674 >character set = &#60;empty string&#62;</B
5675 ></P
5676 ><P
5677 >Example: <B
5678 CLASS="COMMAND"
5679 >character set = ISO8859-1</B
5680 ></P
5681 ></DD
5682 ><DT
5683 ><A
5684 NAME="CLIENTCODEPAGE"
5685 ></A
5686 >client code page (G)</DT
5687 ><DD
5688 ><P
5689 >This parameter specifies the DOS code page
5690                 that the clients accessing Samba are using. To determine what code
5691                 page a Windows or DOS client is using, open a DOS command prompt
5692                 and type the command <B
5693 CLASS="COMMAND"
5694 >chcp</B
5695 >. This will output
5696                 the code page. The default for USA MS-DOS, Windows 95, and
5697                 Windows NT releases is code page 437. The default for western
5698                 European releases of the above operating systems is code page 850.</P
5699 ><P
5700 >This parameter tells <A
5701 HREF="smbd.8.html"
5702 TARGET="_top"
5703 >smbd(8)</A
5704 >
5705                 which of the <TT
5706 CLASS="FILENAME"
5707 >codepage.<TT
5708 CLASS="REPLACEABLE"
5709 ><I
5710 >XXX</I
5711 ></TT
5712 >
5713                 </TT
5714 > files to dynamically load on startup. These files,
5715                 described more fully in the manual page <A
5716 HREF="make_smbcodepage.1.html"
5717 TARGET="_top"
5718 >               <B
5719 CLASS="COMMAND"
5720 >make_smbcodepage(1)</B
5721 ></A
5722 >, tell <B
5723 CLASS="COMMAND"
5724 >               smbd</B
5725 > how to map lower to upper case characters to provide
5726                 the case insensitivity of filenames that Windows clients expect.</P
5727 ><P
5728 >Samba currently ships with the following code page files :</P
5729 ><P
5730 ></P
5731 ><UL
5732 ><LI
5733 ><P
5734 >Code Page 437 - MS-DOS Latin US</P
5735 ></LI
5736 ><LI
5737 ><P
5738 >Code Page 737 - Windows '95 Greek</P
5739 ></LI
5740 ><LI
5741 ><P
5742 >Code Page 850 - MS-DOS Latin 1</P
5743 ></LI
5744 ><LI
5745 ><P
5746 >Code Page 852 - MS-DOS Latin 2</P
5747 ></LI
5748 ><LI
5749 ><P
5750 >Code Page 861 - MS-DOS Icelandic</P
5751 ></LI
5752 ><LI
5753 ><P
5754 >Code Page 866 - MS-DOS Cyrillic</P
5755 ></LI
5756 ><LI
5757 ><P
5758 >Code Page 932 - MS-DOS Japanese SJIS</P
5759 ></LI
5760 ><LI
5761 ><P
5762 >Code Page 936 - MS-DOS Simplified Chinese</P
5763 ></LI
5764 ><LI
5765 ><P
5766 >Code Page 949 - MS-DOS Korean Hangul</P
5767 ></LI
5768 ><LI
5769 ><P
5770 >Code Page 950 - MS-DOS Traditional Chinese</P
5771 ></LI
5772 ></UL
5773 ><P
5774 >Thus this parameter may have any of the values 437, 737, 850, 852,
5775                 861, 932, 936, 949, or 950.  If you don't find the codepage you need,
5776                 read the comments in one of the other codepage files and the
5777                 <B
5778 CLASS="COMMAND"
5779 >make_smbcodepage(1)</B
5780 > man page and write one. Please
5781                 remember to donate it back to the Samba user community.</P
5782 ><P
5783 >This parameter co-operates with the <TT
5784 CLASS="PARAMETER"
5785 ><I
5786 >valid
5787                 chars</I
5788 ></TT
5789 > parameter in determining what characters are
5790                 valid in filenames and how capitalization is done. If you set both
5791                 this parameter and the <TT
5792 CLASS="PARAMETER"
5793 ><I
5794 >valid chars</I
5795 ></TT
5796 > parameter
5797                 the <TT
5798 CLASS="PARAMETER"
5799 ><I
5800 >client code page</I
5801 ></TT
5802 > parameter
5803                 <EM
5804 >MUST</EM
5805 > be set before the <TT
5806 CLASS="PARAMETER"
5807 ><I
5808 >valid
5809                 chars</I
5810 ></TT
5811 > parameter in the <TT
5812 CLASS="FILENAME"
5813 >smb.conf</TT
5814 >
5815                 file. The <TT
5816 CLASS="PARAMETER"
5817 ><I
5818 >valid chars</I
5819 ></TT
5820 > string will then
5821                 augment the character settings in the <TT
5822 CLASS="PARAMETER"
5823 ><I
5824 >client code page</I
5825 ></TT
5826 >
5827                 parameter.</P
5828 ><P
5829 >If not set, <TT
5830 CLASS="PARAMETER"
5831 ><I
5832 >client code page</I
5833 ></TT
5834 > defaults
5835                 to 850.</P
5836 ><P
5837 >See also : <A
5838 HREF="#VALIDCHARS"
5839 ><TT
5840 CLASS="PARAMETER"
5841 ><I
5842 >valid
5843                 chars</I
5844 ></TT
5845 ></A
5846 >, <A
5847 HREF="#CODEPAGEDIRECTORY"
5848 >               <TT
5849 CLASS="PARAMETER"
5850 ><I
5851 >code page directory</I
5852 ></TT
5853 ></A
5854 ></P
5855 ><P
5856 >Default: <B
5857 CLASS="COMMAND"
5858 >client code page = 850</B
5859 ></P
5860 ><P
5861 >Example: <B
5862 CLASS="COMMAND"
5863 >client code page = 936</B
5864 ></P
5865 ></DD
5866 ><DT
5867 ><A
5868 NAME="CODEPAGEDIRECTORY"
5869 ></A
5870 >code page directory (G)</DT
5871 ><DD
5872 ><P
5873 >Define the location of the various client code page
5874                 files.</P
5875 ><P
5876 >See also <A
5877 HREF="#CLIENTCODEPAGE"
5878 ><TT
5879 CLASS="PARAMETER"
5880 ><I
5881 >client
5882                 code page</I
5883 ></TT
5884 ></A
5885 ></P
5886 ><P
5887 >Default: <B
5888 CLASS="COMMAND"
5889 >code page directory = ${prefix}/lib/codepages
5890                 </B
5891 ></P
5892 ><P
5893 >Example: <B
5894 CLASS="COMMAND"
5895 >code page directory = /usr/share/samba/codepages
5896                 </B
5897 ></P
5898 ></DD
5899 ><DT
5900 ><A
5901 NAME="CODINGSYSTEM"
5902 ></A
5903 >coding system (G)</DT
5904 ><DD
5905 ><P
5906 >This parameter is used to determine how incoming
5907                 Shift-JIS Japanese characters are mapped from the incoming <A
5908 HREF="#CLIENTCODEPAGE"
5909 ><TT
5910 CLASS="PARAMETER"
5911 ><I
5912 >client code page</I
5913 ></TT
5914 >
5915                 </A
5916 > used by the client, into file names in the UNIX filesystem.
5917                 Only useful if <TT
5918 CLASS="PARAMETER"
5919 ><I
5920 >client code page</I
5921 ></TT
5922 > is set to
5923                 932 (Japanese Shift-JIS).  The options are :</P
5924 ><P
5925 ></P
5926 ><UL
5927 ><LI
5928 ><P
5929 ><TT
5930 CLASS="CONSTANT"
5931 >SJIS</TT
5932 >  - Shift-JIS. Does no
5933                         conversion of the incoming filename.</P
5934 ></LI
5935 ><LI
5936 ><P
5937 ><TT
5938 CLASS="CONSTANT"
5939 >JIS8, J8BB, J8BH, J8@B,
5940                         J8@J, J8@H </TT
5941 > - Convert from incoming Shift-JIS to eight
5942                         bit JIS code with different shift-in, shift out codes.</P
5943 ></LI
5944 ><LI
5945 ><P
5946 ><TT
5947 CLASS="CONSTANT"
5948 >JIS7, J7BB, J7BH, J7@B, J7@J,
5949                         J7@H </TT
5950 > - Convert from incoming Shift-JIS to seven bit
5951                         JIS code with different shift-in, shift out codes.</P
5952 ></LI
5953 ><LI
5954 ><P
5955 ><TT
5956 CLASS="CONSTANT"
5957 >JUNET, JUBB, JUBH, JU@B, JU@J, JU@H </TT
5958 >
5959                         - Convert from incoming Shift-JIS to JUNET code with different shift-in,
5960                         shift out codes.</P
5961 ></LI
5962 ><LI
5963 ><P
5964 ><TT
5965 CLASS="CONSTANT"
5966 >EUC</TT
5967 > - Convert an incoming
5968                         Shift-JIS character to EUC code.</P
5969 ></LI
5970 ><LI
5971 ><P
5972 ><TT
5973 CLASS="CONSTANT"
5974 >HEX</TT
5975 > - Convert an incoming
5976                         Shift-JIS character to a 3 byte hex representation, i.e.
5977                         <TT
5978 CLASS="CONSTANT"
5979 >:AB</TT
5980 >.</P
5981 ></LI
5982 ><LI
5983 ><P
5984 ><TT
5985 CLASS="CONSTANT"
5986 >CAP</TT
5987 > - Convert an incoming
5988                         Shift-JIS character to the 3 byte hex representation used by
5989                         the Columbia AppleTalk Program (CAP), i.e. <TT
5990 CLASS="CONSTANT"
5991 >:AB</TT
5992 >.
5993                         This is used for compatibility between Samba and CAP.</P
5994 ></LI
5995 ></UL
5996 ><P
5997 >Default: <B
5998 CLASS="COMMAND"
5999 >coding system = &#60;empty value&#62;</B
6000 >
6001                 </P
6002 ></DD
6003 ><DT
6004 ><A
6005 NAME="COMMENT"
6006 ></A
6007 >comment (S)</DT
6008 ><DD
6009 ><P
6010 >This is a text field that is seen next to a share
6011                 when a client does a queries the server, either via the network
6012                 neighborhood or via <B
6013 CLASS="COMMAND"
6014 >net view</B
6015 > to list what shares
6016                 are available.</P
6017 ><P
6018 >If you want to set the string that is displayed next to the
6019                 machine name then see the <A
6020 HREF="#SERVERSTRING"
6021 ><TT
6022 CLASS="PARAMETER"
6023 ><I
6024 >               server string</I
6025 ></TT
6026 ></A
6027 > parameter.</P
6028 ><P
6029 >Default: <EM
6030 >No comment string</EM
6031 ></P
6032 ><P
6033 >Example: <B
6034 CLASS="COMMAND"
6035 >comment = Fred's Files</B
6036 ></P
6037 ></DD
6038 ><DT
6039 ><A
6040 NAME="CONFIGFILE"
6041 ></A
6042 >config file (G)</DT
6043 ><DD
6044 ><P
6045 >This allows you to override the config file
6046                 to use, instead of the default (usually <TT
6047 CLASS="FILENAME"
6048 >smb.conf</TT
6049 >).
6050                 There is a chicken and egg problem here as this option is set
6051                 in the config file!</P
6052 ><P
6053 >For this reason, if the name of the config file has changed
6054                 when the parameters are loaded then it will reload them from
6055                 the new config file.</P
6056 ><P
6057 >This option takes the usual substitutions, which can
6058                 be very useful.</P
6059 ><P
6060 >If the config file doesn't exist then it won't be loaded
6061                 (allowing you to special case the config files of just a few
6062                 clients).</P
6063 ><P
6064 >Example: <B
6065 CLASS="COMMAND"
6066 >config file = /usr/local/samba/lib/smb.conf.%m
6067                 </B
6068 ></P
6069 ></DD
6070 ><DT
6071 ><A
6072 NAME="COPY"
6073 ></A
6074 >copy (S)</DT
6075 ><DD
6076 ><P
6077 >This parameter allows you to "clone" service
6078                 entries. The specified service is simply duplicated under the
6079                 current service's name. Any parameters specified in the current
6080                 section will override those in the section being copied.</P
6081 ><P
6082 >This feature lets you set up a 'template' service and
6083                 create similar services easily. Note that the service being
6084                 copied must occur earlier in the configuration file than the
6085                 service doing the copying.</P
6086 ><P
6087 >Default: <EM
6088 >no value</EM
6089 ></P
6090 ><P
6091 >Example: <B
6092 CLASS="COMMAND"
6093 >copy = otherservice</B
6094 ></P
6095 ></DD
6096 ><DT
6097 ><A
6098 NAME="CREATEMASK"
6099 ></A
6100 >create mask (S)</DT
6101 ><DD
6102 ><P
6103 >A synonym for this parameter is
6104                 <A
6105 HREF="#CREATEMODE"
6106 ><TT
6107 CLASS="PARAMETER"
6108 ><I
6109 >create mode</I
6110 ></TT
6111 >
6112                 </A
6113 >.</P
6114 ><P
6115 >When a file is created, the necessary permissions are
6116                 calculated according to the mapping from DOS modes to UNIX
6117                 permissions, and the resulting UNIX mode is then bit-wise 'AND'ed
6118                 with this parameter. This parameter may be thought of as a bit-wise
6119                 MASK for the UNIX modes of a file. Any bit <EM
6120 >not</EM
6121 >
6122                 set here will be removed from the modes set on a file when it is
6123                 created.</P
6124 ><P
6125 >The default value of this parameter removes the
6126                 'group' and 'other' write and execute bits from the UNIX modes.</P
6127 ><P
6128 >Following this Samba will bit-wise 'OR' the UNIX mode created
6129                 from this parameter with the value of the <A
6130 HREF="#FORCECREATEMODE"
6131 ><TT
6132 CLASS="PARAMETER"
6133 ><I
6134 >force create mode</I
6135 ></TT
6136 ></A
6137 >
6138                 parameter which is set to 000 by default.</P
6139 ><P
6140 >This parameter does not affect directory modes. See the
6141                 parameter <A
6142 HREF="#DIRECTORYMODE"
6143 ><TT
6144 CLASS="PARAMETER"
6145 ><I
6146 >directory mode
6147                 </I
6148 ></TT
6149 ></A
6150 > for details.</P
6151 ><P
6152 >See also the <A
6153 HREF="#FORCECREATEMODE"
6154 ><TT
6155 CLASS="PARAMETER"
6156 ><I
6157 >force
6158                 create mode</I
6159 ></TT
6160 ></A
6161 > parameter for forcing particular mode
6162                 bits to be set on created files. See also the <A
6163 HREF="#DIRECTORYMODE"
6164 >               <TT
6165 CLASS="PARAMETER"
6166 ><I
6167 >directory mode</I
6168 ></TT
6169 ></A
6170 > parameter for masking
6171                 mode bits on created directories.  See also the <A
6172 HREF="#INHERITPERMISSIONS"
6173 >               <TT
6174 CLASS="PARAMETER"
6175 ><I
6176 >inherit permissions</I
6177 ></TT
6178 ></A
6179 > parameter.</P
6180 ><P
6181 >Note that this parameter does not apply to permissions
6182                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
6183                 a mask on access control lists also, they need to set the <A
6184 HREF="#SECURITYMASK"
6185 ><TT
6186 CLASS="PARAMETER"
6187 ><I
6188 >security mask</I
6189 ></TT
6190 ></A
6191 >.</P
6192 ><P
6193 >Default: <B
6194 CLASS="COMMAND"
6195 >create mask = 0744</B
6196 ></P
6197 ><P
6198 >Example: <B
6199 CLASS="COMMAND"
6200 >create mask = 0775</B
6201 ></P
6202 ></DD
6203 ><DT
6204 ><A
6205 NAME="CREATEMODE"
6206 ></A
6207 >create mode (S)</DT
6208 ><DD
6209 ><P
6210 >This is a synonym for <A
6211 HREF="#CREATEMASK"
6212 ><TT
6213 CLASS="PARAMETER"
6214 ><I
6215 >               create mask</I
6216 ></TT
6217 ></A
6218 >.</P
6219 ></DD
6220 ><DT
6221 ><A
6222 NAME="DEADTIME"
6223 ></A
6224 >deadtime (G)</DT
6225 ><DD
6226 ><P
6227 >The value of the parameter (a decimal integer)
6228                 represents the number of minutes of inactivity before a connection
6229                 is considered dead, and it is disconnected. The deadtime only takes
6230                 effect if the number of open files is zero.</P
6231 ><P
6232 >This is useful to stop a server's resources being
6233                 exhausted by a large number of inactive connections.</P
6234 ><P
6235 >Most clients have an auto-reconnect feature when a
6236                 connection is broken so in most cases this parameter should be
6237                 transparent to users.</P
6238 ><P
6239 >Using this parameter with a timeout of a few minutes
6240                 is recommended for most systems.</P
6241 ><P
6242 >A deadtime of zero indicates that no auto-disconnection
6243                 should be performed.</P
6244 ><P
6245 >Default: <B
6246 CLASS="COMMAND"
6247 >deadtime = 0</B
6248 ></P
6249 ><P
6250 >Example: <B
6251 CLASS="COMMAND"
6252 >deadtime = 15</B
6253 ></P
6254 ></DD
6255 ><DT
6256 ><A
6257 NAME="DEBUGHIRESTIMESTAMP"
6258 ></A
6259 >debug hires timestamp (G)</DT
6260 ><DD
6261 ><P
6262 >Sometimes the timestamps in the log messages
6263                 are needed with a resolution of higher that seconds, this
6264                 boolean parameter adds microsecond resolution to the timestamp
6265                 message header when turned on.</P
6266 ><P
6267 >Note that the parameter <A
6268 HREF="#DEBUGTIMESTAMP"
6269 ><TT
6270 CLASS="PARAMETER"
6271 ><I
6272 >               debug timestamp</I
6273 ></TT
6274 ></A
6275 > must be on for this to have an
6276                 effect.</P
6277 ><P
6278 >Default: <B
6279 CLASS="COMMAND"
6280 >debug hires timestamp = no</B
6281 ></P
6282 ></DD
6283 ><DT
6284 ><A
6285 NAME="DEBUGPID"
6286 ></A
6287 >debug pid (G)</DT
6288 ><DD
6289 ><P
6290 >When using only one log file for more then one
6291                 forked <A
6292 HREF="smbd.8.html"
6293 TARGET="_top"
6294 >smbd</A
6295 >-process there may be hard to follow which process
6296                 outputs which message. This boolean parameter is adds the process-id
6297                 to the timestamp message headers in the logfile when turned on.</P
6298 ><P
6299 >Note that the parameter <A
6300 HREF="#DEBUGTIMESTAMP"
6301 ><TT
6302 CLASS="PARAMETER"
6303 ><I
6304 >               debug timestamp</I
6305 ></TT
6306 ></A
6307 > must be on for this to have an
6308                 effect.</P
6309 ><P
6310 >Default: <B
6311 CLASS="COMMAND"
6312 >debug pid = no</B
6313 ></P
6314 ></DD
6315 ><DT
6316 ><A
6317 NAME="DEBUGTIMESTAMP"
6318 ></A
6319 >debug timestamp (G)</DT
6320 ><DD
6321 ><P
6322 >Samba 2.2 debug log messages are timestamped
6323                 by default. If you are running at a high <A
6324 HREF="#DEBUGLEVEL"
6325 >               <TT
6326 CLASS="PARAMETER"
6327 ><I
6328 >debug level</I
6329 ></TT
6330 ></A
6331 > these timestamps
6332                 can be distracting. This boolean parameter allows timestamping
6333                 to be turned off.</P
6334 ><P
6335 >Default: <B
6336 CLASS="COMMAND"
6337 >debug timestamp = yes</B
6338 ></P
6339 ></DD
6340 ><DT
6341 ><A
6342 NAME="DEBUGUID"
6343 ></A
6344 >debug uid (G)</DT
6345 ><DD
6346 ><P
6347 >Samba is sometimes run as root and sometime
6348                 run as the connected user, this boolean parameter inserts the
6349                 current euid, egid, uid and gid to the timestamp message headers
6350                 in the log file if turned on.</P
6351 ><P
6352 >Note that the parameter <A
6353 HREF="#DEBUGTIMESTAMP"
6354 ><TT
6355 CLASS="PARAMETER"
6356 ><I
6357 >               debug timestamp</I
6358 ></TT
6359 ></A
6360 > must be on for this to have an
6361                 effect.</P
6362 ><P
6363 >Default: <B
6364 CLASS="COMMAND"
6365 >debug uid = no</B
6366 ></P
6367 ></DD
6368 ><DT
6369 ><A
6370 NAME="DEBUGLEVEL"
6371 ></A
6372 >debuglevel (G)</DT
6373 ><DD
6374 ><P
6375 >Synonym for <A
6376 HREF="#LOGLEVEL"
6377 ><TT
6378 CLASS="PARAMETER"
6379 ><I
6380 >               log level</I
6381 ></TT
6382 ></A
6383 >.</P
6384 ></DD
6385 ><DT
6386 ><A
6387 NAME="DEFAULT"
6388 ></A
6389 >default (G)</DT
6390 ><DD
6391 ><P
6392 >A synonym for <A
6393 HREF="#DEFAULTSERVICE"
6394 ><TT
6395 CLASS="PARAMETER"
6396 ><I
6397 >               default service</I
6398 ></TT
6399 ></A
6400 >.</P
6401 ></DD
6402 ><DT
6403 ><A
6404 NAME="DEFAULTCASE"
6405 ></A
6406 >default case (S)</DT
6407 ><DD
6408 ><P
6409 >See the section on <A
6410 HREF="#AEN202"
6411 >               NAME MANGLING</A
6412 >. Also note the <A
6413 HREF="#SHORTPRESERVECASE"
6414 >               <TT
6415 CLASS="PARAMETER"
6416 ><I
6417 >short preserve case</I
6418 ></TT
6419 ></A
6420 > parameter.</P
6421 ><P
6422 >Default: <B
6423 CLASS="COMMAND"
6424 >default case = lower</B
6425 ></P
6426 ></DD
6427 ><DT
6428 ><A
6429 NAME="DEFAULTSERVICE"
6430 ></A
6431 >default service (G)</DT
6432 ><DD
6433 ><P
6434 >This parameter specifies the name of a service
6435                 which will be connected to if the service actually requested cannot
6436                 be found. Note that the square brackets are <EM
6437 >NOT</EM
6438 >
6439                 given in the parameter value (see example below).</P
6440 ><P
6441 >There is no default value for this parameter. If this
6442                 parameter is not given, attempting to connect to a nonexistent
6443                 service results in an error.</P
6444 ><P
6445 >Typically the default service would be a <A
6446 HREF="#GUESTOK"
6447 >               <TT
6448 CLASS="PARAMETER"
6449 ><I
6450 >guest ok</I
6451 ></TT
6452 ></A
6453 >, <A
6454 HREF="#READONLY"
6455 >               <TT
6456 CLASS="PARAMETER"
6457 ><I
6458 >read-only</I
6459 ></TT
6460 ></A
6461 > service.</P
6462 ><P
6463 >Also note that the apparent service name will be changed
6464                 to equal that of the requested service, this is very useful as it
6465                 allows you to use macros like <TT
6466 CLASS="PARAMETER"
6467 ><I
6468 >%S</I
6469 ></TT
6470 > to make
6471                 a wildcard service.</P
6472 ><P
6473 >Note also that any "_" characters in the name of the service
6474                 used in the default service will get mapped to a "/". This allows for
6475                 interesting things.</P
6476 ><P
6477 >Example:</P
6478 ><P
6479 ><TABLE
6480 BORDER="0"
6481 BGCOLOR="#E0E0E0"
6482 WIDTH="90%"
6483 ><TR
6484 ><TD
6485 ><PRE
6486 CLASS="PROGRAMLISTING"
6487 >[global]
6488         default service = pub
6489
6490 [pub]
6491         path = /%S
6492                 </PRE
6493 ></TD
6494 ></TR
6495 ></TABLE
6496 ></P
6497 ></DD
6498 ><DT
6499 ><A
6500 NAME="DELETEPRINTERCOMMAND"
6501 ></A
6502 >delete printer command (G)</DT
6503 ><DD
6504 ><P
6505 >With the introduction of MS-RPC based printer
6506                 support for Windows NT/2000 clients in Samba 2.2, it is now
6507                 possible to delete printer at run time by issuing the
6508                 DeletePrinter() RPC call.</P
6509 ><P
6510 >For a Samba host this means that the printer must be
6511                 physically deleted from underlying printing system.  The <TT
6512 CLASS="PARAMETER"
6513 ><I
6514 >               deleteprinter command</I
6515 ></TT
6516 > defines a script to be run which
6517                 will perform the necessary operations for removing the printer
6518                 from the print system and from <TT
6519 CLASS="FILENAME"
6520 >smb.conf</TT
6521 >.
6522                 </P
6523 ><P
6524 >The <TT
6525 CLASS="PARAMETER"
6526 ><I
6527 >delete printer command</I
6528 ></TT
6529 > is
6530                 automatically called with only one parameter: <TT
6531 CLASS="PARAMETER"
6532 ><I
6533 >               "printer name"</I
6534 ></TT
6535 >.</P
6536 ><P
6537 >Once the <TT
6538 CLASS="PARAMETER"
6539 ><I
6540 >delete printer command</I
6541 ></TT
6542 > has
6543                 been executed, <B
6544 CLASS="COMMAND"
6545 >smbd</B
6546 > will reparse the <TT
6547 CLASS="FILENAME"
6548 >               smb.conf</TT
6549 > to associated printer no longer exists.
6550                 If the sharename is still valid, then <B
6551 CLASS="COMMAND"
6552 >smbd
6553                 </B
6554 > will return an ACCESS_DENIED error to the client.</P
6555 ><P
6556 >See also <A
6557 HREF="#ADDPRINTERCOMMAND"
6558 ><TT
6559 CLASS="PARAMETER"
6560 ><I
6561 >               add printer command</I
6562 ></TT
6563 ></A
6564 >, <A
6565 HREF="#PRINTING"
6566 ><TT
6567 CLASS="PARAMETER"
6568 ><I
6569 >printing</I
6570 ></TT
6571 ></A
6572 >,
6573                 <A
6574 HREF="#SHOWADDPRINTERWIZARD"
6575 ><TT
6576 CLASS="PARAMETER"
6577 ><I
6578 >show add
6579                 printer wizard</I
6580 ></TT
6581 ></A
6582 ></P
6583 ><P
6584 >Default: <EM
6585 >none</EM
6586 ></P
6587 ><P
6588 >Example: <B
6589 CLASS="COMMAND"
6590 >deleteprinter command = /usr/bin/removeprinter
6591                 </B
6592 ></P
6593 ></DD
6594 ><DT
6595 ><A
6596 NAME="DELETEREADONLY"
6597 ></A
6598 >delete readonly (S)</DT
6599 ><DD
6600 ><P
6601 >This parameter allows readonly files to be deleted.
6602                 This is not normal DOS semantics, but is allowed by UNIX.</P
6603 ><P
6604 >This option may be useful for running applications such
6605                 as rcs, where UNIX file ownership prevents changing file
6606                 permissions, and DOS semantics prevent deletion of a read only file.</P
6607 ><P
6608 >Default: <B
6609 CLASS="COMMAND"
6610 >delete readonly = no</B
6611 ></P
6612 ></DD
6613 ><DT
6614 ><A
6615 NAME="DELETESHARECOMMAND"
6616 ></A
6617 >delete share command (G)</DT
6618 ><DD
6619 ><P
6620 >Samba 2.2.0 introduced the ability to dynamically
6621                 add and delete shares via the Windows NT 4.0 Server Manager.  The
6622                 <TT
6623 CLASS="PARAMETER"
6624 ><I
6625 >delete share command</I
6626 ></TT
6627 > is used to define an
6628                 external program or script which will remove an existing service
6629                 definition from <TT
6630 CLASS="FILENAME"
6631 >smb.conf</TT
6632 >.  In order to successfully
6633                 execute the <TT
6634 CLASS="PARAMETER"
6635 ><I
6636 >delete share command</I
6637 ></TT
6638 >, <B
6639 CLASS="COMMAND"
6640 >smbd</B
6641 >
6642                 requires that the administrator be connected using a root account (i.e.
6643                 uid == 0).
6644                 </P
6645 ><P
6646 >               When executed, <B
6647 CLASS="COMMAND"
6648 >smbd</B
6649 > will automatically invoke the
6650                 <TT
6651 CLASS="PARAMETER"
6652 ><I
6653 >delete share command</I
6654 ></TT
6655 > with two parameters.
6656                 </P
6657 ><P
6658 ></P
6659 ><UL
6660 ><LI
6661 ><P
6662 ><TT
6663 CLASS="PARAMETER"
6664 ><I
6665 >configFile</I
6666 ></TT
6667 > - the location
6668                         of the global <TT
6669 CLASS="FILENAME"
6670 >smb.conf</TT
6671 > file.
6672                         </P
6673 ></LI
6674 ><LI
6675 ><P
6676 ><TT
6677 CLASS="PARAMETER"
6678 ><I
6679 >shareName</I
6680 ></TT
6681 > - the name of
6682                         the existing service.
6683                         </P
6684 ></LI
6685 ></UL
6686 ><P
6687 >               This parameter is only used to remove file shares.  To delete printer shares,
6688                 see the <A
6689 HREF="#DELETEPRINTERCOMMAND"
6690 ><TT
6691 CLASS="PARAMETER"
6692 ><I
6693 >delete printer
6694                 command</I
6695 ></TT
6696 ></A
6697 >.
6698                 </P
6699 ><P
6700 >               See also <A
6701 HREF="#ADDSHARECOMMAND"
6702 ><TT
6703 CLASS="PARAMETER"
6704 ><I
6705 >delete share
6706                 command</I
6707 ></TT
6708 ></A
6709 >, <A
6710 HREF="#CHANGESHARECOMMAND"
6711 ><TT
6712 CLASS="PARAMETER"
6713 ><I
6714 >change
6715                 share</I
6716 ></TT
6717 ></A
6718 >.
6719                 </P
6720 ><P
6721 >Default: <EM
6722 >none</EM
6723 ></P
6724 ><P
6725 >Example: <B
6726 CLASS="COMMAND"
6727 >delete share command = /usr/local/bin/delshare</B
6728 ></P
6729 ></DD
6730 ><DT
6731 ><A
6732 NAME="DELETEUSERSCRIPT"
6733 ></A
6734 >delete user script (G)</DT
6735 ><DD
6736 ><P
6737 >This is the full pathname to a script that will
6738                 be run <EM
6739 >AS ROOT</EM
6740 > by <A
6741 HREF="smbd.8.html"
6742 TARGET="_top"
6743 >               <B
6744 CLASS="COMMAND"
6745 >smbd(8)</B
6746 ></A
6747 > under special circumstances
6748                 described below.</P
6749 ><P
6750 >Normally, a Samba server requires that UNIX users are
6751                 created for all users accessing files on this server. For sites
6752                 that use Windows NT account databases as their primary user database
6753                 creating these users and keeping the user list in sync with the
6754                 Windows NT PDC is an onerous task. This option allows <B
6755 CLASS="COMMAND"
6756 >               smbd</B
6757 > to delete the required UNIX users <EM
6758 >ON
6759                 DEMAND</EM
6760 > when a user accesses the Samba server and the
6761                 Windows NT user no longer exists.</P
6762 ><P
6763 >In order to use this option, <B
6764 CLASS="COMMAND"
6765 >smbd</B
6766 > must be
6767                 set to <TT
6768 CLASS="PARAMETER"
6769 ><I
6770 >security = domain</I
6771 ></TT
6772 > and <TT
6773 CLASS="PARAMETER"
6774 ><I
6775 >delete
6776                 user script</I
6777 ></TT
6778 > must be set to a full pathname for a script
6779                 that will delete a UNIX user given one argument of <TT
6780 CLASS="PARAMETER"
6781 ><I
6782 >%u
6783                 </I
6784 ></TT
6785 >, which expands into the UNIX user name to delete.
6786                 <EM
6787 >NOTE</EM
6788 > that this is different to the <A
6789 HREF="#ADDUSERSCRIPT"
6790 ><TT
6791 CLASS="PARAMETER"
6792 ><I
6793 >add user script</I
6794 ></TT
6795 ></A
6796 >
6797                 which will work with the <TT
6798 CLASS="PARAMETER"
6799 ><I
6800 >security = server</I
6801 ></TT
6802 > option
6803                 as well as <TT
6804 CLASS="PARAMETER"
6805 ><I
6806 >security = domain</I
6807 ></TT
6808 >. The reason for this
6809                 is only when Samba is a domain member does it get the information
6810                 on an attempted user logon that a user no longer exists. In the
6811                 <TT
6812 CLASS="PARAMETER"
6813 ><I
6814 >security = server</I
6815 ></TT
6816 > mode a missing user
6817                 is treated the same as an invalid password logon attempt. Deleting
6818                 the user in this circumstance would not be a good idea.</P
6819 ><P
6820 >When the Windows user attempts to access the Samba server,
6821                 at <EM
6822 >login</EM
6823 > (session setup in the SMB protocol)
6824                 time, <B
6825 CLASS="COMMAND"
6826 >smbd</B
6827 > contacts the <A
6828 HREF="#PASSWORDSERVER"
6829 >               <TT
6830 CLASS="PARAMETER"
6831 ><I
6832 >password server</I
6833 ></TT
6834 ></A
6835 > and attempts to authenticate
6836                 the given user with the given password. If the authentication fails
6837                 with the specific Domain error code meaning that the user no longer
6838                 exists then <B
6839 CLASS="COMMAND"
6840 >smbd</B
6841 > attempts to find a UNIX user in
6842                 the UNIX password database that matches the Windows user account. If
6843                 this lookup succeeds, and <TT
6844 CLASS="PARAMETER"
6845 ><I
6846 >delete user script</I
6847 ></TT
6848 > is
6849                 set then <B
6850 CLASS="COMMAND"
6851 >smbd</B
6852 > will all the specified script
6853                 <EM
6854 >AS ROOT</EM
6855 >, expanding any <TT
6856 CLASS="PARAMETER"
6857 ><I
6858 >%u</I
6859 ></TT
6860 >
6861                 argument to be the user name to delete.</P
6862 ><P
6863 >This script should delete the given UNIX username. In this way,
6864                 UNIX users are dynamically deleted to match existing Windows NT
6865                 accounts.</P
6866 ><P
6867 >See also <A
6868 HREF="#SECURITYEQUALSDOMAIN"
6869 >security = domain</A
6870 >,
6871                 <A
6872 HREF="#PASSWORDSERVER"
6873 ><TT
6874 CLASS="PARAMETER"
6875 ><I
6876 >password server</I
6877 ></TT
6878 >
6879                 </A
6880 >, <A
6881 HREF="#ADDUSERSCRIPT"
6882 ><TT
6883 CLASS="PARAMETER"
6884 ><I
6885 >add user script</I
6886 ></TT
6887 >
6888                 </A
6889 >.</P
6890 ><P
6891 >Default: <B
6892 CLASS="COMMAND"
6893 >delete user script = &#60;empty string&#62;
6894                 </B
6895 ></P
6896 ><P
6897 >Example: <B
6898 CLASS="COMMAND"
6899 >delete user script = /usr/local/samba/bin/del_user
6900                 %u</B
6901 ></P
6902 ></DD
6903 ><DT
6904 ><A
6905 NAME="DELETEVETOFILES"
6906 ></A
6907 >delete veto files (S)</DT
6908 ><DD
6909 ><P
6910 >This option is used when Samba is attempting to
6911                 delete a directory that contains one or more vetoed directories
6912                 (see the <A
6913 HREF="#VETOFILES"
6914 ><TT
6915 CLASS="PARAMETER"
6916 ><I
6917 >veto files</I
6918 ></TT
6919 ></A
6920 >
6921                 option).  If this option is set to <TT
6922 CLASS="CONSTANT"
6923 >false</TT
6924 > (the default) then if a vetoed
6925                 directory contains any non-vetoed files or directories then the
6926                 directory delete will fail. This is usually what you want.</P
6927 ><P
6928 >If this option is set to <TT
6929 CLASS="CONSTANT"
6930 >true</TT
6931 >, then Samba
6932                 will attempt to recursively delete any files and directories within
6933                 the vetoed directory. This can be useful for integration with file
6934                 serving systems such as NetAtalk which create meta-files within
6935                 directories you might normally veto DOS/Windows users from seeing
6936                 (e.g. <TT
6937 CLASS="FILENAME"
6938 >.AppleDouble</TT
6939 >)</P
6940 ><P
6941 >Setting <B
6942 CLASS="COMMAND"
6943 >delete veto files = yes</B
6944 > allows these
6945                 directories to be  transparently deleted when the parent directory
6946                 is deleted (so long as the user has permissions to do so).</P
6947 ><P
6948 >See also the <A
6949 HREF="#VETOFILES"
6950 ><TT
6951 CLASS="PARAMETER"
6952 ><I
6953 >veto
6954                 files</I
6955 ></TT
6956 ></A
6957 > parameter.</P
6958 ><P
6959 >Default: <B
6960 CLASS="COMMAND"
6961 >delete veto files = no</B
6962 ></P
6963 ></DD
6964 ><DT
6965 ><A
6966 NAME="DENYHOSTS"
6967 ></A
6968 >deny hosts (S)</DT
6969 ><DD
6970 ><P
6971 >Synonym for <A
6972 HREF="#HOSTSDENY"
6973 ><TT
6974 CLASS="PARAMETER"
6975 ><I
6976 >hosts
6977                 deny</I
6978 ></TT
6979 ></A
6980 >.</P
6981 ></DD
6982 ><DT
6983 ><A
6984 NAME="DFREECOMMAND"
6985 ></A
6986 >dfree command (G)</DT
6987 ><DD
6988 ><P
6989 >The <TT
6990 CLASS="PARAMETER"
6991 ><I
6992 >dfree command</I
6993 ></TT
6994 > setting should
6995                 only be used on systems where a problem occurs with the internal
6996                 disk space calculations. This has been known to happen with Ultrix,
6997                 but may occur with other operating systems. The symptom that was
6998                 seen was an error of "Abort Retry Ignore" at the end of each
6999                 directory listing.</P
7000 ><P
7001 >This setting allows the replacement of the internal routines to
7002                 calculate the total disk space and amount available with an external
7003                 routine. The example below gives a possible script that might fulfill
7004                 this function.</P
7005 ><P
7006 >The external program will be passed a single parameter indicating
7007                 a directory in the filesystem being queried. This will typically consist
7008                 of the string <TT
7009 CLASS="FILENAME"
7010 >./</TT
7011 >. The script should return two
7012                 integers in ASCII. The first should be the total disk space in blocks,
7013                 and the second should be the number of available blocks. An optional
7014                 third return value can give the block size in bytes. The default
7015                 blocksize is 1024 bytes.</P
7016 ><P
7017 >Note: Your script should <EM
7018 >NOT</EM
7019 > be setuid or
7020                 setgid and should be owned by (and writeable only by) root!</P
7021 ><P
7022 >Default: <EM
7023 >By default internal routines for
7024                 determining the disk capacity and remaining space will be used.
7025                 </EM
7026 ></P
7027 ><P
7028 >Example: <B
7029 CLASS="COMMAND"
7030 >dfree command = /usr/local/samba/bin/dfree
7031                 </B
7032 ></P
7033 ><P
7034 >Where the script dfree (which must be made executable) could be:</P
7035 ><P
7036 ><TABLE
7037 BORDER="0"
7038 BGCOLOR="#E0E0E0"
7039 WIDTH="90%"
7040 ><TR
7041 ><TD
7042 ><PRE
7043 CLASS="PROGRAMLISTING"
7044 >
7045                 #!/bin/sh
7046                 df $1 | tail -1 | awk '{print $2" "$4}'
7047                 </PRE
7048 ></TD
7049 ></TR
7050 ></TABLE
7051 ></P
7052 ><P
7053 >or perhaps (on Sys V based systems):</P
7054 ><P
7055 ><TABLE
7056 BORDER="0"
7057 BGCOLOR="#E0E0E0"
7058 WIDTH="90%"
7059 ><TR
7060 ><TD
7061 ><PRE
7062 CLASS="PROGRAMLISTING"
7063 >
7064                 #!/bin/sh
7065                 /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
7066                 </PRE
7067 ></TD
7068 ></TR
7069 ></TABLE
7070 ></P
7071 ><P
7072 >Note that you may have to replace the command names
7073                 with full path names on some systems.</P
7074 ></DD
7075 ><DT
7076 ><A
7077 NAME="DIRECTORY"
7078 ></A
7079 >directory (S)</DT
7080 ><DD
7081 ><P
7082 >Synonym for <A
7083 HREF="#PATH"
7084 ><TT
7085 CLASS="PARAMETER"
7086 ><I
7087 >path
7088                 </I
7089 ></TT
7090 ></A
7091 >.</P
7092 ></DD
7093 ><DT
7094 ><A
7095 NAME="DIRECTORYMASK"
7096 ></A
7097 >directory mask (S)</DT
7098 ><DD
7099 ><P
7100 >This parameter is the octal modes which are
7101                 used when converting DOS modes to UNIX modes when creating UNIX
7102                 directories.</P
7103 ><P
7104 >When a directory is created, the necessary permissions are
7105                 calculated according to the mapping from DOS modes to UNIX permissions,
7106                 and the resulting UNIX mode is then bit-wise 'AND'ed with this
7107                 parameter. This parameter may be thought of as a bit-wise MASK for
7108                 the UNIX modes of a directory. Any bit <EM
7109 >not</EM
7110 > set
7111                 here will be removed from the modes set on a directory when it is
7112                 created.</P
7113 ><P
7114 >The default value of this parameter removes the 'group'
7115                 and 'other' write bits from the UNIX mode, allowing only the
7116                 user who owns the directory to modify it.</P
7117 ><P
7118 >Following this Samba will bit-wise 'OR' the UNIX mode
7119                 created from this parameter with the value of the <A
7120 HREF="#FORCEDIRECTORYMODE"
7121 ><TT
7122 CLASS="PARAMETER"
7123 ><I
7124 >force directory mode
7125                 </I
7126 ></TT
7127 ></A
7128 > parameter. This parameter is set to 000 by
7129                 default (i.e. no extra mode bits are added).</P
7130 ><P
7131 >Note that this parameter does not apply to permissions
7132                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
7133                 a mask on access control lists also, they need to set the <A
7134 HREF="#DIRECTORYSECURITYMASK"
7135 ><TT
7136 CLASS="PARAMETER"
7137 ><I
7138 >directory security mask</I
7139 ></TT
7140 ></A
7141 >.</P
7142 ><P
7143 >See the <A
7144 HREF="#FORCEDIRECTORYMODE"
7145 ><TT
7146 CLASS="PARAMETER"
7147 ><I
7148 >force
7149                 directory mode</I
7150 ></TT
7151 ></A
7152 > parameter to cause particular mode
7153                 bits to always be set on created directories.</P
7154 ><P
7155 >See also the <A
7156 HREF="#CREATEMODE"
7157 ><TT
7158 CLASS="PARAMETER"
7159 ><I
7160 >create mode
7161                 </I
7162 ></TT
7163 ></A
7164 > parameter for masking mode bits on created files,
7165                 and the <A
7166 HREF="#DIRECTORYSECURITYMASK"
7167 ><TT
7168 CLASS="PARAMETER"
7169 ><I
7170 >directory
7171                 security mask</I
7172 ></TT
7173 ></A
7174 > parameter.</P
7175 ><P
7176 >Also refer to the <A
7177 HREF="#INHERITPERMISSIONS"
7178 ><TT
7179 CLASS="PARAMETER"
7180 ><I
7181 >               inherit permissions</I
7182 ></TT
7183 ></A
7184 > parameter.</P
7185 ><P
7186 >Default: <B
7187 CLASS="COMMAND"
7188 >directory mask = 0755</B
7189 ></P
7190 ><P
7191 >Example: <B
7192 CLASS="COMMAND"
7193 >directory mask = 0775</B
7194 ></P
7195 ></DD
7196 ><DT
7197 ><A
7198 NAME="DIRECTORYMODE"
7199 ></A
7200 >directory mode (S)</DT
7201 ><DD
7202 ><P
7203 >Synonym for <A
7204 HREF="#DIRECTORYMASK"
7205 ><TT
7206 CLASS="PARAMETER"
7207 ><I
7208 >               directory mask</I
7209 ></TT
7210 ></A
7211 ></P
7212 ></DD
7213 ><DT
7214 ><A
7215 NAME="DIRECTORYSECURITYMASK"
7216 ></A
7217 >directory security mask (S)</DT
7218 ><DD
7219 ><P
7220 >This parameter controls what UNIX permission bits
7221                 can be modified when a Windows NT client is manipulating the UNIX
7222                 permission on a directory using the native NT security dialog
7223                 box.</P
7224 ><P
7225 >This parameter is applied as a mask (AND'ed with) to
7226                 the changed permission bits, thus preventing any bits not in
7227                 this mask from being modified. Essentially, zero bits in this
7228                 mask may be treated as a set of bits the user is not allowed
7229                 to change.</P
7230 ><P
7231 >If not set explicitly this parameter is set to 0777
7232                 meaning a user is allowed to modify all the user/group/world
7233                 permissions on a directory.</P
7234 ><P
7235 ><EM
7236 >Note</EM
7237 > that users who can access the
7238                 Samba server through other means can easily bypass this restriction,
7239                 so it is primarily useful for standalone "appliance" systems.
7240                 Administrators of most normal systems will probably want to leave
7241                 it as the default of <TT
7242 CLASS="CONSTANT"
7243 >0777</TT
7244 >.</P
7245 ><P
7246 >See also the <A
7247 HREF="#FORCEDIRECTORYSECURITYMODE"
7248 ><TT
7249 CLASS="PARAMETER"
7250 ><I
7251 >               force directory security mode</I
7252 ></TT
7253 ></A
7254 >, <A
7255 HREF="#SECURITYMASK"
7256 ><TT
7257 CLASS="PARAMETER"
7258 ><I
7259 >security mask</I
7260 ></TT
7261 ></A
7262 >,
7263                 <A
7264 HREF="#FORCESECURITYMODE"
7265 ><TT
7266 CLASS="PARAMETER"
7267 ><I
7268 >force security mode
7269                 </I
7270 ></TT
7271 ></A
7272 > parameters.</P
7273 ><P
7274 >Default: <B
7275 CLASS="COMMAND"
7276 >directory security mask = 0777</B
7277 ></P
7278 ><P
7279 >Example: <B
7280 CLASS="COMMAND"
7281 >directory security mask = 0700</B
7282 ></P
7283 ></DD
7284 ><DT
7285 ><A
7286 NAME="DISABLESPOOLSS"
7287 ></A
7288 >disable spoolss (G)</DT
7289 ><DD
7290 ><P
7291 >Enabling this parameter will disables Samba's support
7292                 for the SPOOLSS set of MS-RPC's and will yield identical behavior
7293                 as Samba 2.0.x.  Windows NT/2000 clients will downgrade to using
7294                 Lanman style printing commands. Windows 9x/ME will be uneffected by
7295                 the parameter. However, this will also disable the ability to upload
7296                 printer drivers to a Samba server via the Windows NT Add Printer
7297                 Wizard or by using the NT printer properties dialog window.  It will
7298                 also disable the capability of Windows NT/2000 clients to download
7299                 print drivers from the Samba host upon demand.
7300                 <EM
7301 >Be very careful about enabling this parameter.</EM
7302 >
7303                 </P
7304 ><P
7305 >See also <A
7306 HREF="#USECLIENTDRIVER"
7307 >use client driver</A
7308 >
7309                 </P
7310 ><P
7311 >Default : <B
7312 CLASS="COMMAND"
7313 >disable spoolss = no</B
7314 ></P
7315 ></DD
7316 ><DT
7317 ><A
7318 NAME="DNSPROXY"
7319 ></A
7320 >dns proxy (G)</DT
7321 ><DD
7322 ><P
7323 >Specifies that <A
7324 HREF="nmbd.8.html"
7325 TARGET="_top"
7326 >nmbd(8)</A
7327 >
7328                 when acting as a WINS server and finding that a NetBIOS name has not
7329                 been registered, should treat the NetBIOS name word-for-word as a DNS
7330                 name and do a lookup with the DNS server for that name on behalf of
7331                 the name-querying client.</P
7332 ><P
7333 >Note that the maximum length for a NetBIOS name is 15
7334                 characters, so the DNS name (or DNS alias) can likewise only be
7335                 15 characters, maximum.</P
7336 ><P
7337 ><B
7338 CLASS="COMMAND"
7339 >nmbd</B
7340 > spawns a second copy of itself to do the
7341                 DNS name lookup requests, as doing a name lookup is a blocking
7342                 action.</P
7343 ><P
7344 >See also the parameter <A
7345 HREF="#WINSSUPPORT"
7346 ><TT
7347 CLASS="PARAMETER"
7348 ><I
7349 >               wins support</I
7350 ></TT
7351 ></A
7352 >.</P
7353 ><P
7354 >Default: <B
7355 CLASS="COMMAND"
7356 >dns proxy = yes</B
7357 ></P
7358 ></DD
7359 ><DT
7360 ><A
7361 NAME="DOMAINADMINGROUP"
7362 ></A
7363 >domain admin group (G)</DT
7364 ><DD
7365 ><P
7366 >This parameter is intended as a temporary solution
7367                 to enable users to be a member of the "Domain Admins" group when
7368                 a Samba host is acting as a PDC.  A complete solution will be provided
7369                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7370                 Please note that this parameter has a somewhat confusing name.  It
7371                 accepts a list of usernames and of group names in standard
7372                 <TT
7373 CLASS="FILENAME"
7374 >smb.conf</TT
7375 >       notation.
7376                 </P
7377 ><P
7378 >See also <A
7379 HREF="#DOMAINGUESTGROUP"
7380 ><TT
7381 CLASS="PARAMETER"
7382 ><I
7383 >domain
7384                 guest group</I
7385 ></TT
7386 ></A
7387 >, <A
7388 HREF="#DOMAINLOGONS"
7389 ><TT
7390 CLASS="PARAMETER"
7391 ><I
7392 >domain
7393                 logons</I
7394 ></TT
7395 ></A
7396 >
7397                 </P
7398 ><P
7399 >Default: <EM
7400 >no domain administrators</EM
7401 ></P
7402 ><P
7403 >Example: <B
7404 CLASS="COMMAND"
7405 >domain admin group = root @wheel</B
7406 ></P
7407 ></DD
7408 ><DT
7409 ><A
7410 NAME="DOMAINGUESTGROUP"
7411 ></A
7412 >domain guest group (G)</DT
7413 ><DD
7414 ><P
7415 >This parameter is intended as a temporary solution
7416                 to enable users to be a member of the "Domain Guests" group when
7417                 a Samba host is acting as a PDC.  A complete solution will be provided
7418                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7419                 Please note that this parameter has a somewhat confusing name.  It
7420                 accepts a list of usernames and of group names in standard
7421                 <TT
7422 CLASS="FILENAME"
7423 >smb.conf</TT
7424 >       notation.
7425                 </P
7426 ><P
7427 >See also <A
7428 HREF="#DOMAINADMINGROUP"
7429 ><TT
7430 CLASS="PARAMETER"
7431 ><I
7432 >domain
7433                 admin group</I
7434 ></TT
7435 ></A
7436 >, <A
7437 HREF="#DOMAINLOGONS"
7438 ><TT
7439 CLASS="PARAMETER"
7440 ><I
7441 >domain
7442                 logons</I
7443 ></TT
7444 ></A
7445 >
7446                 </P
7447 ><P
7448 >Default: <EM
7449 >no domain guests</EM
7450 ></P
7451 ><P
7452 >Example: <B
7453 CLASS="COMMAND"
7454 >domain guest group = nobody @guest</B
7455 ></P
7456 ></DD
7457 ><DT
7458 ><A
7459 NAME="DOMAINLOGONS"
7460 ></A
7461 >domain logons (G)</DT
7462 ><DD
7463 ><P
7464 >If set to <TT
7465 CLASS="CONSTANT"
7466 >true</TT
7467 >, the Samba server will serve
7468                 Windows 95/98 Domain logons for the <A
7469 HREF="#WORKGROUP"
7470 >               <TT
7471 CLASS="PARAMETER"
7472 ><I
7473 >workgroup</I
7474 ></TT
7475 ></A
7476 > it is in. Samba 2.2 also
7477                 has limited capability to act as a domain controller for Windows
7478                 NT 4 Domains.  For more details on setting up this feature see
7479                 the file DOMAINS.txt in the Samba documentation directory <TT
7480 CLASS="FILENAME"
7481 >docs/
7482                 </TT
7483 > shipped with the source code.</P
7484 ><P
7485 >Default: <B
7486 CLASS="COMMAND"
7487 >domain logons = no</B
7488 ></P
7489 ></DD
7490 ><DT
7491 ><A
7492 NAME="DOMAINMASTER"
7493 ></A
7494 >domain master (G)</DT
7495 ><DD
7496 ><P
7497 >Tell <A
7498 HREF="nmbd.8.html"
7499 TARGET="_top"
7500 ><B
7501 CLASS="COMMAND"
7502 >               nmbd(8)</B
7503 ></A
7504 > to enable WAN-wide browse list
7505                 collation. Setting this option causes <B
7506 CLASS="COMMAND"
7507 >nmbd</B
7508 > to
7509                 claim a special domain specific NetBIOS name that identifies
7510                 it as a domain master browser for its given <A
7511 HREF="#WORKGROUP"
7512 >               <TT
7513 CLASS="PARAMETER"
7514 ><I
7515 >workgroup</I
7516 ></TT
7517 ></A
7518 >. Local master browsers
7519                 in the same <TT
7520 CLASS="PARAMETER"
7521 ><I
7522 >workgroup</I
7523 ></TT
7524 > on broadcast-isolated
7525                 subnets will give this <B
7526 CLASS="COMMAND"
7527 >nmbd</B
7528 > their local browse lists,
7529                 and then ask <A
7530 HREF="smbd.8.html"
7531 TARGET="_top"
7532 ><B
7533 CLASS="COMMAND"
7534 >smbd(8)</B
7535 ></A
7536 >
7537                 for a complete copy of the browse list for the whole wide area
7538                 network.  Browser clients will then contact their local master browser,
7539                 and will receive the domain-wide browse list, instead of just the list
7540                 for their broadcast-isolated subnet.</P
7541 ><P
7542 >Note that Windows NT Primary Domain Controllers expect to be
7543                 able to claim this <TT
7544 CLASS="PARAMETER"
7545 ><I
7546 >workgroup</I
7547 ></TT
7548 > specific special
7549                 NetBIOS name that identifies them as domain master browsers for
7550                 that <TT
7551 CLASS="PARAMETER"
7552 ><I
7553 >workgroup</I
7554 ></TT
7555 > by default (i.e. there is no
7556                 way to prevent a Windows NT PDC from attempting to do this). This
7557                 means that if this parameter is set and <B
7558 CLASS="COMMAND"
7559 >nmbd</B
7560 > claims
7561                 the special name for a <TT
7562 CLASS="PARAMETER"
7563 ><I
7564 >workgroup</I
7565 ></TT
7566 > before a Windows
7567                 NT PDC is able to do so then cross subnet browsing will behave
7568                 strangely and may fail.</P
7569 ><P
7570 >If <A
7571 HREF="#DOMAINLOGONS"
7572 ><B
7573 CLASS="COMMAND"
7574 >domain logons = yes</B
7575 >
7576                 </A
7577 >, then the default behavior is to enable the <TT
7578 CLASS="PARAMETER"
7579 ><I
7580 >domain
7581                 master</I
7582 ></TT
7583 > parameter.  If <TT
7584 CLASS="PARAMETER"
7585 ><I
7586 >domain logons</I
7587 ></TT
7588 > is
7589                 not enabled (the default setting), then neither will <TT
7590 CLASS="PARAMETER"
7591 ><I
7592 >domain
7593                 master</I
7594 ></TT
7595 > be enabled by default.</P
7596 ><P
7597 >Default: <B
7598 CLASS="COMMAND"
7599 >domain master = auto</B
7600 ></P
7601 ></DD
7602 ><DT
7603 ><A
7604 NAME="DONTDESCEND"
7605 ></A
7606 >dont descend (S)</DT
7607 ><DD
7608 ><P
7609 >There are certain directories on some systems
7610                 (e.g., the <TT
7611 CLASS="FILENAME"
7612 >/proc</TT
7613 > tree under Linux) that are either not
7614                 of interest to clients or are infinitely deep (recursive). This
7615                 parameter allows you to specify a comma-delimited list of directories
7616                 that the server should always show as empty.</P
7617 ><P
7618 >Note that Samba can be very fussy about the exact format
7619                 of the "dont descend" entries. For example you may need <TT
7620 CLASS="FILENAME"
7621 >               ./proc</TT
7622 > instead of just <TT
7623 CLASS="FILENAME"
7624 >/proc</TT
7625 >.
7626                 Experimentation is the best policy :-)  </P
7627 ><P
7628 >Default: <EM
7629 >none (i.e., all directories are OK
7630                 to descend)</EM
7631 ></P
7632 ><P
7633 >Example: <B
7634 CLASS="COMMAND"
7635 >dont descend = /proc,/dev</B
7636 ></P
7637 ></DD
7638 ><DT
7639 ><A
7640 NAME="DOSFILEMODE"
7641 ></A
7642 >dos filemode (S)</DT
7643 ><DD
7644 ><P
7645 > The default behavior in Samba is to provide
7646                 UNIX-like behavior where only the owner of a file/directory is
7647                 able to change the permissions on it.  However, this behavior
7648                 is often confusing to  DOS/Windows users.  Enabling this parameter
7649                 allows a user who has write access to the file (by whatever
7650                 means) to modify the permissions on it.  Note that a user
7651                 belonging to the group owning the file will not be allowed to
7652                 change permissions if the group is only granted read access.
7653                 Ownership of the file/directory is not changed, only the permissions
7654                 are modified.</P
7655 ><P
7656 >Default: <B
7657 CLASS="COMMAND"
7658 >dos filemode = no</B
7659 ></P
7660 ></DD
7661 ><DT
7662 ><A
7663 NAME="DOSFILETIMERESOLUTION"
7664 ></A
7665 >dos filetime resolution (S)</DT
7666 ><DD
7667 ><P
7668 >Under the DOS and Windows FAT filesystem, the finest
7669                 granularity on time resolution is two seconds. Setting this parameter
7670                 for a share causes Samba to round the reported time down to the
7671                 nearest two second boundary when a query call that requires one second
7672                 resolution is made to <A
7673 HREF="smbd.8.html"
7674 TARGET="_top"
7675 ><B
7676 CLASS="COMMAND"
7677 >smbd(8)</B
7678 >
7679                 </A
7680 >.</P
7681 ><P
7682 >This option is mainly used as a compatibility option for Visual
7683                 C++ when used against Samba shares. If oplocks are enabled on a
7684                 share, Visual C++ uses two different time reading calls to check if a
7685                 file has changed since it was last read. One of these calls uses a
7686                 one-second granularity, the other uses a two second granularity. As
7687                 the two second call rounds any odd second down, then if the file has a
7688                 timestamp of an odd number of seconds then the two timestamps will not
7689                 match and Visual C++ will keep reporting the file has changed. Setting
7690                 this option causes the two timestamps to match, and Visual C++ is
7691                 happy.</P
7692 ><P
7693 >Default: <B
7694 CLASS="COMMAND"
7695 >dos filetime resolution = no</B
7696 ></P
7697 ></DD
7698 ><DT
7699 ><A
7700 NAME="DOSFILETIMES"
7701 ></A
7702 >dos filetimes (S)</DT
7703 ><DD
7704 ><P
7705 >Under DOS and Windows, if a user can write to a
7706                 file they can change the timestamp on it. Under POSIX semantics,
7707                 only the owner of the file or root may change the timestamp. By
7708                 default, Samba runs with POSIX semantics and refuses to change the
7709                 timestamp on a file if the user <B
7710 CLASS="COMMAND"
7711 >smbd</B
7712 > is acting
7713                 on behalf of is not the file owner. Setting this option to <TT
7714 CLASS="CONSTANT"
7715 >               true</TT
7716 > allows DOS semantics and <A
7717 HREF="smbd.8.html"
7718 TARGET="_top"
7719 >smbd</A
7720 > will change the file
7721                 timestamp as DOS requires.</P
7722 ><P
7723 >Default: <B
7724 CLASS="COMMAND"
7725 >dos filetimes = no</B
7726 ></P
7727 ></DD
7728 ><DT
7729 ><A
7730 NAME="ENCRYPTPASSWORDS"
7731 ></A
7732 >encrypt passwords (G)</DT
7733 ><DD
7734 ><P
7735 >This boolean controls whether encrypted passwords
7736                 will be negotiated with the client. Note that Windows NT 4.0 SP3 and
7737                 above and also Windows 98 will by default expect encrypted passwords
7738                 unless a registry entry is changed. To use encrypted passwords in
7739                 Samba see the file ENCRYPTION.txt in the Samba documentation
7740                 directory <TT
7741 CLASS="FILENAME"
7742 >docs/</TT
7743 > shipped with the source code.</P
7744 ><P
7745 >In order for encrypted passwords to work correctly
7746                 <A
7747 HREF="smbd.8.html"
7748 TARGET="_top"
7749 ><B
7750 CLASS="COMMAND"
7751 >smbd(8)</B
7752 ></A
7753 > must either
7754                 have access to a local <A
7755 HREF="smbpasswd.5.html"
7756 TARGET="_top"
7757 ><TT
7758 CLASS="FILENAME"
7759 >smbpasswd(5)
7760                 </TT
7761 ></A
7762 > file (see the <A
7763 HREF="smbpasswd.8.html"
7764 TARGET="_top"
7765 ><B
7766 CLASS="COMMAND"
7767 >               smbpasswd(8)</B
7768 ></A
7769 > program for information on how to set up
7770                 and maintain this file), or set the <A
7771 HREF="#SECURITY"
7772 >security = [server|domain]</A
7773 > parameter which
7774                 causes <B
7775 CLASS="COMMAND"
7776 >smbd</B
7777 > to authenticate against another
7778                 server.</P
7779 ><P
7780 >Default: <B
7781 CLASS="COMMAND"
7782 >encrypt passwords = no</B
7783 ></P
7784 ></DD
7785 ><DT
7786 ><A
7787 NAME="ENHANCEDBROWSING"
7788 ></A
7789 >enhanced browsing (G)</DT
7790 ><DD
7791 ><P
7792 >This option enables a couple of enhancements to
7793                 cross-subnet browse propagation that have been added in Samba
7794                 but which are not standard in Microsoft implementations.
7795                 </P
7796 ><P
7797 >The first enhancement to browse propagation consists of a regular
7798                 wildcard query to a Samba WINS server for all Domain Master Browsers,
7799                 followed by a browse synchronization with each of the returned
7800                 DMBs. The second enhancement consists of a regular randomised browse
7801                 synchronization with all currently known DMBs.</P
7802 ><P
7803 >You may wish to disable this option if you have a problem with empty
7804                 workgroups not disappearing from browse lists. Due to the restrictions
7805                 of the browse protocols these enhancements can cause a empty workgroup
7806                 to stay around forever which can be annoying.</P
7807 ><P
7808 >In general you should leave this option enabled as it makes
7809                 cross-subnet browse propagation much more reliable.</P
7810 ><P
7811 >Default: <B
7812 CLASS="COMMAND"
7813 >enhanced browsing = yes</B
7814 ></P
7815 ></DD
7816 ><DT
7817 ><A
7818 NAME="ENUMPORTSCOMMAND"
7819 ></A
7820 >enumports command (G)</DT
7821 ><DD
7822 ><P
7823 >The concept of a "port" is fairly foreign
7824                 to UNIX hosts.  Under Windows NT/2000 print servers, a port
7825                 is associated with a port monitor and generally takes the form of
7826                 a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
7827                 (i.e. LPD Port Monitor, etc...).  By default, Samba has only one
7828                 port defined--<TT
7829 CLASS="CONSTANT"
7830 >"Samba Printer Port"</TT
7831 >.  Under
7832                 Windows NT/2000, all printers must have a valid port name.
7833                 If you wish to have a list of ports displayed (<B
7834 CLASS="COMMAND"
7835 >smbd
7836                 </B
7837 > does not use a port name for anything) other than
7838                 the default <TT
7839 CLASS="CONSTANT"
7840 >"Samba Printer Port"</TT
7841 >, you
7842                 can define <TT
7843 CLASS="PARAMETER"
7844 ><I
7845 >enumports command</I
7846 ></TT
7847 > to point to
7848                 a program which should generate a list of ports, one per line,
7849                 to standard output.  This listing will then be used in response
7850                 to the level 1 and 2 EnumPorts() RPC.</P
7851 ><P
7852 >Default: <EM
7853 >no enumports command</EM
7854 ></P
7855 ><P
7856 >Example: <B
7857 CLASS="COMMAND"
7858 >enumports command = /usr/bin/listports
7859                 </B
7860 ></P
7861 ></DD
7862 ><DT
7863 ><A
7864 NAME="EXEC"
7865 ></A
7866 >exec (S)</DT
7867 ><DD
7868 ><P
7869 >This is a synonym for <A
7870 HREF="#PREEXEC"
7871 >               <TT
7872 CLASS="PARAMETER"
7873 ><I
7874 >preexec</I
7875 ></TT
7876 ></A
7877 >.</P
7878 ></DD
7879 ><DT
7880 ><A
7881 NAME="FAKEDIRECTORYCREATETIMES"
7882 ></A
7883 >fake directory create times (S)</DT
7884 ><DD
7885 ><P
7886 >NTFS and Windows VFAT file systems keep a create
7887                 time for all files and directories. This is not the same as the
7888                 ctime - status change time - that Unix keeps, so Samba by default
7889                 reports the earliest of the various times Unix does keep. Setting
7890                 this parameter for a share causes Samba to always report midnight
7891                 1-1-1980 as the create time for directories.</P
7892 ><P
7893 >This option is mainly used as a compatibility option for
7894                 Visual C++ when used against Samba shares. Visual C++ generated
7895                 makefiles have the object directory as a dependency for each object
7896                 file, and a make rule to create the directory. Also, when NMAKE
7897                 compares timestamps it uses the creation time when examining a
7898                 directory. Thus the object directory will be created if it does not
7899                 exist, but once it does exist it will always have an earlier
7900                 timestamp than the object files it contains.</P
7901 ><P
7902 >However, Unix time semantics mean that the create time
7903                 reported by Samba will be updated whenever a file is created or
7904                 or deleted in the directory.  NMAKE finds all object files in
7905                 the object directory.  The timestamp of the last one built is then
7906                 compared to the timestamp of the object directory.  If the
7907                 directory's timestamp if newer, then all object files
7908                 will be rebuilt.  Enabling this option
7909                 ensures directories always predate their contents and an NMAKE build
7910                 will proceed as expected.</P
7911 ><P
7912 >Default: <B
7913 CLASS="COMMAND"
7914 >fake directory create times = no</B
7915 ></P
7916 ></DD
7917 ><DT
7918 ><A
7919 NAME="FAKEOPLOCKS"
7920 ></A
7921 >fake oplocks (S)</DT
7922 ><DD
7923 ><P
7924 >Oplocks are the way that SMB clients get permission
7925                 from a server to locally cache file operations. If a server grants
7926                 an oplock (opportunistic lock) then the client is free to assume
7927                 that it is the only one accessing the file and it will aggressively
7928                 cache file data. With some oplock types the client may even cache
7929                 file open/close operations. This can give enormous performance benefits.
7930                 </P
7931 ><P
7932 >When you set <B
7933 CLASS="COMMAND"
7934 >fake oplocks = yes</B
7935 >, <A
7936 HREF="smbd.8.html"
7937 TARGET="_top"
7938 ><B
7939 CLASS="COMMAND"
7940 >smbd(8)</B
7941 ></A
7942 > will
7943                 always grant oplock requests no matter how many clients are using
7944                 the file.</P
7945 ><P
7946 >It is generally much better to use the real <A
7947 HREF="#OPLOCKS"
7948 ><TT
7949 CLASS="PARAMETER"
7950 ><I
7951 >oplocks</I
7952 ></TT
7953 ></A
7954 > support rather
7955                 than this parameter.</P
7956 ><P
7957 >If you enable this option on all read-only shares or
7958                 shares that you know will only be accessed from one client at a
7959                 time such as physically read-only media like CDROMs, you will see
7960                 a big performance improvement on many operations. If you enable
7961                 this option on shares where multiple clients may be accessing the
7962                 files read-write at the same time you can get data corruption. Use
7963                 this option carefully!</P
7964 ><P
7965 >Default: <B
7966 CLASS="COMMAND"
7967 >fake oplocks = no</B
7968 ></P
7969 ></DD
7970 ><DT
7971 ><A
7972 NAME="FOLLOWSYMLINKS"
7973 ></A
7974 >follow symlinks (S)</DT
7975 ><DD
7976 ><P
7977 >This parameter allows the Samba administrator
7978                 to stop <A
7979 HREF="smbd.8.html"
7980 TARGET="_top"
7981 ><B
7982 CLASS="COMMAND"
7983 >smbd(8)</B
7984 ></A
7985 >
7986                 from following symbolic links in a particular share. Setting this
7987                 parameter to <TT
7988 CLASS="CONSTANT"
7989 >no</TT
7990 > prevents any file or directory
7991                 that is a symbolic link from being followed (the user will get an
7992                 error).  This option is very useful to stop users from adding a
7993                 symbolic link to <TT
7994 CLASS="FILENAME"
7995 >/etc/passwd</TT
7996 > in their home
7997                 directory for instance.  However it will slow filename lookups
7998                 down slightly.</P
7999 ><P
8000 >This option is enabled (i.e. <B
8001 CLASS="COMMAND"
8002 >smbd</B
8003 > will
8004                 follow symbolic links) by default.</P
8005 ><P
8006 >Default: <B
8007 CLASS="COMMAND"
8008 >follow symlinks = yes</B
8009 ></P
8010 ></DD
8011 ><DT
8012 ><A
8013 NAME="FORCECREATEMODE"
8014 ></A
8015 >force create mode (S)</DT
8016 ><DD
8017 ><P
8018 >This parameter specifies a set of UNIX mode bit
8019                 permissions that will <EM
8020 >always</EM
8021 > be set on a
8022                 file created by Samba. This is done by bitwise 'OR'ing these bits onto
8023                 the mode bits of a file that is being created or having its
8024                 permissions changed. The default for this parameter is (in octal)
8025                 000. The modes in this parameter are bitwise 'OR'ed onto the file
8026                 mode after the mask set in the <TT
8027 CLASS="PARAMETER"
8028 ><I
8029 >create mask</I
8030 ></TT
8031 >
8032                 parameter is applied.</P
8033 ><P
8034 >Note that by default this parameter does not apply to permissions
8035                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
8036                 this mask on access control lists also, they need to set the <A
8037 HREF="#RESTRICTACLWITHMASK"
8038 ><TT
8039 CLASS="PARAMETER"
8040 ><I
8041 >restrict acl with
8042                 mask</I
8043 ></TT
8044 ></A
8045 > to <TT
8046 CLASS="CONSTANT"
8047 >true</TT
8048 >.</P
8049 ><P
8050 >See also the parameter <A
8051 HREF="#CREATEMASK"
8052 ><TT
8053 CLASS="PARAMETER"
8054 ><I
8055 >create
8056                 mask</I
8057 ></TT
8058 ></A
8059 > for details on masking mode bits on files.</P
8060 ><P
8061 >See also the <A
8062 HREF="#INHERITPERMISSIONS"
8063 ><TT
8064 CLASS="PARAMETER"
8065 ><I
8066 >inherit
8067                 permissions</I
8068 ></TT
8069 ></A
8070 > parameter.</P
8071 ><P
8072 >Default: <B
8073 CLASS="COMMAND"
8074 >force create mode = 000</B
8075 ></P
8076 ><P
8077 >Example: <B
8078 CLASS="COMMAND"
8079 >force create mode = 0755</B
8080 ></P
8081 ><P
8082 >would force all created files to have read and execute
8083                 permissions set for 'group' and 'other' as well as the
8084                 read/write/execute bits set for the 'user'.</P
8085 ></DD
8086 ><DT
8087 ><A
8088 NAME="FORCEDIRECTORYMODE"
8089 ></A
8090 >force directory mode (S)</DT
8091 ><DD
8092 ><P
8093 >This parameter specifies a set of UNIX mode bit
8094                 permissions that will <EM
8095 >always</EM
8096 > be set on a directory
8097                 created by Samba. This is done by bitwise 'OR'ing these bits onto the
8098                 mode bits of a directory that is being created. The default for this
8099                 parameter is (in octal) 0000 which will not add any extra permission
8100                 bits to a created directory. This operation is done after the mode
8101                 mask in the parameter <TT
8102 CLASS="PARAMETER"
8103 ><I
8104 >directory mask</I
8105 ></TT
8106 > is
8107                 applied.</P
8108 ><P
8109 >Note that by default this parameter does not apply to permissions
8110                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
8111                 this mask on access control lists also, they need to set the <A
8112 HREF="#RESTRICTACLWITHMASK"
8113 ><TT
8114 CLASS="PARAMETER"
8115 ><I
8116 >restrict acl with
8117                 mask</I
8118 ></TT
8119 ></A
8120 > to <TT
8121 CLASS="CONSTANT"
8122 >true</TT
8123 >.</P
8124 ><P
8125 >See also the parameter <A
8126 HREF="#DIRECTORYMASK"
8127 ><TT
8128 CLASS="PARAMETER"
8129 ><I
8130 >               directory mask</I
8131 ></TT
8132 ></A
8133 > for details on masking mode bits
8134                 on created directories.</P
8135 ><P
8136 >See also the <A
8137 HREF="#INHERITPERMISSIONS"
8138 ><TT
8139 CLASS="PARAMETER"
8140 ><I
8141 >               inherit permissions</I
8142 ></TT
8143 ></A
8144 > parameter.</P
8145 ><P
8146 >Default: <B
8147 CLASS="COMMAND"
8148 >force directory mode = 000</B
8149 ></P
8150 ><P
8151 >Example: <B
8152 CLASS="COMMAND"
8153 >force directory mode = 0755</B
8154 ></P
8155 ><P
8156 >would force all created directories to have read and execute
8157                 permissions set for 'group' and 'other' as well as the
8158                 read/write/execute bits set for the 'user'.</P
8159 ></DD
8160 ><DT
8161 ><A
8162 NAME="FORCEDIRECTORYSECURITYMODE"
8163 ></A
8164 >force directory
8165                 security mode (S)</DT
8166 ><DD
8167 ><P
8168 >This parameter controls what UNIX permission bits
8169                 can be modified when a Windows NT client is manipulating the UNIX
8170                 permission on a directory using the native NT security dialog box.</P
8171 ><P
8172 >This parameter is applied as a mask (OR'ed with) to the
8173                 changed permission bits, thus forcing any bits in this mask that
8174                 the user may have modified to be on. Essentially, one bits in this
8175                 mask may be treated as a set of bits that, when modifying security
8176                 on a directory, the user has always set to be 'on'.</P
8177 ><P
8178 >If not set explicitly this parameter is 000, which
8179                 allows a user to modify all the user/group/world permissions on a
8180                 directory without restrictions.</P
8181 ><P
8182 ><EM
8183 >Note</EM
8184 > that users who can access the
8185                 Samba server through other means can easily bypass this restriction,
8186                 so it is primarily useful for standalone "appliance" systems.
8187                 Administrators of most normal systems will probably want to leave
8188                 it set as 0000.</P
8189 ><P
8190 >See also the <A
8191 HREF="#DIRECTORYSECURITYMASK"
8192 ><TT
8193 CLASS="PARAMETER"
8194 ><I
8195 >               directory security mask</I
8196 ></TT
8197 ></A
8198 >, <A
8199 HREF="#SECURITYMASK"
8200 >               <TT
8201 CLASS="PARAMETER"
8202 ><I
8203 >security mask</I
8204 ></TT
8205 ></A
8206 >,
8207                 <A
8208 HREF="#FORCESECURITYMODE"
8209 ><TT
8210 CLASS="PARAMETER"
8211 ><I
8212 >force security mode
8213                 </I
8214 ></TT
8215 ></A
8216 > parameters.</P
8217 ><P
8218 >Default: <B
8219 CLASS="COMMAND"
8220 >force directory security mode = 0</B
8221 ></P
8222 ><P
8223 >Example: <B
8224 CLASS="COMMAND"
8225 >force directory security mode = 700</B
8226 ></P
8227 ></DD
8228 ><DT
8229 ><A
8230 NAME="FORCEGROUP"
8231 ></A
8232 >force group (S)</DT
8233 ><DD
8234 ><P
8235 >This specifies a UNIX group name that will be
8236                 assigned as the default primary group for all users connecting
8237                 to this service. This is useful for sharing files by ensuring
8238                 that all access to files on service will use the named group for
8239                 their permissions checking. Thus, by assigning permissions for this
8240                 group to the files and directories within this service the Samba
8241                 administrator can restrict or allow sharing of these files.</P
8242 ><P
8243 >In Samba 2.0.5 and above this parameter has extended
8244                 functionality in the following way. If the group name listed here
8245                 has a '+' character prepended to it then the current user accessing
8246                 the share only has the primary group default assigned to this group
8247                 if they are already assigned as a member of that group. This allows
8248                 an administrator to decide that only users who are already in a
8249                 particular group will create files with group ownership set to that
8250                 group. This gives a finer granularity of ownership assignment. For
8251                 example, the setting <TT
8252 CLASS="FILENAME"
8253 >force group = +sys</TT
8254 > means
8255                 that only users who are already in group sys will have their default
8256                 primary group assigned to sys when accessing this Samba share. All
8257                 other users will retain their ordinary primary group.</P
8258 ><P
8259 >If the <A
8260 HREF="#FORCEUSER"
8261 ><TT
8262 CLASS="PARAMETER"
8263 ><I
8264 >force user
8265                 </I
8266 ></TT
8267 ></A
8268 > parameter is also set the group specified in
8269                 <TT
8270 CLASS="PARAMETER"
8271 ><I
8272 >force group</I
8273 ></TT
8274 > will override the primary group
8275                 set in <TT
8276 CLASS="PARAMETER"
8277 ><I
8278 >force user</I
8279 ></TT
8280 >.</P
8281 ><P
8282 >See also <A
8283 HREF="#FORCEUSER"
8284 ><TT
8285 CLASS="PARAMETER"
8286 ><I
8287 >force
8288                 user</I
8289 ></TT
8290 ></A
8291 >.</P
8292 ><P
8293 >Default: <EM
8294 >no forced group</EM
8295 ></P
8296 ><P
8297 >Example: <B
8298 CLASS="COMMAND"
8299 >force group = agroup</B
8300 ></P
8301 ></DD
8302 ><DT
8303 ><A
8304 NAME="FORCESECURITYMODE"
8305 ></A
8306 >force security mode (S)</DT
8307 ><DD
8308 ><P
8309 >This parameter controls what UNIX permission
8310                 bits can be modified when a Windows NT client is manipulating
8311                 the UNIX permission on a file using the native NT security dialog
8312                 box.</P
8313 ><P
8314 >This parameter is applied as a mask (OR'ed with) to the
8315                 changed permission bits, thus forcing any bits in this mask that
8316                 the user may have modified to be on. Essentially, one bits in this
8317                 mask may be treated as a set of bits that, when modifying security
8318                 on a file, the user has always set to be 'on'.</P
8319 ><P
8320 >If not set explicitly this parameter is set to 0,
8321                 and allows a user to modify all the user/group/world permissions on a file,
8322                 with no restrictions.</P
8323 ><P
8324 ><EM
8325 >Note</EM
8326 > that users who can access
8327                 the Samba server through other means can easily bypass this restriction,
8328                 so it is primarily useful for standalone "appliance" systems.
8329                 Administrators of most normal systems will probably want to leave
8330                 this set to 0000.</P
8331 ><P
8332 >See also the <A
8333 HREF="#FORCEDIRECTORYSECURITYMODE"
8334 ><TT
8335 CLASS="PARAMETER"
8336 ><I
8337 >               force directory security mode</I
8338 ></TT
8339 ></A
8340 >,
8341                 <A
8342 HREF="#DIRECTORYSECURITYMASK"
8343 ><TT
8344 CLASS="PARAMETER"
8345 ><I
8346 >directory security
8347                 mask</I
8348 ></TT
8349 ></A
8350 >, <A
8351 HREF="#SECURITYMASK"
8352 ><TT
8353 CLASS="PARAMETER"
8354 ><I
8355 >               security mask</I
8356 ></TT
8357 ></A
8358 > parameters.</P
8359 ><P
8360 >Default: <B
8361 CLASS="COMMAND"
8362 >force security mode = 0</B
8363 ></P
8364 ><P
8365 >Example: <B
8366 CLASS="COMMAND"
8367 >force security mode = 700</B
8368 ></P
8369 ></DD
8370 ><DT
8371 ><A
8372 NAME="FORCEUSER"
8373 ></A
8374 >force user (S)</DT
8375 ><DD
8376 ><P
8377 >This specifies a UNIX user name that will be
8378                 assigned as the default user for all users connecting to this service.
8379                 This is useful for sharing files. You should also use it carefully
8380                 as using it incorrectly can cause security problems.</P
8381 ><P
8382 >This user name only gets used once a connection is established.
8383                 Thus clients still need to connect as a valid user and supply a
8384                 valid password. Once connected, all file operations will be performed
8385                 as the "forced user", no matter what username the client connected
8386                 as.  This can be very useful.</P
8387 ><P
8388 >In Samba 2.0.5 and above this parameter also causes the
8389                 primary group of the forced user to be used as the primary group
8390                 for all file activity. Prior to 2.0.5 the primary group was left
8391                 as the primary group of the connecting user (this was a bug).</P
8392 ><P
8393 >See also <A
8394 HREF="#FORCEGROUP"
8395 ><TT
8396 CLASS="PARAMETER"
8397 ><I
8398 >force group
8399                 </I
8400 ></TT
8401 ></A
8402 ></P
8403 ><P
8404 >Default: <EM
8405 >no forced user</EM
8406 ></P
8407 ><P
8408 >Example: <B
8409 CLASS="COMMAND"
8410 >force user = auser</B
8411 ></P
8412 ></DD
8413 ><DT
8414 ><A
8415 NAME="FSTYPE"
8416 ></A
8417 >fstype (S)</DT
8418 ><DD
8419 ><P
8420 >This parameter allows the administrator to
8421                 configure the string that specifies the type of filesystem a share
8422                 is using that is reported by <A
8423 HREF="smbd.8.html"
8424 TARGET="_top"
8425 ><B
8426 CLASS="COMMAND"
8427 >smbd(8)
8428                 </B
8429 ></A
8430 > when a client queries the filesystem type
8431                 for a share. The default type is <TT
8432 CLASS="CONSTANT"
8433 >NTFS</TT
8434 > for
8435                 compatibility with Windows NT but this can be changed to other
8436                 strings such as <TT
8437 CLASS="CONSTANT"
8438 >Samba</TT
8439 > or <TT
8440 CLASS="CONSTANT"
8441 >FAT
8442                 </TT
8443 > if required.</P
8444 ><P
8445 >Default: <B
8446 CLASS="COMMAND"
8447 >fstype = NTFS</B
8448 ></P
8449 ><P
8450 >Example: <B
8451 CLASS="COMMAND"
8452 >fstype = Samba</B
8453 ></P
8454 ></DD
8455 ><DT
8456 ><A
8457 NAME="GETWDCACHE"
8458 ></A
8459 >getwd cache (G)</DT
8460 ><DD
8461 ><P
8462 >This is a tuning option. When this is enabled a
8463                 caching algorithm will be used to reduce the time taken for getwd()
8464                 calls. This can have a significant impact on performance, especially
8465                 when the <A
8466 HREF="#WIDELINKS"
8467 ><TT
8468 CLASS="PARAMETER"
8469 ><I
8470 >wide links</I
8471 ></TT
8472 >
8473                 </A
8474 >parameter is set to <TT
8475 CLASS="CONSTANT"
8476 >false</TT
8477 >.</P
8478 ><P
8479 >Default: <B
8480 CLASS="COMMAND"
8481 >getwd cache = yes</B
8482 ></P
8483 ></DD
8484 ><DT
8485 ><A
8486 NAME="GROUP"
8487 ></A
8488 >group (S)</DT
8489 ><DD
8490 ><P
8491 >Synonym for <A
8492 HREF="#FORCEGROUP"
8493 ><TT
8494 CLASS="PARAMETER"
8495 ><I
8496 >force
8497                 group</I
8498 ></TT
8499 ></A
8500 >.</P
8501 ></DD
8502 ><DT
8503 ><A
8504 NAME="GUESTACCOUNT"
8505 ></A
8506 >guest account (S)</DT
8507 ><DD
8508 ><P
8509 >This is a username which will be used for access
8510                 to services which are specified as <A
8511 HREF="#GUESTOK"
8512 ><TT
8513 CLASS="PARAMETER"
8514 ><I
8515 >               guest ok</I
8516 ></TT
8517 ></A
8518 > (see below). Whatever privileges this
8519                 user has will be available to any client connecting to the guest service.
8520                 Typically this user will exist in the password file, but will not
8521                 have a valid login. The user account "ftp" is often a good choice
8522                 for this parameter. If a username is specified in a given service,
8523                 the specified username overrides this one.</P
8524 ><P
8525 >One some systems the default guest account "nobody" may not
8526                 be able to print. Use another account in this case. You should test
8527                 this by trying to log in as your guest user (perhaps by using the
8528                 <B
8529 CLASS="COMMAND"
8530 >su -</B
8531 > command) and trying to print using the
8532                 system print command such as <B
8533 CLASS="COMMAND"
8534 >lpr(1)</B
8535 > or <B
8536 CLASS="COMMAND"
8537 >               lp(1)</B
8538 >.</P
8539 ><P
8540 >Default: <EM
8541 >specified at compile time, usually
8542                 "nobody"</EM
8543 ></P
8544 ><P
8545 >Example: <B
8546 CLASS="COMMAND"
8547 >guest account = ftp</B
8548 ></P
8549 ></DD
8550 ><DT
8551 ><A
8552 NAME="GUESTOK"
8553 ></A
8554 >guest ok (S)</DT
8555 ><DD
8556 ><P
8557 >If this parameter is <TT
8558 CLASS="CONSTANT"
8559 >yes</TT
8560 > for
8561                 a service, then no password is required to connect to the service.
8562                 Privileges will be those of the <A
8563 HREF="#GUESTACCOUNT"
8564 ><TT
8565 CLASS="PARAMETER"
8566 ><I
8567 >               guest account</I
8568 ></TT
8569 ></A
8570 >.</P
8571 ><P
8572 >See the section below on <A
8573 HREF="#SECURITY"
8574 ><TT
8575 CLASS="PARAMETER"
8576 ><I
8577 >               security</I
8578 ></TT
8579 ></A
8580 > for more information about this option.
8581                 </P
8582 ><P
8583 >Default: <B
8584 CLASS="COMMAND"
8585 >guest ok = no</B
8586 ></P
8587 ></DD
8588 ><DT
8589 ><A
8590 NAME="GUESTONLY"
8591 ></A
8592 >guest only (S)</DT
8593 ><DD
8594 ><P
8595 >If this parameter is <TT
8596 CLASS="CONSTANT"
8597 >yes</TT
8598 > for
8599                 a service, then only guest connections to the service are permitted.
8600                 This parameter will have no effect if <A
8601 HREF="#GUESTOK"
8602 >               <TT
8603 CLASS="PARAMETER"
8604 ><I
8605 >guest ok</I
8606 ></TT
8607 ></A
8608 > is not set for the service.</P
8609 ><P
8610 >See the section below on <A
8611 HREF="#SECURITY"
8612 ><TT
8613 CLASS="PARAMETER"
8614 ><I
8615 >               security</I
8616 ></TT
8617 ></A
8618 > for more information about this option.
8619                 </P
8620 ><P
8621 >Default: <B
8622 CLASS="COMMAND"
8623 >guest only = no</B
8624 ></P
8625 ></DD
8626 ><DT
8627 ><A
8628 NAME="HIDEDOTFILES"
8629 ></A
8630 >hide dot files (S)</DT
8631 ><DD
8632 ><P
8633 >This is a boolean parameter that controls whether
8634                 files starting with a dot appear as hidden files.</P
8635 ><P
8636 >Default: <B
8637 CLASS="COMMAND"
8638 >hide dot files = yes</B
8639 ></P
8640 ></DD
8641 ><DT
8642 ><A
8643 NAME="HIDEFILES"
8644 ></A
8645 >hide files(S)</DT
8646 ><DD
8647 ><P
8648 >This is a list of files or directories that are not
8649                 visible but are accessible.  The DOS 'hidden' attribute is applied
8650                 to any files or directories that match.</P
8651 ><P
8652 >Each entry in the list must be separated by a '/',
8653                 which allows spaces to be included in the entry.  '*'
8654                 and '?' can be used to specify multiple files or directories
8655                 as in DOS wildcards.</P
8656 ><P
8657 >Each entry must be a Unix path, not a DOS path and must
8658                 not include the Unix directory separator '/'.</P
8659 ><P
8660 >Note that the case sensitivity option is applicable
8661                 in hiding files.</P
8662 ><P
8663 >Setting this parameter will affect the performance of Samba,
8664                 as it will be forced to check all files and directories for a match
8665                 as they are scanned.</P
8666 ><P
8667 >See also <A
8668 HREF="#HIDEDOTFILES"
8669 ><TT
8670 CLASS="PARAMETER"
8671 ><I
8672 >hide
8673                 dot files</I
8674 ></TT
8675 ></A
8676 >, <A
8677 HREF="#VETOFILES"
8678 ><TT
8679 CLASS="PARAMETER"
8680 ><I
8681 >               veto files</I
8682 ></TT
8683 ></A
8684 > and <A
8685 HREF="#CASESENSITIVE"
8686 >               <TT
8687 CLASS="PARAMETER"
8688 ><I
8689 >case sensitive</I
8690 ></TT
8691 ></A
8692 >.</P
8693 ><P
8694 >Default: <EM
8695 >no file are hidden</EM
8696 ></P
8697 ><P
8698 >Example: <B
8699 CLASS="COMMAND"
8700 >hide files =
8701                 /.*/DesktopFolderDB/TrashFor%m/resource.frk/</B
8702 ></P
8703 ><P
8704 >The above example is based on files that the Macintosh
8705                 SMB client (DAVE) available from <A
8706 HREF="http://www.thursby.com"
8707 TARGET="_top"
8708 >
8709                 Thursby</A
8710 > creates for internal use, and also still hides
8711                 all files beginning with a dot.</P
8712 ></DD
8713 ><DT
8714 ><A
8715 NAME="HIDELOCALUSERS"
8716 ></A
8717 >hide local users(G)</DT
8718 ><DD
8719 ><P
8720 >This parameter toggles the hiding of local UNIX
8721                 users (root, wheel, floppy, etc) from remote clients.</P
8722 ><P
8723 >Default: <B
8724 CLASS="COMMAND"
8725 >hide local users = no</B
8726 ></P
8727 ></DD
8728 ><DT
8729 ><A
8730 NAME="HIDEUNREADABLE"
8731 ></A
8732 >hide unreadable(G)</DT
8733 ><DD
8734 ><P
8735 >This parameter prevents clients from seeing the
8736                 existance of files that cannot be read. Defaults to off.</P
8737 ><P
8738 >Default: <B
8739 CLASS="COMMAND"
8740 >hide unreadable = no</B
8741 ></P
8742 ></DD
8743 ><DT
8744 ><A
8745 NAME="HOMEDIRMAP"
8746 ></A
8747 >homedir map (G)</DT
8748 ><DD
8749 ><P
8750 >If<A
8751 HREF="#NISHOMEDIR"
8752 ><TT
8753 CLASS="PARAMETER"
8754 ><I
8755 >nis homedir
8756                 </I
8757 ></TT
8758 ></A
8759 > is <TT
8760 CLASS="CONSTANT"
8761 >true</TT
8762 >, and <A
8763 HREF="smbd.8.html"
8764 TARGET="_top"
8765 ><B
8766 CLASS="COMMAND"
8767 >smbd(8)</B
8768 ></A
8769 > is also acting
8770                 as a Win95/98 <TT
8771 CLASS="PARAMETER"
8772 ><I
8773 >logon server</I
8774 ></TT
8775 > then this parameter
8776                 specifies the NIS (or YP) map from which the server for the user's
8777                 home directory should be extracted.  At present, only the Sun
8778                 auto.home map format is understood. The form of the map is:</P
8779 ><P
8780 ><B
8781 CLASS="COMMAND"
8782 >username       server:/some/file/system</B
8783 ></P
8784 ><P
8785 >and the program will extract the servername from before
8786                 the first ':'.  There should probably be a better parsing system
8787                 that copes with different map formats and also Amd (another
8788                 automounter) maps.</P
8789 ><P
8790 ><EM
8791 >NOTE :</EM
8792 >A working NIS client is required on
8793                 the system for this option to work.</P
8794 ><P
8795 >See also <A
8796 HREF="#NISHOMEDIR"
8797 ><TT
8798 CLASS="PARAMETER"
8799 ><I
8800 >nis homedir</I
8801 ></TT
8802 >
8803                 </A
8804 >, <A
8805 HREF="#DOMAINLOGONS"
8806 ><TT
8807 CLASS="PARAMETER"
8808 ><I
8809 >domain logons</I
8810 ></TT
8811 >
8812                 </A
8813 >.</P
8814 ><P
8815 >Default: <B
8816 CLASS="COMMAND"
8817 >homedir map = &#60;empty string&#62;</B
8818 ></P
8819 ><P
8820 >Example: <B
8821 CLASS="COMMAND"
8822 >homedir map = amd.homedir</B
8823 ></P
8824 ></DD
8825 ><DT
8826 ><A
8827 NAME="HOSTMSDFS"
8828 ></A
8829 >host msdfs (G)</DT
8830 ><DD
8831 ><P
8832 >This boolean parameter is only available
8833                 if Samba has been configured and compiled with the <B
8834 CLASS="COMMAND"
8835 >               --with-msdfs</B
8836 > option. If set to <TT
8837 CLASS="CONSTANT"
8838 >yes</TT
8839 >,
8840                 Samba will act as a Dfs server, and  allow Dfs-aware clients
8841                 to browse Dfs trees hosted on the server.</P
8842 ><P
8843 >See also the <A
8844 HREF="#MSDFSROOT"
8845 ><TT
8846 CLASS="PARAMETER"
8847 ><I
8848 >               msdfs root</I
8849 ></TT
8850 ></A
8851 > share  level  parameter.  For
8852                 more  information  on  setting  up a Dfs tree on Samba,
8853                 refer to <A
8854 HREF="msdfs_setup.html"
8855 TARGET="_top"
8856 >msdfs_setup.html</A
8857 >.
8858                 </P
8859 ><P
8860 >Default: <B
8861 CLASS="COMMAND"
8862 >host msdfs = no</B
8863 ></P
8864 ></DD
8865 ><DT
8866 ><A
8867 NAME="HOSTSALLOW"
8868 ></A
8869 >hosts allow (S)</DT
8870 ><DD
8871 ><P
8872 >A synonym for this parameter is <TT
8873 CLASS="PARAMETER"
8874 ><I
8875 >allow
8876                 hosts</I
8877 ></TT
8878 >.</P
8879 ><P
8880 >This parameter is a comma, space, or tab delimited
8881                 set of hosts which are permitted to access a service.</P
8882 ><P
8883 >If specified in the [global] section then it will
8884                 apply to all services, regardless of whether the individual
8885                 service has a different setting.</P
8886 ><P
8887 >You can specify the hosts by name or IP number. For
8888                 example, you could restrict access to only the hosts on a
8889                 Class C subnet with something like <B
8890 CLASS="COMMAND"
8891 >allow hosts = 150.203.5.
8892                 </B
8893 >. The full syntax of the list is described in the man
8894                 page <TT
8895 CLASS="FILENAME"
8896 >hosts_access(5)</TT
8897 >. Note that this man
8898                 page may not be present on your system, so a brief description will
8899                 be given here also.</P
8900 ><P
8901 >Note that the localhost address 127.0.0.1 will always
8902                 be allowed access unless specifically denied by a <A
8903 HREF="#HOSTSDENY"
8904 ><TT
8905 CLASS="PARAMETER"
8906 ><I
8907 >hosts deny</I
8908 ></TT
8909 ></A
8910 > option.</P
8911 ><P
8912 >You can also specify hosts by network/netmask pairs and
8913                 by netgroup names if your system supports netgroups. The
8914                 <EM
8915 >EXCEPT</EM
8916 > keyword can also be used to limit a
8917                 wildcard list. The following examples may provide some help:</P
8918 ><P
8919 >Example 1: allow all IPs in 150.203.*.*; except one</P
8920 ><P
8921 ><B
8922 CLASS="COMMAND"
8923 >hosts allow = 150.203. EXCEPT 150.203.6.66</B
8924 ></P
8925 ><P
8926 >Example 2: allow hosts that match the given network/netmask</P
8927 ><P
8928 ><B
8929 CLASS="COMMAND"
8930 >hosts allow = 150.203.15.0/255.255.255.0</B
8931 ></P
8932 ><P
8933 >Example 3: allow a couple of hosts</P
8934 ><P
8935 ><B
8936 CLASS="COMMAND"
8937 >hosts allow = lapland, arvidsjaur</B
8938 ></P
8939 ><P
8940 >Example 4: allow only hosts in NIS netgroup "foonet", but
8941                 deny access from one particular host</P
8942 ><P
8943 ><B
8944 CLASS="COMMAND"
8945 >hosts allow = @foonet</B
8946 ></P
8947 ><P
8948 ><B
8949 CLASS="COMMAND"
8950 >hosts deny = pirate</B
8951 ></P
8952 ><P
8953 >Note that access still requires suitable user-level passwords.</P
8954 ><P
8955 >See <A
8956 HREF="testparm.1.html"
8957 TARGET="_top"
8958 ><B
8959 CLASS="COMMAND"
8960 >testparm(1)</B
8961 >
8962                 </A
8963 > for a way of testing your host access to see if it does
8964                 what you expect.</P
8965 ><P
8966 >Default: <EM
8967 >none (i.e., all hosts permitted access)
8968                 </EM
8969 ></P
8970 ><P
8971 >Example: <B
8972 CLASS="COMMAND"
8973 >allow hosts = 150.203.5. myhost.mynet.edu.au
8974                 </B
8975 ></P
8976 ></DD
8977 ><DT
8978 ><A
8979 NAME="HOSTSDENY"
8980 ></A
8981 >hosts deny (S)</DT
8982 ><DD
8983 ><P
8984 >The opposite of <TT
8985 CLASS="PARAMETER"
8986 ><I
8987 >hosts allow</I
8988 ></TT
8989 >
8990                 - hosts listed here are <EM
8991 >NOT</EM
8992 > permitted access to
8993                 services unless the specific services have their own lists to override
8994                 this one. Where the lists conflict, the <TT
8995 CLASS="PARAMETER"
8996 ><I
8997 >allow</I
8998 ></TT
8999 >
9000                 list takes precedence.</P
9001 ><P
9002 >Default: <EM
9003 >none (i.e., no hosts specifically excluded)
9004                 </EM
9005 ></P
9006 ><P
9007 >Example: <B
9008 CLASS="COMMAND"
9009 >hosts deny = 150.203.4. badhost.mynet.edu.au
9010                 </B
9011 ></P
9012 ></DD
9013 ><DT
9014 ><A
9015 NAME="HOSTSEQUIV"
9016 ></A
9017 >hosts equiv (G)</DT
9018 ><DD
9019 ><P
9020 >If this global parameter is a non-null string,
9021                 it specifies the name of a file to read for the names of hosts
9022                 and users who will be allowed access without specifying a password.
9023                 </P
9024 ><P
9025 >This is not be confused with <A
9026 HREF="#HOSTSALLOW"
9027 >               <TT
9028 CLASS="PARAMETER"
9029 ><I
9030 >hosts allow</I
9031 ></TT
9032 ></A
9033 > which is about hosts
9034                 access to services and is more useful for guest services. <TT
9035 CLASS="PARAMETER"
9036 ><I
9037 >               hosts equiv</I
9038 ></TT
9039 > may be useful for NT clients which will
9040                 not supply passwords to Samba.</P
9041 ><P
9042 ><EM
9043 >NOTE :</EM
9044 > The use of <TT
9045 CLASS="PARAMETER"
9046 ><I
9047 >hosts equiv
9048                 </I
9049 ></TT
9050 > can be a major security hole. This is because you are
9051                 trusting the PC to supply the correct username. It is very easy to
9052                 get a PC to supply a false username. I recommend that the
9053                 <TT
9054 CLASS="PARAMETER"
9055 ><I
9056 >hosts equiv</I
9057 ></TT
9058 > option be only used if you really
9059                 know what you are doing, or perhaps on a home network where you trust
9060                 your spouse and kids. And only if you <EM
9061 >really</EM
9062 > trust
9063                 them :-).</P
9064 ><P
9065 >Default: <EM
9066 >no host equivalences</EM
9067 ></P
9068 ><P
9069 >Example: <B
9070 CLASS="COMMAND"
9071 >hosts equiv = /etc/hosts.equiv</B
9072 ></P
9073 ></DD
9074 ><DT
9075 ><A
9076 NAME="INCLUDE"
9077 ></A
9078 >include (G)</DT
9079 ><DD
9080 ><P
9081 >This allows you to include one config file
9082                 inside another.  The file is included literally, as though typed
9083                 in place.</P
9084 ><P
9085 >It takes the standard substitutions, except <TT
9086 CLASS="PARAMETER"
9087 ><I
9088 >%u
9089                 </I
9090 ></TT
9091 >, <TT
9092 CLASS="PARAMETER"
9093 ><I
9094 >%P</I
9095 ></TT
9096 > and <TT
9097 CLASS="PARAMETER"
9098 ><I
9099 >%S</I
9100 ></TT
9101 >.
9102                 </P
9103 ><P
9104 >Default: <EM
9105 >no file included</EM
9106 ></P
9107 ><P
9108 >Example: <B
9109 CLASS="COMMAND"
9110 >include = /usr/local/samba/lib/admin_smb.conf
9111                 </B
9112 ></P
9113 ></DD
9114 ><DT
9115 ><A
9116 NAME="INHERITPERMISSIONS"
9117 ></A
9118 >inherit permissions (S)</DT
9119 ><DD
9120 ><P
9121 >The permissions on new files and directories
9122                 are normally governed by <A
9123 HREF="#CREATEMASK"
9124 ><TT
9125 CLASS="PARAMETER"
9126 ><I
9127 >               create mask</I
9128 ></TT
9129 ></A
9130 >, <A
9131 HREF="#DIRECTORYMASK"
9132 >               <TT
9133 CLASS="PARAMETER"
9134 ><I
9135 >directory mask</I
9136 ></TT
9137 ></A
9138 >, <A
9139 HREF="#FORCECREATEMODE"
9140 ><TT
9141 CLASS="PARAMETER"
9142 ><I
9143 >force create mode</I
9144 ></TT
9145 >
9146                 </A
9147 > and <A
9148 HREF="#FORCEDIRECTORYMODE"
9149 ><TT
9150 CLASS="PARAMETER"
9151 ><I
9152 >force
9153                 directory mode</I
9154 ></TT
9155 ></A
9156 > but the boolean inherit
9157                 permissions parameter overrides this.</P
9158 ><P
9159 >New directories inherit the mode of the parent directory,
9160                 including bits such as setgid.</P
9161 ><P
9162 >New files inherit their read/write bits from the parent
9163                 directory.  Their execute bits continue to be determined by
9164                 <A
9165 HREF="#MAPARCHIVE"
9166 ><TT
9167 CLASS="PARAMETER"
9168 ><I
9169 >map archive</I
9170 ></TT
9171 >
9172                 </A
9173 >, <A
9174 HREF="#MAPHIDDEN"
9175 ><TT
9176 CLASS="PARAMETER"
9177 ><I
9178 >map hidden</I
9179 ></TT
9180 >
9181                 </A
9182 > and <A
9183 HREF="#MAPSYSTEM"
9184 ><TT
9185 CLASS="PARAMETER"
9186 ><I
9187 >map system</I
9188 ></TT
9189 >
9190                 </A
9191 > as usual.</P
9192 ><P
9193 >Note that the setuid bit is <EM
9194 >never</EM
9195 > set via
9196                 inheritance (the code explicitly prohibits this).</P
9197 ><P
9198 >This can be particularly useful on large systems with
9199                 many users, perhaps several thousand, to allow a single [homes]
9200                 share to be used flexibly by each user.</P
9201 ><P
9202 >See also <A
9203 HREF="#CREATEMASK"
9204 ><TT
9205 CLASS="PARAMETER"
9206 ><I
9207 >create mask
9208                 </I
9209 ></TT
9210 ></A
9211 >, <A
9212 HREF="#DIRECTORYMASK"
9213 ><TT
9214 CLASS="PARAMETER"
9215 ><I
9216 >               directory mask</I
9217 ></TT
9218 ></A
9219 >, <A
9220 HREF="#FORCECREATEMODE"
9221 >               <TT
9222 CLASS="PARAMETER"
9223 ><I
9224 >force create mode</I
9225 ></TT
9226 ></A
9227 > and <A
9228 HREF="#FORCEDIRECTORYMODE"
9229 ><TT
9230 CLASS="PARAMETER"
9231 ><I
9232 >force directory mode</I
9233 ></TT
9234 >
9235                 </A
9236 >.</P
9237 ><P
9238 >Default: <B
9239 CLASS="COMMAND"
9240 >inherit permissions = no</B
9241 ></P
9242 ></DD
9243 ><DT
9244 ><A
9245 NAME="INTERFACES"
9246 ></A
9247 >interfaces (G)</DT
9248 ><DD
9249 ><P
9250 >This option allows you to override the default
9251                 network interfaces list that Samba will use for browsing, name
9252                 registration and other NBT traffic. By default Samba will query
9253                 the kernel for the list of all active interfaces and use any
9254                 interfaces except 127.0.0.1 that are broadcast capable.</P
9255 ><P
9256 >The option takes a list of interface strings. Each string
9257                 can be in any of the following forms:</P
9258 ><P
9259 ></P
9260 ><UL
9261 ><LI
9262 ><P
9263 >a network interface name (such as eth0).
9264                         This may include shell-like wildcards so eth* will match
9265                         any interface starting with the substring "eth"</P
9266 ></LI
9267 ><LI
9268 ><P
9269 >an IP address. In this case the netmask is
9270                         determined from the list of interfaces obtained from the
9271                         kernel</P
9272 ></LI
9273 ><LI
9274 ><P
9275 >an IP/mask pair. </P
9276 ></LI
9277 ><LI
9278 ><P
9279 >a broadcast/mask pair.</P
9280 ></LI
9281 ></UL
9282 ><P
9283 >The "mask" parameters can either be a bit length (such
9284                 as 24 for a C class network) or a full netmask in dotted
9285                 decimal form.</P
9286 ><P
9287 >The "IP" parameters above can either be a full dotted
9288                 decimal IP address or a hostname which will be looked up via
9289                 the OS's normal hostname resolution mechanisms.</P
9290 ><P
9291 >For example, the following line:</P
9292 ><P
9293 ><B
9294 CLASS="COMMAND"
9295 >interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
9296                 </B
9297 ></P
9298 ><P
9299 >would configure three network interfaces corresponding
9300                 to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10.
9301                 The netmasks of the latter two interfaces would be set to 255.255.255.0.</P
9302 ><P
9303 >See also <A
9304 HREF="#BINDINTERFACESONLY"
9305 ><TT
9306 CLASS="PARAMETER"
9307 ><I
9308 >bind
9309                 interfaces only</I
9310 ></TT
9311 ></A
9312 >.</P
9313 ><P
9314 >Default: <EM
9315 >all active interfaces except 127.0.0.1
9316                 that are broadcast capable</EM
9317 ></P
9318 ></DD
9319 ><DT
9320 ><A
9321 NAME="INVALIDUSERS"
9322 ></A
9323 >invalid users (S)</DT
9324 ><DD
9325 ><P
9326 >This is a list of users that should not be allowed
9327                 to login to this service. This is really a <EM
9328 >paranoid</EM
9329 >
9330                 check to absolutely ensure an improper setting does not breach
9331                 your security.</P
9332 ><P
9333 >A name starting with a '@' is interpreted as an NIS
9334                 netgroup first (if your system supports NIS), and then as a UNIX
9335                 group if the name was not found in the NIS netgroup database.</P
9336 ><P
9337 >A name starting with '+' is interpreted only
9338                 by looking in the UNIX group database. A name starting with
9339                 '&#38;' is interpreted only by looking in the NIS netgroup database
9340                 (this requires NIS to be working on your system). The characters
9341                 '+' and '&#38;' may be used at the start of the name in either order
9342                 so the value <TT
9343 CLASS="PARAMETER"
9344 ><I
9345 >+&#38;group</I
9346 ></TT
9347 > means check the
9348                 UNIX group database, followed by the NIS netgroup database, and
9349                 the value <TT
9350 CLASS="PARAMETER"
9351 ><I
9352 >&#38;+group</I
9353 ></TT
9354 > means check the NIS
9355                 netgroup database, followed by the UNIX group database (the
9356                 same as the '@' prefix).</P
9357 ><P
9358 >The current servicename is substituted for <TT
9359 CLASS="PARAMETER"
9360 ><I
9361 >%S</I
9362 ></TT
9363 >.
9364                 This is useful in the [homes] section.</P
9365 ><P
9366 >See also <A
9367 HREF="#VALIDUSERS"
9368 ><TT
9369 CLASS="PARAMETER"
9370 ><I
9371 >valid users
9372                 </I
9373 ></TT
9374 ></A
9375 >.</P
9376 ><P
9377 >Default: <EM
9378 >no invalid users</EM
9379 ></P
9380 ><P
9381 >Example: <B
9382 CLASS="COMMAND"
9383 >invalid users = root fred admin @wheel
9384                 </B
9385 ></P
9386 ></DD
9387 ><DT
9388 ><A
9389 NAME="KEEPALIVE"
9390 ></A
9391 >keepalive (G)</DT
9392 ><DD
9393 ><P
9394 >The value of the parameter (an integer) represents
9395                 the number of seconds between <TT
9396 CLASS="PARAMETER"
9397 ><I
9398 >keepalive</I
9399 ></TT
9400 >
9401                 packets. If this parameter is zero, no keepalive packets will be
9402                 sent. Keepalive packets, if sent, allow the server to tell whether
9403                 a client is still present and responding.</P
9404 ><P
9405 >Keepalives should, in general, not be needed if the socket
9406                 being used has the SO_KEEPALIVE attribute set on it (see <A
9407 HREF="#SOCKETOPTIONS"
9408 ><TT
9409 CLASS="PARAMETER"
9410 ><I
9411 >socket options</I
9412 ></TT
9413 ></A
9414 >).
9415                 Basically you should only use this option if you strike difficulties.</P
9416 ><P
9417 >Default: <B
9418 CLASS="COMMAND"
9419 >keepalive = 300</B
9420 ></P
9421 ><P
9422 >Example: <B
9423 CLASS="COMMAND"
9424 >keepalive = 600</B
9425 ></P
9426 ></DD
9427 ><DT
9428 ><A
9429 NAME="KERNELOPLOCKS"
9430 ></A
9431 >kernel oplocks (G)</DT
9432 ><DD
9433 ><P
9434 >For UNIXes that support kernel based <A
9435 HREF="#OPLOCKS"
9436 ><TT
9437 CLASS="PARAMETER"
9438 ><I
9439 >oplocks</I
9440 ></TT
9441 ></A
9442 >
9443                 (currently only IRIX and the Linux 2.4 kernel), this parameter
9444                 allows the use of them to be turned on or off.</P
9445 ><P
9446 >Kernel oplocks support allows Samba <TT
9447 CLASS="PARAMETER"
9448 ><I
9449 >oplocks
9450                 </I
9451 ></TT
9452 > to be broken whenever a local UNIX process or NFS operation
9453                 accesses a file that <A
9454 HREF="smbd.8.html"
9455 TARGET="_top"
9456 ><B
9457 CLASS="COMMAND"
9458 >smbd(8)</B
9459 >
9460                 </A
9461 > has oplocked. This allows complete data consistency between
9462                 SMB/CIFS, NFS and local file access (and is a <EM
9463 >very</EM
9464 >
9465                 cool feature :-).</P
9466 ><P
9467 >This parameter defaults to <TT
9468 CLASS="CONSTANT"
9469 >on</TT
9470 >, but is translated
9471                 to a no-op on systems that no not have the necessary kernel support.
9472                 You should never need to touch this parameter.</P
9473 ><P
9474 >See also the <A
9475 HREF="#OPLOCKS"
9476 ><TT
9477 CLASS="PARAMETER"
9478 ><I
9479 >oplocks</I
9480 ></TT
9481 >
9482                 </A
9483 > and <A
9484 HREF="#LEVEL2OPLOCKS"
9485 ><TT
9486 CLASS="PARAMETER"
9487 ><I
9488 >level2 oplocks
9489                 </I
9490 ></TT
9491 ></A
9492 > parameters.</P
9493 ><P
9494 >Default: <B
9495 CLASS="COMMAND"
9496 >kernel oplocks = yes</B
9497 ></P
9498 ></DD
9499 ><DT
9500 ><A
9501 NAME="LANMANAUTH"
9502 ></A
9503 >lanman auth (G)</DT
9504 ><DD
9505 ><P
9506 >This parameter determines whether or not <A
9507 HREF="smbd.8.html"
9508 TARGET="_top"
9509 >smbd</A
9510 > will
9511                 attempt to authenticate users using the LANMAN password hash.
9512                 If disabled, only clients which support NT password hashes (e.g. Windows
9513                 NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS
9514                 network client) will be able to connect to the Samba host.</P
9515 ><P
9516 >Default : <B
9517 CLASS="COMMAND"
9518 >lanman auth = yes</B
9519 ></P
9520 ></DD
9521 ><DT
9522 ><A
9523 NAME="LARGEREADWRITE"
9524 ></A
9525 >large readwrite (G)</DT
9526 ><DD
9527 ><P
9528 >This parameter determines whether or not <A
9529 HREF="smbd.8.html"
9530 TARGET="_top"
9531 >smbd</A
9532 >
9533                 supports the new 64k streaming read and write varient SMB requests introduced
9534                 with Windows 2000. Note that due to Windows 2000 client redirector bugs
9535                 this requires Samba to be running on a 64-bit capable operating system such
9536                 as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with
9537                 Windows 2000 clients. Defaults to off. Not as tested as some other Samba
9538                 code paths.
9539                 </P
9540 ><P
9541 >Default : <B
9542 CLASS="COMMAND"
9543 >large readwrite = no</B
9544 ></P
9545 ></DD
9546 ><DT
9547 ><A
9548 NAME="LEVEL2OPLOCKS"
9549 ></A
9550 >level2 oplocks (S)</DT
9551 ><DD
9552 ><P
9553 >This parameter controls whether Samba supports
9554                 level2 (read-only) oplocks on a share.</P
9555 ><P
9556 >Level2, or read-only oplocks allow Windows NT clients
9557                 that have an oplock on a file to downgrade from a read-write oplock
9558                 to a read-only oplock once a second client opens the file (instead
9559                 of releasing all oplocks on a second open, as in traditional,
9560                 exclusive oplocks). This allows all openers of the file that
9561                 support level2 oplocks to cache the file for read-ahead only (ie.
9562                 they may not cache writes or lock requests) and increases performance
9563                 for many accesses of files that are not commonly written (such as
9564                 application .EXE files).</P
9565 ><P
9566 >Once one of the clients which have a read-only oplock
9567                 writes to the file all clients are notified (no reply is needed
9568                 or waited for) and told to break their oplocks to "none" and
9569                 delete any read-ahead caches.</P
9570 ><P
9571 >It is recommended that this parameter be turned on
9572                 to speed access to shared executables.</P
9573 ><P
9574 >For more discussions on level2 oplocks see the CIFS spec.</P
9575 ><P
9576 >Currently, if <A
9577 HREF="#KERNELOPLOCKS"
9578 ><TT
9579 CLASS="PARAMETER"
9580 ><I
9581 >kernel
9582                 oplocks</I
9583 ></TT
9584 ></A
9585 > are supported then level2 oplocks are
9586                 not granted (even if this parameter is set to <TT
9587 CLASS="CONSTANT"
9588 >yes</TT
9589 >).
9590                 Note also, the <A
9591 HREF="#OPLOCKS"
9592 ><TT
9593 CLASS="PARAMETER"
9594 ><I
9595 >oplocks</I
9596 ></TT
9597 >
9598                 </A
9599 > parameter must be set to <TT
9600 CLASS="CONSTANT"
9601 >true</TT
9602 > on this share in order for
9603                 this parameter to have any effect.</P
9604 ><P
9605 >See also the <A
9606 HREF="#OPLOCKS"
9607 ><TT
9608 CLASS="PARAMETER"
9609 ><I
9610 >oplocks</I
9611 ></TT
9612 >
9613                 </A
9614 > and <A
9615 HREF="#OPLOCKS"
9616 ><TT
9617 CLASS="PARAMETER"
9618 ><I
9619 >kernel oplocks</I
9620 ></TT
9621 >
9622                 </A
9623 > parameters.</P
9624 ><P
9625 >Default: <B
9626 CLASS="COMMAND"
9627 >level2 oplocks = yes</B
9628 ></P
9629 ></DD
9630 ><DT
9631 ><A
9632 NAME="LMANNOUNCE"
9633 ></A
9634 >lm announce (G)</DT
9635 ><DD
9636 ><P
9637 >This parameter determines if <A
9638 HREF="nmbd.8.html"
9639 TARGET="_top"
9640 >               <B
9641 CLASS="COMMAND"
9642 >nmbd(8)</B
9643 ></A
9644 > will produce Lanman announce
9645                 broadcasts that are needed by OS/2 clients in order for them to see
9646                 the Samba server in their browse list. This parameter can have three
9647                 values, <TT
9648 CLASS="CONSTANT"
9649 >true</TT
9650 >, <TT
9651 CLASS="CONSTANT"
9652 >false</TT
9653 >, or
9654                 <TT
9655 CLASS="CONSTANT"
9656 >auto</TT
9657 >. The default is <TT
9658 CLASS="CONSTANT"
9659 >auto</TT
9660 >.
9661                 If set to <TT
9662 CLASS="CONSTANT"
9663 >false</TT
9664 > Samba will never produce these
9665                 broadcasts. If set to <TT
9666 CLASS="CONSTANT"
9667 >true</TT
9668 > Samba will produce
9669                 Lanman announce broadcasts at a frequency set by the parameter
9670                 <TT
9671 CLASS="PARAMETER"
9672 ><I
9673 >lm interval</I
9674 ></TT
9675 >. If set to <TT
9676 CLASS="CONSTANT"
9677 >auto</TT
9678 >
9679                 Samba will not send Lanman announce broadcasts by default but will
9680                 listen for them. If it hears such a broadcast on the wire it will
9681                 then start sending them at a frequency set by the parameter
9682                 <TT
9683 CLASS="PARAMETER"
9684 ><I
9685 >lm interval</I
9686 ></TT
9687 >.</P
9688 ><P
9689 >See also <A
9690 HREF="#LMINTERVAL"
9691 ><TT
9692 CLASS="PARAMETER"
9693 ><I
9694 >lm interval
9695                 </I
9696 ></TT
9697 ></A
9698 >.</P
9699 ><P
9700 >Default: <B
9701 CLASS="COMMAND"
9702 >lm announce = auto</B
9703 ></P
9704 ><P
9705 >Example: <B
9706 CLASS="COMMAND"
9707 >lm announce = yes</B
9708 ></P
9709 ></DD
9710 ><DT
9711 ><A
9712 NAME="LMINTERVAL"
9713 ></A
9714 >lm interval (G)</DT
9715 ><DD
9716 ><P
9717 >If Samba is set to produce Lanman announce
9718                 broadcasts needed by OS/2 clients (see the <A
9719 HREF="#LMANNOUNCE"
9720 >               <TT
9721 CLASS="PARAMETER"
9722 ><I
9723 >lm announce</I
9724 ></TT
9725 ></A
9726 > parameter) then this
9727                 parameter defines the frequency in seconds with which they will be
9728                 made.  If this is set to zero then no Lanman announcements will be
9729                 made despite the setting of the <TT
9730 CLASS="PARAMETER"
9731 ><I
9732 >lm announce</I
9733 ></TT
9734 >
9735                 parameter.</P
9736 ><P
9737 >See also <A
9738 HREF="#LMANNOUNCE"
9739 ><TT
9740 CLASS="PARAMETER"
9741 ><I
9742 >lm
9743                 announce</I
9744 ></TT
9745 ></A
9746 >.</P
9747 ><P
9748 >Default: <B
9749 CLASS="COMMAND"
9750 >lm interval = 60</B
9751 ></P
9752 ><P
9753 >Example: <B
9754 CLASS="COMMAND"
9755 >lm interval = 120</B
9756 ></P
9757 ></DD
9758 ><DT
9759 ><A
9760 NAME="LOADPRINTERS"
9761 ></A
9762 >load printers (G)</DT
9763 ><DD
9764 ><P
9765 >A boolean variable that controls whether all
9766                 printers in the printcap will be loaded for browsing by default.
9767                 See the <A
9768 HREF="#AEN79"
9769 >printers</A
9770 > section for
9771                 more details.</P
9772 ><P
9773 >Default: <B
9774 CLASS="COMMAND"
9775 >load printers = yes</B
9776 ></P
9777 ></DD
9778 ><DT
9779 ><A
9780 NAME="LOCALMASTER"
9781 ></A
9782 >local master (G)</DT
9783 ><DD
9784 ><P
9785 >This option allows <A
9786 HREF="nmbd.8.html"
9787 TARGET="_top"
9788 ><B
9789 CLASS="COMMAND"
9790 >               nmbd(8)</B
9791 ></A
9792 > to try and become a local master browser
9793                 on a subnet. If set to <TT
9794 CLASS="CONSTANT"
9795 >false</TT
9796 > then <B
9797 CLASS="COMMAND"
9798 >               nmbd</B
9799 > will not attempt to become a local master browser
9800                 on a subnet and will also lose in all browsing elections. By
9801                 default this value is set to <TT
9802 CLASS="CONSTANT"
9803 >true</TT
9804 >. Setting this value to <TT
9805 CLASS="CONSTANT"
9806 >true</TT
9807 > doesn't
9808                 mean that Samba will <EM
9809 >become</EM
9810 > the local master
9811                 browser on a subnet, just that <B
9812 CLASS="COMMAND"
9813 >nmbd</B
9814 > will <EM
9815 >               participate</EM
9816 > in elections for local master browser.</P
9817 ><P
9818 >Setting this value to <TT
9819 CLASS="CONSTANT"
9820 >false</TT
9821 > will cause <B
9822 CLASS="COMMAND"
9823 >nmbd</B
9824 >
9825                 <EM
9826 >never</EM
9827 > to become a local master browser.</P
9828 ><P
9829 >Default: <B
9830 CLASS="COMMAND"
9831 >local master = yes</B
9832 ></P
9833 ></DD
9834 ><DT
9835 ><A
9836 NAME="LOCKDIR"
9837 ></A
9838 >lock dir (G)</DT
9839 ><DD
9840 ><P
9841 >Synonym for <A
9842 HREF="#LOCKDIRECTORY"
9843 ><TT
9844 CLASS="PARAMETER"
9845 ><I
9846 >               lock directory</I
9847 ></TT
9848 ></A
9849 >.</P
9850 ></DD
9851 ><DT
9852 ><A
9853 NAME="LOCKDIRECTORY"
9854 ></A
9855 >lock directory (G)</DT
9856 ><DD
9857 ><P
9858 >This option specifies the directory where lock
9859                 files will be placed.  The lock files are used to implement the
9860                 <A
9861 HREF="#MAXCONNECTIONS"
9862 ><TT
9863 CLASS="PARAMETER"
9864 ><I
9865 >max connections</I
9866 ></TT
9867 >
9868                 </A
9869 > option.</P
9870 ><P
9871 >Default: <B
9872 CLASS="COMMAND"
9873 >lock directory = ${prefix}/var/locks</B
9874 ></P
9875 ><P
9876 >Example: <B
9877 CLASS="COMMAND"
9878 >lock directory = /var/run/samba/locks</B
9879 >
9880                 </P
9881 ></DD
9882 ><DT
9883 ><A
9884 NAME="LOCKING"
9885 ></A
9886 >locking (S)</DT
9887 ><DD
9888 ><P
9889 >This controls whether or not locking will be
9890                 performed by the server in response to lock requests from the
9891                 client.</P
9892 ><P
9893 >If <B
9894 CLASS="COMMAND"
9895 >locking = no</B
9896 >, all lock and unlock
9897                 requests will appear to succeed and all lock queries will report
9898                 that the file in question is available for locking.</P
9899 ><P
9900 >If <B
9901 CLASS="COMMAND"
9902 >locking = yes</B
9903 >, real locking will be performed
9904                 by the server.</P
9905 ><P
9906 >This option <EM
9907 >may</EM
9908 > be useful for read-only
9909                 filesystems which <EM
9910 >may</EM
9911 > not need locking (such as
9912                 CDROM drives), although setting this parameter of <TT
9913 CLASS="CONSTANT"
9914 >no</TT
9915 >
9916                 is not really recommended even in this case.</P
9917 ><P
9918 >Be careful about disabling locking either globally or in a
9919                 specific service, as lack of locking may result in data corruption.
9920                 You should never need to set this parameter.</P
9921 ><P
9922 >Default: <B
9923 CLASS="COMMAND"
9924 >locking = yes</B
9925 ></P
9926 ></DD
9927 ><DT
9928 ><A
9929 NAME="LOGFILE"
9930 ></A
9931 >log file (G)</DT
9932 ><DD
9933 ><P
9934 >This option allows you to override the name
9935                 of the Samba log file (also known as the debug file).</P
9936 ><P
9937 >This option takes the standard substitutions, allowing
9938                 you to have separate log files for each user or machine.</P
9939 ><P
9940 >Example: <B
9941 CLASS="COMMAND"
9942 >log file = /usr/local/samba/var/log.%m
9943                 </B
9944 ></P
9945 ></DD
9946 ><DT
9947 ><A
9948 NAME="LOGLEVEL"
9949 ></A
9950 >log level (G)</DT
9951 ><DD
9952 ><P
9953 >The value of the parameter (an integer) allows
9954                 the debug level (logging level) to be specified in the
9955                 <TT
9956 CLASS="FILENAME"
9957 >smb.conf</TT
9958 > file. This is to give greater
9959                 flexibility in the configuration of the system.</P
9960 ><P
9961 >The default will be the log level specified on
9962                 the command line or level zero if none was specified.</P
9963 ><P
9964 >Example: <B
9965 CLASS="COMMAND"
9966 >log level = 3</B
9967 ></P
9968 ></DD
9969 ><DT
9970 ><A
9971 NAME="LOGONDRIVE"
9972 ></A
9973 >logon drive (G)</DT
9974 ><DD
9975 ><P
9976 >This parameter specifies the local path to
9977                 which the home directory will be connected (see <A
9978 HREF="#LOGONHOME"
9979 ><TT
9980 CLASS="PARAMETER"
9981 ><I
9982 >logon home</I
9983 ></TT
9984 ></A
9985 >)
9986                 and is only used by NT Workstations. </P
9987 ><P
9988 >Note that this option is only useful if Samba is set up as a
9989                 logon server.</P
9990 ><P
9991 >Default: <B
9992 CLASS="COMMAND"
9993 >logon drive = z:</B
9994 ></P
9995 ><P
9996 >Example: <B
9997 CLASS="COMMAND"
9998 >logon drive = h:</B
9999 ></P
10000 ></DD
10001 ><DT
10002 ><A
10003 NAME="LOGONHOME"
10004 ></A
10005 >logon home (G)</DT
10006 ><DD
10007 ><P
10008 >This parameter specifies the home directory
10009                 location when a Win95/98 or NT Workstation logs into a Samba PDC.
10010                 It allows you to do </P
10011 ><P
10012 ><TT
10013 CLASS="PROMPT"
10014 >C:\&#62; </TT
10015 ><TT
10016 CLASS="USERINPUT"
10017 ><B
10018 >NET USE H: /HOME</B
10019 ></TT
10020 >
10021                 </P
10022 ><P
10023 >from a command prompt, for example.</P
10024 ><P
10025 >This option takes the standard substitutions, allowing
10026                 you to have separate logon scripts for each user or machine.</P
10027 ><P
10028 >This parameter can be used with Win9X workstations to ensure
10029                 that roaming profiles are stored in a subdirectory of the user's
10030                 home directory.  This is done in the following way:</P
10031 ><P
10032 ><B
10033 CLASS="COMMAND"
10034 >logon home = \\%N\%U\profile</B
10035 ></P
10036 ><P
10037 >This tells Samba to return the above string, with
10038                 substitutions made when a client requests the info, generally
10039                 in a NetUserGetInfo request.  Win9X clients truncate the info to
10040                 \\server\share when a user does <B
10041 CLASS="COMMAND"
10042 >net use /home</B
10043 >
10044                 but use the whole string when dealing with profiles.</P
10045 ><P
10046 >Note that in prior versions of Samba, the <A
10047 HREF="#LOGONPATH"
10048 >               <TT
10049 CLASS="PARAMETER"
10050 ><I
10051 >logon path</I
10052 ></TT
10053 ></A
10054 > was returned rather than
10055                 <TT
10056 CLASS="PARAMETER"
10057 ><I
10058 >logon home</I
10059 ></TT
10060 >.  This broke <B
10061 CLASS="COMMAND"
10062 >net use
10063                 /home</B
10064 > but allowed profiles outside the home directory.
10065                 The current implementation is correct, and can be used for
10066                 profiles if you use the above trick.</P
10067 ><P
10068 >This option is only useful if Samba is set up as a logon
10069                 server.</P
10070 ><P
10071 >Default: <B
10072 CLASS="COMMAND"
10073 >logon home = "\\%N\%U"</B
10074 ></P
10075 ><P
10076 >Example: <B
10077 CLASS="COMMAND"
10078 >logon home = "\\remote_smb_server\%U"</B
10079 >
10080                 </P
10081 ></DD
10082 ><DT
10083 ><A
10084 NAME="LOGONPATH"
10085 ></A
10086 >logon path (G)</DT
10087 ><DD
10088 ><P
10089 >This parameter specifies the home directory
10090                 where roaming profiles (NTuser.dat etc files for Windows NT) are
10091                 stored.  Contrary to previous versions of these manual pages, it has
10092                 nothing to do with Win 9X roaming profiles.  To find out how to
10093                 handle roaming profiles for Win 9X system, see the <A
10094 HREF="#LOGONHOME"
10095 >               <TT
10096 CLASS="PARAMETER"
10097 ><I
10098 >logon home</I
10099 ></TT
10100 ></A
10101 > parameter.</P
10102 ><P
10103 >This option takes the standard substitutions, allowing you
10104                 to have separate logon scripts for each user or machine.  It also
10105                 specifies the directory from which the "Application Data",
10106                 (<TT
10107 CLASS="FILENAME"
10108 >desktop</TT
10109 >, <TT
10110 CLASS="FILENAME"
10111 >start menu</TT
10112 >,
10113                 <TT
10114 CLASS="FILENAME"
10115 >network neighborhood</TT
10116 >, <TT
10117 CLASS="FILENAME"
10118 >programs</TT
10119 >
10120                 and other folders, and their contents, are loaded and displayed on
10121                 your Windows NT client.</P
10122 ><P
10123 >The share and the path must be readable by the user for
10124                 the preferences and directories to be loaded onto the Windows NT
10125                 client.  The share must be writeable when the user logs in for the first
10126                 time, in order that the Windows NT client can create the NTuser.dat
10127                 and other directories.</P
10128 ><P
10129 >Thereafter, the directories and any of the contents can,
10130                 if required, be made read-only.  It is not advisable that the
10131                 NTuser.dat file be made read-only - rename it to NTuser.man to
10132                 achieve the desired effect (a <EM
10133 >MAN</EM
10134 >datory
10135                 profile). </P
10136 ><P
10137 >Windows clients can sometimes maintain a connection to
10138                 the [homes] share, even though there is no user logged in.
10139                 Therefore, it is vital that the logon path does not include a
10140                 reference to the homes share (i.e. setting this parameter to
10141                 \%N\%U\profile_path will cause problems).</P
10142 ><P
10143 >This option takes the standard substitutions, allowing
10144                 you to have separate logon scripts for each user or machine.</P
10145 ><P
10146 >Note that this option is only useful if Samba is set up
10147                 as a logon server.</P
10148 ><P
10149 >Default: <B
10150 CLASS="COMMAND"
10151 >logon path = \\%N\%U\profile</B
10152 ></P
10153 ><P
10154 >Example: <B
10155 CLASS="COMMAND"
10156 >logon path = \\PROFILESERVER\PROFILE\%U</B
10157 ></P
10158 ></DD
10159 ><DT
10160 ><A
10161 NAME="LOGONSCRIPT"
10162 ></A
10163 >logon script (G)</DT
10164 ><DD
10165 ><P
10166 >This parameter specifies the batch file (.bat) or
10167                 NT command file (.cmd) to be downloaded and run on a machine when
10168                 a user successfully logs in.  The file must contain the DOS
10169                 style CR/LF line endings. Using a DOS-style editor to create the
10170                 file is recommended.</P
10171 ><P
10172 >The script must be a relative path to the [netlogon]
10173                 service.  If the [netlogon] service specifies a <A
10174 HREF="#PATH"
10175 >               <TT
10176 CLASS="PARAMETER"
10177 ><I
10178 >path</I
10179 ></TT
10180 ></A
10181 > of <TT
10182 CLASS="FILENAME"
10183 >/usr/local/samba/netlogon
10184                 </TT
10185 >, and <B
10186 CLASS="COMMAND"
10187 >logon script = STARTUP.BAT</B
10188 >, then
10189                 the file that will be downloaded is:</P
10190 ><P
10191 ><TT
10192 CLASS="FILENAME"
10193 >/usr/local/samba/netlogon/STARTUP.BAT</TT
10194 ></P
10195 ><P
10196 >The contents of the batch file are entirely your choice.  A
10197                 suggested command would be to add <B
10198 CLASS="COMMAND"
10199 >NET TIME \\SERVER /SET
10200                 /YES</B
10201 >, to force every machine to synchronize clocks with
10202                 the same time server.  Another use would be to add <B
10203 CLASS="COMMAND"
10204 >NET USE
10205                 U: \\SERVER\UTILS</B
10206 > for commonly used utilities, or <B
10207 CLASS="COMMAND"
10208 >               NET USE Q: \\SERVER\ISO9001_QA</B
10209 > for example.</P
10210 ><P
10211 >Note that it is particularly important not to allow write
10212                 access to the [netlogon] share, or to grant users write permission
10213                 on the batch files in a secure environment, as this would allow
10214                 the batch files to be arbitrarily modified and security to be
10215                 breached.</P
10216 ><P
10217 >This option takes the standard substitutions, allowing you
10218                 to have separate logon scripts for each user or machine.</P
10219 ><P
10220 >This option is only useful if Samba is set up as a logon
10221                 server.</P
10222 ><P
10223 >Default: <EM
10224 >no logon script defined</EM
10225 ></P
10226 ><P
10227 >Example: <B
10228 CLASS="COMMAND"
10229 >logon script = scripts\%U.bat</B
10230 ></P
10231 ></DD
10232 ><DT
10233 ><A
10234 NAME="LPPAUSECOMMAND"
10235 ></A
10236 >lppause command (S)</DT
10237 ><DD
10238 ><P
10239 >This parameter specifies the command to be
10240                 executed on the server host in order to stop printing or spooling
10241                 a specific print job.</P
10242 ><P
10243 >This command should be a program or script which takes
10244                 a printer name and job number to pause the print job. One way
10245                 of implementing this is by using job priorities, where jobs
10246                 having a too low priority won't be sent to the printer.</P
10247 ><P
10248 >If a <TT
10249 CLASS="PARAMETER"
10250 ><I
10251 >%p</I
10252 ></TT
10253 > is given then the printer name
10254                 is put in its place. A <TT
10255 CLASS="PARAMETER"
10256 ><I
10257 >%j</I
10258 ></TT
10259 > is replaced with
10260                 the job number (an integer).  On HPUX (see <TT
10261 CLASS="PARAMETER"
10262 ><I
10263 >printing=hpux
10264                 </I
10265 ></TT
10266 >), if the <TT
10267 CLASS="PARAMETER"
10268 ><I
10269 >-p%p</I
10270 ></TT
10271 > option is added
10272                 to the lpq command, the job will show up with the correct status, i.e.
10273                 if the job priority is lower than the set fence priority it will
10274                 have the PAUSED status, whereas if  the priority is equal or higher it
10275                 will have the SPOOLED or PRINTING status.</P
10276 ><P
10277 >Note that it is good practice to include the absolute path
10278                 in the lppause command as the PATH may not be available to the server.</P
10279 ><P
10280 >See also the <A
10281 HREF="#PRINTING"
10282 ><TT
10283 CLASS="PARAMETER"
10284 ><I
10285 >printing
10286                 </I
10287 ></TT
10288 ></A
10289 > parameter.</P
10290 ><P
10291 >Default: Currently no default value is given to
10292                 this string, unless the value of the <TT
10293 CLASS="PARAMETER"
10294 ><I
10295 >printing</I
10296 ></TT
10297 >
10298                 parameter is <TT
10299 CLASS="CONSTANT"
10300 >SYSV</TT
10301 >, in which case the default is :</P
10302 ><P
10303 ><B
10304 CLASS="COMMAND"
10305 >lp -i %p-%j -H hold</B
10306 ></P
10307 ><P
10308 >or if the value of the <TT
10309 CLASS="PARAMETER"
10310 ><I
10311 >printing</I
10312 ></TT
10313 > parameter
10314                 is <TT
10315 CLASS="CONSTANT"
10316 >SOFTQ</TT
10317 >, then the default is:</P
10318 ><P
10319 ><B
10320 CLASS="COMMAND"
10321 >qstat -s -j%j -h</B
10322 ></P
10323 ><P
10324 >Example for HPUX: <B
10325 CLASS="COMMAND"
10326 >lppause command = /usr/bin/lpalt
10327                 %p-%j -p0</B
10328 ></P
10329 ></DD
10330 ><DT
10331 ><A
10332 NAME="LPQCACHETIME"
10333 ></A
10334 >lpq cache time (G)</DT
10335 ><DD
10336 ><P
10337 >This controls how long lpq info will be cached
10338                 for to prevent the <B
10339 CLASS="COMMAND"
10340 >lpq</B
10341 > command being called too
10342                 often. A separate cache is kept for each variation of the <B
10343 CLASS="COMMAND"
10344 >               lpq</B
10345 > command used by the system, so if you use different
10346                 <B
10347 CLASS="COMMAND"
10348 >lpq</B
10349 > commands for different users then they won't
10350                 share cache information.</P
10351 ><P
10352 >The cache files are stored in <TT
10353 CLASS="FILENAME"
10354 >/tmp/lpq.xxxx</TT
10355 >
10356                 where xxxx is a hash of the <B
10357 CLASS="COMMAND"
10358 >lpq</B
10359 > command in use.</P
10360 ><P
10361 >The default is 10 seconds, meaning that the cached results
10362                 of a previous identical <B
10363 CLASS="COMMAND"
10364 >lpq</B
10365 > command will be used
10366                 if the cached data is less than 10 seconds old. A large value may
10367                 be advisable if your <B
10368 CLASS="COMMAND"
10369 >lpq</B
10370 > command is very slow.</P
10371 ><P
10372 >A value of 0 will disable caching completely.</P
10373 ><P
10374 >See also the <A
10375 HREF="#PRINTING"
10376 ><TT
10377 CLASS="PARAMETER"
10378 ><I
10379 >printing
10380                 </I
10381 ></TT
10382 ></A
10383 > parameter.</P
10384 ><P
10385 >Default: <B
10386 CLASS="COMMAND"
10387 >lpq cache time = 10</B
10388 ></P
10389 ><P
10390 >Example: <B
10391 CLASS="COMMAND"
10392 >lpq cache time = 30</B
10393 ></P
10394 ></DD
10395 ><DT
10396 ><A
10397 NAME="LPQCOMMAND"
10398 ></A
10399 >lpq command (S)</DT
10400 ><DD
10401 ><P
10402 >This parameter specifies the command to be
10403                 executed on the server host in order to obtain <B
10404 CLASS="COMMAND"
10405 >lpq
10406                 </B
10407 >-style printer status information.</P
10408 ><P
10409 >This command should be a program or script which
10410                 takes a printer name as its only parameter and outputs printer
10411                 status information.</P
10412 ><P
10413 >Currently eight styles of printer status information
10414                 are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX and SOFTQ.
10415                 This covers most UNIX systems. You control which type is expected
10416                 using the <TT
10417 CLASS="PARAMETER"
10418 ><I
10419 >printing =</I
10420 ></TT
10421 > option.</P
10422 ><P
10423 >Some clients (notably Windows for Workgroups) may not
10424                 correctly send the connection number for the printer they are
10425                 requesting status information about. To get around this, the
10426                 server reports on the first printer service connected to by the
10427                 client. This only happens if the connection number sent is invalid.</P
10428 ><P
10429 >If a <TT
10430 CLASS="PARAMETER"
10431 ><I
10432 >%p</I
10433 ></TT
10434 > is given then the printer name
10435                 is put in its place. Otherwise it is placed at the end of the
10436                 command.</P
10437 ><P
10438 >Note that it is good practice to include the absolute path
10439                 in the <TT
10440 CLASS="PARAMETER"
10441 ><I
10442 >lpq command</I
10443 ></TT
10444 > as the <TT
10445 CLASS="ENVAR"
10446 >$PATH
10447                 </TT
10448 > may not be available to the server.</P
10449 ><P
10450 >See also the <A
10451 HREF="#PRINTING"
10452 ><TT
10453 CLASS="PARAMETER"
10454 ><I
10455 >printing
10456                 </I
10457 ></TT
10458 ></A
10459 > parameter.</P
10460 ><P
10461 >Default: <EM
10462 >depends on the setting of <TT
10463 CLASS="PARAMETER"
10464 ><I
10465 >               printing</I
10466 ></TT
10467 ></EM
10468 ></P
10469 ><P
10470 >Example: <B
10471 CLASS="COMMAND"
10472 >lpq command = /usr/bin/lpq -P%p</B
10473 ></P
10474 ></DD
10475 ><DT
10476 ><A
10477 NAME="LPRESUMECOMMAND"
10478 ></A
10479 >lpresume command (S)</DT
10480 ><DD
10481 ><P
10482 >This parameter specifies the command to be
10483                 executed on the server host in order to restart or continue
10484                 printing or spooling a specific print job.</P
10485 ><P
10486 >This command should be a program or script which takes
10487                 a printer name and job number to resume the print job. See
10488                 also the <A
10489 HREF="#LPPAUSECOMMAND"
10490 ><TT
10491 CLASS="PARAMETER"
10492 ><I
10493 >lppause command
10494                 </I
10495 ></TT
10496 ></A
10497 > parameter.</P
10498 ><P
10499 >If a <TT
10500 CLASS="PARAMETER"
10501 ><I
10502 >%p</I
10503 ></TT
10504 > is given then the printer name
10505                 is put in its place. A <TT
10506 CLASS="PARAMETER"
10507 ><I
10508 >%j</I
10509 ></TT
10510 > is replaced with
10511                 the job number (an integer).</P
10512 ><P
10513 >Note that it is good practice to include the absolute path
10514                 in the <TT
10515 CLASS="PARAMETER"
10516 ><I
10517 >lpresume command</I
10518 ></TT
10519 > as the PATH may not
10520                 be available to the server.</P
10521 ><P
10522 >See also the <A
10523 HREF="#PRINTING"
10524 ><TT
10525 CLASS="PARAMETER"
10526 ><I
10527 >printing
10528                 </I
10529 ></TT
10530 ></A
10531 > parameter.</P
10532 ><P
10533 >Default: Currently no default value is given
10534                 to this string, unless the value of the <TT
10535 CLASS="PARAMETER"
10536 ><I
10537 >printing</I
10538 ></TT
10539 >
10540                 parameter is <TT
10541 CLASS="CONSTANT"
10542 >SYSV</TT
10543 >, in which case the default is :</P
10544 ><P
10545 ><B
10546 CLASS="COMMAND"
10547 >lp -i %p-%j -H resume</B
10548 ></P
10549 ><P
10550 >or if the value of the <TT
10551 CLASS="PARAMETER"
10552 ><I
10553 >printing</I
10554 ></TT
10555 > parameter
10556                 is <TT
10557 CLASS="CONSTANT"
10558 >SOFTQ</TT
10559 >, then the default is:</P
10560 ><P
10561 ><B
10562 CLASS="COMMAND"
10563 >qstat -s -j%j -r</B
10564 ></P
10565 ><P
10566 >Example for HPUX: <B
10567 CLASS="COMMAND"
10568 >lpresume command = /usr/bin/lpalt
10569                 %p-%j -p2</B
10570 ></P
10571 ></DD
10572 ><DT
10573 ><A
10574 NAME="LPRMCOMMAND"
10575 ></A
10576 >lprm command (S)</DT
10577 ><DD
10578 ><P
10579 >This parameter specifies the command to be
10580                 executed on the server host in order to delete a print job.</P
10581 ><P
10582 >This command should be a program or script which takes
10583                 a printer name and job number, and deletes the print job.</P
10584 ><P
10585 >If a <TT
10586 CLASS="PARAMETER"
10587 ><I
10588 >%p</I
10589 ></TT
10590 > is given then the printer name
10591                 is put in its place. A <TT
10592 CLASS="PARAMETER"
10593 ><I
10594 >%j</I
10595 ></TT
10596 > is replaced with
10597                 the job number (an integer).</P
10598 ><P
10599 >Note that it is good practice to include the absolute
10600                 path in the <TT
10601 CLASS="PARAMETER"
10602 ><I
10603 >lprm command</I
10604 ></TT
10605 > as the PATH may not be
10606                 available to the server.</P
10607 ><P
10608 >See also the <A
10609 HREF="#PRINTING"
10610 ><TT
10611 CLASS="PARAMETER"
10612 ><I
10613 >printing
10614                 </I
10615 ></TT
10616 ></A
10617 > parameter.</P
10618 ><P
10619 >Default: <EM
10620 >depends on the setting of <TT
10621 CLASS="PARAMETER"
10622 ><I
10623 >printing
10624                 </I
10625 ></TT
10626 ></EM
10627 ></P
10628 ><P
10629 >Example 1: <B
10630 CLASS="COMMAND"
10631 >lprm command = /usr/bin/lprm -P%p %j
10632                 </B
10633 ></P
10634 ><P
10635 >Example 2: <B
10636 CLASS="COMMAND"
10637 >lprm command = /usr/bin/cancel %p-%j
10638                 </B
10639 ></P
10640 ></DD
10641 ><DT
10642 ><A
10643 NAME="MACHINEPASSWORDTIMEOUT"
10644 ></A
10645 >machine password timeout (G)</DT
10646 ><DD
10647 ><P
10648 >If a Samba server is a member of a Windows
10649                 NT Domain (see the <A
10650 HREF="#SECURITYEQUALSDOMAIN"
10651 >security = domain</A
10652 >)
10653                 parameter) then periodically a running <A
10654 HREF="smbd.8.html"
10655 TARGET="_top"
10656 >               smbd(8)</A
10657 > process will try and change the MACHINE ACCOUNT
10658                 PASSWORD stored in the TDB called <TT
10659 CLASS="FILENAME"
10660 >private/secrets.tdb
10661                 </TT
10662 >.  This parameter specifies how often this password
10663                 will be changed, in seconds. The default is one week (expressed in
10664                 seconds), the same as a Windows NT Domain member server.</P
10665 ><P
10666 >See also <A
10667 HREF="smbpasswd.8.html"
10668 TARGET="_top"
10669 ><B
10670 CLASS="COMMAND"
10671 >smbpasswd(8)
10672                 </B
10673 ></A
10674 >, and the <A
10675 HREF="#SECURITYEQUALSDOMAIN"
10676 >               security = domain</A
10677 >) parameter.</P
10678 ><P
10679 >Default: <B
10680 CLASS="COMMAND"
10681 >machine password timeout = 604800</B
10682 ></P
10683 ></DD
10684 ><DT
10685 ><A
10686 NAME="MAGICOUTPUT"
10687 ></A
10688 >magic output (S)</DT
10689 ><DD
10690 ><P
10691 >This parameter specifies the name of a file
10692                 which will contain output created by a magic script (see the
10693                 <A
10694 HREF="#MAGICSCRIPT"
10695 ><TT
10696 CLASS="PARAMETER"
10697 ><I
10698 >magic script</I
10699 ></TT
10700 ></A
10701 >
10702                 parameter below).</P
10703 ><P
10704 >Warning: If two clients use the same <TT
10705 CLASS="PARAMETER"
10706 ><I
10707 >magic script
10708                 </I
10709 ></TT
10710 > in the same directory the output file content
10711                 is undefined.</P
10712 ><P
10713 >Default: <B
10714 CLASS="COMMAND"
10715 >magic output = &#60;magic script name&#62;.out
10716                 </B
10717 ></P
10718 ><P
10719 >Example: <B
10720 CLASS="COMMAND"
10721 >magic output = myfile.txt</B
10722 ></P
10723 ></DD
10724 ><DT
10725 ><A
10726 NAME="MAGICSCRIPT"
10727 ></A
10728 >magic script (S)</DT
10729 ><DD
10730 ><P
10731 >This parameter specifies the name of a file which,
10732                 if opened, will be executed by the server when the file is closed.
10733                 This allows a UNIX script to be sent to the Samba host and
10734                 executed on behalf of the connected user.</P
10735 ><P
10736 >Scripts executed in this way will be deleted upon
10737                 completion assuming that the user has the appropriate level
10738                 of privilege and the file permissions allow the deletion.</P
10739 ><P
10740 >If the script generates output, output will be sent to
10741                 the file specified by the <A
10742 HREF="#MAGICOUTPUT"
10743 ><TT
10744 CLASS="PARAMETER"
10745 ><I
10746 >               magic output</I
10747 ></TT
10748 ></A
10749 > parameter (see above).</P
10750 ><P
10751 >Note that some shells are unable to interpret scripts
10752                 containing CR/LF instead of CR as
10753                 the end-of-line marker. Magic scripts must be executable
10754                 <EM
10755 >as is</EM
10756 > on the host, which for some hosts and
10757                 some shells will require filtering at the DOS end.</P
10758 ><P
10759 >Magic scripts are <EM
10760 >EXPERIMENTAL</EM
10761 > and
10762                 should <EM
10763 >NOT</EM
10764 > be relied upon.</P
10765 ><P
10766 >Default: <EM
10767 >None. Magic scripts disabled.</EM
10768 ></P
10769 ><P
10770 >Example: <B
10771 CLASS="COMMAND"
10772 >magic script = user.csh</B
10773 ></P
10774 ></DD
10775 ><DT
10776 ><A
10777 NAME="MANGLECASE"
10778 ></A
10779 >mangle case (S)</DT
10780 ><DD
10781 ><P
10782 >See the section on <A
10783 HREF="#AEN202"
10784 >               NAME MANGLING</A
10785 ></P
10786 ><P
10787 >Default: <B
10788 CLASS="COMMAND"
10789 >mangle case = no</B
10790 ></P
10791 ></DD
10792 ><DT
10793 ><A
10794 NAME="MANGLEDMAP"
10795 ></A
10796 >mangled map (S)</DT
10797 ><DD
10798 ><P
10799 >This is for those who want to directly map UNIX
10800                 file names which cannot be represented on Windows/DOS.  The mangling
10801                 of names is not always what is needed.  In particular you may have
10802                 documents with file extensions that differ between DOS and UNIX.
10803                 For example, under UNIX it is common to use <TT
10804 CLASS="FILENAME"
10805 >.html</TT
10806 >
10807                 for HTML files, whereas under Windows/DOS <TT
10808 CLASS="FILENAME"
10809 >.htm</TT
10810 >
10811                 is more commonly used.</P
10812 ><P
10813 >So to map <TT
10814 CLASS="FILENAME"
10815 >html</TT
10816 > to <TT
10817 CLASS="FILENAME"
10818 >htm</TT
10819 >
10820                 you would use:</P
10821 ><P
10822 ><B
10823 CLASS="COMMAND"
10824 >mangled map = (*.html *.htm)</B
10825 ></P
10826 ><P
10827 >One very useful case is to remove the annoying <TT
10828 CLASS="FILENAME"
10829 >;1
10830                 </TT
10831 > off the ends of filenames on some CDROMs (only visible
10832                 under some UNIXes). To do this use a map of (*;1 *;).</P
10833 ><P
10834 >Default: <EM
10835 >no mangled map</EM
10836 ></P
10837 ><P
10838 >Example: <B
10839 CLASS="COMMAND"
10840 >mangled map = (*;1 *;)</B
10841 ></P
10842 ></DD
10843 ><DT
10844 ><A
10845 NAME="MANGLEDNAMES"
10846 ></A
10847 >mangled names (S)</DT
10848 ><DD
10849 ><P
10850 >This controls whether non-DOS names under UNIX
10851                 should be mapped to DOS-compatible names ("mangled") and made visible,
10852                 or whether non-DOS names should simply be ignored.</P
10853 ><P
10854 >See the section on <A
10855 HREF="#AEN202"
10856 >               NAME MANGLING</A
10857 > for details on how to control the mangling process.</P
10858 ><P
10859 >If mangling is used then the mangling algorithm is as follows:</P
10860 ><P
10861 ></P
10862 ><UL
10863 ><LI
10864 ><P
10865 >The first (up to) five alphanumeric characters
10866                         before the rightmost dot of the filename are preserved, forced
10867                         to upper case, and appear as the first (up to) five characters
10868                         of the mangled name.</P
10869 ></LI
10870 ><LI
10871 ><P
10872 >A tilde "~" is appended to the first part of the mangled
10873                         name, followed by a two-character unique sequence, based on the
10874                         original root name (i.e., the original filename minus its final
10875                         extension). The final extension is included in the hash calculation
10876                         only if it contains any upper case characters or is longer than three
10877                         characters.</P
10878 ><P
10879 >Note that the character to use may be specified using
10880                         the <A
10881 HREF="#MANGLINGCHAR"
10882 ><TT
10883 CLASS="PARAMETER"
10884 ><I
10885 >mangling char</I
10886 ></TT
10887 >
10888                         </A
10889 > option, if you don't like '~'.</P
10890 ></LI
10891 ><LI
10892 ><P
10893 >The first three alphanumeric characters of the final
10894                         extension are preserved, forced to upper case and appear as the
10895                         extension of the mangled name. The final extension is defined as that
10896                         part of the original filename after the rightmost dot. If there are no
10897                         dots in the filename, the mangled name will have no extension (except
10898                         in the case of "hidden files" - see below).</P
10899 ></LI
10900 ><LI
10901 ><P
10902 >Files whose UNIX name begins with a dot will be
10903                         presented as DOS hidden files. The mangled name will be created as
10904                         for other filenames, but with the leading dot removed and "___" as
10905                         its extension regardless of actual original extension (that's three
10906                         underscores).</P
10907 ></LI
10908 ></UL
10909 ><P
10910 >The two-digit hash value consists of upper case
10911                 alphanumeric characters.</P
10912 ><P
10913 >This algorithm can cause name collisions only if files
10914                 in a directory share the same first five alphanumeric characters.
10915                 The probability of such a clash is 1/1300.</P
10916 ><P
10917 >The name mangling (if enabled) allows a file to be
10918                 copied between UNIX directories from Windows/DOS while retaining
10919                 the long UNIX filename. UNIX files can be renamed to a new extension
10920                 from Windows/DOS and will retain the same basename. Mangled names
10921                 do not change between sessions.</P
10922 ><P
10923 >Default: <B
10924 CLASS="COMMAND"
10925 >mangled names = yes</B
10926 ></P
10927 ></DD
10928 ><DT
10929 ><A
10930 NAME="MANGLEDSTACK"
10931 ></A
10932 >mangled stack (G)</DT
10933 ><DD
10934 ><P
10935 >This parameter controls the number of mangled names
10936                 that should be cached in the Samba server <A
10937 HREF="smbd.8.html"
10938 TARGET="_top"
10939 >               smbd(8)</A
10940 >.</P
10941 ><P
10942 >This stack is a list of recently mangled base names
10943                 (extensions are only maintained if they are longer than 3 characters
10944                 or contains upper case characters).</P
10945 ><P
10946 >The larger this value, the more likely it is that mangled
10947                 names can be successfully converted to correct long UNIX names.
10948                 However, large stack sizes will slow most directory accesses. Smaller
10949                 stacks save memory in the server (each stack element costs 256 bytes).
10950                 </P
10951 ><P
10952 >It is not possible to absolutely guarantee correct long
10953                 filenames, so be prepared for some surprises!</P
10954 ><P
10955 >Default: <B
10956 CLASS="COMMAND"
10957 >mangled stack = 50</B
10958 ></P
10959 ><P
10960 >Example: <B
10961 CLASS="COMMAND"
10962 >mangled stack = 100</B
10963 ></P
10964 ></DD
10965 ><DT
10966 ><A
10967 NAME="MANGLINGCHAR"
10968 ></A
10969 >mangling char (S)</DT
10970 ><DD
10971 ><P
10972 >This controls what character is used as
10973                 the <EM
10974 >magic</EM
10975 > character in <A
10976 HREF="#AEN202"
10977 >name mangling</A
10978 >. The default is a '~'
10979                 but this may interfere with some software. Use this option to set
10980                 it to whatever you prefer.</P
10981 ><P
10982 >Default: <B
10983 CLASS="COMMAND"
10984 >mangling char = ~</B
10985 ></P
10986 ><P
10987 >Example: <B
10988 CLASS="COMMAND"
10989 >mangling char = ^</B
10990 ></P
10991 ></DD
10992 ><DT
10993 ><A
10994 NAME="MAPARCHIVE"
10995 ></A
10996 >map archive (S)</DT
10997 ><DD
10998 ><P
10999 >This controls whether the DOS archive attribute
11000                 should be mapped to the UNIX owner execute bit.  The DOS archive bit
11001                 is set when a file has been modified since its last backup.  One
11002                 motivation for this option it to keep Samba/your PC from making
11003                 any file it touches from becoming executable under UNIX.  This can
11004                 be quite annoying for shared source code, documents, etc...</P
11005 ><P
11006 >Note that this requires the <TT
11007 CLASS="PARAMETER"
11008 ><I
11009 >create mask</I
11010 ></TT
11011 >
11012                 parameter to be set such that owner execute bit is not masked out
11013                 (i.e. it must include 100). See the parameter <A
11014 HREF="#CREATEMASK"
11015 >               <TT
11016 CLASS="PARAMETER"
11017 ><I
11018 >create mask</I
11019 ></TT
11020 ></A
11021 > for details.</P
11022 ><P
11023 >Default: <B
11024 CLASS="COMMAND"
11025 >map archive = yes</B
11026 ></P
11027 ></DD
11028 ><DT
11029 ><A
11030 NAME="MAPHIDDEN"
11031 ></A
11032 >map hidden (S)</DT
11033 ><DD
11034 ><P
11035 >This controls whether DOS style hidden files
11036                 should be mapped to the UNIX world execute bit.</P
11037 ><P
11038 >Note that this requires the <TT
11039 CLASS="PARAMETER"
11040 ><I
11041 >create mask</I
11042 ></TT
11043 >
11044                 to be set such that the world execute bit is not masked out (i.e.
11045                 it must include 001). See the parameter <A
11046 HREF="#CREATEMASK"
11047 >               <TT
11048 CLASS="PARAMETER"
11049 ><I
11050 >create mask</I
11051 ></TT
11052 ></A
11053 > for details.</P
11054 ><P
11055 >Default: <B
11056 CLASS="COMMAND"
11057 >map hidden = no</B
11058 ></P
11059 ></DD
11060 ><DT
11061 ><A
11062 NAME="MAPSYSTEM"
11063 ></A
11064 >map system (S)</DT
11065 ><DD
11066 ><P
11067 >This controls whether DOS style system files
11068                 should be mapped to the UNIX group execute bit.</P
11069 ><P
11070 >Note that this requires the <TT
11071 CLASS="PARAMETER"
11072 ><I
11073 >create mask</I
11074 ></TT
11075 >
11076                 to be set such that the group execute bit is not masked out (i.e.
11077                 it must include 010). See the parameter <A
11078 HREF="#CREATEMASK"
11079 >               <TT
11080 CLASS="PARAMETER"
11081 ><I
11082 >create mask</I
11083 ></TT
11084 ></A
11085 > for details.</P
11086 ><P
11087 >Default: <B
11088 CLASS="COMMAND"
11089 >map system = no</B
11090 ></P
11091 ></DD
11092 ><DT
11093 ><A
11094 NAME="MAPTOGUEST"
11095 ></A
11096 >map to guest (G)</DT
11097 ><DD
11098 ><P
11099 >This parameter is only useful in <A
11100 HREF="#SECURITY"
11101 >               security</A
11102 > modes other than <TT
11103 CLASS="PARAMETER"
11104 ><I
11105 >security = share</I
11106 ></TT
11107 >
11108                 - i.e. <TT
11109 CLASS="CONSTANT"
11110 >user</TT
11111 >, <TT
11112 CLASS="CONSTANT"
11113 >server</TT
11114 >,
11115                 and <TT
11116 CLASS="CONSTANT"
11117 >domain</TT
11118 >.</P
11119 ><P
11120 >This parameter can take three different values, which tell
11121                 <A
11122 HREF="smbd.8.html"
11123 TARGET="_top"
11124 >smbd(8)</A
11125 > what to do with user
11126                 login requests that don't match a valid UNIX user in some way.</P
11127 ><P
11128 >The three settings are :</P
11129 ><P
11130 ></P
11131 ><UL
11132 ><LI
11133 ><P
11134 ><TT
11135 CLASS="CONSTANT"
11136 >Never</TT
11137 > - Means user login
11138                         requests with an invalid password are rejected. This is the
11139                         default.</P
11140 ></LI
11141 ><LI
11142 ><P
11143 ><TT
11144 CLASS="CONSTANT"
11145 >Bad User</TT
11146 > - Means user
11147                         logins with an invalid password are rejected, unless the username
11148                         does not exist, in which case it is treated as a guest login and
11149                         mapped into the <A
11150 HREF="#GUESTACCOUNT"
11151 ><TT
11152 CLASS="PARAMETER"
11153 ><I
11154 >                       guest account</I
11155 ></TT
11156 ></A
11157 >.</P
11158 ></LI
11159 ><LI
11160 ><P
11161 ><TT
11162 CLASS="CONSTANT"
11163 >Bad Password</TT
11164 > - Means user logins
11165                         with an invalid password are treated as a guest login and mapped
11166                         into the <A
11167 HREF="#GUESTACCOUNT"
11168 >guest account</A
11169 >. Note that
11170                         this can cause problems as it means that any user incorrectly typing
11171                         their password will be silently logged on as "guest" - and
11172                         will not know the reason they cannot access files they think
11173                         they should - there will have been no message given to them
11174                         that they got their password wrong. Helpdesk services will
11175                         <EM
11176 >hate</EM
11177 > you if you set the <TT
11178 CLASS="PARAMETER"
11179 ><I
11180 >map to
11181                         guest</I
11182 ></TT
11183 > parameter this way :-).</P
11184 ></LI
11185 ></UL
11186 ><P
11187 >Note that this parameter is needed to set up "Guest"
11188                 share services when using <TT
11189 CLASS="PARAMETER"
11190 ><I
11191 >security</I
11192 ></TT
11193 > modes other than
11194                 share. This is because in these modes the name of the resource being
11195                 requested is <EM
11196 >not</EM
11197 > sent to the server until after
11198                 the server has successfully authenticated the client so the server
11199                 cannot make authentication decisions at the correct time (connection
11200                 to the share) for "Guest" shares.</P
11201 ><P
11202 >For people familiar with the older Samba releases, this
11203                 parameter maps to the old compile-time setting of the <TT
11204 CLASS="CONSTANT"
11205 >               GUEST_SESSSETUP</TT
11206 > value in local.h.</P
11207 ><P
11208 >Default: <B
11209 CLASS="COMMAND"
11210 >map to guest = Never</B
11211 ></P
11212 ><P
11213 >Example: <B
11214 CLASS="COMMAND"
11215 >map to guest = Bad User</B
11216 ></P
11217 ></DD
11218 ><DT
11219 ><A
11220 NAME="MAXCONNECTIONS"
11221 ></A
11222 >max connections (S)</DT
11223 ><DD
11224 ><P
11225 >This option allows the number of simultaneous
11226                 connections to a service to be limited. If <TT
11227 CLASS="PARAMETER"
11228 ><I
11229 >max connections
11230                 </I
11231 ></TT
11232 > is greater than 0 then connections will be refused if
11233                 this number of connections to the service are already open. A value
11234                 of zero mean an unlimited number of connections may be made.</P
11235 ><P
11236 >Record lock files are used to implement this feature. The
11237                 lock files will be stored in the directory specified by the <A
11238 HREF="#LOCKDIRECTORY"
11239 ><TT
11240 CLASS="PARAMETER"
11241 ><I
11242 >lock directory</I
11243 ></TT
11244 ></A
11245 >
11246                 option.</P
11247 ><P
11248 >Default: <B
11249 CLASS="COMMAND"
11250 >max connections = 0</B
11251 ></P
11252 ><P
11253 >Example: <B
11254 CLASS="COMMAND"
11255 >max connections = 10</B
11256 ></P
11257 ></DD
11258 ><DT
11259 ><A
11260 NAME="MAXDISKSIZE"
11261 ></A
11262 >max disk size (G)</DT
11263 ><DD
11264 ><P
11265 >This option allows you to put an upper limit
11266                 on the apparent size of disks. If you set this option to 100
11267                 then all shares will appear to be not larger than 100 MB in
11268                 size.</P
11269 ><P
11270 >Note that this option does not limit the amount of
11271                 data you can put on the disk. In the above case you could still
11272                 store much more than 100 MB on the disk, but if a client ever asks
11273                 for the amount of free disk space or the total disk size then the
11274                 result will be bounded by the amount specified in <TT
11275 CLASS="PARAMETER"
11276 ><I
11277 >max
11278                 disk size</I
11279 ></TT
11280 >.</P
11281 ><P
11282 >This option is primarily useful to work around bugs
11283                 in some pieces of software that can't handle very large disks,
11284                 particularly disks over 1GB in size.</P
11285 ><P
11286 >A <TT
11287 CLASS="PARAMETER"
11288 ><I
11289 >max disk size</I
11290 ></TT
11291 > of 0 means no limit.</P
11292 ><P
11293 >Default: <B
11294 CLASS="COMMAND"
11295 >max disk size = 0</B
11296 ></P
11297 ><P
11298 >Example: <B
11299 CLASS="COMMAND"
11300 >max disk size = 1000</B
11301 ></P
11302 ></DD
11303 ><DT
11304 ><A
11305 NAME="MAXLOGSIZE"
11306 ></A
11307 >max log size (G)</DT
11308 ><DD
11309 ><P
11310 >This option (an integer in kilobytes) specifies
11311                 the max size the log file should grow to. Samba periodically checks
11312                 the size and if it is exceeded it will rename the file, adding
11313                 a <TT
11314 CLASS="FILENAME"
11315 >.old</TT
11316 > extension.</P
11317 ><P
11318 >A size of 0 means no limit.</P
11319 ><P
11320 >Default: <B
11321 CLASS="COMMAND"
11322 >max log size = 5000</B
11323 ></P
11324 ><P
11325 >Example: <B
11326 CLASS="COMMAND"
11327 >max log size = 1000</B
11328 ></P
11329 ></DD
11330 ><DT
11331 ><A
11332 NAME="MAXMUX"
11333 ></A
11334 >max mux (G)</DT
11335 ><DD
11336 ><P
11337 >This option controls the maximum number of
11338                 outstanding simultaneous SMB operations that Samba tells the client
11339                 it will allow. You should never need to set this parameter.</P
11340 ><P
11341 >Default: <B
11342 CLASS="COMMAND"
11343 >max mux = 50</B
11344 ></P
11345 ></DD
11346 ><DT
11347 ><A
11348 NAME="MAXOPENFILES"
11349 ></A
11350 >max open files (G)</DT
11351 ><DD
11352 ><P
11353 >This parameter limits the maximum number of
11354                 open files that one <A
11355 HREF="smbd.8.html"
11356 TARGET="_top"
11357 >smbd(8)</A
11358 > file
11359                 serving process may have open for a client at any one time. The
11360                 default for this parameter is set very high (10,000) as Samba uses
11361                 only one bit per unopened file.</P
11362 ><P
11363 >The limit of the number of open files is usually set
11364                 by the UNIX per-process file descriptor limit rather than
11365                 this parameter so you should never need to touch this parameter.</P
11366 ><P
11367 >Default: <B
11368 CLASS="COMMAND"
11369 >max open files = 10000</B
11370 ></P
11371 ></DD
11372 ><DT
11373 ><A
11374 NAME="MAXPRINTJOBS"
11375 ></A
11376 >max print jobs (S)</DT
11377 ><DD
11378 ><P
11379 >This parameter limits the maximum number of
11380                 jobs allowable in a Samba printer queue at any given moment.
11381                 If this number is exceeded, <A
11382 HREF="smbd.8.html"
11383 TARGET="_top"
11384 ><B
11385 CLASS="COMMAND"
11386 >               smbd(8)</B
11387 ></A
11388 > will remote "Out of Space" to the client.
11389                 See all <A
11390 HREF="#TOTALPRINTJOBS"
11391 ><TT
11392 CLASS="PARAMETER"
11393 ><I
11394 >total
11395                 print jobs</I
11396 ></TT
11397 ></A
11398 >.
11399                 </P
11400 ><P
11401 >Default: <B
11402 CLASS="COMMAND"
11403 >max print jobs = 1000</B
11404 ></P
11405 ><P
11406 >Example: <B
11407 CLASS="COMMAND"
11408 >max print jobs = 5000</B
11409 ></P
11410 ></DD
11411 ><DT
11412 ><A
11413 NAME="MAXPROTOCOL"
11414 ></A
11415 >max protocol (G)</DT
11416 ><DD
11417 ><P
11418 >The value of the parameter (a string) is the highest
11419                 protocol level that will be supported by the server.</P
11420 ><P
11421 >Possible values are :</P
11422 ><P
11423 ></P
11424 ><UL
11425 ><LI
11426 ><P
11427 ><TT
11428 CLASS="CONSTANT"
11429 >CORE</TT
11430 >: Earliest version. No
11431                         concept of user names.</P
11432 ></LI
11433 ><LI
11434 ><P
11435 ><TT
11436 CLASS="CONSTANT"
11437 >COREPLUS</TT
11438 >: Slight improvements on
11439                         CORE for efficiency.</P
11440 ></LI
11441 ><LI
11442 ><P
11443 ><TT
11444 CLASS="CONSTANT"
11445 >LANMAN1</TT
11446 >: First <EM
11447 >                       modern</EM
11448 > version of the protocol. Long filename
11449                         support.</P
11450 ></LI
11451 ><LI
11452 ><P
11453 ><TT
11454 CLASS="CONSTANT"
11455 >LANMAN2</TT
11456 >: Updates to Lanman1 protocol.
11457                         </P
11458 ></LI
11459 ><LI
11460 ><P
11461 ><TT
11462 CLASS="CONSTANT"
11463 >NT1</TT
11464 >: Current up to date version of
11465                         the protocol. Used by Windows NT. Known as CIFS.</P
11466 ></LI
11467 ></UL
11468 ><P
11469 >Normally this option should not be set as the automatic
11470                 negotiation phase in the SMB protocol takes care of choosing
11471                 the appropriate protocol.</P
11472 ><P
11473 >See also <A
11474 HREF="#MINPROTOCOL"
11475 ><TT
11476 CLASS="PARAMETER"
11477 ><I
11478 >min
11479                 protocol</I
11480 ></TT
11481 ></A
11482 ></P
11483 ><P
11484 >Default: <B
11485 CLASS="COMMAND"
11486 >max protocol = NT1</B
11487 ></P
11488 ><P
11489 >Example: <B
11490 CLASS="COMMAND"
11491 >max protocol = LANMAN1</B
11492 ></P
11493 ></DD
11494 ><DT
11495 ><A
11496 NAME="MAXSMBDPROCESSES"
11497 ></A
11498 >max smbd processes (G)</DT
11499 ><DD
11500 ><P
11501 >This parameter limits the maximum number of
11502                 <A
11503 HREF="smbd.8.html"
11504 TARGET="_top"
11505 ><B
11506 CLASS="COMMAND"
11507 >smbd(8)</B
11508 ></A
11509 >
11510                 processes concurrently running on a system and is intended
11511                 as a stopgap to prevent degrading service to clients in the event
11512                 that the server has insufficient resources to handle more than this
11513                 number of connections.  Remember that under normal operating
11514                 conditions, each user will have an <A
11515 HREF="smbd.8.html"
11516 TARGET="_top"
11517 >smbd</A
11518 > associated with him or her
11519                 to handle connections to all shares from a given host.
11520                 </P
11521 ><P
11522 >Default: <B
11523 CLASS="COMMAND"
11524 >max smbd processes = 0</B
11525 >   ## no limit</P
11526 ><P
11527 >Example: <B
11528 CLASS="COMMAND"
11529 >max smbd processes = 1000</B
11530 ></P
11531 ></DD
11532 ><DT
11533 ><A
11534 NAME="MAXTTL"
11535 ></A
11536 >max ttl (G)</DT
11537 ><DD
11538 ><P
11539 >This option tells <A
11540 HREF="nmbd.8.html"
11541 TARGET="_top"
11542 >nmbd(8)</A
11543 >
11544                 what the default 'time to live' of NetBIOS names should be (in seconds)
11545                 when <B
11546 CLASS="COMMAND"
11547 >nmbd</B
11548 > is requesting a name using either a
11549                 broadcast packet or from a WINS server. You should never need to
11550                 change this parameter. The default is 3 days.</P
11551 ><P
11552 >Default: <B
11553 CLASS="COMMAND"
11554 >max ttl = 259200</B
11555 ></P
11556 ></DD
11557 ><DT
11558 ><A
11559 NAME="MAXWINSTTL"
11560 ></A
11561 >max wins ttl (G)</DT
11562 ><DD
11563 ><P
11564 >This option tells <A
11565 HREF="nmbd.8.html"
11566 TARGET="_top"
11567 >nmbd(8)
11568                 </A
11569 > when acting as a WINS server (<A
11570 HREF="#WINSSUPPORT"
11571 >               <TT
11572 CLASS="PARAMETER"
11573 ><I
11574 >wins support = yes</I
11575 ></TT
11576 ></A
11577 >) what the maximum
11578                 'time to live' of NetBIOS names that <B
11579 CLASS="COMMAND"
11580 >nmbd</B
11581 >
11582                 will grant will be (in seconds). You should never need to change this
11583                 parameter.  The default is 6 days (518400 seconds).</P
11584 ><P
11585 >See also the <A
11586 HREF="#MINWINSTTL"
11587 ><TT
11588 CLASS="PARAMETER"
11589 ><I
11590 >min
11591                 wins ttl</I
11592 ></TT
11593 ></A
11594 > parameter.</P
11595 ><P
11596 >Default: <B
11597 CLASS="COMMAND"
11598 >max wins ttl = 518400</B
11599 ></P
11600 ></DD
11601 ><DT
11602 ><A
11603 NAME="MAXXMIT"
11604 ></A
11605 >max xmit (G)</DT
11606 ><DD
11607 ><P
11608 >This option controls the maximum packet size
11609                 that will be negotiated by Samba. The default is 65535, which
11610                 is the maximum. In some cases you may find you get better performance
11611                 with a smaller value. A value below 2048 is likely to cause problems.
11612                 </P
11613 ><P
11614 >Default: <B
11615 CLASS="COMMAND"
11616 >max xmit = 65535</B
11617 ></P
11618 ><P
11619 >Example: <B
11620 CLASS="COMMAND"
11621 >max xmit = 8192</B
11622 ></P
11623 ></DD
11624 ><DT
11625 ><A
11626 NAME="MESSAGECOMMAND"
11627 ></A
11628 >message command (G)</DT
11629 ><DD
11630 ><P
11631 >This specifies what command to run when the
11632                 server receives a WinPopup style message.</P
11633 ><P
11634 >This would normally be a command that would
11635                 deliver the message somehow. How this is to be done is
11636                 up to your imagination.</P
11637 ><P
11638 >An example is:</P
11639 ><P
11640 ><B
11641 CLASS="COMMAND"
11642 >message command = csh -c 'xedit %s;rm %s' &#38;</B
11643 >
11644                 </P
11645 ><P
11646 >This delivers the message using <B
11647 CLASS="COMMAND"
11648 >xedit</B
11649 >, then
11650                 removes it afterwards. <EM
11651 >NOTE THAT IT IS VERY IMPORTANT
11652                 THAT THIS COMMAND RETURN IMMEDIATELY</EM
11653 >. That's why I
11654                 have the '&#38;' on the end. If it doesn't return immediately then
11655                 your PCs may freeze when sending messages (they should recover
11656                 after 30 seconds, hopefully).</P
11657 ><P
11658 >All messages are delivered as the global guest user.
11659                 The command takes the standard substitutions, although <TT
11660 CLASS="PARAMETER"
11661 ><I
11662 >               %u</I
11663 ></TT
11664 > won't work (<TT
11665 CLASS="PARAMETER"
11666 ><I
11667 >%U</I
11668 ></TT
11669 > may be better
11670                 in this case).</P
11671 ><P
11672 >Apart from the standard substitutions, some additional
11673                 ones apply. In particular:</P
11674 ><P
11675 ></P
11676 ><UL
11677 ><LI
11678 ><P
11679 ><TT
11680 CLASS="PARAMETER"
11681 ><I
11682 >%s</I
11683 ></TT
11684 > = the filename containing
11685                         the message.</P
11686 ></LI
11687 ><LI
11688 ><P
11689 ><TT
11690 CLASS="PARAMETER"
11691 ><I
11692 >%t</I
11693 ></TT
11694 > = the destination that
11695                         the message was sent to (probably the server name).</P
11696 ></LI
11697 ><LI
11698 ><P
11699 ><TT
11700 CLASS="PARAMETER"
11701 ><I
11702 >%f</I
11703 ></TT
11704 > = who the message
11705                         is from.</P
11706 ></LI
11707 ></UL
11708 ><P
11709 >You could make this command send mail, or whatever else
11710                 takes your fancy. Please let us know of any really interesting
11711                 ideas you have.</P
11712 ><P
11713 >Here's a way of sending the messages as mail to root:</P
11714 ><P
11715 ><B
11716 CLASS="COMMAND"
11717 >message command = /bin/mail -s 'message from %f on
11718                 %m' root &#60; %s; rm %s</B
11719 ></P
11720 ><P
11721 >If you don't have a message command then the message
11722                 won't be delivered and Samba will tell the sender there was
11723                 an error. Unfortunately WfWg totally ignores the error code
11724                 and carries on regardless, saying that the message was delivered.
11725                 </P
11726 ><P
11727 >If you want to silently delete it then try:</P
11728 ><P
11729 ><B
11730 CLASS="COMMAND"
11731 >message command = rm %s</B
11732 ></P
11733 ><P
11734 >Default: <EM
11735 >no message command</EM
11736 ></P
11737 ><P
11738 >Example: <B
11739 CLASS="COMMAND"
11740 >message command = csh -c 'xedit %s;
11741                 rm %s' &#38;</B
11742 ></P
11743 ></DD
11744 ><DT
11745 ><A
11746 NAME="MINPASSWDLENGTH"
11747 ></A
11748 >min passwd length (G)</DT
11749 ><DD
11750 ><P
11751 >Synonym for <A
11752 HREF="#MINPASSWORDLENGTH"
11753 >               <TT
11754 CLASS="PARAMETER"
11755 ><I
11756 >min password length</I
11757 ></TT
11758 ></A
11759 >.</P
11760 ></DD
11761 ><DT
11762 ><A
11763 NAME="MINPASSWORDLENGTH"
11764 ></A
11765 >min password length (G)</DT
11766 ><DD
11767 ><P
11768 >This option sets the minimum length in characters
11769                 of a plaintext password that <B
11770 CLASS="COMMAND"
11771 >smbd</B
11772 > will accept when performing
11773                 UNIX password changing.</P
11774 ><P
11775 >See also <A
11776 HREF="#UNIXPASSWORDSYNC"
11777 ><TT
11778 CLASS="PARAMETER"
11779 ><I
11780 >unix
11781                 password sync</I
11782 ></TT
11783 ></A
11784 >, <A
11785 HREF="#PASSWDPROGRAM"
11786 >               <TT
11787 CLASS="PARAMETER"
11788 ><I
11789 >passwd program</I
11790 ></TT
11791 ></A
11792 > and <A
11793 HREF="#PASSWDCHATDEBUG"
11794 ><TT
11795 CLASS="PARAMETER"
11796 ><I
11797 >passwd chat debug</I
11798 ></TT
11799 >
11800                 </A
11801 >.</P
11802 ><P
11803 >Default: <B
11804 CLASS="COMMAND"
11805 >min password length = 5</B
11806 ></P
11807 ></DD
11808 ><DT
11809 ><A
11810 NAME="MINPRINTSPACE"
11811 ></A
11812 >min print space (S)</DT
11813 ><DD
11814 ><P
11815 >This sets the minimum amount of free disk
11816                 space that must be available before a user will be able to spool
11817                 a print job. It is specified in kilobytes. The default is 0, which
11818                 means a user can always spool a print job.</P
11819 ><P
11820 >See also the <A
11821 HREF="#PRINTING"
11822 ><TT
11823 CLASS="PARAMETER"
11824 ><I
11825 >printing
11826                 </I
11827 ></TT
11828 ></A
11829 > parameter.</P
11830 ><P
11831 >Default: <B
11832 CLASS="COMMAND"
11833 >min print space = 0</B
11834 ></P
11835 ><P
11836 >Example: <B
11837 CLASS="COMMAND"
11838 >min print space = 2000</B
11839 ></P
11840 ></DD
11841 ><DT
11842 ><A
11843 NAME="MINPROTOCOL"
11844 ></A
11845 >min protocol (G)</DT
11846 ><DD
11847 ><P
11848 >The value of the parameter (a string) is the
11849                 lowest SMB protocol dialect than Samba will support.  Please refer
11850                 to the <A
11851 HREF="#MAXPROTOCOL"
11852 ><TT
11853 CLASS="PARAMETER"
11854 ><I
11855 >max protocol</I
11856 ></TT
11857 ></A
11858 >
11859                 parameter for a list of valid protocol names and a brief description
11860                 of each.  You may also wish to refer to the C source code in
11861                 <TT
11862 CLASS="FILENAME"
11863 >source/smbd/negprot.c</TT
11864 > for a listing of known protocol
11865                 dialects supported by clients.</P
11866 ><P
11867 >If you are viewing this parameter as a security measure, you should
11868                 also refer to the <A
11869 HREF="#LANMANAUTH"
11870 ><TT
11871 CLASS="PARAMETER"
11872 ><I
11873 >lanman
11874                 auth</I
11875 ></TT
11876 ></A
11877 > parameter.  Otherwise, you should never need
11878                 to change this parameter.</P
11879 ><P
11880 >Default : <B
11881 CLASS="COMMAND"
11882 >min protocol = CORE</B
11883 ></P
11884 ><P
11885 >Example : <B
11886 CLASS="COMMAND"
11887 >min protocol = NT1</B
11888 >  # disable DOS
11889                 clients</P
11890 ></DD
11891 ><DT
11892 ><A
11893 NAME="MINWINSTTL"
11894 ></A
11895 >min wins ttl (G)</DT
11896 ><DD
11897 ><P
11898 >This option tells <A
11899 HREF="nmbd.8.html"
11900 TARGET="_top"
11901 >nmbd(8)</A
11902 >
11903                 when acting as a WINS server (<A
11904 HREF="#WINSSUPPORT"
11905 ><TT
11906 CLASS="PARAMETER"
11907 ><I
11908 >               wins support = yes</I
11909 ></TT
11910 ></A
11911 >) what the minimum 'time to live'
11912                 of NetBIOS names that <B
11913 CLASS="COMMAND"
11914 >nmbd</B
11915 > will grant will be (in
11916                 seconds). You should never need to change this parameter.  The default
11917                 is 6 hours (21600 seconds).</P
11918 ><P
11919 >Default: <B
11920 CLASS="COMMAND"
11921 >min wins ttl = 21600</B
11922 ></P
11923 ></DD
11924 ><DT
11925 ><A
11926 NAME="MSDFSROOT"
11927 ></A
11928 >msdfs root (S)</DT
11929 ><DD
11930 ><P
11931 >This boolean parameter is only available if
11932                 Samba is configured  and  compiled with the <B
11933 CLASS="COMMAND"
11934 >               --with-msdfs</B
11935 > option.  If set to <TT
11936 CLASS="CONSTANT"
11937 >yes&#62;</TT
11938 >,
11939                 Samba treats the share as a Dfs root and  allows clients to browse
11940                 the distributed file system tree rooted at the share directory.
11941                 Dfs links are specified  in  the share directory by symbolic
11942                 links of the form <TT
11943 CLASS="FILENAME"
11944 >msdfs:serverA\shareA,serverB\shareB
11945                 </TT
11946 > and so on.  For more information on setting up a Dfs tree
11947                 on Samba,  refer to <A
11948 HREF="msdfs_setup.html"
11949 TARGET="_top"
11950 >msdfs_setup.html
11951                 </A
11952 >.</P
11953 ><P
11954 >See also <A
11955 HREF="#HOSTMSDFS"
11956 ><TT
11957 CLASS="PARAMETER"
11958 ><I
11959 >host msdfs
11960                 </I
11961 ></TT
11962 ></A
11963 ></P
11964 ><P
11965 >Default: <B
11966 CLASS="COMMAND"
11967 >msdfs root = no</B
11968 ></P
11969 ></DD
11970 ><DT
11971 ><A
11972 NAME="NAMERESOLVEORDER"
11973 ></A
11974 >name resolve order (G)</DT
11975 ><DD
11976 ><P
11977 >This option is used by the programs in the Samba
11978                 suite to determine what naming services to use and in what order
11979                 to resolve host names to IP addresses. The option takes a space
11980                 separated string of name resolution options.</P
11981 ><P
11982 >The options are :"lmhosts", "host", "wins" and "bcast". They
11983                 cause names to be resolved as follows :</P
11984 ><P
11985 ></P
11986 ><UL
11987 ><LI
11988 ><P
11989 ><TT
11990 CLASS="CONSTANT"
11991 >lmhosts</TT
11992 > : Lookup an IP
11993                         address in the Samba lmhosts file. If the line in lmhosts has
11994                         no name type attached to the NetBIOS name (see the <A
11995 HREF="lmhosts.5.html"
11996 TARGET="_top"
11997 >lmhosts(5)</A
11998 > for details) then
11999                         any name type matches for lookup.</P
12000 ></LI
12001 ><LI
12002 ><P
12003 ><TT
12004 CLASS="CONSTANT"
12005 >host</TT
12006 > : Do a standard host
12007                         name to IP address resolution, using the system <TT
12008 CLASS="FILENAME"
12009 >/etc/hosts
12010                         </TT
12011 >, NIS, or DNS lookups. This method of name resolution
12012                         is operating system depended for instance on IRIX or Solaris this
12013                         may be controlled by the <TT
12014 CLASS="FILENAME"
12015 >/etc/nsswitch.conf</TT
12016 >
12017                         file).  Note that this method is only used if the NetBIOS name
12018                         type being queried is the 0x20 (server) name type, otherwise
12019                         it is ignored.</P
12020 ></LI
12021 ><LI
12022 ><P
12023 ><TT
12024 CLASS="CONSTANT"
12025 >wins</TT
12026 > : Query a name with
12027                         the IP address listed in the <A
12028 HREF="#WINSSERVER"
12029 ><TT
12030 CLASS="PARAMETER"
12031 ><I
12032 >                       wins server</I
12033 ></TT
12034 ></A
12035 > parameter.  If no WINS server has
12036                         been specified this method will be ignored.</P
12037 ></LI
12038 ><LI
12039 ><P
12040 ><TT
12041 CLASS="CONSTANT"
12042 >bcast</TT
12043 > : Do a broadcast on
12044                         each of the known local interfaces listed in the <A
12045 HREF="#INTERFACES"
12046 ><TT
12047 CLASS="PARAMETER"
12048 ><I
12049 >interfaces</I
12050 ></TT
12051 ></A
12052 >
12053                         parameter. This is the least reliable of the name resolution
12054                         methods as it depends on the target host being on a locally
12055                         connected subnet.</P
12056 ></LI
12057 ></UL
12058 ><P
12059 >Default: <B
12060 CLASS="COMMAND"
12061 >name resolve order = lmhosts host wins bcast
12062                 </B
12063 ></P
12064 ><P
12065 >Example: <B
12066 CLASS="COMMAND"
12067 >name resolve order = lmhosts bcast host
12068                 </B
12069 ></P
12070 ><P
12071 >This will cause the local lmhosts file to be examined
12072                 first, followed by a broadcast attempt, followed by a normal
12073                 system hostname lookup.</P
12074 ></DD
12075 ><DT
12076 ><A
12077 NAME="NETBIOSALIASES"
12078 ></A
12079 >netbios aliases (G)</DT
12080 ><DD
12081 ><P
12082 >This is a list of NetBIOS names that <A
12083 HREF="nmbd.8.html"
12084 TARGET="_top"
12085 >nmbd(8)</A
12086 > will advertise as additional
12087                 names by which the Samba server is known. This allows one machine
12088                 to appear in browse lists under multiple names. If a machine is
12089                 acting as a browse server or logon server none
12090                 of these names will be advertised as either browse server or logon
12091                 servers, only the primary name of the machine will be advertised
12092                 with these capabilities.</P
12093 ><P
12094 >See also <A
12095 HREF="#NETBIOSNAME"
12096 ><TT
12097 CLASS="PARAMETER"
12098 ><I
12099 >netbios
12100                 name</I
12101 ></TT
12102 ></A
12103 >.</P
12104 ><P
12105 >Default: <EM
12106 >empty string (no additional names)</EM
12107 ></P
12108 ><P
12109 >Example: <B
12110 CLASS="COMMAND"
12111 >netbios aliases = TEST TEST1 TEST2</B
12112 ></P
12113 ></DD
12114 ><DT
12115 ><A
12116 NAME="NETBIOSNAME"
12117 ></A
12118 >netbios name (G)</DT
12119 ><DD
12120 ><P
12121 >This sets the NetBIOS name by which a Samba
12122                 server is known. By default it is the same as the first component
12123                 of the host's DNS name. If a machine is a browse server or
12124                 logon server this name (or the first component
12125                 of the hosts DNS name) will be the name that these services are
12126                 advertised under.</P
12127 ><P
12128 >See also <A
12129 HREF="#NETBIOSALIASES"
12130 ><TT
12131 CLASS="PARAMETER"
12132 ><I
12133 >netbios
12134                 aliases</I
12135 ></TT
12136 ></A
12137 >.</P
12138 ><P
12139 >Default: <EM
12140 >machine DNS name</EM
12141 ></P
12142 ><P
12143 >Example: <B
12144 CLASS="COMMAND"
12145 >netbios name = MYNAME</B
12146 ></P
12147 ></DD
12148 ><DT
12149 ><A
12150 NAME="NETBIOSSCOPE"
12151 ></A
12152 >netbios scope (G)</DT
12153 ><DD
12154 ><P
12155 >This sets the NetBIOS scope that Samba will
12156                 operate under. This should not be set unless every machine
12157                 on your LAN also sets this value.</P
12158 ></DD
12159 ><DT
12160 ><A
12161 NAME="NISHOMEDIR"
12162 ></A
12163 >nis homedir (G)</DT
12164 ><DD
12165 ><P
12166 >Get the home share server from a NIS map. For
12167                 UNIX systems that use an automounter, the user's home directory
12168                 will often be mounted on a workstation on demand from a remote
12169                 server. </P
12170 ><P
12171 >When the Samba logon server is not the actual home directory
12172                 server, but is mounting the home directories via NFS then two
12173                 network hops would be required to access the users home directory
12174                 if the logon server told the client to use itself as the SMB server
12175                 for home directories (one over SMB and one over NFS). This can
12176                 be very slow.</P
12177 ><P
12178 >This option allows Samba to return the home share as
12179                 being on a different server to the logon server and as
12180                 long as a Samba daemon is running on the home directory server,
12181                 it will be mounted on the Samba client directly from the directory
12182                 server. When Samba is returning the home share to the client, it
12183                 will consult the NIS map specified in <A
12184 HREF="#HOMEDIRMAP"
12185 >               <TT
12186 CLASS="PARAMETER"
12187 ><I
12188 >homedir map</I
12189 ></TT
12190 ></A
12191 > and return the server
12192                 listed there.</P
12193 ><P
12194 >Note that for this option to work there must be a working
12195                 NIS system and the Samba server with this option must also
12196                 be a logon server.</P
12197 ><P
12198 >Default: <B
12199 CLASS="COMMAND"
12200 >nis homedir = no</B
12201 ></P
12202 ></DD
12203 ><DT
12204 ><A
12205 NAME="NTACLSUPPORT"
12206 ></A
12207 >nt acl support (G)</DT
12208 ><DD
12209 ><P
12210 >This boolean parameter controls whether
12211                 <A
12212 HREF="smbd.8.html"
12213 TARGET="_top"
12214 >smbd(8)</A
12215 > will attempt to map
12216                 UNIX permissions into Windows NT access control lists.</P
12217 ><P
12218 >Default: <B
12219 CLASS="COMMAND"
12220 >nt acl support = yes</B
12221 ></P
12222 ></DD
12223 ><DT
12224 ><A
12225 NAME="NTPIPESUPPORT"
12226 ></A
12227 >nt pipe support (G)</DT
12228 ><DD
12229 ><P
12230 >This boolean parameter controls whether
12231                 <A
12232 HREF="smbd.8.html"
12233 TARGET="_top"
12234 >smbd(8)</A
12235 > will allow Windows NT
12236                 clients to connect to the NT SMB specific <TT
12237 CLASS="CONSTANT"
12238 >IPC$</TT
12239 >
12240                 pipes. This is a developer debugging option and can be left
12241                 alone.</P
12242 ><P
12243 >Default: <B
12244 CLASS="COMMAND"
12245 >nt pipe support = yes</B
12246 ></P
12247 ></DD
12248 ><DT
12249 ><A
12250 NAME="NTSMBSUPPORT"
12251 ></A
12252 >nt smb support (G)</DT
12253 ><DD
12254 ><P
12255 >This boolean parameter controls whether <A
12256 HREF="smbd.8.html"
12257 TARGET="_top"
12258 >smbd(8)</A
12259 > will negotiate NT specific SMB
12260                 support with Windows NT clients. Although this is a developer
12261                 debugging option and should be left alone, benchmarking has discovered
12262                 that Windows NT clients give faster performance with this option
12263                 set to <TT
12264 CLASS="CONSTANT"
12265 >no</TT
12266 >. This is still being investigated.
12267                 If this option is set to <TT
12268 CLASS="CONSTANT"
12269 >no</TT
12270 > then Samba offers
12271                 exactly the same SMB calls that versions prior to Samba 2.0 offered.
12272                 This information may be of use if any users are having problems
12273                 with NT SMB support.</P
12274 ><P
12275 >You should not need to ever disable this parameter.</P
12276 ><P
12277 >Default: <B
12278 CLASS="COMMAND"
12279 >nt smb support = yes</B
12280 ></P
12281 ></DD
12282 ><DT
12283 ><A
12284 NAME="NULLPASSWORDS"
12285 ></A
12286 >null passwords (G)</DT
12287 ><DD
12288 ><P
12289 >Allow or disallow client access to accounts
12290                 that have null passwords. </P
12291 ><P
12292 >See also <A
12293 HREF="smbpasswd.5.html"
12294 TARGET="_top"
12295 >smbpasswd (5)</A
12296 >.</P
12297 ><P
12298 >Default: <B
12299 CLASS="COMMAND"
12300 >null passwords = no</B
12301 ></P
12302 ></DD
12303 ><DT
12304 ><A
12305 NAME="OBEYPAMRESTRICTIONS"
12306 ></A
12307 >obey pam restrictions (G)</DT
12308 ><DD
12309 ><P
12310 >When Samba 2.2 is configured to enable PAM support
12311                 (i.e. --with-pam), this parameter will control whether or not Samba
12312                 should obey PAM's account and session management directives.  The
12313                 default behavior is to use PAM for clear text authentication only
12314                 and to ignore any account or session management.  Note that Samba
12315                 always ignores PAM for authentication in the case of <A
12316 HREF="#ENCRYPTPASSWORDS"
12317 ><TT
12318 CLASS="PARAMETER"
12319 ><I
12320 >encrypt passwords = yes</I
12321 ></TT
12322 >
12323                 </A
12324 >.  The reason is that PAM modules cannot support the challenge/response
12325                 authentication mechanism needed in the presence of SMB password encryption.
12326                 </P
12327 ><P
12328 >Default: <B
12329 CLASS="COMMAND"
12330 >obey pam restrictions = no</B
12331 ></P
12332 ></DD
12333 ><DT
12334 ><A
12335 NAME="ONLYUSER"
12336 ></A
12337 >only user (S)</DT
12338 ><DD
12339 ><P
12340 >This is a boolean option that controls whether
12341                 connections with usernames not in the <TT
12342 CLASS="PARAMETER"
12343 ><I
12344 >user</I
12345 ></TT
12346 >
12347                 list will be allowed. By default this option is disabled so that a
12348                 client can supply a username to be used by the server.  Enabling
12349                 this parameter will force the server to only user the login
12350                 names from the <TT
12351 CLASS="PARAMETER"
12352 ><I
12353 >user</I
12354 ></TT
12355 > list and is only really
12356                 useful in <A
12357 HREF="#SECURITYEQUALSSHARE"
12358 >shave level</A
12359 >
12360                 security.</P
12361 ><P
12362 >Note that this also means Samba won't try to deduce
12363                 usernames from the service name. This can be annoying for
12364                 the [homes] section. To get around this you could use <B
12365 CLASS="COMMAND"
12366 >user =
12367                 %S</B
12368 > which means your <TT
12369 CLASS="PARAMETER"
12370 ><I
12371 >user</I
12372 ></TT
12373 > list
12374                 will be just the service name, which for home directories is the
12375                 name of the user.</P
12376 ><P
12377 >See also the <A
12378 HREF="#USER"
12379 ><TT
12380 CLASS="PARAMETER"
12381 ><I
12382 >user</I
12383 ></TT
12384 >
12385                 </A
12386 > parameter.</P
12387 ><P
12388 >Default: <B
12389 CLASS="COMMAND"
12390 >only user = no</B
12391 ></P
12392 ></DD
12393 ><DT
12394 ><A
12395 NAME="ONLYGUEST"
12396 ></A
12397 >only guest (S)</DT
12398 ><DD
12399 ><P
12400 >A synonym for <A
12401 HREF="#GUESTONLY"
12402 ><TT
12403 CLASS="PARAMETER"
12404 ><I
12405 >               guest only</I
12406 ></TT
12407 ></A
12408 >.</P
12409 ></DD
12410 ><DT
12411 ><A
12412 NAME="OPLOCKBREAKWAITTIME"
12413 ></A
12414 >oplock break wait time (G)</DT
12415 ><DD
12416 ><P
12417 >This is a tuning parameter added due to bugs in
12418                 both Windows 9x and WinNT. If Samba responds to a client too
12419                 quickly when that client issues an SMB that can cause an oplock
12420                 break request, then the network client can fail and not respond
12421                 to the break request. This tuning parameter (which is set in milliseconds)
12422                 is the amount of time Samba will wait before sending an oplock break
12423                 request to such (broken) clients.</P
12424 ><P
12425 ><EM
12426 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
12427                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
12428 >.</P
12429 ><P
12430 >Default: <B
12431 CLASS="COMMAND"
12432 >oplock break wait time = 0</B
12433 ></P
12434 ></DD
12435 ><DT
12436 ><A
12437 NAME="OPLOCKCONTENTIONLIMIT"
12438 ></A
12439 >oplock contention limit (S)</DT
12440 ><DD
12441 ><P
12442 >This is a <EM
12443 >very</EM
12444 > advanced
12445                 <A
12446 HREF="smbd.8.html"
12447 TARGET="_top"
12448 >smbd(8)</A
12449 > tuning option to
12450                 improve the efficiency of the granting of oplocks under multiple
12451                 client contention for the same file.</P
12452 ><P
12453 >In brief it specifies a number, which causes <A
12454 HREF="smbd.8.html"
12455 TARGET="_top"
12456 >smbd</A
12457 > not to
12458                 grant an oplock even when requested if the approximate number of
12459                 clients contending for an oplock on the same file goes over this
12460                 limit. This causes <B
12461 CLASS="COMMAND"
12462 >smbd</B
12463 > to behave in a similar
12464                 way to Windows NT.</P
12465 ><P
12466 ><EM
12467 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
12468                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
12469 >.</P
12470 ><P
12471 >Default: <B
12472 CLASS="COMMAND"
12473 >oplock contention limit = 2</B
12474 ></P
12475 ></DD
12476 ><DT
12477 ><A
12478 NAME="OPLOCKS"
12479 ></A
12480 >oplocks (S)</DT
12481 ><DD
12482 ><P
12483 >This boolean option tells <B
12484 CLASS="COMMAND"
12485 >smbd</B
12486 > whether to
12487                 issue oplocks (opportunistic locks) to file open requests on this
12488                 share. The oplock code can dramatically (approx. 30% or more) improve
12489                 the speed of access to files on Samba servers. It allows the clients
12490                 to aggressively cache files locally and you may want to disable this
12491                 option for unreliable network environments (it is turned on by
12492                 default in Windows NT Servers).  For more information see the file
12493                 <TT
12494 CLASS="FILENAME"
12495 >Speed.txt</TT
12496 > in the Samba <TT
12497 CLASS="FILENAME"
12498 >docs/</TT
12499 >
12500                 directory.</P
12501 ><P
12502 >Oplocks may be selectively turned off on certain files with a
12503                 share. See the <A
12504 HREF="#VETOOPLOCKFILES"
12505 ><TT
12506 CLASS="PARAMETER"
12507 ><I
12508 >               veto oplock files</I
12509 ></TT
12510 ></A
12511 > parameter. On some systems
12512                 oplocks are recognized by the underlying operating system. This
12513                 allows data synchronization between all access to oplocked files,
12514                 whether it be via Samba or NFS or a local UNIX process. See the
12515                 <TT
12516 CLASS="PARAMETER"
12517 ><I
12518 >kernel oplocks</I
12519 ></TT
12520 > parameter for details.</P
12521 ><P
12522 >See also the <A
12523 HREF="#KERNELOPLOCKS"
12524 ><TT
12525 CLASS="PARAMETER"
12526 ><I
12527 >kernel
12528                 oplocks</I
12529 ></TT
12530 ></A
12531 > and <A
12532 HREF="#LEVEL2OPLOCKS"
12533 ><TT
12534 CLASS="PARAMETER"
12535 ><I
12536 >               level2 oplocks</I
12537 ></TT
12538 ></A
12539 > parameters.</P
12540 ><P
12541 >Default: <B
12542 CLASS="COMMAND"
12543 >oplocks = yes</B
12544 ></P
12545 ></DD
12546 ><DT
12547 ><A
12548 NAME="OSLEVEL"
12549 ></A
12550 >os level (G)</DT
12551 ><DD
12552 ><P
12553 >This integer value controls what level Samba
12554                 advertises itself as for browse elections. The value of this
12555                 parameter determines whether <A
12556 HREF="nmbd.8.html"
12557 TARGET="_top"
12558 >nmbd(8)</A
12559 >
12560                 has a chance of becoming a local master browser for the <TT
12561 CLASS="PARAMETER"
12562 ><I
12563 >               WORKGROUP</I
12564 ></TT
12565 > in the local broadcast area.</P
12566 ><P
12567 ><EM
12568 >Note :</EM
12569 >By default, Samba will win
12570                 a local master browsing election over all Microsoft operating
12571                 systems except a Windows NT 4.0/2000 Domain Controller.  This
12572                 means that a misconfigured Samba host can effectively isolate
12573                 a subnet for browsing purposes.  See <TT
12574 CLASS="FILENAME"
12575 >BROWSING.txt
12576                 </TT
12577 > in the Samba <TT
12578 CLASS="FILENAME"
12579 >docs/</TT
12580 > directory
12581                 for details.</P
12582 ><P
12583 >Default: <B
12584 CLASS="COMMAND"
12585 >os level = 20</B
12586 ></P
12587 ><P
12588 >Example: <B
12589 CLASS="COMMAND"
12590 >os level = 65 </B
12591 ></P
12592 ></DD
12593 ><DT
12594 ><A
12595 NAME="OS2DRIVERMAP"
12596 ></A
12597 >os2 driver map (G)</DT
12598 ><DD
12599 ><P
12600 >The parameter is used to define the absolute
12601                 path to a file containing a mapping of Windows NT printer driver
12602                 names to OS/2 printer driver names.  The format is:</P
12603 ><P
12604 >&#60;nt driver name&#62; = &#60;os2 driver
12605                 name&#62;.&#60;device name&#62;</P
12606 ><P
12607 >For example, a valid entry using the HP LaserJet 5
12608                 printer driver would appear as <B
12609 CLASS="COMMAND"
12610 >HP LaserJet 5L = LASERJET.HP
12611                 LaserJet 5L</B
12612 >.</P
12613 ><P
12614 >The need for the file is due to the printer driver namespace
12615                 problem described in the <A
12616 HREF="printer_driver2.html"
12617 TARGET="_top"
12618 >Samba
12619                 Printing HOWTO</A
12620 >.  For more details on OS/2 clients, please
12621                 refer to the <A
12622 HREF="OS2-Client-HOWTO.html"
12623 TARGET="_top"
12624 >OS2-Client-HOWTO
12625                 </A
12626 > containing in the Samba documentation.</P
12627 ><P
12628 >Default: <B
12629 CLASS="COMMAND"
12630 >os2 driver map = &#60;empty string&#62;
12631                 </B
12632 ></P
12633 ></DD
12634 ><DT
12635 ><A
12636 NAME="PAMPASSWORDCHANGE"
12637 ></A
12638 >pam password change (G)</DT
12639 ><DD
12640 ><P
12641 >With the addition of better PAM support in Samba 2.2,
12642                 this parameter, it is possible to use PAM's password change control
12643                 flag for Samba.  If enabled, then PAM will be used for password
12644                 changes when requested by an SMB client insted of the program listed in
12645                 <A
12646 HREF="#PASSWDPROGRAM"
12647 ><TT
12648 CLASS="PARAMETER"
12649 ><I
12650 >passwd program</I
12651 ></TT
12652 ></A
12653 >.
12654                 It should be possible to enable this without changing your
12655                 <A
12656 HREF="#PASSWDCHAT"
12657 ><TT
12658 CLASS="PARAMETER"
12659 ><I
12660 >passwd chat</I
12661 ></TT
12662 ></A
12663 >
12664                 paramater for most setups.
12665                 </P
12666 ><P
12667 >Default: <B
12668 CLASS="COMMAND"
12669 >pam password change = no</B
12670 ></P
12671 ></DD
12672 ><DT
12673 ><A
12674 NAME="PANICACTION"
12675 ></A
12676 >panic action (G)</DT
12677 ><DD
12678 ><P
12679 >This is a Samba developer option that allows a
12680                 system command to be called when either <A
12681 HREF="smbd.8.html"
12682 TARGET="_top"
12683 >               smbd(8)</A
12684 > or <A
12685 HREF="nmbd.8.html"
12686 TARGET="_top"
12687 >nmbd(8)</A
12688 >
12689                 crashes. This is usually used to draw attention to the fact that
12690                 a problem occurred.</P
12691 ><P
12692 >Default: <B
12693 CLASS="COMMAND"
12694 >panic action = &#60;empty string&#62;</B
12695 ></P
12696 ><P
12697 >Example: <B
12698 CLASS="COMMAND"
12699 >panic action = "/bin/sleep 90000"</B
12700 ></P
12701 ></DD
12702 ><DT
12703 ><A
12704 NAME="PASSWDCHAT"
12705 ></A
12706 >passwd chat (G)</DT
12707 ><DD
12708 ><P
12709 >This string controls the <EM
12710 >"chat"</EM
12711 >
12712                 conversation that takes places between <A
12713 HREF="smbd.8.html"
12714 TARGET="_top"
12715 >smbd</A
12716 > and the local password changing
12717                 program to change the user's password. The string describes a
12718                 sequence of response-receive pairs that <A
12719 HREF="smbd.8.html"
12720 TARGET="_top"
12721 >               smbd(8)</A
12722 > uses to determine what to send to the
12723                 <A
12724 HREF="#PASSWDPROGRAM"
12725 ><TT
12726 CLASS="PARAMETER"
12727 ><I
12728 >passwd program</I
12729 ></TT
12730 >
12731                 </A
12732 > and what to expect back. If the expected output is not
12733                 received then the password is not changed.</P
12734 ><P
12735 >This chat sequence is often quite site specific, depending
12736                 on what local methods are used for password control (such as NIS
12737                 etc).</P
12738 ><P
12739 >The string can contain the macros <TT
12740 CLASS="PARAMETER"
12741 ><I
12742 >%o</I
12743 ></TT
12744 >
12745                 and <TT
12746 CLASS="PARAMETER"
12747 ><I
12748 >%n</I
12749 ></TT
12750 > which are substituted for the old
12751                 and new passwords respectively. It can also contain the standard
12752                 macros <TT
12753 CLASS="CONSTANT"
12754 >\n</TT
12755 >, <TT
12756 CLASS="CONSTANT"
12757 >\r</TT
12758 >, <TT
12759 CLASS="CONSTANT"
12760 >               \t</TT
12761 > and <TT
12762 CLASS="CONSTANT"
12763 >%s</TT
12764 > to give line-feed,
12765                 carriage-return, tab and space.</P
12766 ><P
12767 >The string can also contain a '*' which matches
12768                 any sequence of characters.</P
12769 ><P
12770 >Double quotes can be used to collect strings with spaces
12771                 in them into a single string.</P
12772 ><P
12773 >If the send string in any part of the chat sequence
12774                 is a full stop ".",  then no string is sent. Similarly,
12775                 if the expect string is a full stop then no string is expected.</P
12776 ><P
12777 >Note that if the <A
12778 HREF="#UNIXPASSWORDSYNC"
12779 ><TT
12780 CLASS="PARAMETER"
12781 ><I
12782 >unix
12783                 password sync</I
12784 ></TT
12785 ></A
12786 > parameter is set to <TT
12787 CLASS="CONSTANT"
12788 >true</TT
12789 >, then this
12790                 sequence is called <EM
12791 >AS ROOT</EM
12792 > when the SMB password
12793                 in the smbpasswd file is being changed, without access to the old
12794                 password cleartext. In this case the old password cleartext is set
12795                 to "" (the empty string).</P
12796 ><P
12797 >Also, if the <A
12798 HREF="#PAMPASSWORDCHANGE"
12799 ><TT
12800 CLASS="PARAMETER"
12801 ><I
12802 >pam
12803                 password change</I
12804 ></TT
12805 ></A
12806 > parameter is set to true, the chat pairs
12807                 may be matched in any order, and sucess is determined by the PAM result,
12808                 not any particular output. The \n macro is ignored for PAM conversions.
12809                 </P
12810 ><P
12811 >See also <A
12812 HREF="#UNIXPASSWORDSYNC"
12813 ><TT
12814 CLASS="PARAMETER"
12815 ><I
12816 >unix password
12817                 sync</I
12818 ></TT
12819 ></A
12820 >, <A
12821 HREF="#PASSWDPROGRAM"
12822 ><TT
12823 CLASS="PARAMETER"
12824 ><I
12825 >               passwd program</I
12826 ></TT
12827 ></A
12828 > ,<A
12829 HREF="#PASSWDCHATDEBUG"
12830 >               <TT
12831 CLASS="PARAMETER"
12832 ><I
12833 >passwd chat debug</I
12834 ></TT
12835 ></A
12836 > and <A
12837 HREF="#PAMPASSWORDCHANGE"
12838 >               <TT
12839 CLASS="PARAMETER"
12840 ><I
12841 >pam password change</I
12842 ></TT
12843 ></A
12844 >.</P
12845 ><P
12846 >Default: <B
12847 CLASS="COMMAND"
12848 >passwd chat = *new*password* %n\n
12849                 *new*password* %n\n *changed*</B
12850 ></P
12851 ><P
12852 >Example: <B
12853 CLASS="COMMAND"
12854 >passwd chat = "*Enter OLD password*" %o\n
12855                 "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password
12856                 changed*"</B
12857 ></P
12858 ></DD
12859 ><DT
12860 ><A
12861 NAME="PASSWDCHATDEBUG"
12862 ></A
12863 >passwd chat debug (G)</DT
12864 ><DD
12865 ><P
12866 >This boolean specifies if the passwd chat script
12867                 parameter is run in <EM
12868 >debug</EM
12869 > mode. In this mode the
12870                 strings passed to and received from the passwd chat are printed
12871                 in the <A
12872 HREF="smbd.8.html"
12873 TARGET="_top"
12874 >smbd(8)</A
12875 > log with a
12876                 <A
12877 HREF="#DEBUGLEVEL"
12878 ><TT
12879 CLASS="PARAMETER"
12880 ><I
12881 >debug level</I
12882 ></TT
12883 ></A
12884 >
12885                 of 100. This is a dangerous option as it will allow plaintext passwords
12886                 to be seen in the <B
12887 CLASS="COMMAND"
12888 >smbd</B
12889 > log. It is available to help
12890                 Samba admins debug their <TT
12891 CLASS="PARAMETER"
12892 ><I
12893 >passwd chat</I
12894 ></TT
12895 > scripts
12896                 when calling the <TT
12897 CLASS="PARAMETER"
12898 ><I
12899 >passwd program</I
12900 ></TT
12901 > and should
12902                 be turned off after this has been done. This option has no effect if the
12903                 <A
12904 HREF="#PAMPASSWORDCHANGE"
12905 ><TT
12906 CLASS="PARAMETER"
12907 ><I
12908 >pam password change</I
12909 ></TT
12910 ></A
12911 >
12912                 paramter is set. This parameter is off by default.</P
12913 ><P
12914 >See also <A
12915 HREF="#PASSWDCHAT"
12916 ><TT
12917 CLASS="PARAMETER"
12918 ><I
12919 >passwd chat</I
12920 ></TT
12921 >
12922                 </A
12923 >, <A
12924 HREF="#PAMPASSWORDCHANGE"
12925 ><TT
12926 CLASS="PARAMETER"
12927 ><I
12928 >pam password change</I
12929 ></TT
12930 >
12931                 </A
12932 >, <A
12933 HREF="#PASSWDPROGRAM"
12934 ><TT
12935 CLASS="PARAMETER"
12936 ><I
12937 >passwd program</I
12938 ></TT
12939 >
12940                 </A
12941 >.</P
12942 ><P
12943 >Default: <B
12944 CLASS="COMMAND"
12945 >passwd chat debug = no</B
12946 ></P
12947 ></DD
12948 ><DT
12949 ><A
12950 NAME="PASSWDPROGRAM"
12951 ></A
12952 >passwd program (G)</DT
12953 ><DD
12954 ><P
12955 >The name of a program that can be used to set
12956                 UNIX user passwords.  Any occurrences of <TT
12957 CLASS="PARAMETER"
12958 ><I
12959 >%u</I
12960 ></TT
12961 >
12962                 will be replaced with the user name. The user name is checked for
12963                 existence before calling the password changing program.</P
12964 ><P
12965 >Also note that many passwd programs insist in <EM
12966 >reasonable
12967                 </EM
12968 > passwords, such as a minimum length, or the inclusion
12969                 of mixed case chars and digits. This can pose a problem as some clients
12970                 (such as Windows for Workgroups) uppercase the password before sending
12971                 it.</P
12972 ><P
12973 ><EM
12974 >Note</EM
12975 > that if the <TT
12976 CLASS="PARAMETER"
12977 ><I
12978 >unix
12979                 password sync</I
12980 ></TT
12981 > parameter is set to <TT
12982 CLASS="CONSTANT"
12983 >true
12984                 </TT
12985 > then this program is called <EM
12986 >AS ROOT</EM
12987 >
12988                 before the SMB password in the <A
12989 HREF="smbpasswd.5.html"
12990 TARGET="_top"
12991 >smbpasswd(5)
12992                 </A
12993 > file is changed. If this UNIX password change fails, then
12994                 <B
12995 CLASS="COMMAND"
12996 >smbd</B
12997 > will fail to change the SMB password also
12998                 (this is by design).</P
12999 ><P
13000 >If the <TT
13001 CLASS="PARAMETER"
13002 ><I
13003 >unix password sync</I
13004 ></TT
13005 > parameter
13006                 is set this parameter <EM
13007 >MUST USE ABSOLUTE PATHS</EM
13008 >
13009                 for <EM
13010 >ALL</EM
13011 > programs called, and must be examined
13012                 for security implications. Note that by default <TT
13013 CLASS="PARAMETER"
13014 ><I
13015 >unix
13016                 password sync</I
13017 ></TT
13018 > is set to <TT
13019 CLASS="CONSTANT"
13020 >false</TT
13021 >.</P
13022 ><P
13023 >See also <A
13024 HREF="#UNIXPASSWORDSYNC"
13025 ><TT
13026 CLASS="PARAMETER"
13027 ><I
13028 >unix
13029                 password sync</I
13030 ></TT
13031 ></A
13032 >.</P
13033 ><P
13034 >Default: <B
13035 CLASS="COMMAND"
13036 >passwd program = /bin/passwd</B
13037 ></P
13038 ><P
13039 >Example: <B
13040 CLASS="COMMAND"
13041 >passwd program = /sbin/npasswd %u</B
13042 >
13043                 </P
13044 ></DD
13045 ><DT
13046 ><A
13047 NAME="PASSWORDLEVEL"
13048 ></A
13049 >password level (G)</DT
13050 ><DD
13051 ><P
13052 >Some client/server combinations have difficulty
13053                 with mixed-case passwords.  One offending client is Windows for
13054                 Workgroups, which for some reason forces passwords to upper
13055                 case when using the LANMAN1 protocol, but leaves them alone when
13056                 using COREPLUS!  Another problem child is the Windows 95/98
13057                 family of operating systems.  These clients upper case clear
13058                 text passwords even when NT LM 0.12 selected by the protocol
13059                 negotiation request/response.</P
13060 ><P
13061 >This parameter defines the maximum number of characters
13062                 that may be upper case in passwords.</P
13063 ><P
13064 >For example, say the password given was "FRED". If <TT
13065 CLASS="PARAMETER"
13066 ><I
13067 >               password level</I
13068 ></TT
13069 > is set to 1, the following combinations
13070                 would be tried if "FRED" failed:</P
13071 ><P
13072 >"Fred", "fred", "fRed", "frEd","freD"</P
13073 ><P
13074 >If <TT
13075 CLASS="PARAMETER"
13076 ><I
13077 >password level</I
13078 ></TT
13079 > was set to 2,
13080                 the following combinations would also be tried: </P
13081 ><P
13082 >"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</P
13083 ><P
13084 >And so on.</P
13085 ><P
13086 >The higher value this parameter is set to the more likely
13087                 it is that a mixed case password will be matched against a single
13088                 case password. However, you should be aware that use of this
13089                 parameter reduces security and increases the time taken to
13090                 process a new connection.</P
13091 ><P
13092 >A value of zero will cause only two attempts to be
13093                 made - the password as is and the password in all-lower case.</P
13094 ><P
13095 >Default: <B
13096 CLASS="COMMAND"
13097 >password level = 0</B
13098 ></P
13099 ><P
13100 >Example: <B
13101 CLASS="COMMAND"
13102 >password level = 4</B
13103 ></P
13104 ></DD
13105 ><DT
13106 ><A
13107 NAME="PASSWORDSERVER"
13108 ></A
13109 >password server (G)</DT
13110 ><DD
13111 ><P
13112 >By specifying the name of another SMB server (such
13113                 as a WinNT box) with this option, and using <B
13114 CLASS="COMMAND"
13115 >security = domain
13116                 </B
13117 > or <B
13118 CLASS="COMMAND"
13119 >security = server</B
13120 > you can get Samba
13121                 to do all its username/password validation via a remote server.</P
13122 ><P
13123 >This option sets the name of the password server to use.
13124                 It must be a NetBIOS name, so if the machine's NetBIOS name is
13125                 different from its Internet name then you may have to add its NetBIOS
13126                 name to the lmhosts  file which is stored in the same directory
13127                 as the <TT
13128 CLASS="FILENAME"
13129 >smb.conf</TT
13130 > file.</P
13131 ><P
13132 >The name of the password server is looked up using the
13133                 parameter <A
13134 HREF="#NAMERESOLVEORDER"
13135 ><TT
13136 CLASS="PARAMETER"
13137 ><I
13138 >name
13139                 resolve order</I
13140 ></TT
13141 ></A
13142 > and so may resolved
13143                 by any method and order described in that parameter.</P
13144 ><P
13145 >The password server much be a machine capable of using
13146                 the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in
13147                 user level security mode.</P
13148 ><P
13149 ><EM
13150 >NOTE:</EM
13151 > Using a password server
13152                 means your UNIX box (running Samba) is only as secure as your
13153                 password server. <EM
13154 >DO NOT CHOOSE A PASSWORD SERVER THAT
13155                 YOU DON'T COMPLETELY TRUST</EM
13156 >.</P
13157 ><P
13158 >Never point a Samba server at itself for password
13159                 serving. This will cause a loop and could lock up your Samba
13160                 server!</P
13161 ><P
13162 >The name of the password server takes the standard
13163                 substitutions, but probably the only useful one is <TT
13164 CLASS="PARAMETER"
13165 ><I
13166 >%m
13167                 </I
13168 ></TT
13169 >, which means the Samba server will use the incoming
13170                 client as the password server. If you use this then you better
13171                 trust your clients, and you had better restrict them with hosts allow!</P
13172 ><P
13173 >If the <TT
13174 CLASS="PARAMETER"
13175 ><I
13176 >security</I
13177 ></TT
13178 > parameter is set to
13179                 <TT
13180 CLASS="CONSTANT"
13181 >domain</TT
13182 >, then the list of machines in this
13183                 option must be a list of Primary or Backup Domain controllers for the
13184                 Domain or the character '*', as the Samba server is effectively
13185                 in that domain, and will use cryptographically authenticated RPC calls
13186                 to authenticate the user logging on. The advantage of using <B
13187 CLASS="COMMAND"
13188 >               security = domain</B
13189 > is that if you list several hosts in the
13190                 <TT
13191 CLASS="PARAMETER"
13192 ><I
13193 >password server</I
13194 ></TT
13195 > option then <B
13196 CLASS="COMMAND"
13197 >smbd
13198                 </B
13199 > will try each in turn till it finds one that responds. This
13200                 is useful in case your primary server goes down.</P
13201 ><P
13202 >If the <TT
13203 CLASS="PARAMETER"
13204 ><I
13205 >password server</I
13206 ></TT
13207 > option is set
13208                 to the character '*', then Samba will attempt to auto-locate the
13209                 Primary or Backup Domain controllers to authenticate against by
13210                 doing a query for the name <TT
13211 CLASS="CONSTANT"
13212 >WORKGROUP&#60;1C&#62;</TT
13213 >
13214                 and then contacting each server returned in the list of IP
13215                 addresses from the name resolution source. </P
13216 ><P
13217 >If the <TT
13218 CLASS="PARAMETER"
13219 ><I
13220 >security</I
13221 ></TT
13222 > parameter is
13223                 set to <TT
13224 CLASS="CONSTANT"
13225 >server</TT
13226 >, then there are different
13227                 restrictions that <B
13228 CLASS="COMMAND"
13229 >security = domain</B
13230 > doesn't
13231                 suffer from:</P
13232 ><P
13233 ></P
13234 ><UL
13235 ><LI
13236 ><P
13237 >You may list several password servers in
13238                         the <TT
13239 CLASS="PARAMETER"
13240 ><I
13241 >password server</I
13242 ></TT
13243 > parameter, however if an
13244                         <B
13245 CLASS="COMMAND"
13246 >smbd</B
13247 > makes a connection to a password server,
13248                         and then the password server fails, no more users will be able
13249                         to be authenticated from this <B
13250 CLASS="COMMAND"
13251 >smbd</B
13252 >.  This is a
13253                         restriction of the SMB/CIFS protocol when in <B
13254 CLASS="COMMAND"
13255 >security = server
13256                         </B
13257 > mode and cannot be fixed in Samba.</P
13258 ></LI
13259 ><LI
13260 ><P
13261 >If you are using a Windows NT server as your
13262                         password server then you will have to ensure that your users
13263                         are able to login from the Samba server, as when in <B
13264 CLASS="COMMAND"
13265 >                       security = server</B
13266 >  mode the network logon will appear to
13267                         come from there rather than from the users workstation.</P
13268 ></LI
13269 ></UL
13270 ><P
13271 >See also the <A
13272 HREF="#SECURITY"
13273 ><TT
13274 CLASS="PARAMETER"
13275 ><I
13276 >security
13277                 </I
13278 ></TT
13279 ></A
13280 > parameter.</P
13281 ><P
13282 >Default: <B
13283 CLASS="COMMAND"
13284 >password server = &#60;empty string&#62;</B
13285 >
13286                 </P
13287 ><P
13288 >Example: <B
13289 CLASS="COMMAND"
13290 >password server = NT-PDC, NT-BDC1, NT-BDC2
13291                 </B
13292 ></P
13293 ><P
13294 >Example: <B
13295 CLASS="COMMAND"
13296 >password server = *</B
13297 ></P
13298 ></DD
13299 ><DT
13300 ><A
13301 NAME="PATH"
13302 ></A
13303 >path (S)</DT
13304 ><DD
13305 ><P
13306 >This parameter specifies a directory to which
13307                 the user of the service is to be given access. In the case of
13308                 printable services, this is where print data will spool prior to
13309                 being submitted to the host for printing.</P
13310 ><P
13311 >For a printable service offering guest access, the service
13312                 should be readonly and the path should be world-writeable and
13313                 have the sticky bit set. This is not mandatory of course, but
13314                 you probably won't get the results you expect if you do
13315                 otherwise.</P
13316 ><P
13317 >Any occurrences of <TT
13318 CLASS="PARAMETER"
13319 ><I
13320 >%u</I
13321 ></TT
13322 > in the path
13323                 will be replaced with the UNIX username that the client is using
13324                 on this connection. Any occurrences of <TT
13325 CLASS="PARAMETER"
13326 ><I
13327 >%m</I
13328 ></TT
13329 >
13330                 will be replaced by the NetBIOS name of the machine they are
13331                 connecting from. These replacements are very useful for setting
13332                 up pseudo home directories for users.</P
13333 ><P
13334 >Note that this path will be based on <A
13335 HREF="#ROOTDIR"
13336 >               <TT
13337 CLASS="PARAMETER"
13338 ><I
13339 >root dir</I
13340 ></TT
13341 ></A
13342 > if one was specified.</P
13343 ><P
13344 >Default: <EM
13345 >none</EM
13346 ></P
13347 ><P
13348 >Example: <B
13349 CLASS="COMMAND"
13350 >path = /home/fred</B
13351 ></P
13352 ></DD
13353 ><DT
13354 ><A
13355 NAME="POSIXLOCKING"
13356 ></A
13357 >posix locking (S)</DT
13358 ><DD
13359 ><P
13360 >The <A
13361 HREF="smbd.8.html"
13362 TARGET="_top"
13363 ><B
13364 CLASS="COMMAND"
13365 >smbd(8)</B
13366 ></A
13367 >
13368                 daemon maintains an database of file locks obtained by SMB clients.
13369                 The default behavior is to map this internal database to POSIX
13370                 locks.  This means that file locks obtained by SMB clients are
13371                 consistent with those seen by POSIX compliant applications accessing
13372                 the files via a non-SMB method (e.g. NFS or local file access).
13373                 You should never need to disable this parameter.</P
13374 ><P
13375 >Default: <B
13376 CLASS="COMMAND"
13377 >posix locking = yes</B
13378 ></P
13379 ></DD
13380 ><DT
13381 ><A
13382 NAME="POSTEXEC"
13383 ></A
13384 >postexec (S)</DT
13385 ><DD
13386 ><P
13387 >This option specifies a command to be run
13388                 whenever the service is disconnected. It takes the usual
13389                 substitutions. The command may be run as the root on some
13390                 systems.</P
13391 ><P
13392 >An interesting example may be to unmount server
13393                 resources:</P
13394 ><P
13395 ><B
13396 CLASS="COMMAND"
13397 >postexec = /etc/umount /cdrom</B
13398 ></P
13399 ><P
13400 >See also <A
13401 HREF="#PREEXEC"
13402 ><TT
13403 CLASS="PARAMETER"
13404 ><I
13405 >preexec</I
13406 ></TT
13407 >
13408                 </A
13409 >.</P
13410 ><P
13411 >Default: <EM
13412 >none (no command executed)</EM
13413 >
13414                 </P
13415 ><P
13416 >Example: <B
13417 CLASS="COMMAND"
13418 >postexec = echo \"%u disconnected from %S
13419                 from %m (%I)\" &#62;&#62; /tmp/log</B
13420 ></P
13421 ></DD
13422 ><DT
13423 ><A
13424 NAME="POSTSCRIPT"
13425 ></A
13426 >postscript (S)</DT
13427 ><DD
13428 ><P
13429 >This parameter forces a printer to interpret
13430                 the print files as PostScript. This is done by adding a <TT
13431 CLASS="CONSTANT"
13432 >%!
13433                 </TT
13434 > to the start of print output.</P
13435 ><P
13436 >This is most useful when you have lots of PCs that persist
13437                 in putting a control-D at the start of print jobs, which then
13438                 confuses your printer.</P
13439 ><P
13440 >Default: <B
13441 CLASS="COMMAND"
13442 >postscript = no</B
13443 ></P
13444 ></DD
13445 ><DT
13446 ><A
13447 NAME="PREEXEC"
13448 ></A
13449 >preexec (S)</DT
13450 ><DD
13451 ><P
13452 >This option specifies a command to be run whenever
13453                 the service is connected to. It takes the usual substitutions.</P
13454 ><P
13455 >An interesting example is to send the users a welcome
13456                 message every time they log in. Maybe a message of the day? Here
13457                 is an example:</P
13458 ><P
13459 ><B
13460 CLASS="COMMAND"
13461 >preexec = csh -c 'echo \"Welcome to %S!\" |
13462                  /usr/local/samba/bin/smbclient -M %m -I %I' &#38; </B
13463 ></P
13464 ><P
13465 >Of course, this could get annoying after a while :-)</P
13466 ><P
13467 >See also <A
13468 HREF="#PREEXECCLOSE"
13469 ><TT
13470 CLASS="PARAMETER"
13471 ><I
13472 >preexec close
13473                 </I
13474 ></TT
13475 ></A
13476 > and <A
13477 HREF="#POSTEXEC"
13478 ><TT
13479 CLASS="PARAMETER"
13480 ><I
13481 >postexec
13482                 </I
13483 ></TT
13484 ></A
13485 >.</P
13486 ><P
13487 >Default: <EM
13488 >none (no command executed)</EM
13489 ></P
13490 ><P
13491 >Example: <B
13492 CLASS="COMMAND"
13493 >preexec = echo \"%u connected to %S from %m
13494                 (%I)\" &#62;&#62; /tmp/log</B
13495 ></P
13496 ></DD
13497 ><DT
13498 ><A
13499 NAME="PREEXECCLOSE"
13500 ></A
13501 >preexec close (S)</DT
13502 ><DD
13503 ><P
13504 >This boolean option controls whether a non-zero
13505                 return code from <A
13506 HREF="#PREEXEC"
13507 ><TT
13508 CLASS="PARAMETER"
13509 ><I
13510 >preexec
13511                 </I
13512 ></TT
13513 ></A
13514 > should close the service being connected to.</P
13515 ><P
13516 >Default: <B
13517 CLASS="COMMAND"
13518 >preexec close = no</B
13519 ></P
13520 ></DD
13521 ><DT
13522 ><A
13523 NAME="PREFERREDMASTER"
13524 ></A
13525 >preferred master (G)</DT
13526 ><DD
13527 ><P
13528 >This boolean parameter controls if <A
13529 HREF="nmbd.8.html"
13530 TARGET="_top"
13531 >nmbd(8)</A
13532 > is a preferred master browser
13533                 for its workgroup.</P
13534 ><P
13535 >If this is set to <TT
13536 CLASS="CONSTANT"
13537 >true</TT
13538 >, on startup, <B
13539 CLASS="COMMAND"
13540 >nmbd</B
13541 >
13542                 will force an election, and it will have a slight advantage in
13543                 winning the election.  It is recommended that this parameter is
13544                 used in conjunction with <B
13545 CLASS="COMMAND"
13546 ><A
13547 HREF="#DOMAINMASTER"
13548 ><TT
13549 CLASS="PARAMETER"
13550 ><I
13551 >               domain master</I
13552 ></TT
13553 ></A
13554 > = yes</B
13555 >, so that <B
13556 CLASS="COMMAND"
13557 >               nmbd</B
13558 > can guarantee becoming a domain master.</P
13559 ><P
13560 >Use this option with caution, because if there are several
13561                 hosts (whether Samba servers, Windows 95 or NT) that are preferred
13562                 master browsers on the same subnet, they will each periodically
13563                 and continuously attempt to become the local master browser.
13564                 This will result in unnecessary broadcast traffic and reduced browsing
13565                 capabilities.</P
13566 ><P
13567 >See also <A
13568 HREF="#OSLEVEL"
13569 ><TT
13570 CLASS="PARAMETER"
13571 ><I
13572 >os level</I
13573 ></TT
13574 >
13575                 </A
13576 >.</P
13577 ><P
13578 >Default: <B
13579 CLASS="COMMAND"
13580 >preferred master = auto</B
13581 ></P
13582 ></DD
13583 ><DT
13584 ><A
13585 NAME="PREFEREDMASTER"
13586 ></A
13587 >prefered master (G)</DT
13588 ><DD
13589 ><P
13590 >Synonym for <A
13591 HREF="#PREFERREDMASTER"
13592 ><TT
13593 CLASS="PARAMETER"
13594 ><I
13595 >               preferred master</I
13596 ></TT
13597 ></A
13598 > for people who cannot spell :-).</P
13599 ></DD
13600 ><DT
13601 ><A
13602 NAME="PRELOAD"
13603 ></A
13604 >preload</DT
13605 ><DD
13606 ><P
13607 >This is a list of services that you want to be
13608                 automatically added to the browse lists. This is most useful
13609                 for homes and printers services that would otherwise not be
13610                 visible.</P
13611 ><P
13612 >Note that if you just want all printers in your
13613                 printcap file loaded then the <A
13614 HREF="#LOADPRINTERS"
13615 >               <TT
13616 CLASS="PARAMETER"
13617 ><I
13618 >load printers</I
13619 ></TT
13620 ></A
13621 > option is easier.</P
13622 ><P
13623 >Default: <EM
13624 >no preloaded services</EM
13625 ></P
13626 ><P
13627 >Example: <B
13628 CLASS="COMMAND"
13629 >preload = fred lp colorlp</B
13630 ></P
13631 ></DD
13632 ><DT
13633 ><A
13634 NAME="PRESERVECASE"
13635 ></A
13636 >preserve case (S)</DT
13637 ><DD
13638 ><P
13639 > This controls if new filenames are created
13640                 with the case that the client passes, or if they are forced to
13641                 be the <A
13642 HREF="#DEFAULTCASE"
13643 ><TT
13644 CLASS="PARAMETER"
13645 ><I
13646 >default case
13647                 </I
13648 ></TT
13649 ></A
13650 >.</P
13651 ><P
13652 >Default: <B
13653 CLASS="COMMAND"
13654 >preserve case = yes</B
13655 ></P
13656 ><P
13657 >See the section on <A
13658 HREF="#AEN202"
13659 >NAME
13660                 MANGLING</A
13661 > for a fuller discussion.</P
13662 ></DD
13663 ><DT
13664 ><A
13665 NAME="PRINTCOMMAND"
13666 ></A
13667 >print command (S)</DT
13668 ><DD
13669 ><P
13670 >After a print job has finished spooling to
13671                 a service, this command will be used via a <B
13672 CLASS="COMMAND"
13673 >system()</B
13674 >
13675                 call to process the spool file. Typically the command specified will
13676                 submit the spool file to the host's printing subsystem, but there
13677                 is no requirement that this be the case. The server will not remove
13678                 the spool file, so whatever command you specify should remove the
13679                 spool file when it has been processed, otherwise you will need to
13680                 manually remove old spool files.</P
13681 ><P
13682 >The print command is simply a text string. It will be used
13683                 verbatim, with two exceptions: All occurrences of <TT
13684 CLASS="PARAMETER"
13685 ><I
13686 >%s
13687                 </I
13688 ></TT
13689 > and <TT
13690 CLASS="PARAMETER"
13691 ><I
13692 >%f</I
13693 ></TT
13694 > will be replaced by the
13695                 appropriate spool file name, and all occurrences of <TT
13696 CLASS="PARAMETER"
13697 ><I
13698 >%p
13699                 </I
13700 ></TT
13701 > will be replaced by the appropriate printer name. The
13702                 spool file name is generated automatically by the server, the printer
13703                 name is discussed below.</P
13704 ><P
13705 >The print command <EM
13706 >MUST</EM
13707 > contain at least
13708                 one occurrence of <TT
13709 CLASS="PARAMETER"
13710 ><I
13711 >%s</I
13712 ></TT
13713 > or <TT
13714 CLASS="PARAMETER"
13715 ><I
13716 >%f
13717                 </I
13718 ></TT
13719 > - the <TT
13720 CLASS="PARAMETER"
13721 ><I
13722 >%p</I
13723 ></TT
13724 > is optional. At the time
13725                 a job is submitted, if no printer name is supplied the <TT
13726 CLASS="PARAMETER"
13727 ><I
13728 >%p
13729                 </I
13730 ></TT
13731 > will be silently removed from the printer command.</P
13732 ><P
13733 >If specified in the [global] section, the print command given
13734                 will be used for any printable service that does not have its own
13735                 print command specified.</P
13736 ><P
13737 >If there is neither a specified print command for a
13738                 printable service nor a global print command, spool files will
13739                 be created but not processed and (most importantly) not removed.</P
13740 ><P
13741 >Note that printing may fail on some UNIXes from the
13742                 <TT
13743 CLASS="CONSTANT"
13744 >nobody</TT
13745 > account. If this happens then create
13746                 an alternative guest account that can print and set the <A
13747 HREF="#GUESTACCOUNT"
13748 ><TT
13749 CLASS="PARAMETER"
13750 ><I
13751 >guest account</I
13752 ></TT
13753 ></A
13754 >
13755                 in the [global] section.</P
13756 ><P
13757 >You can form quite complex print commands by realizing
13758                 that they are just passed to a shell. For example the following
13759                 will log a print job, print the file, then remove it. Note that
13760                 ';' is the usual separator for command in shell scripts.</P
13761 ><P
13762 ><B
13763 CLASS="COMMAND"
13764 >print command = echo Printing %s &#62;&#62;
13765                 /tmp/print.log; lpr -P %p %s; rm %s</B
13766 ></P
13767 ><P
13768 >You may have to vary this command considerably depending
13769                 on how you normally print files on your system. The default for
13770                 the parameter varies depending on the setting of the <A
13771 HREF="#PRINTING"
13772 >               <TT
13773 CLASS="PARAMETER"
13774 ><I
13775 >printing</I
13776 ></TT
13777 ></A
13778 > parameter.</P
13779 ><P
13780 >Default: For <B
13781 CLASS="COMMAND"
13782 >printing = BSD, AIX, QNX, LPRNG
13783                 or PLP :</B
13784 ></P
13785 ><P
13786 ><B
13787 CLASS="COMMAND"
13788 >print command = lpr -r -P%p %s</B
13789 ></P
13790 ><P
13791 >For <B
13792 CLASS="COMMAND"
13793 >printing = SYS or HPUX :</B
13794 ></P
13795 ><P
13796 ><B
13797 CLASS="COMMAND"
13798 >print command = lp -c -d%p %s; rm %s</B
13799 ></P
13800 ><P
13801 >For <B
13802 CLASS="COMMAND"
13803 >printing = SOFTQ :</B
13804 ></P
13805 ><P
13806 ><B
13807 CLASS="COMMAND"
13808 >print command = lp -d%p -s %s; rm %s</B
13809 ></P
13810 ><P
13811 >Example: <B
13812 CLASS="COMMAND"
13813 >print command = /usr/local/samba/bin/myprintscript
13814                 %p %s</B
13815 ></P
13816 ></DD
13817 ><DT
13818 ><A
13819 NAME="PRINTOK"
13820 ></A
13821 >print ok (S)</DT
13822 ><DD
13823 ><P
13824 >Synonym for <A
13825 HREF="#PRINTABLE"
13826 >               <TT
13827 CLASS="PARAMETER"
13828 ><I
13829 >printable</I
13830 ></TT
13831 ></A
13832 >.</P
13833 ></DD
13834 ><DT
13835 ><A
13836 NAME="PRINTABLE"
13837 ></A
13838 >printable (S)</DT
13839 ><DD
13840 ><P
13841 >If this parameter is <TT
13842 CLASS="CONSTANT"
13843 >yes</TT
13844 >, then
13845                 clients may open, write to and submit spool files on the directory
13846                 specified for the service. </P
13847 ><P
13848 >Note that a printable service will ALWAYS allow writing
13849                 to the service path (user privileges permitting) via the spooling
13850                 of print data. The <A
13851 HREF="#WRITEABLE"
13852 ><TT
13853 CLASS="PARAMETER"
13854 ><I
13855 >writeable
13856                 </I
13857 ></TT
13858 ></A
13859 > parameter controls only non-printing access to
13860                 the resource.</P
13861 ><P
13862 >Default: <B
13863 CLASS="COMMAND"
13864 >printable = no</B
13865 ></P
13866 ></DD
13867 ><DT
13868 ><A
13869 NAME="PRINTCAP"
13870 ></A
13871 >printcap (G)</DT
13872 ><DD
13873 ><P
13874 >Synonym for    <A
13875 HREF="#PRINTCAPNAME"
13876 ><TT
13877 CLASS="PARAMETER"
13878 ><I
13879 >               printcap name</I
13880 ></TT
13881 ></A
13882 >.</P
13883 ></DD
13884 ><DT
13885 ><A
13886 NAME="PRINTCAPNAME"
13887 ></A
13888 >printcap name (G)</DT
13889 ><DD
13890 ><P
13891 >This parameter may be used to override the
13892                 compiled-in default printcap name used by the server (usually <TT
13893 CLASS="FILENAME"
13894 >               /etc/printcap</TT
13895 >). See the discussion of the <A
13896 HREF="#AEN79"
13897 >[printers]</A
13898 > section above for reasons
13899                 why you might want to do this.</P
13900 ><P
13901 >On System V systems that use <B
13902 CLASS="COMMAND"
13903 >lpstat</B
13904 > to
13905                 list available printers you can use <B
13906 CLASS="COMMAND"
13907 >printcap name = lpstat
13908                 </B
13909 > to automatically obtain lists of available printers. This
13910                 is the default for systems that define SYSV at configure time in
13911                 Samba (this includes most System V based systems). If <TT
13912 CLASS="PARAMETER"
13913 ><I
13914 >               printcap name</I
13915 ></TT
13916 > is set to <B
13917 CLASS="COMMAND"
13918 >lpstat</B
13919 > on
13920                 these systems then Samba will launch <B
13921 CLASS="COMMAND"
13922 >lpstat -v</B
13923 > and
13924                 attempt to parse the output to obtain a printer list.</P
13925 ><P
13926 >A minimal printcap file would look something like this:</P
13927 ><P
13928 ><TABLE
13929 BORDER="0"
13930 BGCOLOR="#E0E0E0"
13931 WIDTH="90%"
13932 ><TR
13933 ><TD
13934 ><PRE
13935 CLASS="PROGRAMLISTING"
13936 >               print1|My Printer 1
13937                 print2|My Printer 2
13938                 print3|My Printer 3
13939                 print4|My Printer 4
13940                 print5|My Printer 5
13941                 </PRE
13942 ></TD
13943 ></TR
13944 ></TABLE
13945 ></P
13946 ><P
13947 >where the '|' separates aliases of a printer. The fact
13948                 that the second alias has a space in it gives a hint to Samba
13949                 that it's a comment.</P
13950 ><P
13951 ><EM
13952 >NOTE</EM
13953 >: Under AIX the default printcap
13954                 name is <TT
13955 CLASS="FILENAME"
13956 >/etc/qconfig</TT
13957 >. Samba will assume the
13958                 file is in AIX <TT
13959 CLASS="FILENAME"
13960 >qconfig</TT
13961 > format if the string
13962                 <TT
13963 CLASS="FILENAME"
13964 >qconfig</TT
13965 > appears in the printcap filename.</P
13966 ><P
13967 >Default: <B
13968 CLASS="COMMAND"
13969 >printcap name = /etc/printcap</B
13970 ></P
13971 ><P
13972 >Example: <B
13973 CLASS="COMMAND"
13974 >printcap name = /etc/myprintcap</B
13975 ></P
13976 ></DD
13977 ><DT
13978 ><A
13979 NAME="PRINTERADMIN"
13980 ></A
13981 >printer admin (S)</DT
13982 ><DD
13983 ><P
13984 >This is a list of users that can do anything to
13985                 printers via the remote administration interfaces offered by MS-RPC
13986                 (usually using a NT workstation). Note that the root user always
13987                 has admin rights.</P
13988 ><P
13989 >Default: <B
13990 CLASS="COMMAND"
13991 >printer admin = &#60;empty string&#62;</B
13992 >
13993                 </P
13994 ><P
13995 >Example: <B
13996 CLASS="COMMAND"
13997 >printer admin = admin, @staff</B
13998 ></P
13999 ></DD
14000 ><DT
14001 ><A
14002 NAME="PRINTERDRIVER"
14003 ></A
14004 >printer driver (S)</DT
14005 ><DD
14006 ><P
14007 ><EM
14008 >Note :</EM
14009 >This is a deprecated
14010                 parameter and will be removed in the next major release
14011                 following version 2.2.  Please see the instructions in
14012                 the <A
14013 HREF="printer_driver2.html"
14014 TARGET="_top"
14015 >Samba 2.2. Printing
14016                 HOWTO</A
14017 > for more information
14018                 on the new method of loading printer drivers onto a Samba server.
14019                 </P
14020 ><P
14021 >This option allows you to control the string
14022                 that clients receive when they ask the server for the printer driver
14023                 associated with a printer. If you are using Windows95 or Windows NT
14024                 then you can use this to automate the setup of printers on your
14025                 system.</P
14026 ><P
14027 >You need to set this parameter to the exact string (case
14028                 sensitive) that describes the appropriate printer driver for your
14029                 system. If you don't know the exact string to use then you should
14030                 first try with no <A
14031 HREF="#PRINTERDRIVER"
14032 ><TT
14033 CLASS="PARAMETER"
14034 ><I
14035 >               printer driver</I
14036 ></TT
14037 ></A
14038 > option set and the client will
14039                 give you a list of printer drivers. The appropriate strings are
14040                 shown in a scroll box after you have chosen the printer manufacturer.</P
14041 ><P
14042 >See also <A
14043 HREF="#PRINTERDRIVERFILE"
14044 ><TT
14045 CLASS="PARAMETER"
14046 ><I
14047 >printer
14048                 driver file</I
14049 ></TT
14050 ></A
14051 >.</P
14052 ><P
14053 >Example: <B
14054 CLASS="COMMAND"
14055 >printer driver = HP LaserJet 4L</B
14056 ></P
14057 ></DD
14058 ><DT
14059 ><A
14060 NAME="PRINTERDRIVERFILE"
14061 ></A
14062 >printer driver file (G)</DT
14063 ><DD
14064 ><P
14065 ><EM
14066 >Note :</EM
14067 >This is a deprecated
14068                 parameter and will be removed in the next major release
14069                 following version 2.2.  Please see the instructions in
14070                 the <A
14071 HREF="printer_driver2.html"
14072 TARGET="_top"
14073 >Samba 2.2. Printing
14074                 HOWTO</A
14075 > for more information
14076                 on the new method of loading printer drivers onto a Samba server.
14077                 </P
14078 ><P
14079 >This parameter tells Samba where the printer driver
14080                 definition file, used when serving drivers to Windows 95 clients, is
14081                 to be found. If this is not set, the default is :</P
14082 ><P
14083 ><TT
14084 CLASS="FILENAME"
14085 ><TT
14086 CLASS="REPLACEABLE"
14087 ><I
14088 >SAMBA_INSTALL_DIRECTORY</I
14089 ></TT
14090 >
14091                 /lib/printers.def</TT
14092 ></P
14093 ><P
14094 >This file is created from Windows 95 <TT
14095 CLASS="FILENAME"
14096 >msprint.inf
14097                 </TT
14098 > files found on the Windows 95 client system. For more
14099                 details on setting up serving of printer drivers to Windows 95
14100                 clients, see the outdated documentation file in the <TT
14101 CLASS="FILENAME"
14102 >docs/</TT
14103 >
14104                 directory, <TT
14105 CLASS="FILENAME"
14106 >PRINTER_DRIVER.txt</TT
14107 >.</P
14108 ><P
14109 >See also <A
14110 HREF="#PRINTERDRIVERLOCATION"
14111 ><TT
14112 CLASS="PARAMETER"
14113 ><I
14114 >               printer driver location</I
14115 ></TT
14116 ></A
14117 >.</P
14118 ><P
14119 >Default: <EM
14120 >None (set in compile).</EM
14121 ></P
14122 ><P
14123 >Example: <B
14124 CLASS="COMMAND"
14125 >printer driver file =
14126                 /usr/local/samba/printers/drivers.def</B
14127 ></P
14128 ></DD
14129 ><DT
14130 ><A
14131 NAME="PRINTERDRIVERLOCATION"
14132 ></A
14133 >printer driver location (S)</DT
14134 ><DD
14135 ><P
14136 ><EM
14137 >Note :</EM
14138 >This is a deprecated
14139                 parameter and will be removed in the next major release
14140                 following version 2.2.  Please see the instructions in
14141                 the <A
14142 HREF="printer_driver2.html"
14143 TARGET="_top"
14144 >Samba 2.2. Printing
14145                 HOWTO</A
14146 > for more information
14147                 on the new method of loading printer drivers onto a Samba server.
14148                 </P
14149 ><P
14150 >This parameter tells clients of a particular printer
14151                 share where to find the printer driver files for the automatic
14152                 installation of drivers for Windows 95 machines. If Samba is set up
14153                 to serve printer drivers to Windows 95 machines, this should be set to</P
14154 ><P
14155 ><B
14156 CLASS="COMMAND"
14157 >\\MACHINE\PRINTER$</B
14158 ></P
14159 ><P
14160 >Where MACHINE is the NetBIOS name of your Samba server,
14161                 and PRINTER$ is a share you set up for serving printer driver
14162                 files. For more details on setting this up see the outdated documentation
14163                 file in the <TT
14164 CLASS="FILENAME"
14165 >docs/</TT
14166 > directory, <TT
14167 CLASS="FILENAME"
14168 >               PRINTER_DRIVER.txt</TT
14169 >.</P
14170 ><P
14171 >See also <A
14172 HREF="#PRINTERDRIVERFILE"
14173 ><TT
14174 CLASS="PARAMETER"
14175 ><I
14176 >               printer driver file</I
14177 ></TT
14178 ></A
14179 >.</P
14180 ><P
14181 >Default: <B
14182 CLASS="COMMAND"
14183 >none</B
14184 ></P
14185 ><P
14186 >Example: <B
14187 CLASS="COMMAND"
14188 >printer driver location = \\MACHINE\PRINTER$
14189                 </B
14190 ></P
14191 ></DD
14192 ><DT
14193 ><A
14194 NAME="PRINTERNAME"
14195 ></A
14196 >printer name (S)</DT
14197 ><DD
14198 ><P
14199 >This parameter specifies the name of the printer
14200                 to which print jobs spooled through a printable service will be sent.</P
14201 ><P
14202 >If specified in the [global] section, the printer
14203                 name given will be used for any printable service that does
14204                 not have its own printer name specified.</P
14205 ><P
14206 >Default: <EM
14207 >none (but may be <TT
14208 CLASS="CONSTANT"
14209 >lp</TT
14210 >
14211                 on many systems)</EM
14212 ></P
14213 ><P
14214 >Example: <B
14215 CLASS="COMMAND"
14216 >printer name = laserwriter</B
14217 ></P
14218 ></DD
14219 ><DT
14220 ><A
14221 NAME="PRINTER"
14222 ></A
14223 >printer (S)</DT
14224 ><DD
14225 ><P
14226 >Synonym for <A
14227 HREF="#PRINTERNAME"
14228 ><TT
14229 CLASS="PARAMETER"
14230 ><I
14231 >               printer name</I
14232 ></TT
14233 ></A
14234 >.</P
14235 ></DD
14236 ><DT
14237 ><A
14238 NAME="PRINTING"
14239 ></A
14240 >printing (S)</DT
14241 ><DD
14242 ><P
14243 >This parameters controls how printer status
14244                 information is interpreted on your system. It also affects the
14245                 default values for the <TT
14246 CLASS="PARAMETER"
14247 ><I
14248 >print command</I
14249 ></TT
14250 >,
14251                 <TT
14252 CLASS="PARAMETER"
14253 ><I
14254 >lpq command</I
14255 ></TT
14256 >, <TT
14257 CLASS="PARAMETER"
14258 ><I
14259 >lppause command
14260                 </I
14261 ></TT
14262 >, <TT
14263 CLASS="PARAMETER"
14264 ><I
14265 >lpresume command</I
14266 ></TT
14267 >, and
14268                 <TT
14269 CLASS="PARAMETER"
14270 ><I
14271 >lprm command</I
14272 ></TT
14273 > if specified in the
14274                 [global] section.</P
14275 ><P
14276 >Currently eight printing styles are supported. They are
14277                 <TT
14278 CLASS="CONSTANT"
14279 >BSD</TT
14280 >, <TT
14281 CLASS="CONSTANT"
14282 >AIX</TT
14283 >,
14284                 <TT
14285 CLASS="CONSTANT"
14286 >LPRNG</TT
14287 >, <TT
14288 CLASS="CONSTANT"
14289 >PLP</TT
14290 >,
14291                 <TT
14292 CLASS="CONSTANT"
14293 >SYSV</TT
14294 >, <TT
14295 CLASS="CONSTANT"
14296 >HPUX</TT
14297 >,
14298                 <TT
14299 CLASS="CONSTANT"
14300 >QNX</TT
14301 >, <TT
14302 CLASS="CONSTANT"
14303 >SOFTQ</TT
14304 >,
14305                 and <TT
14306 CLASS="CONSTANT"
14307 >CUPS</TT
14308 >.</P
14309 ><P
14310 >To see what the defaults are for the other print
14311                 commands when using the various options use the <A
14312 HREF="testparm.1.html"
14313 TARGET="_top"
14314 >testparm(1)</A
14315 > program.</P
14316 ><P
14317 >This option can be set on a per printer basis</P
14318 ><P
14319 >See also the discussion in the <A
14320 HREF="#AEN79"
14321 >               [printers]</A
14322 > section.</P
14323 ></DD
14324 ><DT
14325 ><A
14326 NAME="PROTOCOL"
14327 ></A
14328 >protocol (G)</DT
14329 ><DD
14330 ><P
14331 >Synonym for <A
14332 HREF="#MAXPROTOCOL"
14333 >               <TT
14334 CLASS="PARAMETER"
14335 ><I
14336 >max protocol</I
14337 ></TT
14338 ></A
14339 >.</P
14340 ></DD
14341 ><DT
14342 ><A
14343 NAME="PUBLIC"
14344 ></A
14345 >public (S)</DT
14346 ><DD
14347 ><P
14348 >Synonym for <A
14349 HREF="#GUESTOK"
14350 ><TT
14351 CLASS="PARAMETER"
14352 ><I
14353 >guest
14354                 ok</I
14355 ></TT
14356 ></A
14357 >.</P
14358 ></DD
14359 ><DT
14360 ><A
14361 NAME="QUEUEPAUSECOMMAND"
14362 ></A
14363 >queuepause command (S)</DT
14364 ><DD
14365 ><P
14366 >This parameter specifies the command to be
14367                 executed on the server host in order to pause the printer queue.</P
14368 ><P
14369 >This command should be a program or script which takes
14370                 a printer name as its only parameter and stops the printer queue,
14371                 such that no longer jobs are submitted to the printer.</P
14372 ><P
14373 >This command is not supported by Windows for Workgroups,
14374                 but can be issued from the Printers window under Windows 95
14375                 and NT.</P
14376 ><P
14377 >If a <TT
14378 CLASS="PARAMETER"
14379 ><I
14380 >%p</I
14381 ></TT
14382 > is given then the printer name
14383                 is put in its place. Otherwise it is placed at the end of the command.
14384                 </P
14385 ><P
14386 >Note that it is good practice to include the absolute
14387                 path in the command as the PATH may not be available to the
14388                 server.</P
14389 ><P
14390 >Default: <EM
14391 >depends on the setting of <TT
14392 CLASS="PARAMETER"
14393 ><I
14394 >printing
14395                 </I
14396 ></TT
14397 ></EM
14398 ></P
14399 ><P
14400 >Example: <B
14401 CLASS="COMMAND"
14402 >queuepause command = disable %p</B
14403 ></P
14404 ></DD
14405 ><DT
14406 ><A
14407 NAME="QUEUERESUMECOMMAND"
14408 ></A
14409 >queueresume command (S)</DT
14410 ><DD
14411 ><P
14412 >This parameter specifies the command to be
14413                 executed on the server host in order to resume the printer queue. It
14414                 is the command to undo the behavior that is caused by the
14415                 previous parameter (<A
14416 HREF="#QUEUEPAUSECOMMAND"
14417 ><TT
14418 CLASS="PARAMETER"
14419 ><I
14420 >               queuepause command</I
14421 ></TT
14422 ></A
14423 >).</P
14424 ><P
14425 >This command should be a program or script which takes
14426                 a printer name as its only parameter and resumes the printer queue,
14427                 such that queued jobs are resubmitted to the printer.</P
14428 ><P
14429 >This command is not supported by Windows for Workgroups,
14430                 but can be issued from the Printers window under Windows 95
14431                 and NT.</P
14432 ><P
14433 >If a <TT
14434 CLASS="PARAMETER"
14435 ><I
14436 >%p</I
14437 ></TT
14438 > is given then the printer name
14439                 is put in its place. Otherwise it is placed at the end of the
14440                 command.</P
14441 ><P
14442 >Note that it is good practice to include the absolute
14443                 path in the command as the PATH may not be available to the
14444                 server.</P
14445 ><P
14446 >Default: <EM
14447 >depends on the setting of <A
14448 HREF="#PRINTING"
14449 ><TT
14450 CLASS="PARAMETER"
14451 ><I
14452 >printing</I
14453 ></TT
14454 ></A
14455 ></EM
14456 >
14457                 </P
14458 ><P
14459 >Example: <B
14460 CLASS="COMMAND"
14461 >queuepause command = enable %p
14462                 </B
14463 ></P
14464 ></DD
14465 ><DT
14466 ><A
14467 NAME="READBMPX"
14468 ></A
14469 >read bmpx (G)</DT
14470 ><DD
14471 ><P
14472 >This boolean parameter controls whether <A
14473 HREF="smbd.8.html"
14474 TARGET="_top"
14475 >smbd(8)</A
14476 > will support the "Read
14477                 Block Multiplex" SMB. This is now rarely used and defaults to
14478                 <TT
14479 CLASS="CONSTANT"
14480 >no</TT
14481 >. You should never need to set this
14482                 parameter.</P
14483 ><P
14484 >Default: <B
14485 CLASS="COMMAND"
14486 >read bmpx = no</B
14487 ></P
14488 ></DD
14489 ><DT
14490 ><A
14491 NAME="READLIST"
14492 ></A
14493 >read list (S)</DT
14494 ><DD
14495 ><P
14496 >This is a list of users that are given read-only
14497                 access to a service. If the connecting user is in this list then
14498                 they will not be given write access, no matter what the <A
14499 HREF="#WRITEABLE"
14500 ><TT
14501 CLASS="PARAMETER"
14502 ><I
14503 >writeable</I
14504 ></TT
14505 ></A
14506 >
14507                 option is set to. The list can include group names using the
14508                 syntax described in the <A
14509 HREF="#INVALIDUSERS"
14510 ><TT
14511 CLASS="PARAMETER"
14512 ><I
14513 >               invalid users</I
14514 ></TT
14515 ></A
14516 > parameter.</P
14517 ><P
14518 >See also the <A
14519 HREF="#WRITELIST"
14520 ><TT
14521 CLASS="PARAMETER"
14522 ><I
14523 >               write list</I
14524 ></TT
14525 ></A
14526 > parameter and the <A
14527 HREF="#INVALIDUSERS"
14528 ><TT
14529 CLASS="PARAMETER"
14530 ><I
14531 >invalid users</I
14532 ></TT
14533 >
14534                 </A
14535 > parameter.</P
14536 ><P
14537 >Default: <B
14538 CLASS="COMMAND"
14539 >read list = &#60;empty string&#62;</B
14540 ></P
14541 ><P
14542 >Example: <B
14543 CLASS="COMMAND"
14544 >read list = mary, @students</B
14545 ></P
14546 ></DD
14547 ><DT
14548 ><A
14549 NAME="READONLY"
14550 ></A
14551 >read only (S)</DT
14552 ><DD
14553 ><P
14554 >Note that this is an inverted synonym for <A
14555 HREF="#WRITEABLE"
14556 ><TT
14557 CLASS="PARAMETER"
14558 ><I
14559 >writeable</I
14560 ></TT
14561 ></A
14562 >.</P
14563 ></DD
14564 ><DT
14565 ><A
14566 NAME="READRAW"
14567 ></A
14568 >read raw (G)</DT
14569 ><DD
14570 ><P
14571 >This parameter controls whether or not the server
14572                 will support the raw read SMB requests when transferring data
14573                 to clients.</P
14574 ><P
14575 >If enabled, raw reads allow reads of 65535 bytes in
14576                 one packet. This typically provides a major performance benefit.
14577                 </P
14578 ><P
14579 >However, some clients either negotiate the allowable
14580                 block size incorrectly or are incapable of supporting larger block
14581                 sizes, and for these clients you may need to disable raw reads.</P
14582 ><P
14583 >In general this parameter should be viewed as a system tuning
14584                 tool and left severely alone. See also <A
14585 HREF="#WRITERAW"
14586 >               <TT
14587 CLASS="PARAMETER"
14588 ><I
14589 >write raw</I
14590 ></TT
14591 ></A
14592 >.</P
14593 ><P
14594 >Default: <B
14595 CLASS="COMMAND"
14596 >read raw = yes</B
14597 ></P
14598 ></DD
14599 ><DT
14600 ><A
14601 NAME="READSIZE"
14602 ></A
14603 >read size (G)</DT
14604 ><DD
14605 ><P
14606 >The option <TT
14607 CLASS="PARAMETER"
14608 ><I
14609 >read size</I
14610 ></TT
14611 >
14612                 affects the overlap of disk reads/writes with network reads/writes.
14613                 If the amount of data being transferred in several of the SMB
14614                 commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger
14615                 than this value then the server begins writing the data before it
14616                 has received the whole packet from the network, or in the case of
14617                 SMBreadbraw, it begins writing to the network before all the data
14618                 has been read from disk.</P
14619 ><P
14620 >This overlapping works best when the speeds of disk and
14621                 network access are similar, having very little effect when the
14622                 speed of one is much greater than the other.</P
14623 ><P
14624 >The default value is 16384, but very little experimentation
14625                 has been done yet to determine the optimal value, and it is likely
14626                 that the best value will vary greatly between systems anyway.
14627                 A value over 65536 is pointless and will cause you to allocate
14628                 memory unnecessarily.</P
14629 ><P
14630 >Default: <B
14631 CLASS="COMMAND"
14632 >read size = 16384</B
14633 ></P
14634 ><P
14635 >Example: <B
14636 CLASS="COMMAND"
14637 >read size = 8192</B
14638 ></P
14639 ></DD
14640 ><DT
14641 ><A
14642 NAME="REMOTEANNOUNCE"
14643 ></A
14644 >remote announce (G)</DT
14645 ><DD
14646 ><P
14647 >This option allows you to setup <A
14648 HREF="nmbd.8.html"
14649 TARGET="_top"
14650 >nmbd(8)</A
14651 > to periodically announce itself
14652                 to arbitrary IP addresses with an arbitrary workgroup name.</P
14653 ><P
14654 >This is useful if you want your Samba server to appear
14655                 in a remote workgroup for which the normal browse propagation
14656                 rules don't work. The remote workgroup can be anywhere that you
14657                 can send IP packets to.</P
14658 ><P
14659 >For example:</P
14660 ><P
14661 ><B
14662 CLASS="COMMAND"
14663 >remote announce = 192.168.2.255/SERVERS
14664                 192.168.4.255/STAFF</B
14665 ></P
14666 ><P
14667 >the above line would cause <B
14668 CLASS="COMMAND"
14669 >nmbd</B
14670 > to announce itself
14671                 to the two given IP addresses using the given workgroup names.
14672                 If you leave out the workgroup name then the one given in
14673                 the <A
14674 HREF="#WORKGROUP"
14675 ><TT
14676 CLASS="PARAMETER"
14677 ><I
14678 >workgroup</I
14679 ></TT
14680 ></A
14681 >
14682                 parameter is used instead.</P
14683 ><P
14684 >The IP addresses you choose would normally be the broadcast
14685                 addresses of the remote networks, but can also be the IP addresses
14686                 of known browse masters if your network config is that stable.</P
14687 ><P
14688 >See the documentation file <TT
14689 CLASS="FILENAME"
14690 >BROWSING.txt</TT
14691 >
14692                 in the <TT
14693 CLASS="FILENAME"
14694 >docs/</TT
14695 > directory.</P
14696 ><P
14697 >Default: <B
14698 CLASS="COMMAND"
14699 >remote announce = &#60;empty string&#62;
14700                 </B
14701 ></P
14702 ></DD
14703 ><DT
14704 ><A
14705 NAME="REMOTEBROWSESYNC"
14706 ></A
14707 >remote browse sync (G)</DT
14708 ><DD
14709 ><P
14710 >This option allows you to setup <A
14711 HREF="nmbd.8.html"
14712 TARGET="_top"
14713 >nmbd(8)</A
14714 > to periodically request
14715                 synchronization of browse lists with the master browser of a Samba
14716                 server that is on a remote segment. This option will allow you to
14717                 gain browse lists for multiple workgroups across routed networks. This
14718                 is done in a manner that does not work with any non-Samba servers.</P
14719 ><P
14720 >This is useful if you want your Samba server and all local
14721                 clients to appear in a remote workgroup for which the normal browse
14722                 propagation rules don't work. The remote workgroup can be anywhere
14723                 that you can send IP packets to.</P
14724 ><P
14725 >For example:</P
14726 ><P
14727 ><B
14728 CLASS="COMMAND"
14729 >remote browse sync = 192.168.2.255 192.168.4.255
14730                 </B
14731 ></P
14732 ><P
14733 >the above line would cause <B
14734 CLASS="COMMAND"
14735 >nmbd</B
14736 > to request
14737                 the master browser on the specified subnets or addresses to
14738                 synchronize their browse lists with the local server.</P
14739 ><P
14740 >The IP addresses you choose would normally be the broadcast
14741                 addresses of the remote networks, but can also be the IP addresses
14742                 of known browse masters if your network config is that stable. If
14743                 a machine IP address is given Samba makes NO attempt to validate
14744                 that the remote machine is available, is listening, nor that it
14745                 is in fact the browse master on its segment.</P
14746 ><P
14747 >Default: <B
14748 CLASS="COMMAND"
14749 >remote browse sync = &#60;empty string&#62;
14750                 </B
14751 ></P
14752 ></DD
14753 ><DT
14754 ><A
14755 NAME="RESTRICTACLWITHMASK"
14756 ></A
14757 >restrict acl with mask (S)</DT
14758 ><DD
14759 ><P
14760 >This is a boolean parameter.  If set to <TT
14761 CLASS="CONSTANT"
14762 >false</TT
14763 > (default), then
14764                 creation of files with access control lists (ACLS) and modification of ACLs
14765                 using the Windows NT/2000 ACL editor will be applied directly to the file
14766                 or directory.</P
14767 ><P
14768 >If set to <TT
14769 CLASS="CONSTANT"
14770 >true</TT
14771 >, then all requests to set an ACL on a file will have the
14772                 parameters <A
14773 HREF="#CREATEMASK"
14774 ><TT
14775 CLASS="PARAMETER"
14776 ><I
14777 >create mask</I
14778 ></TT
14779 ></A
14780 >,
14781                 <A
14782 HREF="#FORCECREATEMODE"
14783 ><TT
14784 CLASS="PARAMETER"
14785 ><I
14786 >force create mode</I
14787 ></TT
14788 ></A
14789 >
14790                 applied before setting the ACL, and all requests to set an ACL on a directory will
14791                 have the parameters <A
14792 HREF="#DIRECTORYMASK"
14793 ><TT
14794 CLASS="PARAMETER"
14795 ><I
14796 >directory
14797                 mask</I
14798 ></TT
14799 ></A
14800 >, <A
14801 HREF="#FORCEDIRECTORYMODE"
14802 ><TT
14803 CLASS="PARAMETER"
14804 ><I
14805 >force
14806                 directory mode</I
14807 ></TT
14808 ></A
14809 > applied before setting the ACL.
14810                 </P
14811 ><P
14812 >See also <A
14813 HREF="#CREATEMASK"
14814 ><TT
14815 CLASS="PARAMETER"
14816 ><I
14817 >create mask</I
14818 ></TT
14819 ></A
14820 >,
14821                 <A
14822 HREF="#FORCECREATEMODE"
14823 ><TT
14824 CLASS="PARAMETER"
14825 ><I
14826 >force create mode</I
14827 ></TT
14828 ></A
14829 >,
14830                 <A
14831 HREF="#DIRECTORYMASK"
14832 ><TT
14833 CLASS="PARAMETER"
14834 ><I
14835 >directory mask</I
14836 ></TT
14837 ></A
14838 >,
14839                 <A
14840 HREF="#FORCEDIRECTORYMODE"
14841 ><TT
14842 CLASS="PARAMETER"
14843 ><I
14844 >force directory mode</I
14845 ></TT
14846 ></A
14847 >
14848                 </P
14849 ><P
14850 >Default: <B
14851 CLASS="COMMAND"
14852 >restrict acl with mask = no</B
14853 ></P
14854 ></DD
14855 ><DT
14856 ><A
14857 NAME="RESTRICTANONYMOUS"
14858 ></A
14859 >restrict anonymous (G)</DT
14860 ><DD
14861 ><P
14862 >This is a boolean parameter.  If it is <TT
14863 CLASS="CONSTANT"
14864 >true</TT
14865 >, then
14866                 anonymous access to the server will be restricted, namely in the
14867                 case where the server is expecting the client to send a username,
14868                 but it doesn't.  Setting it to <TT
14869 CLASS="CONSTANT"
14870 >true</TT
14871 > will force these anonymous
14872                 connections to be denied, and the client will be required to always
14873                 supply a username and password when connecting. Use of this parameter
14874                 is only recommended for homogeneous NT client environments.</P
14875 ><P
14876 >This parameter makes the use of macro expansions that rely
14877                 on the username (%U, %G, etc) consistent.  NT 4.0
14878                 likes to use anonymous connections when refreshing the share list,
14879                 and this is a way to work around that.</P
14880 ><P
14881 >When restrict anonymous is <TT
14882 CLASS="CONSTANT"
14883 >true</TT
14884 >, all anonymous connections
14885                 are denied no matter what they are for.  This can effect the ability
14886                 of a machine to access the Samba Primary Domain Controller to revalidate
14887                 its machine account after someone else has logged on the client
14888                 interactively.  The NT client will display a message saying that
14889                 the machine's account in  the domain doesn't exist or the password is
14890                 bad.  The best way to deal  with this is to reboot NT client machines
14891                 between interactive logons,  using "Shutdown and Restart", rather
14892                 than "Close all programs and logon as a different user".</P
14893 ><P
14894 >Default: <B
14895 CLASS="COMMAND"
14896 >restrict anonymous = no</B
14897 ></P
14898 ></DD
14899 ><DT
14900 ><A
14901 NAME="ROOT"
14902 ></A
14903 >root (G)</DT
14904 ><DD
14905 ><P
14906 >Synonym for <A
14907 HREF="#ROOTDIRECTORY"
14908 >               <TT
14909 CLASS="PARAMETER"
14910 ><I
14911 >root directory"</I
14912 ></TT
14913 ></A
14914 >.</P
14915 ></DD
14916 ><DT
14917 ><A
14918 NAME="ROOTDIR"
14919 ></A
14920 >root dir (G)</DT
14921 ><DD
14922 ><P
14923 >Synonym for <A
14924 HREF="#ROOTDIRECTORY"
14925 >               <TT
14926 CLASS="PARAMETER"
14927 ><I
14928 >root directory"</I
14929 ></TT
14930 ></A
14931 >.</P
14932 ></DD
14933 ><DT
14934 ><A
14935 NAME="ROOTDIRECTORY"
14936 ></A
14937 >root directory (G)</DT
14938 ><DD
14939 ><P
14940 >The server will <B
14941 CLASS="COMMAND"
14942 >chroot()</B
14943 > (i.e.
14944                 Change its root directory) to this directory on startup. This is
14945                 not strictly necessary for secure operation. Even without it the
14946                 server will deny access to files not in one of the service entries.
14947                 It may also check for, and deny access to, soft links to other
14948                 parts of the filesystem, or attempts to use ".." in file names
14949                 to access other directories (depending on the setting of the <A
14950 HREF="#WIDELINKS"
14951 ><TT
14952 CLASS="PARAMETER"
14953 ><I
14954 >wide links</I
14955 ></TT
14956 ></A
14957 >
14958                 parameter).</P
14959 ><P
14960 >Adding a <TT
14961 CLASS="PARAMETER"
14962 ><I
14963 >root directory</I
14964 ></TT
14965 > entry other
14966                 than "/" adds an extra level of security, but at a price. It
14967                 absolutely ensures that no access is given to files not in the
14968                 sub-tree specified in the <TT
14969 CLASS="PARAMETER"
14970 ><I
14971 >root directory</I
14972 ></TT
14973 >
14974                 option, <EM
14975 >including</EM
14976 > some files needed for
14977                 complete operation of the server. To maintain full operability
14978                 of the server you will need to mirror some system files
14979                 into the <TT
14980 CLASS="PARAMETER"
14981 ><I
14982 >root directory</I
14983 ></TT
14984 > tree. In particular
14985                 you will need to mirror <TT
14986 CLASS="FILENAME"
14987 >/etc/passwd</TT
14988 > (or a
14989                 subset of it), and any binaries or configuration files needed for
14990                 printing (if required). The set of files that must be mirrored is
14991                 operating system dependent.</P
14992 ><P
14993 >Default: <B
14994 CLASS="COMMAND"
14995 >root directory = /</B
14996 ></P
14997 ><P
14998 >Example: <B
14999 CLASS="COMMAND"
15000 >root directory = /homes/smb</B
15001 ></P
15002 ></DD
15003 ><DT
15004 ><A
15005 NAME="ROOTPOSTEXEC"
15006 ></A
15007 >root postexec (S)</DT
15008 ><DD
15009 ><P
15010 >This is the same as the <TT
15011 CLASS="PARAMETER"
15012 ><I
15013 >postexec</I
15014 ></TT
15015 >
15016                 parameter except that the command is run as root. This
15017                 is useful for unmounting filesystems
15018                 (such as CDROMs) after a connection is closed.</P
15019 ><P
15020 >See also <A
15021 HREF="#POSTEXEC"
15022 ><TT
15023 CLASS="PARAMETER"
15024 ><I
15025 >               postexec</I
15026 ></TT
15027 ></A
15028 >.</P
15029 ><P
15030 >Default: <B
15031 CLASS="COMMAND"
15032 >root postexec = &#60;empty string&#62;
15033                 </B
15034 ></P
15035 ></DD
15036 ><DT
15037 ><A
15038 NAME="ROOTPREEXEC"
15039 ></A
15040 >root preexec (S)</DT
15041 ><DD
15042 ><P
15043 >This is the same as the <TT
15044 CLASS="PARAMETER"
15045 ><I
15046 >preexec</I
15047 ></TT
15048 >
15049                 parameter except that the command is run as root. This
15050                 is useful for mounting filesystems (such as CDROMs) when a
15051                 connection is opened.</P
15052 ><P
15053 >See also <A
15054 HREF="#PREEXEC"
15055 ><TT
15056 CLASS="PARAMETER"
15057 ><I
15058 >               preexec</I
15059 ></TT
15060 ></A
15061 > and <A
15062 HREF="#PREEXECCLOSE"
15063 >               <TT
15064 CLASS="PARAMETER"
15065 ><I
15066 >preexec close</I
15067 ></TT
15068 ></A
15069 >.</P
15070 ><P
15071 >Default: <B
15072 CLASS="COMMAND"
15073 >root preexec = &#60;empty string&#62;
15074                 </B
15075 ></P
15076 ></DD
15077 ><DT
15078 ><A
15079 NAME="ROOTPREEXECCLOSE"
15080 ></A
15081 >root preexec close (S)</DT
15082 ><DD
15083 ><P
15084 >This is the same as the <TT
15085 CLASS="PARAMETER"
15086 ><I
15087 >preexec close
15088                 </I
15089 ></TT
15090 > parameter except that the command is run as root.</P
15091 ><P
15092 >See also <A
15093 HREF="#PREEXEC"
15094 ><TT
15095 CLASS="PARAMETER"
15096 ><I
15097 >               preexec</I
15098 ></TT
15099 ></A
15100 > and <A
15101 HREF="#PREEXECCLOSE"
15102 >               <TT
15103 CLASS="PARAMETER"
15104 ><I
15105 >preexec close</I
15106 ></TT
15107 ></A
15108 >.</P
15109 ><P
15110 >Default: <B
15111 CLASS="COMMAND"
15112 >root preexec close = no</B
15113 ></P
15114 ></DD
15115 ><DT
15116 ><A
15117 NAME="SECURITY"
15118 ></A
15119 >security (G)</DT
15120 ><DD
15121 ><P
15122 >This option affects how clients respond to
15123                 Samba and is one of the most important settings in the <TT
15124 CLASS="FILENAME"
15125 >               smb.conf</TT
15126 > file.</P
15127 ><P
15128 >The option sets the "security mode bit" in replies to
15129                 protocol negotiations with <A
15130 HREF="smbd.8.html"
15131 TARGET="_top"
15132 >smbd(8)
15133                 </A
15134 > to turn share level security on or off. Clients decide
15135                 based on this bit whether (and how) to transfer user and password
15136                 information to the server.</P
15137 ><P
15138 >The default is <B
15139 CLASS="COMMAND"
15140 >security = user</B
15141 >, as this is
15142                 the most common setting needed when talking to Windows 98 and
15143                 Windows NT.</P
15144 ><P
15145 >The alternatives are <B
15146 CLASS="COMMAND"
15147 >security = share</B
15148 >,
15149                 <B
15150 CLASS="COMMAND"
15151 >security = server</B
15152 > or <B
15153 CLASS="COMMAND"
15154 >security = domain
15155                 </B
15156 >.</P
15157 ><P
15158 >In versions of Samba prior to 2..0, the default was
15159                 <B
15160 CLASS="COMMAND"
15161 >security = share</B
15162 > mainly because that was
15163                 the only option at one stage.</P
15164 ><P
15165 >There is a bug in WfWg that has relevance to this
15166                 setting. When in user or server level security a WfWg client
15167                 will totally ignore the password you type in the "connect
15168                 drive" dialog box. This makes it very difficult (if not impossible)
15169                 to connect to a Samba service as anyone except the user that
15170                 you are logged into WfWg as.</P
15171 ><P
15172 >If your PCs use usernames that are the same as their
15173                 usernames on the UNIX machine then you will want to use
15174                 <B
15175 CLASS="COMMAND"
15176 >security = user</B
15177 >. If you mostly use usernames
15178                 that don't exist on the UNIX box then use <B
15179 CLASS="COMMAND"
15180 >security =
15181                 share</B
15182 >.</P
15183 ><P
15184 >You should also use <B
15185 CLASS="COMMAND"
15186 >security = share</B
15187 > if you
15188                 want to mainly setup shares without a password (guest shares). This
15189                 is commonly used for a shared printer server. It is more difficult
15190                 to setup guest shares with <B
15191 CLASS="COMMAND"
15192 >security = user</B
15193 >, see
15194                 the <A
15195 HREF="#MAPTOGUEST"
15196 ><TT
15197 CLASS="PARAMETER"
15198 ><I
15199 >map to guest</I
15200 ></TT
15201 >
15202                 </A
15203 >parameter for details.</P
15204 ><P
15205 >It is possible to use <B
15206 CLASS="COMMAND"
15207 >smbd</B
15208 > in a <EM
15209 >               hybrid mode</EM
15210 > where it is offers both user and share
15211                 level security under different <A
15212 HREF="#NETBIOSALIASES"
15213 >               <TT
15214 CLASS="PARAMETER"
15215 ><I
15216 >NetBIOS aliases</I
15217 ></TT
15218 ></A
15219 >. </P
15220 ><P
15221 >The different settings will now be explained.</P
15222 ><P
15223 ><A
15224 NAME="SECURITYEQUALSSHARE"
15225 ></A
15226 ><EM
15227 >SECURITY = SHARE
15228                 </EM
15229 ></P
15230 ><P
15231 >When clients connect to a share level security server they
15232                 need not log onto the server with a valid username and password before
15233                 attempting to connect to a shared resource (although modern clients
15234                 such as Windows 95/98 and Windows NT will send a logon request with
15235                 a username but no password when talking to a <B
15236 CLASS="COMMAND"
15237 >security = share
15238                 </B
15239 > server). Instead, the clients send authentication information
15240                 (passwords) on a per-share basis, at the time they attempt to connect
15241                 to that share.</P
15242 ><P
15243 >Note that <B
15244 CLASS="COMMAND"
15245 >smbd</B
15246 > <EM
15247 >ALWAYS</EM
15248 >
15249                 uses a valid UNIX user to act on behalf of the client, even in
15250                 <B
15251 CLASS="COMMAND"
15252 >security = share</B
15253 > level security.</P
15254 ><P
15255 >As clients are not required to send a username to the server
15256                 in share level security, <B
15257 CLASS="COMMAND"
15258 >smbd</B
15259 > uses several
15260                 techniques to determine the correct UNIX user to use on behalf
15261                 of the client.</P
15262 ><P
15263 >A list of possible UNIX usernames to match with the given
15264                 client password is constructed using the following methods :</P
15265 ><P
15266 ></P
15267 ><UL
15268 ><LI
15269 ><P
15270 >If the <A
15271 HREF="#GUESTONLY"
15272 ><TT
15273 CLASS="PARAMETER"
15274 ><I
15275 >guest
15276                         only</I
15277 ></TT
15278 ></A
15279 > parameter is set, then all the other
15280                         stages are missed and only the <A
15281 HREF="#GUESTACCOUNT"
15282 >                       <TT
15283 CLASS="PARAMETER"
15284 ><I
15285 >guest account</I
15286 ></TT
15287 ></A
15288 > username is checked.
15289                         </P
15290 ></LI
15291 ><LI
15292 ><P
15293 >Is a username is sent with the share connection
15294                         request, then this username (after mapping - see <A
15295 HREF="#USERNAMEMAP"
15296 ><TT
15297 CLASS="PARAMETER"
15298 ><I
15299 >username map</I
15300 ></TT
15301 ></A
15302 >),
15303                         is added as a potential username.</P
15304 ></LI
15305 ><LI
15306 ><P
15307 >If the client did a previous <EM
15308 >logon
15309                         </EM
15310 > request (the SessionSetup SMB call) then the
15311                         username sent in this SMB will be added as a potential username.
15312                         </P
15313 ></LI
15314 ><LI
15315 ><P
15316 >The name of the service the client requested is
15317                         added as a potential username.</P
15318 ></LI
15319 ><LI
15320 ><P
15321 >The NetBIOS name of the client is added to
15322                         the list as a potential username.</P
15323 ></LI
15324 ><LI
15325 ><P
15326 >Any users on the <A
15327 HREF="#USER"
15328 ><TT
15329 CLASS="PARAMETER"
15330 ><I
15331 >                       user</I
15332 ></TT
15333 ></A
15334 > list are added as potential usernames.
15335                         </P
15336 ></LI
15337 ></UL
15338 ><P
15339 >If the <TT
15340 CLASS="PARAMETER"
15341 ><I
15342 >guest only</I
15343 ></TT
15344 > parameter is
15345                 not set, then this list is then tried with the supplied password.
15346                 The first user for whom the password matches will be used as the
15347                 UNIX user.</P
15348 ><P
15349 >If the <TT
15350 CLASS="PARAMETER"
15351 ><I
15352 >guest only</I
15353 ></TT
15354 > parameter is
15355                 set, or no username can be determined then if the share is marked
15356                 as available to the <TT
15357 CLASS="PARAMETER"
15358 ><I
15359 >guest account</I
15360 ></TT
15361 >, then this
15362                 guest user will be used, otherwise access is denied.</P
15363 ><P
15364 >Note that it can be <EM
15365 >very</EM
15366 > confusing
15367                 in share-level security as to which UNIX username will eventually
15368                 be used in granting access.</P
15369 ><P
15370 >See also the section <A
15371 HREF="#AEN235"
15372 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15373 >.</P
15374 ><P
15375 ><A
15376 NAME="SECURITYEQUALSUSER"
15377 ></A
15378 ><EM
15379 >SECURITY = USER
15380                 </EM
15381 ></P
15382 ><P
15383 >This is the default security setting in Samba 2.2.
15384                 With user-level security a client must first "log-on" with a
15385                 valid username and password (which can be mapped using the <A
15386 HREF="#USERNAMEMAP"
15387 ><TT
15388 CLASS="PARAMETER"
15389 ><I
15390 >username map</I
15391 ></TT
15392 ></A
15393 >
15394                 parameter). Encrypted passwords (see the <A
15395 HREF="#ENCRYPTPASSWORDS"
15396 >               <TT
15397 CLASS="PARAMETER"
15398 ><I
15399 >encrypted passwords</I
15400 ></TT
15401 ></A
15402 > parameter) can also
15403                 be used in this security mode. Parameters such as <A
15404 HREF="#USER"
15405 >               <TT
15406 CLASS="PARAMETER"
15407 ><I
15408 >user</I
15409 ></TT
15410 ></A
15411 > and <A
15412 HREF="#GUESTONLY"
15413 >               <TT
15414 CLASS="PARAMETER"
15415 ><I
15416 >guest only</I
15417 ></TT
15418 ></A
15419 > if set        are then applied and
15420                 may change the UNIX user to use on this connection, but only after
15421                 the user has been successfully authenticated.</P
15422 ><P
15423 ><EM
15424 >Note</EM
15425 > that the name of the resource being
15426                 requested is <EM
15427 >not</EM
15428 > sent to the server until after
15429                 the server has successfully authenticated the client. This is why
15430                 guest shares don't work in user level security without allowing
15431                 the server to automatically map unknown users into the <A
15432 HREF="#GUESTACCOUNT"
15433 ><TT
15434 CLASS="PARAMETER"
15435 ><I
15436 >guest account</I
15437 ></TT
15438 ></A
15439 >.
15440                 See the <A
15441 HREF="#MAPTOGUEST"
15442 ><TT
15443 CLASS="PARAMETER"
15444 ><I
15445 >map to guest</I
15446 ></TT
15447 >
15448                 </A
15449 > parameter for details on doing this.</P
15450 ><P
15451 >See also the section <A
15452 HREF="#AEN235"
15453 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15454 >.</P
15455 ><P
15456 ><A
15457 NAME="SECURITYEQUALSSERVER"
15458 ></A
15459 ><EM
15460 >SECURITY = SERVER
15461                 </EM
15462 ></P
15463 ><P
15464 >In this mode Samba will try to validate the username/password
15465                 by passing it to another SMB server, such as an NT box. If this
15466                 fails it will revert to <B
15467 CLASS="COMMAND"
15468 >security = user</B
15469 >, but note
15470                 that if encrypted passwords have been negotiated then Samba cannot
15471                 revert back to checking the UNIX password file, it must have a valid
15472                 <TT
15473 CLASS="FILENAME"
15474 >smbpasswd</TT
15475 > file to check users against. See the
15476                 documentation file in the <TT
15477 CLASS="FILENAME"
15478 >docs/</TT
15479 > directory
15480                 <TT
15481 CLASS="FILENAME"
15482 >ENCRYPTION.txt</TT
15483 > for details on how to set this
15484                 up.</P
15485 ><P
15486 ><EM
15487 >Note</EM
15488 > that from the client's point of
15489                 view <B
15490 CLASS="COMMAND"
15491 >security = server</B
15492 > is the same as <B
15493 CLASS="COMMAND"
15494 >               security = user</B
15495 >.  It only affects how the server deals
15496                 with the authentication, it does not in any way affect what the
15497                 client sees.</P
15498 ><P
15499 ><EM
15500 >Note</EM
15501 > that the name of the resource being
15502                 requested is <EM
15503 >not</EM
15504 > sent to the server until after
15505                 the server has successfully authenticated the client. This is why
15506                 guest shares don't work in user level security without allowing
15507                 the server to automatically map unknown users into the <A
15508 HREF="#GUESTACCOUNT"
15509 ><TT
15510 CLASS="PARAMETER"
15511 ><I
15512 >guest account</I
15513 ></TT
15514 ></A
15515 >.
15516                 See the <A
15517 HREF="#MAPTOGUEST"
15518 ><TT
15519 CLASS="PARAMETER"
15520 ><I
15521 >map to guest</I
15522 ></TT
15523 >
15524                 </A
15525 > parameter for details on doing this.</P
15526 ><P
15527 >See also the section <A
15528 HREF="#AEN235"
15529 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15530 >.</P
15531 ><P
15532 >See also the <A
15533 HREF="#PASSWORDSERVER"
15534 ><TT
15535 CLASS="PARAMETER"
15536 ><I
15537 >password
15538                 server</I
15539 ></TT
15540 ></A
15541 > parameter and the <A
15542 HREF="#ENCRYPTPASSWORDS"
15543 ><TT
15544 CLASS="PARAMETER"
15545 ><I
15546 >encrypted passwords</I
15547 ></TT
15548 >
15549                 </A
15550 > parameter.</P
15551 ><P
15552 ><A
15553 NAME="SECURITYEQUALSDOMAIN"
15554 ></A
15555 ><EM
15556 >SECURITY = DOMAIN
15557                 </EM
15558 ></P
15559 ><P
15560 >This mode will only work correctly if <A
15561 HREF="smbpasswd.8.html"
15562 TARGET="_top"
15563 >smbpasswd(8)</A
15564 > has been used to add this
15565                 machine into a Windows NT Domain. It expects the <A
15566 HREF="#ENCRYPTPASSWORDS"
15567 ><TT
15568 CLASS="PARAMETER"
15569 ><I
15570 >encrypted passwords</I
15571 ></TT
15572 >
15573                 </A
15574 > parameter to be set to <TT
15575 CLASS="CONSTANT"
15576 >true</TT
15577 >. In this
15578                 mode Samba will try to validate the username/password by passing
15579                 it to a Windows NT Primary or Backup Domain Controller, in exactly
15580                 the same way that a Windows NT Server would do.</P
15581 ><P
15582 ><EM
15583 >Note</EM
15584 > that a valid UNIX user must still
15585                 exist as well as the account on the Domain Controller to allow
15586                 Samba to have a valid UNIX account to map file access to.</P
15587 ><P
15588 ><EM
15589 >Note</EM
15590 > that from the client's point
15591                 of view <B
15592 CLASS="COMMAND"
15593 >security = domain</B
15594 > is the same as <B
15595 CLASS="COMMAND"
15596 >security = user
15597                 </B
15598 >. It only affects how the server deals with the authentication,
15599                 it does not in any way affect what the client sees.</P
15600 ><P
15601 ><EM
15602 >Note</EM
15603 > that the name of the resource being
15604                 requested is <EM
15605 >not</EM
15606 > sent to the server until after
15607                 the server has successfully authenticated the client. This is why
15608                 guest shares don't work in user level security without allowing
15609                 the server to automatically map unknown users into the <A
15610 HREF="#GUESTACCOUNT"
15611 ><TT
15612 CLASS="PARAMETER"
15613 ><I
15614 >guest account</I
15615 ></TT
15616 ></A
15617 >.
15618                 See the <A
15619 HREF="#MAPTOGUEST"
15620 ><TT
15621 CLASS="PARAMETER"
15622 ><I
15623 >map to guest</I
15624 ></TT
15625 >
15626                 </A
15627 > parameter for details on doing this.</P
15628 ><P
15629 ><EM
15630 >BUG:</EM
15631 > There is currently a bug in the
15632                 implementation of <B
15633 CLASS="COMMAND"
15634 >security = domain</B
15635 > with respect
15636                 to multi-byte character set usernames. The communication with a
15637                 Domain Controller must be done in UNICODE and Samba currently
15638                 does not widen multi-byte user names to UNICODE correctly, thus
15639                 a multi-byte username will not be recognized correctly at the
15640                 Domain Controller. This issue will be addressed in a future release.</P
15641 ><P
15642 >See also the section <A
15643 HREF="#AEN235"
15644 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15645 >.</P
15646 ><P
15647 >See also the <A
15648 HREF="#PASSWORDSERVER"
15649 ><TT
15650 CLASS="PARAMETER"
15651 ><I
15652 >password
15653                 server</I
15654 ></TT
15655 ></A
15656 > parameter and the <A
15657 HREF="#ENCRYPTPASSWORDS"
15658 ><TT
15659 CLASS="PARAMETER"
15660 ><I
15661 >encrypted passwords</I
15662 ></TT
15663 >
15664                 </A
15665 > parameter.</P
15666 ><P
15667 >Default: <B
15668 CLASS="COMMAND"
15669 >security = USER</B
15670 ></P
15671 ><P
15672 >Example: <B
15673 CLASS="COMMAND"
15674 >security = DOMAIN</B
15675 ></P
15676 ></DD
15677 ><DT
15678 ><A
15679 NAME="SECURITYMASK"
15680 ></A
15681 >security mask (S)</DT
15682 ><DD
15683 ><P
15684 >This parameter controls what UNIX permission
15685                 bits can be modified when a Windows NT client is manipulating
15686                 the UNIX permission on a file using the native NT security
15687                 dialog box.</P
15688 ><P
15689 >This parameter is applied as a mask (AND'ed with) to
15690                 the changed permission bits, thus preventing any bits not in
15691                 this mask from being modified. Essentially, zero bits in this
15692                 mask may be treated as a set of bits the user is not allowed
15693                 to change.</P
15694 ><P
15695 >If not set explicitly this parameter is 0777, allowing
15696                 a user to modify all the user/group/world permissions on a file.
15697                 </P
15698 ><P
15699 ><EM
15700 >Note</EM
15701 > that users who can access the
15702                 Samba server through other means can easily bypass this
15703                 restriction, so it is primarily useful for standalone
15704                 "appliance" systems.  Administrators of most normal systems will
15705                 probably want to leave it set to <TT
15706 CLASS="CONSTANT"
15707 >0777</TT
15708 >.</P
15709 ><P
15710 >See also the <A
15711 HREF="#FORCEDIRECTORYSECURITYMODE"
15712 >               <TT
15713 CLASS="PARAMETER"
15714 ><I
15715 >force directory security mode</I
15716 ></TT
15717 ></A
15718 >,
15719                 <A
15720 HREF="#DIRECTORYSECURITYMASK"
15721 ><TT
15722 CLASS="PARAMETER"
15723 ><I
15724 >directory
15725                 security mask</I
15726 ></TT
15727 ></A
15728 >, <A
15729 HREF="#FORCESECURITYMODE"
15730 >               <TT
15731 CLASS="PARAMETER"
15732 ><I
15733 >force security mode</I
15734 ></TT
15735 ></A
15736 > parameters.</P
15737 ><P
15738 >Default: <B
15739 CLASS="COMMAND"
15740 >security mask = 0777</B
15741 ></P
15742 ><P
15743 >Example: <B
15744 CLASS="COMMAND"
15745 >security mask = 0770</B
15746 ></P
15747 ></DD
15748 ><DT
15749 ><A
15750 NAME="SERVERSTRING"
15751 ></A
15752 >server string (G)</DT
15753 ><DD
15754 ><P
15755 >This controls what string will show up in the
15756                 printer comment box in print manager and next to the IPC connection
15757                 in <B
15758 CLASS="COMMAND"
15759 >net view</B
15760 >. It can be any string that you wish
15761                 to show to your users.</P
15762 ><P
15763 >It also sets what will appear in browse lists next
15764                 to the machine name.</P
15765 ><P
15766 >A <TT
15767 CLASS="PARAMETER"
15768 ><I
15769 >%v</I
15770 ></TT
15771 > will be replaced with the Samba
15772                 version number.</P
15773 ><P
15774 >A <TT
15775 CLASS="PARAMETER"
15776 ><I
15777 >%h</I
15778 ></TT
15779 > will be replaced with the
15780                 hostname.</P
15781 ><P
15782 >Default: <B
15783 CLASS="COMMAND"
15784 >server string = Samba %v</B
15785 ></P
15786 ><P
15787 >Example: <B
15788 CLASS="COMMAND"
15789 >server string = University of GNUs Samba
15790                 Server</B
15791 ></P
15792 ></DD
15793 ><DT
15794 ><A
15795 NAME="SETDIRECTORY"
15796 ></A
15797 >set directory (S)</DT
15798 ><DD
15799 ><P
15800 >If <B
15801 CLASS="COMMAND"
15802 >set directory = no</B
15803 >, then
15804                 users of the service may not use the setdir command to change
15805                 directory.</P
15806 ><P
15807 >The <B
15808 CLASS="COMMAND"
15809 >setdir</B
15810 > command is only implemented
15811                 in the Digital Pathworks client. See the Pathworks documentation
15812                 for details.</P
15813 ><P
15814 >Default: <B
15815 CLASS="COMMAND"
15816 >set directory = no</B
15817 ></P
15818 ></DD
15819 ><DT
15820 ><A
15821 NAME="SHORTPRESERVECASE"
15822 ></A
15823 >short preserve case (S)</DT
15824 ><DD
15825 ><P
15826 >This boolean parameter controls if new files
15827                 which conform to 8.3 syntax, that is all in upper case and of
15828                 suitable length, are created upper case, or if they are forced
15829                 to be the <A
15830 HREF="#DEFAULTCASE"
15831 ><TT
15832 CLASS="PARAMETER"
15833 ><I
15834 >default case
15835                 </I
15836 ></TT
15837 ></A
15838 >. This  option can be use with <A
15839 HREF="#PRESERVECASE"
15840 ><B
15841 CLASS="COMMAND"
15842 >preserve case = yes</B
15843 >
15844                 </A
15845 > to permit long filenames to retain their case, while short
15846                 names are lowered. </P
15847 ><P
15848 >See the section on <A
15849 HREF="#AEN202"
15850 >               NAME MANGLING</A
15851 >.</P
15852 ><P
15853 >Default: <B
15854 CLASS="COMMAND"
15855 >short preserve case = yes</B
15856 ></P
15857 ></DD
15858 ><DT
15859 ><A
15860 NAME="SHOWADDPRINTERWIZARD"
15861 ></A
15862 >show add printer wizard (G)</DT
15863 ><DD
15864 ><P
15865 >With the introduction of MS-RPC based printing support
15866                 for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will
15867                 appear on Samba hosts in the share listing.  Normally this folder will
15868                 contain an icon for the MS Add Printer Wizard (APW).  However, it is
15869                 possible to disable this feature regardless of the level of privilege
15870                 of the connected user.</P
15871 ><P
15872 >Under normal circumstances, the Windows NT/2000 client will
15873                 open a handle on the printer server with OpenPrinterEx() asking for
15874                 Administrator privileges.  If the user does not have administrative
15875                 access on the print server (i.e is not root or a member of the
15876                 <TT
15877 CLASS="PARAMETER"
15878 ><I
15879 >printer admin</I
15880 ></TT
15881 > group), the OpenPrinterEx()
15882                 call fails and the client makes another open call with a request for
15883                 a lower privilege level.  This should succeed, however the APW
15884                 icon will not be displayed.</P
15885 ><P
15886 >Disabling the <TT
15887 CLASS="PARAMETER"
15888 ><I
15889 >show add printer wizard</I
15890 ></TT
15891 >
15892                 parameter will always cause the OpenPrinterEx() on the server
15893                 to fail.  Thus the APW icon will never be displayed. <EM
15894 >               Note :</EM
15895 >This does not prevent the same user from having
15896                 administrative privilege on an individual printer.</P
15897 ><P
15898 >See also <A
15899 HREF="#ADDPRINTERCOMMAND"
15900 ><TT
15901 CLASS="PARAMETER"
15902 ><I
15903 >addprinter
15904                 command</I
15905 ></TT
15906 ></A
15907 >, <A
15908 HREF="#DELETEPRINTERCOMMAND"
15909 >               <TT
15910 CLASS="PARAMETER"
15911 ><I
15912 >deleteprinter command</I
15913 ></TT
15914 ></A
15915 >, <A
15916 HREF="#PRINTERADMIN"
15917 ><TT
15918 CLASS="PARAMETER"
15919 ><I
15920 >printer admin</I
15921 ></TT
15922 ></A
15923 ></P
15924 ><P
15925 >Default :<B
15926 CLASS="COMMAND"
15927 >show add printer wizard = yes</B
15928 ></P
15929 ></DD
15930 ><DT
15931 ><A
15932 NAME="SHUTDOWNSCRIPT"
15933 ></A
15934 >shutdown script (G)</DT
15935 ><DD
15936 ><P
15937 ><EM
15938 >This parameter only exists in the HEAD cvs branch</EM
15939 >
15940                 This a full path name to a script called by
15941                 <A
15942 HREF="smbd.8.html"
15943 TARGET="_top"
15944 ><B
15945 CLASS="COMMAND"
15946 >smbd(8)</B
15947 ></A
15948 > that
15949                 should start a shutdown procedure.</P
15950 ><P
15951 >This command will be run as the user connected to the
15952                 server.</P
15953 ><P
15954 >%m %t %r %f parameters are expanded</P
15955 ><P
15956 ><TT
15957 CLASS="PARAMETER"
15958 ><I
15959 >%m</I
15960 ></TT
15961 > will be substituted with the
15962                 shutdown message sent to the server.</P
15963 ><P
15964 ><TT
15965 CLASS="PARAMETER"
15966 ><I
15967 >%t</I
15968 ></TT
15969 > will be substituted with the
15970                 number of seconds to wait before effectively starting the
15971                 shutdown procedure.</P
15972 ><P
15973 ><TT
15974 CLASS="PARAMETER"
15975 ><I
15976 >%r</I
15977 ></TT
15978 > will be substituted with the
15979                 switch <EM
15980 >-r</EM
15981 >. It means reboot after shutdown
15982                 for NT.
15983                 </P
15984 ><P
15985 ><TT
15986 CLASS="PARAMETER"
15987 ><I
15988 >%f</I
15989 ></TT
15990 > will be substituted with the
15991                 switch <EM
15992 >-f</EM
15993 >. It means force the shutdown
15994                 even if applications do not respond for NT.</P
15995 ><P
15996 >Default: <EM
15997 >None</EM
15998 >.</P
15999 ><P
16000 >Example: <B
16001 CLASS="COMMAND"
16002 >abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f</B
16003 ></P
16004 ><P
16005 >Shutdown script example:
16006                 <TABLE
16007 BORDER="0"
16008 BGCOLOR="#E0E0E0"
16009 WIDTH="90%"
16010 ><TR
16011 ><TD
16012 ><PRE
16013 CLASS="PROGRAMLISTING"
16014 >               #!/bin/bash
16015
16016                 $time=0
16017                 let "time/60"
16018                 let "time++"
16019
16020                 /sbin/shutdown $3 $4 +$time $1 &#38;
16021                 </PRE
16022 ></TD
16023 ></TR
16024 ></TABLE
16025 >
16026                 Shutdown does not return so we need to launch it in background.
16027                 </P
16028 ><P
16029 >See also <A
16030 HREF="#ABORTSHUTDOWNSCRIPT"
16031 ><TT
16032 CLASS="PARAMETER"
16033 ><I
16034 >abort shutdown script</I
16035 ></TT
16036 ></A
16037 >.</P
16038 ></DD
16039 ><DT
16040 ><A
16041 NAME="SMBPASSWDFILE"
16042 ></A
16043 >smb passwd file (G)</DT
16044 ><DD
16045 ><P
16046 >This option sets the path to the encrypted
16047                 smbpasswd file.  By default the path to the smbpasswd file
16048                 is compiled into Samba.</P
16049 ><P
16050 >Default: <B
16051 CLASS="COMMAND"
16052 >smb passwd file = ${prefix}/private/smbpasswd
16053                 </B
16054 ></P
16055 ><P
16056 >Example: <B
16057 CLASS="COMMAND"
16058 >smb passwd file = /etc/samba/smbpasswd
16059                 </B
16060 ></P
16061 ></DD
16062 ><DT
16063 ><A
16064 NAME="SOCKETADDRESS"
16065 ></A
16066 >socket address (G)</DT
16067 ><DD
16068 ><P
16069 >This option allows you to control what
16070                 address Samba will listen for connections on. This is used to
16071                 support multiple virtual interfaces on the one server, each
16072                 with a different configuration.</P
16073 ><P
16074 >By default Samba will accept connections on any
16075                 address.</P
16076 ><P
16077 >Example: <B
16078 CLASS="COMMAND"
16079 >socket address = 192.168.2.20</B
16080 >
16081                 </P
16082 ></DD
16083 ><DT
16084 ><A
16085 NAME="SOCKETOPTIONS"
16086 ></A
16087 >socket options (G)</DT
16088 ><DD
16089 ><P
16090 >This option allows you to set socket options
16091                 to be used when talking with the client.</P
16092 ><P
16093 >Socket options are controls on the networking layer
16094                 of the operating systems which allow the connection to be
16095                 tuned.</P
16096 ><P
16097 >This option will typically be used to tune your Samba
16098                 server for optimal performance for your local network. There is
16099                 no way that Samba can know what the optimal parameters are for
16100                 your net, so you must experiment and choose them yourself. We
16101                 strongly suggest you read the appropriate documentation for your
16102                 operating system first (perhaps <B
16103 CLASS="COMMAND"
16104 >man setsockopt</B
16105 >
16106                 will help).</P
16107 ><P
16108 >You may find that on some systems Samba will say
16109                 "Unknown socket option" when you supply an option. This means you
16110                 either incorrectly  typed it or you need to add an include file
16111                 to includes.h for your OS.  If the latter is the case please
16112                 send the patch to <A
16113 HREF="mailto:samba@samba.org"
16114 TARGET="_top"
16115 >               samba@samba.org</A
16116 >.</P
16117 ><P
16118 >Any of the supported socket options may be combined
16119                 in any way you like, as long as your OS allows it.</P
16120 ><P
16121 >This is the list of socket options currently settable
16122                 using this option:</P
16123 ><P
16124 ></P
16125 ><UL
16126 ><LI
16127 ><P
16128 >SO_KEEPALIVE</P
16129 ></LI
16130 ><LI
16131 ><P
16132 >SO_REUSEADDR</P
16133 ></LI
16134 ><LI
16135 ><P
16136 >SO_BROADCAST</P
16137 ></LI
16138 ><LI
16139 ><P
16140 >TCP_NODELAY</P
16141 ></LI
16142 ><LI
16143 ><P
16144 >IPTOS_LOWDELAY</P
16145 ></LI
16146 ><LI
16147 ><P
16148 >IPTOS_THROUGHPUT</P
16149 ></LI
16150 ><LI
16151 ><P
16152 >SO_SNDBUF *</P
16153 ></LI
16154 ><LI
16155 ><P
16156 >SO_RCVBUF *</P
16157 ></LI
16158 ><LI
16159 ><P
16160 >SO_SNDLOWAT *</P
16161 ></LI
16162 ><LI
16163 ><P
16164 >SO_RCVLOWAT *</P
16165 ></LI
16166 ></UL
16167 ><P
16168 >Those marked with a <EM
16169 >'*'</EM
16170 > take an integer
16171                 argument. The others can optionally take a 1 or 0 argument to enable
16172                 or disable the option, by default they will be enabled if you
16173                 don't specify 1 or 0.</P
16174 ><P
16175 >To specify an argument use the syntax SOME_OPTION = VALUE
16176                 for example <B
16177 CLASS="COMMAND"
16178 >SO_SNDBUF = 8192</B
16179 >. Note that you must
16180                 not have any spaces before or after the = sign.</P
16181 ><P
16182 >If you are on a local network then a sensible option
16183                 might be</P
16184 ><P
16185 ><B
16186 CLASS="COMMAND"
16187 >socket options = IPTOS_LOWDELAY</B
16188 ></P
16189 ><P
16190 >If you have a local network then you could try:</P
16191 ><P
16192 ><B
16193 CLASS="COMMAND"
16194 >socket options = IPTOS_LOWDELAY TCP_NODELAY</B
16195 ></P
16196 ><P
16197 >If you are on a wide area network then perhaps try
16198                 setting IPTOS_THROUGHPUT. </P
16199 ><P
16200 >Note that several of the options may cause your Samba
16201                 server to fail completely. Use these options with caution!</P
16202 ><P
16203 >Default: <B
16204 CLASS="COMMAND"
16205 >socket options = TCP_NODELAY</B
16206 ></P
16207 ><P
16208 >Example: <B
16209 CLASS="COMMAND"
16210 >socket options = IPTOS_LOWDELAY</B
16211 ></P
16212 ></DD
16213 ><DT
16214 ><A
16215 NAME="SOURCEENVIRONMENT"
16216 ></A
16217 >source environment (G)</DT
16218 ><DD
16219 ><P
16220 >This parameter causes Samba to set environment
16221                 variables as per the content of the file named.</P
16222 ><P
16223 >If the value of this parameter starts with a "|" character
16224                 then Samba will treat that value as a pipe command to open and
16225                 will set the environment variables from the output of the pipe.</P
16226 ><P
16227 >The contents of the file or the output of the pipe should
16228                 be formatted as the output of the standard Unix <B
16229 CLASS="COMMAND"
16230 >env(1)
16231                 </B
16232 > command. This is of the form :</P
16233 ><P
16234 >Example environment entry:</P
16235 ><P
16236 ><B
16237 CLASS="COMMAND"
16238 >SAMBA_NETBIOS_NAME = myhostname</B
16239 ></P
16240 ><P
16241 >Default: <EM
16242 >No default value</EM
16243 ></P
16244 ><P
16245 >Examples: <B
16246 CLASS="COMMAND"
16247 >source environment = |/etc/smb.conf.sh
16248                 </B
16249 ></P
16250 ><P
16251 >Example: <B
16252 CLASS="COMMAND"
16253 >source environment =
16254                 /usr/local/smb_env_vars</B
16255 ></P
16256 ></DD
16257 ><DT
16258 ><A
16259 NAME="SSL"
16260 ></A
16261 >ssl (G)</DT
16262 ><DD
16263 ><P
16264 >This variable is part of SSL-enabled Samba. This
16265                 is only available if the SSL libraries have been compiled on your
16266                 system and the configure option <B
16267 CLASS="COMMAND"
16268 >--with-ssl</B
16269 > was
16270                 given at configure time.</P
16271 ><P
16272 ><EM
16273 >Note</EM
16274 > that for export control reasons
16275                 this code is <EM
16276 >NOT</EM
16277 > enabled by default in any
16278                 current binary version of Samba.</P
16279 ><P
16280 >This variable enables or disables the entire SSL mode. If
16281                 it is set to <TT
16282 CLASS="CONSTANT"
16283 >no</TT
16284 >, the SSL-enabled Samba behaves
16285                 exactly like the non-SSL Samba. If set to <TT
16286 CLASS="CONSTANT"
16287 >yes</TT
16288 >,
16289                 it depends on the variables <A
16290 HREF="#SSLHOSTS"
16291 ><TT
16292 CLASS="PARAMETER"
16293 ><I
16294 >               ssl hosts</I
16295 ></TT
16296 ></A
16297 > and <A
16298 HREF="#SSLHOSTSRESIGN"
16299 >               <TT
16300 CLASS="PARAMETER"
16301 ><I
16302 >ssl hosts resign</I
16303 ></TT
16304 ></A
16305 > whether an SSL
16306                 connection will be required.</P
16307 ><P
16308 >Default: <B
16309 CLASS="COMMAND"
16310 >ssl = no</B
16311 ></P
16312 ></DD
16313 ><DT
16314 ><A
16315 NAME="SSLCACERTDIR"
16316 ></A
16317 >ssl CA certDir (G)</DT
16318 ><DD
16319 ><P
16320 >This variable is part of SSL-enabled Samba. This
16321                 is only available if the SSL libraries have been compiled on your
16322                 system and the configure option <B
16323 CLASS="COMMAND"
16324 >--with-ssl</B
16325 > was
16326                 given at configure time.</P
16327 ><P
16328 ><EM
16329 >Note</EM
16330 > that for export control reasons
16331                 this code is <EM
16332 >NOT</EM
16333 > enabled by default in any
16334                 current binary version of Samba.</P
16335 ><P
16336 >This variable defines where to look up the Certification
16337                 Authorities. The given directory should contain one file for
16338                 each CA that Samba will trust.  The file name must be the hash
16339                 value over the "Distinguished Name" of the CA. How this directory
16340                 is set up is explained later in this document. All files within the
16341                 directory that don't fit into this naming scheme are ignored. You
16342                 don't need this variable if you don't verify client certificates.</P
16343 ><P
16344 >Default: <B
16345 CLASS="COMMAND"
16346 >ssl CA certDir = /usr/local/ssl/certs
16347                 </B
16348 ></P
16349 ></DD
16350 ><DT
16351 ><A
16352 NAME="SSLCACERTFILE"
16353 ></A
16354 >ssl CA certFile (G)</DT
16355 ><DD
16356 ><P
16357 >This variable is part of SSL-enabled Samba. This
16358                 is only available if the SSL libraries have been compiled on your
16359                 system and the configure option <B
16360 CLASS="COMMAND"
16361 >--with-ssl</B
16362 > was
16363                 given at configure time.</P
16364 ><P
16365 ><EM
16366 >Note</EM
16367 > that for export control reasons
16368                 this code is <EM
16369 >NOT</EM
16370 > enabled by default in any
16371                 current binary version of Samba.</P
16372 ><P
16373 >This variable is a second way to define the trusted CAs.
16374                 The certificates of the trusted CAs are collected in one big
16375                 file and this variable points to the file. You will probably
16376                 only use one of the two ways to define your CAs. The first choice is
16377                 preferable if you have many CAs or want to be flexible, the second
16378                 is preferable if you only have one CA and want to keep things
16379                 simple (you won't need to create the hashed file names). You
16380                 don't need this variable if you don't verify client certificates.</P
16381 ><P
16382 >Default: <B
16383 CLASS="COMMAND"
16384 >ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem
16385                 </B
16386 ></P
16387 ></DD
16388 ><DT
16389 ><A
16390 NAME="SSLCIPHERS"
16391 ></A
16392 >ssl ciphers (G)</DT
16393 ><DD
16394 ><P
16395 >This variable is part of SSL-enabled Samba. This
16396                 is only available if the SSL libraries have been compiled on your
16397                 system and the configure option <B
16398 CLASS="COMMAND"
16399 >--with-ssl</B
16400 > was
16401                 given at configure time.</P
16402 ><P
16403 ><EM
16404 >Note</EM
16405 > that for export control reasons
16406                 this code is <EM
16407 >NOT</EM
16408 > enabled by default in any
16409                 current binary version of Samba.</P
16410 ><P
16411 >This variable defines the ciphers that should be offered
16412                 during SSL negotiation. You should not set this variable unless
16413                 you know what you are doing.</P
16414 ></DD
16415 ><DT
16416 ><A
16417 NAME="SSLCLIENTCERT"
16418 ></A
16419 >ssl client cert (G)</DT
16420 ><DD
16421 ><P
16422 >This variable is part of SSL-enabled Samba. This
16423                 is only available if the SSL libraries have been compiled on your
16424                 system and the configure option <B
16425 CLASS="COMMAND"
16426 >--with-ssl</B
16427 > was
16428                 given at configure time.</P
16429 ><P
16430 ><EM
16431 >Note</EM
16432 > that for export control reasons
16433                 this code is <EM
16434 >NOT</EM
16435 > enabled by default in any
16436                 current binary version of Samba.</P
16437 ><P
16438 >The certificate in this file is used by <A
16439 HREF="smbclient.1.html"
16440 TARGET="_top"
16441 >               <B
16442 CLASS="COMMAND"
16443 >smbclient(1)</B
16444 ></A
16445 > if it exists. It's needed
16446                 if the server requires a client certificate.</P
16447 ><P
16448 >Default: <B
16449 CLASS="COMMAND"
16450 >ssl client cert = /usr/local/ssl/certs/smbclient.pem
16451                 </B
16452 ></P
16453 ></DD
16454 ><DT
16455 ><A
16456 NAME="SSLCLIENTKEY"
16457 ></A
16458 >ssl client key (G)</DT
16459 ><DD
16460 ><P
16461 >This variable is part of SSL-enabled Samba. This
16462                 is only available if the SSL libraries have been compiled on your
16463                 system and the configure option <B
16464 CLASS="COMMAND"
16465 >--with-ssl</B
16466 > was
16467                 given at configure time.</P
16468 ><P
16469 ><EM
16470 >Note</EM
16471 > that for export control reasons
16472                 this code is <EM
16473 >NOT</EM
16474 > enabled by default in any
16475                 current binary version of Samba.</P
16476 ><P
16477 >This is the private key for <A
16478 HREF="smbclient.1.html"
16479 TARGET="_top"
16480 >               <B
16481 CLASS="COMMAND"
16482 >smbclient(1)</B
16483 ></A
16484 >. It's only needed if the
16485                 client should have a certificate. </P
16486 ><P
16487 >Default: <B
16488 CLASS="COMMAND"
16489 >ssl client key = /usr/local/ssl/private/smbclient.pem
16490                 </B
16491 ></P
16492 ></DD
16493 ><DT
16494 ><A
16495 NAME="SSLCOMPATIBILITY"
16496 ></A
16497 >ssl compatibility (G)</DT
16498 ><DD
16499 ><P
16500 >This variable is part of SSL-enabled Samba. This
16501                 is only available if the SSL libraries have been compiled on your
16502                 system and the configure option <B
16503 CLASS="COMMAND"
16504 >--with-ssl</B
16505 > was
16506                 given at configure time.</P
16507 ><P
16508 ><EM
16509 >Note</EM
16510 > that for export control reasons
16511                 this code is <EM
16512 >NOT</EM
16513 > enabled by default in any
16514                 current binary version of Samba.</P
16515 ><P
16516 >This variable defines whether SSLeay should be configured
16517                 for bug compatibility with other SSL implementations. This is
16518                 probably not desirable because currently no clients with SSL
16519                 implementations other than SSLeay exist.</P
16520 ><P
16521 >Default: <B
16522 CLASS="COMMAND"
16523 >ssl compatibility = no</B
16524 ></P
16525 ></DD
16526 ><DT
16527 ><A
16528 NAME="SSLHOSTS"
16529 ></A
16530 >ssl hosts (G)</DT
16531 ><DD
16532 ><P
16533 >See <A
16534 HREF="#SSLHOSTSRESIGN"
16535 ><TT
16536 CLASS="PARAMETER"
16537 ><I
16538 >               ssl hosts resign</I
16539 ></TT
16540 ></A
16541 >.</P
16542 ></DD
16543 ><DT
16544 ><A
16545 NAME="SSLHOSTSRESIGN"
16546 ></A
16547 >ssl hosts resign (G)</DT
16548 ><DD
16549 ><P
16550 >This variable is part of SSL-enabled Samba. This
16551                 is only available if the SSL libraries have been compiled on your
16552                 system and the configure option <B
16553 CLASS="COMMAND"
16554 >--with-ssl</B
16555 > was
16556                 given at configure time.</P
16557 ><P
16558 ><EM
16559 >Note</EM
16560 > that for export control reasons
16561                 this code is <EM
16562 >NOT</EM
16563 > enabled by default in any
16564                 current binary version of Samba.</P
16565 ><P
16566 >These two variables define whether Samba will go
16567                 into SSL mode or not. If none of them is defined, Samba will
16568                 allow only SSL connections. If the <A
16569 HREF="#SSLHOSTS"
16570 >               <TT
16571 CLASS="PARAMETER"
16572 ><I
16573 >ssl hosts</I
16574 ></TT
16575 ></A
16576 > variable lists
16577                 hosts (by IP-address, IP-address range, net group or name),
16578                 only these hosts will be forced into SSL mode. If the <TT
16579 CLASS="PARAMETER"
16580 ><I
16581 >               ssl hosts resign</I
16582 ></TT
16583 > variable lists hosts, only these
16584                 hosts will <EM
16585 >NOT</EM
16586 > be forced into SSL mode. The syntax for these two
16587                 variables is the same as for the <A
16588 HREF="#HOSTSALLOW"
16589 ><TT
16590 CLASS="PARAMETER"
16591 ><I
16592 >               hosts allow</I
16593 ></TT
16594 ></A
16595 > and <A
16596 HREF="#HOSTSDENY"
16597 >               <TT
16598 CLASS="PARAMETER"
16599 ><I
16600 >hosts deny</I
16601 ></TT
16602 ></A
16603 > pair of variables, only
16604                 that the subject of the decision is different: It's not the access
16605                 right but whether SSL is used or not. </P
16606 ><P
16607 >The example below requires SSL connections from all hosts
16608                 outside the local net (which is 192.168.*.*).</P
16609 ><P
16610 >Default: <B
16611 CLASS="COMMAND"
16612 >ssl hosts = &#60;empty string&#62;</B
16613 ></P
16614 ><P
16615 ><B
16616 CLASS="COMMAND"
16617 >ssl hosts resign = &#60;empty string&#62;</B
16618 ></P
16619 ><P
16620 >Example: <B
16621 CLASS="COMMAND"
16622 >ssl hosts resign = 192.168.</B
16623 ></P
16624 ></DD
16625 ><DT
16626 ><A
16627 NAME="SSLREQUIRECLIENTCERT"
16628 ></A
16629 >ssl require clientcert (G)</DT
16630 ><DD
16631 ><P
16632 >This variable is part of SSL-enabled Samba. This
16633                 is only available if the SSL libraries have been compiled on your
16634                 system and the configure option <B
16635 CLASS="COMMAND"
16636 >--with-ssl</B
16637 > was
16638                 given at configure time.</P
16639 ><P
16640 ><EM
16641 >Note</EM
16642 > that for export control reasons
16643                 this code is <EM
16644 >NOT</EM
16645 > enabled by default in any
16646                 current binary version of Samba.</P
16647 ><P
16648 >If this variable is set to <TT
16649 CLASS="CONSTANT"
16650 >yes</TT
16651 >, the
16652                 server will not tolerate connections from clients that don't
16653                 have a valid certificate. The directory/file given in <A
16654 HREF="#SSLCACERTDIR"
16655 ><TT
16656 CLASS="PARAMETER"
16657 ><I
16658 >ssl CA certDir</I
16659 ></TT
16660 >
16661                 </A
16662 > and <A
16663 HREF="#SSLCACERTFILE"
16664 ><TT
16665 CLASS="PARAMETER"
16666 ><I
16667 >ssl CA certFile
16668                 </I
16669 ></TT
16670 ></A
16671 > will be used to look up the CAs that issued
16672                 the client's certificate. If the certificate can't be verified
16673                 positively, the connection will be terminated.  If this variable
16674                 is set to <TT
16675 CLASS="CONSTANT"
16676 >no</TT
16677 >, clients don't need certificates.
16678                 Contrary to web applications you really <EM
16679 >should</EM
16680 >
16681                 require client certificates. In the web environment the client's
16682                 data is sensitive (credit card numbers) and the server must prove
16683                 to be trustworthy. In a file server environment the server's data
16684                 will be sensitive and the clients must prove to be trustworthy.</P
16685 ><P
16686 >Default: <B
16687 CLASS="COMMAND"
16688 >ssl require clientcert = no</B
16689 ></P
16690 ></DD
16691 ><DT
16692 ><A
16693 NAME="SSLREQUIRESERVERCERT"
16694 ></A
16695 >ssl require servercert (G)</DT
16696 ><DD
16697 ><P
16698 >This variable is part of SSL-enabled Samba. This
16699                 is only available if the SSL libraries have been compiled on your
16700                 system and the configure option <B
16701 CLASS="COMMAND"
16702 >--with-ssl</B
16703 > was
16704                 given at configure time.</P
16705 ><P
16706 ><EM
16707 >Note</EM
16708 > that for export control reasons
16709                 this code is <EM
16710 >NOT</EM
16711 > enabled by default in any
16712                 current binary version of Samba.</P
16713 ><P
16714 >If this variable is set to <TT
16715 CLASS="CONSTANT"
16716 >yes</TT
16717 >, the
16718                 <A
16719 HREF="smbclient.1.html"
16720 TARGET="_top"
16721 ><B
16722 CLASS="COMMAND"
16723 >smbclient(1)</B
16724 >
16725                 </A
16726 > will request a certificate from the server. Same as
16727                 <A
16728 HREF="#SSLREQUIRECLIENTCERT"
16729 ><TT
16730 CLASS="PARAMETER"
16731 ><I
16732 >ssl require
16733                 clientcert</I
16734 ></TT
16735 ></A
16736 > for the server.</P
16737 ><P
16738 >Default: <B
16739 CLASS="COMMAND"
16740 >ssl require servercert = no</B
16741 >
16742                 </P
16743 ></DD
16744 ><DT
16745 ><A
16746 NAME="SSLSERVERCERT"
16747 ></A
16748 >ssl server cert (G)</DT
16749 ><DD
16750 ><P
16751 >This variable is part of SSL-enabled Samba. This
16752                 is only available if the SSL libraries have been compiled on your
16753                 system and the configure option <B
16754 CLASS="COMMAND"
16755 >--with-ssl</B
16756 > was
16757                 given at configure time.</P
16758 ><P
16759 ><EM
16760 >Note</EM
16761 > that for export control reasons
16762                 this code is <EM
16763 >NOT</EM
16764 > enabled by default in any
16765                 current binary version of Samba.</P
16766 ><P
16767 >This is the file containing the server's certificate.
16768                 The server <EM
16769 >must</EM
16770 > have a certificate. The
16771                 file may also contain the server's private key. See later for
16772                 how certificates and private keys are created.</P
16773 ><P
16774 >Default: <B
16775 CLASS="COMMAND"
16776 >ssl server cert = &#60;empty string&#62;
16777                 </B
16778 ></P
16779 ></DD
16780 ><DT
16781 ><A
16782 NAME="SSLSERVERKEY"
16783 ></A
16784 >ssl server key (G)</DT
16785 ><DD
16786 ><P
16787 >This variable is part of SSL-enabled Samba. This
16788                 is only available if the SSL libraries have been compiled on your
16789                 system and the configure option <B
16790 CLASS="COMMAND"
16791 >--with-ssl</B
16792 > was
16793                 given at configure time.</P
16794 ><P
16795 ><EM
16796 >Note</EM
16797 > that for export control reasons
16798                 this code is <EM
16799 >NOT</EM
16800 > enabled by default in any
16801                 current binary version of Samba.</P
16802 ><P
16803 >This file contains the private key of the server. If
16804                 this variable is not defined, the key is looked up in the
16805                 certificate file (it may be appended to the certificate).
16806                 The server <EM
16807 >must</EM
16808 > have a private key
16809                 and the certificate <EM
16810 >must</EM
16811 >
16812                 match this private key.</P
16813 ><P
16814 >Default: <B
16815 CLASS="COMMAND"
16816 >ssl server key = &#60;empty string&#62;
16817                 </B
16818 ></P
16819 ></DD
16820 ><DT
16821 ><A
16822 NAME="SSLVERSION"
16823 ></A
16824 >ssl version (G)</DT
16825 ><DD
16826 ><P
16827 >This variable is part of SSL-enabled Samba. This
16828                 is only available if the SSL libraries have been compiled on your
16829                 system and the configure option <B
16830 CLASS="COMMAND"
16831 >--with-ssl</B
16832 > was
16833                 given at configure time.</P
16834 ><P
16835 ><EM
16836 >Note</EM
16837 > that for export control reasons
16838                 this code is <EM
16839 >NOT</EM
16840 > enabled by default in any
16841                 current binary version of Samba.</P
16842 ><P
16843 >This enumeration variable defines the versions of the
16844                 SSL protocol that will be used. <TT
16845 CLASS="CONSTANT"
16846 >ssl2or3</TT
16847 > allows
16848                 dynamic negotiation of SSL v2 or v3, <TT
16849 CLASS="CONSTANT"
16850 >ssl2</TT
16851 > results
16852                 in SSL v2, <TT
16853 CLASS="CONSTANT"
16854 >ssl3</TT
16855 > results in SSL v3 and
16856                 <TT
16857 CLASS="CONSTANT"
16858 >tls1</TT
16859 > results in TLS v1. TLS (Transport Layer
16860                 Security) is the new standard for SSL.</P
16861 ><P
16862 >Default: <B
16863 CLASS="COMMAND"
16864 >ssl version = "ssl2or3"</B
16865 ></P
16866 ></DD
16867 ><DT
16868 ><A
16869 NAME="STATCACHE"
16870 ></A
16871 >stat cache (G)</DT
16872 ><DD
16873 ><P
16874 >This parameter determines if <A
16875 HREF="smbd.8.html"
16876 TARGET="_top"
16877 >smbd(8)</A
16878 > will use a cache in order to
16879                 speed up case insensitive name mappings. You should never need
16880                 to change this parameter.</P
16881 ><P
16882 >Default: <B
16883 CLASS="COMMAND"
16884 >stat cache = yes</B
16885 ></P
16886 ></DD
16887 ><DT
16888 ><A
16889 NAME="STATCACHESIZE"
16890 ></A
16891 >stat cache size (G)</DT
16892 ><DD
16893 ><P
16894 >This parameter determines the number of
16895                 entries in the <TT
16896 CLASS="PARAMETER"
16897 ><I
16898 >stat cache</I
16899 ></TT
16900 >.  You should
16901                 never need to change this parameter.</P
16902 ><P
16903 >Default: <B
16904 CLASS="COMMAND"
16905 >stat cache size = 50</B
16906 ></P
16907 ></DD
16908 ><DT
16909 ><A
16910 NAME="STATUS"
16911 ></A
16912 >status (G)</DT
16913 ><DD
16914 ><P
16915 >This enables or disables logging of connections
16916                 to a status file that <A
16917 HREF="smbstatus.1.html"
16918 TARGET="_top"
16919 >smbstatus(1)</A
16920 >
16921                 can read.</P
16922 ><P
16923 >With this disabled <B
16924 CLASS="COMMAND"
16925 >smbstatus</B
16926 > won't be able
16927                 to tell you what connections are active. You should never need to
16928                 change this parameter.</P
16929 ><P
16930 >Default: <B
16931 CLASS="COMMAND"
16932 >status = yes</B
16933 ></P
16934 ></DD
16935 ><DT
16936 ><A
16937 NAME="STRICTLOCKING"
16938 ></A
16939 >strict locking (S)</DT
16940 ><DD
16941 ><P
16942 >This is a boolean that controls the handling of
16943                 file locking in the server. When this is set to <TT
16944 CLASS="CONSTANT"
16945 >yes</TT
16946 >
16947                 the server will check every read and write access for file locks, and
16948                 deny access if locks exist. This can be slow on some systems.</P
16949 ><P
16950 >When strict locking is <TT
16951 CLASS="CONSTANT"
16952 >no</TT
16953 > the server does file
16954                 lock checks only when the client explicitly asks for them.</P
16955 ><P
16956 >Well-behaved clients always ask for lock checks when it
16957                 is important, so in the vast majority of cases <B
16958 CLASS="COMMAND"
16959 >strict
16960                 locking = no</B
16961 > is preferable.</P
16962 ><P
16963 >Default: <B
16964 CLASS="COMMAND"
16965 >strict locking = no</B
16966 ></P
16967 ></DD
16968 ><DT
16969 ><A
16970 NAME="STRICTSYNC"
16971 ></A
16972 >strict sync (S)</DT
16973 ><DD
16974 ><P
16975 >Many Windows applications (including the Windows
16976                 98 explorer shell) seem to confuse flushing buffer contents to
16977                 disk with doing a sync to disk. Under UNIX, a sync call forces
16978                 the process to be suspended until the kernel has ensured that
16979                 all outstanding data in kernel disk buffers has been safely stored
16980                 onto stable storage. This is very slow and should only be done
16981                 rarely. Setting this parameter to <TT
16982 CLASS="CONSTANT"
16983 >no</TT
16984 > (the
16985                 default) means that <A
16986 HREF="smbd.8.html"
16987 TARGET="_top"
16988 >smbd</A
16989 > ignores the Windows applications requests for
16990                 a sync call. There is only a possibility of losing data if the
16991                 operating system itself that Samba is running on crashes, so there is
16992                 little danger in this default setting. In addition, this fixes many
16993                 performance problems that people have reported with the new Windows98
16994                 explorer shell file copies.</P
16995 ><P
16996 >See also the <A
16997 HREF="#SYNCALWAYS"
16998 ><TT
16999 CLASS="PARAMETER"
17000 ><I
17001 >sync
17002                 always&#62;</I
17003 ></TT
17004 ></A
17005 > parameter.</P
17006 ><P
17007 >Default: <B
17008 CLASS="COMMAND"
17009 >strict sync = no</B
17010 ></P
17011 ></DD
17012 ><DT
17013 ><A
17014 NAME="STRIPDOT"
17015 ></A
17016 >strip dot (G)</DT
17017 ><DD
17018 ><P
17019 >This is a boolean that controls whether to
17020                 strip trailing dots off UNIX filenames. This helps with some
17021                 CDROMs that have filenames ending in a single dot.</P
17022 ><P
17023 >Default: <B
17024 CLASS="COMMAND"
17025 >strip dot = no</B
17026 ></P
17027 ></DD
17028 ><DT
17029 ><A
17030 NAME="SYNCALWAYS"
17031 ></A
17032 >sync always (S)</DT
17033 ><DD
17034 ><P
17035 >This is a boolean parameter that controls
17036                 whether writes will always be written to stable storage before
17037                 the write call returns. If this is <TT
17038 CLASS="CONSTANT"
17039 >false</TT
17040 > then the server will be
17041                 guided by the client's request in each write call (clients can
17042                 set a bit indicating that a particular write should be synchronous).
17043                 If this is <TT
17044 CLASS="CONSTANT"
17045 >true</TT
17046 > then every write will be followed by a <B
17047 CLASS="COMMAND"
17048 >fsync()
17049                 </B
17050 > call to ensure the data is written to disk. Note that
17051                 the <TT
17052 CLASS="PARAMETER"
17053 ><I
17054 >strict sync</I
17055 ></TT
17056 > parameter must be set to
17057                 <TT
17058 CLASS="CONSTANT"
17059 >yes</TT
17060 > in order for this parameter to have
17061                 any affect.</P
17062 ><P
17063 >See also the <A
17064 HREF="#STRICTSYNC"
17065 ><TT
17066 CLASS="PARAMETER"
17067 ><I
17068 >strict
17069                 sync</I
17070 ></TT
17071 ></A
17072 > parameter.</P
17073 ><P
17074 >Default: <B
17075 CLASS="COMMAND"
17076 >sync always = no</B
17077 ></P
17078 ></DD
17079 ><DT
17080 ><A
17081 NAME="SYSLOG"
17082 ></A
17083 >syslog (G)</DT
17084 ><DD
17085 ><P
17086 >This parameter maps how Samba debug messages
17087                 are logged onto the system syslog logging levels. Samba debug
17088                 level zero maps onto syslog <TT
17089 CLASS="CONSTANT"
17090 >LOG_ERR</TT
17091 >, debug
17092                 level one maps onto <TT
17093 CLASS="CONSTANT"
17094 >LOG_WARNING</TT
17095 >, debug level
17096                 two maps onto <TT
17097 CLASS="CONSTANT"
17098 >LOG_NOTICE</TT
17099 >, debug level three
17100                 maps onto LOG_INFO. All higher levels are mapped to <TT
17101 CLASS="CONSTANT"
17102 >               LOG_DEBUG</TT
17103 >.</P
17104 ><P
17105 >This parameter sets the threshold for sending messages
17106                 to syslog.  Only messages with debug level less than this value
17107                 will be sent to syslog.</P
17108 ><P
17109 >Default: <B
17110 CLASS="COMMAND"
17111 >syslog = 1</B
17112 ></P
17113 ></DD
17114 ><DT
17115 ><A
17116 NAME="SYSLOGONLY"
17117 ></A
17118 >syslog only (G)</DT
17119 ><DD
17120 ><P
17121 >If this parameter is set then Samba debug
17122                 messages are logged into the system syslog only, and not to
17123                 the debug log files.</P
17124 ><P
17125 >Default: <B
17126 CLASS="COMMAND"
17127 >syslog only = no</B
17128 ></P
17129 ></DD
17130 ><DT
17131 ><A
17132 NAME="TEMPLATEHOMEDIR"
17133 ></A
17134 >template homedir (G)</DT
17135 ><DD
17136 ><P
17137 >When filling out the user information for a Windows NT
17138                 user, the <A
17139 HREF="winbindd.8.html"
17140 TARGET="_top"
17141 >winbindd(8)</A
17142 > daemon
17143                 uses this parameter to fill in the home directory for that user.
17144                 If the string <TT
17145 CLASS="PARAMETER"
17146 ><I
17147 >%D</I
17148 ></TT
17149 > is present it is substituted
17150                 with the user's Windows NT domain name.  If the string <TT
17151 CLASS="PARAMETER"
17152 ><I
17153 >%U
17154                 </I
17155 ></TT
17156 > is present it is substituted with the user's Windows
17157                 NT user name.</P
17158 ><P
17159 >Default: <B
17160 CLASS="COMMAND"
17161 >template homedir = /home/%D/%U</B
17162 ></P
17163 ></DD
17164 ><DT
17165 ><A
17166 NAME="TEMPLATESHELL"
17167 ></A
17168 >template shell (G)</DT
17169 ><DD
17170 ><P
17171 >When filling out the user information for a Windows NT
17172                 user, the <A
17173 HREF="winbindd.8.html"
17174 TARGET="_top"
17175 >winbindd(8)</A
17176 > daemon
17177                 uses this parameter to fill in the login shell for that user.</P
17178 ><P
17179 >Default: <B
17180 CLASS="COMMAND"
17181 >template shell = /bin/false</B
17182 ></P
17183 ></DD
17184 ><DT
17185 ><A
17186 NAME="TIMEOFFSET"
17187 ></A
17188 >time offset (G)</DT
17189 ><DD
17190 ><P
17191 >This parameter is a setting in minutes to add
17192                 to the normal GMT to local time conversion. This is useful if
17193                 you are serving a lot of PCs that have incorrect daylight
17194                 saving time handling.</P
17195 ><P
17196 >Default: <B
17197 CLASS="COMMAND"
17198 >time offset = 0</B
17199 ></P
17200 ><P
17201 >Example: <B
17202 CLASS="COMMAND"
17203 >time offset = 60</B
17204 ></P
17205 ></DD
17206 ><DT
17207 ><A
17208 NAME="TIMESERVER"
17209 ></A
17210 >time server (G)</DT
17211 ><DD
17212 ><P
17213 >This parameter determines if <A
17214 HREF="nmbd.8.html"
17215 TARGET="_top"
17216 >
17217                 nmbd(8)</A
17218 > advertises itself as a time server to Windows
17219                 clients.</P
17220 ><P
17221 >Default: <B
17222 CLASS="COMMAND"
17223 >time server = no</B
17224 ></P
17225 ></DD
17226 ><DT
17227 ><A
17228 NAME="TIMESTAMPLOGS"
17229 ></A
17230 >timestamp logs (G)</DT
17231 ><DD
17232 ><P
17233 >Synonym for <A
17234 HREF="#DEBUGTIMESTAMP"
17235 ><TT
17236 CLASS="PARAMETER"
17237 ><I
17238 >               debug timestamp</I
17239 ></TT
17240 ></A
17241 >.</P
17242 ></DD
17243 ><DT
17244 ><A
17245 NAME="TOTALPRINTJOBS"
17246 ></A
17247 >total print jobs (G)</DT
17248 ><DD
17249 ><P
17250 >This parameter accepts an integer value which defines
17251                 a limit on the maximum number of print jobs that will be accepted
17252                 system wide at any given time.  If a print job is submitted
17253                 by a client which will exceed this number, then <A
17254 HREF="smbd.8.html"
17255 TARGET="_top"
17256 >smbd</A
17257 > will return an
17258                 error indicating that no space is available on the server.  The
17259                 default value of 0 means that no such limit exists.  This parameter
17260                 can be used to prevent a server from exceeding its capacity and is
17261                 designed as a printing throttle.  See also
17262                 <A
17263 HREF="#MAXPRINTJOBS"
17264 ><TT
17265 CLASS="PARAMETER"
17266 ><I
17267 >max print jobs</I
17268 ></TT
17269 ></A
17270 >.
17271                 </P
17272 ><P
17273 >Default: <B
17274 CLASS="COMMAND"
17275 >total print jobs = 0</B
17276 ></P
17277 ><P
17278 >Example: <B
17279 CLASS="COMMAND"
17280 >total print jobs = 5000</B
17281 ></P
17282 ></DD
17283 ><DT
17284 ><A
17285 NAME="UNIXPASSWORDSYNC"
17286 ></A
17287 >unix password sync (G)</DT
17288 ><DD
17289 ><P
17290 >This boolean parameter controls whether Samba
17291                 attempts to synchronize the UNIX password with the SMB password
17292                 when the encrypted SMB password in the smbpasswd file is changed.
17293                 If this is set to <TT
17294 CLASS="CONSTANT"
17295 >true</TT
17296 > the program specified in the <TT
17297 CLASS="PARAMETER"
17298 ><I
17299 >passwd
17300                 program</I
17301 ></TT
17302 >parameter is called <EM
17303 >AS ROOT</EM
17304 > -
17305                 to allow the new UNIX password to be set without access to the
17306                 old UNIX password (as the SMB password change code has no
17307                 access to the old password cleartext, only the new).</P
17308 ><P
17309 >See also <A
17310 HREF="#PASSWDPROGRAM"
17311 ><TT
17312 CLASS="PARAMETER"
17313 ><I
17314 >passwd
17315                 program</I
17316 ></TT
17317 ></A
17318 >, <A
17319 HREF="#PASSWDCHAT"
17320 ><TT
17321 CLASS="PARAMETER"
17322 ><I
17323 >               passwd chat</I
17324 ></TT
17325 ></A
17326 >.</P
17327 ><P
17328 >Default: <B
17329 CLASS="COMMAND"
17330 >unix password sync = no</B
17331 ></P
17332 ></DD
17333 ><DT
17334 ><A
17335 NAME="UPDATEENCRYPTED"
17336 ></A
17337 >update encrypted (G)</DT
17338 ><DD
17339 ><P
17340 >This boolean parameter allows a user logging
17341                 on with a plaintext password to have their encrypted (hashed)
17342                 password in the smbpasswd file to be updated automatically as
17343                 they log on. This option allows a site to migrate from plaintext
17344                 password authentication (users authenticate with plaintext
17345                 password over the wire, and are checked against a UNIX account
17346                 database) to encrypted password authentication (the SMB
17347                 challenge/response authentication mechanism) without forcing
17348                 all users to re-enter their passwords via smbpasswd at the time the
17349                 change is made. This is a convenience option to allow the change over
17350                 to encrypted passwords to be made over a longer period. Once all users
17351                 have encrypted representations of their passwords in the smbpasswd
17352                 file this parameter should be set to <TT
17353 CLASS="CONSTANT"
17354 >no</TT
17355 >.</P
17356 ><P
17357 >In order for this parameter to work correctly the <A
17358 HREF="#ENCRYPTPASSWORDS"
17359 ><TT
17360 CLASS="PARAMETER"
17361 ><I
17362 >encrypt passwords</I
17363 ></TT
17364 >
17365                 </A
17366 > parameter must be set to <TT
17367 CLASS="CONSTANT"
17368 >no</TT
17369 > when
17370                 this parameter is set to <TT
17371 CLASS="CONSTANT"
17372 >yes</TT
17373 >.</P
17374 ><P
17375 >Note that even when this parameter is set a user
17376                 authenticating to <B
17377 CLASS="COMMAND"
17378 >smbd</B
17379 > must still enter a valid
17380                 password in order to connect correctly, and to update their hashed
17381                 (smbpasswd) passwords.</P
17382 ><P
17383 >Default: <B
17384 CLASS="COMMAND"
17385 >update encrypted = no</B
17386 ></P
17387 ></DD
17388 ><DT
17389 ><A
17390 NAME="USECLIENTDRIVER"
17391 ></A
17392 >use client driver (S)</DT
17393 ><DD
17394 ><P
17395 >This parameter applies only to Windows NT/2000
17396                 clients.  It has no affect on Windows 95/98/ME clients.  When
17397                 serving a printer to Windows NT/2000 clients without first installing
17398                 a valid printer driver on the Samba host, the client will be required
17399                 to install a local printer driver.  From this point on, the client
17400                 will treat the print as a local printer and not a network printer
17401                 connection.  This is much the same behavior that will occur
17402                 when <B
17403 CLASS="COMMAND"
17404 >disable spoolss = yes</B
17405 >.  </P
17406 ><P
17407 >The differentiating
17408                 factor is that under normal circumstances, the NT/2000 client will
17409                 attempt to open the network printer using MS-RPC.  The problem is that
17410                 because the client considers the printer to be local, it will attempt
17411                 to issue the OpenPrinterEx() call requesting access rights associated
17412                 with the logged on user. If the user possesses local administator rights
17413                 but not root privilegde on the Samba host (often the case), the OpenPrinterEx()
17414                 call will fail.  The result is that the client will now display an "Access
17415                 Denied; Unable to connect" message in the printer queue window (even though
17416                 jobs may successfully be printed).  </P
17417 ><P
17418 >If this parameter is enabled for a printer, then any attempt
17419                 to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
17420                 to PRINTER_ACCESS_USE instead.  Thus allowing the OpenPrinterEx()
17421                 call to succeed.  <EM
17422 >This parameter MUST not be able enabled
17423                 on a print share which has valid print driver installed on the Samba
17424                 server.</EM
17425 ></P
17426 ><P
17427 >See also <A
17428 HREF="#DISABLESPOOLSS"
17429 >disable spoolss</A
17430 >
17431                 </P
17432 ><P
17433 >Default: <B
17434 CLASS="COMMAND"
17435 >use client driver = no</B
17436 ></P
17437 ></DD
17438 ><DT
17439 ><A
17440 NAME="USERHOSTS"
17441 ></A
17442 >use rhosts (G)</DT
17443 ><DD
17444 ><P
17445 >If this global parameter is <TT
17446 CLASS="CONSTANT"
17447 >true</TT
17448 >, it specifies
17449                 that the UNIX user's <TT
17450 CLASS="FILENAME"
17451 >.rhosts</TT
17452 > file in their home directory
17453                 will be read to find the names of hosts and users who will be allowed
17454                 access without specifying a password.</P
17455 ><P
17456 ><EM
17457 >NOTE:</EM
17458 > The use of <TT
17459 CLASS="PARAMETER"
17460 ><I
17461 >use rhosts
17462                 </I
17463 ></TT
17464 > can be a major security hole. This is because you are
17465                 trusting the PC to supply the correct username. It is very easy to
17466                 get a PC to supply a false username. I recommend that the <TT
17467 CLASS="PARAMETER"
17468 ><I
17469 >               use rhosts</I
17470 ></TT
17471 > option be only used if you really know what
17472                 you are doing.</P
17473 ><P
17474 >Default: <B
17475 CLASS="COMMAND"
17476 >use rhosts = no</B
17477 ></P
17478 ></DD
17479 ><DT
17480 ><A
17481 NAME="USER"
17482 ></A
17483 >user (S)</DT
17484 ><DD
17485 ><P
17486 >Synonym for <A
17487 HREF="#USERNAME"
17488 ><TT
17489 CLASS="PARAMETER"
17490 ><I
17491 >               username</I
17492 ></TT
17493 ></A
17494 >.</P
17495 ></DD
17496 ><DT
17497 ><A
17498 NAME="USERS"
17499 ></A
17500 >users (S)</DT
17501 ><DD
17502 ><P
17503 >Synonym for <A
17504 HREF="#USERNAME"
17505 ><TT
17506 CLASS="PARAMETER"
17507 ><I
17508 >               username</I
17509 ></TT
17510 ></A
17511 >.</P
17512 ></DD
17513 ><DT
17514 ><A
17515 NAME="USERNAME"
17516 ></A
17517 >username (S)</DT
17518 ><DD
17519 ><P
17520 >Multiple users may be specified in a comma-delimited
17521                 list, in which case the supplied password will be tested against
17522                 each username in turn (left to right).</P
17523 ><P
17524 >The <TT
17525 CLASS="PARAMETER"
17526 ><I
17527 >username</I
17528 ></TT
17529 > line is needed only when
17530                 the PC is unable to supply its own username. This is the case
17531                 for the COREPLUS protocol or where your users have different WfWg
17532                 usernames to UNIX usernames. In both these cases you may also be
17533                 better using the \\server\share%user syntax instead.</P
17534 ><P
17535 >The <TT
17536 CLASS="PARAMETER"
17537 ><I
17538 >username</I
17539 ></TT
17540 > line is not a great
17541                 solution in many cases as it means Samba will try to validate
17542                 the supplied password against each of the usernames in the
17543                 <TT
17544 CLASS="PARAMETER"
17545 ><I
17546 >username</I
17547 ></TT
17548 > line in turn. This is slow and
17549                 a bad idea for lots of users in case of duplicate passwords.
17550                 You may get timeouts or security breaches using this parameter
17551                 unwisely.</P
17552 ><P
17553 >Samba relies on the underlying UNIX security. This
17554                 parameter does not restrict who can login, it just offers hints
17555                 to the Samba server as to what usernames might correspond to the
17556                 supplied password. Users can login as whoever they please and
17557                 they will be able to do no more damage than if they started a
17558                 telnet session. The daemon runs as the user that they log in as,
17559                 so they cannot do anything that user cannot do.</P
17560 ><P
17561 >To restrict a service to a particular set of users you
17562                 can use the <A
17563 HREF="#VALIDUSERS"
17564 ><TT
17565 CLASS="PARAMETER"
17566 ><I
17567 >valid users
17568                 </I
17569 ></TT
17570 ></A
17571 > parameter.</P
17572 ><P
17573 >If any of the usernames begin with a '@' then the name
17574                 will be looked up first in the NIS netgroups list (if Samba
17575                 is compiled with netgroup support), followed by a lookup in
17576                 the UNIX groups database and will expand to a list of all users
17577                 in the group of that name.</P
17578 ><P
17579 >If any of the usernames begin with a '+' then the name
17580                 will be looked up only in the UNIX groups database and will
17581                 expand to a list of all users in the group of that name.</P
17582 ><P
17583 >If any of the usernames begin with a '&#38;'then the name
17584                 will be looked up only in the NIS netgroups database (if Samba
17585                 is compiled with netgroup support) and will expand to a list
17586                 of all users in the netgroup group of that name.</P
17587 ><P
17588 >Note that searching though a groups database can take
17589                 quite some time, and some clients may time out during the
17590                 search.</P
17591 ><P
17592 >See the section <A
17593 HREF="#AEN235"
17594 >NOTE ABOUT
17595                 USERNAME/PASSWORD VALIDATION</A
17596 > for more information on how
17597                 this parameter determines access to the services.</P
17598 ><P
17599 >Default: <B
17600 CLASS="COMMAND"
17601 >The guest account if a guest service,
17602                 else &#60;empty string&#62;.</B
17603 ></P
17604 ><P
17605 >Examples:<B
17606 CLASS="COMMAND"
17607 >username = fred, mary, jack, jane,
17608                 @users, @pcgroup</B
17609 ></P
17610 ></DD
17611 ><DT
17612 ><A
17613 NAME="USERNAMELEVEL"
17614 ></A
17615 >username level (G)</DT
17616 ><DD
17617 ><P
17618 >This option helps Samba to try and 'guess' at
17619                 the real UNIX username, as many DOS clients send an all-uppercase
17620                 username. By default Samba tries all lowercase, followed by the
17621                 username with the first letter capitalized, and fails if the
17622                 username is not found on the UNIX machine.</P
17623 ><P
17624 >If this parameter is set to non-zero the behavior changes.
17625                 This parameter is a number that specifies the number of uppercase
17626                 combinations to try while trying to determine the UNIX user name. The
17627                 higher the number the more combinations will be tried, but the slower
17628                 the discovery of usernames will be. Use this parameter when you have
17629                 strange usernames on your UNIX machine, such as <TT
17630 CLASS="CONSTANT"
17631 >AstrangeUser
17632                 </TT
17633 >.</P
17634 ><P
17635 >Default: <B
17636 CLASS="COMMAND"
17637 >username level = 0</B
17638 ></P
17639 ><P
17640 >Example: <B
17641 CLASS="COMMAND"
17642 >username level = 5</B
17643 ></P
17644 ></DD
17645 ><DT
17646 ><A
17647 NAME="USERNAMEMAP"
17648 ></A
17649 >username map (G)</DT
17650 ><DD
17651 ><P
17652 >This option allows you to specify a file containing
17653                 a mapping of usernames from the clients to the server. This can be
17654                 used for several purposes. The most common is to map usernames
17655                 that users use on DOS or Windows machines to those that the UNIX
17656                 box uses. The other is to map multiple users to a single username
17657                 so that they can more easily share files.</P
17658 ><P
17659 >The map file is parsed line by line. Each line should
17660                 contain a single UNIX username on the left then a '=' followed
17661                 by a list of usernames on the right. The list of usernames on the
17662                 right may contain names of the form @group in which case they
17663                 will match any UNIX username in that group. The special client
17664                 name '*' is a wildcard and matches any name. Each line of the
17665                 map file may be up to 1023 characters long.</P
17666 ><P
17667 >The file is processed on each line by taking the
17668                 supplied username and comparing it with each username on the right
17669                 hand side of the '=' signs. If the supplied name matches any of
17670                 the names on the right hand side then it is replaced with the name
17671                 on the left. Processing then continues with the next line.</P
17672 ><P
17673 >If any line begins with a '#' or a ';' then it is
17674                 ignored</P
17675 ><P
17676 >If any line begins with an '!' then the processing
17677                 will stop after that line if a mapping was done by the line.
17678                 Otherwise mapping continues with every line being processed.
17679                 Using '!' is most useful when you have a wildcard mapping line
17680                 later in the file.</P
17681 ><P
17682 >For example to map from the name <TT
17683 CLASS="CONSTANT"
17684 >admin</TT
17685 >
17686                 or <TT
17687 CLASS="CONSTANT"
17688 >administrator</TT
17689 > to the UNIX name <TT
17690 CLASS="CONSTANT"
17691 >               root</TT
17692 > you would use:</P
17693 ><P
17694 ><B
17695 CLASS="COMMAND"
17696 >root = admin administrator</B
17697 ></P
17698 ><P
17699 >Or to map anyone in the UNIX group <TT
17700 CLASS="CONSTANT"
17701 >system</TT
17702 >
17703                 to the UNIX name <TT
17704 CLASS="CONSTANT"
17705 >sys</TT
17706 > you would use:</P
17707 ><P
17708 ><B
17709 CLASS="COMMAND"
17710 >sys = @system</B
17711 ></P
17712 ><P
17713 >You can have as many mappings as you like in a username
17714                 map file.</P
17715 ><P
17716 >If your system supports the NIS NETGROUP option then
17717                 the netgroup database is checked before the <TT
17718 CLASS="FILENAME"
17719 >/etc/group
17720                 </TT
17721 > database for matching groups.</P
17722 ><P
17723 >You can map Windows usernames that have spaces in them
17724                  by using double quotes around the name. For example:</P
17725 ><P
17726 ><B
17727 CLASS="COMMAND"
17728 >tridge = "Andrew Tridgell"</B
17729 ></P
17730 ><P
17731 >would map the windows username "Andrew Tridgell" to the
17732                 unix username "tridge".</P
17733 ><P
17734 >The following example would map mary and fred to the
17735                 unix user sys, and map the rest to guest. Note the use of the
17736                 '!' to tell Samba to stop processing if it gets a match on
17737                 that line.</P
17738 ><P
17739 ><TABLE
17740 BORDER="0"
17741 BGCOLOR="#E0E0E0"
17742 WIDTH="90%"
17743 ><TR
17744 ><TD
17745 ><PRE
17746 CLASS="PROGRAMLISTING"
17747 >               !sys = mary fred
17748                 guest = *
17749                 </PRE
17750 ></TD
17751 ></TR
17752 ></TABLE
17753 ></P
17754 ><P
17755 >Note that the remapping is applied to all occurrences
17756                 of usernames. Thus if you connect to \\server\fred and <TT
17757 CLASS="CONSTANT"
17758 >               fred</TT
17759 > is remapped to <TT
17760 CLASS="CONSTANT"
17761 >mary</TT
17762 > then you
17763                 will actually be connecting to \\server\mary and will need to
17764                 supply a password suitable for <TT
17765 CLASS="CONSTANT"
17766 >mary</TT
17767 > not
17768                 <TT
17769 CLASS="CONSTANT"
17770 >fred</TT
17771 >. The only exception to this is the
17772                 username passed to the <A
17773 HREF="#PASSWORDSERVER"
17774 ><TT
17775 CLASS="PARAMETER"
17776 ><I
17777 >               password server</I
17778 ></TT
17779 ></A
17780 > (if you have one). The password
17781                 server will receive whatever username the client supplies without
17782                 modification.</P
17783 ><P
17784 >Also note that no reverse mapping is done. The main effect
17785                 this has is with printing. Users who have been mapped may have
17786                 trouble deleting print jobs as PrintManager under WfWg will think
17787                 they don't own the print job.</P
17788 ><P
17789 >Default: <EM
17790 >no username map</EM
17791 ></P
17792 ><P
17793 >Example: <B
17794 CLASS="COMMAND"
17795 >username map = /usr/local/samba/lib/users.map
17796                 </B
17797 ></P
17798 ></DD
17799 ><DT
17800 ><A
17801 NAME="UTMP"
17802 ></A
17803 >utmp (G)</DT
17804 ><DD
17805 ><P
17806 >This boolean parameter is only available if
17807                 Samba has been configured and compiled  with the option <B
17808 CLASS="COMMAND"
17809 >               --with-utmp</B
17810 >. If set to <TT
17811 CLASS="CONSTANT"
17812 >true</TT
17813 > then Samba will attempt
17814                 to add utmp or utmpx records (depending on the UNIX system) whenever a
17815                 connection is made to a Samba server. Sites may use this to record the
17816                 user connecting to a Samba share.</P
17817 ><P
17818 >See also the <A
17819 HREF="#UTMPDIRECTORY"
17820 ><TT
17821 CLASS="PARAMETER"
17822 ><I
17823 >               utmp directory</I
17824 ></TT
17825 ></A
17826 > parameter.</P
17827 ><P
17828 >Default: <B
17829 CLASS="COMMAND"
17830 >utmp = no</B
17831 ></P
17832 ></DD
17833 ><DT
17834 ><A
17835 NAME="UTMPDIRECTORY"
17836 ></A
17837 >utmp directory(G)</DT
17838 ><DD
17839 ><P
17840 >This parameter is only available if Samba has
17841                 been configured and compiled with the option <B
17842 CLASS="COMMAND"
17843 >               --with-utmp</B
17844 >. It specifies a directory pathname that is
17845                 used to store the utmp or utmpx files (depending on the UNIX system) that
17846                 record user connections to a Samba server. See also the <A
17847 HREF="#UTMP"
17848 >               <TT
17849 CLASS="PARAMETER"
17850 ><I
17851 >utmp</I
17852 ></TT
17853 ></A
17854 > parameter. By default this is
17855                 not set, meaning the system will use whatever utmp file the
17856                 native system is set to use (usually
17857                 <TT
17858 CLASS="FILENAME"
17859 >/var/run/utmp</TT
17860 > on Linux).</P
17861 ><P
17862 >Default: <EM
17863 >no utmp directory</EM
17864 ></P
17865 ></DD
17866 ><DT
17867 ><A
17868 NAME="VALIDCHARS"
17869 ></A
17870 >valid chars (G)</DT
17871 ><DD
17872 ><P
17873 >The option allows you to specify additional
17874                 characters that should be considered valid by the server in
17875                 filenames. This is particularly useful for national character
17876                 sets, such as adding u-umlaut or a-ring.</P
17877 ><P
17878 >The option takes a list of characters in either integer
17879                 or character form with spaces between them. If you give two
17880                 characters with a colon between them then it will be taken as
17881                 an lowercase:uppercase pair.</P
17882 ><P
17883 >If you have an editor capable of entering the characters
17884                 into the config file then it is probably easiest to use this
17885                 method. Otherwise you can specify the characters in octal,
17886                 decimal or hexadecimal form using the usual C notation.</P
17887 ><P
17888 >For example to add the single character 'Z' to the charset
17889                 (which is a pointless thing to do as it's already there) you could
17890                 do one of the following</P
17891 ><P
17892 ><TABLE
17893 BORDER="0"
17894 BGCOLOR="#E0E0E0"
17895 WIDTH="90%"
17896 ><TR
17897 ><TD
17898 ><PRE
17899 CLASS="PROGRAMLISTING"
17900 >               valid chars = Z
17901                 valid chars = z:Z
17902                 valid chars = 0132:0172
17903                 </PRE
17904 ></TD
17905 ></TR
17906 ></TABLE
17907 ></P
17908 ><P
17909 >The last two examples above actually add two characters,
17910                 and alter the uppercase and lowercase mappings appropriately.</P
17911 ><P
17912 >Note that you <EM
17913 >MUST</EM
17914 > specify this parameter
17915                 after the <TT
17916 CLASS="PARAMETER"
17917 ><I
17918 >client code page</I
17919 ></TT
17920 > parameter if you
17921                 have both set. If <TT
17922 CLASS="PARAMETER"
17923 ><I
17924 >client code page</I
17925 ></TT
17926 > is set after
17927                 the <TT
17928 CLASS="PARAMETER"
17929 ><I
17930 >valid chars</I
17931 ></TT
17932 > parameter the <TT
17933 CLASS="PARAMETER"
17934 ><I
17935 >valid
17936                 chars</I
17937 ></TT
17938 > settings will be overwritten.</P
17939 ><P
17940 >See also the <A
17941 HREF="#CLIENTCODEPAGE"
17942 ><TT
17943 CLASS="PARAMETER"
17944 ><I
17945 >client
17946                 code page</I
17947 ></TT
17948 ></A
17949 > parameter.</P
17950 ><P
17951 >Default: <EM
17952 >Samba defaults to using a reasonable set
17953                 of valid characters for English systems</EM
17954 ></P
17955 ><P
17956 >Example: <B
17957 CLASS="COMMAND"
17958 >valid chars = 0345:0305 0366:0326 0344:0304
17959                 </B
17960 ></P
17961 ><P
17962 >The above example allows filenames to have the Swedish
17963                 characters in them.</P
17964 ><P
17965 ><EM
17966 >NOTE:</EM
17967 > It is actually quite difficult to
17968                 correctly produce a <TT
17969 CLASS="PARAMETER"
17970 ><I
17971 >valid chars</I
17972 ></TT
17973 > line for
17974                 a particular system. To automate the process <A
17975 HREF="mailto:tino@augsburg.net"
17976 TARGET="_top"
17977 >tino@augsburg.net</A
17978 > has written
17979                 a package called <B
17980 CLASS="COMMAND"
17981 >validchars</B
17982 > which will automatically
17983                 produce a complete <TT
17984 CLASS="PARAMETER"
17985 ><I
17986 >valid chars</I
17987 ></TT
17988 > line for
17989                 a given client system. Look in the <TT
17990 CLASS="FILENAME"
17991 >examples/validchars/
17992                 </TT
17993 > subdirectory of your Samba source code distribution
17994                 for this package.</P
17995 ></DD
17996 ><DT
17997 ><A
17998 NAME="VALIDUSERS"
17999 ></A
18000 >valid users (S)</DT
18001 ><DD
18002 ><P
18003 >This is a list of users that should be allowed
18004                 to login to this service. Names starting with '@', '+' and  '&#38;'
18005                 are interpreted using the same rules as described in the
18006                 <TT
18007 CLASS="PARAMETER"
18008 ><I
18009 >invalid users</I
18010 ></TT
18011 > parameter.</P
18012 ><P
18013 >If this is empty (the default) then any user can login.
18014                 If a username is in both this list and the <TT
18015 CLASS="PARAMETER"
18016 ><I
18017 >invalid
18018                 users</I
18019 ></TT
18020 > list then access is denied for that user.</P
18021 ><P
18022 >The current servicename is substituted for <TT
18023 CLASS="PARAMETER"
18024 ><I
18025 >%S
18026                 </I
18027 ></TT
18028 >. This is useful in the [homes] section.</P
18029 ><P
18030 >See also <A
18031 HREF="#INVALIDUSERS"
18032 ><TT
18033 CLASS="PARAMETER"
18034 ><I
18035 >invalid users
18036                 </I
18037 ></TT
18038 ></A
18039 ></P
18040 ><P
18041 >Default: <EM
18042 >No valid users list (anyone can login)
18043                 </EM
18044 ></P
18045 ><P
18046 >Example: <B
18047 CLASS="COMMAND"
18048 >valid users = greg, @pcusers</B
18049 ></P
18050 ></DD
18051 ><DT
18052 ><A
18053 NAME="VETOFILES"
18054 ></A
18055 >veto files(S)</DT
18056 ><DD
18057 ><P
18058 >This is a list of files and directories that
18059                 are neither visible nor accessible.  Each entry in the list must
18060                 be separated by a '/', which allows spaces to be included
18061                 in the entry. '*' and '?' can be used to specify multiple files
18062                 or directories as in DOS wildcards.</P
18063 ><P
18064 >Each entry must be a unix path, not a DOS path and
18065                 must <EM
18066 >not</EM
18067 > include the  unix directory
18068                 separator '/'.</P
18069 ><P
18070 >Note that the <TT
18071 CLASS="PARAMETER"
18072 ><I
18073 >case sensitive</I
18074 ></TT
18075 > option
18076                 is applicable in vetoing files.</P
18077 ><P
18078 >One feature of the veto files parameter that it
18079                 is important to be aware of is Samba's behaviour when
18080                 trying to delete a directory. If a directory that is
18081                 to be deleted contains nothing but veto files this
18082                 deletion will <EM
18083 >fail</EM
18084 > unless you also set
18085                 the <TT
18086 CLASS="PARAMETER"
18087 ><I
18088 >delete veto files</I
18089 ></TT
18090 > parameter to
18091                 <TT
18092 CLASS="PARAMETER"
18093 ><I
18094 >yes</I
18095 ></TT
18096 >.</P
18097 ><P
18098 >Setting this parameter will affect the performance
18099                 of Samba, as it will be forced to check all files and directories
18100                 for a match as they are scanned.</P
18101 ><P
18102 >See also <A
18103 HREF="#HIDEFILES"
18104 ><TT
18105 CLASS="PARAMETER"
18106 ><I
18107 >hide files
18108                 </I
18109 ></TT
18110 ></A
18111 > and <A
18112 HREF="#CASESENSITIVE"
18113 ><TT
18114 CLASS="PARAMETER"
18115 ><I
18116 >               case sensitive</I
18117 ></TT
18118 ></A
18119 >.</P
18120 ><P
18121 >Default: <EM
18122 >No files or directories are vetoed.
18123                 </EM
18124 ></P
18125 ><P
18126 >Examples:<TABLE
18127 BORDER="0"
18128 BGCOLOR="#E0E0E0"
18129 WIDTH="90%"
18130 ><TR
18131 ><TD
18132 ><PRE
18133 CLASS="PROGRAMLISTING"
18134 >          ; Veto any files containing the word Security,
18135         ; any ending in .tmp, and any directory containing the
18136         ; word root.
18137                 veto files = /*Security*/*.tmp/*root*/
18138
18139                 ; Veto the Apple specific files that a NetAtalk server
18140         ; creates.
18141                 veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
18142                 </PRE
18143 ></TD
18144 ></TR
18145 ></TABLE
18146 ></P
18147 ></DD
18148 ><DT
18149 ><A
18150 NAME="VETOOPLOCKFILES"
18151 ></A
18152 >veto oplock files (S)</DT
18153 ><DD
18154 ><P
18155 >This parameter is only valid when the <A
18156 HREF="#OPLOCKS"
18157 ><TT
18158 CLASS="PARAMETER"
18159 ><I
18160 >oplocks</I
18161 ></TT
18162 ></A
18163 >
18164                 parameter is turned on for a share. It allows the Samba administrator
18165                 to selectively turn off the granting of oplocks on selected files that
18166                 match a wildcarded list, similar to the wildcarded list used in the
18167                 <A
18168 HREF="#VETOFILES"
18169 ><TT
18170 CLASS="PARAMETER"
18171 ><I
18172 >veto files</I
18173 ></TT
18174 ></A
18175 >
18176                 parameter.</P
18177 ><P
18178 >Default: <EM
18179 >No files are vetoed for oplock
18180                 grants</EM
18181 ></P
18182 ><P
18183 >You might want to do this on files that you know will
18184                 be heavily contended for by clients. A good example of this
18185                 is in the NetBench SMB benchmark program, which causes heavy
18186                 client contention for files ending in <TT
18187 CLASS="FILENAME"
18188 >.SEM</TT
18189 >.
18190                 To cause Samba not to grant oplocks on these files you would use
18191                 the line (either in the [global] section or in the section for
18192                 the particular NetBench share :</P
18193 ><P
18194 >Example: <B
18195 CLASS="COMMAND"
18196 >veto oplock files = /*.SEM/
18197                 </B
18198 ></P
18199 ></DD
18200 ><DT
18201 ><A
18202 NAME="VFSOBJECT"
18203 ></A
18204 >vfs object (S)</DT
18205 ><DD
18206 ><P
18207 >This parameter specifies a shared object file that
18208                 is used for Samba VFS I/O operations.  By default, normal
18209                 disk I/O operations are used but these can be overloaded
18210                 with a VFS object.  The Samba VFS layer is new to Samba 2.2 and
18211                 must be enabled at compile time with --with-vfs.</P
18212 ><P
18213 >Default : <EM
18214 >no value</EM
18215 ></P
18216 ></DD
18217 ><DT
18218 ><A
18219 NAME="VFSOPTIONS"
18220 ></A
18221 >vfs options (S)</DT
18222 ><DD
18223 ><P
18224 >This parameter allows parameters to be passed
18225                 to the vfs layer at initialization time.  The Samba VFS layer
18226                 is new to Samba 2.2 and must be enabled at compile time
18227                 with --with-vfs.  See also <A
18228 HREF="#VFSOBJECT"
18229 ><TT
18230 CLASS="PARAMETER"
18231 ><I
18232 >               vfs object</I
18233 ></TT
18234 ></A
18235 >.</P
18236 ><P
18237 >Default : <EM
18238 >no value</EM
18239 ></P
18240 ></DD
18241 ><DT
18242 ><A
18243 NAME="VOLUME"
18244 ></A
18245 >volume (S)</DT
18246 ><DD
18247 ><P
18248 > This allows you to override the volume label
18249                 returned for a share. Useful for CDROMs with installation programs
18250                 that insist on a particular volume label.</P
18251 ><P
18252 >Default: <EM
18253 >the name of the share</EM
18254 ></P
18255 ></DD
18256 ><DT
18257 ><A
18258 NAME="WIDELINKS"
18259 ></A
18260 >wide links (S)</DT
18261 ><DD
18262 ><P
18263 >This parameter controls whether or not links
18264                 in the UNIX file system may be followed by the server. Links
18265                 that point to areas within the directory tree exported by the
18266                 server are always allowed; this parameter controls access only
18267                 to areas that are outside the directory tree being exported.</P
18268 ><P
18269 >Note that setting this parameter can have a negative
18270                 effect on your server performance due to the extra system calls
18271                 that Samba has to  do in order to perform the link checks.</P
18272 ><P
18273 >Default: <B
18274 CLASS="COMMAND"
18275 >wide links = yes</B
18276 ></P
18277 ></DD
18278 ><DT
18279 ><A
18280 NAME="WINBINDCACHETIME"
18281 ></A
18282 >winbind cache time</DT
18283 ><DD
18284 ><P
18285 >This parameter specifies the number of seconds the
18286                 <A
18287 HREF="winbindd.8.html"
18288 TARGET="_top"
18289 >winbindd(8)</A
18290 > daemon will cache
18291                 user and group information before querying a Windows NT server
18292                 again.</P
18293 ><P
18294 >Default: <B
18295 CLASS="COMMAND"
18296 >winbind cache type = 15</B
18297 ></P
18298 ></DD
18299 ><DT
18300 ><A
18301 NAME="WINBINDGID"
18302 ></A
18303 >winbind gid</DT
18304 ><DD
18305 ><P
18306 >The winbind gid parameter specifies the range of group
18307                 ids that are allocated by the <A
18308 HREF="winbindd.8.html"
18309 TARGET="_top"
18310 >               winbindd(8)</A
18311 > daemon.  This range of group ids should have no
18312                 existing local or NIS groups within it as strange conflicts can
18313                 occur otherwise.</P
18314 ><P
18315 >Default: <B
18316 CLASS="COMMAND"
18317 >winbind gid = &#60;empty string&#62;
18318                 </B
18319 ></P
18320 ><P
18321 >Example: <B
18322 CLASS="COMMAND"
18323 >winbind gid = 10000-20000</B
18324 ></P
18325 ></DD
18326 ><DT
18327 ><A
18328 NAME="WINBINDSEPARATOR"
18329 ></A
18330 >winbind separator</DT
18331 ><DD
18332 ><P
18333 >This parameter allows an admin to define the character
18334                 used when listing a username of the form of <TT
18335 CLASS="REPLACEABLE"
18336 ><I
18337 >DOMAIN
18338                 </I
18339 ></TT
18340 >\<TT
18341 CLASS="REPLACEABLE"
18342 ><I
18343 >user</I
18344 ></TT
18345 >.  This parameter
18346                 is only applicable when using the <TT
18347 CLASS="FILENAME"
18348 >pam_winbind.so</TT
18349 >
18350                 and <TT
18351 CLASS="FILENAME"
18352 >nss_winbind.so</TT
18353 > modules for UNIX services.
18354                 </P
18355 ><P
18356 >Example: <B
18357 CLASS="COMMAND"
18358 >winbind separator = \</B
18359 ></P
18360 ><P
18361 >Example: <B
18362 CLASS="COMMAND"
18363 >winbind separator = +</B
18364 ></P
18365 ></DD
18366 ><DT
18367 ><A
18368 NAME="WINBINDUID"
18369 ></A
18370 >winbind uid</DT
18371 ><DD
18372 ><P
18373 >The winbind gid parameter specifies the range of group
18374                 ids that are allocated by the <A
18375 HREF="winbindd.8.html"
18376 TARGET="_top"
18377 >               winbindd(8)</A
18378 > daemon.  This range of ids should have no
18379                 existing local or NIS users within it as strange conflicts can
18380                 occur otherwise.</P
18381 ><P
18382 >Default: <B
18383 CLASS="COMMAND"
18384 >winbind uid = &#60;empty string&#62;
18385                 </B
18386 ></P
18387 ><P
18388 >Example: <B
18389 CLASS="COMMAND"
18390 >winbind uid = 10000-20000</B
18391 ></P
18392 ></DD
18393 ><DT
18394 ><A
18395 NAME="WINSHOOK"
18396 ></A
18397 >wins hook (G)</DT
18398 ><DD
18399 ><P
18400 >When Samba is running as a WINS server this
18401                 allows you to call an external program for all changes to the
18402                 WINS database. The primary use for this option is to allow the
18403                 dynamic update of external name resolution databases such as
18404                 dynamic DNS.</P
18405 ><P
18406 >The wins hook parameter specifies the name of a script
18407                 or executable that will be called as follows:</P
18408 ><P
18409 ><B
18410 CLASS="COMMAND"
18411 >wins_hook operation name nametype ttl IP_list
18412                 </B
18413 ></P
18414 ><P
18415 ></P
18416 ><UL
18417 ><LI
18418 ><P
18419 >The first argument is the operation and is one
18420                         of "add", "delete", or "refresh". In most cases the operation can
18421                         be ignored as the rest of the parameters provide sufficient
18422                         information. Note that "refresh" may sometimes be called when the
18423                         name has not previously been added, in that case it should be treated
18424                         as an add.</P
18425 ></LI
18426 ><LI
18427 ><P
18428 >The second argument is the NetBIOS name. If the
18429                         name is not a legal name then the wins hook is not called.
18430                         Legal names contain only  letters, digits, hyphens, underscores
18431                         and periods.</P
18432 ></LI
18433 ><LI
18434 ><P
18435 >The third argument is the NetBIOS name
18436                         type as a 2 digit hexadecimal number. </P
18437 ></LI
18438 ><LI
18439 ><P
18440 >The fourth argument is the TTL (time to live)
18441                         for the name in seconds.</P
18442 ></LI
18443 ><LI
18444 ><P
18445 >The fifth and subsequent arguments are the IP
18446                         addresses currently registered for that name. If this list is
18447                         empty then the name should be deleted.</P
18448 ></LI
18449 ></UL
18450 ><P
18451 >An example script that calls the BIND dynamic DNS update
18452                 program <B
18453 CLASS="COMMAND"
18454 >nsupdate</B
18455 > is provided in the examples
18456                 directory of the Samba source code. </P
18457 ></DD
18458 ><DT
18459 ><A
18460 NAME="WINSPROXY"
18461 ></A
18462 >wins proxy (G)</DT
18463 ><DD
18464 ><P
18465 >This is a boolean that controls if <A
18466 HREF="nmbd.8.html"
18467 TARGET="_top"
18468 >nmbd(8)</A
18469 > will respond to broadcast name
18470                 queries on behalf of  other hosts. You may need to set this
18471                 to <TT
18472 CLASS="CONSTANT"
18473 >yes</TT
18474 > for some older clients.</P
18475 ><P
18476 >Default: <B
18477 CLASS="COMMAND"
18478 >wins proxy = no</B
18479 ></P
18480 ></DD
18481 ><DT
18482 ><A
18483 NAME="WINSSERVER"
18484 ></A
18485 >wins server (G)</DT
18486 ><DD
18487 ><P
18488 >This specifies the IP address (or DNS name: IP
18489                 address for preference) of the WINS server that <A
18490 HREF="nmbd.8.html"
18491 TARGET="_top"
18492 >               nmbd(8)</A
18493 > should register with. If you have a WINS server on
18494                 your network then you should set this to the WINS server's IP.</P
18495 ><P
18496 >You should point this at your WINS server if you have a
18497                 multi-subnetted network.</P
18498 ><P
18499 ><EM
18500 >NOTE</EM
18501 >. You need to set up Samba to point
18502                 to a WINS server if you have multiple subnets and wish cross-subnet
18503                 browsing to work correctly.</P
18504 ><P
18505 >See the documentation file <TT
18506 CLASS="FILENAME"
18507 >BROWSING.txt</TT
18508 >
18509                 in the docs/ directory of your Samba source distribution.</P
18510 ><P
18511 >Default: <EM
18512 >not enabled</EM
18513 ></P
18514 ><P
18515 >Example: <B
18516 CLASS="COMMAND"
18517 >wins server = 192.9.200.1</B
18518 ></P
18519 ></DD
18520 ><DT
18521 ><A
18522 NAME="WINSSUPPORT"
18523 ></A
18524 >wins support (G)</DT
18525 ><DD
18526 ><P
18527 >This boolean controls if the <A
18528 HREF="nmbd.8.html"
18529 TARGET="_top"
18530 >
18531                 nmbd(8)</A
18532 > process in Samba will act as a WINS server. You should
18533                 not set this to <TT
18534 CLASS="CONSTANT"
18535 >true</TT
18536 > unless you have a multi-subnetted network and
18537                 you wish a particular <B
18538 CLASS="COMMAND"
18539 >nmbd</B
18540 > to be your WINS server.
18541                 Note that you should <EM
18542 >NEVER</EM
18543 > set this to <TT
18544 CLASS="CONSTANT"
18545 >true</TT
18546 >
18547                 on more than one machine in your network.</P
18548 ><P
18549 >Default: <B
18550 CLASS="COMMAND"
18551 >wins support = no</B
18552 ></P
18553 ></DD
18554 ><DT
18555 ><A
18556 NAME="WORKGROUP"
18557 ></A
18558 >workgroup (G)</DT
18559 ><DD
18560 ><P
18561 >This controls what workgroup your server will
18562                 appear to be in when queried by clients. Note that this parameter
18563                 also controls the Domain name used with the <A
18564 HREF="#SECURITYEQUALSDOMAIN"
18565 ><B
18566 CLASS="COMMAND"
18567 >security = domain</B
18568 ></A
18569 >
18570                 setting.</P
18571 ><P
18572 >Default: <EM
18573 >set at compile time to WORKGROUP</EM
18574 ></P
18575 ><P
18576 >Example: <B
18577 CLASS="COMMAND"
18578 >workgroup = MYGROUP</B
18579 ></P
18580 ></DD
18581 ><DT
18582 ><A
18583 NAME="WRITABLE"
18584 ></A
18585 >writable (S)</DT
18586 ><DD
18587 ><P
18588 >Synonym for <A
18589 HREF="#WRITEABLE"
18590 ><TT
18591 CLASS="PARAMETER"
18592 ><I
18593 >               writeable</I
18594 ></TT
18595 ></A
18596 > for people who can't spell :-).</P
18597 ></DD
18598 ><DT
18599 ><A
18600 NAME="WRITECACHESIZE"
18601 ></A
18602 >write cache size (S)</DT
18603 ><DD
18604 ><P
18605 >If this integer parameter is set to non-zero value,
18606                 Samba will create an in-memory cache for each oplocked file
18607                 (it does <EM
18608 >not</EM
18609 > do this for
18610                 non-oplocked files). All writes that the client does not request
18611                 to be flushed directly to disk will be stored in this cache if possible.
18612                 The cache is flushed onto disk when a write comes in whose offset
18613                 would not fit into the cache or when the file is closed by the client.
18614                 Reads for the file are also served from this cache if the data is stored
18615                 within it.</P
18616 ><P
18617 >This cache allows Samba to batch client writes into a more
18618                 efficient write size for RAID disks (i.e. writes may be tuned to
18619                 be the RAID stripe size) and can improve performance on systems
18620                 where the disk subsystem is a bottleneck but there is free
18621                 memory for userspace programs.</P
18622 ><P
18623 >The integer parameter specifies the size of this cache
18624                 (per oplocked file) in bytes.</P
18625 ><P
18626 >Default: <B
18627 CLASS="COMMAND"
18628 >write cache size = 0</B
18629 ></P
18630 ><P
18631 >Example: <B
18632 CLASS="COMMAND"
18633 >write cache size = 262144</B
18634 ></P
18635 ><P
18636 >for a 256k cache size per file.</P
18637 ></DD
18638 ><DT
18639 ><A
18640 NAME="WRITELIST"
18641 ></A
18642 >write list (S)</DT
18643 ><DD
18644 ><P
18645 >This is a list of users that are given read-write
18646                 access to a service. If the connecting user is in this list then
18647                 they will be given write access, no matter what the <A
18648 HREF="#WRITEABLE"
18649 ><TT
18650 CLASS="PARAMETER"
18651 ><I
18652 >writeable</I
18653 ></TT
18654 ></A
18655 >
18656                 option is set to. The list can include group names using the
18657                 @group syntax.</P
18658 ><P
18659 >Note that if a user is in both the read list and the
18660                 write list then they will be given write access.</P
18661 ><P
18662 >See also the <A
18663 HREF="#READLIST"
18664 ><TT
18665 CLASS="PARAMETER"
18666 ><I
18667 >read list
18668                 </I
18669 ></TT
18670 ></A
18671 > option.</P
18672 ><P
18673 >Default: <B
18674 CLASS="COMMAND"
18675 >write list = &#60;empty string&#62;
18676                 </B
18677 ></P
18678 ><P
18679 >Example: <B
18680 CLASS="COMMAND"
18681 >write list = admin, root, @staff
18682                 </B
18683 ></P
18684 ></DD
18685 ><DT
18686 ><A
18687 NAME="WRITEOK"
18688 ></A
18689 >write ok (S)</DT
18690 ><DD
18691 ><P
18692 >Synonym for <A
18693 HREF="#WRITEABLE"
18694 ><TT
18695 CLASS="PARAMETER"
18696 ><I
18697 >               writeable</I
18698 ></TT
18699 ></A
18700 >.</P
18701 ></DD
18702 ><DT
18703 ><A
18704 NAME="WRITERAW"
18705 ></A
18706 >write raw (G)</DT
18707 ><DD
18708 ><P
18709 >This parameter controls whether or not the server
18710                 will support raw write SMB's when transferring data from clients.
18711                 You should never need to change this parameter.</P
18712 ><P
18713 >Default: <B
18714 CLASS="COMMAND"
18715 >write raw = yes</B
18716 ></P
18717 ></DD
18718 ><DT
18719 ><A
18720 NAME="WRITEABLE"
18721 ></A
18722 >writeable (S)</DT
18723 ><DD
18724 ><P
18725 >An inverted synonym is <A
18726 HREF="#READONLY"
18727 >               <TT
18728 CLASS="PARAMETER"
18729 ><I
18730 >read only</I
18731 ></TT
18732 ></A
18733 >.</P
18734 ><P
18735 >If this parameter is <TT
18736 CLASS="CONSTANT"
18737 >no</TT
18738 >, then users
18739                 of a service may not create or modify files in the service's
18740                 directory.</P
18741 ><P
18742 >Note that a printable service (<B
18743 CLASS="COMMAND"
18744 >printable = yes</B
18745 >)
18746                 will <EM
18747 >ALWAYS</EM
18748 > allow writing to the directory
18749                 (user privileges permitting), but only via spooling operations.</P
18750 ><P
18751 >Default: <B
18752 CLASS="COMMAND"
18753 >writeable = no</B
18754 ></P
18755 ></DD
18756 ></DL
18757 ></DIV
18758 ></DIV
18759 ><DIV
18760 CLASS="REFSECT1"
18761 ><A
18762 NAME="AEN5917"
18763 ></A
18764 ><H2
18765 >WARNINGS</H2
18766 ><P
18767 >Although the configuration file permits service names
18768         to contain spaces, your client software may not. Spaces will
18769         be ignored in comparisons anyway, so it shouldn't be a
18770         problem - but be aware of the possibility.</P
18771 ><P
18772 >On a similar note, many clients - especially DOS clients -
18773         limit service names to eight characters. <A
18774 HREF="smbd.8.html"
18775 TARGET="_top"
18776 >smbd(8)
18777         </A
18778 > has no such limitation, but attempts to connect from such
18779         clients will fail if they truncate the service names.  For this reason
18780         you should probably keep your service names down to eight characters
18781         in length.</P
18782 ><P
18783 >Use of the [homes] and [printers] special sections make life
18784         for an administrator easy, but the various combinations of default
18785         attributes can be tricky. Take extreme care when designing these
18786         sections. In particular, ensure that the permissions on spool
18787         directories are correct.</P
18788 ></DIV
18789 ><DIV
18790 CLASS="REFSECT1"
18791 ><A
18792 NAME="AEN5923"
18793 ></A
18794 ><H2
18795 >VERSION</H2
18796 ><P
18797 >This man page is correct for version 2.2 of
18798         the Samba suite.</P
18799 ></DIV
18800 ><DIV
18801 CLASS="REFSECT1"
18802 ><A
18803 NAME="AEN5926"
18804 ></A
18805 ><H2
18806 >SEE ALSO</H2
18807 ><P
18808 ><A
18809 HREF="samba.7.html"
18810 TARGET="_top"
18811 >samba(7)</A
18812 >,
18813         <A
18814 HREF="smbpasswd.8.html"
18815 TARGET="_top"
18816 ><B
18817 CLASS="COMMAND"
18818 >smbpasswd(8)</B
18819 ></A
18820 >,
18821         <A
18822 HREF="swat.8.html"
18823 TARGET="_top"
18824 ><B
18825 CLASS="COMMAND"
18826 >swat(8)</B
18827 ></A
18828 >,
18829         <A
18830 HREF="smbd.8.html"
18831 TARGET="_top"
18832 ><B
18833 CLASS="COMMAND"
18834 >smbd(8)</B
18835 ></A
18836 >,
18837         <A
18838 HREF="nmbd.8.html"
18839 TARGET="_top"
18840 ><B
18841 CLASS="COMMAND"
18842 >nmbd(8)</B
18843 ></A
18844 >,
18845         <A
18846 HREF="smbclient.1.html"
18847 TARGET="_top"
18848 ><B
18849 CLASS="COMMAND"
18850 >smbclient(1)</B
18851 ></A
18852 >,
18853         <A
18854 HREF="nmblookup.1.html"
18855 TARGET="_top"
18856 ><B
18857 CLASS="COMMAND"
18858 >nmblookup(1)</B
18859 ></A
18860 >,
18861         <A
18862 HREF="testparm.1.html"
18863 TARGET="_top"
18864 ><B
18865 CLASS="COMMAND"
18866 >testparm(1)</B
18867 ></A
18868 >,
18869         <A
18870 HREF="testprns.1.html"
18871 TARGET="_top"
18872 ><B
18873 CLASS="COMMAND"
18874 >testprns(1)</B
18875 ></A
18876 >
18877         </P
18878 ></DIV
18879 ><DIV
18880 CLASS="REFSECT1"
18881 ><A
18882 NAME="AEN5946"
18883 ></A
18884 ><H2
18885 >AUTHOR</H2
18886 ><P
18887 >The original Samba software and related utilities
18888         were created by Andrew Tridgell. Samba is now developed
18889         by the Samba Team as an Open Source project similar
18890         to the way the Linux kernel is developed.</P
18891 ><P
18892 >The original Samba man pages were written by Karl Auer.
18893         The man page sources were converted to YODL format (another
18894         excellent piece of Open Source software, available at
18895         <A
18896 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
18897 TARGET="_top"
18898 >       ftp://ftp.icce.rug.nl/pub/unix/</A
18899 >) and updated for the Samba 2.0
18900         release by Jeremy Allison.  The conversion to DocBook for
18901         Samba 2.2 was done by Gerald Carter</P
18902 ></DIV
18903 ></BODY
18904 ></HTML
18905 >