docs/htmldocs/smb.conf.5.html

   1 <HTML
   2 ><HEAD
   3 ><TITLE
   4 >smb.conf</TITLE
   5 ><META
   6 NAME="GENERATOR"
   7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
   8 ><BODY
   9 CLASS="REFENTRY"
  10 BGCOLOR="#FFFFFF"
  11 TEXT="#000000"
  12 LINK="#0000FF"
  13 VLINK="#840084"
  14 ALINK="#0000FF"
  15 ><H1
  16 ><A
  17 NAME="SMB.CONF"
  18 >smb.conf</A
  19 ></H1
  20 ><DIV
  21 CLASS="REFNAMEDIV"
  22 ><A
  23 NAME="AEN5"
  24 ></A
  25 ><H2
  26 >Name</H2
  27 >smb.conf&nbsp;--&nbsp;The configuration file for the Samba suite</DIV
  28 ><DIV
  29 CLASS="REFSECT1"
  30 ><A
  31 NAME="AEN8"
  32 ></A
  33 ><H2
  34 >SYNOPSIS</H2
  35 ><P
  36 >The <TT
  37 CLASS="FILENAME"
  38 >smb.conf</TT
  39 > file is a configuration
  40         file for the Samba suite. <TT
  41 CLASS="FILENAME"
  42 >smb.conf</TT
  43 > contains
  44         runtime configuration information for the Samba programs. The
  45         <TT
  46 CLASS="FILENAME"
  47 >smb.conf</TT
  48 > file is designed to be configured and
  49         administered by the <A
  50 HREF="swat.8.html"
  51 TARGET="_top"
  52 ><B
  53 CLASS="COMMAND"
  54 >swat(8)</B
  55 >
  56         </A
  57 > program. The complete description of the file format and
  58         possible parameters held within are here for reference purposes.</P
  59 ></DIV
  60 ><DIV
  61 CLASS="REFSECT1"
  62 ><A
  63 NAME="AEN16"
  64 ></A
  65 ><H2
  66 >FILE FORMAT</H2
  67 ><P
  68 >The file consists of sections and parameters. A section
  69         begins with the name of the section in square brackets and continues
  70         until the next section begins. Sections contain parameters of the
  71         form</P
  72 ><P
  73 ><TT
  74 CLASS="REPLACEABLE"
  75 ><I
  76 >name</I
  77 ></TT
  78 > = <TT
  79 CLASS="REPLACEABLE"
  80 ><I
  81 >value
  82         </I
  83 ></TT
  84 ></P
  85 ><P
  86 >The file is line-based - that is, each newline-terminated
  87         line represents either a comment, a section name or a parameter.</P
  88 ><P
  89 >Section and parameter names are not case sensitive.</P
  90 ><P
  91 >Only the first equals sign in a parameter is significant.
  92         Whitespace before or after the first equals sign is discarded.
  93         Leading, trailing and internal whitespace in section and parameter
  94         names is irrelevant. Leading and trailing whitespace in a parameter
  95         value is discarded. Internal whitespace within a parameter value
  96         is retained verbatim.</P
  97 ><P
  98 >Any line beginning with a semicolon (';') or a hash ('#')
  99         character is ignored, as are lines containing only whitespace.</P
 100 ><P
 101 >Any line ending in a '\' is continued
 102         on the next line in the customary UNIX fashion.</P
 103 ><P
 104 >The values following the equals sign in parameters are all
 105         either a string (no quotes needed) or a boolean, which may be given
 106         as yes/no, 0/1 or true/false. Case is not significant in boolean
 107         values, but is preserved in string values. Some items such as
 108         create modes are numeric.</P
 109 ></DIV
 110 ><DIV
 111 CLASS="REFSECT1"
 112 ><A
 113 NAME="AEN28"
 114 ></A
 115 ><H2
 116 >SECTION DESCRIPTIONS</H2
 117 ><P
 118 >Each section in the configuration file (except for the
 119         [global] section) describes a shared resource (known
 120         as a "share"). The section name is the name of the
 121         shared resource and the parameters within the section define
 122         the shares attributes.</P
 123 ><P
 124 >There are three special sections, [global],
 125         [homes] and [printers], which are
 126         described under <EM
 127 >special sections</EM
 128 >. The
 129         following notes apply to ordinary section descriptions.</P
 130 ><P
 131 >A share consists of a directory to which access is being
 132         given plus a description of the access rights which are granted
 133         to the user of the service. Some housekeeping options are
 134         also specifiable.</P
 135 ><P
 136 >Sections are either file share services (used by the
 137         client as an extension of their native file systems) or
 138         printable services (used by the client to access print services
 139         on the host running the server).</P
 140 ><P
 141 >Sections may be designated <EM
 142 >guest</EM
 143 > services,
 144         in which case no password is required to access them. A specified
 145         UNIX <EM
 146 >guest account</EM
 147 > is used to define access
 148         privileges in this case.</P
 149 ><P
 150 >Sections other than guest services will require a password
 151         to access them. The client provides the username. As older clients
 152         only provide passwords and not usernames, you may specify a list
 153         of usernames to check against the password using the "user ="
 154         option in the share definition. For modern clients such as
 155         Windows 95/98/ME/NT/2000, this should not be necessary.</P
 156 ><P
 157 >Note that the access rights granted by the server are
 158         masked by the access rights granted to the specified or guest
 159         UNIX user by the host system. The server does not grant more
 160         access than the host system grants.</P
 161 ><P
 162 >The following sample section defines a file space share.
 163         The user has write access to the path <TT
 164 CLASS="FILENAME"
 165 >/home/bar</TT
 166 >.
 167         The share is accessed via the share name "foo":</P
 168 ><TABLE
 169 BORDER="0"
 170 BGCOLOR="#E0E0E0"
 171 WIDTH="100%"
 172 ><TR
 173 ><TD
 174 ><PRE
 175 CLASS="SCREEN"
 176 >       <TT
 177 CLASS="COMPUTEROUTPUT"
 178 >       [foo]
 179                 path = /home/bar
 180                 read only = no
 181         </TT
 182 >
 183         </PRE
 184 ></TD
 185 ></TR
 186 ></TABLE
 187 ><P
 188 >The following sample section defines a printable share.
 189         The share is readonly, but printable. That is, the only write
 190         access permitted is via calls to open, write to and close a
 191         spool file. The <EM
 192 >guest ok</EM
 193 > parameter means
 194         access will be permitted as the default guest user (specified
 195         elsewhere):</P
 196 ><TABLE
 197 BORDER="0"
 198 BGCOLOR="#E0E0E0"
 199 WIDTH="100%"
 200 ><TR
 201 ><TD
 202 ><PRE
 203 CLASS="SCREEN"
 204 >       <TT
 205 CLASS="COMPUTEROUTPUT"
 206 >       [aprinter]
 207                 path = /usr/spool/public
 208                 read only = yes
 209                 printable = yes
 210                 guest ok = yes
 211         </TT
 212 >
 213         </PRE
 214 ></TD
 215 ></TR
 216 ></TABLE
 217 ></DIV
 218 ><DIV
 219 CLASS="REFSECT1"
 220 ><A
 221 NAME="AEN48"
 222 ></A
 223 ><H2
 224 >SPECIAL SECTIONS</H2
 225 ><DIV
 226 CLASS="REFSECT2"
 227 ><A
 228 NAME="AEN50"
 229 ></A
 230 ><H3
 231 >The [global] section</H3
 232 ><P
 233 >parameters in this section apply to the server
 234                 as a whole, or are defaults for sections which do not
 235                 specifically define certain items. See the notes
 236                 under PARAMETERS for more information.</P
 237 ></DIV
 238 ><DIV
 239 CLASS="REFSECT2"
 240 ><A
 241 NAME="AEN53"
 242 ></A
 243 ><H3
 244 >The [homes] section</H3
 245 ><P
 246 >If a section called homes is included in the
 247                 configuration file, services connecting clients to their
 248                 home directories can be created on the fly by the server.</P
 249 ><P
 250 >When the connection request is made, the existing
 251                 sections are scanned. If a match is found, it is used. If no
 252                 match is found, the requested section name is treated as a
 253                 user name and looked up in the local password file. If the
 254                 name exists and the correct password has been given, a share is
 255                 created by cloning the [homes] section.</P
 256 ><P
 257 >Some modifications are then made to the newly
 258                 created share:</P
 259 ><P
 260 ></P
 261 ><UL
 262 ><LI
 263 ><P
 264 >The share name is changed from homes to
 265                 the located username.</P
 266 ></LI
 267 ><LI
 268 ><P
 269 >If no path was given, the path is set to
 270                 the user's home directory.</P
 271 ></LI
 272 ></UL
 273 ><P
 274 >If you decide to use a <EM
 275 >path =</EM
 276 > line
 277                 in your [homes] section then you may find it useful
 278                 to use the %S macro. For example :</P
 279 ><P
 280 ><TT
 281 CLASS="USERINPUT"
 282 ><B
 283 >path = /data/pchome/%S</B
 284 ></TT
 285 ></P
 286 ><P
 287 >would be useful if you have different home directories
 288                 for your PCs than for UNIX access.</P
 289 ><P
 290 >This is a fast and simple way to give a large number
 291                 of clients access to their home directories with a minimum
 292                 of fuss.</P
 293 ><P
 294 >A similar process occurs if the requested section
 295                 name is "homes", except that the share name is not
 296                 changed to that of the requesting user. This method of using
 297                 the [homes] section works well if different users share
 298                 a client PC.</P
 299 ><P
 300 >The [homes] section can specify all the parameters
 301                 a normal service section can specify, though some make more sense
 302                 than others. The following is a typical and suitable [homes]
 303                 section:</P
 304 ><TABLE
 305 BORDER="0"
 306 BGCOLOR="#E0E0E0"
 307 WIDTH="100%"
 308 ><TR
 309 ><TD
 310 ><PRE
 311 CLASS="SCREEN"
 312 >               <TT
 313 CLASS="COMPUTEROUTPUT"
 314 >               [homes]
 315                         read only = no
 316                 </TT
 317 >
 318                 </PRE
 319 ></TD
 320 ></TR
 321 ></TABLE
 322 ><P
 323 >An important point is that if guest access is specified
 324                 in the [homes] section, all home directories will be
 325                 visible to all clients <EM
 326 >without a password</EM
 327 >.
 328                 In the very unlikely event that this is actually desirable, it
 329                 would be wise to also specify <EM
 330 >read only
 331                 access</EM
 332 >.</P
 333 ><P
 334 >Note that the <EM
 335 >browseable</EM
 336 > flag for
 337                 auto home directories will be inherited from the global browseable
 338                 flag, not the [homes] browseable flag. This is useful as
 339                 it means setting <EM
 340 >browseable = no</EM
 341 > in
 342                 the [homes] section will hide the [homes] share but make
 343                 any auto home directories visible.</P
 344 ></DIV
 345 ><DIV
 346 CLASS="REFSECT2"
 347 ><A
 348 NAME="AEN79"
 349 ></A
 350 ><H3
 351 >The [printers] section</H3
 352 ><P
 353 >This section works like [homes],
 354                 but for printers.</P
 355 ><P
 356 >If a [printers] section occurs in the
 357                 configuration file, users are able to connect to any printer
 358                 specified in the local host's printcap file.</P
 359 ><P
 360 >When a connection request is made, the existing sections
 361                 are scanned. If a match is found, it is used. If no match is found,
 362                 but a [homes] section exists, it is used as described
 363                 above. Otherwise, the requested section name is treated as a
 364                 printer name and the appropriate printcap file is scanned to see
 365                 if the requested section name is a valid printer share name. If
 366                 a match is found, a new printer share is created by cloning
 367                 the [printers] section.</P
 368 ><P
 369 >A few modifications are then made to the newly created
 370                 share:</P
 371 ><P
 372 ></P
 373 ><UL
 374 ><LI
 375 ><P
 376 >The share name is set to the located printer
 377                 name</P
 378 ></LI
 379 ><LI
 380 ><P
 381 >If no printer name was given, the printer name
 382                 is set to the located printer name</P
 383 ></LI
 384 ><LI
 385 ><P
 386 >If the share does not permit guest access and
 387                 no username was given, the username is set to the located
 388                 printer name.</P
 389 ></LI
 390 ></UL
 391 ><P
 392 >Note that the [printers] service MUST be
 393                 printable - if you specify otherwise, the server will refuse
 394                 to load the configuration file.</P
 395 ><P
 396 >Typically the path specified would be that of a
 397                 world-writeable spool directory with the sticky bit set on
 398                 it. A typical [printers] entry would look like
 399                 this:</P
 400 ><TABLE
 401 BORDER="0"
 402 BGCOLOR="#E0E0E0"
 403 WIDTH="100%"
 404 ><TR
 405 ><TD
 406 ><PRE
 407 CLASS="SCREEN"
 408 ><TT
 409 CLASS="COMPUTEROUTPUT"
 410 >               [printers]
 411                         path = /usr/spool/public
 412                         guest ok = yes
 413                         printable = yes
 414                 </TT
 415 ></PRE
 416 ></TD
 417 ></TR
 418 ></TABLE
 419 ><P
 420 >All aliases given for a printer in the printcap file
 421                 are legitimate printer names as far as the server is concerned.
 422                 If your printing subsystem doesn't work like that, you will have
 423                 to set up a pseudo-printcap. This is a file consisting of one or
 424                 more lines like this:</P
 425 ><TABLE
 426 BORDER="0"
 427 BGCOLOR="#E0E0E0"
 428 WIDTH="100%"
 429 ><TR
 430 ><TD
 431 ><PRE
 432 CLASS="SCREEN"
 433 >               <TT
 434 CLASS="COMPUTEROUTPUT"
 435 >               alias|alias|alias|alias...
 436                 </TT
 437 >
 438                 </PRE
 439 ></TD
 440 ></TR
 441 ></TABLE
 442 ><P
 443 >Each alias should be an acceptable printer name for
 444                 your printing subsystem. In the [global] section, specify
 445                 the new file as your printcap.  The server will then only recognize
 446                 names found in your pseudo-printcap, which of course can contain
 447                 whatever aliases you like. The same technique could be used
 448                 simply to limit access to a subset of your local printers.</P
 449 ><P
 450 >An alias, by the way, is defined as any component of the
 451                 first entry of a printcap record. Records are separated by newlines,
 452                 components (if there are more than one) are separated by vertical
 453                 bar symbols ('|').</P
 454 ><P
 455 >NOTE: On SYSV systems which use lpstat to determine what
 456                 printers are defined on the system you may be able to use
 457                 "printcap name = lpstat" to automatically obtain a list
 458                 of printers. See the "printcap name" option
 459                 for more details.</P
 460 ></DIV
 461 ></DIV
 462 ><DIV
 463 CLASS="REFSECT1"
 464 ><A
 465 NAME="AEN102"
 466 ></A
 467 ><H2
 468 >PARAMETERS</H2
 469 ><P
 470 >parameters define the specific attributes of sections.</P
 471 ><P
 472 >Some parameters are specific to the [global] section
 473         (e.g., <EM
 474 >security</EM
 475 >).  Some parameters are usable
 476         in all sections (e.g., <EM
 477 >create mode</EM
 478 >). All others
 479         are permissible only in normal sections. For the purposes of the
 480         following descriptions the [homes] and [printers]
 481         sections will be considered normal.  The letter <EM
 482 >G</EM
 483 >
 484         in parentheses indicates that a parameter is specific to the
 485         [global] section. The letter <EM
 486 >S</EM
 487 >
 488         indicates that a parameter can be specified in a service specific
 489         section. Note that all <EM
 490 >S</EM
 491 > parameters can also be specified in
 492         the [global] section - in which case they will define
 493         the default behavior for all services.</P
 494 ><P
 495 >parameters are arranged here in alphabetical order - this may
 496         not create best bedfellows, but at least you can find them! Where
 497         there are synonyms, the preferred synonym is described, others refer
 498         to the preferred synonym.</P
 499 ></DIV
 500 ><DIV
 501 CLASS="REFSECT1"
 502 ><A
 503 NAME="AEN112"
 504 ></A
 505 ><H2
 506 >VARIABLE SUBSTITUTIONS</H2
 507 ><P
 508 >Many of the strings that are settable in the config file
 509         can take substitutions. For example the option "path =
 510         /tmp/%u" would be interpreted as "path =
 511         /tmp/john" if the user connected with the username john.</P
 512 ><P
 513 >These substitutions are mostly noted in the descriptions below,
 514         but there are some general substitutions which apply whenever they
 515         might be relevant. These are:</P
 516 ><P
 517 ></P
 518 ><DIV
 519 CLASS="VARIABLELIST"
 520 ><DL
 521 ><DT
 522 >%S</DT
 523 ><DD
 524 ><P
 525 >the name of the current service, if any.</P
 526 ></DD
 527 ><DT
 528 >%P</DT
 529 ><DD
 530 ><P
 531 >the root directory of the current service,
 532                 if any.</P
 533 ></DD
 534 ><DT
 535 >%u</DT
 536 ><DD
 537 ><P
 538 >user name of the current service, if any.</P
 539 ></DD
 540 ><DT
 541 >%g</DT
 542 ><DD
 543 ><P
 544 >primary group name of %u.</P
 545 ></DD
 546 ><DT
 547 >%U</DT
 548 ><DD
 549 ><P
 550 >session user name (the user name that the client
 551                 wanted, not necessarily the same as the one they got).</P
 552 ></DD
 553 ><DT
 554 >%G</DT
 555 ><DD
 556 ><P
 557 >primary group name of %U.</P
 558 ></DD
 559 ><DT
 560 >%H</DT
 561 ><DD
 562 ><P
 563 >the home directory of the user given
 564                 by %u.</P
 565 ></DD
 566 ><DT
 567 >%v</DT
 568 ><DD
 569 ><P
 570 >the Samba version.</P
 571 ></DD
 572 ><DT
 573 >%h</DT
 574 ><DD
 575 ><P
 576 >the Internet hostname that Samba is running
 577                 on.</P
 578 ></DD
 579 ><DT
 580 >%m</DT
 581 ><DD
 582 ><P
 583 >the NetBIOS name of the client machine
 584                 (very useful).</P
 585 ></DD
 586 ><DT
 587 >%L</DT
 588 ><DD
 589 ><P
 590 >the NetBIOS name of the server. This allows you
 591                 to change your config based on what the client calls you. Your
 592                 server can have a "dual personality".</P
 593 ><P
 594 >Note that this paramater is not available when Samba listens
 595                 on port 445, as clients no longer send this information </P
 596 ></DD
 597 ><DT
 598 >%M</DT
 599 ><DD
 600 ><P
 601 >the Internet name of the client machine.
 602                 </P
 603 ></DD
 604 ><DT
 605 >%N</DT
 606 ><DD
 607 ><P
 608 >the name of your NIS home directory server.
 609                 This is obtained from your NIS auto.map entry.  If you have
 610                 not compiled Samba with the <EM
 611 >--with-automount</EM
 612 >
 613                 option then this value will be the same as %L.</P
 614 ></DD
 615 ><DT
 616 >%p</DT
 617 ><DD
 618 ><P
 619 >the path of the service's home directory,
 620                 obtained from your NIS auto.map entry. The NIS auto.map entry
 621                 is split up as "%N:%p".</P
 622 ></DD
 623 ><DT
 624 >%R</DT
 625 ><DD
 626 ><P
 627 >the selected protocol level after
 628                 protocol negotiation. It can be one of CORE, COREPLUS,
 629                 LANMAN1, LANMAN2 or NT1.</P
 630 ></DD
 631 ><DT
 632 >%d</DT
 633 ><DD
 634 ><P
 635 >The process id of the current server
 636                 process.</P
 637 ></DD
 638 ><DT
 639 >%a</DT
 640 ><DD
 641 ><P
 642 >the architecture of the remote
 643                 machine. Only some are recognized, and those may not be
 644                 100% reliable. It currently recognizes Samba, WfWg, Win95,
 645                 WinNT and Win2k. Anything else will be known as
 646                 "UNKNOWN". If it gets it wrong then sending a level
 647                 3 log to <A
 648 HREF="mailto:samba@samba.org"
 649 TARGET="_top"
 650 >samba@samba.org
 651                 </A
 652 > should allow it to be fixed.</P
 653 ></DD
 654 ><DT
 655 >%I</DT
 656 ><DD
 657 ><P
 658 >The IP address of the client machine.</P
 659 ></DD
 660 ><DT
 661 >%T</DT
 662 ><DD
 663 ><P
 664 >the current date and time.</P
 665 ></DD
 666 ><DT
 667 >%$(<TT
 668 CLASS="REPLACEABLE"
 669 ><I
 670 >envvar</I
 671 ></TT
 672 >)</DT
 673 ><DD
 674 ><P
 675 >The value of the environment variable
 676                 <TT
 677 CLASS="REPLACEABLE"
 678 ><I
 679 >envar</I
 680 ></TT
 681 >.</P
 682 ></DD
 683 ></DL
 684 ></DIV
 685 ><P
 686 >There are some quite creative things that can be done
 687         with these substitutions and other smb.conf options.</P
 688 ></DIV
 689 ><DIV
 690 CLASS="REFSECT1"
 691 ><A
 692 NAME="AEN203"
 693 ></A
 694 ><H2
 695 >NAME MANGLING</H2
 696 ><P
 697 >Samba supports "name mangling" so that DOS and
 698         Windows clients can use files that don't conform to the 8.3 format.
 699         It can also be set to adjust the case of 8.3 format filenames.</P
 700 ><P
 701 >There are several options that control the way mangling is
 702         performed, and they are grouped here rather than listed separately.
 703         For the defaults look at the output of the testparm program. </P
 704 ><P
 705 >All of these options can be set separately for each service
 706         (or globally, of course). </P
 707 ><P
 708 >The options are: </P
 709 ><P
 710 ></P
 711 ><DIV
 712 CLASS="VARIABLELIST"
 713 ><DL
 714 ><DT
 715 >mangling method</DT
 716 ><DD
 717 ><P
 718 > controls the algorithm used for the generating
 719                 the mangled names. Can take two different values, "hash" and
 720                 "hash2". "hash" is  the default and is the algorithm that has been
 721                 used in Samba for many years. "hash2" is a newer and considered
 722                 a better algorithm (generates less collisions) in the names.
 723                 However, many Win32 applications store the
 724                 mangled names and so changing to the new algorithm must not be done
 725                 lightly as these applications may break unless reinstalled.
 726                 New installations of Samba may set the default to hash2.
 727                 Default <EM
 728 >hash</EM
 729 >.</P
 730 ></DD
 731 ><DT
 732 >mangle case = yes/no</DT
 733 ><DD
 734 ><P
 735 > controls if names that have characters that
 736                 aren't of the "default" case are mangled. For example,
 737                 if this is yes then a name like "Mail" would be mangled.
 738                 Default <EM
 739 >no</EM
 740 >.</P
 741 ></DD
 742 ><DT
 743 >case sensitive = yes/no</DT
 744 ><DD
 745 ><P
 746 >controls whether filenames are case sensitive. If
 747                 they aren't then Samba must do a filename search and match on passed
 748                 names. Default <EM
 749 >no</EM
 750 >.</P
 751 ></DD
 752 ><DT
 753 >default case = upper/lower</DT
 754 ><DD
 755 ><P
 756 >controls what the default case is for new
 757                 filenames. Default <EM
 758 >lower</EM
 759 >.</P
 760 ></DD
 761 ><DT
 762 >preserve case = yes/no</DT
 763 ><DD
 764 ><P
 765 >controls if new files are created with the
 766                 case that the client passes, or if they are forced to be the
 767                 "default" case. Default <EM
 768 >yes</EM
 769 >.
 770                 </P
 771 ></DD
 772 ><DT
 773 >short preserve case = yes/no</DT
 774 ><DD
 775 ><P
 776 >controls if new files which conform to 8.3 syntax,
 777                 that is all in upper case and of suitable length, are created
 778                 upper case, or if they are forced to be the "default"
 779                 case. This option can be use with "preserve case = yes"
 780                 to permit long filenames to retain their case, while short names
 781                 are lowercased. Default <EM
 782 >yes</EM
 783 >.</P
 784 ></DD
 785 ></DL
 786 ></DIV
 787 ><P
 788 >By default, Samba 2.2 has the same semantics as a Windows
 789         NT server, in that it is case insensitive but case preserving.</P
 790 ></DIV
 791 ><DIV
 792 CLASS="REFSECT1"
 793 ><A
 794 NAME="AEN241"
 795 ></A
 796 ><H2
 797 >NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2
 798 ><P
 799 >There are a number of ways in which a user can connect
 800         to a service. The server uses the following steps in determining
 801         if it will allow a connection to a specified service. If all the
 802         steps fail, then the connection request is rejected.  However, if one of the
 803         steps succeeds, then the following steps are not checked.</P
 804 ><P
 805 >If the service is marked "guest only = yes" and the
 806         server is running with share-level security ("security = share")
 807         then steps 1 to 5 are skipped.</P
 808 ><P
 809 ></P
 810 ><OL
 811 TYPE="1"
 812 ><LI
 813 ><P
 814 >If the client has passed a username/password
 815                 pair and that username/password pair is validated by the UNIX
 816                 system's password programs then the connection is made as that
 817                 username. Note that this includes the
 818                 \\server\service%<TT
 819 CLASS="REPLACEABLE"
 820 ><I
 821 >username</I
 822 ></TT
 823 > method of passing
 824                 a username.</P
 825 ></LI
 826 ><LI
 827 ><P
 828 >If the client has previously registered a username
 829                 with the system and now supplies a correct password for that
 830                 username then the connection is allowed.</P
 831 ></LI
 832 ><LI
 833 ><P
 834 >The client's NetBIOS name and any previously
 835                 used user names are checked against the supplied password, if
 836                 they match then the connection is allowed as the corresponding
 837                 user.</P
 838 ></LI
 839 ><LI
 840 ><P
 841 >If the client has previously validated a
 842                 username/password pair with the server and the client has passed
 843                 the validation token then that username is used. </P
 844 ></LI
 845 ><LI
 846 ><P
 847 >If a "user = " field is given in the
 848                 <TT
 849 CLASS="FILENAME"
 850 >smb.conf</TT
 851 > file for the service and the client
 852                 has supplied a password, and that password matches (according to
 853                 the UNIX system's password checking) with one of the usernames
 854                 from the "user =" field then the connection is made as
 855                 the username in the "user =" line. If one
 856                 of the username in the "user =" list begins with a
 857                 '@' then that name expands to a list of names in
 858                 the group of the same name.</P
 859 ></LI
 860 ><LI
 861 ><P
 862 >If the service is a guest service then a
 863                 connection is made as the username given in the "guest
 864                 account =" for the service, irrespective of the
 865                 supplied password.</P
 866 ></LI
 867 ></OL
 868 ></DIV
 869 ><DIV
 870 CLASS="REFSECT1"
 871 ><A
 872 NAME="AEN260"
 873 ></A
 874 ><H2
 875 >COMPLETE LIST OF GLOBAL PARAMETERS</H2
 876 ><P
 877 >Here is a list of all global parameters. See the section of
 878         each parameter for details.  Note that some are synonyms.</P
 879 ><P
 880 ></P
 881 ><UL
 882 ><LI
 883 ><P
 884 ><A
 885 HREF="#ADDPRINTERCOMMAND"
 886 ><TT
 887 CLASS="PARAMETER"
 888 ><I
 889 >add printer command</I
 890 ></TT
 891 ></A
 892 ></P
 893 ></LI
 894 ><LI
 895 ><P
 896 ><A
 897 HREF="#ADDSHARECOMMAND"
 898 ><TT
 899 CLASS="PARAMETER"
 900 ><I
 901 >add share command</I
 902 ></TT
 903 ></A
 904 ></P
 905 ></LI
 906 ><LI
 907 ><P
 908 ><A
 909 HREF="#ADDUSERSCRIPT"
 910 ><TT
 911 CLASS="PARAMETER"
 912 ><I
 913 >add user script</I
 914 ></TT
 915 ></A
 916 ></P
 917 ></LI
 918 ><LI
 919 ><P
 920 ><A
 921 HREF="#ALLOWTRUSTEDDOMAINS"
 922 ><TT
 923 CLASS="PARAMETER"
 924 ><I
 925 >allow trusted domains</I
 926 ></TT
 927 ></A
 928 ></P
 929 ></LI
 930 ><LI
 931 ><P
 932 ><A
 933 HREF="#ANNOUNCEAS"
 934 ><TT
 935 CLASS="PARAMETER"
 936 ><I
 937 >announce as</I
 938 ></TT
 939 ></A
 940 ></P
 941 ></LI
 942 ><LI
 943 ><P
 944 ><A
 945 HREF="#ANNOUNCEVERSION"
 946 ><TT
 947 CLASS="PARAMETER"
 948 ><I
 949 >announce version</I
 950 ></TT
 951 ></A
 952 ></P
 953 ></LI
 954 ><LI
 955 ><P
 956 ><A
 957 HREF="#AUTOSERVICES"
 958 ><TT
 959 CLASS="PARAMETER"
 960 ><I
 961 >auto services</I
 962 ></TT
 963 ></A
 964 ></P
 965 ></LI
 966 ><LI
 967 ><P
 968 ><A
 969 HREF="#BINDINTERFACESONLY"
 970 ><TT
 971 CLASS="PARAMETER"
 972 ><I
 973 >bind interfaces only</I
 974 ></TT
 975 ></A
 976 ></P
 977 ></LI
 978 ><LI
 979 ><P
 980 ><A
 981 HREF="#BROWSELIST"
 982 ><TT
 983 CLASS="PARAMETER"
 984 ><I
 985 >browse list</I
 986 ></TT
 987 ></A
 988 ></P
 989 ></LI
 990 ><LI
 991 ><P
 992 ><A
 993 HREF="#CHANGENOTIFYTIMEOUT"
 994 ><TT
 995 CLASS="PARAMETER"
 996 ><I
 997 >change notify timeout</I
 998 ></TT
 999 ></A
1000 ></P
1001 ></LI
1002 ><LI
1003 ><P
1004 ><A
1005 HREF="#CHANGESHARECOMMAND"
1006 ><TT
1007 CLASS="PARAMETER"
1008 ><I
1009 >change share command</I
1010 ></TT
1011 ></A
1012 ></P
1013 ></LI
1014 ><LI
1015 ><P
1016 ><A
1017 HREF="#CHARACTERSET"
1018 ><TT
1019 CLASS="PARAMETER"
1020 ><I
1021 >character set</I
1022 ></TT
1023 ></A
1024 ></P
1025 ></LI
1026 ><LI
1027 ><P
1028 ><A
1029 HREF="#CLIENTCODEPAGE"
1030 ><TT
1031 CLASS="PARAMETER"
1032 ><I
1033 >client code page</I
1034 ></TT
1035 ></A
1036 ></P
1037 ></LI
1038 ><LI
1039 ><P
1040 ><A
1041 HREF="#CODEPAGEDIRECTORY"
1042 ><TT
1043 CLASS="PARAMETER"
1044 ><I
1045 >code page directory</I
1046 ></TT
1047 ></A
1048 ></P
1049 ></LI
1050 ><LI
1051 ><P
1052 ><A
1053 HREF="#CODINGSYSTEM"
1054 ><TT
1055 CLASS="PARAMETER"
1056 ><I
1057 >coding system</I
1058 ></TT
1059 ></A
1060 ></P
1061 ></LI
1062 ><LI
1063 ><P
1064 ><A
1065 HREF="#CONFIGFILE"
1066 ><TT
1067 CLASS="PARAMETER"
1068 ><I
1069 >config file</I
1070 ></TT
1071 ></A
1072 ></P
1073 ></LI
1074 ><LI
1075 ><P
1076 ><A
1077 HREF="#DEADTIME"
1078 ><TT
1079 CLASS="PARAMETER"
1080 ><I
1081 >deadtime</I
1082 ></TT
1083 ></A
1084 ></P
1085 ></LI
1086 ><LI
1087 ><P
1088 ><A
1089 HREF="#DEBUGHIRESTIMESTAMP"
1090 ><TT
1091 CLASS="PARAMETER"
1092 ><I
1093 >debug hires timestamp</I
1094 ></TT
1095 ></A
1096 ></P
1097 ></LI
1098 ><LI
1099 ><P
1100 ><A
1101 HREF="#DEBUGPID"
1102 ><TT
1103 CLASS="PARAMETER"
1104 ><I
1105 >debug pid</I
1106 ></TT
1107 ></A
1108 ></P
1109 ></LI
1110 ><LI
1111 ><P
1112 ><A
1113 HREF="#DEBUGTIMESTAMP"
1114 ><TT
1115 CLASS="PARAMETER"
1116 ><I
1117 >debug timestamp</I
1118 ></TT
1119 ></A
1120 ></P
1121 ></LI
1122 ><LI
1123 ><P
1124 ><A
1125 HREF="#DEBUGUID"
1126 ><TT
1127 CLASS="PARAMETER"
1128 ><I
1129 >debug uid</I
1130 ></TT
1131 ></A
1132 ></P
1133 ></LI
1134 ><LI
1135 ><P
1136 ><A
1137 HREF="#DEBUGLEVEL"
1138 ><TT
1139 CLASS="PARAMETER"
1140 ><I
1141 >debuglevel</I
1142 ></TT
1143 ></A
1144 ></P
1145 ></LI
1146 ><LI
1147 ><P
1148 ><A
1149 HREF="#DEFAULT"
1150 ><TT
1151 CLASS="PARAMETER"
1152 ><I
1153 >default</I
1154 ></TT
1155 ></A
1156 ></P
1157 ></LI
1158 ><LI
1159 ><P
1160 ><A
1161 HREF="#DEFAULTSERVICE"
1162 ><TT
1163 CLASS="PARAMETER"
1164 ><I
1165 >default service</I
1166 ></TT
1167 ></A
1168 ></P
1169 ></LI
1170 ><LI
1171 ><P
1172 ><A
1173 HREF="#DELETEPRINTERCOMMAND"
1174 ><TT
1175 CLASS="PARAMETER"
1176 ><I
1177 >delete printer command</I
1178 ></TT
1179 ></A
1180 ></P
1181 ></LI
1182 ><LI
1183 ><P
1184 ><A
1185 HREF="#DELETESHARECOMMAND"
1186 ><TT
1187 CLASS="PARAMETER"
1188 ><I
1189 >delete share command</I
1190 ></TT
1191 ></A
1192 ></P
1193 ></LI
1194 ><LI
1195 ><P
1196 ><A
1197 HREF="#DELETEUSERSCRIPT"
1198 ><TT
1199 CLASS="PARAMETER"
1200 ><I
1201 >delete user script</I
1202 ></TT
1203 ></A
1204 ></P
1205 ></LI
1206 ><LI
1207 ><P
1208 ><A
1209 HREF="#DFREECOMMAND"
1210 ><TT
1211 CLASS="PARAMETER"
1212 ><I
1213 >dfree command</I
1214 ></TT
1215 ></A
1216 ></P
1217 ></LI
1218 ><LI
1219 ><P
1220 ><A
1221 HREF="#DISABLESPOOLSS"
1222 ><TT
1223 CLASS="PARAMETER"
1224 ><I
1225 >disable spoolss</I
1226 ></TT
1227 ></A
1228 ></P
1229 ></LI
1230 ><LI
1231 ><P
1232 ><A
1233 HREF="#DNSPROXY"
1234 ><TT
1235 CLASS="PARAMETER"
1236 ><I
1237 >dns proxy</I
1238 ></TT
1239 ></A
1240 ></P
1241 ></LI
1242 ><LI
1243 ><P
1244 ><A
1245 HREF="#DOMAINADMINGROUP"
1246 ><TT
1247 CLASS="PARAMETER"
1248 ><I
1249 >domain admin group</I
1250 ></TT
1251 ></A
1252 ></P
1253 ></LI
1254 ><LI
1255 ><P
1256 ><A
1257 HREF="#DOMAINGUESTGROUP"
1258 ><TT
1259 CLASS="PARAMETER"
1260 ><I
1261 >domain guest group</I
1262 ></TT
1263 ></A
1264 ></P
1265 ></LI
1266 ><LI
1267 ><P
1268 ><A
1269 HREF="#DOMAINLOGONS"
1270 ><TT
1271 CLASS="PARAMETER"
1272 ><I
1273 >domain logons</I
1274 ></TT
1275 ></A
1276 ></P
1277 ></LI
1278 ><LI
1279 ><P
1280 ><A
1281 HREF="#DOMAINMASTER"
1282 ><TT
1283 CLASS="PARAMETER"
1284 ><I
1285 >domain master</I
1286 ></TT
1287 ></A
1288 ></P
1289 ></LI
1290 ><LI
1291 ><P
1292 ><A
1293 HREF="#ENCRYPTPASSWORDS"
1294 ><TT
1295 CLASS="PARAMETER"
1296 ><I
1297 >encrypt passwords</I
1298 ></TT
1299 ></A
1300 ></P
1301 ></LI
1302 ><LI
1303 ><P
1304 ><A
1305 HREF="#ENHANCEDBROWSING"
1306 ><TT
1307 CLASS="PARAMETER"
1308 ><I
1309 >enhanced browsing</I
1310 ></TT
1311 ></A
1312 ></P
1313 ></LI
1314 ><LI
1315 ><P
1316 ><A
1317 HREF="#ENUMPORTSCOMMAND"
1318 ><TT
1319 CLASS="PARAMETER"
1320 ><I
1321 >enumports command</I
1322 ></TT
1323 ></A
1324 ></P
1325 ></LI
1326 ><LI
1327 ><P
1328 ><A
1329 HREF="#GETWDCACHE"
1330 ><TT
1331 CLASS="PARAMETER"
1332 ><I
1333 >getwd cache</I
1334 ></TT
1335 ></A
1336 ></P
1337 ></LI
1338 ><LI
1339 ><P
1340 ><A
1341 HREF="#HIDELOCALUSERS"
1342 ><TT
1343 CLASS="PARAMETER"
1344 ><I
1345 >hide local users</I
1346 ></TT
1347 ></A
1348 ></P
1349 ></LI
1350 ><LI
1351 ><P
1352 ><A
1353 HREF="#HIDEUNREADABLE"
1354 ><TT
1355 CLASS="PARAMETER"
1356 ><I
1357 >hide unreadable</I
1358 ></TT
1359 ></A
1360 ></P
1361 ></LI
1362 ><LI
1363 ><P
1364 ><A
1365 HREF="#HOMEDIRMAP"
1366 ><TT
1367 CLASS="PARAMETER"
1368 ><I
1369 >homedir map</I
1370 ></TT
1371 ></A
1372 ></P
1373 ></LI
1374 ><LI
1375 ><P
1376 ><A
1377 HREF="#HOSTMSDFS"
1378 ><TT
1379 CLASS="PARAMETER"
1380 ><I
1381 >host msdfs</I
1382 ></TT
1383 ></A
1384 ></P
1385 ></LI
1386 ><LI
1387 ><P
1388 ><A
1389 HREF="#HOSTSEQUIV"
1390 ><TT
1391 CLASS="PARAMETER"
1392 ><I
1393 >hosts equiv</I
1394 ></TT
1395 ></A
1396 ></P
1397 ></LI
1398 ><LI
1399 ><P
1400 ><A
1401 HREF="#INTERFACES"
1402 ><TT
1403 CLASS="PARAMETER"
1404 ><I
1405 >interfaces</I
1406 ></TT
1407 ></A
1408 ></P
1409 ></LI
1410 ><LI
1411 ><P
1412 ><A
1413 HREF="#KEEPALIVE"
1414 ><TT
1415 CLASS="PARAMETER"
1416 ><I
1417 >keepalive</I
1418 ></TT
1419 ></A
1420 ></P
1421 ></LI
1422 ><LI
1423 ><P
1424 ><A
1425 HREF="#KERNELOPLOCKS"
1426 ><TT
1427 CLASS="PARAMETER"
1428 ><I
1429 >kernel oplocks</I
1430 ></TT
1431 ></A
1432 ></P
1433 ></LI
1434 ><LI
1435 ><P
1436 ><A
1437 HREF="#LANMANAUTH"
1438 ><TT
1439 CLASS="PARAMETER"
1440 ><I
1441 >lanman auth</I
1442 ></TT
1443 ></A
1444 ></P
1445 ></LI
1446 ><LI
1447 ><P
1448 ><A
1449 HREF="#LARGEREADWRITE"
1450 ><TT
1451 CLASS="PARAMETER"
1452 ><I
1453 >large readwrite</I
1454 ></TT
1455 ></A
1456 ></P
1457 ></LI
1458 ><LI
1459 ><P
1460 ><A
1461 HREF="#LDAPADMINDN"
1462 ><TT
1463 CLASS="PARAMETER"
1464 ><I
1465 >ldap admin dn</I
1466 ></TT
1467 ></A
1468 ></P
1469 ></LI
1470 ><LI
1471 ><P
1472 ><A
1473 HREF="#LDAPFILTER"
1474 ><TT
1475 CLASS="PARAMETER"
1476 ><I
1477 >ldap filter</I
1478 ></TT
1479 ></A
1480 ></P
1481 ></LI
1482 ><LI
1483 ><P
1484 ><A
1485 HREF="#LDAPPORT"
1486 ><TT
1487 CLASS="PARAMETER"
1488 ><I
1489 >ldap port</I
1490 ></TT
1491 ></A
1492 ></P
1493 ></LI
1494 ><LI
1495 ><P
1496 ><A
1497 HREF="#LDAPSERVER"
1498 ><TT
1499 CLASS="PARAMETER"
1500 ><I
1501 >ldap server</I
1502 ></TT
1503 ></A
1504 ></P
1505 ></LI
1506 ><LI
1507 ><P
1508 ><A
1509 HREF="#LDAPSSL"
1510 ><TT
1511 CLASS="PARAMETER"
1512 ><I
1513 >ldap ssl</I
1514 ></TT
1515 ></A
1516 ></P
1517 ></LI
1518 ><LI
1519 ><P
1520 ><A
1521 HREF="#LDAPSUFFIX"
1522 ><TT
1523 CLASS="PARAMETER"
1524 ><I
1525 >ldap suffix</I
1526 ></TT
1527 ></A
1528 ></P
1529 ></LI
1530 ><LI
1531 ><P
1532 ><A
1533 HREF="#LMANNOUNCE"
1534 ><TT
1535 CLASS="PARAMETER"
1536 ><I
1537 >lm announce</I
1538 ></TT
1539 ></A
1540 ></P
1541 ></LI
1542 ><LI
1543 ><P
1544 ><A
1545 HREF="#LMINTERVAL"
1546 ><TT
1547 CLASS="PARAMETER"
1548 ><I
1549 >lm interval</I
1550 ></TT
1551 ></A
1552 ></P
1553 ></LI
1554 ><LI
1555 ><P
1556 ><A
1557 HREF="#LOADPRINTERS"
1558 ><TT
1559 CLASS="PARAMETER"
1560 ><I
1561 >load printers</I
1562 ></TT
1563 ></A
1564 ></P
1565 ></LI
1566 ><LI
1567 ><P
1568 ><A
1569 HREF="#LOCALMASTER"
1570 ><TT
1571 CLASS="PARAMETER"
1572 ><I
1573 >local master</I
1574 ></TT
1575 ></A
1576 ></P
1577 ></LI
1578 ><LI
1579 ><P
1580 ><A
1581 HREF="#LOCKDIR"
1582 ><TT
1583 CLASS="PARAMETER"
1584 ><I
1585 >lock dir</I
1586 ></TT
1587 ></A
1588 ></P
1589 ></LI
1590 ><LI
1591 ><P
1592 ><A
1593 HREF="#LOCKDIRECTORY"
1594 ><TT
1595 CLASS="PARAMETER"
1596 ><I
1597 >lock directory</I
1598 ></TT
1599 ></A
1600 ></P
1601 ></LI
1602 ><LI
1603 ><P
1604 ><A
1605 HREF="#LOCKSPINCOUNT"
1606 ><TT
1607 CLASS="PARAMETER"
1608 ><I
1609 >lock spin count</I
1610 ></TT
1611 ></A
1612 ></P
1613 ></LI
1614 ><LI
1615 ><P
1616 ><A
1617 HREF="#LOCKSPINTIME"
1618 ><TT
1619 CLASS="PARAMETER"
1620 ><I
1621 >lock spin time</I
1622 ></TT
1623 ></A
1624 ></P
1625 ></LI
1626 ><LI
1627 ><P
1628 ><A
1629 HREF="#PIDDIRECTORY"
1630 ><TT
1631 CLASS="PARAMETER"
1632 ><I
1633 >pid directory</I
1634 ></TT
1635 ></A
1636 ></P
1637 ></LI
1638 ><LI
1639 ><P
1640 ><A
1641 HREF="#LOGFILE"
1642 ><TT
1643 CLASS="PARAMETER"
1644 ><I
1645 >log file</I
1646 ></TT
1647 ></A
1648 ></P
1649 ></LI
1650 ><LI
1651 ><P
1652 ><A
1653 HREF="#LOGLEVEL"
1654 ><TT
1655 CLASS="PARAMETER"
1656 ><I
1657 >log level</I
1658 ></TT
1659 ></A
1660 ></P
1661 ></LI
1662 ><LI
1663 ><P
1664 ><A
1665 HREF="#LOGONDRIVE"
1666 ><TT
1667 CLASS="PARAMETER"
1668 ><I
1669 >logon drive</I
1670 ></TT
1671 ></A
1672 ></P
1673 ></LI
1674 ><LI
1675 ><P
1676 ><A
1677 HREF="#LOGONHOME"
1678 ><TT
1679 CLASS="PARAMETER"
1680 ><I
1681 >logon home</I
1682 ></TT
1683 ></A
1684 ></P
1685 ></LI
1686 ><LI
1687 ><P
1688 ><A
1689 HREF="#LOGONPATH"
1690 ><TT
1691 CLASS="PARAMETER"
1692 ><I
1693 >logon path</I
1694 ></TT
1695 ></A
1696 ></P
1697 ></LI
1698 ><LI
1699 ><P
1700 ><A
1701 HREF="#LOGONSCRIPT"
1702 ><TT
1703 CLASS="PARAMETER"
1704 ><I
1705 >logon script</I
1706 ></TT
1707 ></A
1708 ></P
1709 ></LI
1710 ><LI
1711 ><P
1712 ><A
1713 HREF="#LPQCACHETIME"
1714 ><TT
1715 CLASS="PARAMETER"
1716 ><I
1717 >lpq cache time</I
1718 ></TT
1719 ></A
1720 ></P
1721 ></LI
1722 ><LI
1723 ><P
1724 ><A
1725 HREF="#MACHINEPASSWORDTIMEOUT"
1726 ><TT
1727 CLASS="PARAMETER"
1728 ><I
1729 >machine password timeout</I
1730 ></TT
1731 ></A
1732 ></P
1733 ></LI
1734 ><LI
1735 ><P
1736 ><A
1737 HREF="#MANGLEDSTACK"
1738 ><TT
1739 CLASS="PARAMETER"
1740 ><I
1741 >mangled stack</I
1742 ></TT
1743 ></A
1744 ></P
1745 ></LI
1746 ><LI
1747 ><P
1748 ><A
1749 HREF="#MANGLINGMETHOD"
1750 ><TT
1751 CLASS="PARAMETER"
1752 ><I
1753 >mangling method</I
1754 ></TT
1755 ></A
1756 ></P
1757 ></LI
1758 ><LI
1759 ><P
1760 ><A
1761 HREF="#MAPTOGUEST"
1762 ><TT
1763 CLASS="PARAMETER"
1764 ><I
1765 >map to guest</I
1766 ></TT
1767 ></A
1768 ></P
1769 ></LI
1770 ><LI
1771 ><P
1772 ><A
1773 HREF="#MAXDISKSIZE"
1774 ><TT
1775 CLASS="PARAMETER"
1776 ><I
1777 >max disk size</I
1778 ></TT
1779 ></A
1780 ></P
1781 ></LI
1782 ><LI
1783 ><P
1784 ><A
1785 HREF="#MAXLOGSIZE"
1786 ><TT
1787 CLASS="PARAMETER"
1788 ><I
1789 >max log size</I
1790 ></TT
1791 ></A
1792 ></P
1793 ></LI
1794 ><LI
1795 ><P
1796 ><A
1797 HREF="#MAXMUX"
1798 ><TT
1799 CLASS="PARAMETER"
1800 ><I
1801 >max mux</I
1802 ></TT
1803 ></A
1804 ></P
1805 ></LI
1806 ><LI
1807 ><P
1808 ><A
1809 HREF="#MAXOPENFILES"
1810 ><TT
1811 CLASS="PARAMETER"
1812 ><I
1813 >max open files</I
1814 ></TT
1815 ></A
1816 ></P
1817 ></LI
1818 ><LI
1819 ><P
1820 ><A
1821 HREF="#MAXPROTOCOL"
1822 ><TT
1823 CLASS="PARAMETER"
1824 ><I
1825 >max protocol</I
1826 ></TT
1827 ></A
1828 ></P
1829 ></LI
1830 ><LI
1831 ><P
1832 ><A
1833 HREF="#MAXSMBDPROCESSES"
1834 ><TT
1835 CLASS="PARAMETER"
1836 ><I
1837 >max smbd processes</I
1838 ></TT
1839 ></A
1840 ></P
1841 ></LI
1842 ><LI
1843 ><P
1844 ><A
1845 HREF="#MAXTTL"
1846 ><TT
1847 CLASS="PARAMETER"
1848 ><I
1849 >max ttl</I
1850 ></TT
1851 ></A
1852 ></P
1853 ></LI
1854 ><LI
1855 ><P
1856 ><A
1857 HREF="#MAXWINSTTL"
1858 ><TT
1859 CLASS="PARAMETER"
1860 ><I
1861 >max wins ttl</I
1862 ></TT
1863 ></A
1864 ></P
1865 ></LI
1866 ><LI
1867 ><P
1868 ><A
1869 HREF="#MAXXMIT"
1870 ><TT
1871 CLASS="PARAMETER"
1872 ><I
1873 >max xmit</I
1874 ></TT
1875 ></A
1876 ></P
1877 ></LI
1878 ><LI
1879 ><P
1880 ><A
1881 HREF="#MESSAGECOMMAND"
1882 ><TT
1883 CLASS="PARAMETER"
1884 ><I
1885 >message command</I
1886 ></TT
1887 ></A
1888 ></P
1889 ></LI
1890 ><LI
1891 ><P
1892 ><A
1893 HREF="#MINPASSWDLENGTH"
1894 ><TT
1895 CLASS="PARAMETER"
1896 ><I
1897 >min passwd length</I
1898 ></TT
1899 ></A
1900 ></P
1901 ></LI
1902 ><LI
1903 ><P
1904 ><A
1905 HREF="#MINPASSWORDLENGTH"
1906 ><TT
1907 CLASS="PARAMETER"
1908 ><I
1909 >min password length</I
1910 ></TT
1911 ></A
1912 ></P
1913 ></LI
1914 ><LI
1915 ><P
1916 ><A
1917 HREF="#MINPROTOCOL"
1918 ><TT
1919 CLASS="PARAMETER"
1920 ><I
1921 >min protocol</I
1922 ></TT
1923 ></A
1924 ></P
1925 ></LI
1926 ><LI
1927 ><P
1928 ><A
1929 HREF="#MINWINSTTL"
1930 ><TT
1931 CLASS="PARAMETER"
1932 ><I
1933 >min wins ttl</I
1934 ></TT
1935 ></A
1936 ></P
1937 ></LI
1938 ><LI
1939 ><P
1940 ><A
1941 HREF="#NAMERESOLVEORDER"
1942 ><TT
1943 CLASS="PARAMETER"
1944 ><I
1945 >name resolve order</I
1946 ></TT
1947 ></A
1948 ></P
1949 ></LI
1950 ><LI
1951 ><P
1952 ><A
1953 HREF="#NETBIOSALIASES"
1954 ><TT
1955 CLASS="PARAMETER"
1956 ><I
1957 >netbios aliases</I
1958 ></TT
1959 ></A
1960 ></P
1961 ></LI
1962 ><LI
1963 ><P
1964 ><A
1965 HREF="#NETBIOSNAME"
1966 ><TT
1967 CLASS="PARAMETER"
1968 ><I
1969 >netbios name</I
1970 ></TT
1971 ></A
1972 ></P
1973 ></LI
1974 ><LI
1975 ><P
1976 ><A
1977 HREF="#NETBIOSSCOPE"
1978 ><TT
1979 CLASS="PARAMETER"
1980 ><I
1981 >netbios scope</I
1982 ></TT
1983 ></A
1984 ></P
1985 ></LI
1986 ><LI
1987 ><P
1988 ><A
1989 HREF="#NISHOMEDIR"
1990 ><TT
1991 CLASS="PARAMETER"
1992 ><I
1993 >nis homedir</I
1994 ></TT
1995 ></A
1996 ></P
1997 ></LI
1998 ><LI
1999 ><P
2000 ><A
2001 HREF="#NTPIPESUPPORT"
2002 ><TT
2003 CLASS="PARAMETER"
2004 ><I
2005 >nt pipe support</I
2006 ></TT
2007 ></A
2008 ></P
2009 ></LI
2010 ><LI
2011 ><P
2012 ><A
2013 HREF="#NTSMBSUPPORT"
2014 ><TT
2015 CLASS="PARAMETER"
2016 ><I
2017 >nt smb support</I
2018 ></TT
2019 ></A
2020 ></P
2021 ></LI
2022 ><LI
2023 ><P
2024 ><A
2025 HREF="#NTSTATUSSUPPORT"
2026 ><TT
2027 CLASS="PARAMETER"
2028 ><I
2029 >nt status support</I
2030 ></TT
2031 ></A
2032 ></P
2033 ></LI
2034 ><LI
2035 ><P
2036 ><A
2037 HREF="#NULLPASSWORDS"
2038 ><TT
2039 CLASS="PARAMETER"
2040 ><I
2041 >null passwords</I
2042 ></TT
2043 ></A
2044 ></P
2045 ></LI
2046 ><LI
2047 ><P
2048 ><A
2049 HREF="#OBEYPAMRESTRICTIONS"
2050 ><TT
2051 CLASS="PARAMETER"
2052 ><I
2053 >obey pam restrictions</I
2054 ></TT
2055 ></A
2056 ></P
2057 ></LI
2058 ><LI
2059 ><P
2060 ><A
2061 HREF="#OPLOCKBREAKWAITTIME"
2062 ><TT
2063 CLASS="PARAMETER"
2064 ><I
2065 >oplock break wait time</I
2066 ></TT
2067 ></A
2068 ></P
2069 ></LI
2070 ><LI
2071 ><P
2072 ><A
2073 HREF="#OSLEVEL"
2074 ><TT
2075 CLASS="PARAMETER"
2076 ><I
2077 >os level</I
2078 ></TT
2079 ></A
2080 ></P
2081 ></LI
2082 ><LI
2083 ><P
2084 ><A
2085 HREF="#OS2DRIVERMAP"
2086 ><TT
2087 CLASS="PARAMETER"
2088 ><I
2089 >os2 driver map</I
2090 ></TT
2091 ></A
2092 ></P
2093 ></LI
2094 ><LI
2095 ><P
2096 ><A
2097 HREF="#PAMPASSWORDCHANGE"
2098 ><TT
2099 CLASS="PARAMETER"
2100 ><I
2101 >pam password change</I
2102 ></TT
2103 ></A
2104 ></P
2105 ></LI
2106 ><LI
2107 ><P
2108 ><A
2109 HREF="#PANICACTION"
2110 ><TT
2111 CLASS="PARAMETER"
2112 ><I
2113 >panic action</I
2114 ></TT
2115 ></A
2116 ></P
2117 ></LI
2118 ><LI
2119 ><P
2120 ><A
2121 HREF="#PASSWDCHAT"
2122 ><TT
2123 CLASS="PARAMETER"
2124 ><I
2125 >passwd chat</I
2126 ></TT
2127 ></A
2128 ></P
2129 ></LI
2130 ><LI
2131 ><P
2132 ><A
2133 HREF="#PASSWDCHATDEBUG"
2134 ><TT
2135 CLASS="PARAMETER"
2136 ><I
2137 >passwd chat debug</I
2138 ></TT
2139 ></A
2140 ></P
2141 ></LI
2142 ><LI
2143 ><P
2144 ><A
2145 HREF="#PASSWDPROGRAM"
2146 ><TT
2147 CLASS="PARAMETER"
2148 ><I
2149 >passwd program</I
2150 ></TT
2151 ></A
2152 ></P
2153 ></LI
2154 ><LI
2155 ><P
2156 ><A
2157 HREF="#PASSWORDLEVEL"
2158 ><TT
2159 CLASS="PARAMETER"
2160 ><I
2161 >password level</I
2162 ></TT
2163 ></A
2164 ></P
2165 ></LI
2166 ><LI
2167 ><P
2168 ><A
2169 HREF="#PASSWORDSERVER"
2170 ><TT
2171 CLASS="PARAMETER"
2172 ><I
2173 >password server</I
2174 ></TT
2175 ></A
2176 ></P
2177 ></LI
2178 ><LI
2179 ><P
2180 ><A
2181 HREF="#PREFEREDMASTER"
2182 ><TT
2183 CLASS="PARAMETER"
2184 ><I
2185 >prefered master</I
2186 ></TT
2187 ></A
2188 ></P
2189 ></LI
2190 ><LI
2191 ><P
2192 ><A
2193 HREF="#PREFERREDMASTER"
2194 ><TT
2195 CLASS="PARAMETER"
2196 ><I
2197 >preferred master</I
2198 ></TT
2199 ></A
2200 ></P
2201 ></LI
2202 ><LI
2203 ><P
2204 ><A
2205 HREF="#PRELOAD"
2206 ><TT
2207 CLASS="PARAMETER"
2208 ><I
2209 >preload</I
2210 ></TT
2211 ></A
2212 ></P
2213 ></LI
2214 ><LI
2215 ><P
2216 ><A
2217 HREF="#PRINTCAP"
2218 ><TT
2219 CLASS="PARAMETER"
2220 ><I
2221 >printcap</I
2222 ></TT
2223 ></A
2224 ></P
2225 ></LI
2226 ><LI
2227 ><P
2228 ><A
2229 HREF="#PRINTCAPNAME"
2230 ><TT
2231 CLASS="PARAMETER"
2232 ><I
2233 >printcap name</I
2234 ></TT
2235 ></A
2236 ></P
2237 ></LI
2238 ><LI
2239 ><P
2240 ><A
2241 HREF="#PRINTERDRIVERFILE"
2242 ><TT
2243 CLASS="PARAMETER"
2244 ><I
2245 >printer driver file</I
2246 ></TT
2247 ></A
2248 ></P
2249 ></LI
2250 ><LI
2251 ><P
2252 ><A
2253 HREF="#PROTOCOL"
2254 ><TT
2255 CLASS="PARAMETER"
2256 ><I
2257 >protocol</I
2258 ></TT
2259 ></A
2260 ></P
2261 ></LI
2262 ><LI
2263 ><P
2264 ><A
2265 HREF="#READBMPX"
2266 ><TT
2267 CLASS="PARAMETER"
2268 ><I
2269 >read bmpx</I
2270 ></TT
2271 ></A
2272 ></P
2273 ></LI
2274 ><LI
2275 ><P
2276 ><A
2277 HREF="#READRAW"
2278 ><TT
2279 CLASS="PARAMETER"
2280 ><I
2281 >read raw</I
2282 ></TT
2283 ></A
2284 ></P
2285 ></LI
2286 ><LI
2287 ><P
2288 ><A
2289 HREF="#READSIZE"
2290 ><TT
2291 CLASS="PARAMETER"
2292 ><I
2293 >read size</I
2294 ></TT
2295 ></A
2296 ></P
2297 ></LI
2298 ><LI
2299 ><P
2300 ><A
2301 HREF="#REMOTEANNOUNCE"
2302 ><TT
2303 CLASS="PARAMETER"
2304 ><I
2305 >remote announce</I
2306 ></TT
2307 ></A
2308 ></P
2309 ></LI
2310 ><LI
2311 ><P
2312 ><A
2313 HREF="#REMOTEBROWSESYNC"
2314 ><TT
2315 CLASS="PARAMETER"
2316 ><I
2317 >remote browse sync</I
2318 ></TT
2319 ></A
2320 ></P
2321 ></LI
2322 ><LI
2323 ><P
2324 ><A
2325 HREF="#RESTRICTANONYMOUS"
2326 ><TT
2327 CLASS="PARAMETER"
2328 ><I
2329 >restrict anonymous</I
2330 ></TT
2331 ></A
2332 ></P
2333 ></LI
2334 ><LI
2335 ><P
2336 ><A
2337 HREF="#ROOT"
2338 ><TT
2339 CLASS="PARAMETER"
2340 ><I
2341 >root</I
2342 ></TT
2343 ></A
2344 ></P
2345 ></LI
2346 ><LI
2347 ><P
2348 ><A
2349 HREF="#ROOTDIR"
2350 ><TT
2351 CLASS="PARAMETER"
2352 ><I
2353 >root dir</I
2354 ></TT
2355 ></A
2356 ></P
2357 ></LI
2358 ><LI
2359 ><P
2360 ><A
2361 HREF="#ROOTDIRECTORY"
2362 ><TT
2363 CLASS="PARAMETER"
2364 ><I
2365 >root directory</I
2366 ></TT
2367 ></A
2368 ></P
2369 ></LI
2370 ><LI
2371 ><P
2372 ><A
2373 HREF="#SECURITY"
2374 ><TT
2375 CLASS="PARAMETER"
2376 ><I
2377 >security</I
2378 ></TT
2379 ></A
2380 ></P
2381 ></LI
2382 ><LI
2383 ><P
2384 ><A
2385 HREF="#SERVERSTRING"
2386 ><TT
2387 CLASS="PARAMETER"
2388 ><I
2389 >server string</I
2390 ></TT
2391 ></A
2392 ></P
2393 ></LI
2394 ><LI
2395 ><P
2396 ><A
2397 HREF="#SHOWADDPRINTERWIZARD"
2398 ><TT
2399 CLASS="PARAMETER"
2400 ><I
2401 >show add printer wizard</I
2402 ></TT
2403 ></A
2404 ></P
2405 ></LI
2406 ><LI
2407 ><P
2408 ><A
2409 HREF="#SMBPASSWDFILE"
2410 ><TT
2411 CLASS="PARAMETER"
2412 ><I
2413 >smb passwd file</I
2414 ></TT
2415 ></A
2416 ></P
2417 ></LI
2418 ><LI
2419 ><P
2420 ><A
2421 HREF="#SOCKETADDRESS"
2422 ><TT
2423 CLASS="PARAMETER"
2424 ><I
2425 >socket address</I
2426 ></TT
2427 ></A
2428 ></P
2429 ></LI
2430 ><LI
2431 ><P
2432 ><A
2433 HREF="#SOCKETOPTIONS"
2434 ><TT
2435 CLASS="PARAMETER"
2436 ><I
2437 >socket options</I
2438 ></TT
2439 ></A
2440 ></P
2441 ></LI
2442 ><LI
2443 ><P
2444 ><A
2445 HREF="#SOURCEENVIRONMENT"
2446 ><TT
2447 CLASS="PARAMETER"
2448 ><I
2449 >source environment</I
2450 ></TT
2451 ></A
2452 ></P
2453 ></LI
2454 ><LI
2455 ><P
2456 ><A
2457 HREF="#SSL"
2458 ><TT
2459 CLASS="PARAMETER"
2460 ><I
2461 >ssl</I
2462 ></TT
2463 ></A
2464 ></P
2465 ></LI
2466 ><LI
2467 ><P
2468 ><A
2469 HREF="#SSLCACERTDIR"
2470 ><TT
2471 CLASS="PARAMETER"
2472 ><I
2473 >ssl CA certDir</I
2474 ></TT
2475 ></A
2476 ></P
2477 ></LI
2478 ><LI
2479 ><P
2480 ><A
2481 HREF="#SSLCACERTFILE"
2482 ><TT
2483 CLASS="PARAMETER"
2484 ><I
2485 >ssl CA certFile</I
2486 ></TT
2487 ></A
2488 ></P
2489 ></LI
2490 ><LI
2491 ><P
2492 ><A
2493 HREF="#SSLCIPHERS"
2494 ><TT
2495 CLASS="PARAMETER"
2496 ><I
2497 >ssl ciphers</I
2498 ></TT
2499 ></A
2500 ></P
2501 ></LI
2502 ><LI
2503 ><P
2504 ><A
2505 HREF="#SSLCLIENTCERT"
2506 ><TT
2507 CLASS="PARAMETER"
2508 ><I
2509 >ssl client cert</I
2510 ></TT
2511 ></A
2512 ></P
2513 ></LI
2514 ><LI
2515 ><P
2516 ><A
2517 HREF="#SSLCLIENTKEY"
2518 ><TT
2519 CLASS="PARAMETER"
2520 ><I
2521 >ssl client key</I
2522 ></TT
2523 ></A
2524 ></P
2525 ></LI
2526 ><LI
2527 ><P
2528 ><A
2529 HREF="#SSLCOMPATIBILITY"
2530 ><TT
2531 CLASS="PARAMETER"
2532 ><I
2533 >ssl compatibility</I
2534 ></TT
2535 ></A
2536 ></P
2537 ></LI
2538 ><LI
2539 ><P
2540 ><A
2541 HREF="#SSLEGDSOCKET"
2542 ><TT
2543 CLASS="PARAMETER"
2544 ><I
2545 >ssl egd socket</I
2546 ></TT
2547 ></A
2548 ></P
2549 ></LI
2550 ><LI
2551 ><P
2552 ><A
2553 HREF="#SSLENTROPYBYTES"
2554 ><TT
2555 CLASS="PARAMETER"
2556 ><I
2557 >ssl entropy bytes</I
2558 ></TT
2559 ></A
2560 ></P
2561 ></LI
2562 ><LI
2563 ><P
2564 ><A
2565 HREF="#SSLENTROPYFILE"
2566 ><TT
2567 CLASS="PARAMETER"
2568 ><I
2569 >ssl entropy file</I
2570 ></TT
2571 ></A
2572 ></P
2573 ></LI
2574 ><LI
2575 ><P
2576 ><A
2577 HREF="#SSLHOSTS"
2578 ><TT
2579 CLASS="PARAMETER"
2580 ><I
2581 >ssl hosts</I
2582 ></TT
2583 ></A
2584 ></P
2585 ></LI
2586 ><LI
2587 ><P
2588 ><A
2589 HREF="#SSLHOSTSRESIGN"
2590 ><TT
2591 CLASS="PARAMETER"
2592 ><I
2593 >ssl hosts resign</I
2594 ></TT
2595 ></A
2596 ></P
2597 ></LI
2598 ><LI
2599 ><P
2600 ><A
2601 HREF="#SSLREQUIRECLIENTCERT"
2602 ><TT
2603 CLASS="PARAMETER"
2604 ><I
2605 >ssl require clientcert</I
2606 ></TT
2607 ></A
2608 ></P
2609 ></LI
2610 ><LI
2611 ><P
2612 ><A
2613 HREF="#SSLREQUIRESERVERCERT"
2614 ><TT
2615 CLASS="PARAMETER"
2616 ><I
2617 >ssl require servercert</I
2618 ></TT
2619 ></A
2620 ></P
2621 ></LI
2622 ><LI
2623 ><P
2624 ><A
2625 HREF="#SSLSERVERCERT"
2626 ><TT
2627 CLASS="PARAMETER"
2628 ><I
2629 >ssl server cert</I
2630 ></TT
2631 ></A
2632 ></P
2633 ></LI
2634 ><LI
2635 ><P
2636 ><A
2637 HREF="#SSLSERVERKEY"
2638 ><TT
2639 CLASS="PARAMETER"
2640 ><I
2641 >ssl server key</I
2642 ></TT
2643 ></A
2644 ></P
2645 ></LI
2646 ><LI
2647 ><P
2648 ><A
2649 HREF="#SSLVERSION"
2650 ><TT
2651 CLASS="PARAMETER"
2652 ><I
2653 >ssl version</I
2654 ></TT
2655 ></A
2656 ></P
2657 ></LI
2658 ><LI
2659 ><P
2660 ><A
2661 HREF="#STATCACHE"
2662 ><TT
2663 CLASS="PARAMETER"
2664 ><I
2665 >stat cache</I
2666 ></TT
2667 ></A
2668 ></P
2669 ></LI
2670 ><LI
2671 ><P
2672 ><A
2673 HREF="#STATCACHESIZE"
2674 ><TT
2675 CLASS="PARAMETER"
2676 ><I
2677 >stat cache size</I
2678 ></TT
2679 ></A
2680 ></P
2681 ></LI
2682 ><LI
2683 ><P
2684 ><A
2685 HREF="#STRIPDOT"
2686 ><TT
2687 CLASS="PARAMETER"
2688 ><I
2689 >strip dot</I
2690 ></TT
2691 ></A
2692 ></P
2693 ></LI
2694 ><LI
2695 ><P
2696 ><A
2697 HREF="#SYSLOG"
2698 ><TT
2699 CLASS="PARAMETER"
2700 ><I
2701 >syslog</I
2702 ></TT
2703 ></A
2704 ></P
2705 ></LI
2706 ><LI
2707 ><P
2708 ><A
2709 HREF="#SYSLOGONLY"
2710 ><TT
2711 CLASS="PARAMETER"
2712 ><I
2713 >syslog only</I
2714 ></TT
2715 ></A
2716 ></P
2717 ></LI
2718 ><LI
2719 ><P
2720 ><A
2721 HREF="#TEMPLATEHOMEDIR"
2722 ><TT
2723 CLASS="PARAMETER"
2724 ><I
2725 >template homedir</I
2726 ></TT
2727 ></A
2728 ></P
2729 ></LI
2730 ><LI
2731 ><P
2732 ><A
2733 HREF="#TEMPLATESHELL"
2734 ><TT
2735 CLASS="PARAMETER"
2736 ><I
2737 >template shell</I
2738 ></TT
2739 ></A
2740 ></P
2741 ></LI
2742 ><LI
2743 ><P
2744 ><A
2745 HREF="#TIMEOFFSET"
2746 ><TT
2747 CLASS="PARAMETER"
2748 ><I
2749 >time offset</I
2750 ></TT
2751 ></A
2752 ></P
2753 ></LI
2754 ><LI
2755 ><P
2756 ><A
2757 HREF="#TIMESERVER"
2758 ><TT
2759 CLASS="PARAMETER"
2760 ><I
2761 >time server</I
2762 ></TT
2763 ></A
2764 ></P
2765 ></LI
2766 ><LI
2767 ><P
2768 ><A
2769 HREF="#TIMESTAMPLOGS"
2770 ><TT
2771 CLASS="PARAMETER"
2772 ><I
2773 >timestamp logs</I
2774 ></TT
2775 ></A
2776 ></P
2777 ></LI
2778 ><LI
2779 ><P
2780 ><A
2781 HREF="#TOTALPRINTJOBS"
2782 ><TT
2783 CLASS="PARAMETER"
2784 ><I
2785 >total print jobs</I
2786 ></TT
2787 ></A
2788 ></P
2789 ></LI
2790 ><LI
2791 ><P
2792 ><A
2793 HREF="#UNIXEXTENSIONS"
2794 ><TT
2795 CLASS="PARAMETER"
2796 ><I
2797 >unix extensions</I
2798 ></TT
2799 ></A
2800 ></P
2801 ></LI
2802 ><LI
2803 ><P
2804 ><A
2805 HREF="#UNIXPASSWORDSYNC"
2806 ><TT
2807 CLASS="PARAMETER"
2808 ><I
2809 >unix password sync</I
2810 ></TT
2811 ></A
2812 ></P
2813 ></LI
2814 ><LI
2815 ><P
2816 ><A
2817 HREF="#UPDATEENCRYPTED"
2818 ><TT
2819 CLASS="PARAMETER"
2820 ><I
2821 >update encrypted</I
2822 ></TT
2823 ></A
2824 ></P
2825 ></LI
2826 ><LI
2827 ><P
2828 ><A
2829 HREF="#USEMMAP"
2830 ><TT
2831 CLASS="PARAMETER"
2832 ><I
2833 >use mmap</I
2834 ></TT
2835 ></A
2836 ></P
2837 ></LI
2838 ><LI
2839 ><P
2840 ><A
2841 HREF="#USERHOSTS"
2842 ><TT
2843 CLASS="PARAMETER"
2844 ><I
2845 >use rhosts</I
2846 ></TT
2847 ></A
2848 ></P
2849 ></LI
2850 ><LI
2851 ><P
2852 ><A
2853 HREF="#USERNAMELEVEL"
2854 ><TT
2855 CLASS="PARAMETER"
2856 ><I
2857 >username level</I
2858 ></TT
2859 ></A
2860 ></P
2861 ></LI
2862 ><LI
2863 ><P
2864 ><A
2865 HREF="#USERNAMEMAP"
2866 ><TT
2867 CLASS="PARAMETER"
2868 ><I
2869 >username map</I
2870 ></TT
2871 ></A
2872 ></P
2873 ></LI
2874 ><LI
2875 ><P
2876 ><A
2877 HREF="#UTMP"
2878 ><TT
2879 CLASS="PARAMETER"
2880 ><I
2881 >utmp</I
2882 ></TT
2883 ></A
2884 ></P
2885 ></LI
2886 ><LI
2887 ><P
2888 ><A
2889 HREF="#UTMPDIRECTORY"
2890 ><TT
2891 CLASS="PARAMETER"
2892 ><I
2893 >utmp directory</I
2894 ></TT
2895 ></A
2896 ></P
2897 ></LI
2898 ><LI
2899 ><P
2900 ><A
2901 HREF="#VALIDCHARS"
2902 ><TT
2903 CLASS="PARAMETER"
2904 ><I
2905 >valid chars</I
2906 ></TT
2907 ></A
2908 ></P
2909 ></LI
2910 ><LI
2911 ><P
2912 ><A
2913 HREF="#WINBINDCACHETIME"
2914 ><TT
2915 CLASS="PARAMETER"
2916 ><I
2917 >winbind cache time</I
2918 ></TT
2919 ></A
2920 ></P
2921 ></LI
2922 ><LI
2923 ><P
2924 ><A
2925 HREF="#WINBINDENUMUSERS"
2926 ><TT
2927 CLASS="PARAMETER"
2928 ><I
2929 >winbind enum users</I
2930 ></TT
2931 ></A
2932 ></P
2933 ></LI
2934 ><LI
2935 ><P
2936 ><A
2937 HREF="#WINBINDENUMGROUPS"
2938 ><TT
2939 CLASS="PARAMETER"
2940 ><I
2941 >winbind enum groups</I
2942 ></TT
2943 ></A
2944 ></P
2945 ></LI
2946 ><LI
2947 ><P
2948 ><A
2949 HREF="#WINBINDGID"
2950 ><TT
2951 CLASS="PARAMETER"
2952 ><I
2953 >winbind gid</I
2954 ></TT
2955 ></A
2956 ></P
2957 ></LI
2958 ><LI
2959 ><P
2960 ><A
2961 HREF="#WINBINDSEPARATOR"
2962 ><TT
2963 CLASS="PARAMETER"
2964 ><I
2965 >winbind separator</I
2966 ></TT
2967 ></A
2968 ></P
2969 ></LI
2970 ><LI
2971 ><P
2972 ><A
2973 HREF="#WINBINDUID"
2974 ><TT
2975 CLASS="PARAMETER"
2976 ><I
2977 >winbind uid</I
2978 ></TT
2979 ></A
2980 ></P
2981 ></LI
2982 ><LI
2983 ><P
2984 ><A
2985 HREF="#WINBINDUSEDEFAULTDOMAIN"
2986 ><TT
2987 CLASS="PARAMETER"
2988 ><I
2989 >winbind use default domain</I
2990 ></TT
2991 ></A
2992 ></P
2993 ></LI
2994 ><LI
2995 ><P
2996 ><A
2997 HREF="#WINSHOOK"
2998 ><TT
2999 CLASS="PARAMETER"
3000 ><I
3001 >wins hook</I
3002 ></TT
3003 ></A
3004 ></P
3005 ></LI
3006 ><LI
3007 ><P
3008 ><A
3009 HREF="#WINSPROXY"
3010 ><TT
3011 CLASS="PARAMETER"
3012 ><I
3013 >wins proxy</I
3014 ></TT
3015 ></A
3016 ></P
3017 ></LI
3018 ><LI
3019 ><P
3020 ><A
3021 HREF="#WINSSERVER"
3022 ><TT
3023 CLASS="PARAMETER"
3024 ><I
3025 >wins server</I
3026 ></TT
3027 ></A
3028 ></P
3029 ></LI
3030 ><LI
3031 ><P
3032 ><A
3033 HREF="#WINSSUPPORT"
3034 ><TT
3035 CLASS="PARAMETER"
3036 ><I
3037 >wins support</I
3038 ></TT
3039 ></A
3040 ></P
3041 ></LI
3042 ><LI
3043 ><P
3044 ><A
3045 HREF="#WORKGROUP"
3046 ><TT
3047 CLASS="PARAMETER"
3048 ><I
3049 >workgroup</I
3050 ></TT
3051 ></A
3052 ></P
3053 ></LI
3054 ><LI
3055 ><P
3056 ><A
3057 HREF="#WRITERAW"
3058 ><TT
3059 CLASS="PARAMETER"
3060 ><I
3061 >write raw</I
3062 ></TT
3063 ></A
3064 ></P
3065 ></LI
3066 ></UL
3067 ></DIV
3068 ><DIV
3069 CLASS="REFSECT1"
3070 ><A
3071 NAME="AEN992"
3072 ></A
3073 ><H2
3074 >COMPLETE LIST OF SERVICE PARAMETERS</H2
3075 ><P
3076 >Here is a list of all service parameters. See the section on
3077         each parameter for details. Note that some are synonyms.</P
3078 ><P
3079 ></P
3080 ><UL
3081 ><LI
3082 ><P
3083 ><A
3084 HREF="#ADMINUSERS"
3085 ><TT
3086 CLASS="PARAMETER"
3087 ><I
3088 >admin users</I
3089 ></TT
3090 ></A
3091 ></P
3092 ></LI
3093 ><LI
3094 ><P
3095 ><A
3096 HREF="#ALLOWHOSTS"
3097 ><TT
3098 CLASS="PARAMETER"
3099 ><I
3100 >allow hosts</I
3101 ></TT
3102 ></A
3103 ></P
3104 ></LI
3105 ><LI
3106 ><P
3107 ><A
3108 HREF="#AVAILABLE"
3109 ><TT
3110 CLASS="PARAMETER"
3111 ><I
3112 >available</I
3113 ></TT
3114 ></A
3115 ></P
3116 ></LI
3117 ><LI
3118 ><P
3119 ><A
3120 HREF="#BLOCKINGLOCKS"
3121 ><TT
3122 CLASS="PARAMETER"
3123 ><I
3124 >blocking locks</I
3125 ></TT
3126 ></A
3127 ></P
3128 ></LI
3129 ><LI
3130 ><P
3131 ><A
3132 HREF="#BLOCKSIZE"
3133 ><TT
3134 CLASS="PARAMETER"
3135 ><I
3136 >block size</I
3137 ></TT
3138 ></A
3139 ></P
3140 ></LI
3141 ><LI
3142 ><P
3143 ><A
3144 HREF="#BROWSABLE"
3145 ><TT
3146 CLASS="PARAMETER"
3147 ><I
3148 >browsable</I
3149 ></TT
3150 ></A
3151 ></P
3152 ></LI
3153 ><LI
3154 ><P
3155 ><A
3156 HREF="#BROWSEABLE"
3157 ><TT
3158 CLASS="PARAMETER"
3159 ><I
3160 >browseable</I
3161 ></TT
3162 ></A
3163 ></P
3164 ></LI
3165 ><LI
3166 ><P
3167 ><A
3168 HREF="#CASESENSITIVE"
3169 ><TT
3170 CLASS="PARAMETER"
3171 ><I
3172 >case sensitive</I
3173 ></TT
3174 ></A
3175 ></P
3176 ></LI
3177 ><LI
3178 ><P
3179 ><A
3180 HREF="#CASESIGNAMES"
3181 ><TT
3182 CLASS="PARAMETER"
3183 ><I
3184 >casesignames</I
3185 ></TT
3186 ></A
3187 ></P
3188 ></LI
3189 ><LI
3190 ><P
3191 ><A
3192 HREF="#COMMENT"
3193 ><TT
3194 CLASS="PARAMETER"
3195 ><I
3196 >comment</I
3197 ></TT
3198 ></A
3199 ></P
3200 ></LI
3201 ><LI
3202 ><P
3203 ><A
3204 HREF="#COPY"
3205 ><TT
3206 CLASS="PARAMETER"
3207 ><I
3208 >copy</I
3209 ></TT
3210 ></A
3211 ></P
3212 ></LI
3213 ><LI
3214 ><P
3215 ><A
3216 HREF="#CREATEMASK"
3217 ><TT
3218 CLASS="PARAMETER"
3219 ><I
3220 >create mask</I
3221 ></TT
3222 ></A
3223 ></P
3224 ></LI
3225 ><LI
3226 ><P
3227 ><A
3228 HREF="#CREATEMODE"
3229 ><TT
3230 CLASS="PARAMETER"
3231 ><I
3232 >create mode</I
3233 ></TT
3234 ></A
3235 ></P
3236 ></LI
3237 ><LI
3238 ><P
3239 ><A
3240 HREF="#CSCPOLICY"
3241 ><TT
3242 CLASS="PARAMETER"
3243 ><I
3244 >csc policy</I
3245 ></TT
3246 ></A
3247 ></P
3248 ></LI
3249 ><LI
3250 ><P
3251 ><A
3252 HREF="#DEFAULTCASE"
3253 ><TT
3254 CLASS="PARAMETER"
3255 ><I
3256 >default case</I
3257 ></TT
3258 ></A
3259 ></P
3260 ></LI
3261 ><LI
3262 ><P
3263 ><A
3264 HREF="#DEFAULTDEVMODE"
3265 ><TT
3266 CLASS="PARAMETER"
3267 ><I
3268 >default devmode</I
3269 ></TT
3270 ></A
3271 ></P
3272 ></LI
3273 ><LI
3274 ><P
3275 ><A
3276 HREF="#DELETEREADONLY"
3277 ><TT
3278 CLASS="PARAMETER"
3279 ><I
3280 >delete readonly</I
3281 ></TT
3282 ></A
3283 ></P
3284 ></LI
3285 ><LI
3286 ><P
3287 ><A
3288 HREF="#DELETEVETOFILES"
3289 ><TT
3290 CLASS="PARAMETER"
3291 ><I
3292 >delete veto files</I
3293 ></TT
3294 ></A
3295 ></P
3296 ></LI
3297 ><LI
3298 ><P
3299 ><A
3300 HREF="#DENYHOSTS"
3301 ><TT
3302 CLASS="PARAMETER"
3303 ><I
3304 >deny hosts</I
3305 ></TT
3306 ></A
3307 ></P
3308 ></LI
3309 ><LI
3310 ><P
3311 ><A
3312 HREF="#DIRECTORY"
3313 ><TT
3314 CLASS="PARAMETER"
3315 ><I
3316 >directory</I
3317 ></TT
3318 ></A
3319 ></P
3320 ></LI
3321 ><LI
3322 ><P
3323 ><A
3324 HREF="#DIRECTORYMASK"
3325 ><TT
3326 CLASS="PARAMETER"
3327 ><I
3328 >directory mask</I
3329 ></TT
3330 ></A
3331 ></P
3332 ></LI
3333 ><LI
3334 ><P
3335 ><A
3336 HREF="#DIRECTORYMODE"
3337 ><TT
3338 CLASS="PARAMETER"
3339 ><I
3340 >directory mode</I
3341 ></TT
3342 ></A
3343 ></P
3344 ></LI
3345 ><LI
3346 ><P
3347 ><A
3348 HREF="#DIRECTORYSECURITYMASK"
3349 ><TT
3350 CLASS="PARAMETER"
3351 ><I
3352 >directory security mask</I
3353 ></TT
3354 ></A
3355 ></P
3356 ></LI
3357 ><LI
3358 ><P
3359 ><A
3360 HREF="#DONTDESCEND"
3361 ><TT
3362 CLASS="PARAMETER"
3363 ><I
3364 >dont descend</I
3365 ></TT
3366 ></A
3367 ></P
3368 ></LI
3369 ><LI
3370 ><P
3371 ><A
3372 HREF="#DOSFILEMODE"
3373 ><TT
3374 CLASS="PARAMETER"
3375 ><I
3376 >dos filemode</I
3377 ></TT
3378 ></A
3379 ></P
3380 ></LI
3381 ><LI
3382 ><P
3383 ><A
3384 HREF="#DOSFILETIMERESOLUTION"
3385 ><TT
3386 CLASS="PARAMETER"
3387 ><I
3388 >dos filetime resolution</I
3389 ></TT
3390 ></A
3391 ></P
3392 ></LI
3393 ><LI
3394 ><P
3395 ><A
3396 HREF="#DOSFILETIMES"
3397 ><TT
3398 CLASS="PARAMETER"
3399 ><I
3400 >dos filetimes</I
3401 ></TT
3402 ></A
3403 ></P
3404 ></LI
3405 ><LI
3406 ><P
3407 ><A
3408 HREF="#EXEC"
3409 ><TT
3410 CLASS="PARAMETER"
3411 ><I
3412 >exec</I
3413 ></TT
3414 ></A
3415 ></P
3416 ></LI
3417 ><LI
3418 ><P
3419 ><A
3420 HREF="#FAKEDIRECTORYCREATETIMES"
3421 ><TT
3422 CLASS="PARAMETER"
3423 ><I
3424 >fake directory create times</I
3425 ></TT
3426 ></A
3427 ></P
3428 ></LI
3429 ><LI
3430 ><P
3431 ><A
3432 HREF="#FAKEOPLOCKS"
3433 ><TT
3434 CLASS="PARAMETER"
3435 ><I
3436 >fake oplocks</I
3437 ></TT
3438 ></A
3439 ></P
3440 ></LI
3441 ><LI
3442 ><P
3443 ><A
3444 HREF="#FOLLOWSYMLINKS"
3445 ><TT
3446 CLASS="PARAMETER"
3447 ><I
3448 >follow symlinks</I
3449 ></TT
3450 ></A
3451 ></P
3452 ></LI
3453 ><LI
3454 ><P
3455 ><A
3456 HREF="#FORCECREATEMODE"
3457 ><TT
3458 CLASS="PARAMETER"
3459 ><I
3460 >force create mode</I
3461 ></TT
3462 ></A
3463 ></P
3464 ></LI
3465 ><LI
3466 ><P
3467 ><A
3468 HREF="#FORCEDIRECTORYMODE"
3469 ><TT
3470 CLASS="PARAMETER"
3471 ><I
3472 >force directory mode</I
3473 ></TT
3474 ></A
3475 ></P
3476 ></LI
3477 ><LI
3478 ><P
3479 ><A
3480 HREF="#FORCEDIRECTORYSECURITYMODE"
3481 ><TT
3482 CLASS="PARAMETER"
3483 ><I
3484 >force directory security mode</I
3485 ></TT
3486 ></A
3487 ></P
3488 ></LI
3489 ><LI
3490 ><P
3491 ><A
3492 HREF="#FORCEGROUP"
3493 ><TT
3494 CLASS="PARAMETER"
3495 ><I
3496 >force group</I
3497 ></TT
3498 ></A
3499 ></P
3500 ></LI
3501 ><LI
3502 ><P
3503 ><A
3504 HREF="#FORCESECURITYMODE"
3505 ><TT
3506 CLASS="PARAMETER"
3507 ><I
3508 >force security mode</I
3509 ></TT
3510 ></A
3511 ></P
3512 ></LI
3513 ><LI
3514 ><P
3515 ><A
3516 HREF="#FORCEUNKNOWNACLUSER"
3517 ><TT
3518 CLASS="PARAMETER"
3519 ><I
3520 >force unknown acl user</I
3521 ></TT
3522 ></A
3523 ></P
3524 ></LI
3525 ><LI
3526 ><P
3527 ><A
3528 HREF="#FORCEUSER"
3529 ><TT
3530 CLASS="PARAMETER"
3531 ><I
3532 >force user</I
3533 ></TT
3534 ></A
3535 ></P
3536 ></LI
3537 ><LI
3538 ><P
3539 ><A
3540 HREF="#FSTYPE"
3541 ><TT
3542 CLASS="PARAMETER"
3543 ><I
3544 >fstype</I
3545 ></TT
3546 ></A
3547 ></P
3548 ></LI
3549 ><LI
3550 ><P
3551 ><A
3552 HREF="#GROUP"
3553 ><TT
3554 CLASS="PARAMETER"
3555 ><I
3556 >group</I
3557 ></TT
3558 ></A
3559 ></P
3560 ></LI
3561 ><LI
3562 ><P
3563 ><A
3564 HREF="#GUESTACCOUNT"
3565 ><TT
3566 CLASS="PARAMETER"
3567 ><I
3568 >guest account</I
3569 ></TT
3570 ></A
3571 ></P
3572 ></LI
3573 ><LI
3574 ><P
3575 ><A
3576 HREF="#GUESTOK"
3577 ><TT
3578 CLASS="PARAMETER"
3579 ><I
3580 >guest ok</I
3581 ></TT
3582 ></A
3583 ></P
3584 ></LI
3585 ><LI
3586 ><P
3587 ><A
3588 HREF="#GUESTONLY"
3589 ><TT
3590 CLASS="PARAMETER"
3591 ><I
3592 >guest only</I
3593 ></TT
3594 ></A
3595 ></P
3596 ></LI
3597 ><LI
3598 ><P
3599 ><A
3600 HREF="#HIDEDOTFILES"
3601 ><TT
3602 CLASS="PARAMETER"
3603 ><I
3604 >hide dot files</I
3605 ></TT
3606 ></A
3607 ></P
3608 ></LI
3609 ><LI
3610 ><P
3611 ><A
3612 HREF="#HIDEFILES"
3613 ><TT
3614 CLASS="PARAMETER"
3615 ><I
3616 >hide files</I
3617 ></TT
3618 ></A
3619 ></P
3620 ></LI
3621 ><LI
3622 ><P
3623 ><A
3624 HREF="#HOSTSALLOW"
3625 ><TT
3626 CLASS="PARAMETER"
3627 ><I
3628 >hosts allow</I
3629 ></TT
3630 ></A
3631 ></P
3632 ></LI
3633 ><LI
3634 ><P
3635 ><A
3636 HREF="#HOSTSDENY"
3637 ><TT
3638 CLASS="PARAMETER"
3639 ><I
3640 >hosts deny</I
3641 ></TT
3642 ></A
3643 ></P
3644 ></LI
3645 ><LI
3646 ><P
3647 ><A
3648 HREF="#INCLUDE"
3649 ><TT
3650 CLASS="PARAMETER"
3651 ><I
3652 >include</I
3653 ></TT
3654 ></A
3655 ></P
3656 ></LI
3657 ><LI
3658 ><P
3659 ><A
3660 HREF="#INHERITACLS"
3661 ><TT
3662 CLASS="PARAMETER"
3663 ><I
3664 >inherit acls</I
3665 ></TT
3666 ></A
3667 ></P
3668 ></LI
3669 ><LI
3670 ><P
3671 ><A
3672 HREF="#INHERITPERMISSIONS"
3673 ><TT
3674 CLASS="PARAMETER"
3675 ><I
3676 >inherit permissions</I
3677 ></TT
3678 ></A
3679 ></P
3680 ></LI
3681 ><LI
3682 ><P
3683 ><A
3684 HREF="#INVALIDUSERS"
3685 ><TT
3686 CLASS="PARAMETER"
3687 ><I
3688 >invalid users</I
3689 ></TT
3690 ></A
3691 ></P
3692 ></LI
3693 ><LI
3694 ><P
3695 ><A
3696 HREF="#LEVEL2OPLOCKS"
3697 ><TT
3698 CLASS="PARAMETER"
3699 ><I
3700 >level2 oplocks</I
3701 ></TT
3702 ></A
3703 ></P
3704 ></LI
3705 ><LI
3706 ><P
3707 ><A
3708 HREF="#LOCKING"
3709 ><TT
3710 CLASS="PARAMETER"
3711 ><I
3712 >locking</I
3713 ></TT
3714 ></A
3715 ></P
3716 ></LI
3717 ><LI
3718 ><P
3719 ><A
3720 HREF="#LPPAUSECOMMAND"
3721 ><TT
3722 CLASS="PARAMETER"
3723 ><I
3724 >lppause command</I
3725 ></TT
3726 ></A
3727 ></P
3728 ></LI
3729 ><LI
3730 ><P
3731 ><A
3732 HREF="#LPQCOMMAND"
3733 ><TT
3734 CLASS="PARAMETER"
3735 ><I
3736 >lpq command</I
3737 ></TT
3738 ></A
3739 ></P
3740 ></LI
3741 ><LI
3742 ><P
3743 ><A
3744 HREF="#LPRESUMECOMMAND"
3745 ><TT
3746 CLASS="PARAMETER"
3747 ><I
3748 >lpresume command</I
3749 ></TT
3750 ></A
3751 ></P
3752 ></LI
3753 ><LI
3754 ><P
3755 ><A
3756 HREF="#LPRMCOMMAND"
3757 ><TT
3758 CLASS="PARAMETER"
3759 ><I
3760 >lprm command</I
3761 ></TT
3762 ></A
3763 ></P
3764 ></LI
3765 ><LI
3766 ><P
3767 ><A
3768 HREF="#MAGICOUTPUT"
3769 ><TT
3770 CLASS="PARAMETER"
3771 ><I
3772 >magic output</I
3773 ></TT
3774 ></A
3775 ></P
3776 ></LI
3777 ><LI
3778 ><P
3779 ><A
3780 HREF="#MAGICSCRIPT"
3781 ><TT
3782 CLASS="PARAMETER"
3783 ><I
3784 >magic script</I
3785 ></TT
3786 ></A
3787 ></P
3788 ></LI
3789 ><LI
3790 ><P
3791 ><A
3792 HREF="#MANGLECASE"
3793 ><TT
3794 CLASS="PARAMETER"
3795 ><I
3796 >mangle case</I
3797 ></TT
3798 ></A
3799 ></P
3800 ></LI
3801 ><LI
3802 ><P
3803 ><A
3804 HREF="#MANGLEDMAP"
3805 ><TT
3806 CLASS="PARAMETER"
3807 ><I
3808 >mangled map</I
3809 ></TT
3810 ></A
3811 ></P
3812 ></LI
3813 ><LI
3814 ><P
3815 ><A
3816 HREF="#MANGLEDNAMES"
3817 ><TT
3818 CLASS="PARAMETER"
3819 ><I
3820 >mangled names</I
3821 ></TT
3822 ></A
3823 ></P
3824 ></LI
3825 ><LI
3826 ><P
3827 ><A
3828 HREF="#MANGLINGCHAR"
3829 ><TT
3830 CLASS="PARAMETER"
3831 ><I
3832 >mangling char</I
3833 ></TT
3834 ></A
3835 ></P
3836 ></LI
3837 ><LI
3838 ><P
3839 ><A
3840 HREF="#MAPARCHIVE"
3841 ><TT
3842 CLASS="PARAMETER"
3843 ><I
3844 >map archive</I
3845 ></TT
3846 ></A
3847 ></P
3848 ></LI
3849 ><LI
3850 ><P
3851 ><A
3852 HREF="#MAPHIDDEN"
3853 ><TT
3854 CLASS="PARAMETER"
3855 ><I
3856 >map hidden</I
3857 ></TT
3858 ></A
3859 ></P
3860 ></LI
3861 ><LI
3862 ><P
3863 ><A
3864 HREF="#MAPSYSTEM"
3865 ><TT
3866 CLASS="PARAMETER"
3867 ><I
3868 >map system</I
3869 ></TT
3870 ></A
3871 ></P
3872 ></LI
3873 ><LI
3874 ><P
3875 ><A
3876 HREF="#MAXCONNECTIONS"
3877 ><TT
3878 CLASS="PARAMETER"
3879 ><I
3880 >max connections</I
3881 ></TT
3882 ></A
3883 ></P
3884 ></LI
3885 ><LI
3886 ><P
3887 ><A
3888 HREF="#MAXPRINTJOBS"
3889 ><TT
3890 CLASS="PARAMETER"
3891 ><I
3892 >max print jobs</I
3893 ></TT
3894 ></A
3895 ></P
3896 ></LI
3897 ><LI
3898 ><P
3899 ><A
3900 HREF="#MINPRINTSPACE"
3901 ><TT
3902 CLASS="PARAMETER"
3903 ><I
3904 >min print space</I
3905 ></TT
3906 ></A
3907 ></P
3908 ></LI
3909 ><LI
3910 ><P
3911 ><A
3912 HREF="#MSDFSROOT"
3913 ><TT
3914 CLASS="PARAMETER"
3915 ><I
3916 >msdfs root</I
3917 ></TT
3918 ></A
3919 ></P
3920 ></LI
3921 ><LI
3922 ><P
3923 ><A
3924 HREF="#NTACLSUPPORT"
3925 ><TT
3926 CLASS="PARAMETER"
3927 ><I
3928 >nt acl support</I
3929 ></TT
3930 ></A
3931 ></P
3932 ></LI
3933 ><LI
3934 ><P
3935 ><A
3936 HREF="#ONLYGUEST"
3937 ><TT
3938 CLASS="PARAMETER"
3939 ><I
3940 >only guest</I
3941 ></TT
3942 ></A
3943 ></P
3944 ></LI
3945 ><LI
3946 ><P
3947 ><A
3948 HREF="#ONLYUSER"
3949 ><TT
3950 CLASS="PARAMETER"
3951 ><I
3952 >only user</I
3953 ></TT
3954 ></A
3955 ></P
3956 ></LI
3957 ><LI
3958 ><P
3959 ><A
3960 HREF="#OPLOCKCONTENTIONLIMIT"
3961 ><TT
3962 CLASS="PARAMETER"
3963 ><I
3964 >oplock contention limit</I
3965 ></TT
3966 ></A
3967 ></P
3968 ></LI
3969 ><LI
3970 ><P
3971 ><A
3972 HREF="#OPLOCKS"
3973 ><TT
3974 CLASS="PARAMETER"
3975 ><I
3976 >oplocks</I
3977 ></TT
3978 ></A
3979 ></P
3980 ></LI
3981 ><LI
3982 ><P
3983 ><A
3984 HREF="#PATH"
3985 ><TT
3986 CLASS="PARAMETER"
3987 ><I
3988 >path</I
3989 ></TT
3990 ></A
3991 ></P
3992 ></LI
3993 ><LI
3994 ><P
3995 ><A
3996 HREF="#POSIXLOCKING"
3997 ><TT
3998 CLASS="PARAMETER"
3999 ><I
4000 >posix locking</I
4001 ></TT
4002 ></A
4003 ></P
4004 ></LI
4005 ><LI
4006 ><P
4007 ><A
4008 HREF="#POSTEXEC"
4009 ><TT
4010 CLASS="PARAMETER"
4011 ><I
4012 >postexec</I
4013 ></TT
4014 ></A
4015 ></P
4016 ></LI
4017 ><LI
4018 ><P
4019 ><A
4020 HREF="#POSTSCRIPT"
4021 ><TT
4022 CLASS="PARAMETER"
4023 ><I
4024 >postscript</I
4025 ></TT
4026 ></A
4027 ></P
4028 ></LI
4029 ><LI
4030 ><P
4031 ><A
4032 HREF="#PREEXEC"
4033 ><TT
4034 CLASS="PARAMETER"
4035 ><I
4036 >preexec</I
4037 ></TT
4038 ></A
4039 ></P
4040 ></LI
4041 ><LI
4042 ><P
4043 ><A
4044 HREF="#PREEXECCLOSE"
4045 ><TT
4046 CLASS="PARAMETER"
4047 ><I
4048 >preexec close</I
4049 ></TT
4050 ></A
4051 ></P
4052 ></LI
4053 ><LI
4054 ><P
4055 ><A
4056 HREF="#PRESERVECASE"
4057 ><TT
4058 CLASS="PARAMETER"
4059 ><I
4060 >preserve case</I
4061 ></TT
4062 ></A
4063 ></P
4064 ></LI
4065 ><LI
4066 ><P
4067 ><A
4068 HREF="#PRINTCOMMAND"
4069 ><TT
4070 CLASS="PARAMETER"
4071 ><I
4072 >print command</I
4073 ></TT
4074 ></A
4075 ></P
4076 ></LI
4077 ><LI
4078 ><P
4079 ><A
4080 HREF="#PRINTOK"
4081 ><TT
4082 CLASS="PARAMETER"
4083 ><I
4084 >print ok</I
4085 ></TT
4086 ></A
4087 ></P
4088 ></LI
4089 ><LI
4090 ><P
4091 ><A
4092 HREF="#PRINTABLE"
4093 ><TT
4094 CLASS="PARAMETER"
4095 ><I
4096 >printable</I
4097 ></TT
4098 ></A
4099 ></P
4100 ></LI
4101 ><LI
4102 ><P
4103 ><A
4104 HREF="#PRINTER"
4105 ><TT
4106 CLASS="PARAMETER"
4107 ><I
4108 >printer</I
4109 ></TT
4110 ></A
4111 ></P
4112 ></LI
4113 ><LI
4114 ><P
4115 ><A
4116 HREF="#PRINTERADMIN"
4117 ><TT
4118 CLASS="PARAMETER"
4119 ><I
4120 >printer admin</I
4121 ></TT
4122 ></A
4123 ></P
4124 ></LI
4125 ><LI
4126 ><P
4127 ><A
4128 HREF="#PRINTERDRIVER"
4129 ><TT
4130 CLASS="PARAMETER"
4131 ><I
4132 >printer driver</I
4133 ></TT
4134 ></A
4135 ></P
4136 ></LI
4137 ><LI
4138 ><P
4139 ><A
4140 HREF="#PRINTERDRIVERLOCATION"
4141 ><TT
4142 CLASS="PARAMETER"
4143 ><I
4144 >printer driver location</I
4145 ></TT
4146 ></A
4147 ></P
4148 ></LI
4149 ><LI
4150 ><P
4151 ><A
4152 HREF="#PRINTERNAME"
4153 ><TT
4154 CLASS="PARAMETER"
4155 ><I
4156 >printer name</I
4157 ></TT
4158 ></A
4159 ></P
4160 ></LI
4161 ><LI
4162 ><P
4163 ><A
4164 HREF="#PRINTING"
4165 ><TT
4166 CLASS="PARAMETER"
4167 ><I
4168 >printing</I
4169 ></TT
4170 ></A
4171 ></P
4172 ></LI
4173 ><LI
4174 ><P
4175 ><A
4176 HREF="#PROFILEACLS"
4177 ><TT
4178 CLASS="PARAMETER"
4179 ><I
4180 >profile acls</I
4181 ></TT
4182 ></A
4183 ></P
4184 ></LI
4185 ><LI
4186 ><P
4187 ><A
4188 HREF="#PUBLIC"
4189 ><TT
4190 CLASS="PARAMETER"
4191 ><I
4192 >public</I
4193 ></TT
4194 ></A
4195 ></P
4196 ></LI
4197 ><LI
4198 ><P
4199 ><A
4200 HREF="#QUEUEPAUSECOMMAND"
4201 ><TT
4202 CLASS="PARAMETER"
4203 ><I
4204 >queuepause command</I
4205 ></TT
4206 ></A
4207 ></P
4208 ></LI
4209 ><LI
4210 ><P
4211 ><A
4212 HREF="#QUEUERESUMECOMMAND"
4213 ><TT
4214 CLASS="PARAMETER"
4215 ><I
4216 >queueresume command</I
4217 ></TT
4218 ></A
4219 ></P
4220 ></LI
4221 ><LI
4222 ><P
4223 ><A
4224 HREF="#READLIST"
4225 ><TT
4226 CLASS="PARAMETER"
4227 ><I
4228 >read list</I
4229 ></TT
4230 ></A
4231 ></P
4232 ></LI
4233 ><LI
4234 ><P
4235 ><A
4236 HREF="#READONLY"
4237 ><TT
4238 CLASS="PARAMETER"
4239 ><I
4240 >read only</I
4241 ></TT
4242 ></A
4243 ></P
4244 ></LI
4245 ><LI
4246 ><P
4247 ><A
4248 HREF="#ROOTPOSTEXEC"
4249 ><TT
4250 CLASS="PARAMETER"
4251 ><I
4252 >root postexec</I
4253 ></TT
4254 ></A
4255 ></P
4256 ></LI
4257 ><LI
4258 ><P
4259 ><A
4260 HREF="#ROOTPREEXEC"
4261 ><TT
4262 CLASS="PARAMETER"
4263 ><I
4264 >root preexec</I
4265 ></TT
4266 ></A
4267 ></P
4268 ></LI
4269 ><LI
4270 ><P
4271 ><A
4272 HREF="#ROOTPREEXECCLOSE"
4273 ><TT
4274 CLASS="PARAMETER"
4275 ><I
4276 >root preexec close</I
4277 ></TT
4278 ></A
4279 ></P
4280 ></LI
4281 ><LI
4282 ><P
4283 ><A
4284 HREF="#SECURITYMASK"
4285 ><TT
4286 CLASS="PARAMETER"
4287 ><I
4288 >security mask</I
4289 ></TT
4290 ></A
4291 ></P
4292 ></LI
4293 ><LI
4294 ><P
4295 ><A
4296 HREF="#SETDIRECTORY"
4297 ><TT
4298 CLASS="PARAMETER"
4299 ><I
4300 >set directory</I
4301 ></TT
4302 ></A
4303 ></P
4304 ></LI
4305 ><LI
4306 ><P
4307 ><A
4308 HREF="#SHAREMODES"
4309 ><TT
4310 CLASS="PARAMETER"
4311 ><I
4312 >share modes</I
4313 ></TT
4314 ></A
4315 ></P
4316 ></LI
4317 ><LI
4318 ><P
4319 ><A
4320 HREF="#SHORTPRESERVECASE"
4321 ><TT
4322 CLASS="PARAMETER"
4323 ><I
4324 >short preserve case</I
4325 ></TT
4326 ></A
4327 ></P
4328 ></LI
4329 ><LI
4330 ><P
4331 ><A
4332 HREF="#STATUS"
4333 ><TT
4334 CLASS="PARAMETER"
4335 ><I
4336 >status</I
4337 ></TT
4338 ></A
4339 ></P
4340 ></LI
4341 ><LI
4342 ><P
4343 ><A
4344 HREF="#STRICTALLOCATE"
4345 ><TT
4346 CLASS="PARAMETER"
4347 ><I
4348 >strict allocate</I
4349 ></TT
4350 ></A
4351 ></P
4352 ></LI
4353 ><LI
4354 ><P
4355 ><A
4356 HREF="#STRICTLOCKING"
4357 ><TT
4358 CLASS="PARAMETER"
4359 ><I
4360 >strict locking</I
4361 ></TT
4362 ></A
4363 ></P
4364 ></LI
4365 ><LI
4366 ><P
4367 ><A
4368 HREF="#STRICTSYNC"
4369 ><TT
4370 CLASS="PARAMETER"
4371 ><I
4372 >strict sync</I
4373 ></TT
4374 ></A
4375 ></P
4376 ></LI
4377 ><LI
4378 ><P
4379 ><A
4380 HREF="#SYNCALWAYS"
4381 ><TT
4382 CLASS="PARAMETER"
4383 ><I
4384 >sync always</I
4385 ></TT
4386 ></A
4387 ></P
4388 ></LI
4389 ><LI
4390 ><P
4391 ><A
4392 HREF="#USECLIENTDRIVER"
4393 ><TT
4394 CLASS="PARAMETER"
4395 ><I
4396 >use client driver</I
4397 ></TT
4398 ></A
4399 ></P
4400 ></LI
4401 ><LI
4402 ><P
4403 ><A
4404 HREF="#USESENDFILE"
4405 ><TT
4406 CLASS="PARAMETER"
4407 ><I
4408 >use sendfile</I
4409 ></TT
4410 ></A
4411 ></P
4412 ></LI
4413 ><LI
4414 ><P
4415 ><A
4416 HREF="#USER"
4417 ><TT
4418 CLASS="PARAMETER"
4419 ><I
4420 >user</I
4421 ></TT
4422 ></A
4423 ></P
4424 ></LI
4425 ><LI
4426 ><P
4427 ><A
4428 HREF="#USERNAME"
4429 ><TT
4430 CLASS="PARAMETER"
4431 ><I
4432 >username</I
4433 ></TT
4434 ></A
4435 ></P
4436 ></LI
4437 ><LI
4438 ><P
4439 ><A
4440 HREF="#USERS"
4441 ><TT
4442 CLASS="PARAMETER"
4443 ><I
4444 >users</I
4445 ></TT
4446 ></A
4447 ></P
4448 ></LI
4449 ><LI
4450 ><P
4451 ><A
4452 HREF="#VALIDUSERS"
4453 ><TT
4454 CLASS="PARAMETER"
4455 ><I
4456 >valid users</I
4457 ></TT
4458 ></A
4459 ></P
4460 ></LI
4461 ><LI
4462 ><P
4463 ><A
4464 HREF="#VETOFILES"
4465 ><TT
4466 CLASS="PARAMETER"
4467 ><I
4468 >veto files</I
4469 ></TT
4470 ></A
4471 ></P
4472 ></LI
4473 ><LI
4474 ><P
4475 ><A
4476 HREF="#VETOOPLOCKFILES"
4477 ><TT
4478 CLASS="PARAMETER"
4479 ><I
4480 >veto oplock files</I
4481 ></TT
4482 ></A
4483 ></P
4484 ></LI
4485 ><LI
4486 ><P
4487 ><A
4488 HREF="#VFSOBJECT"
4489 ><TT
4490 CLASS="PARAMETER"
4491 ><I
4492 >vfs object</I
4493 ></TT
4494 ></A
4495 ></P
4496 ></LI
4497 ><LI
4498 ><P
4499 ><A
4500 HREF="#VFSOPTIONS"
4501 ><TT
4502 CLASS="PARAMETER"
4503 ><I
4504 >vfs options</I
4505 ></TT
4506 ></A
4507 ></P
4508 ></LI
4509 ><LI
4510 ><P
4511 ><A
4512 HREF="#VOLUME"
4513 ><TT
4514 CLASS="PARAMETER"
4515 ><I
4516 >volume</I
4517 ></TT
4518 ></A
4519 ></P
4520 ></LI
4521 ><LI
4522 ><P
4523 ><A
4524 HREF="#WIDELINKS"
4525 ><TT
4526 CLASS="PARAMETER"
4527 ><I
4528 >wide links</I
4529 ></TT
4530 ></A
4531 ></P
4532 ></LI
4533 ><LI
4534 ><P
4535 ><A
4536 HREF="#WRITABLE"
4537 ><TT
4538 CLASS="PARAMETER"
4539 ><I
4540 >writable</I
4541 ></TT
4542 ></A
4543 ></P
4544 ></LI
4545 ><LI
4546 ><P
4547 ><A
4548 HREF="#WRITECACHESIZE"
4549 ><TT
4550 CLASS="PARAMETER"
4551 ><I
4552 >write cache size</I
4553 ></TT
4554 ></A
4555 ></P
4556 ></LI
4557 ><LI
4558 ><P
4559 ><A
4560 HREF="#WRITELIST"
4561 ><TT
4562 CLASS="PARAMETER"
4563 ><I
4564 >write list</I
4565 ></TT
4566 ></A
4567 ></P
4568 ></LI
4569 ><LI
4570 ><P
4571 ><A
4572 HREF="#WRITEOK"
4573 ><TT
4574 CLASS="PARAMETER"
4575 ><I
4576 >write ok</I
4577 ></TT
4578 ></A
4579 ></P
4580 ></LI
4581 ><LI
4582 ><P
4583 ><A
4584 HREF="#WRITEABLE"
4585 ><TT
4586 CLASS="PARAMETER"
4587 ><I
4588 >writeable</I
4589 ></TT
4590 ></A
4591 ></P
4592 ></LI
4593 ></UL
4594 ></DIV
4595 ><DIV
4596 CLASS="REFSECT1"
4597 ><A
4598 NAME="AEN1500"
4599 ></A
4600 ><H2
4601 >EXPLANATION OF EACH PARAMETER</H2
4602 ><P
4603 ></P
4604 ><DIV
4605 CLASS="VARIABLELIST"
4606 ><DL
4607 ><DT
4608 ><A
4609 NAME="ADDPRINTERCOMMAND"
4610 ></A
4611 >add printer command (G)</DT
4612 ><DD
4613 ><P
4614 >With the introduction of MS-RPC based printing
4615                 support for Windows NT/2000 clients in Samba 2.2, The MS Add
4616                 Printer Wizard (APW) icon is now also available in the
4617                 "Printers..." folder displayed a share listing.  The APW
4618                 allows for printers to be add remotely to a Samba or Windows
4619                 NT/2000 print server.</P
4620 ><P
4621 >For a Samba host this means that the printer must be
4622                 physically added to the underlying printing system.  The <TT
4623 CLASS="PARAMETER"
4624 ><I
4625 >add
4626                 printer command</I
4627 ></TT
4628 > defines a script to be run which
4629                 will perform the necessary operations for adding the printer
4630                 to the print system and to add the appropriate service definition
4631                 to the  <TT
4632 CLASS="FILENAME"
4633 >smb.conf</TT
4634 > file in order that it can be
4635                 shared by <A
4636 HREF="smbd.8.html"
4637 TARGET="_top"
4638 ><B
4639 CLASS="COMMAND"
4640 >smbd(8)</B
4641 >
4642                 </A
4643 >.</P
4644 ><P
4645 >The <TT
4646 CLASS="PARAMETER"
4647 ><I
4648 >add printer command</I
4649 ></TT
4650 > is
4651                 automatically invoked with the following parameter (in
4652                 order:</P
4653 ><P
4654 ></P
4655 ><UL
4656 ><LI
4657 ><P
4658 ><TT
4659 CLASS="PARAMETER"
4660 ><I
4661 >printer name</I
4662 ></TT
4663 ></P
4664 ></LI
4665 ><LI
4666 ><P
4667 ><TT
4668 CLASS="PARAMETER"
4669 ><I
4670 >share name</I
4671 ></TT
4672 ></P
4673 ></LI
4674 ><LI
4675 ><P
4676 ><TT
4677 CLASS="PARAMETER"
4678 ><I
4679 >port name</I
4680 ></TT
4681 ></P
4682 ></LI
4683 ><LI
4684 ><P
4685 ><TT
4686 CLASS="PARAMETER"
4687 ><I
4688 >driver name</I
4689 ></TT
4690 ></P
4691 ></LI
4692 ><LI
4693 ><P
4694 ><TT
4695 CLASS="PARAMETER"
4696 ><I
4697 >location</I
4698 ></TT
4699 ></P
4700 ></LI
4701 ><LI
4702 ><P
4703 ><TT
4704 CLASS="PARAMETER"
4705 ><I
4706 >Windows 9x driver location</I
4707 ></TT
4708 >
4709                         </P
4710 ></LI
4711 ></UL
4712 ><P
4713 >All parameters are filled in from the PRINTER_INFO_2 structure sent
4714                 by the Windows NT/2000 client with one exception.  The "Windows 9x
4715                 driver location" parameter is included for backwards compatibility
4716                 only.  The remaining fields in the structure are generated from answers
4717                 to the APW questions.</P
4718 ><P
4719 >Once the <TT
4720 CLASS="PARAMETER"
4721 ><I
4722 >add printer command</I
4723 ></TT
4724 > has
4725                 been executed, <B
4726 CLASS="COMMAND"
4727 >smbd</B
4728 > will reparse the <TT
4729 CLASS="FILENAME"
4730 >               smb.conf</TT
4731 > to determine if the share defined by the APW
4732                 exists.  If the sharename is still invalid, then <B
4733 CLASS="COMMAND"
4734 >smbd
4735                 </B
4736 > will return an ACCESS_DENIED error to the client.</P
4737 ><P
4738 >See also <A
4739 HREF="#DELETEPRINTERCOMMAND"
4740 ><TT
4741 CLASS="PARAMETER"
4742 ><I
4743 >               delete printer command</I
4744 ></TT
4745 ></A
4746 >, <A
4747 HREF="#PRINTING"
4748 ><TT
4749 CLASS="PARAMETER"
4750 ><I
4751 >printing</I
4752 ></TT
4753 ></A
4754 >,
4755                 <A
4756 HREF="#SHOWADDPRINTERWIZARD"
4757 ><TT
4758 CLASS="PARAMETER"
4759 ><I
4760 >show add
4761                 printer wizard</I
4762 ></TT
4763 ></A
4764 ></P
4765 ><P
4766 >Default: <EM
4767 >none</EM
4768 ></P
4769 ><P
4770 >Example: <B
4771 CLASS="COMMAND"
4772 >addprinter command = /usr/bin/addprinter
4773                 </B
4774 ></P
4775 ></DD
4776 ><DT
4777 ><A
4778 NAME="ADDSHARECOMMAND"
4779 ></A
4780 >add share command (G)</DT
4781 ><DD
4782 ><P
4783 >Samba 2.2.0 introduced the ability to dynamically
4784                 add and delete shares via the Windows NT 4.0 Server Manager.  The
4785                 <TT
4786 CLASS="PARAMETER"
4787 ><I
4788 >add share command</I
4789 ></TT
4790 > is used to define an
4791                 external program or script which will add a new service definition
4792                 to <TT
4793 CLASS="FILENAME"
4794 >smb.conf</TT
4795 >.  In order to successfully
4796                 execute the <TT
4797 CLASS="PARAMETER"
4798 ><I
4799 >add share command</I
4800 ></TT
4801 >, <B
4802 CLASS="COMMAND"
4803 >smbd</B
4804 >
4805                 requires that the administrator be connected using a root account (i.e.
4806                 uid == 0).
4807                 </P
4808 ><P
4809 >               When executed, <B
4810 CLASS="COMMAND"
4811 >smbd</B
4812 > will automatically invoke the
4813                 <TT
4814 CLASS="PARAMETER"
4815 ><I
4816 >add share command</I
4817 ></TT
4818 > with four parameters.
4819                 </P
4820 ><P
4821 ></P
4822 ><UL
4823 ><LI
4824 ><P
4825 ><TT
4826 CLASS="PARAMETER"
4827 ><I
4828 >configFile</I
4829 ></TT
4830 > - the location
4831                         of the global <TT
4832 CLASS="FILENAME"
4833 >smb.conf</TT
4834 > file.
4835                         </P
4836 ></LI
4837 ><LI
4838 ><P
4839 ><TT
4840 CLASS="PARAMETER"
4841 ><I
4842 >shareName</I
4843 ></TT
4844 > - the name of the new
4845                         share.
4846                         </P
4847 ></LI
4848 ><LI
4849 ><P
4850 ><TT
4851 CLASS="PARAMETER"
4852 ><I
4853 >pathName</I
4854 ></TT
4855 > - path to an **existing**
4856                         directory on disk.
4857                         </P
4858 ></LI
4859 ><LI
4860 ><P
4861 ><TT
4862 CLASS="PARAMETER"
4863 ><I
4864 >comment</I
4865 ></TT
4866 > - comment string to associate
4867                         with the new share.
4868                         </P
4869 ></LI
4870 ></UL
4871 ><P
4872 >               This parameter is only used for add file shares.  To add printer shares,
4873                 see the <A
4874 HREF="#ADDPRINTERCOMMAND"
4875 ><TT
4876 CLASS="PARAMETER"
4877 ><I
4878 >add printer
4879                 command</I
4880 ></TT
4881 ></A
4882 >.
4883                 </P
4884 ><P
4885 >               See also <A
4886 HREF="#CHANGESHARECOMMAND"
4887 ><TT
4888 CLASS="PARAMETER"
4889 ><I
4890 >change share
4891                 command</I
4892 ></TT
4893 ></A
4894 >, <A
4895 HREF="#DELETESHARECOMMAND"
4896 ><TT
4897 CLASS="PARAMETER"
4898 ><I
4899 >delete share
4900                 command</I
4901 ></TT
4902 ></A
4903 >.
4904                 </P
4905 ><P
4906 >Default: <EM
4907 >none</EM
4908 ></P
4909 ><P
4910 >Example: <B
4911 CLASS="COMMAND"
4912 >add share command = /usr/local/bin/addshare</B
4913 ></P
4914 ></DD
4915 ><DT
4916 ><A
4917 NAME="ADDUSERSCRIPT"
4918 ></A
4919 >add user script (G)</DT
4920 ><DD
4921 ><P
4922 >This is the full pathname to a script that will
4923                 be run <EM
4924 >AS ROOT</EM
4925 > by <A
4926 HREF="smbd.8.html"
4927 TARGET="_top"
4928 >smbd(8)
4929                 </A
4930 > under special circumstances described below.</P
4931 ><P
4932 >Normally, a Samba server requires that UNIX users are
4933                 created for all users accessing files on this server. For sites
4934                 that use Windows NT account databases as their primary user database
4935                 creating these users and keeping the user list in sync with the
4936                 Windows NT PDC is an onerous task. This option allows <A
4937 HREF="smbd.8.html"
4938 TARGET="_top"
4939 >smbd</A
4940 > to create the required UNIX users
4941                 <EM
4942 >ON DEMAND</EM
4943 > when a user accesses the Samba server.</P
4944 ><P
4945 >In order to use this option, <A
4946 HREF="smbd.8.html"
4947 TARGET="_top"
4948 >smbd</A
4949 >
4950                 must <EM
4951 >NOT</EM
4952 > be set to <TT
4953 CLASS="PARAMETER"
4954 ><I
4955 >security = share</I
4956 ></TT
4957 >
4958                 and <TT
4959 CLASS="PARAMETER"
4960 ><I
4961 >add user script</I
4962 ></TT
4963 >
4964                 must be set to a full pathname for a script that will create a UNIX
4965                 user given one argument of <TT
4966 CLASS="PARAMETER"
4967 ><I
4968 >%u</I
4969 ></TT
4970 >, which expands into
4971                 the UNIX user name to create.</P
4972 ><P
4973 >When the Windows user attempts to access the Samba server,
4974                 at login (session setup in the SMB protocol) time, <A
4975 HREF="smbd.8.html"
4976 TARGET="_top"
4977 >               smbd</A
4978 > contacts the <TT
4979 CLASS="PARAMETER"
4980 ><I
4981 >password server</I
4982 ></TT
4983 > and
4984                 attempts to authenticate the given user with the given password. If the
4985                 authentication succeeds then <B
4986 CLASS="COMMAND"
4987 >smbd</B
4988 >
4989                 attempts to find a UNIX user in the UNIX password database to map the
4990                 Windows user into. If this lookup fails, and <TT
4991 CLASS="PARAMETER"
4992 ><I
4993 >add user script
4994                 </I
4995 ></TT
4996 > is set then <B
4997 CLASS="COMMAND"
4998 >smbd</B
4999 > will
5000                 call the specified script <EM
5001 >AS ROOT</EM
5002 >, expanding
5003                 any <TT
5004 CLASS="PARAMETER"
5005 ><I
5006 >%u</I
5007 ></TT
5008 > argument to be the user name to create.</P
5009 ><P
5010 >If this script successfully creates the user then <B
5011 CLASS="COMMAND"
5012 >smbd
5013                 </B
5014 > will continue on as though the UNIX user
5015                 already existed. In this way, UNIX users are dynamically created to
5016                 match existing Windows NT accounts.</P
5017 ><P
5018 >See also <A
5019 HREF="#SECURITY"
5020 ><TT
5021 CLASS="PARAMETER"
5022 ><I
5023 >               security</I
5024 ></TT
5025 ></A
5026 >, <A
5027 HREF="#PASSWORDSERVER"
5028 >               <TT
5029 CLASS="PARAMETER"
5030 ><I
5031 >password server</I
5032 ></TT
5033 ></A
5034 >,
5035                 <A
5036 HREF="#DELETEUSERSCRIPT"
5037 ><TT
5038 CLASS="PARAMETER"
5039 ><I
5040 >delete user
5041                 script</I
5042 ></TT
5043 ></A
5044 >.</P
5045 ><P
5046 >Default: <B
5047 CLASS="COMMAND"
5048 >add user script = &#60;empty string&#62;
5049                 </B
5050 ></P
5051 ><P
5052 >Example: <B
5053 CLASS="COMMAND"
5054 >add user script = /usr/local/samba/bin/add_user
5055                 %u</B
5056 ></P
5057 ></DD
5058 ><DT
5059 ><A
5060 NAME="ADMINUSERS"
5061 ></A
5062 >admin users (S)</DT
5063 ><DD
5064 ><P
5065 >This is a list of users who will be granted
5066                 administrative privileges on the share. This means that they
5067                 will do all file operations as the super-user (root).</P
5068 ><P
5069 >You should use this option very carefully, as any user in
5070                 this list will be able to do anything they like on the share,
5071                 irrespective of file permissions.</P
5072 ><P
5073 >Default: <EM
5074 >no admin users</EM
5075 ></P
5076 ><P
5077 >Example: <B
5078 CLASS="COMMAND"
5079 >admin users = jason</B
5080 ></P
5081 ></DD
5082 ><DT
5083 ><A
5084 NAME="ALLOWHOSTS"
5085 ></A
5086 >allow hosts (S)</DT
5087 ><DD
5088 ><P
5089 >Synonym for <A
5090 HREF="#HOSTSALLOW"
5091 >               <TT
5092 CLASS="PARAMETER"
5093 ><I
5094 >hosts allow</I
5095 ></TT
5096 ></A
5097 >.</P
5098 ></DD
5099 ><DT
5100 ><A
5101 NAME="ALLOWTRUSTEDDOMAINS"
5102 ></A
5103 >allow trusted domains (G)</DT
5104 ><DD
5105 ><P
5106 >This option only takes effect when the <A
5107 HREF="#SECURITY"
5108 ><TT
5109 CLASS="PARAMETER"
5110 ><I
5111 >security</I
5112 ></TT
5113 ></A
5114 > option is set to
5115                 <TT
5116 CLASS="CONSTANT"
5117 >server</TT
5118 > or <TT
5119 CLASS="CONSTANT"
5120 >domain</TT
5121 >.
5122                 If it is set to no, then attempts to connect to a resource from
5123                 a domain or workgroup other than the one which <A
5124 HREF="smbd.8.html"
5125 TARGET="_top"
5126 >smbd</A
5127 > is running
5128                 in will fail, even if that domain is trusted by the remote server
5129                 doing the authentication.</P
5130 ><P
5131 >This is useful if you only want your Samba server to
5132                 serve resources to users in the domain it is a member of. As
5133                 an example, suppose that there are two domains DOMA and DOMB.  DOMB
5134                 is trusted by DOMA, which contains the Samba server.  Under normal
5135                 circumstances, a user with an account in DOMB can then access the
5136                 resources of a UNIX account with the same account name on the
5137                 Samba server even if they do not have an account in DOMA.  This
5138                 can make implementing a security boundary difficult.</P
5139 ><P
5140 >Default: <B
5141 CLASS="COMMAND"
5142 >allow trusted domains = yes</B
5143 ></P
5144 ></DD
5145 ><DT
5146 ><A
5147 NAME="ANNOUNCEAS"
5148 ></A
5149 >announce as (G)</DT
5150 ><DD
5151 ><P
5152 >This specifies what type of server
5153                 <A
5154 HREF="nmbd.8.html"
5155 TARGET="_top"
5156 ><B
5157 CLASS="COMMAND"
5158 >nmbd</B
5159 ></A
5160 >
5161                 will announce itself as, to a network neighborhood browse
5162                 list. By default this is set to Windows NT. The valid options
5163                 are : "NT Server" (which can also be written as "NT"),
5164                 "NT Workstation", "Win95" or "WfW" meaning Windows NT Server,
5165                 Windows NT Workstation, Windows 95 and Windows for Workgroups
5166                 respectively. Do not change this parameter unless you have a
5167                 specific need to stop Samba appearing as an NT server as this
5168                 may prevent Samba servers from participating as browser servers
5169                 correctly.</P
5170 ><P
5171 >Default: <B
5172 CLASS="COMMAND"
5173 >announce as = NT Server</B
5174 ></P
5175 ><P
5176 >Example: <B
5177 CLASS="COMMAND"
5178 >announce as = Win95</B
5179 ></P
5180 ></DD
5181 ><DT
5182 ><A
5183 NAME="ANNOUNCEVERSION"
5184 ></A
5185 >announce version (G)</DT
5186 ><DD
5187 ><P
5188 >This specifies the major and minor version numbers
5189                 that nmbd will use when announcing itself as a server. The default
5190                 is 4.9.  Do not change this parameter unless you have a specific
5191                 need to set a Samba server to be a downlevel server.</P
5192 ><P
5193 >Default: <B
5194 CLASS="COMMAND"
5195 >announce version = 4.9</B
5196 ></P
5197 ><P
5198 >Example: <B
5199 CLASS="COMMAND"
5200 >announce version = 2.0</B
5201 ></P
5202 ></DD
5203 ><DT
5204 ><A
5205 NAME="AUTOSERVICES"
5206 ></A
5207 >auto services (G)</DT
5208 ><DD
5209 ><P
5210 >This is a synonym for the <A
5211 HREF="#PRELOAD"
5212 >               <TT
5213 CLASS="PARAMETER"
5214 ><I
5215 >preload</I
5216 ></TT
5217 ></A
5218 >.</P
5219 ></DD
5220 ><DT
5221 ><A
5222 NAME="AVAILABLE"
5223 ></A
5224 >available (S)</DT
5225 ><DD
5226 ><P
5227 >This parameter lets you "turn off" a service. If
5228                 <TT
5229 CLASS="PARAMETER"
5230 ><I
5231 >available = no</I
5232 ></TT
5233 >, then <EM
5234 >ALL</EM
5235 >
5236                 attempts to connect to the service will fail. Such failures are
5237                 logged.</P
5238 ><P
5239 >Default: <B
5240 CLASS="COMMAND"
5241 >available = yes</B
5242 ></P
5243 ></DD
5244 ><DT
5245 ><A
5246 NAME="BINDINTERFACESONLY"
5247 ></A
5248 >bind interfaces only (G)</DT
5249 ><DD
5250 ><P
5251 >This global parameter allows the Samba admin
5252                 to limit what interfaces on a machine will serve SMB requests. If
5253                 affects file service <A
5254 HREF="smbd.8.html"
5255 TARGET="_top"
5256 >smbd(8)</A
5257 > and
5258                 name service <A
5259 HREF="nmbd.8.html"
5260 TARGET="_top"
5261 >nmbd(8)</A
5262 > in slightly
5263                 different ways.</P
5264 ><P
5265 >For name service it causes <B
5266 CLASS="COMMAND"
5267 >nmbd</B
5268 > to bind
5269                 to ports 137 and 138 on the interfaces listed in the <A
5270 HREF="#INTERFACES"
5271 >interfaces</A
5272 > parameter. <B
5273 CLASS="COMMAND"
5274 >nmbd
5275                 </B
5276 > also binds to the "all addresses" interface (0.0.0.0)
5277                 on ports 137 and 138 for the purposes of reading broadcast messages.
5278                 If this option is not set then <B
5279 CLASS="COMMAND"
5280 >nmbd</B
5281 > will service
5282                 name requests on all of these sockets. If <TT
5283 CLASS="PARAMETER"
5284 ><I
5285 >bind interfaces
5286                 only</I
5287 ></TT
5288 > is set then <B
5289 CLASS="COMMAND"
5290 >nmbd</B
5291 > will check the
5292                 source address of any packets coming in on the broadcast sockets
5293                 and discard any that don't match the broadcast addresses of the
5294                 interfaces in the <TT
5295 CLASS="PARAMETER"
5296 ><I
5297 >interfaces</I
5298 ></TT
5299 > parameter list.
5300                 As unicast packets are received on the other sockets it allows
5301                 <B
5302 CLASS="COMMAND"
5303 >nmbd</B
5304 > to refuse to serve names to machines that
5305                 send packets that arrive through any interfaces not listed in the
5306                 <TT
5307 CLASS="PARAMETER"
5308 ><I
5309 >interfaces</I
5310 ></TT
5311 > list.  IP Source address spoofing
5312                 does defeat this simple check, however so it must not be used
5313                 seriously as a security feature for <B
5314 CLASS="COMMAND"
5315 >nmbd</B
5316 >.</P
5317 ><P
5318 >For file service it causes <A
5319 HREF="smbd.8.html"
5320 TARGET="_top"
5321 >smbd(8)</A
5322 >
5323                 to bind only to the interface list given in the <A
5324 HREF="#INTERFACES"
5325 >               interfaces</A
5326 > parameter. This restricts the networks that
5327                 <B
5328 CLASS="COMMAND"
5329 >smbd</B
5330 > will serve to packets coming in those
5331                 interfaces.  Note that you should not use this parameter for machines
5332                 that are serving PPP or other intermittent or non-broadcast network
5333                 interfaces as it will not cope with non-permanent interfaces.</P
5334 ><P
5335 >If <TT
5336 CLASS="PARAMETER"
5337 ><I
5338 >bind interfaces only</I
5339 ></TT
5340 > is set then
5341                 unless the network address <EM
5342 >127.0.0.1</EM
5343 > is added
5344                 to the <TT
5345 CLASS="PARAMETER"
5346 ><I
5347 >interfaces</I
5348 ></TT
5349 > parameter list <A
5350 HREF="smbpasswd.8.html"
5351 TARGET="_top"
5352 ><B
5353 CLASS="COMMAND"
5354 >smbpasswd(8)</B
5355 ></A
5356 >
5357                 and <A
5358 HREF="swat.8.html"
5359 TARGET="_top"
5360 ><B
5361 CLASS="COMMAND"
5362 >swat(8)</B
5363 ></A
5364 > may
5365                 not work as expected due to the reasons covered below.</P
5366 ><P
5367 >To change a users SMB password, the <B
5368 CLASS="COMMAND"
5369 >smbpasswd</B
5370 >
5371                 by default connects to the <EM
5372 >localhost - 127.0.0.1</EM
5373 >
5374                 address as an SMB client to issue the password change request. If
5375                 <TT
5376 CLASS="PARAMETER"
5377 ><I
5378 >bind interfaces only</I
5379 ></TT
5380 > is set then unless the
5381                 network address <EM
5382 >127.0.0.1</EM
5383 > is added to the
5384                 <TT
5385 CLASS="PARAMETER"
5386 ><I
5387 >interfaces</I
5388 ></TT
5389 > parameter list then <B
5390 CLASS="COMMAND"
5391 >               smbpasswd</B
5392 > will fail to connect in it's default mode.
5393                 <B
5394 CLASS="COMMAND"
5395 >smbpasswd</B
5396 > can be forced to use the primary IP interface
5397                 of the local host by using its <A
5398 HREF="smbpasswd.8.html#minusr"
5399 TARGET="_top"
5400 >               <TT
5401 CLASS="PARAMETER"
5402 ><I
5403 >-r <TT
5404 CLASS="REPLACEABLE"
5405 ><I
5406 >remote machine</I
5407 ></TT
5408 ></I
5409 ></TT
5410 >
5411                 </A
5412 > parameter, with <TT
5413 CLASS="REPLACEABLE"
5414 ><I
5415 >remote machine</I
5416 ></TT
5417 > set
5418                 to the IP name of the primary interface of the local host.</P
5419 ><P
5420 >The <B
5421 CLASS="COMMAND"
5422 >swat</B
5423 > status page tries to connect with
5424                 <B
5425 CLASS="COMMAND"
5426 >smbd</B
5427 > and <B
5428 CLASS="COMMAND"
5429 >nmbd</B
5430 > at the address
5431                 <EM
5432 >127.0.0.1</EM
5433 > to determine if they are running.
5434                 Not adding <EM
5435 >127.0.0.1</EM
5436 >  will cause <B
5437 CLASS="COMMAND"
5438 >               smbd</B
5439 > and <B
5440 CLASS="COMMAND"
5441 >nmbd</B
5442 > to always show
5443                 "not running" even if they really are.  This can prevent <B
5444 CLASS="COMMAND"
5445 >               swat</B
5446 > from starting/stopping/restarting <B
5447 CLASS="COMMAND"
5448 >smbd</B
5449 >
5450                 and <B
5451 CLASS="COMMAND"
5452 >nmbd</B
5453 >.</P
5454 ><P
5455 >Default: <B
5456 CLASS="COMMAND"
5457 >bind interfaces only = no</B
5458 ></P
5459 ></DD
5460 ><DT
5461 ><A
5462 NAME="BLOCKSIZE"
5463 ></A
5464 >block size (S)</DT
5465 ><DD
5466 ><P
5467 >This parameter controls the behavior of <A
5468 HREF="smbd.8.html"
5469 TARGET="_top"
5470 >smbd(8)</A
5471 > when reporting disk free sizes.
5472                 By default, this reports a disk block size of 1024 bytes.</P
5473 ><P
5474 >Changing this parameter may have some effect on the
5475                 efficiency of client writes, this is not yet confirmed. This
5476                 parameter was added to allow advanced administrators to change
5477                 it (usually to a higher value) and test the effect it has on
5478                 client write performance without re-compiling the code. As this
5479                 is an experimental option it may be removed in a future release.
5480                 </P
5481 ><P
5482 >Changing this option does not change the disk free reporting
5483                 size, just the block size unit reported to the client.</P
5484 ><P
5485 >Default: <B
5486 CLASS="COMMAND"
5487 >block size = 1024</B
5488 ></P
5489 ><P
5490 >Example: <B
5491 CLASS="COMMAND"
5492 >block size = 65536</B
5493 ></P
5494 ></DD
5495 ><DT
5496 ><A
5497 NAME="BLOCKINGLOCKS"
5498 ></A
5499 >blocking locks (S)</DT
5500 ><DD
5501 ><P
5502 >This parameter controls the behavior of <A
5503 HREF="smbd.8.html"
5504 TARGET="_top"
5505 >smbd(8)</A
5506 > when given a request by a client
5507                 to obtain a byte range lock on a region of an open file, and the
5508                 request has a time limit associated with it.</P
5509 ><P
5510 >If this parameter is set and the lock range requested
5511                 cannot be immediately satisfied, Samba 2.2 will internally
5512                 queue the lock request, and periodically attempt to obtain
5513                 the lock until the timeout period expires.</P
5514 ><P
5515 >If this parameter is set to <TT
5516 CLASS="CONSTANT"
5517 >no</TT
5518 >, then
5519                 Samba 2.2 will behave as previous versions of Samba would and
5520                 will fail the lock request immediately if the lock range
5521                 cannot be obtained.</P
5522 ><P
5523 >Default: <B
5524 CLASS="COMMAND"
5525 >blocking locks = yes</B
5526 ></P
5527 ></DD
5528 ><DT
5529 ><A
5530 NAME="BROWSABLE"
5531 ></A
5532 >browsable (S)</DT
5533 ><DD
5534 ><P
5535 >See the <A
5536 HREF="#BROWSEABLE"
5537 ><TT
5538 CLASS="PARAMETER"
5539 ><I
5540 >               browseable</I
5541 ></TT
5542 ></A
5543 >.</P
5544 ></DD
5545 ><DT
5546 ><A
5547 NAME="BROWSELIST"
5548 ></A
5549 >browse list (G)</DT
5550 ><DD
5551 ><P
5552 >This controls whether <A
5553 HREF="smbd.8.html"
5554 TARGET="_top"
5555 >               <B
5556 CLASS="COMMAND"
5557 >smbd(8)</B
5558 ></A
5559 > will serve a browse list to
5560                 a client doing a <B
5561 CLASS="COMMAND"
5562 >NetServerEnum</B
5563 > call. Normally
5564                 set to <TT
5565 CLASS="CONSTANT"
5566 >yes</TT
5567 >. You should never need to change
5568                 this.</P
5569 ><P
5570 >Default: <B
5571 CLASS="COMMAND"
5572 >browse list = yes</B
5573 ></P
5574 ></DD
5575 ><DT
5576 ><A
5577 NAME="BROWSEABLE"
5578 ></A
5579 >browseable (S)</DT
5580 ><DD
5581 ><P
5582 >This controls whether this share is seen in
5583                 the list of available shares in a net view and in the browse list.</P
5584 ><P
5585 >Default: <B
5586 CLASS="COMMAND"
5587 >browseable = yes</B
5588 ></P
5589 ></DD
5590 ><DT
5591 ><A
5592 NAME="CASESENSITIVE"
5593 ></A
5594 >case sensitive (S)</DT
5595 ><DD
5596 ><P
5597 >See the discussion in the section <A
5598 HREF="#AEN203"
5599 >NAME MANGLING</A
5600 >.</P
5601 ><P
5602 >Default: <B
5603 CLASS="COMMAND"
5604 >case sensitive = no</B
5605 ></P
5606 ></DD
5607 ><DT
5608 ><A
5609 NAME="CASESIGNAMES"
5610 ></A
5611 >casesignames (S)</DT
5612 ><DD
5613 ><P
5614 >Synonym for <A
5615 HREF="#CASESENSITIVE"
5616 >case
5617                 sensitive</A
5618 >.</P
5619 ></DD
5620 ><DT
5621 ><A
5622 NAME="CHANGENOTIFYTIMEOUT"
5623 ></A
5624 >change notify timeout (G)</DT
5625 ><DD
5626 ><P
5627 >This SMB allows a client to tell a server to
5628                 "watch" a particular directory for any changes and only reply to
5629                 the SMB request when a change has occurred. Such constant scanning of
5630                 a directory is expensive under UNIX, hence an <A
5631 HREF="smbd.8.html"
5632 TARGET="_top"
5633 >               <B
5634 CLASS="COMMAND"
5635 >smbd(8)</B
5636 ></A
5637 > daemon only performs such a scan
5638                 on each requested directory once every <TT
5639 CLASS="PARAMETER"
5640 ><I
5641 >change notify
5642                 timeout</I
5643 ></TT
5644 > seconds.</P
5645 ><P
5646 >Default: <B
5647 CLASS="COMMAND"
5648 >change notify timeout = 60</B
5649 ></P
5650 ><P
5651 >Example: <B
5652 CLASS="COMMAND"
5653 >change notify timeout = 300</B
5654 ></P
5655 ><P
5656 >Would change the scan time to every 5 minutes.</P
5657 ></DD
5658 ><DT
5659 ><A
5660 NAME="CHANGESHARECOMMAND"
5661 ></A
5662 >change share command (G)</DT
5663 ><DD
5664 ><P
5665 >Samba 2.2.0 introduced the ability to dynamically
5666                 add and delete shares via the Windows NT 4.0 Server Manager.  The
5667                 <TT
5668 CLASS="PARAMETER"
5669 ><I
5670 >change share command</I
5671 ></TT
5672 > is used to define an
5673                 external program or script which will modify an existing service definition
5674                 in <TT
5675 CLASS="FILENAME"
5676 >smb.conf</TT
5677 >.  In order to successfully
5678                 execute the <TT
5679 CLASS="PARAMETER"
5680 ><I
5681 >change share command</I
5682 ></TT
5683 >, <B
5684 CLASS="COMMAND"
5685 >smbd</B
5686 >
5687                 requires that the administrator be connected using a root account (i.e.
5688                 uid == 0).
5689                 </P
5690 ><P
5691 >               When executed, <B
5692 CLASS="COMMAND"
5693 >smbd</B
5694 > will automatically invoke the
5695                 <TT
5696 CLASS="PARAMETER"
5697 ><I
5698 >change share command</I
5699 ></TT
5700 > with four parameters.
5701                 </P
5702 ><P
5703 ></P
5704 ><UL
5705 ><LI
5706 ><P
5707 ><TT
5708 CLASS="PARAMETER"
5709 ><I
5710 >configFile</I
5711 ></TT
5712 > - the location
5713                         of the global <TT
5714 CLASS="FILENAME"
5715 >smb.conf</TT
5716 > file.
5717                         </P
5718 ></LI
5719 ><LI
5720 ><P
5721 ><TT
5722 CLASS="PARAMETER"
5723 ><I
5724 >shareName</I
5725 ></TT
5726 > - the name of the new
5727                         share.
5728                         </P
5729 ></LI
5730 ><LI
5731 ><P
5732 ><TT
5733 CLASS="PARAMETER"
5734 ><I
5735 >pathName</I
5736 ></TT
5737 > - path to an **existing**
5738                         directory on disk.
5739                         </P
5740 ></LI
5741 ><LI
5742 ><P
5743 ><TT
5744 CLASS="PARAMETER"
5745 ><I
5746 >comment</I
5747 ></TT
5748 > - comment string to associate
5749                         with the new share.
5750                         </P
5751 ></LI
5752 ></UL
5753 ><P
5754 >               This parameter is only used modify existing file shares definitions.  To modify
5755                 printer shares, use the "Printers..." folder as seen when browsing the Samba host.
5756                 </P
5757 ><P
5758 >               See also <A
5759 HREF="#ADDSHARECOMMAND"
5760 ><TT
5761 CLASS="PARAMETER"
5762 ><I
5763 >add share
5764                 command</I
5765 ></TT
5766 ></A
5767 >, <A
5768 HREF="#DELETESHARECOMMAND"
5769 ><TT
5770 CLASS="PARAMETER"
5771 ><I
5772 >delete
5773                 share command</I
5774 ></TT
5775 ></A
5776 >.
5777                 </P
5778 ><P
5779 >Default: <EM
5780 >none</EM
5781 ></P
5782 ><P
5783 >Example: <B
5784 CLASS="COMMAND"
5785 >change share command = /usr/local/bin/addshare</B
5786 ></P
5787 ></DD
5788 ><DT
5789 ><A
5790 NAME="CHARACTERSET"
5791 ></A
5792 >character set (G)</DT
5793 ><DD
5794 ><P
5795 >This allows <A
5796 HREF="smbd.8.html"
5797 TARGET="_top"
5798 >smbd</A
5799 > to map incoming filenames
5800                 from a DOS Code page (see the <A
5801 HREF="#CLIENTCODEPAGE"
5802 >client
5803                 code page</A
5804 > parameter) to several built in UNIX character sets.
5805                 The built in code page translations are:</P
5806 ><P
5807 ></P
5808 ><UL
5809 ><LI
5810 ><P
5811 ><TT
5812 CLASS="CONSTANT"
5813 >ISO8859-1</TT
5814 > : Western European
5815                         UNIX character set. The parameter <TT
5816 CLASS="PARAMETER"
5817 ><I
5818 >client code page</I
5819 ></TT
5820 >
5821                         <EM
5822 >MUST</EM
5823 > be set to code page 850 if the
5824                         <TT
5825 CLASS="PARAMETER"
5826 ><I
5827 >character set</I
5828 ></TT
5829 > parameter is set to
5830                         <TT
5831 CLASS="CONSTANT"
5832 >ISO8859-1</TT
5833 > in order for the conversion to the
5834                         UNIX character set to be done correctly.</P
5835 ></LI
5836 ><LI
5837 ><P
5838 ><TT
5839 CLASS="CONSTANT"
5840 >ISO8859-2</TT
5841 > : Eastern European
5842                         UNIX character set. The parameter <TT
5843 CLASS="PARAMETER"
5844 ><I
5845 >client code page
5846                         </I
5847 ></TT
5848 > <EM
5849 >MUST</EM
5850 > be set to code page 852 if
5851                         the <TT
5852 CLASS="PARAMETER"
5853 ><I
5854 > character set</I
5855 ></TT
5856 > parameter is set
5857                         to <TT
5858 CLASS="CONSTANT"
5859 >ISO8859-2</TT
5860 > in order for the conversion
5861                         to the UNIX character set to be done correctly. </P
5862 ></LI
5863 ><LI
5864 ><P
5865 ><TT
5866 CLASS="CONSTANT"
5867 >ISO8859-5</TT
5868 > : Russian Cyrillic
5869                         UNIX character set. The parameter <TT
5870 CLASS="PARAMETER"
5871 ><I
5872 >client code page
5873                         </I
5874 ></TT
5875 > <EM
5876 >MUST</EM
5877 > be set to code page
5878                         866 if the <TT
5879 CLASS="PARAMETER"
5880 ><I
5881 >character set </I
5882 ></TT
5883 > parameter is
5884                         set to <TT
5885 CLASS="CONSTANT"
5886 >ISO8859-5</TT
5887 > in order for the conversion
5888                         to the UNIX character set to be done correctly. </P
5889 ></LI
5890 ><LI
5891 ><P
5892 ><TT
5893 CLASS="CONSTANT"
5894 >ISO8859-7</TT
5895 > : Greek UNIX
5896                         character set. The parameter <TT
5897 CLASS="PARAMETER"
5898 ><I
5899 >client code page
5900                         </I
5901 ></TT
5902 > <EM
5903 >MUST</EM
5904 > be set to code page
5905                         737 if the <TT
5906 CLASS="PARAMETER"
5907 ><I
5908 >character set</I
5909 ></TT
5910 > parameter is
5911                         set to <TT
5912 CLASS="CONSTANT"
5913 >ISO8859-7</TT
5914 > in order for the conversion
5915                         to the UNIX character set to be done correctly.</P
5916 ></LI
5917 ><LI
5918 ><P
5919 ><TT
5920 CLASS="CONSTANT"
5921 >KOI8-R</TT
5922 > : Alternate mapping
5923                         for Russian Cyrillic UNIX character set. The parameter
5924                         <TT
5925 CLASS="PARAMETER"
5926 ><I
5927 >client code page</I
5928 ></TT
5929 > <EM
5930 >MUST</EM
5931 >
5932                         be set to code page 866 if the <TT
5933 CLASS="PARAMETER"
5934 ><I
5935 >character set</I
5936 ></TT
5937 >
5938                         parameter is set to <TT
5939 CLASS="CONSTANT"
5940 >KOI8-R</TT
5941 > in order for the
5942                         conversion to the UNIX character set to be done correctly.</P
5943 ></LI
5944 ></UL
5945 ><P
5946 ><EM
5947 >BUG</EM
5948 >. These MSDOS code page to UNIX character
5949                 set mappings should be dynamic, like the loading of MS DOS code pages,
5950                 not static.</P
5951 ><P
5952 >Normally this parameter is not set, meaning no filename
5953                 translation is done.</P
5954 ><P
5955 >Default: <B
5956 CLASS="COMMAND"
5957 >character set = &#60;empty string&#62;</B
5958 ></P
5959 ><P
5960 >Example: <B
5961 CLASS="COMMAND"
5962 >character set = ISO8859-1</B
5963 ></P
5964 ></DD
5965 ><DT
5966 ><A
5967 NAME="CLIENTCODEPAGE"
5968 ></A
5969 >client code page (G)</DT
5970 ><DD
5971 ><P
5972 >This parameter specifies the DOS code page
5973                 that the clients accessing Samba are using. To determine what code
5974                 page a Windows or DOS client is using, open a DOS command prompt
5975                 and type the command <B
5976 CLASS="COMMAND"
5977 >chcp</B
5978 >. This will output
5979                 the code page. The default for USA MS-DOS, Windows 95, and
5980                 Windows NT releases is code page 437. The default for western
5981                 European releases of the above operating systems is code page 850.</P
5982 ><P
5983 >This parameter tells <A
5984 HREF="smbd.8.html"
5985 TARGET="_top"
5986 >smbd(8)</A
5987 >
5988                 which of the <TT
5989 CLASS="FILENAME"
5990 >codepage.<TT
5991 CLASS="REPLACEABLE"
5992 ><I
5993 >XXX</I
5994 ></TT
5995 >
5996                 </TT
5997 > files to dynamically load on startup. These files,
5998                 described more fully in the manual page <A
5999 HREF="make_smbcodepage.1.html"
6000 TARGET="_top"
6001 >               <B
6002 CLASS="COMMAND"
6003 >make_smbcodepage(1)</B
6004 ></A
6005 >, tell <B
6006 CLASS="COMMAND"
6007 >               smbd</B
6008 > how to map lower to upper case characters to provide
6009                 the case insensitivity of filenames that Windows clients expect.</P
6010 ><P
6011 >Samba currently ships with the following code page files :</P
6012 ><P
6013 ></P
6014 ><UL
6015 ><LI
6016 ><P
6017 >Code Page 437 - MS-DOS Latin US</P
6018 ></LI
6019 ><LI
6020 ><P
6021 >Code Page 737 - Windows '95 Greek</P
6022 ></LI
6023 ><LI
6024 ><P
6025 >Code Page 850 - MS-DOS Latin 1</P
6026 ></LI
6027 ><LI
6028 ><P
6029 >Code Page 852 - MS-DOS Latin 2</P
6030 ></LI
6031 ><LI
6032 ><P
6033 >Code Page 861 - MS-DOS Icelandic</P
6034 ></LI
6035 ><LI
6036 ><P
6037 >Code Page 866 - MS-DOS Cyrillic</P
6038 ></LI
6039 ><LI
6040 ><P
6041 >Code Page 932 - MS-DOS Japanese SJIS</P
6042 ></LI
6043 ><LI
6044 ><P
6045 >Code Page 936 - MS-DOS Simplified Chinese</P
6046 ></LI
6047 ><LI
6048 ><P
6049 >Code Page 949 - MS-DOS Korean Hangul</P
6050 ></LI
6051 ><LI
6052 ><P
6053 >Code Page 950 - MS-DOS Traditional Chinese</P
6054 ></LI
6055 ></UL
6056 ><P
6057 >Thus this parameter may have any of the values 437, 737, 850, 852,
6058                 861, 932, 936, 949, or 950.  If you don't find the codepage you need,
6059                 read the comments in one of the other codepage files and the
6060                 <B
6061 CLASS="COMMAND"
6062 >make_smbcodepage(1)</B
6063 > man page and write one. Please
6064                 remember to donate it back to the Samba user community.</P
6065 ><P
6066 >This parameter co-operates with the <TT
6067 CLASS="PARAMETER"
6068 ><I
6069 >valid
6070                 chars</I
6071 ></TT
6072 > parameter in determining what characters are
6073                 valid in filenames and how capitalization is done. If you set both
6074                 this parameter and the <TT
6075 CLASS="PARAMETER"
6076 ><I
6077 >valid chars</I
6078 ></TT
6079 > parameter
6080                 the <TT
6081 CLASS="PARAMETER"
6082 ><I
6083 >client code page</I
6084 ></TT
6085 > parameter
6086                 <EM
6087 >MUST</EM
6088 > be set before the <TT
6089 CLASS="PARAMETER"
6090 ><I
6091 >valid
6092                 chars</I
6093 ></TT
6094 > parameter in the <TT
6095 CLASS="FILENAME"
6096 >smb.conf</TT
6097 >
6098                 file. The <TT
6099 CLASS="PARAMETER"
6100 ><I
6101 >valid chars</I
6102 ></TT
6103 > string will then
6104                 augment the character settings in the <TT
6105 CLASS="PARAMETER"
6106 ><I
6107 >client code page</I
6108 ></TT
6109 >
6110                 parameter.</P
6111 ><P
6112 >If not set, <TT
6113 CLASS="PARAMETER"
6114 ><I
6115 >client code page</I
6116 ></TT
6117 > defaults
6118                 to 850.</P
6119 ><P
6120 >See also : <A
6121 HREF="#VALIDCHARS"
6122 ><TT
6123 CLASS="PARAMETER"
6124 ><I
6125 >valid
6126                 chars</I
6127 ></TT
6128 ></A
6129 >, <A
6130 HREF="#CODEPAGEDIRECTORY"
6131 >               <TT
6132 CLASS="PARAMETER"
6133 ><I
6134 >code page directory</I
6135 ></TT
6136 ></A
6137 ></P
6138 ><P
6139 >Default: <B
6140 CLASS="COMMAND"
6141 >client code page = 850</B
6142 ></P
6143 ><P
6144 >Example: <B
6145 CLASS="COMMAND"
6146 >client code page = 936</B
6147 ></P
6148 ></DD
6149 ><DT
6150 ><A
6151 NAME="CODEPAGEDIRECTORY"
6152 ></A
6153 >code page directory (G)</DT
6154 ><DD
6155 ><P
6156 >Define the location of the various client code page
6157                 files.</P
6158 ><P
6159 >See also <A
6160 HREF="#CLIENTCODEPAGE"
6161 ><TT
6162 CLASS="PARAMETER"
6163 ><I
6164 >client
6165                 code page</I
6166 ></TT
6167 ></A
6168 ></P
6169 ><P
6170 >Default: <B
6171 CLASS="COMMAND"
6172 >code page directory = ${prefix}/lib/codepages
6173                 </B
6174 ></P
6175 ><P
6176 >Example: <B
6177 CLASS="COMMAND"
6178 >code page directory = /usr/share/samba/codepages
6179                 </B
6180 ></P
6181 ></DD
6182 ><DT
6183 ><A
6184 NAME="CODINGSYSTEM"
6185 ></A
6186 >coding system (G)</DT
6187 ><DD
6188 ><P
6189 >This parameter is used to determine how incoming
6190                 Shift-JIS Japanese characters are mapped from the incoming <A
6191 HREF="#CLIENTCODEPAGE"
6192 ><TT
6193 CLASS="PARAMETER"
6194 ><I
6195 >client code page</I
6196 ></TT
6197 >
6198                 </A
6199 > used by the client, into file names in the UNIX filesystem.
6200                 Only useful if <TT
6201 CLASS="PARAMETER"
6202 ><I
6203 >client code page</I
6204 ></TT
6205 > is set to
6206                 932 (Japanese Shift-JIS).  The options are :</P
6207 ><P
6208 ></P
6209 ><UL
6210 ><LI
6211 ><P
6212 ><TT
6213 CLASS="CONSTANT"
6214 >SJIS</TT
6215 >  - Shift-JIS. Does no
6216                         conversion of the incoming filename.</P
6217 ></LI
6218 ><LI
6219 ><P
6220 ><TT
6221 CLASS="CONSTANT"
6222 >JIS8, J8BB, J8BH, J8@B,
6223                         J8@J, J8@H </TT
6224 > - Convert from incoming Shift-JIS to eight
6225                         bit JIS code with different shift-in, shift out codes.</P
6226 ></LI
6227 ><LI
6228 ><P
6229 ><TT
6230 CLASS="CONSTANT"
6231 >JIS7, J7BB, J7BH, J7@B, J7@J,
6232                         J7@H </TT
6233 > - Convert from incoming Shift-JIS to seven bit
6234                         JIS code with different shift-in, shift out codes.</P
6235 ></LI
6236 ><LI
6237 ><P
6238 ><TT
6239 CLASS="CONSTANT"
6240 >JUNET, JUBB, JUBH, JU@B, JU@J, JU@H </TT
6241 >
6242                         - Convert from incoming Shift-JIS to JUNET code with different shift-in,
6243                         shift out codes.</P
6244 ></LI
6245 ><LI
6246 ><P
6247 ><TT
6248 CLASS="CONSTANT"
6249 >EUC</TT
6250 > - Convert an incoming
6251                         Shift-JIS character to EUC code.</P
6252 ></LI
6253 ><LI
6254 ><P
6255 ><TT
6256 CLASS="CONSTANT"
6257 >HEX</TT
6258 > - Convert an incoming
6259                         Shift-JIS character to a 3 byte hex representation, i.e.
6260                         <TT
6261 CLASS="CONSTANT"
6262 >:AB</TT
6263 >.</P
6264 ></LI
6265 ><LI
6266 ><P
6267 ><TT
6268 CLASS="CONSTANT"
6269 >CAP</TT
6270 > - Convert an incoming
6271                         Shift-JIS character to the 3 byte hex representation used by
6272                         the Columbia AppleTalk Program (CAP), i.e. <TT
6273 CLASS="CONSTANT"
6274 >:AB</TT
6275 >.
6276                         This is used for compatibility between Samba and CAP.</P
6277 ></LI
6278 ></UL
6279 ><P
6280 >Default: <B
6281 CLASS="COMMAND"
6282 >coding system = &#60;empty value&#62;</B
6283 >
6284                 </P
6285 ></DD
6286 ><DT
6287 ><A
6288 NAME="COMMENT"
6289 ></A
6290 >comment (S)</DT
6291 ><DD
6292 ><P
6293 >This is a text field that is seen next to a share
6294                 when a client does a queries the server, either via the network
6295                 neighborhood or via <B
6296 CLASS="COMMAND"
6297 >net view</B
6298 > to list what shares
6299                 are available.</P
6300 ><P
6301 >If you want to set the string that is displayed next to the
6302                 machine name then see the <A
6303 HREF="#SERVERSTRING"
6304 ><TT
6305 CLASS="PARAMETER"
6306 ><I
6307 >               server string</I
6308 ></TT
6309 ></A
6310 > parameter.</P
6311 ><P
6312 >Default: <EM
6313 >No comment string</EM
6314 ></P
6315 ><P
6316 >Example: <B
6317 CLASS="COMMAND"
6318 >comment = Fred's Files</B
6319 ></P
6320 ></DD
6321 ><DT
6322 ><A
6323 NAME="CONFIGFILE"
6324 ></A
6325 >config file (G)</DT
6326 ><DD
6327 ><P
6328 >This allows you to override the config file
6329                 to use, instead of the default (usually <TT
6330 CLASS="FILENAME"
6331 >smb.conf</TT
6332 >).
6333                 There is a chicken and egg problem here as this option is set
6334                 in the config file!</P
6335 ><P
6336 >For this reason, if the name of the config file has changed
6337                 when the parameters are loaded then it will reload them from
6338                 the new config file.</P
6339 ><P
6340 >This option takes the usual substitutions, which can
6341                 be very useful.</P
6342 ><P
6343 >If the config file doesn't exist then it won't be loaded
6344                 (allowing you to special case the config files of just a few
6345                 clients).</P
6346 ><P
6347 >Example: <B
6348 CLASS="COMMAND"
6349 >config file = /usr/local/samba/lib/smb.conf.%m
6350                 </B
6351 ></P
6352 ></DD
6353 ><DT
6354 ><A
6355 NAME="COPY"
6356 ></A
6357 >copy (S)</DT
6358 ><DD
6359 ><P
6360 >This parameter allows you to "clone" service
6361                 entries. The specified service is simply duplicated under the
6362                 current service's name. Any parameters specified in the current
6363                 section will override those in the section being copied.</P
6364 ><P
6365 >This feature lets you set up a 'template' service and
6366                 create similar services easily. Note that the service being
6367                 copied must occur earlier in the configuration file than the
6368                 service doing the copying.</P
6369 ><P
6370 >Default: <EM
6371 >no value</EM
6372 ></P
6373 ><P
6374 >Example: <B
6375 CLASS="COMMAND"
6376 >copy = otherservice</B
6377 ></P
6378 ></DD
6379 ><DT
6380 ><A
6381 NAME="CREATEMASK"
6382 ></A
6383 >create mask (S)</DT
6384 ><DD
6385 ><P
6386 >A synonym for this parameter is
6387                 <A
6388 HREF="#CREATEMODE"
6389 ><TT
6390 CLASS="PARAMETER"
6391 ><I
6392 >create mode</I
6393 ></TT
6394 >
6395                 </A
6396 >.</P
6397 ><P
6398 >When a file is created, the necessary permissions are
6399                 calculated according to the mapping from DOS modes to UNIX
6400                 permissions, and the resulting UNIX mode is then bit-wise 'AND'ed
6401                 with this parameter. This parameter may be thought of as a bit-wise
6402                 MASK for the UNIX modes of a file. Any bit <EM
6403 >not</EM
6404 >
6405                 set here will be removed from the modes set on a file when it is
6406                 created.</P
6407 ><P
6408 >The default value of this parameter removes the
6409                 'group' and 'other' write and execute bits from the UNIX modes.</P
6410 ><P
6411 >Following this Samba will bit-wise 'OR' the UNIX mode created
6412                 from this parameter with the value of the <A
6413 HREF="#FORCECREATEMODE"
6414 ><TT
6415 CLASS="PARAMETER"
6416 ><I
6417 >force create mode</I
6418 ></TT
6419 ></A
6420 >
6421                 parameter which is set to 000 by default.</P
6422 ><P
6423 >This parameter does not affect directory modes. See the
6424                 parameter <A
6425 HREF="#DIRECTORYMODE"
6426 ><TT
6427 CLASS="PARAMETER"
6428 ><I
6429 >directory mode
6430                 </I
6431 ></TT
6432 ></A
6433 > for details.</P
6434 ><P
6435 >See also the <A
6436 HREF="#FORCECREATEMODE"
6437 ><TT
6438 CLASS="PARAMETER"
6439 ><I
6440 >force
6441                 create mode</I
6442 ></TT
6443 ></A
6444 > parameter for forcing particular mode
6445                 bits to be set on created files. See also the <A
6446 HREF="#DIRECTORYMODE"
6447 >               <TT
6448 CLASS="PARAMETER"
6449 ><I
6450 >directory mode</I
6451 ></TT
6452 ></A
6453 > parameter for masking
6454                 mode bits on created directories.  See also the <A
6455 HREF="#INHERITPERMISSIONS"
6456 >               <TT
6457 CLASS="PARAMETER"
6458 ><I
6459 >inherit permissions</I
6460 ></TT
6461 ></A
6462 > parameter.</P
6463 ><P
6464 >Note that this parameter does not apply to permissions
6465                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
6466                 a mask on access control lists also, they need to set the <A
6467 HREF="#SECURITYMASK"
6468 ><TT
6469 CLASS="PARAMETER"
6470 ><I
6471 >security mask</I
6472 ></TT
6473 ></A
6474 >.</P
6475 ><P
6476 >Default: <B
6477 CLASS="COMMAND"
6478 >create mask = 0744</B
6479 ></P
6480 ><P
6481 >Example: <B
6482 CLASS="COMMAND"
6483 >create mask = 0775</B
6484 ></P
6485 ></DD
6486 ><DT
6487 ><A
6488 NAME="CREATEMODE"
6489 ></A
6490 >create mode (S)</DT
6491 ><DD
6492 ><P
6493 >This is a synonym for <A
6494 HREF="#CREATEMASK"
6495 ><TT
6496 CLASS="PARAMETER"
6497 ><I
6498 >               create mask</I
6499 ></TT
6500 ></A
6501 >.</P
6502 ></DD
6503 ><DT
6504 ><A
6505 NAME="CSCPOLICY"
6506 ></A
6507 >csc policy (S)</DT
6508 ><DD
6509 ><P
6510 >This stands for <EM
6511 >client-side caching
6512                 policy</EM
6513 >, and specifies how clients capable of offline
6514                 caching will cache the files in the share. The valid values
6515                 are: manual, documents, programs, disable.</P
6516 ><P
6517 >These values correspond to those used on Windows
6518                 servers.</P
6519 ><P
6520 >For example, shares containing roaming profiles can have
6521                 offline caching disabled using <B
6522 CLASS="COMMAND"
6523 >csc policy = disable
6524                 </B
6525 >.</P
6526 ><P
6527 >Default: <B
6528 CLASS="COMMAND"
6529 >csc policy = manual</B
6530 ></P
6531 ><P
6532 >Example: <B
6533 CLASS="COMMAND"
6534 >csc policy = programs</B
6535 ></P
6536 ></DD
6537 ><DT
6538 ><A
6539 NAME="DEADTIME"
6540 ></A
6541 >deadtime (G)</DT
6542 ><DD
6543 ><P
6544 >The value of the parameter (a decimal integer)
6545                 represents the number of minutes of inactivity before a connection
6546                 is considered dead, and it is disconnected. The deadtime only takes
6547                 effect if the number of open files is zero.</P
6548 ><P
6549 >This is useful to stop a server's resources being
6550                 exhausted by a large number of inactive connections.</P
6551 ><P
6552 >Most clients have an auto-reconnect feature when a
6553                 connection is broken so in most cases this parameter should be
6554                 transparent to users.</P
6555 ><P
6556 >Using this parameter with a timeout of a few minutes
6557                 is recommended for most systems.</P
6558 ><P
6559 >A deadtime of zero indicates that no auto-disconnection
6560                 should be performed.</P
6561 ><P
6562 >Default: <B
6563 CLASS="COMMAND"
6564 >deadtime = 0</B
6565 ></P
6566 ><P
6567 >Example: <B
6568 CLASS="COMMAND"
6569 >deadtime = 15</B
6570 ></P
6571 ></DD
6572 ><DT
6573 ><A
6574 NAME="DEBUGHIRESTIMESTAMP"
6575 ></A
6576 >debug hires timestamp (G)</DT
6577 ><DD
6578 ><P
6579 >Sometimes the timestamps in the log messages
6580                 are needed with a resolution of higher that seconds, this
6581                 boolean parameter adds microsecond resolution to the timestamp
6582                 message header when turned on.</P
6583 ><P
6584 >Note that the parameter <A
6585 HREF="#DEBUGTIMESTAMP"
6586 ><TT
6587 CLASS="PARAMETER"
6588 ><I
6589 >               debug timestamp</I
6590 ></TT
6591 ></A
6592 > must be on for this to have an
6593                 effect.</P
6594 ><P
6595 >Default: <B
6596 CLASS="COMMAND"
6597 >debug hires timestamp = no</B
6598 ></P
6599 ></DD
6600 ><DT
6601 ><A
6602 NAME="DEBUGPID"
6603 ></A
6604 >debug pid (G)</DT
6605 ><DD
6606 ><P
6607 >When using only one log file for more then one
6608                 forked <A
6609 HREF="smbd.8.html"
6610 TARGET="_top"
6611 >smbd</A
6612 >-process there may be hard to follow which process
6613                 outputs which message. This boolean parameter is adds the process-id
6614                 to the timestamp message headers in the logfile when turned on.</P
6615 ><P
6616 >Note that the parameter <A
6617 HREF="#DEBUGTIMESTAMP"
6618 ><TT
6619 CLASS="PARAMETER"
6620 ><I
6621 >               debug timestamp</I
6622 ></TT
6623 ></A
6624 > must be on for this to have an
6625                 effect.</P
6626 ><P
6627 >Default: <B
6628 CLASS="COMMAND"
6629 >debug pid = no</B
6630 ></P
6631 ></DD
6632 ><DT
6633 ><A
6634 NAME="DEBUGTIMESTAMP"
6635 ></A
6636 >debug timestamp (G)</DT
6637 ><DD
6638 ><P
6639 >Samba 2.2 debug log messages are timestamped
6640                 by default. If you are running at a high <A
6641 HREF="#DEBUGLEVEL"
6642 >               <TT
6643 CLASS="PARAMETER"
6644 ><I
6645 >debug level</I
6646 ></TT
6647 ></A
6648 > these timestamps
6649                 can be distracting. This boolean parameter allows timestamping
6650                 to be turned off.</P
6651 ><P
6652 >Default: <B
6653 CLASS="COMMAND"
6654 >debug timestamp = yes</B
6655 ></P
6656 ></DD
6657 ><DT
6658 ><A
6659 NAME="DEBUGUID"
6660 ></A
6661 >debug uid (G)</DT
6662 ><DD
6663 ><P
6664 >Samba is sometimes run as root and sometime
6665                 run as the connected user, this boolean parameter inserts the
6666                 current euid, egid, uid and gid to the timestamp message headers
6667                 in the log file if turned on.</P
6668 ><P
6669 >Note that the parameter <A
6670 HREF="#DEBUGTIMESTAMP"
6671 ><TT
6672 CLASS="PARAMETER"
6673 ><I
6674 >               debug timestamp</I
6675 ></TT
6676 ></A
6677 > must be on for this to have an
6678                 effect.</P
6679 ><P
6680 >Default: <B
6681 CLASS="COMMAND"
6682 >debug uid = no</B
6683 ></P
6684 ></DD
6685 ><DT
6686 ><A
6687 NAME="DEBUGLEVEL"
6688 ></A
6689 >debuglevel (G)</DT
6690 ><DD
6691 ><P
6692 >Synonym for <A
6693 HREF="#LOGLEVEL"
6694 ><TT
6695 CLASS="PARAMETER"
6696 ><I
6697 >               log level</I
6698 ></TT
6699 ></A
6700 >.</P
6701 ></DD
6702 ><DT
6703 ><A
6704 NAME="DEFAULT"
6705 ></A
6706 >default (G)</DT
6707 ><DD
6708 ><P
6709 >A synonym for <A
6710 HREF="#DEFAULTSERVICE"
6711 ><TT
6712 CLASS="PARAMETER"
6713 ><I
6714 >               default service</I
6715 ></TT
6716 ></A
6717 >.</P
6718 ></DD
6719 ><DT
6720 ><A
6721 NAME="DEFAULTCASE"
6722 ></A
6723 >default case (S)</DT
6724 ><DD
6725 ><P
6726 >See the section on <A
6727 HREF="#AEN203"
6728 >               NAME MANGLING</A
6729 >. Also note the <A
6730 HREF="#SHORTPRESERVECASE"
6731 >               <TT
6732 CLASS="PARAMETER"
6733 ><I
6734 >short preserve case</I
6735 ></TT
6736 ></A
6737 > parameter.</P
6738 ><P
6739 >Default: <B
6740 CLASS="COMMAND"
6741 >default case = lower</B
6742 ></P
6743 ></DD
6744 ><DT
6745 ><A
6746 NAME="DEFAULTDEVMODE"
6747 ></A
6748 >default devmode (S)</DT
6749 ><DD
6750 ><P
6751 >This parameter is only applicable to <A
6752 HREF="#PRINTOK"
6753 >printable</A
6754 > services.  When smbd is serving
6755                 Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
6756                 server has a Device Mode which defines things such as paper size and
6757                 orientation and duplex settings.  The device mode can only correctly be
6758                 generated by the printer driver itself (which can only be executed on a
6759                 Win32 platform).  Because smbd is unable to execute the driver code
6760                 to generate the device mode, the default behavior is to set this field
6761                 to NULL.
6762                 </P
6763 ><P
6764 >Most problems with serving printer drivers to Windows NT/2k/XP clients
6765                 can be traced to a problem with the generated device mode.  Certain drivers
6766                 will do things such as crashing the client's Explorer.exe with a NULL devmode.
6767                 However, other printer drivers can cause the client's spooler service
6768                 (spoolsv.exe) to die if the devmode was not created by the driver itself
6769                 (i.e. smbd generates a default devmode).
6770                 </P
6771 ><P
6772 >This parameter should be used with care and tested with the printer
6773                 driver in question.  It is better to leave the device mode to NULL
6774                 and let the Windows client set the correct values.  Because drivers do not
6775                 do this all the time, setting <B
6776 CLASS="COMMAND"
6777 >default devmode = yes</B
6778 >
6779                 will instruct smbd to generate a default one.
6780                 </P
6781 ><P
6782 >For more information on Windows NT/2k printing and Device Modes,
6783                 see the <A
6784 HREF="http://msdn.microsoft.com/"
6785 TARGET="_top"
6786 >MSDN documentation</A
6787 >.
6788                 </P
6789 ><P
6790 >Default: <B
6791 CLASS="COMMAND"
6792 >default devmode = no</B
6793 ></P
6794 ></DD
6795 ><DT
6796 ><A
6797 NAME="DEFAULTSERVICE"
6798 ></A
6799 >default service (G)</DT
6800 ><DD
6801 ><P
6802 >This parameter specifies the name of a service
6803                 which will be connected to if the service actually requested cannot
6804                 be found. Note that the square brackets are <EM
6805 >NOT</EM
6806 >
6807                 given in the parameter value (see example below).</P
6808 ><P
6809 >There is no default value for this parameter. If this
6810                 parameter is not given, attempting to connect to a nonexistent
6811                 service results in an error.</P
6812 ><P
6813 >Typically the default service would be a <A
6814 HREF="#GUESTOK"
6815 >               <TT
6816 CLASS="PARAMETER"
6817 ><I
6818 >guest ok</I
6819 ></TT
6820 ></A
6821 >, <A
6822 HREF="#READONLY"
6823 >               <TT
6824 CLASS="PARAMETER"
6825 ><I
6826 >read-only</I
6827 ></TT
6828 ></A
6829 > service.</P
6830 ><P
6831 >Also note that the apparent service name will be changed
6832                 to equal that of the requested service, this is very useful as it
6833                 allows you to use macros like <TT
6834 CLASS="PARAMETER"
6835 ><I
6836 >%S</I
6837 ></TT
6838 > to make
6839                 a wildcard service.</P
6840 ><P
6841 >Note also that any "_" characters in the name of the service
6842                 used in the default service will get mapped to a "/". This allows for
6843                 interesting things.</P
6844 ><P
6845 >Example:</P
6846 ><P
6847 ><TABLE
6848 BORDER="0"
6849 BGCOLOR="#E0E0E0"
6850 WIDTH="90%"
6851 ><TR
6852 ><TD
6853 ><PRE
6854 CLASS="PROGRAMLISTING"
6855 >[global]
6856         default service = pub
6857
6858 [pub]
6859         path = /%S
6860                 </PRE
6861 ></TD
6862 ></TR
6863 ></TABLE
6864 ></P
6865 ></DD
6866 ><DT
6867 ><A
6868 NAME="DELETEPRINTERCOMMAND"
6869 ></A
6870 >delete printer command (G)</DT
6871 ><DD
6872 ><P
6873 >With the introduction of MS-RPC based printer
6874                 support for Windows NT/2000 clients in Samba 2.2, it is now
6875                 possible to delete printer at run time by issuing the
6876                 DeletePrinter() RPC call.</P
6877 ><P
6878 >For a Samba host this means that the printer must be
6879                 physically deleted from underlying printing system.  The <TT
6880 CLASS="PARAMETER"
6881 ><I
6882 >               deleteprinter command</I
6883 ></TT
6884 > defines a script to be run which
6885                 will perform the necessary operations for removing the printer
6886                 from the print system and from <TT
6887 CLASS="FILENAME"
6888 >smb.conf</TT
6889 >.
6890                 </P
6891 ><P
6892 >The <TT
6893 CLASS="PARAMETER"
6894 ><I
6895 >delete printer command</I
6896 ></TT
6897 > is
6898                 automatically called with only one parameter: <TT
6899 CLASS="PARAMETER"
6900 ><I
6901 >               "printer name"</I
6902 ></TT
6903 >.</P
6904 ><P
6905 >Once the <TT
6906 CLASS="PARAMETER"
6907 ><I
6908 >delete printer command</I
6909 ></TT
6910 > has
6911                 been executed, <B
6912 CLASS="COMMAND"
6913 >smbd</B
6914 > will reparse the <TT
6915 CLASS="FILENAME"
6916 >               smb.conf</TT
6917 > to associated printer no longer exists.
6918                 If the sharename is still valid, then <B
6919 CLASS="COMMAND"
6920 >smbd
6921                 </B
6922 > will return an ACCESS_DENIED error to the client.</P
6923 ><P
6924 >See also <A
6925 HREF="#ADDPRINTERCOMMAND"
6926 ><TT
6927 CLASS="PARAMETER"
6928 ><I
6929 >               add printer command</I
6930 ></TT
6931 ></A
6932 >, <A
6933 HREF="#PRINTING"
6934 ><TT
6935 CLASS="PARAMETER"
6936 ><I
6937 >printing</I
6938 ></TT
6939 ></A
6940 >,
6941                 <A
6942 HREF="#SHOWADDPRINTERWIZARD"
6943 ><TT
6944 CLASS="PARAMETER"
6945 ><I
6946 >show add
6947                 printer wizard</I
6948 ></TT
6949 ></A
6950 ></P
6951 ><P
6952 >Default: <EM
6953 >none</EM
6954 ></P
6955 ><P
6956 >Example: <B
6957 CLASS="COMMAND"
6958 >deleteprinter command = /usr/bin/removeprinter
6959                 </B
6960 ></P
6961 ></DD
6962 ><DT
6963 ><A
6964 NAME="DELETEREADONLY"
6965 ></A
6966 >delete readonly (S)</DT
6967 ><DD
6968 ><P
6969 >This parameter allows readonly files to be deleted.
6970                 This is not normal DOS semantics, but is allowed by UNIX.</P
6971 ><P
6972 >This option may be useful for running applications such
6973                 as rcs, where UNIX file ownership prevents changing file
6974                 permissions, and DOS semantics prevent deletion of a read only file.</P
6975 ><P
6976 >Default: <B
6977 CLASS="COMMAND"
6978 >delete readonly = no</B
6979 ></P
6980 ></DD
6981 ><DT
6982 ><A
6983 NAME="DELETESHARECOMMAND"
6984 ></A
6985 >delete share command (G)</DT
6986 ><DD
6987 ><P
6988 >Samba 2.2.0 introduced the ability to dynamically
6989                 add and delete shares via the Windows NT 4.0 Server Manager.  The
6990                 <TT
6991 CLASS="PARAMETER"
6992 ><I
6993 >delete share command</I
6994 ></TT
6995 > is used to define an
6996                 external program or script which will remove an existing service
6997                 definition from <TT
6998 CLASS="FILENAME"
6999 >smb.conf</TT
7000 >.  In order to successfully
7001                 execute the <TT
7002 CLASS="PARAMETER"
7003 ><I
7004 >delete share command</I
7005 ></TT
7006 >, <B
7007 CLASS="COMMAND"
7008 >smbd</B
7009 >
7010                 requires that the administrator be connected using a root account (i.e.
7011                 uid == 0).
7012                 </P
7013 ><P
7014 >               When executed, <B
7015 CLASS="COMMAND"
7016 >smbd</B
7017 > will automatically invoke the
7018                 <TT
7019 CLASS="PARAMETER"
7020 ><I
7021 >delete share command</I
7022 ></TT
7023 > with two parameters.
7024                 </P
7025 ><P
7026 ></P
7027 ><UL
7028 ><LI
7029 ><P
7030 ><TT
7031 CLASS="PARAMETER"
7032 ><I
7033 >configFile</I
7034 ></TT
7035 > - the location
7036                         of the global <TT
7037 CLASS="FILENAME"
7038 >smb.conf</TT
7039 > file.
7040                         </P
7041 ></LI
7042 ><LI
7043 ><P
7044 ><TT
7045 CLASS="PARAMETER"
7046 ><I
7047 >shareName</I
7048 ></TT
7049 > - the name of
7050                         the existing service.
7051                         </P
7052 ></LI
7053 ></UL
7054 ><P
7055 >               This parameter is only used to remove file shares.  To delete printer shares,
7056                 see the <A
7057 HREF="#DELETEPRINTERCOMMAND"
7058 ><TT
7059 CLASS="PARAMETER"
7060 ><I
7061 >delete printer
7062                 command</I
7063 ></TT
7064 ></A
7065 >.
7066                 </P
7067 ><P
7068 >               See also <A
7069 HREF="#ADDSHARECOMMAND"
7070 ><TT
7071 CLASS="PARAMETER"
7072 ><I
7073 >add share
7074                 command</I
7075 ></TT
7076 ></A
7077 >, <A
7078 HREF="#CHANGESHARECOMMAND"
7079 ><TT
7080 CLASS="PARAMETER"
7081 ><I
7082 >change
7083                 share command</I
7084 ></TT
7085 ></A
7086 >.
7087                 </P
7088 ><P
7089 >Default: <EM
7090 >none</EM
7091 ></P
7092 ><P
7093 >Example: <B
7094 CLASS="COMMAND"
7095 >delete share command = /usr/local/bin/delshare</B
7096 ></P
7097 ></DD
7098 ><DT
7099 ><A
7100 NAME="DELETEUSERSCRIPT"
7101 ></A
7102 >delete user script (G)</DT
7103 ><DD
7104 ><P
7105 >This is the full pathname to a script that will
7106                 be run <EM
7107 >AS ROOT</EM
7108 > by <A
7109 HREF="smbd.8.html"
7110 TARGET="_top"
7111 >               <B
7112 CLASS="COMMAND"
7113 >smbd(8)</B
7114 ></A
7115 > under special circumstances
7116                 described below.</P
7117 ><P
7118 >Normally, a Samba server requires that UNIX users are
7119                 created for all users accessing files on this server. For sites
7120                 that use Windows NT account databases as their primary user database
7121                 creating these users and keeping the user list in sync with the
7122                 Windows NT PDC is an onerous task. This option allows <B
7123 CLASS="COMMAND"
7124 >               smbd</B
7125 > to delete the required UNIX users <EM
7126 >ON
7127                 DEMAND</EM
7128 > when a user accesses the Samba server and the
7129                 Windows NT user no longer exists.</P
7130 ><P
7131 >In order to use this option, <B
7132 CLASS="COMMAND"
7133 >smbd</B
7134 > must be
7135                 set to <TT
7136 CLASS="PARAMETER"
7137 ><I
7138 >security = domain</I
7139 ></TT
7140 > or <TT
7141 CLASS="PARAMETER"
7142 ><I
7143 >security =
7144                 user</I
7145 ></TT
7146 > and <TT
7147 CLASS="PARAMETER"
7148 ><I
7149 >delete user script</I
7150 ></TT
7151 >
7152                 must be set to a full pathname for a script
7153                 that will delete a UNIX user given one argument of <TT
7154 CLASS="PARAMETER"
7155 ><I
7156 >%u</I
7157 ></TT
7158 >,
7159                 which expands into the UNIX user name to delete.</P
7160 ><P
7161 >When the Windows user attempts to access the Samba server,
7162                 at <EM
7163 >login</EM
7164 > (session setup in the SMB protocol)
7165                 time, <B
7166 CLASS="COMMAND"
7167 >smbd</B
7168 > contacts the <A
7169 HREF="#PASSWORDSERVER"
7170 >               <TT
7171 CLASS="PARAMETER"
7172 ><I
7173 >password server</I
7174 ></TT
7175 ></A
7176 > and attempts to authenticate
7177                 the given user with the given password. If the authentication fails
7178                 with the specific Domain error code meaning that the user no longer
7179                 exists then <B
7180 CLASS="COMMAND"
7181 >smbd</B
7182 > attempts to find a UNIX user in
7183                 the UNIX password database that matches the Windows user account. If
7184                 this lookup succeeds, and <TT
7185 CLASS="PARAMETER"
7186 ><I
7187 >delete user script</I
7188 ></TT
7189 > is
7190                 set then <B
7191 CLASS="COMMAND"
7192 >smbd</B
7193 > will all the specified script
7194                 <EM
7195 >AS ROOT</EM
7196 >, expanding any <TT
7197 CLASS="PARAMETER"
7198 ><I
7199 >%u</I
7200 ></TT
7201 >
7202                 argument to be the user name to delete.</P
7203 ><P
7204 >This script should delete the given UNIX username. In this way,
7205                 UNIX users are dynamically deleted to match existing Windows NT
7206                 accounts.</P
7207 ><P
7208 >See also <A
7209 HREF="#SECURITYEQUALSDOMAIN"
7210 >security = domain</A
7211 >,
7212                 <A
7213 HREF="#PASSWORDSERVER"
7214 ><TT
7215 CLASS="PARAMETER"
7216 ><I
7217 >password server</I
7218 ></TT
7219 >
7220                 </A
7221 >, <A
7222 HREF="#ADDUSERSCRIPT"
7223 ><TT
7224 CLASS="PARAMETER"
7225 ><I
7226 >add user script</I
7227 ></TT
7228 >
7229                 </A
7230 >.</P
7231 ><P
7232 >Default: <B
7233 CLASS="COMMAND"
7234 >delete user script = &#60;empty string&#62;
7235                 </B
7236 ></P
7237 ><P
7238 >Example: <B
7239 CLASS="COMMAND"
7240 >delete user script = /usr/local/samba/bin/del_user
7241                 %u</B
7242 ></P
7243 ></DD
7244 ><DT
7245 ><A
7246 NAME="DELETEVETOFILES"
7247 ></A
7248 >delete veto files (S)</DT
7249 ><DD
7250 ><P
7251 >This option is used when Samba is attempting to
7252                 delete a directory that contains one or more vetoed directories
7253                 (see the <A
7254 HREF="#VETOFILES"
7255 ><TT
7256 CLASS="PARAMETER"
7257 ><I
7258 >veto files</I
7259 ></TT
7260 ></A
7261 >
7262                 option).  If this option is set to <TT
7263 CLASS="CONSTANT"
7264 >no</TT
7265 > (the default) then if a vetoed
7266                 directory contains any non-vetoed files or directories then the
7267                 directory delete will fail. This is usually what you want.</P
7268 ><P
7269 >If this option is set to <TT
7270 CLASS="CONSTANT"
7271 >yes</TT
7272 >, then Samba
7273                 will attempt to recursively delete any files and directories within
7274                 the vetoed directory. This can be useful for integration with file
7275                 serving systems such as NetAtalk which create meta-files within
7276                 directories you might normally veto DOS/Windows users from seeing
7277                 (e.g. <TT
7278 CLASS="FILENAME"
7279 >.AppleDouble</TT
7280 >)</P
7281 ><P
7282 >Setting <B
7283 CLASS="COMMAND"
7284 >delete veto files = yes</B
7285 > allows these
7286                 directories to be  transparently deleted when the parent directory
7287                 is deleted (so long as the user has permissions to do so).</P
7288 ><P
7289 >See also the <A
7290 HREF="#VETOFILES"
7291 ><TT
7292 CLASS="PARAMETER"
7293 ><I
7294 >veto
7295                 files</I
7296 ></TT
7297 ></A
7298 > parameter.</P
7299 ><P
7300 >Default: <B
7301 CLASS="COMMAND"
7302 >delete veto files = no</B
7303 ></P
7304 ></DD
7305 ><DT
7306 ><A
7307 NAME="DENYHOSTS"
7308 ></A
7309 >deny hosts (S)</DT
7310 ><DD
7311 ><P
7312 >Synonym for <A
7313 HREF="#HOSTSDENY"
7314 ><TT
7315 CLASS="PARAMETER"
7316 ><I
7317 >hosts
7318                 deny</I
7319 ></TT
7320 ></A
7321 >.</P
7322 ></DD
7323 ><DT
7324 ><A
7325 NAME="DFREECOMMAND"
7326 ></A
7327 >dfree command (G)</DT
7328 ><DD
7329 ><P
7330 >The <TT
7331 CLASS="PARAMETER"
7332 ><I
7333 >dfree command</I
7334 ></TT
7335 > setting should
7336                 only be used on systems where a problem occurs with the internal
7337                 disk space calculations. This has been known to happen with Ultrix,
7338                 but may occur with other operating systems. The symptom that was
7339                 seen was an error of "Abort Retry Ignore" at the end of each
7340                 directory listing.</P
7341 ><P
7342 >This setting allows the replacement of the internal routines to
7343                 calculate the total disk space and amount available with an external
7344                 routine. The example below gives a possible script that might fulfill
7345                 this function.</P
7346 ><P
7347 >The external program will be passed a single parameter indicating
7348                 a directory in the filesystem being queried. This will typically consist
7349                 of the string <TT
7350 CLASS="FILENAME"
7351 >./</TT
7352 >. The script should return two
7353                 integers in ASCII. The first should be the total disk space in blocks,
7354                 and the second should be the number of available blocks. An optional
7355                 third return value can give the block size in bytes. The default
7356                 blocksize is 1024 bytes.</P
7357 ><P
7358 >Note: Your script should <EM
7359 >NOT</EM
7360 > be setuid or
7361                 setgid and should be owned by (and writeable only by) root!</P
7362 ><P
7363 >Default: <EM
7364 >By default internal routines for
7365                 determining the disk capacity and remaining space will be used.
7366                 </EM
7367 ></P
7368 ><P
7369 >Example: <B
7370 CLASS="COMMAND"
7371 >dfree command = /usr/local/samba/bin/dfree
7372                 </B
7373 ></P
7374 ><P
7375 >Where the script dfree (which must be made executable) could be:</P
7376 ><P
7377 ><TABLE
7378 BORDER="0"
7379 BGCOLOR="#E0E0E0"
7380 WIDTH="90%"
7381 ><TR
7382 ><TD
7383 ><PRE
7384 CLASS="PROGRAMLISTING"
7385 >
7386                 #!/bin/sh
7387                 df $1 | tail -1 | awk '{print $2" "$4}'
7388                 </PRE
7389 ></TD
7390 ></TR
7391 ></TABLE
7392 ></P
7393 ><P
7394 >or perhaps (on Sys V based systems):</P
7395 ><P
7396 ><TABLE
7397 BORDER="0"
7398 BGCOLOR="#E0E0E0"
7399 WIDTH="90%"
7400 ><TR
7401 ><TD
7402 ><PRE
7403 CLASS="PROGRAMLISTING"
7404 >
7405                 #!/bin/sh
7406                 /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
7407                 </PRE
7408 ></TD
7409 ></TR
7410 ></TABLE
7411 ></P
7412 ><P
7413 >Note that you may have to replace the command names
7414                 with full path names on some systems.</P
7415 ></DD
7416 ><DT
7417 ><A
7418 NAME="DIRECTORY"
7419 ></A
7420 >directory (S)</DT
7421 ><DD
7422 ><P
7423 >Synonym for <A
7424 HREF="#PATH"
7425 ><TT
7426 CLASS="PARAMETER"
7427 ><I
7428 >path
7429                 </I
7430 ></TT
7431 ></A
7432 >.</P
7433 ></DD
7434 ><DT
7435 ><A
7436 NAME="DIRECTORYMASK"
7437 ></A
7438 >directory mask (S)</DT
7439 ><DD
7440 ><P
7441 >This parameter is the octal modes which are
7442                 used when converting DOS modes to UNIX modes when creating UNIX
7443                 directories.</P
7444 ><P
7445 >When a directory is created, the necessary permissions are
7446                 calculated according to the mapping from DOS modes to UNIX permissions,
7447                 and the resulting UNIX mode is then bit-wise 'AND'ed with this
7448                 parameter. This parameter may be thought of as a bit-wise MASK for
7449                 the UNIX modes of a directory. Any bit <EM
7450 >not</EM
7451 > set
7452                 here will be removed from the modes set on a directory when it is
7453                 created.</P
7454 ><P
7455 >The default value of this parameter removes the 'group'
7456                 and 'other' write bits from the UNIX mode, allowing only the
7457                 user who owns the directory to modify it.</P
7458 ><P
7459 >Following this Samba will bit-wise 'OR' the UNIX mode
7460                 created from this parameter with the value of the <A
7461 HREF="#FORCEDIRECTORYMODE"
7462 ><TT
7463 CLASS="PARAMETER"
7464 ><I
7465 >force directory mode
7466                 </I
7467 ></TT
7468 ></A
7469 > parameter. This parameter is set to 000 by
7470                 default (i.e. no extra mode bits are added).</P
7471 ><P
7472 >Note that this parameter does not apply to permissions
7473                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
7474                 a mask on access control lists also, they need to set the <A
7475 HREF="#DIRECTORYSECURITYMASK"
7476 ><TT
7477 CLASS="PARAMETER"
7478 ><I
7479 >directory security mask</I
7480 ></TT
7481 ></A
7482 >.</P
7483 ><P
7484 >See the <A
7485 HREF="#FORCEDIRECTORYMODE"
7486 ><TT
7487 CLASS="PARAMETER"
7488 ><I
7489 >force
7490                 directory mode</I
7491 ></TT
7492 ></A
7493 > parameter to cause particular mode
7494                 bits to always be set on created directories.</P
7495 ><P
7496 >See also the <A
7497 HREF="#CREATEMODE"
7498 ><TT
7499 CLASS="PARAMETER"
7500 ><I
7501 >create mode
7502                 </I
7503 ></TT
7504 ></A
7505 > parameter for masking mode bits on created files,
7506                 and the <A
7507 HREF="#DIRECTORYSECURITYMASK"
7508 ><TT
7509 CLASS="PARAMETER"
7510 ><I
7511 >directory
7512                 security mask</I
7513 ></TT
7514 ></A
7515 > parameter.</P
7516 ><P
7517 >Also refer to the <A
7518 HREF="#INHERITPERMISSIONS"
7519 ><TT
7520 CLASS="PARAMETER"
7521 ><I
7522 >               inherit permissions</I
7523 ></TT
7524 ></A
7525 > parameter.</P
7526 ><P
7527 >Default: <B
7528 CLASS="COMMAND"
7529 >directory mask = 0755</B
7530 ></P
7531 ><P
7532 >Example: <B
7533 CLASS="COMMAND"
7534 >directory mask = 0775</B
7535 ></P
7536 ></DD
7537 ><DT
7538 ><A
7539 NAME="DIRECTORYMODE"
7540 ></A
7541 >directory mode (S)</DT
7542 ><DD
7543 ><P
7544 >Synonym for <A
7545 HREF="#DIRECTORYMASK"
7546 ><TT
7547 CLASS="PARAMETER"
7548 ><I
7549 >               directory mask</I
7550 ></TT
7551 ></A
7552 ></P
7553 ></DD
7554 ><DT
7555 ><A
7556 NAME="DIRECTORYSECURITYMASK"
7557 ></A
7558 >directory security mask (S)</DT
7559 ><DD
7560 ><P
7561 >This parameter controls what UNIX permission bits
7562                 can be modified when a Windows NT client is manipulating the UNIX
7563                 permission on a directory using the native NT security dialog
7564                 box.</P
7565 ><P
7566 >This parameter is applied as a mask (AND'ed with) to
7567                 the changed permission bits, thus preventing any bits not in
7568                 this mask from being modified. Essentially, zero bits in this
7569                 mask may be treated as a set of bits the user is not allowed
7570                 to change.</P
7571 ><P
7572 >If not set explicitly this parameter is set to 0777
7573                 meaning a user is allowed to modify all the user/group/world
7574                 permissions on a directory.</P
7575 ><P
7576 ><EM
7577 >Note</EM
7578 > that users who can access the
7579                 Samba server through other means can easily bypass this restriction,
7580                 so it is primarily useful for standalone "appliance" systems.
7581                 Administrators of most normal systems will probably want to leave
7582                 it as the default of <TT
7583 CLASS="CONSTANT"
7584 >0777</TT
7585 >.</P
7586 ><P
7587 >See also the <A
7588 HREF="#FORCEDIRECTORYSECURITYMODE"
7589 ><TT
7590 CLASS="PARAMETER"
7591 ><I
7592 >               force directory security mode</I
7593 ></TT
7594 ></A
7595 >, <A
7596 HREF="#SECURITYMASK"
7597 ><TT
7598 CLASS="PARAMETER"
7599 ><I
7600 >security mask</I
7601 ></TT
7602 ></A
7603 >,
7604                 <A
7605 HREF="#FORCESECURITYMODE"
7606 ><TT
7607 CLASS="PARAMETER"
7608 ><I
7609 >force security mode
7610                 </I
7611 ></TT
7612 ></A
7613 > parameters.</P
7614 ><P
7615 >Default: <B
7616 CLASS="COMMAND"
7617 >directory security mask = 0777</B
7618 ></P
7619 ><P
7620 >Example: <B
7621 CLASS="COMMAND"
7622 >directory security mask = 0700</B
7623 ></P
7624 ></DD
7625 ><DT
7626 ><A
7627 NAME="DISABLESPOOLSS"
7628 ></A
7629 >disable spoolss (G)</DT
7630 ><DD
7631 ><P
7632 >Enabling this parameter will disables Samba's support
7633                 for the SPOOLSS set of MS-RPC's and will yield identical behavior
7634                 as Samba 2.0.x.  Windows NT/2000 clients will downgrade to using
7635                 Lanman style printing commands. Windows 9x/ME will be uneffected by
7636                 the parameter. However, this will also disable the ability to upload
7637                 printer drivers to a Samba server via the Windows NT Add Printer
7638                 Wizard or by using the NT printer properties dialog window.  It will
7639                 also disable the capability of Windows NT/2000 clients to download
7640                 print drivers from the Samba host upon demand.
7641                 <EM
7642 >Be very careful about enabling this parameter.</EM
7643 >
7644                 </P
7645 ><P
7646 >See also <A
7647 HREF="#USECLIENTDRIVER"
7648 >use client driver</A
7649 >
7650                 </P
7651 ><P
7652 >Default : <B
7653 CLASS="COMMAND"
7654 >disable spoolss = no</B
7655 ></P
7656 ></DD
7657 ><DT
7658 ><A
7659 NAME="DNSPROXY"
7660 ></A
7661 >dns proxy (G)</DT
7662 ><DD
7663 ><P
7664 >Specifies that <A
7665 HREF="nmbd.8.html"
7666 TARGET="_top"
7667 >nmbd(8)</A
7668 >
7669                 when acting as a WINS server and finding that a NetBIOS name has not
7670                 been registered, should treat the NetBIOS name word-for-word as a DNS
7671                 name and do a lookup with the DNS server for that name on behalf of
7672                 the name-querying client.</P
7673 ><P
7674 >Note that the maximum length for a NetBIOS name is 15
7675                 characters, so the DNS name (or DNS alias) can likewise only be
7676                 15 characters, maximum.</P
7677 ><P
7678 ><B
7679 CLASS="COMMAND"
7680 >nmbd</B
7681 > spawns a second copy of itself to do the
7682                 DNS name lookup requests, as doing a name lookup is a blocking
7683                 action.</P
7684 ><P
7685 >See also the parameter <A
7686 HREF="#WINSSUPPORT"
7687 ><TT
7688 CLASS="PARAMETER"
7689 ><I
7690 >               wins support</I
7691 ></TT
7692 ></A
7693 >.</P
7694 ><P
7695 >Default: <B
7696 CLASS="COMMAND"
7697 >dns proxy = yes</B
7698 ></P
7699 ></DD
7700 ><DT
7701 ><A
7702 NAME="DOMAINADMINGROUP"
7703 ></A
7704 >domain admin group (G)</DT
7705 ><DD
7706 ><P
7707 >This parameter is intended as a temporary solution
7708                 to enable users to be a member of the "Domain Admins" group when
7709                 a Samba host is acting as a PDC.  A complete solution will be provided
7710                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7711                 Please note that this parameter has a somewhat confusing name.  It
7712                 accepts a list of usernames and of group names in standard
7713                 <TT
7714 CLASS="FILENAME"
7715 >smb.conf</TT
7716 >       notation.
7717                 </P
7718 ><P
7719 >See also <A
7720 HREF="#DOMAINGUESTGROUP"
7721 ><TT
7722 CLASS="PARAMETER"
7723 ><I
7724 >domain
7725                 guest group</I
7726 ></TT
7727 ></A
7728 >, <A
7729 HREF="#DOMAINLOGONS"
7730 ><TT
7731 CLASS="PARAMETER"
7732 ><I
7733 >domain
7734                 logons</I
7735 ></TT
7736 ></A
7737 >
7738                 </P
7739 ><P
7740 >Default: <EM
7741 >no domain administrators</EM
7742 ></P
7743 ><P
7744 >Example: <B
7745 CLASS="COMMAND"
7746 >domain admin group = root @wheel</B
7747 ></P
7748 ></DD
7749 ><DT
7750 ><A
7751 NAME="DOMAINGUESTGROUP"
7752 ></A
7753 >domain guest group (G)</DT
7754 ><DD
7755 ><P
7756 >This parameter is intended as a temporary solution
7757                 to enable users to be a member of the "Domain Guests" group when
7758                 a Samba host is acting as a PDC.  A complete solution will be provided
7759                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7760                 Please note that this parameter has a somewhat confusing name.  It
7761                 accepts a list of usernames and of group names in standard
7762                 <TT
7763 CLASS="FILENAME"
7764 >smb.conf</TT
7765 >       notation.
7766                 </P
7767 ><P
7768 >See also <A
7769 HREF="#DOMAINADMINGROUP"
7770 ><TT
7771 CLASS="PARAMETER"
7772 ><I
7773 >domain
7774                 admin group</I
7775 ></TT
7776 ></A
7777 >, <A
7778 HREF="#DOMAINLOGONS"
7779 ><TT
7780 CLASS="PARAMETER"
7781 ><I
7782 >domain
7783                 logons</I
7784 ></TT
7785 ></A
7786 >
7787                 </P
7788 ><P
7789 >Default: <EM
7790 >no domain guests</EM
7791 ></P
7792 ><P
7793 >Example: <B
7794 CLASS="COMMAND"
7795 >domain guest group = nobody @guest</B
7796 ></P
7797 ></DD
7798 ><DT
7799 ><A
7800 NAME="DOMAINLOGONS"
7801 ></A
7802 >domain logons (G)</DT
7803 ><DD
7804 ><P
7805 >If set to <TT
7806 CLASS="CONSTANT"
7807 >yes</TT
7808 >, the Samba server will serve
7809                 Windows 95/98 Domain logons for the <A
7810 HREF="#WORKGROUP"
7811 >               <TT
7812 CLASS="PARAMETER"
7813 ><I
7814 >workgroup</I
7815 ></TT
7816 ></A
7817 > it is in. Samba 2.2 also
7818                 has limited capability to act as a domain controller for Windows
7819                 NT 4 Domains.  For more details on setting up this feature see
7820                 the Samba-PDC-HOWTO included in the <TT
7821 CLASS="FILENAME"
7822 >htmldocs/</TT
7823 >
7824                 directory shipped with the source code.</P
7825 ><P
7826 >Default: <B
7827 CLASS="COMMAND"
7828 >domain logons = no</B
7829 ></P
7830 ></DD
7831 ><DT
7832 ><A
7833 NAME="DOMAINMASTER"
7834 ></A
7835 >domain master (G)</DT
7836 ><DD
7837 ><P
7838 >Tell <A
7839 HREF="nmbd.8.html"
7840 TARGET="_top"
7841 ><B
7842 CLASS="COMMAND"
7843 >               nmbd(8)</B
7844 ></A
7845 > to enable WAN-wide browse list
7846                 collation. Setting this option causes <B
7847 CLASS="COMMAND"
7848 >nmbd</B
7849 > to
7850                 claim a special domain specific NetBIOS name that identifies
7851                 it as a domain master browser for its given <A
7852 HREF="#WORKGROUP"
7853 >               <TT
7854 CLASS="PARAMETER"
7855 ><I
7856 >workgroup</I
7857 ></TT
7858 ></A
7859 >. Local master browsers
7860                 in the same <TT
7861 CLASS="PARAMETER"
7862 ><I
7863 >workgroup</I
7864 ></TT
7865 > on broadcast-isolated
7866                 subnets will give this <B
7867 CLASS="COMMAND"
7868 >nmbd</B
7869 > their local browse lists,
7870                 and then ask <A
7871 HREF="smbd.8.html"
7872 TARGET="_top"
7873 ><B
7874 CLASS="COMMAND"
7875 >smbd(8)</B
7876 ></A
7877 >
7878                 for a complete copy of the browse list for the whole wide area
7879                 network.  Browser clients will then contact their local master browser,
7880                 and will receive the domain-wide browse list, instead of just the list
7881                 for their broadcast-isolated subnet.</P
7882 ><P
7883 >Note that Windows NT Primary Domain Controllers expect to be
7884                 able to claim this <TT
7885 CLASS="PARAMETER"
7886 ><I
7887 >workgroup</I
7888 ></TT
7889 > specific special
7890                 NetBIOS name that identifies them as domain master browsers for
7891                 that <TT
7892 CLASS="PARAMETER"
7893 ><I
7894 >workgroup</I
7895 ></TT
7896 > by default (i.e. there is no
7897                 way to prevent a Windows NT PDC from attempting to do this). This
7898                 means that if this parameter is set and <B
7899 CLASS="COMMAND"
7900 >nmbd</B
7901 > claims
7902                 the special name for a <TT
7903 CLASS="PARAMETER"
7904 ><I
7905 >workgroup</I
7906 ></TT
7907 > before a Windows
7908                 NT PDC is able to do so then cross subnet browsing will behave
7909                 strangely and may fail.</P
7910 ><P
7911 >If <A
7912 HREF="#DOMAINLOGONS"
7913 ><B
7914 CLASS="COMMAND"
7915 >domain logons = yes</B
7916 >
7917                 </A
7918 >, then the default behavior is to enable the <TT
7919 CLASS="PARAMETER"
7920 ><I
7921 >domain
7922                 master</I
7923 ></TT
7924 > parameter.  If <TT
7925 CLASS="PARAMETER"
7926 ><I
7927 >domain logons</I
7928 ></TT
7929 > is
7930                 not enabled (the default setting), then neither will <TT
7931 CLASS="PARAMETER"
7932 ><I
7933 >domain
7934                 master</I
7935 ></TT
7936 > be enabled by default.</P
7937 ><P
7938 >Default: <B
7939 CLASS="COMMAND"
7940 >domain master = auto</B
7941 ></P
7942 ></DD
7943 ><DT
7944 ><A
7945 NAME="DONTDESCEND"
7946 ></A
7947 >dont descend (S)</DT
7948 ><DD
7949 ><P
7950 >There are certain directories on some systems
7951                 (e.g., the <TT
7952 CLASS="FILENAME"
7953 >/proc</TT
7954 > tree under Linux) that are either not
7955                 of interest to clients or are infinitely deep (recursive). This
7956                 parameter allows you to specify a comma-delimited list of directories
7957                 that the server should always show as empty.</P
7958 ><P
7959 >Note that Samba can be very fussy about the exact format
7960                 of the "dont descend" entries. For example you may need <TT
7961 CLASS="FILENAME"
7962 >               ./proc</TT
7963 > instead of just <TT
7964 CLASS="FILENAME"
7965 >/proc</TT
7966 >.
7967                 Experimentation is the best policy :-)  </P
7968 ><P
7969 >Default: <EM
7970 >none (i.e., all directories are OK
7971                 to descend)</EM
7972 ></P
7973 ><P
7974 >Example: <B
7975 CLASS="COMMAND"
7976 >dont descend = /proc,/dev</B
7977 ></P
7978 ></DD
7979 ><DT
7980 ><A
7981 NAME="DOSFILEMODE"
7982 ></A
7983 >dos filemode (S)</DT
7984 ><DD
7985 ><P
7986 > The default behavior in Samba is to provide
7987                 UNIX-like behavior where only the owner of a file/directory is
7988                 able to change the permissions on it.  However, this behavior
7989                 is often confusing to  DOS/Windows users.  Enabling this parameter
7990                 allows a user who has write access to the file (by whatever
7991                 means) to modify the permissions on it.  Note that a user
7992                 belonging to the group owning the file will not be allowed to
7993                 change permissions if the group is only granted read access.
7994                 Ownership of the file/directory is not changed, only the permissions
7995                 are modified.</P
7996 ><P
7997 >Default: <B
7998 CLASS="COMMAND"
7999 >dos filemode = no</B
8000 ></P
8001 ></DD
8002 ><DT
8003 ><A
8004 NAME="DOSFILETIMERESOLUTION"
8005 ></A
8006 >dos filetime resolution (S)</DT
8007 ><DD
8008 ><P
8009 >Under the DOS and Windows FAT filesystem, the finest
8010                 granularity on time resolution is two seconds. Setting this parameter
8011                 for a share causes Samba to round the reported time down to the
8012                 nearest two second boundary when a query call that requires one second
8013                 resolution is made to <A
8014 HREF="smbd.8.html"
8015 TARGET="_top"
8016 ><B
8017 CLASS="COMMAND"
8018 >smbd(8)</B
8019 >
8020                 </A
8021 >.</P
8022 ><P
8023 >This option is mainly used as a compatibility option for Visual
8024                 C++ when used against Samba shares. If oplocks are enabled on a
8025                 share, Visual C++ uses two different time reading calls to check if a
8026                 file has changed since it was last read. One of these calls uses a
8027                 one-second granularity, the other uses a two second granularity. As
8028                 the two second call rounds any odd second down, then if the file has a
8029                 timestamp of an odd number of seconds then the two timestamps will not
8030                 match and Visual C++ will keep reporting the file has changed. Setting
8031                 this option causes the two timestamps to match, and Visual C++ is
8032                 happy.</P
8033 ><P
8034 >Default: <B
8035 CLASS="COMMAND"
8036 >dos filetime resolution = no</B
8037 ></P
8038 ></DD
8039 ><DT
8040 ><A
8041 NAME="DOSFILETIMES"
8042 ></A
8043 >dos filetimes (S)</DT
8044 ><DD
8045 ><P
8046 >Under DOS and Windows, if a user can write to a
8047                 file they can change the timestamp on it. Under POSIX semantics,
8048                 only the owner of the file or root may change the timestamp. By
8049                 default, Samba runs with POSIX semantics and refuses to change the
8050                 timestamp on a file if the user <B
8051 CLASS="COMMAND"
8052 >smbd</B
8053 > is acting
8054                 on behalf of is not the file owner. Setting this option to <TT
8055 CLASS="CONSTANT"
8056 >               yes</TT
8057 > allows DOS semantics and <A
8058 HREF="smbd.8.html"
8059 TARGET="_top"
8060 >smbd</A
8061 > will change the file
8062                 timestamp as DOS requires.</P
8063 ><P
8064 >Default: <B
8065 CLASS="COMMAND"
8066 >dos filetimes = no</B
8067 ></P
8068 ></DD
8069 ><DT
8070 ><A
8071 NAME="ENCRYPTPASSWORDS"
8072 ></A
8073 >encrypt passwords (G)</DT
8074 ><DD
8075 ><P
8076 >This boolean controls whether encrypted passwords
8077                 will be negotiated with the client. Note that Windows NT 4.0 SP3 and
8078                 above and also Windows 98 will by default expect encrypted passwords
8079                 unless a registry entry is changed. To use encrypted passwords in
8080                 Samba see the file ENCRYPTION.txt in the Samba documentation
8081                 directory <TT
8082 CLASS="FILENAME"
8083 >docs/</TT
8084 > shipped with the source code.</P
8085 ><P
8086 >In order for encrypted passwords to work correctly
8087                 <A
8088 HREF="smbd.8.html"
8089 TARGET="_top"
8090 ><B
8091 CLASS="COMMAND"
8092 >smbd(8)</B
8093 ></A
8094 > must either
8095                 have access to a local <A
8096 HREF="smbpasswd.5.html"
8097 TARGET="_top"
8098 ><TT
8099 CLASS="FILENAME"
8100 >smbpasswd(5)
8101                 </TT
8102 ></A
8103 > file (see the <A
8104 HREF="smbpasswd.8.html"
8105 TARGET="_top"
8106 ><B
8107 CLASS="COMMAND"
8108 >               smbpasswd(8)</B
8109 ></A
8110 > program for information on how to set up
8111                 and maintain this file), or set the <A
8112 HREF="#SECURITY"
8113 >security = [server|domain]</A
8114 > parameter which
8115                 causes <B
8116 CLASS="COMMAND"
8117 >smbd</B
8118 > to authenticate against another
8119                 server.</P
8120 ><P
8121 >Default: <B
8122 CLASS="COMMAND"
8123 >encrypt passwords = no</B
8124 ></P
8125 ></DD
8126 ><DT
8127 ><A
8128 NAME="ENHANCEDBROWSING"
8129 ></A
8130 >enhanced browsing (G)</DT
8131 ><DD
8132 ><P
8133 >This option enables a couple of enhancements to
8134                 cross-subnet browse propagation that have been added in Samba
8135                 but which are not standard in Microsoft implementations.
8136                 </P
8137 ><P
8138 >The first enhancement to browse propagation consists of a regular
8139                 wildcard query to a Samba WINS server for all Domain Master Browsers,
8140                 followed by a browse synchronization with each of the returned
8141                 DMBs. The second enhancement consists of a regular randomised browse
8142                 synchronization with all currently known DMBs.</P
8143 ><P
8144 >You may wish to disable this option if you have a problem with empty
8145                 workgroups not disappearing from browse lists. Due to the restrictions
8146                 of the browse protocols these enhancements can cause a empty workgroup
8147                 to stay around forever which can be annoying.</P
8148 ><P
8149 >In general you should leave this option enabled as it makes
8150                 cross-subnet browse propagation much more reliable.</P
8151 ><P
8152 >Default: <B
8153 CLASS="COMMAND"
8154 >enhanced browsing = yes</B
8155 ></P
8156 ></DD
8157 ><DT
8158 ><A
8159 NAME="ENUMPORTSCOMMAND"
8160 ></A
8161 >enumports command (G)</DT
8162 ><DD
8163 ><P
8164 >The concept of a "port" is fairly foreign
8165                 to UNIX hosts.  Under Windows NT/2000 print servers, a port
8166                 is associated with a port monitor and generally takes the form of
8167                 a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
8168                 (i.e. LPD Port Monitor, etc...).  By default, Samba has only one
8169                 port defined--<TT
8170 CLASS="CONSTANT"
8171 >"Samba Printer Port"</TT
8172 >.  Under
8173                 Windows NT/2000, all printers must have a valid port name.
8174                 If you wish to have a list of ports displayed (<B
8175 CLASS="COMMAND"
8176 >smbd
8177                 </B
8178 > does not use a port name for anything) other than
8179                 the default <TT
8180 CLASS="CONSTANT"
8181 >"Samba Printer Port"</TT
8182 >, you
8183                 can define <TT
8184 CLASS="PARAMETER"
8185 ><I
8186 >enumports command</I
8187 ></TT
8188 > to point to
8189                 a program which should generate a list of ports, one per line,
8190                 to standard output.  This listing will then be used in response
8191                 to the level 1 and 2 EnumPorts() RPC.</P
8192 ><P
8193 >Default: <EM
8194 >no enumports command</EM
8195 ></P
8196 ><P
8197 >Example: <B
8198 CLASS="COMMAND"
8199 >enumports command = /usr/bin/listports
8200                 </B
8201 ></P
8202 ></DD
8203 ><DT
8204 ><A
8205 NAME="EXEC"
8206 ></A
8207 >exec (S)</DT
8208 ><DD
8209 ><P
8210 >This is a synonym for <A
8211 HREF="#PREEXEC"
8212 >               <TT
8213 CLASS="PARAMETER"
8214 ><I
8215 >preexec</I
8216 ></TT
8217 ></A
8218 >.</P
8219 ></DD
8220 ><DT
8221 ><A
8222 NAME="FAKEDIRECTORYCREATETIMES"
8223 ></A
8224 >fake directory create times (S)</DT
8225 ><DD
8226 ><P
8227 >NTFS and Windows VFAT file systems keep a create
8228                 time for all files and directories. This is not the same as the
8229                 ctime - status change time - that Unix keeps, so Samba by default
8230                 reports the earliest of the various times Unix does keep. Setting
8231                 this parameter for a share causes Samba to always report midnight
8232                 1-1-1980 as the create time for directories.</P
8233 ><P
8234 >This option is mainly used as a compatibility option for
8235                 Visual C++ when used against Samba shares. Visual C++ generated
8236                 makefiles have the object directory as a dependency for each object
8237                 file, and a make rule to create the directory. Also, when NMAKE
8238                 compares timestamps it uses the creation time when examining a
8239                 directory. Thus the object directory will be created if it does not
8240                 exist, but once it does exist it will always have an earlier
8241                 timestamp than the object files it contains.</P
8242 ><P
8243 >However, Unix time semantics mean that the create time
8244                 reported by Samba will be updated whenever a file is created or
8245                 or deleted in the directory.  NMAKE finds all object files in
8246                 the object directory.  The timestamp of the last one built is then
8247                 compared to the timestamp of the object directory.  If the
8248                 directory's timestamp if newer, then all object files
8249                 will be rebuilt.  Enabling this option
8250                 ensures directories always predate their contents and an NMAKE build
8251                 will proceed as expected.</P
8252 ><P
8253 >Default: <B
8254 CLASS="COMMAND"
8255 >fake directory create times = no</B
8256 ></P
8257 ></DD
8258 ><DT
8259 ><A
8260 NAME="FAKEOPLOCKS"
8261 ></A
8262 >fake oplocks (S)</DT
8263 ><DD
8264 ><P
8265 >Oplocks are the way that SMB clients get permission
8266                 from a server to locally cache file operations. If a server grants
8267                 an oplock (opportunistic lock) then the client is free to assume
8268                 that it is the only one accessing the file and it will aggressively
8269                 cache file data. With some oplock types the client may even cache
8270                 file open/close operations. This can give enormous performance benefits.
8271                 </P
8272 ><P
8273 >When you set <B
8274 CLASS="COMMAND"
8275 >fake oplocks = yes</B
8276 >, <A
8277 HREF="smbd.8.html"
8278 TARGET="_top"
8279 ><B
8280 CLASS="COMMAND"
8281 >smbd(8)</B
8282 ></A
8283 > will
8284                 always grant oplock requests no matter how many clients are using
8285                 the file.</P
8286 ><P
8287 >It is generally much better to use the real <A
8288 HREF="#OPLOCKS"
8289 ><TT
8290 CLASS="PARAMETER"
8291 ><I
8292 >oplocks</I
8293 ></TT
8294 ></A
8295 > support rather
8296                 than this parameter.</P
8297 ><P
8298 >If you enable this option on all read-only shares or
8299                 shares that you know will only be accessed from one client at a
8300                 time such as physically read-only media like CDROMs, you will see
8301                 a big performance improvement on many operations. If you enable
8302                 this option on shares where multiple clients may be accessing the
8303                 files read-write at the same time you can get data corruption. Use
8304                 this option carefully!</P
8305 ><P
8306 >Default: <B
8307 CLASS="COMMAND"
8308 >fake oplocks = no</B
8309 ></P
8310 ></DD
8311 ><DT
8312 ><A
8313 NAME="FOLLOWSYMLINKS"
8314 ></A
8315 >follow symlinks (S)</DT
8316 ><DD
8317 ><P
8318 >This parameter allows the Samba administrator
8319                 to stop <A
8320 HREF="smbd.8.html"
8321 TARGET="_top"
8322 ><B
8323 CLASS="COMMAND"
8324 >smbd(8)</B
8325 ></A
8326 >
8327                 from following symbolic links in a particular share. Setting this
8328                 parameter to <TT
8329 CLASS="CONSTANT"
8330 >no</TT
8331 > prevents any file or directory
8332                 that is a symbolic link from being followed (the user will get an
8333                 error).  This option is very useful to stop users from adding a
8334                 symbolic link to <TT
8335 CLASS="FILENAME"
8336 >/etc/passwd</TT
8337 > in their home
8338                 directory for instance.  However it will slow filename lookups
8339                 down slightly.</P
8340 ><P
8341 >This option is enabled (i.e. <B
8342 CLASS="COMMAND"
8343 >smbd</B
8344 > will
8345                 follow symbolic links) by default.</P
8346 ><P
8347 >Default: <B
8348 CLASS="COMMAND"
8349 >follow symlinks = yes</B
8350 ></P
8351 ></DD
8352 ><DT
8353 ><A
8354 NAME="FORCECREATEMODE"
8355 ></A
8356 >force create mode (S)</DT
8357 ><DD
8358 ><P
8359 >This parameter specifies a set of UNIX mode bit
8360                 permissions that will <EM
8361 >always</EM
8362 > be set on a
8363                 file created by Samba. This is done by bitwise 'OR'ing these bits onto
8364                 the mode bits of a file that is being created or having its
8365                 permissions changed. The default for this parameter is (in octal)
8366                 000. The modes in this parameter are bitwise 'OR'ed onto the file
8367                 mode after the mask set in the <TT
8368 CLASS="PARAMETER"
8369 ><I
8370 >create mask</I
8371 ></TT
8372 >
8373                 parameter is applied.</P
8374 ><P
8375 >See also the parameter <A
8376 HREF="#CREATEMASK"
8377 ><TT
8378 CLASS="PARAMETER"
8379 ><I
8380 >create
8381                 mask</I
8382 ></TT
8383 ></A
8384 > for details on masking mode bits on files.</P
8385 ><P
8386 >See also the <A
8387 HREF="#INHERITPERMISSIONS"
8388 ><TT
8389 CLASS="PARAMETER"
8390 ><I
8391 >inherit
8392                 permissions</I
8393 ></TT
8394 ></A
8395 > parameter.</P
8396 ><P
8397 >Default: <B
8398 CLASS="COMMAND"
8399 >force create mode = 000</B
8400 ></P
8401 ><P
8402 >Example: <B
8403 CLASS="COMMAND"
8404 >force create mode = 0755</B
8405 ></P
8406 ><P
8407 >would force all created files to have read and execute
8408                 permissions set for 'group' and 'other' as well as the
8409                 read/write/execute bits set for the 'user'.</P
8410 ></DD
8411 ><DT
8412 ><A
8413 NAME="FORCEDIRECTORYMODE"
8414 ></A
8415 >force directory mode (S)</DT
8416 ><DD
8417 ><P
8418 >This parameter specifies a set of UNIX mode bit
8419                 permissions that will <EM
8420 >always</EM
8421 > be set on a directory
8422                 created by Samba. This is done by bitwise 'OR'ing these bits onto the
8423                 mode bits of a directory that is being created. The default for this
8424                 parameter is (in octal) 0000 which will not add any extra permission
8425                 bits to a created directory. This operation is done after the mode
8426                 mask in the parameter <TT
8427 CLASS="PARAMETER"
8428 ><I
8429 >directory mask</I
8430 ></TT
8431 > is
8432                 applied.</P
8433 ><P
8434 >See also the parameter <A
8435 HREF="#DIRECTORYMASK"
8436 ><TT
8437 CLASS="PARAMETER"
8438 ><I
8439 >               directory mask</I
8440 ></TT
8441 ></A
8442 > for details on masking mode bits
8443                 on created directories.</P
8444 ><P
8445 >See also the <A
8446 HREF="#INHERITPERMISSIONS"
8447 ><TT
8448 CLASS="PARAMETER"
8449 ><I
8450 >               inherit permissions</I
8451 ></TT
8452 ></A
8453 > parameter.</P
8454 ><P
8455 >Default: <B
8456 CLASS="COMMAND"
8457 >force directory mode = 000</B
8458 ></P
8459 ><P
8460 >Example: <B
8461 CLASS="COMMAND"
8462 >force directory mode = 0755</B
8463 ></P
8464 ><P
8465 >would force all created directories to have read and execute
8466                 permissions set for 'group' and 'other' as well as the
8467                 read/write/execute bits set for the 'user'.</P
8468 ></DD
8469 ><DT
8470 ><A
8471 NAME="FORCEDIRECTORYSECURITYMODE"
8472 ></A
8473 >force directory
8474                 security mode (S)</DT
8475 ><DD
8476 ><P
8477 >This parameter controls what UNIX permission bits
8478                 can be modified when a Windows NT client is manipulating the UNIX
8479                 permission on a directory using the native NT security dialog box.</P
8480 ><P
8481 >This parameter is applied as a mask (OR'ed with) to the
8482                 changed permission bits, thus forcing any bits in this mask that
8483                 the user may have modified to be on. Essentially, one bits in this
8484                 mask may be treated as a set of bits that, when modifying security
8485                 on a directory, the user has always set to be 'on'.</P
8486 ><P
8487 >If not set explicitly this parameter is 000, which
8488                 allows a user to modify all the user/group/world permissions on a
8489                 directory without restrictions.</P
8490 ><P
8491 ><EM
8492 >Note</EM
8493 > that users who can access the
8494                 Samba server through other means can easily bypass this restriction,
8495                 so it is primarily useful for standalone "appliance" systems.
8496                 Administrators of most normal systems will probably want to leave
8497                 it set as 0000.</P
8498 ><P
8499 >See also the <A
8500 HREF="#DIRECTORYSECURITYMASK"
8501 ><TT
8502 CLASS="PARAMETER"
8503 ><I
8504 >               directory security mask</I
8505 ></TT
8506 ></A
8507 >, <A
8508 HREF="#SECURITYMASK"
8509 >               <TT
8510 CLASS="PARAMETER"
8511 ><I
8512 >security mask</I
8513 ></TT
8514 ></A
8515 >,
8516                 <A
8517 HREF="#FORCESECURITYMODE"
8518 ><TT
8519 CLASS="PARAMETER"
8520 ><I
8521 >force security mode
8522                 </I
8523 ></TT
8524 ></A
8525 > parameters.</P
8526 ><P
8527 >Default: <B
8528 CLASS="COMMAND"
8529 >force directory security mode = 0</B
8530 ></P
8531 ><P
8532 >Example: <B
8533 CLASS="COMMAND"
8534 >force directory security mode = 700</B
8535 ></P
8536 ></DD
8537 ><DT
8538 ><A
8539 NAME="FORCEGROUP"
8540 ></A
8541 >force group (S)</DT
8542 ><DD
8543 ><P
8544 >This specifies a UNIX group name that will be
8545                 assigned as the default primary group for all users connecting
8546                 to this service. This is useful for sharing files by ensuring
8547                 that all access to files on service will use the named group for
8548                 their permissions checking. Thus, by assigning permissions for this
8549                 group to the files and directories within this service the Samba
8550                 administrator can restrict or allow sharing of these files.</P
8551 ><P
8552 >In Samba 2.0.5 and above this parameter has extended
8553                 functionality in the following way. If the group name listed here
8554                 has a '+' character prepended to it then the current user accessing
8555                 the share only has the primary group default assigned to this group
8556                 if they are already assigned as a member of that group. This allows
8557                 an administrator to decide that only users who are already in a
8558                 particular group will create files with group ownership set to that
8559                 group. This gives a finer granularity of ownership assignment. For
8560                 example, the setting <TT
8561 CLASS="FILENAME"
8562 >force group = +sys</TT
8563 > means
8564                 that only users who are already in group sys will have their default
8565                 primary group assigned to sys when accessing this Samba share. All
8566                 other users will retain their ordinary primary group.</P
8567 ><P
8568 >If the <A
8569 HREF="#FORCEUSER"
8570 ><TT
8571 CLASS="PARAMETER"
8572 ><I
8573 >force user
8574                 </I
8575 ></TT
8576 ></A
8577 > parameter is also set the group specified in
8578                 <TT
8579 CLASS="PARAMETER"
8580 ><I
8581 >force group</I
8582 ></TT
8583 > will override the primary group
8584                 set in <TT
8585 CLASS="PARAMETER"
8586 ><I
8587 >force user</I
8588 ></TT
8589 >.</P
8590 ><P
8591 >See also <A
8592 HREF="#FORCEUSER"
8593 ><TT
8594 CLASS="PARAMETER"
8595 ><I
8596 >force
8597                 user</I
8598 ></TT
8599 ></A
8600 >.</P
8601 ><P
8602 >Default: <EM
8603 >no forced group</EM
8604 ></P
8605 ><P
8606 >Example: <B
8607 CLASS="COMMAND"
8608 >force group = agroup</B
8609 ></P
8610 ></DD
8611 ><DT
8612 ><A
8613 NAME="FORCESECURITYMODE"
8614 ></A
8615 >force security mode (S)</DT
8616 ><DD
8617 ><P
8618 >This parameter controls what UNIX permission
8619                 bits can be modified when a Windows NT client is manipulating
8620                 the UNIX permission on a file using the native NT security dialog
8621                 box.</P
8622 ><P
8623 >This parameter is applied as a mask (OR'ed with) to the
8624                 changed permission bits, thus forcing any bits in this mask that
8625                 the user may have modified to be on. Essentially, one bits in this
8626                 mask may be treated as a set of bits that, when modifying security
8627                 on a file, the user has always set to be 'on'.</P
8628 ><P
8629 >If not set explicitly this parameter is set to 0,
8630                 and allows a user to modify all the user/group/world permissions on a file,
8631                 with no restrictions.</P
8632 ><P
8633 ><EM
8634 >Note</EM
8635 > that users who can access
8636                 the Samba server through other means can easily bypass this restriction,
8637                 so it is primarily useful for standalone "appliance" systems.
8638                 Administrators of most normal systems will probably want to leave
8639                 this set to 0000.</P
8640 ><P
8641 >See also the <A
8642 HREF="#FORCEDIRECTORYSECURITYMODE"
8643 ><TT
8644 CLASS="PARAMETER"
8645 ><I
8646 >               force directory security mode</I
8647 ></TT
8648 ></A
8649 >,
8650                 <A
8651 HREF="#DIRECTORYSECURITYMASK"
8652 ><TT
8653 CLASS="PARAMETER"
8654 ><I
8655 >directory security
8656                 mask</I
8657 ></TT
8658 ></A
8659 >, <A
8660 HREF="#SECURITYMASK"
8661 ><TT
8662 CLASS="PARAMETER"
8663 ><I
8664 >               security mask</I
8665 ></TT
8666 ></A
8667 > parameters.</P
8668 ><P
8669 >Default: <B
8670 CLASS="COMMAND"
8671 >force security mode = 0</B
8672 ></P
8673 ><P
8674 >Example: <B
8675 CLASS="COMMAND"
8676 >force security mode = 700</B
8677 ></P
8678 ></DD
8679 ><DT
8680 ><A
8681 NAME="FORCEUNKNOWNACLUSER"
8682 ></A
8683 >force unknown acl user (S)</DT
8684 ><DD
8685 ><P
8686 >If this parameter is set, a Windows NT ACL that contains
8687                 an unknown SID (security descriptor, or representation of a user or group id)
8688                 as the owner or group owner of the file will be silently mapped into the
8689                 current UNIX uid or gid of the currently connected user.</P
8690 ><P
8691 >This is designed to allow Windows NT clients to copy files and
8692                 folders containing ACLs that were created locally on the client machine
8693                 and contain users local to that machine only (no domain users) to be
8694                 copied to a Samba server (usually with XCOPY /O) and have the unknown
8695                 userid and groupid of the file owner map to the current connected user.
8696                 This can only be fixed correctly when winbindd allows arbitrary mapping
8697                 from any Windows NT SID to a UNIX uid or gid.</P
8698 ><P
8699 >Try using this parameter when XCOPY /O gives an ACCESS_DENIED error.
8700                 </P
8701 ><P
8702 >See also <A
8703 HREF="#FORCEGROUP"
8704 ><TT
8705 CLASS="PARAMETER"
8706 ><I
8707 >force group
8708                 </I
8709 ></TT
8710 ></A
8711 ></P
8712 ><P
8713 >Default: <EM
8714 >False</EM
8715 ></P
8716 ><P
8717 >Example: <B
8718 CLASS="COMMAND"
8719 >force unknown acl user = yes</B
8720 ></P
8721 ></DD
8722 ><DT
8723 ><A
8724 NAME="FORCEUSER"
8725 ></A
8726 >force user (S)</DT
8727 ><DD
8728 ><P
8729 >This specifies a UNIX user name that will be
8730                 assigned as the default user for all users connecting to this service.
8731                 This is useful for sharing files. You should also use it carefully
8732                 as using it incorrectly can cause security problems.</P
8733 ><P
8734 >This user name only gets used once a connection is established.
8735                 Thus clients still need to connect as a valid user and supply a
8736                 valid password. Once connected, all file operations will be performed
8737                 as the "forced user", no matter what username the client connected
8738                 as.  This can be very useful.</P
8739 ><P
8740 >In Samba 2.0.5 and above this parameter also causes the
8741                 primary group of the forced user to be used as the primary group
8742                 for all file activity. Prior to 2.0.5 the primary group was left
8743                 as the primary group of the connecting user (this was a bug).</P
8744 ><P
8745 >See also <A
8746 HREF="#FORCEGROUP"
8747 ><TT
8748 CLASS="PARAMETER"
8749 ><I
8750 >force group
8751                 </I
8752 ></TT
8753 ></A
8754 ></P
8755 ><P
8756 >Default: <EM
8757 >no forced user</EM
8758 ></P
8759 ><P
8760 >Example: <B
8761 CLASS="COMMAND"
8762 >force user = auser</B
8763 ></P
8764 ></DD
8765 ><DT
8766 ><A
8767 NAME="FSTYPE"
8768 ></A
8769 >fstype (S)</DT
8770 ><DD
8771 ><P
8772 >This parameter allows the administrator to
8773                 configure the string that specifies the type of filesystem a share
8774                 is using that is reported by <A
8775 HREF="smbd.8.html"
8776 TARGET="_top"
8777 ><B
8778 CLASS="COMMAND"
8779 >smbd(8)
8780                 </B
8781 ></A
8782 > when a client queries the filesystem type
8783                 for a share. The default type is <TT
8784 CLASS="CONSTANT"
8785 >NTFS</TT
8786 > for
8787                 compatibility with Windows NT but this can be changed to other
8788                 strings such as <TT
8789 CLASS="CONSTANT"
8790 >Samba</TT
8791 > or <TT
8792 CLASS="CONSTANT"
8793 >FAT
8794                 </TT
8795 > if required.</P
8796 ><P
8797 >Default: <B
8798 CLASS="COMMAND"
8799 >fstype = NTFS</B
8800 ></P
8801 ><P
8802 >Example: <B
8803 CLASS="COMMAND"
8804 >fstype = Samba</B
8805 ></P
8806 ></DD
8807 ><DT
8808 ><A
8809 NAME="GETWDCACHE"
8810 ></A
8811 >getwd cache (G)</DT
8812 ><DD
8813 ><P
8814 >This is a tuning option. When this is enabled a
8815                 caching algorithm will be used to reduce the time taken for getwd()
8816                 calls. This can have a significant impact on performance, especially
8817                 when the <A
8818 HREF="#WIDELINKS"
8819 ><TT
8820 CLASS="PARAMETER"
8821 ><I
8822 >wide links</I
8823 ></TT
8824 >
8825                 </A
8826 >parameter is set to <TT
8827 CLASS="CONSTANT"
8828 >no</TT
8829 >.</P
8830 ><P
8831 >Default: <B
8832 CLASS="COMMAND"
8833 >getwd cache = yes</B
8834 ></P
8835 ></DD
8836 ><DT
8837 ><A
8838 NAME="GROUP"
8839 ></A
8840 >group (S)</DT
8841 ><DD
8842 ><P
8843 >Synonym for <A
8844 HREF="#FORCEGROUP"
8845 ><TT
8846 CLASS="PARAMETER"
8847 ><I
8848 >force
8849                 group</I
8850 ></TT
8851 ></A
8852 >.</P
8853 ></DD
8854 ><DT
8855 ><A
8856 NAME="GUESTACCOUNT"
8857 ></A
8858 >guest account (S)</DT
8859 ><DD
8860 ><P
8861 >This is a username which will be used for access
8862                 to services which are specified as <A
8863 HREF="#GUESTOK"
8864 ><TT
8865 CLASS="PARAMETER"
8866 ><I
8867 >               guest ok</I
8868 ></TT
8869 ></A
8870 > (see below). Whatever privileges this
8871                 user has will be available to any client connecting to the guest service.
8872                 Typically this user will exist in the password file, but will not
8873                 have a valid login. The user account "ftp" is often a good choice
8874                 for this parameter. If a username is specified in a given service,
8875                 the specified username overrides this one.</P
8876 ><P
8877 >One some systems the default guest account "nobody" may not
8878                 be able to print. Use another account in this case. You should test
8879                 this by trying to log in as your guest user (perhaps by using the
8880                 <B
8881 CLASS="COMMAND"
8882 >su -</B
8883 > command) and trying to print using the
8884                 system print command such as <B
8885 CLASS="COMMAND"
8886 >lpr(1)</B
8887 > or <B
8888 CLASS="COMMAND"
8889 >               lp(1)</B
8890 >.</P
8891 ><P
8892 >Default: <EM
8893 >specified at compile time, usually
8894                 "nobody"</EM
8895 ></P
8896 ><P
8897 >Example: <B
8898 CLASS="COMMAND"
8899 >guest account = ftp</B
8900 ></P
8901 ></DD
8902 ><DT
8903 ><A
8904 NAME="GUESTOK"
8905 ></A
8906 >guest ok (S)</DT
8907 ><DD
8908 ><P
8909 >If this parameter is <TT
8910 CLASS="CONSTANT"
8911 >yes</TT
8912 > for
8913                 a service, then no password is required to connect to the service.
8914                 Privileges will be those of the <A
8915 HREF="#GUESTACCOUNT"
8916 ><TT
8917 CLASS="PARAMETER"
8918 ><I
8919 >               guest account</I
8920 ></TT
8921 ></A
8922 >.</P
8923 ><P
8924 >See the section below on <A
8925 HREF="#SECURITY"
8926 ><TT
8927 CLASS="PARAMETER"
8928 ><I
8929 >               security</I
8930 ></TT
8931 ></A
8932 > for more information about this option.
8933                 </P
8934 ><P
8935 >Default: <B
8936 CLASS="COMMAND"
8937 >guest ok = no</B
8938 ></P
8939 ></DD
8940 ><DT
8941 ><A
8942 NAME="GUESTONLY"
8943 ></A
8944 >guest only (S)</DT
8945 ><DD
8946 ><P
8947 >If this parameter is <TT
8948 CLASS="CONSTANT"
8949 >yes</TT
8950 > for
8951                 a service, then only guest connections to the service are permitted.
8952                 This parameter will have no effect if <A
8953 HREF="#GUESTOK"
8954 >               <TT
8955 CLASS="PARAMETER"
8956 ><I
8957 >guest ok</I
8958 ></TT
8959 ></A
8960 > is not set for the service.</P
8961 ><P
8962 >See the section below on <A
8963 HREF="#SECURITY"
8964 ><TT
8965 CLASS="PARAMETER"
8966 ><I
8967 >               security</I
8968 ></TT
8969 ></A
8970 > for more information about this option.
8971                 </P
8972 ><P
8973 >Default: <B
8974 CLASS="COMMAND"
8975 >guest only = no</B
8976 ></P
8977 ></DD
8978 ><DT
8979 ><A
8980 NAME="HIDEDOTFILES"
8981 ></A
8982 >hide dot files (S)</DT
8983 ><DD
8984 ><P
8985 >This is a boolean parameter that controls whether
8986                 files starting with a dot appear as hidden files.</P
8987 ><P
8988 >Default: <B
8989 CLASS="COMMAND"
8990 >hide dot files = yes</B
8991 ></P
8992 ></DD
8993 ><DT
8994 ><A
8995 NAME="HIDEFILES"
8996 ></A
8997 >hide files(S)</DT
8998 ><DD
8999 ><P
9000 >This is a list of files or directories that are not
9001                 visible but are accessible.  The DOS 'hidden' attribute is applied
9002                 to any files or directories that match.</P
9003 ><P
9004 >Each entry in the list must be separated by a '/',
9005                 which allows spaces to be included in the entry.  '*'
9006                 and '?' can be used to specify multiple files or directories
9007                 as in DOS wildcards.</P
9008 ><P
9009 >Each entry must be a Unix path, not a DOS path and must
9010                 not include the Unix directory separator '/'.</P
9011 ><P
9012 >Note that the case sensitivity option is applicable
9013                 in hiding files.</P
9014 ><P
9015 >Setting this parameter will affect the performance of Samba,
9016                 as it will be forced to check all files and directories for a match
9017                 as they are scanned.</P
9018 ><P
9019 >See also <A
9020 HREF="#HIDEDOTFILES"
9021 ><TT
9022 CLASS="PARAMETER"
9023 ><I
9024 >hide
9025                 dot files</I
9026 ></TT
9027 ></A
9028 >, <A
9029 HREF="#VETOFILES"
9030 ><TT
9031 CLASS="PARAMETER"
9032 ><I
9033 >               veto files</I
9034 ></TT
9035 ></A
9036 > and <A
9037 HREF="#CASESENSITIVE"
9038 >               <TT
9039 CLASS="PARAMETER"
9040 ><I
9041 >case sensitive</I
9042 ></TT
9043 ></A
9044 >.</P
9045 ><P
9046 >Default: <EM
9047 >no file are hidden</EM
9048 ></P
9049 ><P
9050 >Example: <B
9051 CLASS="COMMAND"
9052 >hide files =
9053                 /.*/DesktopFolderDB/TrashFor%m/resource.frk/</B
9054 ></P
9055 ><P
9056 >The above example is based on files that the Macintosh
9057                 SMB client (DAVE) available from <A
9058 HREF="http://www.thursby.com"
9059 TARGET="_top"
9060 >
9061                 Thursby</A
9062 > creates for internal use, and also still hides
9063                 all files beginning with a dot.</P
9064 ></DD
9065 ><DT
9066 ><A
9067 NAME="HIDELOCALUSERS"
9068 ></A
9069 >hide local users(G)</DT
9070 ><DD
9071 ><P
9072 >This parameter toggles the hiding of local UNIX
9073                 users (root, wheel, floppy, etc) from remote clients.</P
9074 ><P
9075 >Default: <B
9076 CLASS="COMMAND"
9077 >hide local users = no</B
9078 ></P
9079 ></DD
9080 ><DT
9081 ><A
9082 NAME="HIDEUNREADABLE"
9083 ></A
9084 >hide unreadable (S)</DT
9085 ><DD
9086 ><P
9087 >This parameter prevents clients from seeing the
9088                 existance of files that cannot be read. Defaults to off.</P
9089 ><P
9090 >Default: <B
9091 CLASS="COMMAND"
9092 >hide unreadable = no</B
9093 ></P
9094 ></DD
9095 ><DT
9096 ><A
9097 NAME="HOMEDIRMAP"
9098 ></A
9099 >homedir map (G)</DT
9100 ><DD
9101 ><P
9102 >If<A
9103 HREF="#NISHOMEDIR"
9104 ><TT
9105 CLASS="PARAMETER"
9106 ><I
9107 >nis homedir
9108                 </I
9109 ></TT
9110 ></A
9111 > is <TT
9112 CLASS="CONSTANT"
9113 >yes</TT
9114 >, and <A
9115 HREF="smbd.8.html"
9116 TARGET="_top"
9117 ><B
9118 CLASS="COMMAND"
9119 >smbd(8)</B
9120 ></A
9121 > is also acting
9122                 as a Win95/98 <TT
9123 CLASS="PARAMETER"
9124 ><I
9125 >logon server</I
9126 ></TT
9127 > then this parameter
9128                 specifies the NIS (or YP) map from which the server for the user's
9129                 home directory should be extracted.  At present, only the Sun
9130                 auto.home map format is understood. The form of the map is:</P
9131 ><P
9132 ><B
9133 CLASS="COMMAND"
9134 >username       server:/some/file/system</B
9135 ></P
9136 ><P
9137 >and the program will extract the servername from before
9138                 the first ':'.  There should probably be a better parsing system
9139                 that copes with different map formats and also Amd (another
9140                 automounter) maps.</P
9141 ><P
9142 ><EM
9143 >NOTE :</EM
9144 >A working NIS client is required on
9145                 the system for this option to work.</P
9146 ><P
9147 >See also <A
9148 HREF="#NISHOMEDIR"
9149 ><TT
9150 CLASS="PARAMETER"
9151 ><I
9152 >nis homedir</I
9153 ></TT
9154 >
9155                 </A
9156 >, <A
9157 HREF="#DOMAINLOGONS"
9158 ><TT
9159 CLASS="PARAMETER"
9160 ><I
9161 >domain logons</I
9162 ></TT
9163 >
9164                 </A
9165 >.</P
9166 ><P
9167 >Default: <B
9168 CLASS="COMMAND"
9169 >homedir map = &#60;empty string&#62;</B
9170 ></P
9171 ><P
9172 >Example: <B
9173 CLASS="COMMAND"
9174 >homedir map = amd.homedir</B
9175 ></P
9176 ></DD
9177 ><DT
9178 ><A
9179 NAME="HOSTMSDFS"
9180 ></A
9181 >host msdfs (G)</DT
9182 ><DD
9183 ><P
9184 >This boolean parameter is only available
9185                 if Samba has been configured and compiled with the <B
9186 CLASS="COMMAND"
9187 >               --with-msdfs</B
9188 > option. If set to <TT
9189 CLASS="CONSTANT"
9190 >yes</TT
9191 >,
9192                 Samba will act as a Dfs server, and  allow Dfs-aware clients
9193                 to browse Dfs trees hosted on the server.</P
9194 ><P
9195 >See also the <A
9196 HREF="#MSDFSROOT"
9197 ><TT
9198 CLASS="PARAMETER"
9199 ><I
9200 >               msdfs root</I
9201 ></TT
9202 ></A
9203 > share  level  parameter.  For
9204                 more  information  on  setting  up a Dfs tree on Samba,
9205                 refer to <A
9206 HREF="msdfs_setup.html"
9207 TARGET="_top"
9208 >msdfs_setup.html</A
9209 >.
9210                 </P
9211 ><P
9212 >Default: <B
9213 CLASS="COMMAND"
9214 >host msdfs = no</B
9215 ></P
9216 ></DD
9217 ><DT
9218 ><A
9219 NAME="HOSTSALLOW"
9220 ></A
9221 >hosts allow (S)</DT
9222 ><DD
9223 ><P
9224 >A synonym for this parameter is <TT
9225 CLASS="PARAMETER"
9226 ><I
9227 >allow
9228                 hosts</I
9229 ></TT
9230 >.</P
9231 ><P
9232 >This parameter is a comma, space, or tab delimited
9233                 set of hosts which are permitted to access a service.</P
9234 ><P
9235 >If specified in the [global] section then it will
9236                 apply to all services, regardless of whether the individual
9237                 service has a different setting.</P
9238 ><P
9239 >You can specify the hosts by name or IP number. For
9240                 example, you could restrict access to only the hosts on a
9241                 Class C subnet with something like <B
9242 CLASS="COMMAND"
9243 >allow hosts = 150.203.5.
9244                 </B
9245 >. The full syntax of the list is described in the man
9246                 page <TT
9247 CLASS="FILENAME"
9248 >hosts_access(5)</TT
9249 >. Note that this man
9250                 page may not be present on your system, so a brief description will
9251                 be given here also.</P
9252 ><P
9253 >Note that the localhost address 127.0.0.1 will always
9254                 be allowed access unless specifically denied by a <A
9255 HREF="#HOSTSDENY"
9256 ><TT
9257 CLASS="PARAMETER"
9258 ><I
9259 >hosts deny</I
9260 ></TT
9261 ></A
9262 > option.</P
9263 ><P
9264 >You can also specify hosts by network/netmask pairs and
9265                 by netgroup names if your system supports netgroups. The
9266                 <EM
9267 >EXCEPT</EM
9268 > keyword can also be used to limit a
9269                 wildcard list. The following examples may provide some help:</P
9270 ><P
9271 >Example 1: allow all IPs in 150.203.*.*; except one</P
9272 ><P
9273 ><B
9274 CLASS="COMMAND"
9275 >hosts allow = 150.203. EXCEPT 150.203.6.66</B
9276 ></P
9277 ><P
9278 >Example 2: allow hosts that match the given network/netmask</P
9279 ><P
9280 ><B
9281 CLASS="COMMAND"
9282 >hosts allow = 150.203.15.0/255.255.255.0</B
9283 ></P
9284 ><P
9285 >Example 3: allow a couple of hosts</P
9286 ><P
9287 ><B
9288 CLASS="COMMAND"
9289 >hosts allow = lapland, arvidsjaur</B
9290 ></P
9291 ><P
9292 >Example 4: allow only hosts in NIS netgroup "foonet", but
9293                 deny access from one particular host</P
9294 ><P
9295 ><B
9296 CLASS="COMMAND"
9297 >hosts allow = @foonet</B
9298 ></P
9299 ><P
9300 ><B
9301 CLASS="COMMAND"
9302 >hosts deny = pirate</B
9303 ></P
9304 ><P
9305 >Note that access still requires suitable user-level passwords.</P
9306 ><P
9307 >See <A
9308 HREF="testparm.1.html"
9309 TARGET="_top"
9310 ><B
9311 CLASS="COMMAND"
9312 >testparm(1)</B
9313 >
9314                 </A
9315 > for a way of testing your host access to see if it does
9316                 what you expect.</P
9317 ><P
9318 >Default: <EM
9319 >none (i.e., all hosts permitted access)
9320                 </EM
9321 ></P
9322 ><P
9323 >Example: <B
9324 CLASS="COMMAND"
9325 >allow hosts = 150.203.5. myhost.mynet.edu.au
9326                 </B
9327 ></P
9328 ></DD
9329 ><DT
9330 ><A
9331 NAME="HOSTSDENY"
9332 ></A
9333 >hosts deny (S)</DT
9334 ><DD
9335 ><P
9336 >The opposite of <TT
9337 CLASS="PARAMETER"
9338 ><I
9339 >hosts allow</I
9340 ></TT
9341 >
9342                 - hosts listed here are <EM
9343 >NOT</EM
9344 > permitted access to
9345                 services unless the specific services have their own lists to override
9346                 this one. Where the lists conflict, the <TT
9347 CLASS="PARAMETER"
9348 ><I
9349 >allow</I
9350 ></TT
9351 >
9352                 list takes precedence.</P
9353 ><P
9354 >Default: <EM
9355 >none (i.e., no hosts specifically excluded)
9356                 </EM
9357 ></P
9358 ><P
9359 >Example: <B
9360 CLASS="COMMAND"
9361 >hosts deny = 150.203.4. badhost.mynet.edu.au
9362                 </B
9363 ></P
9364 ></DD
9365 ><DT
9366 ><A
9367 NAME="HOSTSEQUIV"
9368 ></A
9369 >hosts equiv (G)</DT
9370 ><DD
9371 ><P
9372 >If this global parameter is a non-null string,
9373                 it specifies the name of a file to read for the names of hosts
9374                 and users who will be allowed access without specifying a password.
9375                 </P
9376 ><P
9377 >This is not be confused with <A
9378 HREF="#HOSTSALLOW"
9379 >               <TT
9380 CLASS="PARAMETER"
9381 ><I
9382 >hosts allow</I
9383 ></TT
9384 ></A
9385 > which is about hosts
9386                 access to services and is more useful for guest services. <TT
9387 CLASS="PARAMETER"
9388 ><I
9389 >               hosts equiv</I
9390 ></TT
9391 > may be useful for NT clients which will
9392                 not supply passwords to Samba.</P
9393 ><P
9394 ><EM
9395 >NOTE :</EM
9396 > The use of <TT
9397 CLASS="PARAMETER"
9398 ><I
9399 >hosts equiv
9400                 </I
9401 ></TT
9402 > can be a major security hole. This is because you are
9403                 trusting the PC to supply the correct username. It is very easy to
9404                 get a PC to supply a false username. I recommend that the
9405                 <TT
9406 CLASS="PARAMETER"
9407 ><I
9408 >hosts equiv</I
9409 ></TT
9410 > option be only used if you really
9411                 know what you are doing, or perhaps on a home network where you trust
9412                 your spouse and kids. And only if you <EM
9413 >really</EM
9414 > trust
9415                 them :-).</P
9416 ><P
9417 >Default: <EM
9418 >no host equivalences</EM
9419 ></P
9420 ><P
9421 >Example: <B
9422 CLASS="COMMAND"
9423 >hosts equiv = /etc/hosts.equiv</B
9424 ></P
9425 ></DD
9426 ><DT
9427 ><A
9428 NAME="INCLUDE"
9429 ></A
9430 >include (G)</DT
9431 ><DD
9432 ><P
9433 >This allows you to include one config file
9434                 inside another.  The file is included literally, as though typed
9435                 in place.</P
9436 ><P
9437 >It takes the standard substitutions, except <TT
9438 CLASS="PARAMETER"
9439 ><I
9440 >%u
9441                 </I
9442 ></TT
9443 >, <TT
9444 CLASS="PARAMETER"
9445 ><I
9446 >%P</I
9447 ></TT
9448 > and <TT
9449 CLASS="PARAMETER"
9450 ><I
9451 >%S</I
9452 ></TT
9453 >.
9454                 </P
9455 ><P
9456 >Default: <EM
9457 >no file included</EM
9458 ></P
9459 ><P
9460 >Example: <B
9461 CLASS="COMMAND"
9462 >include = /usr/local/samba/lib/admin_smb.conf
9463                 </B
9464 ></P
9465 ></DD
9466 ><DT
9467 ><A
9468 NAME="INHERITACLS"
9469 ></A
9470 >inherit acls (S)</DT
9471 ><DD
9472 ><P
9473 >This parameter can be used to ensure
9474                 that if default acls exist on parent directories,
9475                 they are always honored when creating a subdirectory.
9476                 The default behavior is to use the mode specified
9477                 when creating the directory.  Enabling this option
9478                 sets the mode to 0777, thus guaranteeing that
9479                 default directory acls are propagated.
9480                 </P
9481 ><P
9482 >Default: <B
9483 CLASS="COMMAND"
9484 >inherit acls = no</B
9485 >
9486                 </P
9487 ></DD
9488 ><DT
9489 ><A
9490 NAME="INHERITPERMISSIONS"
9491 ></A
9492 >inherit permissions (S)</DT
9493 ><DD
9494 ><P
9495 >The permissions on new files and directories
9496                 are normally governed by <A
9497 HREF="#CREATEMASK"
9498 ><TT
9499 CLASS="PARAMETER"
9500 ><I
9501 >               create mask</I
9502 ></TT
9503 ></A
9504 >, <A
9505 HREF="#DIRECTORYMASK"
9506 >               <TT
9507 CLASS="PARAMETER"
9508 ><I
9509 >directory mask</I
9510 ></TT
9511 ></A
9512 >, <A
9513 HREF="#FORCECREATEMODE"
9514 ><TT
9515 CLASS="PARAMETER"
9516 ><I
9517 >force create mode</I
9518 ></TT
9519 >
9520                 </A
9521 > and <A
9522 HREF="#FORCEDIRECTORYMODE"
9523 ><TT
9524 CLASS="PARAMETER"
9525 ><I
9526 >force
9527                 directory mode</I
9528 ></TT
9529 ></A
9530 > but the boolean inherit
9531                 permissions parameter overrides this.</P
9532 ><P
9533 >New directories inherit the mode of the parent directory,
9534                 including bits such as setgid.</P
9535 ><P
9536 >New files inherit their read/write bits from the parent
9537                 directory.  Their execute bits continue to be determined by
9538                 <A
9539 HREF="#MAPARCHIVE"
9540 ><TT
9541 CLASS="PARAMETER"
9542 ><I
9543 >map archive</I
9544 ></TT
9545 >
9546                 </A
9547 >, <A
9548 HREF="#MAPHIDDEN"
9549 ><TT
9550 CLASS="PARAMETER"
9551 ><I
9552 >map hidden</I
9553 ></TT
9554 >
9555                 </A
9556 > and <A
9557 HREF="#MAPSYSTEM"
9558 ><TT
9559 CLASS="PARAMETER"
9560 ><I
9561 >map system</I
9562 ></TT
9563 >
9564                 </A
9565 > as usual.</P
9566 ><P
9567 >Note that the setuid bit is <EM
9568 >never</EM
9569 > set via
9570                 inheritance (the code explicitly prohibits this).</P
9571 ><P
9572 >This can be particularly useful on large systems with
9573                 many users, perhaps several thousand, to allow a single [homes]
9574                 share to be used flexibly by each user.</P
9575 ><P
9576 >See also <A
9577 HREF="#CREATEMASK"
9578 ><TT
9579 CLASS="PARAMETER"
9580 ><I
9581 >create mask
9582                 </I
9583 ></TT
9584 ></A
9585 >, <A
9586 HREF="#DIRECTORYMASK"
9587 ><TT
9588 CLASS="PARAMETER"
9589 ><I
9590 >               directory mask</I
9591 ></TT
9592 ></A
9593 >, <A
9594 HREF="#FORCECREATEMODE"
9595 >               <TT
9596 CLASS="PARAMETER"
9597 ><I
9598 >force create mode</I
9599 ></TT
9600 ></A
9601 > and <A
9602 HREF="#FORCEDIRECTORYMODE"
9603 ><TT
9604 CLASS="PARAMETER"
9605 ><I
9606 >force directory mode</I
9607 ></TT
9608 >
9609                 </A
9610 >.</P
9611 ><P
9612 >Default: <B
9613 CLASS="COMMAND"
9614 >inherit permissions = no</B
9615 ></P
9616 ></DD
9617 ><DT
9618 ><A
9619 NAME="INTERFACES"
9620 ></A
9621 >interfaces (G)</DT
9622 ><DD
9623 ><P
9624 >This option allows you to override the default
9625                 network interfaces list that Samba will use for browsing, name
9626                 registration and other NBT traffic. By default Samba will query
9627                 the kernel for the list of all active interfaces and use any
9628                 interfaces except 127.0.0.1 that are broadcast capable.</P
9629 ><P
9630 >The option takes a list of interface strings. Each string
9631                 can be in any of the following forms:</P
9632 ><P
9633 ></P
9634 ><UL
9635 ><LI
9636 ><P
9637 >a network interface name (such as eth0).
9638                         This may include shell-like wildcards so eth* will match
9639                         any interface starting with the substring "eth"</P
9640 ></LI
9641 ><LI
9642 ><P
9643 >an IP address. In this case the netmask is
9644                         determined from the list of interfaces obtained from the
9645                         kernel</P
9646 ></LI
9647 ><LI
9648 ><P
9649 >an IP/mask pair. </P
9650 ></LI
9651 ><LI
9652 ><P
9653 >a broadcast/mask pair.</P
9654 ></LI
9655 ></UL
9656 ><P
9657 >The "mask" parameters can either be a bit length (such
9658                 as 24 for a C class network) or a full netmask in dotted
9659                 decimal form.</P
9660 ><P
9661 >The "IP" parameters above can either be a full dotted
9662                 decimal IP address or a hostname which will be looked up via
9663                 the OS's normal hostname resolution mechanisms.</P
9664 ><P
9665 >For example, the following line:</P
9666 ><P
9667 ><B
9668 CLASS="COMMAND"
9669 >interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
9670                 </B
9671 ></P
9672 ><P
9673 >would configure three network interfaces corresponding
9674                 to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10.
9675                 The netmasks of the latter two interfaces would be set to 255.255.255.0.</P
9676 ><P
9677 >See also <A
9678 HREF="#BINDINTERFACESONLY"
9679 ><TT
9680 CLASS="PARAMETER"
9681 ><I
9682 >bind
9683                 interfaces only</I
9684 ></TT
9685 ></A
9686 >.</P
9687 ><P
9688 >Default: <EM
9689 >all active interfaces except 127.0.0.1
9690                 that are broadcast capable</EM
9691 ></P
9692 ></DD
9693 ><DT
9694 ><A
9695 NAME="INVALIDUSERS"
9696 ></A
9697 >invalid users (S)</DT
9698 ><DD
9699 ><P
9700 >This is a list of users that should not be allowed
9701                 to login to this service. This is really a <EM
9702 >paranoid</EM
9703 >
9704                 check to absolutely ensure an improper setting does not breach
9705                 your security.</P
9706 ><P
9707 >A name starting with a '@' is interpreted as an NIS
9708                 netgroup first (if your system supports NIS), and then as a UNIX
9709                 group if the name was not found in the NIS netgroup database.</P
9710 ><P
9711 >A name starting with '+' is interpreted only
9712                 by looking in the UNIX group database. A name starting with
9713                 '&#38;' is interpreted only by looking in the NIS netgroup database
9714                 (this requires NIS to be working on your system). The characters
9715                 '+' and '&#38;' may be used at the start of the name in either order
9716                 so the value <TT
9717 CLASS="PARAMETER"
9718 ><I
9719 >+&#38;group</I
9720 ></TT
9721 > means check the
9722                 UNIX group database, followed by the NIS netgroup database, and
9723                 the value <TT
9724 CLASS="PARAMETER"
9725 ><I
9726 >&#38;+group</I
9727 ></TT
9728 > means check the NIS
9729                 netgroup database, followed by the UNIX group database (the
9730                 same as the '@' prefix).</P
9731 ><P
9732 >The current servicename is substituted for <TT
9733 CLASS="PARAMETER"
9734 ><I
9735 >%S</I
9736 ></TT
9737 >.
9738                 This is useful in the [homes] section.</P
9739 ><P
9740 >See also <A
9741 HREF="#VALIDUSERS"
9742 ><TT
9743 CLASS="PARAMETER"
9744 ><I
9745 >valid users
9746                 </I
9747 ></TT
9748 ></A
9749 >.</P
9750 ><P
9751 >Default: <EM
9752 >no invalid users</EM
9753 ></P
9754 ><P
9755 >Example: <B
9756 CLASS="COMMAND"
9757 >invalid users = root fred admin @wheel
9758                 </B
9759 ></P
9760 ></DD
9761 ><DT
9762 ><A
9763 NAME="KEEPALIVE"
9764 ></A
9765 >keepalive (G)</DT
9766 ><DD
9767 ><P
9768 >The value of the parameter (an integer) represents
9769                 the number of seconds between <TT
9770 CLASS="PARAMETER"
9771 ><I
9772 >keepalive</I
9773 ></TT
9774 >
9775                 packets. If this parameter is zero, no keepalive packets will be
9776                 sent. Keepalive packets, if sent, allow the server to tell whether
9777                 a client is still present and responding.</P
9778 ><P
9779 >Keepalives should, in general, not be needed if the socket
9780                 being used has the SO_KEEPALIVE attribute set on it (see <A
9781 HREF="#SOCKETOPTIONS"
9782 ><TT
9783 CLASS="PARAMETER"
9784 ><I
9785 >socket options</I
9786 ></TT
9787 ></A
9788 >).
9789                 Basically you should only use this option if you strike difficulties.</P
9790 ><P
9791 >Default: <B
9792 CLASS="COMMAND"
9793 >keepalive = 300</B
9794 ></P
9795 ><P
9796 >Example: <B
9797 CLASS="COMMAND"
9798 >keepalive = 600</B
9799 ></P
9800 ></DD
9801 ><DT
9802 ><A
9803 NAME="KERNELOPLOCKS"
9804 ></A
9805 >kernel oplocks (G)</DT
9806 ><DD
9807 ><P
9808 >For UNIXes that support kernel based <A
9809 HREF="#OPLOCKS"
9810 ><TT
9811 CLASS="PARAMETER"
9812 ><I
9813 >oplocks</I
9814 ></TT
9815 ></A
9816 >
9817                 (currently only IRIX and the Linux 2.4 kernel), this parameter
9818                 allows the use of them to be turned on or off.</P
9819 ><P
9820 >Kernel oplocks support allows Samba <TT
9821 CLASS="PARAMETER"
9822 ><I
9823 >oplocks
9824                 </I
9825 ></TT
9826 > to be broken whenever a local UNIX process or NFS operation
9827                 accesses a file that <A
9828 HREF="smbd.8.html"
9829 TARGET="_top"
9830 ><B
9831 CLASS="COMMAND"
9832 >smbd(8)</B
9833 >
9834                 </A
9835 > has oplocked. This allows complete data consistency between
9836                 SMB/CIFS, NFS and local file access (and is a <EM
9837 >very</EM
9838 >
9839                 cool feature :-).</P
9840 ><P
9841 >This parameter defaults to <TT
9842 CLASS="CONSTANT"
9843 >on</TT
9844 >, but is translated
9845                 to a no-op on systems that no not have the necessary kernel support.
9846                 You should never need to touch this parameter.</P
9847 ><P
9848 >See also the <A
9849 HREF="#OPLOCKS"
9850 ><TT
9851 CLASS="PARAMETER"
9852 ><I
9853 >oplocks</I
9854 ></TT
9855 >
9856                 </A
9857 > and <A
9858 HREF="#LEVEL2OPLOCKS"
9859 ><TT
9860 CLASS="PARAMETER"
9861 ><I
9862 >level2 oplocks
9863                 </I
9864 ></TT
9865 ></A
9866 > parameters.</P
9867 ><P
9868 >Default: <B
9869 CLASS="COMMAND"
9870 >kernel oplocks = yes</B
9871 ></P
9872 ></DD
9873 ><DT
9874 ><A
9875 NAME="LANMANAUTH"
9876 ></A
9877 >lanman auth (G)</DT
9878 ><DD
9879 ><P
9880 >This parameter determines whether or not <A
9881 HREF="smbd.8.html"
9882 TARGET="_top"
9883 >smbd</A
9884 > will
9885                 attempt to authenticate users using the LANMAN password hash.
9886                 If disabled, only clients which support NT password hashes (e.g. Windows
9887                 NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS
9888                 network client) will be able to connect to the Samba host.</P
9889 ><P
9890 >Default : <B
9891 CLASS="COMMAND"
9892 >lanman auth = yes</B
9893 ></P
9894 ></DD
9895 ><DT
9896 ><A
9897 NAME="LARGEREADWRITE"
9898 ></A
9899 >large readwrite (G)</DT
9900 ><DD
9901 ><P
9902 >This parameter determines whether or not <A
9903 HREF="smbd.8.html"
9904 TARGET="_top"
9905 >smbd</A
9906 >
9907                 supports the new 64k streaming read and write varient SMB requests introduced
9908                 with Windows 2000. Note that due to Windows 2000 client redirector bugs
9909                 this requires Samba to be running on a 64-bit capable operating system such
9910                 as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with
9911                 Windows 2000 clients. Defaults to on. Windows NT 4.0 only supports
9912                 read version of this call, and ignores the write version.
9913                 </P
9914 ><P
9915 >Default : <B
9916 CLASS="COMMAND"
9917 >large readwrite = yes</B
9918 ></P
9919 ></DD
9920 ><DT
9921 ><A
9922 NAME="LDAPADMINDN"
9923 ></A
9924 >ldap admin dn (G)</DT
9925 ><DD
9926 ><P
9927 >This parameter is only available if Samba has been
9928                 configure to include the <B
9929 CLASS="COMMAND"
9930 >--with-ldapsam</B
9931 > option
9932                 at compile time. This option should be considered experimental and
9933                 under active development.
9934                 </P
9935 ><P
9936 >               The <TT
9937 CLASS="PARAMETER"
9938 ><I
9939 >ldap admin dn</I
9940 ></TT
9941 > defines the Distinguished
9942                 Name (DN) name used by Samba to contact the <A
9943 HREF="#LDAPSERVER"
9944 >ldap
9945                 server</A
9946 > when retreiving user account information. The <TT
9947 CLASS="PARAMETER"
9948 ><I
9949 >ldap
9950                 admin dn</I
9951 ></TT
9952 > is used in conjunction with the admin dn password
9953                 stored in the <TT
9954 CLASS="FILENAME"
9955 >private/secrets.tdb</TT
9956 > file.  See the
9957                 <A
9958 HREF="smbpasswd.8.html"
9959 TARGET="_top"
9960 ><B
9961 CLASS="COMMAND"
9962 >smbpasswd(8)</B
9963 ></A
9964 > man
9965                 page for more information on how to accmplish this.
9966                 </P
9967 ><P
9968 >Default : <EM
9969 >none</EM
9970 ></P
9971 ></DD
9972 ><DT
9973 ><A
9974 NAME="LDAPFILTER"
9975 ></A
9976 >ldap filter (G)</DT
9977 ><DD
9978 ><P
9979 >This parameter is only available if Samba has been
9980                 configure to include the <B
9981 CLASS="COMMAND"
9982 >--with-ldapsam</B
9983 > option
9984                 at compile time. This option should be considered experimental and
9985                 under active development.
9986                 </P
9987 ><P
9988 >               This parameter specifies the RFC 2254 compliant LDAP search filter.
9989                 The default is to match the login name with the <TT
9990 CLASS="CONSTANT"
9991 >uid</TT
9992 >
9993                 attribute for all entries matching the <TT
9994 CLASS="CONSTANT"
9995 >sambaAccount</TT
9996 >
9997                 objectclass.  Note that this filter should only return one entry.
9998                 </P
9999 ><P
10000 >Default : <B
10001 CLASS="COMMAND"
10002 >ldap filter = (&#38;(uid=%u)(objectclass=sambaAccount))</B
10003 ></P
10004 ></DD
10005 ><DT
10006 ><A
10007 NAME="LDAPPORT"
10008 ></A
10009 >ldap port (G)</DT
10010 ><DD
10011 ><P
10012 >This parameter is only available if Samba has been
10013                 configure to include the <B
10014 CLASS="COMMAND"
10015 >--with-ldapsam</B
10016 > option
10017                 at compile time. This option should be considered experimental and
10018                 under active development.
10019                 </P
10020 ><P
10021 >               This option is used to control the tcp port number used to contact
10022                 the <A
10023 HREF="#LDAPSERVER"
10024 ><TT
10025 CLASS="PARAMETER"
10026 ><I
10027 >ldap server</I
10028 ></TT
10029 ></A
10030 >.
10031                 The default is to use the stand LDAPS port 636.
10032                 </P
10033 ><P
10034 >See Also: <A
10035 HREF="#LDAPSSL"
10036 >ldap ssl</A
10037 >
10038                 </P
10039 ><P
10040 >Default : <B
10041 CLASS="COMMAND"
10042 >ldap port = 636 ; if ldap ssl = on</B
10043 ></P
10044 ><P
10045 >Default : <B
10046 CLASS="COMMAND"
10047 >ldap port = 389 ; if ldap ssl = off</B
10048 ></P
10049 ></DD
10050 ><DT
10051 ><A
10052 NAME="LDAPSERVER"
10053 ></A
10054 >ldap server (G)</DT
10055 ><DD
10056 ><P
10057 >This parameter is only available if Samba has been
10058                 configure to include the <B
10059 CLASS="COMMAND"
10060 >--with-ldapsam</B
10061 > option
10062                 at compile time. This option should be considered experimental and
10063                 under active development.
10064                 </P
10065 ><P
10066 >               This parameter should contains the FQDN of the ldap directory
10067                 server which should be queried to locate user account information.
10068                 </P
10069 ><P
10070 >Default : <B
10071 CLASS="COMMAND"
10072 >ldap server = localhost</B
10073 ></P
10074 ></DD
10075 ><DT
10076 ><A
10077 NAME="LDAPSSL"
10078 ></A
10079 >ldap ssl (G)</DT
10080 ><DD
10081 ><P
10082 >This parameter is only available if Samba has been
10083                 configure to include the <B
10084 CLASS="COMMAND"
10085 >--with-ldapsam</B
10086 > option
10087                 at compile time. This option should be considered experimental and
10088                 under active development.
10089                 </P
10090 ><P
10091 >               This option is used to define whether or not Samba should
10092                 use SSL when connecting to the <A
10093 HREF="#LDAPSERVER"
10094 ><TT
10095 CLASS="PARAMETER"
10096 ><I
10097 >ldap
10098                 server</I
10099 ></TT
10100 ></A
10101 >.  This is <EM
10102 >NOT</EM
10103 > related to
10104                 Samba SSL support which is enabled by specifying the
10105                 <B
10106 CLASS="COMMAND"
10107 >--with-ssl</B
10108 > option to the <TT
10109 CLASS="FILENAME"
10110 >configure</TT
10111 >
10112                 script (see <A
10113 HREF="#SSL"
10114 ><TT
10115 CLASS="PARAMETER"
10116 ><I
10117 >ssl</I
10118 ></TT
10119 ></A
10120 >).
10121                 </P
10122 ><P
10123 >               The <TT
10124 CLASS="PARAMETER"
10125 ><I
10126 >ldap ssl</I
10127 ></TT
10128 > can be set to one of three values:
10129                 (a) <TT
10130 CLASS="CONSTANT"
10131 >on</TT
10132 > - Always use SSL when contacting the
10133                 <TT
10134 CLASS="PARAMETER"
10135 ><I
10136 >ldap   server</I
10137 ></TT
10138 >, (b) <TT
10139 CLASS="CONSTANT"
10140 >off</TT
10141 > -
10142                 Never use SSL when querying the directory, or (c) <TT
10143 CLASS="CONSTANT"
10144 >start_tls</TT
10145 >
10146                 - Use the LDAPv3 StartTLS extended operation
10147                 (RFC2830) for communicating with the directory server.
10148                 </P
10149 ><P
10150 >Default : <B
10151 CLASS="COMMAND"
10152 >ldap ssl = on</B
10153 ></P
10154 ></DD
10155 ><DT
10156 ><A
10157 NAME="LDAPSUFFIX"
10158 ></A
10159 >ldap suffix (G)</DT
10160 ><DD
10161 ><P
10162 >This parameter is only available if Samba has been
10163                 configure to include the <B
10164 CLASS="COMMAND"
10165 >--with-ldapsam</B
10166 > option
10167                 at compile time. This option should be considered experimental and
10168                 under active development.
10169                 </P
10170 ><P
10171 >Default : <EM
10172 >none</EM
10173 ></P
10174 ></DD
10175 ><DT
10176 ><A
10177 NAME="LEVEL2OPLOCKS"
10178 ></A
10179 >level2 oplocks (S)</DT
10180 ><DD
10181 ><P
10182 >This parameter controls whether Samba supports
10183                 level2 (read-only) oplocks on a share.</P
10184 ><P
10185 >Level2, or read-only oplocks allow Windows NT clients
10186                 that have an oplock on a file to downgrade from a read-write oplock
10187                 to a read-only oplock once a second client opens the file (instead
10188                 of releasing all oplocks on a second open, as in traditional,
10189                 exclusive oplocks). This allows all openers of the file that
10190                 support level2 oplocks to cache the file for read-ahead only (ie.
10191                 they may not cache writes or lock requests) and increases performance
10192                 for many accesses of files that are not commonly written (such as
10193                 application .EXE files).</P
10194 ><P
10195 >Once one of the clients which have a read-only oplock
10196                 writes to the file all clients are notified (no reply is needed
10197                 or waited for) and told to break their oplocks to "none" and
10198                 delete any read-ahead caches.</P
10199 ><P
10200 >It is recommended that this parameter be turned on
10201                 to speed access to shared executables.</P
10202 ><P
10203 >For more discussions on level2 oplocks see the CIFS spec.</P
10204 ><P
10205 >Currently, if <A
10206 HREF="#KERNELOPLOCKS"
10207 ><TT
10208 CLASS="PARAMETER"
10209 ><I
10210 >kernel
10211                 oplocks</I
10212 ></TT
10213 ></A
10214 > are supported then level2 oplocks are
10215                 not granted (even if this parameter is set to <TT
10216 CLASS="CONSTANT"
10217 >yes</TT
10218 >).
10219                 Note also, the <A
10220 HREF="#OPLOCKS"
10221 ><TT
10222 CLASS="PARAMETER"
10223 ><I
10224 >oplocks</I
10225 ></TT
10226 >
10227                 </A
10228 > parameter must be set to <TT
10229 CLASS="CONSTANT"
10230 >yes</TT
10231 > on this share in order for
10232                 this parameter to have any effect.</P
10233 ><P
10234 >See also the <A
10235 HREF="#OPLOCKS"
10236 ><TT
10237 CLASS="PARAMETER"
10238 ><I
10239 >oplocks</I
10240 ></TT
10241 >
10242                 </A
10243 > and <A
10244 HREF="#OPLOCKS"
10245 ><TT
10246 CLASS="PARAMETER"
10247 ><I
10248 >kernel oplocks</I
10249 ></TT
10250 >
10251                 </A
10252 > parameters.</P
10253 ><P
10254 >Default: <B
10255 CLASS="COMMAND"
10256 >level2 oplocks = yes</B
10257 ></P
10258 ></DD
10259 ><DT
10260 ><A
10261 NAME="LMANNOUNCE"
10262 ></A
10263 >lm announce (G)</DT
10264 ><DD
10265 ><P
10266 >This parameter determines if <A
10267 HREF="nmbd.8.html"
10268 TARGET="_top"
10269 >               <B
10270 CLASS="COMMAND"
10271 >nmbd(8)</B
10272 ></A
10273 > will produce Lanman announce
10274                 broadcasts that are needed by OS/2 clients in order for them to see
10275                 the Samba server in their browse list. This parameter can have three
10276                 values, <TT
10277 CLASS="CONSTANT"
10278 >yes</TT
10279 >, <TT
10280 CLASS="CONSTANT"
10281 >no</TT
10282 >, or
10283                 <TT
10284 CLASS="CONSTANT"
10285 >auto</TT
10286 >. The default is <TT
10287 CLASS="CONSTANT"
10288 >auto</TT
10289 >.
10290                 If set to <TT
10291 CLASS="CONSTANT"
10292 >no</TT
10293 > Samba will never produce these
10294                 broadcasts. If set to <TT
10295 CLASS="CONSTANT"
10296 >yes</TT
10297 > Samba will produce
10298                 Lanman announce broadcasts at a frequency set by the parameter
10299                 <TT
10300 CLASS="PARAMETER"
10301 ><I
10302 >lm interval</I
10303 ></TT
10304 >. If set to <TT
10305 CLASS="CONSTANT"
10306 >auto</TT
10307 >
10308                 Samba will not send Lanman announce broadcasts by default but will
10309                 listen for them. If it hears such a broadcast on the wire it will
10310                 then start sending them at a frequency set by the parameter
10311                 <TT
10312 CLASS="PARAMETER"
10313 ><I
10314 >lm interval</I
10315 ></TT
10316 >.</P
10317 ><P
10318 >See also <A
10319 HREF="#LMINTERVAL"
10320 ><TT
10321 CLASS="PARAMETER"
10322 ><I
10323 >lm interval
10324                 </I
10325 ></TT
10326 ></A
10327 >.</P
10328 ><P
10329 >Default: <B
10330 CLASS="COMMAND"
10331 >lm announce = auto</B
10332 ></P
10333 ><P
10334 >Example: <B
10335 CLASS="COMMAND"
10336 >lm announce = yes</B
10337 ></P
10338 ></DD
10339 ><DT
10340 ><A
10341 NAME="LMINTERVAL"
10342 ></A
10343 >lm interval (G)</DT
10344 ><DD
10345 ><P
10346 >If Samba is set to produce Lanman announce
10347                 broadcasts needed by OS/2 clients (see the <A
10348 HREF="#LMANNOUNCE"
10349 >               <TT
10350 CLASS="PARAMETER"
10351 ><I
10352 >lm announce</I
10353 ></TT
10354 ></A
10355 > parameter) then this
10356                 parameter defines the frequency in seconds with which they will be
10357                 made.  If this is set to zero then no Lanman announcements will be
10358                 made despite the setting of the <TT
10359 CLASS="PARAMETER"
10360 ><I
10361 >lm announce</I
10362 ></TT
10363 >
10364                 parameter.</P
10365 ><P
10366 >See also <A
10367 HREF="#LMANNOUNCE"
10368 ><TT
10369 CLASS="PARAMETER"
10370 ><I
10371 >lm
10372                 announce</I
10373 ></TT
10374 ></A
10375 >.</P
10376 ><P
10377 >Default: <B
10378 CLASS="COMMAND"
10379 >lm interval = 60</B
10380 ></P
10381 ><P
10382 >Example: <B
10383 CLASS="COMMAND"
10384 >lm interval = 120</B
10385 ></P
10386 ></DD
10387 ><DT
10388 ><A
10389 NAME="LOADPRINTERS"
10390 ></A
10391 >load printers (G)</DT
10392 ><DD
10393 ><P
10394 >A boolean variable that controls whether all
10395                 printers in the printcap will be loaded for browsing by default.
10396                 See the <A
10397 HREF="#AEN79"
10398 >printers</A
10399 > section for
10400                 more details.</P
10401 ><P
10402 >Default: <B
10403 CLASS="COMMAND"
10404 >load printers = yes</B
10405 ></P
10406 ></DD
10407 ><DT
10408 ><A
10409 NAME="LOCALMASTER"
10410 ></A
10411 >local master (G)</DT
10412 ><DD
10413 ><P
10414 >This option allows <A
10415 HREF="nmbd.8.html"
10416 TARGET="_top"
10417 ><B
10418 CLASS="COMMAND"
10419 >               nmbd(8)</B
10420 ></A
10421 > to try and become a local master browser
10422                 on a subnet. If set to <TT
10423 CLASS="CONSTANT"
10424 >no</TT
10425 > then <B
10426 CLASS="COMMAND"
10427 >               nmbd</B
10428 > will not attempt to become a local master browser
10429                 on a subnet and will also lose in all browsing elections. By
10430                 default this value is set to <TT
10431 CLASS="CONSTANT"
10432 >yes</TT
10433 >. Setting this value to <TT
10434 CLASS="CONSTANT"
10435 >yes</TT
10436 > doesn't
10437                 mean that Samba will <EM
10438 >become</EM
10439 > the local master
10440                 browser on a subnet, just that <B
10441 CLASS="COMMAND"
10442 >nmbd</B
10443 > will <EM
10444 >               participate</EM
10445 > in elections for local master browser.</P
10446 ><P
10447 >Setting this value to <TT
10448 CLASS="CONSTANT"
10449 >no</TT
10450 > will cause <B
10451 CLASS="COMMAND"
10452 >nmbd</B
10453 >
10454                 <EM
10455 >never</EM
10456 > to become a local master browser.</P
10457 ><P
10458 >Default: <B
10459 CLASS="COMMAND"
10460 >local master = yes</B
10461 ></P
10462 ></DD
10463 ><DT
10464 ><A
10465 NAME="LOCKDIR"
10466 ></A
10467 >lock dir (G)</DT
10468 ><DD
10469 ><P
10470 >Synonym for <A
10471 HREF="#LOCKDIRECTORY"
10472 ><TT
10473 CLASS="PARAMETER"
10474 ><I
10475 >               lock directory</I
10476 ></TT
10477 ></A
10478 >.</P
10479 ></DD
10480 ><DT
10481 ><A
10482 NAME="LOCKDIRECTORY"
10483 ></A
10484 >lock directory (G)</DT
10485 ><DD
10486 ><P
10487 >This option specifies the directory where lock
10488                 files will be placed.  The lock files are used to implement the
10489                 <A
10490 HREF="#MAXCONNECTIONS"
10491 ><TT
10492 CLASS="PARAMETER"
10493 ><I
10494 >max connections</I
10495 ></TT
10496 >
10497                 </A
10498 > option.</P
10499 ><P
10500 >Default: <B
10501 CLASS="COMMAND"
10502 >lock directory = ${prefix}/var/locks</B
10503 ></P
10504 ><P
10505 >Example: <B
10506 CLASS="COMMAND"
10507 >lock directory = /var/run/samba/locks</B
10508 >
10509                 </P
10510 ></DD
10511 ><DT
10512 ><A
10513 NAME="LOCKSPINCOUNT"
10514 ></A
10515 >lock spin count (G)</DT
10516 ><DD
10517 ><P
10518 >This parameter controls the number of times
10519                 that smbd should attempt to gain a byte range lock on the
10520                 behalf of a client request.  Experiments have shown that
10521                 Windows 2k servers do not reply with a failure if the lock
10522                 could not be immediately granted, but try a few more times
10523                 in case the lock could later be aquired.  This behavior
10524                 is used to support PC database formats such as MS Access
10525                 and FoxPro.
10526                 </P
10527 ><P
10528 >Default: <B
10529 CLASS="COMMAND"
10530 >lock spin count = 2</B
10531 >
10532                 </P
10533 ></DD
10534 ><DT
10535 ><A
10536 NAME="LOCKSPINTIME"
10537 ></A
10538 >lock spin time (G)</DT
10539 ><DD
10540 ><P
10541 >The time in microseconds that smbd should
10542                 pause before attempting to gain a failed lock.  See
10543                 <A
10544 HREF="#LOCKSPINCOUNT"
10545 ><TT
10546 CLASS="PARAMETER"
10547 ><I
10548 >lock spin
10549                 count</I
10550 ></TT
10551 ></A
10552 > for more details.
10553                 </P
10554 ><P
10555 >Default: <B
10556 CLASS="COMMAND"
10557 >lock spin time = 10</B
10558 >
10559                 </P
10560 ></DD
10561 ><DT
10562 ><A
10563 NAME="LOCKING"
10564 ></A
10565 >locking (S)</DT
10566 ><DD
10567 ><P
10568 >This controls whether or not locking will be
10569                 performed by the server in response to lock requests from the
10570                 client.</P
10571 ><P
10572 >If <B
10573 CLASS="COMMAND"
10574 >locking = no</B
10575 >, all lock and unlock
10576                 requests will appear to succeed and all lock queries will report
10577                 that the file in question is available for locking.</P
10578 ><P
10579 >If <B
10580 CLASS="COMMAND"
10581 >locking = yes</B
10582 >, real locking will be performed
10583                 by the server.</P
10584 ><P
10585 >This option <EM
10586 >may</EM
10587 > be useful for read-only
10588                 filesystems which <EM
10589 >may</EM
10590 > not need locking (such as
10591                 CDROM drives), although setting this parameter of <TT
10592 CLASS="CONSTANT"
10593 >no</TT
10594 >
10595                 is not really recommended even in this case.</P
10596 ><P
10597 >Be careful about disabling locking either globally or in a
10598                 specific service, as lack of locking may result in data corruption.
10599                 You should never need to set this parameter.</P
10600 ><P
10601 >Default: <B
10602 CLASS="COMMAND"
10603 >locking = yes</B
10604 ></P
10605 ></DD
10606 ><DT
10607 ><A
10608 NAME="LOGFILE"
10609 ></A
10610 >log file (G)</DT
10611 ><DD
10612 ><P
10613 >This option allows you to override the name
10614                 of the Samba log file (also known as the debug file).</P
10615 ><P
10616 >This option takes the standard substitutions, allowing
10617                 you to have separate log files for each user or machine.</P
10618 ><P
10619 >Example: <B
10620 CLASS="COMMAND"
10621 >log file = /usr/local/samba/var/log.%m
10622                 </B
10623 ></P
10624 ></DD
10625 ><DT
10626 ><A
10627 NAME="LOGLEVEL"
10628 ></A
10629 >log level (G)</DT
10630 ><DD
10631 ><P
10632 >The value of the parameter (an integer) allows
10633                 the debug level (logging level) to be specified in the
10634                 <TT
10635 CLASS="FILENAME"
10636 >smb.conf</TT
10637 > file. This is to give greater
10638                 flexibility in the configuration of the system.</P
10639 ><P
10640 >The default will be the log level specified on
10641                 the command line or level zero if none was specified.</P
10642 ><P
10643 >Example: <B
10644 CLASS="COMMAND"
10645 >log level = 3</B
10646 ></P
10647 ></DD
10648 ><DT
10649 ><A
10650 NAME="LOGONDRIVE"
10651 ></A
10652 >logon drive (G)</DT
10653 ><DD
10654 ><P
10655 >This parameter specifies the local path to
10656                 which the home directory will be connected (see <A
10657 HREF="#LOGONHOME"
10658 ><TT
10659 CLASS="PARAMETER"
10660 ><I
10661 >logon home</I
10662 ></TT
10663 ></A
10664 >)
10665                 and is only used by NT Workstations. </P
10666 ><P
10667 >Note that this option is only useful if Samba is set up as a
10668                 logon server.</P
10669 ><P
10670 >Default: <B
10671 CLASS="COMMAND"
10672 >logon drive = z:</B
10673 ></P
10674 ><P
10675 >Example: <B
10676 CLASS="COMMAND"
10677 >logon drive = h:</B
10678 ></P
10679 ></DD
10680 ><DT
10681 ><A
10682 NAME="LOGONHOME"
10683 ></A
10684 >logon home (G)</DT
10685 ><DD
10686 ><P
10687 >This parameter specifies the home directory
10688                 location when a Win95/98 or NT Workstation logs into a Samba PDC.
10689                 It allows you to do </P
10690 ><P
10691 ><TT
10692 CLASS="PROMPT"
10693 >C:\&#62; </TT
10694 ><TT
10695 CLASS="USERINPUT"
10696 ><B
10697 >NET USE H: /HOME</B
10698 ></TT
10699 >
10700                 </P
10701 ><P
10702 >from a command prompt, for example.</P
10703 ><P
10704 >This option takes the standard substitutions, allowing
10705                 you to have separate logon scripts for each user or machine.</P
10706 ><P
10707 >This parameter can be used with Win9X workstations to ensure
10708                 that roaming profiles are stored in a subdirectory of the user's
10709                 home directory.  This is done in the following way:</P
10710 ><P
10711 ><B
10712 CLASS="COMMAND"
10713 >logon home = \\%N\%U\profile</B
10714 ></P
10715 ><P
10716 >This tells Samba to return the above string, with
10717                 substitutions made when a client requests the info, generally
10718                 in a NetUserGetInfo request.  Win9X clients truncate the info to
10719                 \\server\share when a user does <B
10720 CLASS="COMMAND"
10721 >net use /home</B
10722 >
10723                 but use the whole string when dealing with profiles.</P
10724 ><P
10725 >Note that in prior versions of Samba, the <A
10726 HREF="#LOGONPATH"
10727 >               <TT
10728 CLASS="PARAMETER"
10729 ><I
10730 >logon path</I
10731 ></TT
10732 ></A
10733 > was returned rather than
10734                 <TT
10735 CLASS="PARAMETER"
10736 ><I
10737 >logon home</I
10738 ></TT
10739 >.  This broke <B
10740 CLASS="COMMAND"
10741 >net use
10742                 /home</B
10743 > but allowed profiles outside the home directory.
10744                 The current implementation is correct, and can be used for
10745                 profiles if you use the above trick.</P
10746 ><P
10747 >This option is only useful if Samba is set up as a logon
10748                 server.</P
10749 ><P
10750 >Default: <B
10751 CLASS="COMMAND"
10752 >logon home = "\\%N\%U"</B
10753 ></P
10754 ><P
10755 >Example: <B
10756 CLASS="COMMAND"
10757 >logon home = "\\remote_smb_server\%U"</B
10758 >
10759                 </P
10760 ></DD
10761 ><DT
10762 ><A
10763 NAME="LOGONPATH"
10764 ></A
10765 >logon path (G)</DT
10766 ><DD
10767 ><P
10768 >This parameter specifies the home directory
10769                 where roaming profiles (NTuser.dat etc files for Windows NT) are
10770                 stored.  Contrary to previous versions of these manual pages, it has
10771                 nothing to do with Win 9X roaming profiles.  To find out how to
10772                 handle roaming profiles for Win 9X system, see the <A
10773 HREF="#LOGONHOME"
10774 >               <TT
10775 CLASS="PARAMETER"
10776 ><I
10777 >logon home</I
10778 ></TT
10779 ></A
10780 > parameter.</P
10781 ><P
10782 >This option takes the standard substitutions, allowing you
10783                 to have separate logon scripts for each user or machine.  It also
10784                 specifies the directory from which the "Application Data",
10785                 (<TT
10786 CLASS="FILENAME"
10787 >desktop</TT
10788 >, <TT
10789 CLASS="FILENAME"
10790 >start menu</TT
10791 >,
10792                 <TT
10793 CLASS="FILENAME"
10794 >network neighborhood</TT
10795 >, <TT
10796 CLASS="FILENAME"
10797 >programs</TT
10798 >
10799                 and other folders, and their contents, are loaded and displayed on
10800                 your Windows NT client.</P
10801 ><P
10802 >The share and the path must be readable by the user for
10803                 the preferences and directories to be loaded onto the Windows NT
10804                 client.  The share must be writeable when the user logs in for the first
10805                 time, in order that the Windows NT client can create the NTuser.dat
10806                 and other directories.</P
10807 ><P
10808 >Thereafter, the directories and any of the contents can,
10809                 if required, be made read-only.  It is not advisable that the
10810                 NTuser.dat file be made read-only - rename it to NTuser.man to
10811                 achieve the desired effect (a <EM
10812 >MAN</EM
10813 >datory
10814                 profile). </P
10815 ><P
10816 >Windows clients can sometimes maintain a connection to
10817                 the [homes] share, even though there is no user logged in.
10818                 Therefore, it is vital that the logon path does not include a
10819                 reference to the homes share (i.e. setting this parameter to
10820                 \%N\%U\profile_path will cause problems).</P
10821 ><P
10822 >This option takes the standard substitutions, allowing
10823                 you to have separate logon scripts for each user or machine.</P
10824 ><P
10825 >Note that this option is only useful if Samba is set up
10826                 as a logon server.</P
10827 ><P
10828 >Default: <B
10829 CLASS="COMMAND"
10830 >logon path = \\%N\%U\profile</B
10831 ></P
10832 ><P
10833 >Example: <B
10834 CLASS="COMMAND"
10835 >logon path = \\PROFILESERVER\PROFILE\%U</B
10836 ></P
10837 ></DD
10838 ><DT
10839 ><A
10840 NAME="LOGONSCRIPT"
10841 ></A
10842 >logon script (G)</DT
10843 ><DD
10844 ><P
10845 >This parameter specifies the batch file (.bat) or
10846                 NT command file (.cmd) to be downloaded and run on a machine when
10847                 a user successfully logs in.  The file must contain the DOS
10848                 style CR/LF line endings. Using a DOS-style editor to create the
10849                 file is recommended.</P
10850 ><P
10851 >The script must be a relative path to the [netlogon]
10852                 service.  If the [netlogon] service specifies a <A
10853 HREF="#PATH"
10854 >               <TT
10855 CLASS="PARAMETER"
10856 ><I
10857 >path</I
10858 ></TT
10859 ></A
10860 > of <TT
10861 CLASS="FILENAME"
10862 >/usr/local/samba/netlogon
10863                 </TT
10864 >, and <B
10865 CLASS="COMMAND"
10866 >logon script = STARTUP.BAT</B
10867 >, then
10868                 the file that will be downloaded is:</P
10869 ><P
10870 ><TT
10871 CLASS="FILENAME"
10872 >/usr/local/samba/netlogon/STARTUP.BAT</TT
10873 ></P
10874 ><P
10875 >The contents of the batch file are entirely your choice.  A
10876                 suggested command would be to add <B
10877 CLASS="COMMAND"
10878 >NET TIME \\SERVER /SET
10879                 /YES</B
10880 >, to force every machine to synchronize clocks with
10881                 the same time server.  Another use would be to add <B
10882 CLASS="COMMAND"
10883 >NET USE
10884                 U: \\SERVER\UTILS</B
10885 > for commonly used utilities, or <B
10886 CLASS="COMMAND"
10887 >               NET USE Q: \\SERVER\ISO9001_QA</B
10888 > for example.</P
10889 ><P
10890 >Note that it is particularly important not to allow write
10891                 access to the [netlogon] share, or to grant users write permission
10892                 on the batch files in a secure environment, as this would allow
10893                 the batch files to be arbitrarily modified and security to be
10894                 breached.</P
10895 ><P
10896 >This option takes the standard substitutions, allowing you
10897                 to have separate logon scripts for each user or machine.</P
10898 ><P
10899 >This option is only useful if Samba is set up as a logon
10900                 server.</P
10901 ><P
10902 >Default: <EM
10903 >no logon script defined</EM
10904 ></P
10905 ><P
10906 >Example: <B
10907 CLASS="COMMAND"
10908 >logon script = scripts\%U.bat</B
10909 ></P
10910 ></DD
10911 ><DT
10912 ><A
10913 NAME="LPPAUSECOMMAND"
10914 ></A
10915 >lppause command (S)</DT
10916 ><DD
10917 ><P
10918 >This parameter specifies the command to be
10919                 executed on the server host in order to stop printing or spooling
10920                 a specific print job.</P
10921 ><P
10922 >This command should be a program or script which takes
10923                 a printer name and job number to pause the print job. One way
10924                 of implementing this is by using job priorities, where jobs
10925                 having a too low priority won't be sent to the printer.</P
10926 ><P
10927 >If a <TT
10928 CLASS="PARAMETER"
10929 ><I
10930 >%p</I
10931 ></TT
10932 > is given then the printer name
10933                 is put in its place. A <TT
10934 CLASS="PARAMETER"
10935 ><I
10936 >%j</I
10937 ></TT
10938 > is replaced with
10939                 the job number (an integer).  On HPUX (see <TT
10940 CLASS="PARAMETER"
10941 ><I
10942 >printing=hpux
10943                 </I
10944 ></TT
10945 >), if the <TT
10946 CLASS="PARAMETER"
10947 ><I
10948 >-p%p</I
10949 ></TT
10950 > option is added
10951                 to the lpq command, the job will show up with the correct status, i.e.
10952                 if the job priority is lower than the set fence priority it will
10953                 have the PAUSED status, whereas if  the priority is equal or higher it
10954                 will have the SPOOLED or PRINTING status.</P
10955 ><P
10956 >Note that it is good practice to include the absolute path
10957                 in the lppause command as the PATH may not be available to the server.</P
10958 ><P
10959 >See also the <A
10960 HREF="#PRINTING"
10961 ><TT
10962 CLASS="PARAMETER"
10963 ><I
10964 >printing
10965                 </I
10966 ></TT
10967 ></A
10968 > parameter.</P
10969 ><P
10970 >Default: Currently no default value is given to
10971                 this string, unless the value of the <TT
10972 CLASS="PARAMETER"
10973 ><I
10974 >printing</I
10975 ></TT
10976 >
10977                 parameter is <TT
10978 CLASS="CONSTANT"
10979 >SYSV</TT
10980 >, in which case the default is :</P
10981 ><P
10982 ><B
10983 CLASS="COMMAND"
10984 >lp -i %p-%j -H hold</B
10985 ></P
10986 ><P
10987 >or if the value of the <TT
10988 CLASS="PARAMETER"
10989 ><I
10990 >printing</I
10991 ></TT
10992 > parameter
10993                 is <TT
10994 CLASS="CONSTANT"
10995 >SOFTQ</TT
10996 >, then the default is:</P
10997 ><P
10998 ><B
10999 CLASS="COMMAND"
11000 >qstat -s -j%j -h</B
11001 ></P
11002 ><P
11003 >Example for HPUX: <B
11004 CLASS="COMMAND"
11005 >lppause command = /usr/bin/lpalt
11006                 %p-%j -p0</B
11007 ></P
11008 ></DD
11009 ><DT
11010 ><A
11011 NAME="LPQCACHETIME"
11012 ></A
11013 >lpq cache time (G)</DT
11014 ><DD
11015 ><P
11016 >This controls how long lpq info will be cached
11017                 for to prevent the <B
11018 CLASS="COMMAND"
11019 >lpq</B
11020 > command being called too
11021                 often. A separate cache is kept for each variation of the <B
11022 CLASS="COMMAND"
11023 >               lpq</B
11024 > command used by the system, so if you use different
11025                 <B
11026 CLASS="COMMAND"
11027 >lpq</B
11028 > commands for different users then they won't
11029                 share cache information.</P
11030 ><P
11031 >The cache files are stored in <TT
11032 CLASS="FILENAME"
11033 >/tmp/lpq.xxxx</TT
11034 >
11035                 where xxxx is a hash of the <B
11036 CLASS="COMMAND"
11037 >lpq</B
11038 > command in use.</P
11039 ><P
11040 >The default is 10 seconds, meaning that the cached results
11041                 of a previous identical <B
11042 CLASS="COMMAND"
11043 >lpq</B
11044 > command will be used
11045                 if the cached data is less than 10 seconds old. A large value may
11046                 be advisable if your <B
11047 CLASS="COMMAND"
11048 >lpq</B
11049 > command is very slow.</P
11050 ><P
11051 >A value of 0 will disable caching completely.</P
11052 ><P
11053 >See also the <A
11054 HREF="#PRINTING"
11055 ><TT
11056 CLASS="PARAMETER"
11057 ><I
11058 >printing
11059                 </I
11060 ></TT
11061 ></A
11062 > parameter.</P
11063 ><P
11064 >Default: <B
11065 CLASS="COMMAND"
11066 >lpq cache time = 10</B
11067 ></P
11068 ><P
11069 >Example: <B
11070 CLASS="COMMAND"
11071 >lpq cache time = 30</B
11072 ></P
11073 ></DD
11074 ><DT
11075 ><A
11076 NAME="LPQCOMMAND"
11077 ></A
11078 >lpq command (S)</DT
11079 ><DD
11080 ><P
11081 >This parameter specifies the command to be
11082                 executed on the server host in order to obtain <B
11083 CLASS="COMMAND"
11084 >lpq
11085                 </B
11086 >-style printer status information.</P
11087 ><P
11088 >This command should be a program or script which
11089                 takes a printer name as its only parameter and outputs printer
11090                 status information.</P
11091 ><P
11092 >Currently nine styles of printer status information
11093                 are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ.
11094                 This covers most UNIX systems. You control which type is expected
11095                 using the <TT
11096 CLASS="PARAMETER"
11097 ><I
11098 >printing =</I
11099 ></TT
11100 > option.</P
11101 ><P
11102 >Some clients (notably Windows for Workgroups) may not
11103                 correctly send the connection number for the printer they are
11104                 requesting status information about. To get around this, the
11105                 server reports on the first printer service connected to by the
11106                 client. This only happens if the connection number sent is invalid.</P
11107 ><P
11108 >If a <TT
11109 CLASS="PARAMETER"
11110 ><I
11111 >%p</I
11112 ></TT
11113 > is given then the printer name
11114                 is put in its place. Otherwise it is placed at the end of the
11115                 command.</P
11116 ><P
11117 >Note that it is good practice to include the absolute path
11118                 in the <TT
11119 CLASS="PARAMETER"
11120 ><I
11121 >lpq command</I
11122 ></TT
11123 > as the <TT
11124 CLASS="ENVAR"
11125 >$PATH
11126                 </TT
11127 > may not be available to the server.  When compiled with
11128                 the CUPS libraries, no <TT
11129 CLASS="PARAMETER"
11130 ><I
11131 >lpq command</I
11132 ></TT
11133 > is
11134                 needed because smbd will make a library call to obtain the
11135                 print queue listing.</P
11136 ><P
11137 >See also the <A
11138 HREF="#PRINTING"
11139 ><TT
11140 CLASS="PARAMETER"
11141 ><I
11142 >printing
11143                 </I
11144 ></TT
11145 ></A
11146 > parameter.</P
11147 ><P
11148 >Default: <EM
11149 >depends on the setting of <TT
11150 CLASS="PARAMETER"
11151 ><I
11152 >               printing</I
11153 ></TT
11154 ></EM
11155 ></P
11156 ><P
11157 >Example: <B
11158 CLASS="COMMAND"
11159 >lpq command = /usr/bin/lpq -P%p</B
11160 ></P
11161 ></DD
11162 ><DT
11163 ><A
11164 NAME="LPRESUMECOMMAND"
11165 ></A
11166 >lpresume command (S)</DT
11167 ><DD
11168 ><P
11169 >This parameter specifies the command to be
11170                 executed on the server host in order to restart or continue
11171                 printing or spooling a specific print job.</P
11172 ><P
11173 >This command should be a program or script which takes
11174                 a printer name and job number to resume the print job. See
11175                 also the <A
11176 HREF="#LPPAUSECOMMAND"
11177 ><TT
11178 CLASS="PARAMETER"
11179 ><I
11180 >lppause command
11181                 </I
11182 ></TT
11183 ></A
11184 > parameter.</P
11185 ><P
11186 >If a <TT
11187 CLASS="PARAMETER"
11188 ><I
11189 >%p</I
11190 ></TT
11191 > is given then the printer name
11192                 is put in its place. A <TT
11193 CLASS="PARAMETER"
11194 ><I
11195 >%j</I
11196 ></TT
11197 > is replaced with
11198                 the job number (an integer).</P
11199 ><P
11200 >Note that it is good practice to include the absolute path
11201                 in the <TT
11202 CLASS="PARAMETER"
11203 ><I
11204 >lpresume command</I
11205 ></TT
11206 > as the PATH may not
11207                 be available to the server.</P
11208 ><P
11209 >See also the <A
11210 HREF="#PRINTING"
11211 ><TT
11212 CLASS="PARAMETER"
11213 ><I
11214 >printing
11215                 </I
11216 ></TT
11217 ></A
11218 > parameter.</P
11219 ><P
11220 >Default: Currently no default value is given
11221                 to this string, unless the value of the <TT
11222 CLASS="PARAMETER"
11223 ><I
11224 >printing</I
11225 ></TT
11226 >
11227                 parameter is <TT
11228 CLASS="CONSTANT"
11229 >SYSV</TT
11230 >, in which case the default is :</P
11231 ><P
11232 ><B
11233 CLASS="COMMAND"
11234 >lp -i %p-%j -H resume</B
11235 ></P
11236 ><P
11237 >or if the value of the <TT
11238 CLASS="PARAMETER"
11239 ><I
11240 >printing</I
11241 ></TT
11242 > parameter
11243                 is <TT
11244 CLASS="CONSTANT"
11245 >SOFTQ</TT
11246 >, then the default is:</P
11247 ><P
11248 ><B
11249 CLASS="COMMAND"
11250 >qstat -s -j%j -r</B
11251 ></P
11252 ><P
11253 >Example for HPUX: <B
11254 CLASS="COMMAND"
11255 >lpresume command = /usr/bin/lpalt
11256                 %p-%j -p2</B
11257 ></P
11258 ></DD
11259 ><DT
11260 ><A
11261 NAME="LPRMCOMMAND"
11262 ></A
11263 >lprm command (S)</DT
11264 ><DD
11265 ><P
11266 >This parameter specifies the command to be
11267                 executed on the server host in order to delete a print job.</P
11268 ><P
11269 >This command should be a program or script which takes
11270                 a printer name and job number, and deletes the print job.</P
11271 ><P
11272 >If a <TT
11273 CLASS="PARAMETER"
11274 ><I
11275 >%p</I
11276 ></TT
11277 > is given then the printer name
11278                 is put in its place. A <TT
11279 CLASS="PARAMETER"
11280 ><I
11281 >%j</I
11282 ></TT
11283 > is replaced with
11284                 the job number (an integer).</P
11285 ><P
11286 >Note that it is good practice to include the absolute
11287                 path in the <TT
11288 CLASS="PARAMETER"
11289 ><I
11290 >lprm command</I
11291 ></TT
11292 > as the PATH may not be
11293                 available to the server.</P
11294 ><P
11295 >See also the <A
11296 HREF="#PRINTING"
11297 ><TT
11298 CLASS="PARAMETER"
11299 ><I
11300 >printing
11301                 </I
11302 ></TT
11303 ></A
11304 > parameter.</P
11305 ><P
11306 >Default: <EM
11307 >depends on the setting of <TT
11308 CLASS="PARAMETER"
11309 ><I
11310 >printing
11311                 </I
11312 ></TT
11313 ></EM
11314 ></P
11315 ><P
11316 >Example 1: <B
11317 CLASS="COMMAND"
11318 >lprm command = /usr/bin/lprm -P%p %j
11319                 </B
11320 ></P
11321 ><P
11322 >Example 2: <B
11323 CLASS="COMMAND"
11324 >lprm command = /usr/bin/cancel %p-%j
11325                 </B
11326 ></P
11327 ></DD
11328 ><DT
11329 ><A
11330 NAME="MACHINEPASSWORDTIMEOUT"
11331 ></A
11332 >machine password timeout (G)</DT
11333 ><DD
11334 ><P
11335 >If a Samba server is a member of a Windows
11336                 NT Domain (see the <A
11337 HREF="#SECURITYEQUALSDOMAIN"
11338 >security = domain</A
11339 >)
11340                 parameter) then periodically a running <A
11341 HREF="smbd.8.html"
11342 TARGET="_top"
11343 >               smbd(8)</A
11344 > process will try and change the MACHINE ACCOUNT
11345                 PASSWORD stored in the TDB called <TT
11346 CLASS="FILENAME"
11347 >private/secrets.tdb
11348                 </TT
11349 >.  This parameter specifies how often this password
11350                 will be changed, in seconds. The default is one week (expressed in
11351                 seconds), the same as a Windows NT Domain member server.</P
11352 ><P
11353 >See also <A
11354 HREF="smbpasswd.8.html"
11355 TARGET="_top"
11356 ><B
11357 CLASS="COMMAND"
11358 >smbpasswd(8)
11359                 </B
11360 ></A
11361 >, and the <A
11362 HREF="#SECURITYEQUALSDOMAIN"
11363 >               security = domain</A
11364 >) parameter.</P
11365 ><P
11366 >Default: <B
11367 CLASS="COMMAND"
11368 >machine password timeout = 604800</B
11369 ></P
11370 ></DD
11371 ><DT
11372 ><A
11373 NAME="MAGICOUTPUT"
11374 ></A
11375 >magic output (S)</DT
11376 ><DD
11377 ><P
11378 >This parameter specifies the name of a file
11379                 which will contain output created by a magic script (see the
11380                 <A
11381 HREF="#MAGICSCRIPT"
11382 ><TT
11383 CLASS="PARAMETER"
11384 ><I
11385 >magic script</I
11386 ></TT
11387 ></A
11388 >
11389                 parameter below).</P
11390 ><P
11391 >Warning: If two clients use the same <TT
11392 CLASS="PARAMETER"
11393 ><I
11394 >magic script
11395                 </I
11396 ></TT
11397 > in the same directory the output file content
11398                 is undefined.</P
11399 ><P
11400 >Default: <B
11401 CLASS="COMMAND"
11402 >magic output = &#60;magic script name&#62;.out
11403                 </B
11404 ></P
11405 ><P
11406 >Example: <B
11407 CLASS="COMMAND"
11408 >magic output = myfile.txt</B
11409 ></P
11410 ></DD
11411 ><DT
11412 ><A
11413 NAME="MAGICSCRIPT"
11414 ></A
11415 >magic script (S)</DT
11416 ><DD
11417 ><P
11418 >This parameter specifies the name of a file which,
11419                 if opened, will be executed by the server when the file is closed.
11420                 This allows a UNIX script to be sent to the Samba host and
11421                 executed on behalf of the connected user.</P
11422 ><P
11423 >Scripts executed in this way will be deleted upon
11424                 completion assuming that the user has the appropriate level
11425                 of privilege and the file permissions allow the deletion.</P
11426 ><P
11427 >If the script generates output, output will be sent to
11428                 the file specified by the <A
11429 HREF="#MAGICOUTPUT"
11430 ><TT
11431 CLASS="PARAMETER"
11432 ><I
11433 >               magic output</I
11434 ></TT
11435 ></A
11436 > parameter (see above).</P
11437 ><P
11438 >Note that some shells are unable to interpret scripts
11439                 containing CR/LF instead of CR as
11440                 the end-of-line marker. Magic scripts must be executable
11441                 <EM
11442 >as is</EM
11443 > on the host, which for some hosts and
11444                 some shells will require filtering at the DOS end.</P
11445 ><P
11446 >Magic scripts are <EM
11447 >EXPERIMENTAL</EM
11448 > and
11449                 should <EM
11450 >NOT</EM
11451 > be relied upon.</P
11452 ><P
11453 >Default: <EM
11454 >None. Magic scripts disabled.</EM
11455 ></P
11456 ><P
11457 >Example: <B
11458 CLASS="COMMAND"
11459 >magic script = user.csh</B
11460 ></P
11461 ></DD
11462 ><DT
11463 ><A
11464 NAME="MANGLECASE"
11465 ></A
11466 >mangle case (S)</DT
11467 ><DD
11468 ><P
11469 >See the section on <A
11470 HREF="#AEN203"
11471 >               NAME MANGLING</A
11472 ></P
11473 ><P
11474 >Default: <B
11475 CLASS="COMMAND"
11476 >mangle case = no</B
11477 ></P
11478 ></DD
11479 ><DT
11480 ><A
11481 NAME="MANGLEDMAP"
11482 ></A
11483 >mangled map (S)</DT
11484 ><DD
11485 ><P
11486 >This is for those who want to directly map UNIX
11487                 file names which cannot be represented on Windows/DOS.  The mangling
11488                 of names is not always what is needed.  In particular you may have
11489                 documents with file extensions that differ between DOS and UNIX.
11490                 For example, under UNIX it is common to use <TT
11491 CLASS="FILENAME"
11492 >.html</TT
11493 >
11494                 for HTML files, whereas under Windows/DOS <TT
11495 CLASS="FILENAME"
11496 >.htm</TT
11497 >
11498                 is more commonly used.</P
11499 ><P
11500 >So to map <TT
11501 CLASS="FILENAME"
11502 >html</TT
11503 > to <TT
11504 CLASS="FILENAME"
11505 >htm</TT
11506 >
11507                 you would use:</P
11508 ><P
11509 ><B
11510 CLASS="COMMAND"
11511 >mangled map = (*.html *.htm)</B
11512 ></P
11513 ><P
11514 >One very useful case is to remove the annoying <TT
11515 CLASS="FILENAME"
11516 >;1
11517                 </TT
11518 > off the ends of filenames on some CDROMs (only visible
11519                 under some UNIXes). To do this use a map of (*;1 *;).</P
11520 ><P
11521 >Default: <EM
11522 >no mangled map</EM
11523 ></P
11524 ><P
11525 >Example: <B
11526 CLASS="COMMAND"
11527 >mangled map = (*;1 *;)</B
11528 ></P
11529 ></DD
11530 ><DT
11531 ><A
11532 NAME="MANGLEDNAMES"
11533 ></A
11534 >mangled names (S)</DT
11535 ><DD
11536 ><P
11537 >This controls whether non-DOS names under UNIX
11538                 should be mapped to DOS-compatible names ("mangled") and made visible,
11539                 or whether non-DOS names should simply be ignored.</P
11540 ><P
11541 >See the section on <A
11542 HREF="#AEN203"
11543 >               NAME MANGLING</A
11544 > for details on how to control the mangling process.</P
11545 ><P
11546 >If mangling algorithm "hash" is used then the mangling algorithm is as follows:</P
11547 ><P
11548 ></P
11549 ><UL
11550 ><LI
11551 ><P
11552 >The first (up to) five alphanumeric characters
11553                         before the rightmost dot of the filename are preserved, forced
11554                         to upper case, and appear as the first (up to) five characters
11555                         of the mangled name.</P
11556 ></LI
11557 ><LI
11558 ><P
11559 >A tilde "~" is appended to the first part of the mangled
11560                         name, followed by a two-character unique sequence, based on the
11561                         original root name (i.e., the original filename minus its final
11562                         extension). The final extension is included in the hash calculation
11563                         only if it contains any upper case characters or is longer than three
11564                         characters.</P
11565 ><P
11566 >Note that the character to use may be specified using
11567                         the <A
11568 HREF="#MANGLINGCHAR"
11569 ><TT
11570 CLASS="PARAMETER"
11571 ><I
11572 >mangling char</I
11573 ></TT
11574 >
11575                         </A
11576 > option, if you don't like '~'.</P
11577 ></LI
11578 ><LI
11579 ><P
11580 >The first three alphanumeric characters of the final
11581                         extension are preserved, forced to upper case and appear as the
11582                         extension of the mangled name. The final extension is defined as that
11583                         part of the original filename after the rightmost dot. If there are no
11584                         dots in the filename, the mangled name will have no extension (except
11585                         in the case of "hidden files" - see below).</P
11586 ></LI
11587 ><LI
11588 ><P
11589 >Files whose UNIX name begins with a dot will be
11590                         presented as DOS hidden files. The mangled name will be created as
11591                         for other filenames, but with the leading dot removed and "___" as
11592                         its extension regardless of actual original extension (that's three
11593                         underscores).</P
11594 ></LI
11595 ></UL
11596 ><P
11597 >The two-digit hash value consists of upper case
11598                 alphanumeric characters.</P
11599 ><P
11600 >This algorithm can cause name collisions only if files
11601                 in a directory share the same first five alphanumeric characters.
11602                 The probability of such a clash is 1/1300.</P
11603 ><P
11604 >If mangling algorithm "hash2" is used then the mangling algorithm is as follows:</P
11605 ><P
11606 ></P
11607 ><UL
11608 ><LI
11609 ><P
11610 >The first alphanumeric character
11611                         before the rightmost dot of the filename is preserved, forced
11612                         to upper case, and appears as the first character of the mangled name.
11613                         </P
11614 ></LI
11615 ><LI
11616 ><P
11617 >A base63 hash of 5 characters is generated and the
11618                         first 4 characters of that hash are appended to the first character.
11619                         </P
11620 ></LI
11621 ><LI
11622 ><P
11623 >A tilde "~" is appended to the first part of the mangled
11624                         name, followed by the final character of the base36 hash of the name.
11625                         </P
11626 ><P
11627 >Note that the character to use may be specified using
11628                         the <A
11629 HREF="#MANGLINGCHAR"
11630 ><TT
11631 CLASS="PARAMETER"
11632 ><I
11633 >mangling char</I
11634 ></TT
11635 >
11636                         </A
11637 > option, if you don't like '~'.</P
11638 ></LI
11639 ><LI
11640 ><P
11641 >The first three alphanumeric characters of the final
11642                         extension are preserved, forced to upper case and appear as the
11643                         extension of the mangled name. The final extension is defined as that
11644                         part of the original filename after the rightmost dot. If there are no
11645                         dots in the filename, the mangled name will have no extension (except
11646                         in the case of "hidden files" - see below).</P
11647 ></LI
11648 ><LI
11649 ><P
11650 >Files whose UNIX name begins with a dot will be
11651                         presented as DOS hidden files. The mangled name will be created as
11652                         for other filenames, but with the leading dot removed and "___" as
11653                         its extension regardless of actual original extension (that's three
11654                         underscores).</P
11655 ></LI
11656 ></UL
11657 ><P
11658 >The name mangling (if enabled) allows a file to be
11659                 copied between UNIX directories from Windows/DOS while retaining
11660                 the long UNIX filename. UNIX files can be renamed to a new extension
11661                 from Windows/DOS and will retain the same basename. Mangled names
11662                 do not change between sessions.</P
11663 ><P
11664 >Default: <B
11665 CLASS="COMMAND"
11666 >mangled names = yes</B
11667 ></P
11668 ></DD
11669 ><DT
11670 ><A
11671 NAME="MANGLEDSTACK"
11672 ></A
11673 >mangled stack (G)</DT
11674 ><DD
11675 ><P
11676 >This parameter controls the number of mangled names
11677                 that should be cached in the Samba server <A
11678 HREF="smbd.8.html"
11679 TARGET="_top"
11680 >               smbd(8)</A
11681 >.</P
11682 ><P
11683 >This stack is a list of recently mangled base names
11684                 (extensions are only maintained if they are longer than 3 characters
11685                 or contains upper case characters).</P
11686 ><P
11687 >The larger this value, the more likely it is that mangled
11688                 names can be successfully converted to correct long UNIX names.
11689                 However, large stack sizes will slow most directory accesses. Smaller
11690                 stacks save memory in the server (each stack element costs 256 bytes).
11691                 </P
11692 ><P
11693 >It is not possible to absolutely guarantee correct long
11694                 filenames, so be prepared for some surprises!</P
11695 ><P
11696 >Default: <B
11697 CLASS="COMMAND"
11698 >mangled stack = 50</B
11699 ></P
11700 ><P
11701 >Example: <B
11702 CLASS="COMMAND"
11703 >mangled stack = 100</B
11704 ></P
11705 ></DD
11706 ><DT
11707 ><A
11708 NAME="MANGLINGCHAR"
11709 ></A
11710 >mangling char (S)</DT
11711 ><DD
11712 ><P
11713 >This controls what character is used as
11714                 the <EM
11715 >magic</EM
11716 > character in <A
11717 HREF="#AEN203"
11718 >name mangling</A
11719 >. The default is a '~'
11720                 but this may interfere with some software. Use this option to set
11721                 it to whatever you prefer.</P
11722 ><P
11723 >Default: <B
11724 CLASS="COMMAND"
11725 >mangling char = ~</B
11726 ></P
11727 ><P
11728 >Example: <B
11729 CLASS="COMMAND"
11730 >mangling char = ^</B
11731 ></P
11732 ></DD
11733 ><DT
11734 ><A
11735 NAME="MANGLINGMETHOD"
11736 ></A
11737 >mangling mathod(G)</DT
11738 ><DD
11739 ><P
11740 > controls the algorithm used for the generating
11741                 the mangled names. Can take two different values, "hash" and
11742                 "hash2". "hash" is  the default and is the algorithm that has been
11743                 used in Samba for many years. "hash2" is a newer and considered
11744                 a better algorithm (generates less collisions) in the names.
11745                 However, many Win32 applications store the mangled names and so
11746                 changing to the new algorithm must not be done
11747                 lightly as these applications may break unless reinstalled.
11748                 New installations of Samba may set the default to hash2.</P
11749 ><P
11750 >Default: <B
11751 CLASS="COMMAND"
11752 >mangling method = hash</B
11753 ></P
11754 ><P
11755 >Example: <B
11756 CLASS="COMMAND"
11757 >mangling method = hash2</B
11758 ></P
11759 ></DD
11760 ><DT
11761 ><A
11762 NAME="MAPARCHIVE"
11763 ></A
11764 >map archive (S)</DT
11765 ><DD
11766 ><P
11767 >This controls whether the DOS archive attribute
11768                 should be mapped to the UNIX owner execute bit.  The DOS archive bit
11769                 is set when a file has been modified since its last backup.  One
11770                 motivation for this option it to keep Samba/your PC from making
11771                 any file it touches from becoming executable under UNIX.  This can
11772                 be quite annoying for shared source code, documents, etc...</P
11773 ><P
11774 >Note that this requires the <TT
11775 CLASS="PARAMETER"
11776 ><I
11777 >create mask</I
11778 ></TT
11779 >
11780                 parameter to be set such that owner execute bit is not masked out
11781                 (i.e. it must include 100). See the parameter <A
11782 HREF="#CREATEMASK"
11783 >               <TT
11784 CLASS="PARAMETER"
11785 ><I
11786 >create mask</I
11787 ></TT
11788 ></A
11789 > for details.</P
11790 ><P
11791 >Default: <B
11792 CLASS="COMMAND"
11793 >map archive = yes</B
11794 ></P
11795 ></DD
11796 ><DT
11797 ><A
11798 NAME="MAPHIDDEN"
11799 ></A
11800 >map hidden (S)</DT
11801 ><DD
11802 ><P
11803 >This controls whether DOS style hidden files
11804                 should be mapped to the UNIX world execute bit.</P
11805 ><P
11806 >Note that this requires the <TT
11807 CLASS="PARAMETER"
11808 ><I
11809 >create mask</I
11810 ></TT
11811 >
11812                 to be set such that the world execute bit is not masked out (i.e.
11813                 it must include 001). See the parameter <A
11814 HREF="#CREATEMASK"
11815 >               <TT
11816 CLASS="PARAMETER"
11817 ><I
11818 >create mask</I
11819 ></TT
11820 ></A
11821 > for details.</P
11822 ><P
11823 >Default: <B
11824 CLASS="COMMAND"
11825 >map hidden = no</B
11826 ></P
11827 ></DD
11828 ><DT
11829 ><A
11830 NAME="MAPSYSTEM"
11831 ></A
11832 >map system (S)</DT
11833 ><DD
11834 ><P
11835 >This controls whether DOS style system files
11836                 should be mapped to the UNIX group execute bit.</P
11837 ><P
11838 >Note that this requires the <TT
11839 CLASS="PARAMETER"
11840 ><I
11841 >create mask</I
11842 ></TT
11843 >
11844                 to be set such that the group execute bit is not masked out (i.e.
11845                 it must include 010). See the parameter <A
11846 HREF="#CREATEMASK"
11847 >               <TT
11848 CLASS="PARAMETER"
11849 ><I
11850 >create mask</I
11851 ></TT
11852 ></A
11853 > for details.</P
11854 ><P
11855 >Default: <B
11856 CLASS="COMMAND"
11857 >map system = no</B
11858 ></P
11859 ></DD
11860 ><DT
11861 ><A
11862 NAME="MAPTOGUEST"
11863 ></A
11864 >map to guest (G)</DT
11865 ><DD
11866 ><P
11867 >This parameter is only useful in <A
11868 HREF="#SECURITY"
11869 >               security</A
11870 > modes other than <TT
11871 CLASS="PARAMETER"
11872 ><I
11873 >security = share</I
11874 ></TT
11875 >
11876                 - i.e. <TT
11877 CLASS="CONSTANT"
11878 >user</TT
11879 >, <TT
11880 CLASS="CONSTANT"
11881 >server</TT
11882 >,
11883                 and <TT
11884 CLASS="CONSTANT"
11885 >domain</TT
11886 >.</P
11887 ><P
11888 >This parameter can take three different values, which tell
11889                 <A
11890 HREF="smbd.8.html"
11891 TARGET="_top"
11892 >smbd(8)</A
11893 > what to do with user
11894                 login requests that don't match a valid UNIX user in some way.</P
11895 ><P
11896 >The three settings are :</P
11897 ><P
11898 ></P
11899 ><UL
11900 ><LI
11901 ><P
11902 ><TT
11903 CLASS="CONSTANT"
11904 >Never</TT
11905 > - Means user login
11906                         requests with an invalid password are rejected. This is the
11907                         default.</P
11908 ></LI
11909 ><LI
11910 ><P
11911 ><TT
11912 CLASS="CONSTANT"
11913 >Bad User</TT
11914 > - Means user
11915                         logins with an invalid password are rejected, unless the username
11916                         does not exist, in which case it is treated as a guest login and
11917                         mapped into the <A
11918 HREF="#GUESTACCOUNT"
11919 ><TT
11920 CLASS="PARAMETER"
11921 ><I
11922 >                       guest account</I
11923 ></TT
11924 ></A
11925 >.</P
11926 ></LI
11927 ><LI
11928 ><P
11929 ><TT
11930 CLASS="CONSTANT"
11931 >Bad Password</TT
11932 > - Means user logins
11933                         with an invalid password are treated as a guest login and mapped
11934                         into the <A
11935 HREF="#GUESTACCOUNT"
11936 >guest account</A
11937 >. Note that
11938                         this can cause problems as it means that any user incorrectly typing
11939                         their password will be silently logged on as "guest" - and
11940                         will not know the reason they cannot access files they think
11941                         they should - there will have been no message given to them
11942                         that they got their password wrong. Helpdesk services will
11943                         <EM
11944 >hate</EM
11945 > you if you set the <TT
11946 CLASS="PARAMETER"
11947 ><I
11948 >map to
11949                         guest</I
11950 ></TT
11951 > parameter this way :-).</P
11952 ></LI
11953 ></UL
11954 ><P
11955 >Note that this parameter is needed to set up "Guest"
11956                 share services when using <TT
11957 CLASS="PARAMETER"
11958 ><I
11959 >security</I
11960 ></TT
11961 > modes other than
11962                 share. This is because in these modes the name of the resource being
11963                 requested is <EM
11964 >not</EM
11965 > sent to the server until after
11966                 the server has successfully authenticated the client so the server
11967                 cannot make authentication decisions at the correct time (connection
11968                 to the share) for "Guest" shares.</P
11969 ><P
11970 >For people familiar with the older Samba releases, this
11971                 parameter maps to the old compile-time setting of the <TT
11972 CLASS="CONSTANT"
11973 >               GUEST_SESSSETUP</TT
11974 > value in local.h.</P
11975 ><P
11976 >Default: <B
11977 CLASS="COMMAND"
11978 >map to guest = Never</B
11979 ></P
11980 ><P
11981 >Example: <B
11982 CLASS="COMMAND"
11983 >map to guest = Bad User</B
11984 ></P
11985 ></DD
11986 ><DT
11987 ><A
11988 NAME="MAXCONNECTIONS"
11989 ></A
11990 >max connections (S)</DT
11991 ><DD
11992 ><P
11993 >This option allows the number of simultaneous
11994                 connections to a service to be limited. If <TT
11995 CLASS="PARAMETER"
11996 ><I
11997 >max connections
11998                 </I
11999 ></TT
12000 > is greater than 0 then connections will be refused if
12001                 this number of connections to the service are already open. A value
12002                 of zero mean an unlimited number of connections may be made.</P
12003 ><P
12004 >Record lock files are used to implement this feature. The
12005                 lock files will be stored in the directory specified by the <A
12006 HREF="#LOCKDIRECTORY"
12007 ><TT
12008 CLASS="PARAMETER"
12009 ><I
12010 >lock directory</I
12011 ></TT
12012 ></A
12013 >
12014                 option.</P
12015 ><P
12016 >Default: <B
12017 CLASS="COMMAND"
12018 >max connections = 0</B
12019 ></P
12020 ><P
12021 >Example: <B
12022 CLASS="COMMAND"
12023 >max connections = 10</B
12024 ></P
12025 ></DD
12026 ><DT
12027 ><A
12028 NAME="MAXDISKSIZE"
12029 ></A
12030 >max disk size (G)</DT
12031 ><DD
12032 ><P
12033 >This option allows you to put an upper limit
12034                 on the apparent size of disks. If you set this option to 100
12035                 then all shares will appear to be not larger than 100 MB in
12036                 size.</P
12037 ><P
12038 >Note that this option does not limit the amount of
12039                 data you can put on the disk. In the above case you could still
12040                 store much more than 100 MB on the disk, but if a client ever asks
12041                 for the amount of free disk space or the total disk size then the
12042                 result will be bounded by the amount specified in <TT
12043 CLASS="PARAMETER"
12044 ><I
12045 >max
12046                 disk size</I
12047 ></TT
12048 >.</P
12049 ><P
12050 >This option is primarily useful to work around bugs
12051                 in some pieces of software that can't handle very large disks,
12052                 particularly disks over 1GB in size.</P
12053 ><P
12054 >A <TT
12055 CLASS="PARAMETER"
12056 ><I
12057 >max disk size</I
12058 ></TT
12059 > of 0 means no limit.</P
12060 ><P
12061 >Default: <B
12062 CLASS="COMMAND"
12063 >max disk size = 0</B
12064 ></P
12065 ><P
12066 >Example: <B
12067 CLASS="COMMAND"
12068 >max disk size = 1000</B
12069 ></P
12070 ></DD
12071 ><DT
12072 ><A
12073 NAME="MAXLOGSIZE"
12074 ></A
12075 >max log size (G)</DT
12076 ><DD
12077 ><P
12078 >This option (an integer in kilobytes) specifies
12079                 the max size the log file should grow to. Samba periodically checks
12080                 the size and if it is exceeded it will rename the file, adding
12081                 a <TT
12082 CLASS="FILENAME"
12083 >.old</TT
12084 > extension.</P
12085 ><P
12086 >A size of 0 means no limit.</P
12087 ><P
12088 >Default: <B
12089 CLASS="COMMAND"
12090 >max log size = 5000</B
12091 ></P
12092 ><P
12093 >Example: <B
12094 CLASS="COMMAND"
12095 >max log size = 1000</B
12096 ></P
12097 ></DD
12098 ><DT
12099 ><A
12100 NAME="MAXMUX"
12101 ></A
12102 >max mux (G)</DT
12103 ><DD
12104 ><P
12105 >This option controls the maximum number of
12106                 outstanding simultaneous SMB operations that Samba tells the client
12107                 it will allow. You should never need to set this parameter.</P
12108 ><P
12109 >Default: <B
12110 CLASS="COMMAND"
12111 >max mux = 50</B
12112 ></P
12113 ></DD
12114 ><DT
12115 ><A
12116 NAME="MAXOPENFILES"
12117 ></A
12118 >max open files (G)</DT
12119 ><DD
12120 ><P
12121 >This parameter limits the maximum number of
12122                 open files that one <A
12123 HREF="smbd.8.html"
12124 TARGET="_top"
12125 >smbd(8)</A
12126 > file
12127                 serving process may have open for a client at any one time. The
12128                 default for this parameter is set very high (10,000) as Samba uses
12129                 only one bit per unopened file.</P
12130 ><P
12131 >The limit of the number of open files is usually set
12132                 by the UNIX per-process file descriptor limit rather than
12133                 this parameter so you should never need to touch this parameter.</P
12134 ><P
12135 >Default: <B
12136 CLASS="COMMAND"
12137 >max open files = 10000</B
12138 ></P
12139 ></DD
12140 ><DT
12141 ><A
12142 NAME="MAXPRINTJOBS"
12143 ></A
12144 >max print jobs (S)</DT
12145 ><DD
12146 ><P
12147 >This parameter limits the maximum number of
12148                 jobs allowable in a Samba printer queue at any given moment.
12149                 If this number is exceeded, <A
12150 HREF="smbd.8.html"
12151 TARGET="_top"
12152 ><B
12153 CLASS="COMMAND"
12154 >               smbd(8)</B
12155 ></A
12156 > will remote "Out of Space" to the client.
12157                 See all <A
12158 HREF="#TOTALPRINTJOBS"
12159 ><TT
12160 CLASS="PARAMETER"
12161 ><I
12162 >total
12163                 print jobs</I
12164 ></TT
12165 ></A
12166 >.
12167                 </P
12168 ><P
12169 >Default: <B
12170 CLASS="COMMAND"
12171 >max print jobs = 1000</B
12172 ></P
12173 ><P
12174 >Example: <B
12175 CLASS="COMMAND"
12176 >max print jobs = 5000</B
12177 ></P
12178 ></DD
12179 ><DT
12180 ><A
12181 NAME="MAXPROTOCOL"
12182 ></A
12183 >max protocol (G)</DT
12184 ><DD
12185 ><P
12186 >The value of the parameter (a string) is the highest
12187                 protocol level that will be supported by the server.</P
12188 ><P
12189 >Possible values are :</P
12190 ><P
12191 ></P
12192 ><UL
12193 ><LI
12194 ><P
12195 ><TT
12196 CLASS="CONSTANT"
12197 >CORE</TT
12198 >: Earliest version. No
12199                         concept of user names.</P
12200 ></LI
12201 ><LI
12202 ><P
12203 ><TT
12204 CLASS="CONSTANT"
12205 >COREPLUS</TT
12206 >: Slight improvements on
12207                         CORE for efficiency.</P
12208 ></LI
12209 ><LI
12210 ><P
12211 ><TT
12212 CLASS="CONSTANT"
12213 >LANMAN1</TT
12214 >: First <EM
12215 >                       modern</EM
12216 > version of the protocol. Long filename
12217                         support.</P
12218 ></LI
12219 ><LI
12220 ><P
12221 ><TT
12222 CLASS="CONSTANT"
12223 >LANMAN2</TT
12224 >: Updates to Lanman1 protocol.
12225                         </P
12226 ></LI
12227 ><LI
12228 ><P
12229 ><TT
12230 CLASS="CONSTANT"
12231 >NT1</TT
12232 >: Current up to date version of
12233                         the protocol. Used by Windows NT. Known as CIFS.</P
12234 ></LI
12235 ></UL
12236 ><P
12237 >Normally this option should not be set as the automatic
12238                 negotiation phase in the SMB protocol takes care of choosing
12239                 the appropriate protocol.</P
12240 ><P
12241 >See also <A
12242 HREF="#MINPROTOCOL"
12243 ><TT
12244 CLASS="PARAMETER"
12245 ><I
12246 >min
12247                 protocol</I
12248 ></TT
12249 ></A
12250 ></P
12251 ><P
12252 >Default: <B
12253 CLASS="COMMAND"
12254 >max protocol = NT1</B
12255 ></P
12256 ><P
12257 >Example: <B
12258 CLASS="COMMAND"
12259 >max protocol = LANMAN1</B
12260 ></P
12261 ></DD
12262 ><DT
12263 ><A
12264 NAME="MAXSMBDPROCESSES"
12265 ></A
12266 >max smbd processes (G)</DT
12267 ><DD
12268 ><P
12269 >This parameter limits the maximum number of
12270                 <A
12271 HREF="smbd.8.html"
12272 TARGET="_top"
12273 ><B
12274 CLASS="COMMAND"
12275 >smbd(8)</B
12276 ></A
12277 >
12278                 processes concurrently running on a system and is intended
12279                 as a stopgap to prevent degrading service to clients in the event
12280                 that the server has insufficient resources to handle more than this
12281                 number of connections.  Remember that under normal operating
12282                 conditions, each user will have an <A
12283 HREF="smbd.8.html"
12284 TARGET="_top"
12285 >smbd</A
12286 > associated with him or her
12287                 to handle connections to all shares from a given host.
12288                 </P
12289 ><P
12290 >Default: <B
12291 CLASS="COMMAND"
12292 >max smbd processes = 0</B
12293 >   ## no limit</P
12294 ><P
12295 >Example: <B
12296 CLASS="COMMAND"
12297 >max smbd processes = 1000</B
12298 ></P
12299 ></DD
12300 ><DT
12301 ><A
12302 NAME="MAXTTL"
12303 ></A
12304 >max ttl (G)</DT
12305 ><DD
12306 ><P
12307 >This option tells <A
12308 HREF="nmbd.8.html"
12309 TARGET="_top"
12310 >nmbd(8)</A
12311 >
12312                 what the default 'time to live' of NetBIOS names should be (in seconds)
12313                 when <B
12314 CLASS="COMMAND"
12315 >nmbd</B
12316 > is requesting a name using either a
12317                 broadcast packet or from a WINS server. You should never need to
12318                 change this parameter. The default is 3 days.</P
12319 ><P
12320 >Default: <B
12321 CLASS="COMMAND"
12322 >max ttl = 259200</B
12323 ></P
12324 ></DD
12325 ><DT
12326 ><A
12327 NAME="MAXWINSTTL"
12328 ></A
12329 >max wins ttl (G)</DT
12330 ><DD
12331 ><P
12332 >This option tells <A
12333 HREF="nmbd.8.html"
12334 TARGET="_top"
12335 >nmbd(8)
12336                 </A
12337 > when acting as a WINS server (<A
12338 HREF="#WINSSUPPORT"
12339 >               <TT
12340 CLASS="PARAMETER"
12341 ><I
12342 >wins support = yes</I
12343 ></TT
12344 ></A
12345 >) what the maximum
12346                 'time to live' of NetBIOS names that <B
12347 CLASS="COMMAND"
12348 >nmbd</B
12349 >
12350                 will grant will be (in seconds). You should never need to change this
12351                 parameter.  The default is 6 days (518400 seconds).</P
12352 ><P
12353 >See also the <A
12354 HREF="#MINWINSTTL"
12355 ><TT
12356 CLASS="PARAMETER"
12357 ><I
12358 >min
12359                 wins ttl</I
12360 ></TT
12361 ></A
12362 > parameter.</P
12363 ><P
12364 >Default: <B
12365 CLASS="COMMAND"
12366 >max wins ttl = 518400</B
12367 ></P
12368 ></DD
12369 ><DT
12370 ><A
12371 NAME="MAXXMIT"
12372 ></A
12373 >max xmit (G)</DT
12374 ><DD
12375 ><P
12376 >This option controls the maximum packet size
12377                 that will be negotiated by Samba. The default in Samba 2.2.6 is
12378                 now 16644 (changed from 65535 in earlier releases) which matches
12379                 Windows 2000. This allows better performance with Windows NT clients.
12380                 The maximum is 65535. In some cases you may find you get better performance
12381                 with a smaller value. A value below 2048 is likely to cause problems.
12382                 </P
12383 ><P
12384 >Default: <B
12385 CLASS="COMMAND"
12386 >max xmit = 16644</B
12387 ></P
12388 ><P
12389 >Example: <B
12390 CLASS="COMMAND"
12391 >max xmit = 8192</B
12392 ></P
12393 ></DD
12394 ><DT
12395 ><A
12396 NAME="MESSAGECOMMAND"
12397 ></A
12398 >message command (G)</DT
12399 ><DD
12400 ><P
12401 >This specifies what command to run when the
12402                 server receives a WinPopup style message.</P
12403 ><P
12404 >This would normally be a command that would
12405                 deliver the message somehow. How this is to be done is
12406                 up to your imagination.</P
12407 ><P
12408 >An example is:</P
12409 ><P
12410 ><B
12411 CLASS="COMMAND"
12412 >message command = csh -c 'xedit %s;rm %s' &#38;</B
12413 >
12414                 </P
12415 ><P
12416 >This delivers the message using <B
12417 CLASS="COMMAND"
12418 >xedit</B
12419 >, then
12420                 removes it afterwards. <EM
12421 >NOTE THAT IT IS VERY IMPORTANT
12422                 THAT THIS COMMAND RETURN IMMEDIATELY</EM
12423 >. That's why I
12424                 have the '&#38;' on the end. If it doesn't return immediately then
12425                 your PCs may freeze when sending messages (they should recover
12426                 after 30 seconds, hopefully).</P
12427 ><P
12428 >All messages are delivered as the global guest user.
12429                 The command takes the standard substitutions, although <TT
12430 CLASS="PARAMETER"
12431 ><I
12432 >               %u</I
12433 ></TT
12434 > won't work (<TT
12435 CLASS="PARAMETER"
12436 ><I
12437 >%U</I
12438 ></TT
12439 > may be better
12440                 in this case).</P
12441 ><P
12442 >Apart from the standard substitutions, some additional
12443                 ones apply. In particular:</P
12444 ><P
12445 ></P
12446 ><UL
12447 ><LI
12448 ><P
12449 ><TT
12450 CLASS="PARAMETER"
12451 ><I
12452 >%s</I
12453 ></TT
12454 > = the filename containing
12455                         the message.</P
12456 ></LI
12457 ><LI
12458 ><P
12459 ><TT
12460 CLASS="PARAMETER"
12461 ><I
12462 >%t</I
12463 ></TT
12464 > = the destination that
12465                         the message was sent to (probably the server name).</P
12466 ></LI
12467 ><LI
12468 ><P
12469 ><TT
12470 CLASS="PARAMETER"
12471 ><I
12472 >%f</I
12473 ></TT
12474 > = who the message
12475                         is from.</P
12476 ></LI
12477 ></UL
12478 ><P
12479 >You could make this command send mail, or whatever else
12480                 takes your fancy. Please let us know of any really interesting
12481                 ideas you have.</P
12482 ><P
12483 >Here's a way of sending the messages as mail to root:</P
12484 ><P
12485 ><B
12486 CLASS="COMMAND"
12487 >message command = /bin/mail -s 'message from %f on
12488                 %m' root &#60; %s; rm %s</B
12489 ></P
12490 ><P
12491 >If you don't have a message command then the message
12492                 won't be delivered and Samba will tell the sender there was
12493                 an error. Unfortunately WfWg totally ignores the error code
12494                 and carries on regardless, saying that the message was delivered.
12495                 </P
12496 ><P
12497 >If you want to silently delete it then try:</P
12498 ><P
12499 ><B
12500 CLASS="COMMAND"
12501 >message command = rm %s</B
12502 ></P
12503 ><P
12504 >Default: <EM
12505 >no message command</EM
12506 ></P
12507 ><P
12508 >Example: <B
12509 CLASS="COMMAND"
12510 >message command = csh -c 'xedit %s;
12511                 rm %s' &#38;</B
12512 ></P
12513 ></DD
12514 ><DT
12515 ><A
12516 NAME="MINPASSWDLENGTH"
12517 ></A
12518 >min passwd length (G)</DT
12519 ><DD
12520 ><P
12521 >Synonym for <A
12522 HREF="#MINPASSWORDLENGTH"
12523 >               <TT
12524 CLASS="PARAMETER"
12525 ><I
12526 >min password length</I
12527 ></TT
12528 ></A
12529 >.</P
12530 ></DD
12531 ><DT
12532 ><A
12533 NAME="MINPASSWORDLENGTH"
12534 ></A
12535 >min password length (G)</DT
12536 ><DD
12537 ><P
12538 >This option sets the minimum length in characters
12539                 of a plaintext password that <B
12540 CLASS="COMMAND"
12541 >smbd</B
12542 > will accept when performing
12543                 UNIX password changing.</P
12544 ><P
12545 >See also <A
12546 HREF="#UNIXPASSWORDSYNC"
12547 ><TT
12548 CLASS="PARAMETER"
12549 ><I
12550 >unix
12551                 password sync</I
12552 ></TT
12553 ></A
12554 >, <A
12555 HREF="#PASSWDPROGRAM"
12556 >               <TT
12557 CLASS="PARAMETER"
12558 ><I
12559 >passwd program</I
12560 ></TT
12561 ></A
12562 > and <A
12563 HREF="#PASSWDCHATDEBUG"
12564 ><TT
12565 CLASS="PARAMETER"
12566 ><I
12567 >passwd chat debug</I
12568 ></TT
12569 >
12570                 </A
12571 >.</P
12572 ><P
12573 >Default: <B
12574 CLASS="COMMAND"
12575 >min password length = 5</B
12576 ></P
12577 ></DD
12578 ><DT
12579 ><A
12580 NAME="MINPRINTSPACE"
12581 ></A
12582 >min print space (S)</DT
12583 ><DD
12584 ><P
12585 >This sets the minimum amount of free disk
12586                 space that must be available before a user will be able to spool
12587                 a print job. It is specified in kilobytes. The default is 0, which
12588                 means a user can always spool a print job.</P
12589 ><P
12590 >See also the <A
12591 HREF="#PRINTING"
12592 ><TT
12593 CLASS="PARAMETER"
12594 ><I
12595 >printing
12596                 </I
12597 ></TT
12598 ></A
12599 > parameter.</P
12600 ><P
12601 >Default: <B
12602 CLASS="COMMAND"
12603 >min print space = 0</B
12604 ></P
12605 ><P
12606 >Example: <B
12607 CLASS="COMMAND"
12608 >min print space = 2000</B
12609 ></P
12610 ></DD
12611 ><DT
12612 ><A
12613 NAME="MINPROTOCOL"
12614 ></A
12615 >min protocol (G)</DT
12616 ><DD
12617 ><P
12618 >The value of the parameter (a string) is the
12619                 lowest SMB protocol dialect than Samba will support.  Please refer
12620                 to the <A
12621 HREF="#MAXPROTOCOL"
12622 ><TT
12623 CLASS="PARAMETER"
12624 ><I
12625 >max protocol</I
12626 ></TT
12627 ></A
12628 >
12629                 parameter for a list of valid protocol names and a brief description
12630                 of each.  You may also wish to refer to the C source code in
12631                 <TT
12632 CLASS="FILENAME"
12633 >source/smbd/negprot.c</TT
12634 > for a listing of known protocol
12635                 dialects supported by clients.</P
12636 ><P
12637 >If you are viewing this parameter as a security measure, you should
12638                 also refer to the <A
12639 HREF="#LANMANAUTH"
12640 ><TT
12641 CLASS="PARAMETER"
12642 ><I
12643 >lanman
12644                 auth</I
12645 ></TT
12646 ></A
12647 > parameter.  Otherwise, you should never need
12648                 to change this parameter.</P
12649 ><P
12650 >Default : <B
12651 CLASS="COMMAND"
12652 >min protocol = CORE</B
12653 ></P
12654 ><P
12655 >Example : <B
12656 CLASS="COMMAND"
12657 >min protocol = NT1</B
12658 >  # disable DOS
12659                 clients</P
12660 ></DD
12661 ><DT
12662 ><A
12663 NAME="MINWINSTTL"
12664 ></A
12665 >min wins ttl (G)</DT
12666 ><DD
12667 ><P
12668 >This option tells <A
12669 HREF="nmbd.8.html"
12670 TARGET="_top"
12671 >nmbd(8)</A
12672 >
12673                 when acting as a WINS server (<A
12674 HREF="#WINSSUPPORT"
12675 ><TT
12676 CLASS="PARAMETER"
12677 ><I
12678 >               wins support = yes</I
12679 ></TT
12680 ></A
12681 >) what the minimum 'time to live'
12682                 of NetBIOS names that <B
12683 CLASS="COMMAND"
12684 >nmbd</B
12685 > will grant will be (in
12686                 seconds). You should never need to change this parameter.  The default
12687                 is 6 hours (21600 seconds).</P
12688 ><P
12689 >Default: <B
12690 CLASS="COMMAND"
12691 >min wins ttl = 21600</B
12692 ></P
12693 ></DD
12694 ><DT
12695 ><A
12696 NAME="MSDFSROOT"
12697 ></A
12698 >msdfs root (S)</DT
12699 ><DD
12700 ><P
12701 >This boolean parameter is only available if
12702                 Samba is configured  and  compiled with the <B
12703 CLASS="COMMAND"
12704 >               --with-msdfs</B
12705 > option.  If set to <TT
12706 CLASS="CONSTANT"
12707 >yes</TT
12708 >,
12709                 Samba treats the share as a Dfs root and  allows clients to browse
12710                 the distributed file system tree rooted at the share directory.
12711                 Dfs links are specified  in  the share directory by symbolic
12712                 links of the form <TT
12713 CLASS="FILENAME"
12714 >msdfs:serverA\shareA,serverB\shareB
12715                 </TT
12716 > and so on.  For more information on setting up a Dfs tree
12717                 on Samba,  refer to <A
12718 HREF="msdfs_setup.html"
12719 TARGET="_top"
12720 >msdfs_setup.html
12721                 </A
12722 >.</P
12723 ><P
12724 >See also <A
12725 HREF="#HOSTMSDFS"
12726 ><TT
12727 CLASS="PARAMETER"
12728 ><I
12729 >host msdfs
12730                 </I
12731 ></TT
12732 ></A
12733 ></P
12734 ><P
12735 >Default: <B
12736 CLASS="COMMAND"
12737 >msdfs root = no</B
12738 ></P
12739 ></DD
12740 ><DT
12741 ><A
12742 NAME="NAMERESOLVEORDER"
12743 ></A
12744 >name resolve order (G)</DT
12745 ><DD
12746 ><P
12747 >This option is used by the programs in the Samba
12748                 suite to determine what naming services to use and in what order
12749                 to resolve host names to IP addresses. The option takes a space
12750                 separated string of name resolution options.</P
12751 ><P
12752 >The options are :"lmhosts", "host", "wins" and "bcast". They
12753                 cause names to be resolved as follows :</P
12754 ><P
12755 ></P
12756 ><UL
12757 ><LI
12758 ><P
12759 ><TT
12760 CLASS="CONSTANT"
12761 >lmhosts</TT
12762 > : Lookup an IP
12763                         address in the Samba lmhosts file. If the line in lmhosts has
12764                         no name type attached to the NetBIOS name (see the <A
12765 HREF="lmhosts.5.html"
12766 TARGET="_top"
12767 >lmhosts(5)</A
12768 > for details) then
12769                         any name type matches for lookup.</P
12770 ></LI
12771 ><LI
12772 ><P
12773 ><TT
12774 CLASS="CONSTANT"
12775 >host</TT
12776 > : Do a standard host
12777                         name to IP address resolution, using the system <TT
12778 CLASS="FILENAME"
12779 >/etc/hosts
12780                         </TT
12781 >, NIS, or DNS lookups. This method of name resolution
12782                         is operating system depended for instance on IRIX or Solaris this
12783                         may be controlled by the <TT
12784 CLASS="FILENAME"
12785 >/etc/nsswitch.conf</TT
12786 >
12787                         file.  Note that this method is only used if the NetBIOS name
12788                         type being queried is the 0x20 (server) name type, otherwise
12789                         it is ignored.</P
12790 ></LI
12791 ><LI
12792 ><P
12793 ><TT
12794 CLASS="CONSTANT"
12795 >wins</TT
12796 > : Query a name with
12797                         the IP address listed in the <A
12798 HREF="#WINSSERVER"
12799 ><TT
12800 CLASS="PARAMETER"
12801 ><I
12802 >                       wins server</I
12803 ></TT
12804 ></A
12805 > parameter.  If no WINS server has
12806                         been specified this method will be ignored.</P
12807 ></LI
12808 ><LI
12809 ><P
12810 ><TT
12811 CLASS="CONSTANT"
12812 >bcast</TT
12813 > : Do a broadcast on
12814                         each of the known local interfaces listed in the <A
12815 HREF="#INTERFACES"
12816 ><TT
12817 CLASS="PARAMETER"
12818 ><I
12819 >interfaces</I
12820 ></TT
12821 ></A
12822 >
12823                         parameter. This is the least reliable of the name resolution
12824                         methods as it depends on the target host being on a locally
12825                         connected subnet.</P
12826 ></LI
12827 ></UL
12828 ><P
12829 >Default: <B
12830 CLASS="COMMAND"
12831 >name resolve order = lmhosts host wins bcast
12832                 </B
12833 ></P
12834 ><P
12835 >Example: <B
12836 CLASS="COMMAND"
12837 >name resolve order = lmhosts bcast host
12838                 </B
12839 ></P
12840 ><P
12841 >This will cause the local lmhosts file to be examined
12842                 first, followed by a broadcast attempt, followed by a normal
12843                 system hostname lookup.</P
12844 ></DD
12845 ><DT
12846 ><A
12847 NAME="NETBIOSALIASES"
12848 ></A
12849 >netbios aliases (G)</DT
12850 ><DD
12851 ><P
12852 >This is a list of NetBIOS names that <A
12853 HREF="nmbd.8.html"
12854 TARGET="_top"
12855 >nmbd(8)</A
12856 > will advertise as additional
12857                 names by which the Samba server is known. This allows one machine
12858                 to appear in browse lists under multiple names. If a machine is
12859                 acting as a browse server or logon server none
12860                 of these names will be advertised as either browse server or logon
12861                 servers, only the primary name of the machine will be advertised
12862                 with these capabilities.</P
12863 ><P
12864 >See also <A
12865 HREF="#NETBIOSNAME"
12866 ><TT
12867 CLASS="PARAMETER"
12868 ><I
12869 >netbios
12870                 name</I
12871 ></TT
12872 ></A
12873 >.</P
12874 ><P
12875 >Default: <EM
12876 >empty string (no additional names)</EM
12877 ></P
12878 ><P
12879 >Example: <B
12880 CLASS="COMMAND"
12881 >netbios aliases = TEST TEST1 TEST2</B
12882 ></P
12883 ></DD
12884 ><DT
12885 ><A
12886 NAME="NETBIOSNAME"
12887 ></A
12888 >netbios name (G)</DT
12889 ><DD
12890 ><P
12891 >This sets the NetBIOS name by which a Samba
12892                 server is known. By default it is the same as the first component
12893                 of the host's DNS name. If a machine is a browse server or
12894                 logon server this name (or the first component
12895                 of the hosts DNS name) will be the name that these services are
12896                 advertised under.</P
12897 ><P
12898 >See also <A
12899 HREF="#NETBIOSALIASES"
12900 ><TT
12901 CLASS="PARAMETER"
12902 ><I
12903 >netbios
12904                 aliases</I
12905 ></TT
12906 ></A
12907 >.</P
12908 ><P
12909 >Default: <EM
12910 >machine DNS name</EM
12911 ></P
12912 ><P
12913 >Example: <B
12914 CLASS="COMMAND"
12915 >netbios name = MYNAME</B
12916 ></P
12917 ></DD
12918 ><DT
12919 ><A
12920 NAME="NETBIOSSCOPE"
12921 ></A
12922 >netbios scope (G)</DT
12923 ><DD
12924 ><P
12925 >This sets the NetBIOS scope that Samba will
12926                 operate under. This should not be set unless every machine
12927                 on your LAN also sets this value.</P
12928 ></DD
12929 ><DT
12930 ><A
12931 NAME="NISHOMEDIR"
12932 ></A
12933 >nis homedir (G)</DT
12934 ><DD
12935 ><P
12936 >Get the home share server from a NIS map. For
12937                 UNIX systems that use an automounter, the user's home directory
12938                 will often be mounted on a workstation on demand from a remote
12939                 server. </P
12940 ><P
12941 >When the Samba logon server is not the actual home directory
12942                 server, but is mounting the home directories via NFS then two
12943                 network hops would be required to access the users home directory
12944                 if the logon server told the client to use itself as the SMB server
12945                 for home directories (one over SMB and one over NFS). This can
12946                 be very slow.</P
12947 ><P
12948 >This option allows Samba to return the home share as
12949                 being on a different server to the logon server and as
12950                 long as a Samba daemon is running on the home directory server,
12951                 it will be mounted on the Samba client directly from the directory
12952                 server. When Samba is returning the home share to the client, it
12953                 will consult the NIS map specified in <A
12954 HREF="#HOMEDIRMAP"
12955 >               <TT
12956 CLASS="PARAMETER"
12957 ><I
12958 >homedir map</I
12959 ></TT
12960 ></A
12961 > and return the server
12962                 listed there.</P
12963 ><P
12964 >Note that for this option to work there must be a working
12965                 NIS system and the Samba server with this option must also
12966                 be a logon server.</P
12967 ><P
12968 >Default: <B
12969 CLASS="COMMAND"
12970 >nis homedir = no</B
12971 ></P
12972 ></DD
12973 ><DT
12974 ><A
12975 NAME="NTACLSUPPORT"
12976 ></A
12977 >nt acl support (S)</DT
12978 ><DD
12979 ><P
12980 >This boolean parameter controls whether
12981                 <A
12982 HREF="smbd.8.html"
12983 TARGET="_top"
12984 >smbd(8)</A
12985 > will attempt to map
12986                 UNIX permissions into Windows NT access control lists.
12987                 This parameter was formally a global parameter in releases
12988                 prior to 2.2.2.</P
12989 ><P
12990 >Default: <B
12991 CLASS="COMMAND"
12992 >nt acl support = yes</B
12993 ></P
12994 ></DD
12995 ><DT
12996 ><A
12997 NAME="NTPIPESUPPORT"
12998 ></A
12999 >nt pipe support (G)</DT
13000 ><DD
13001 ><P
13002 >This boolean parameter controls whether
13003                 <A
13004 HREF="smbd.8.html"
13005 TARGET="_top"
13006 >smbd(8)</A
13007 > will allow Windows NT
13008                 clients to connect to the NT SMB specific <TT
13009 CLASS="CONSTANT"
13010 >IPC$</TT
13011 >
13012                 pipes. This is a developer debugging option and can be left
13013                 alone.</P
13014 ><P
13015 >Default: <B
13016 CLASS="COMMAND"
13017 >nt pipe support = yes</B
13018 ></P
13019 ></DD
13020 ><DT
13021 ><A
13022 NAME="NTSMBSUPPORT"
13023 ></A
13024 >nt smb support (G)</DT
13025 ><DD
13026 ><P
13027 >This boolean parameter controls whether <A
13028 HREF="smbd.8.html"
13029 TARGET="_top"
13030 >smbd(8)</A
13031 > will negotiate NT specific SMB
13032                 support with Windows NT/2k/XP clients. Although this is a developer
13033                 debugging option and should be left alone, benchmarking has discovered
13034                 that Windows NT clients give faster performance with this option
13035                 set to <TT
13036 CLASS="CONSTANT"
13037 >no</TT
13038 >. This is still being investigated.
13039                 If this option is set to <TT
13040 CLASS="CONSTANT"
13041 >no</TT
13042 > then Samba offers
13043                 exactly the same SMB calls that versions prior to Samba 2.0 offered.
13044                 This information may be of use if any users are having problems
13045                 with NT SMB support.</P
13046 ><P
13047 >You should not need to ever disable this parameter.</P
13048 ><P
13049 >Default: <B
13050 CLASS="COMMAND"
13051 >nt smb support = yes</B
13052 ></P
13053 ></DD
13054 ><DT
13055 ><A
13056 NAME="NTSTATUSSUPPORT"
13057 ></A
13058 >nt status support (G)</DT
13059 ><DD
13060 ><P
13061 >This boolean parameter controls whether <A
13062 HREF="smbd.8.html"
13063 TARGET="_top"
13064 >smbd(8)</A
13065 > will negotiate NT specific status
13066                 support with Windows NT/2k/XP clients. This is a developer
13067                 debugging option and should be left alone.
13068                 If this option is set to <TT
13069 CLASS="CONSTANT"
13070 >no</TT
13071 > then Samba offers
13072                 exactly the same DOS error codes that versions prior to Samba 2.2.3
13073                 reported.</P
13074 ><P
13075 >You should not need to ever disable this parameter.</P
13076 ><P
13077 >Default: <B
13078 CLASS="COMMAND"
13079 >nt status support = yes</B
13080 ></P
13081 ></DD
13082 ><DT
13083 ><A
13084 NAME="NULLPASSWORDS"
13085 ></A
13086 >null passwords (G)</DT
13087 ><DD
13088 ><P
13089 >Allow or disallow client access to accounts
13090                 that have null passwords. </P
13091 ><P
13092 >See also <A
13093 HREF="smbpasswd.5.html"
13094 TARGET="_top"
13095 >smbpasswd (5)</A
13096 >.</P
13097 ><P
13098 >Default: <B
13099 CLASS="COMMAND"
13100 >null passwords = no</B
13101 ></P
13102 ></DD
13103 ><DT
13104 ><A
13105 NAME="OBEYPAMRESTRICTIONS"
13106 ></A
13107 >obey pam restrictions (G)</DT
13108 ><DD
13109 ><P
13110 >When Samba 2.2 is configured to enable PAM support
13111                 (i.e. --with-pam), this parameter will control whether or not Samba
13112                 should obey PAM's account and session management directives.  The
13113                 default behavior is to use PAM for clear text authentication only
13114                 and to ignore any account or session management.  Note that Samba
13115                 always ignores PAM for authentication in the case of <A
13116 HREF="#ENCRYPTPASSWORDS"
13117 ><TT
13118 CLASS="PARAMETER"
13119 ><I
13120 >encrypt passwords = yes</I
13121 ></TT
13122 >
13123                 </A
13124 >.  The reason is that PAM modules cannot support the challenge/response
13125                 authentication mechanism needed in the presence of SMB password encryption.
13126                 </P
13127 ><P
13128 >Default: <B
13129 CLASS="COMMAND"
13130 >obey pam restrictions = no</B
13131 ></P
13132 ></DD
13133 ><DT
13134 ><A
13135 NAME="ONLYUSER"
13136 ></A
13137 >only user (S)</DT
13138 ><DD
13139 ><P
13140 >This is a boolean option that controls whether
13141                 connections with usernames not in the <TT
13142 CLASS="PARAMETER"
13143 ><I
13144 >user</I
13145 ></TT
13146 >
13147                 list will be allowed. By default this option is disabled so that a
13148                 client can supply a username to be used by the server.  Enabling
13149                 this parameter will force the server to only user the login
13150                 names from the <TT
13151 CLASS="PARAMETER"
13152 ><I
13153 >user</I
13154 ></TT
13155 > list and is only really
13156                 useful in <A
13157 HREF="#SECURITYEQUALSSHARE"
13158 >shave level</A
13159 >
13160                 security.</P
13161 ><P
13162 >Note that this also means Samba won't try to deduce
13163                 usernames from the service name. This can be annoying for
13164                 the [homes] section. To get around this you could use <B
13165 CLASS="COMMAND"
13166 >user =
13167                 %S</B
13168 > which means your <TT
13169 CLASS="PARAMETER"
13170 ><I
13171 >user</I
13172 ></TT
13173 > list
13174                 will be just the service name, which for home directories is the
13175                 name of the user.</P
13176 ><P
13177 >See also the <A
13178 HREF="#USER"
13179 ><TT
13180 CLASS="PARAMETER"
13181 ><I
13182 >user</I
13183 ></TT
13184 >
13185                 </A
13186 > parameter.</P
13187 ><P
13188 >Default: <B
13189 CLASS="COMMAND"
13190 >only user = no</B
13191 ></P
13192 ></DD
13193 ><DT
13194 ><A
13195 NAME="ONLYGUEST"
13196 ></A
13197 >only guest (S)</DT
13198 ><DD
13199 ><P
13200 >A synonym for <A
13201 HREF="#GUESTONLY"
13202 ><TT
13203 CLASS="PARAMETER"
13204 ><I
13205 >               guest only</I
13206 ></TT
13207 ></A
13208 >.</P
13209 ></DD
13210 ><DT
13211 ><A
13212 NAME="OPLOCKBREAKWAITTIME"
13213 ></A
13214 >oplock break wait time (G)</DT
13215 ><DD
13216 ><P
13217 >This is a tuning parameter added due to bugs in
13218                 both Windows 9x and WinNT. If Samba responds to a client too
13219                 quickly when that client issues an SMB that can cause an oplock
13220                 break request, then the network client can fail and not respond
13221                 to the break request. This tuning parameter (which is set in milliseconds)
13222                 is the amount of time Samba will wait before sending an oplock break
13223                 request to such (broken) clients.</P
13224 ><P
13225 ><EM
13226 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
13227                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
13228 >.</P
13229 ><P
13230 >Default: <B
13231 CLASS="COMMAND"
13232 >oplock break wait time = 0</B
13233 ></P
13234 ></DD
13235 ><DT
13236 ><A
13237 NAME="OPLOCKCONTENTIONLIMIT"
13238 ></A
13239 >oplock contention limit (S)</DT
13240 ><DD
13241 ><P
13242 >This is a <EM
13243 >very</EM
13244 > advanced
13245                 <A
13246 HREF="smbd.8.html"
13247 TARGET="_top"
13248 >smbd(8)</A
13249 > tuning option to
13250                 improve the efficiency of the granting of oplocks under multiple
13251                 client contention for the same file.</P
13252 ><P
13253 >In brief it specifies a number, which causes <A
13254 HREF="smbd.8.html"
13255 TARGET="_top"
13256 >smbd</A
13257 > not to
13258                 grant an oplock even when requested if the approximate number of
13259                 clients contending for an oplock on the same file goes over this
13260                 limit. This causes <B
13261 CLASS="COMMAND"
13262 >smbd</B
13263 > to behave in a similar
13264                 way to Windows NT.</P
13265 ><P
13266 ><EM
13267 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
13268                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
13269 >.</P
13270 ><P
13271 >Default: <B
13272 CLASS="COMMAND"
13273 >oplock contention limit = 2</B
13274 ></P
13275 ></DD
13276 ><DT
13277 ><A
13278 NAME="OPLOCKS"
13279 ></A
13280 >oplocks (S)</DT
13281 ><DD
13282 ><P
13283 >This boolean option tells <B
13284 CLASS="COMMAND"
13285 >smbd</B
13286 > whether to
13287                 issue oplocks (opportunistic locks) to file open requests on this
13288                 share. The oplock code can dramatically (approx. 30% or more) improve
13289                 the speed of access to files on Samba servers. It allows the clients
13290                 to aggressively cache files locally and you may want to disable this
13291                 option for unreliable network environments (it is turned on by
13292                 default in Windows NT Servers).  For more information see the file
13293                 <TT
13294 CLASS="FILENAME"
13295 >Speed.txt</TT
13296 > in the Samba <TT
13297 CLASS="FILENAME"
13298 >docs/</TT
13299 >
13300                 directory.</P
13301 ><P
13302 >Oplocks may be selectively turned off on certain files with a
13303                 share. See the <A
13304 HREF="#VETOOPLOCKFILES"
13305 ><TT
13306 CLASS="PARAMETER"
13307 ><I
13308 >               veto oplock files</I
13309 ></TT
13310 ></A
13311 > parameter. On some systems
13312                 oplocks are recognized by the underlying operating system. This
13313                 allows data synchronization between all access to oplocked files,
13314                 whether it be via Samba or NFS or a local UNIX process. See the
13315                 <TT
13316 CLASS="PARAMETER"
13317 ><I
13318 >kernel oplocks</I
13319 ></TT
13320 > parameter for details.</P
13321 ><P
13322 >See also the <A
13323 HREF="#KERNELOPLOCKS"
13324 ><TT
13325 CLASS="PARAMETER"
13326 ><I
13327 >kernel
13328                 oplocks</I
13329 ></TT
13330 ></A
13331 > and <A
13332 HREF="#LEVEL2OPLOCKS"
13333 ><TT
13334 CLASS="PARAMETER"
13335 ><I
13336 >               level2 oplocks</I
13337 ></TT
13338 ></A
13339 > parameters.</P
13340 ><P
13341 >Default: <B
13342 CLASS="COMMAND"
13343 >oplocks = yes</B
13344 ></P
13345 ></DD
13346 ><DT
13347 ><A
13348 NAME="OSLEVEL"
13349 ></A
13350 >os level (G)</DT
13351 ><DD
13352 ><P
13353 >This integer value controls what level Samba
13354                 advertises itself as for browse elections. The value of this
13355                 parameter determines whether <A
13356 HREF="nmbd.8.html"
13357 TARGET="_top"
13358 >nmbd(8)</A
13359 >
13360                 has a chance of becoming a local master browser for the <TT
13361 CLASS="PARAMETER"
13362 ><I
13363 >               WORKGROUP</I
13364 ></TT
13365 > in the local broadcast area.</P
13366 ><P
13367 ><EM
13368 >Note :</EM
13369 >By default, Samba will win
13370                 a local master browsing election over all Microsoft operating
13371                 systems except a Windows NT 4.0/2000 Domain Controller.  This
13372                 means that a misconfigured Samba host can effectively isolate
13373                 a subnet for browsing purposes.  See <TT
13374 CLASS="FILENAME"
13375 >BROWSING.txt
13376                 </TT
13377 > in the Samba <TT
13378 CLASS="FILENAME"
13379 >docs/</TT
13380 > directory
13381                 for details.</P
13382 ><P
13383 >Default: <B
13384 CLASS="COMMAND"
13385 >os level = 20</B
13386 ></P
13387 ><P
13388 >Example: <B
13389 CLASS="COMMAND"
13390 >os level = 65 </B
13391 ></P
13392 ></DD
13393 ><DT
13394 ><A
13395 NAME="OS2DRIVERMAP"
13396 ></A
13397 >os2 driver map (G)</DT
13398 ><DD
13399 ><P
13400 >The parameter is used to define the absolute
13401                 path to a file containing a mapping of Windows NT printer driver
13402                 names to OS/2 printer driver names.  The format is:</P
13403 ><P
13404 >&#60;nt driver name&#62; = &#60;os2 driver
13405                 name&#62;.&#60;device name&#62;</P
13406 ><P
13407 >For example, a valid entry using the HP LaserJet 5
13408                 printer driver would appear as <B
13409 CLASS="COMMAND"
13410 >HP LaserJet 5L = LASERJET.HP
13411                 LaserJet 5L</B
13412 >.</P
13413 ><P
13414 >The need for the file is due to the printer driver namespace
13415                 problem described in the <A
13416 HREF="printer_driver2.html"
13417 TARGET="_top"
13418 >Samba
13419                 Printing HOWTO</A
13420 >.  For more details on OS/2 clients, please
13421                 refer to the <A
13422 HREF="OS2-Client-HOWTO.html"
13423 TARGET="_top"
13424 >OS2-Client-HOWTO
13425                 </A
13426 > containing in the Samba documentation.</P
13427 ><P
13428 >Default: <B
13429 CLASS="COMMAND"
13430 >os2 driver map = &#60;empty string&#62;
13431                 </B
13432 ></P
13433 ></DD
13434 ><DT
13435 ><A
13436 NAME="PAMPASSWORDCHANGE"
13437 ></A
13438 >pam password change (G)</DT
13439 ><DD
13440 ><P
13441 >With the addition of better PAM support in Samba 2.2,
13442                 this parameter, it is possible to use PAM's password change control
13443                 flag for Samba.  If enabled, then PAM will be used for password
13444                 changes when requested by an SMB client instead of the program listed in
13445                 <A
13446 HREF="#PASSWDPROGRAM"
13447 ><TT
13448 CLASS="PARAMETER"
13449 ><I
13450 >passwd program</I
13451 ></TT
13452 ></A
13453 >.
13454                 It should be possible to enable this without changing your
13455                 <A
13456 HREF="#PASSWDCHAT"
13457 ><TT
13458 CLASS="PARAMETER"
13459 ><I
13460 >passwd chat</I
13461 ></TT
13462 ></A
13463 >
13464                 parameter for most setups.
13465                 </P
13466 ><P
13467 >Default: <B
13468 CLASS="COMMAND"
13469 >pam password change = no</B
13470 ></P
13471 ></DD
13472 ><DT
13473 ><A
13474 NAME="PANICACTION"
13475 ></A
13476 >panic action (G)</DT
13477 ><DD
13478 ><P
13479 >This is a Samba developer option that allows a
13480                 system command to be called when either <A
13481 HREF="smbd.8.html"
13482 TARGET="_top"
13483 >               smbd(8)</A
13484 > or <A
13485 HREF="nmbd.8.html"
13486 TARGET="_top"
13487 >nmbd(8)</A
13488 >
13489                 crashes. This is usually used to draw attention to the fact that
13490                 a problem occurred.</P
13491 ><P
13492 >Default: <B
13493 CLASS="COMMAND"
13494 >panic action = &#60;empty string&#62;</B
13495 ></P
13496 ><P
13497 >Example: <B
13498 CLASS="COMMAND"
13499 >panic action = "/bin/sleep 90000"</B
13500 ></P
13501 ></DD
13502 ><DT
13503 ><A
13504 NAME="PASSWDCHAT"
13505 ></A
13506 >passwd chat (G)</DT
13507 ><DD
13508 ><P
13509 >This string controls the <EM
13510 >"chat"</EM
13511 >
13512                 conversation that takes places between <A
13513 HREF="smbd.8.html"
13514 TARGET="_top"
13515 >smbd</A
13516 > and the local password changing
13517                 program to change the user's password. The string describes a
13518                 sequence of response-receive pairs that <A
13519 HREF="smbd.8.html"
13520 TARGET="_top"
13521 >               smbd(8)</A
13522 > uses to determine what to send to the
13523                 <A
13524 HREF="#PASSWDPROGRAM"
13525 ><TT
13526 CLASS="PARAMETER"
13527 ><I
13528 >passwd program</I
13529 ></TT
13530 >
13531                 </A
13532 > and what to expect back. If the expected output is not
13533                 received then the password is not changed.</P
13534 ><P
13535 >This chat sequence is often quite site specific, depending
13536                 on what local methods are used for password control (such as NIS
13537                 etc).</P
13538 ><P
13539 >Note that this parameter only is only used if the <A
13540 HREF="#UNIXPASSWORDSYNC"
13541 ><TT
13542 CLASS="PARAMETER"
13543 ><I
13544 >unix
13545                 password sync</I
13546 ></TT
13547 ></A
13548 > parameter is set to <TT
13549 CLASS="CONSTANT"
13550 >yes</TT
13551 >. This
13552                 sequence is then called <EM
13553 >AS ROOT</EM
13554 > when the SMB password
13555                 in the smbpasswd file is being changed, without access to the old
13556                 password cleartext. This means that root must be able to reset the user's password
13557                 without knowing the text of the previous password. In the presence of NIS/YP,
13558                 this means that the <A
13559 HREF="#PASSWDPROGRAM"
13560 >passwd program</A
13561 > must be
13562                 executed on the NIS master.
13563                 </P
13564 ><P
13565 >The string can contain the macro <TT
13566 CLASS="PARAMETER"
13567 ><I
13568 >%n</I
13569 ></TT
13570 > which is substituted
13571                 for the new password.  The chat sequence can also contain the standard
13572                 macros <TT
13573 CLASS="CONSTANT"
13574 >\n</TT
13575 >, <TT
13576 CLASS="CONSTANT"
13577 >\r</TT
13578 >, <TT
13579 CLASS="CONSTANT"
13580 >               \t</TT
13581 > and <TT
13582 CLASS="CONSTANT"
13583 >\s</TT
13584 > to give line-feed,
13585                 carriage-return, tab and space.  The chat sequence string can also contain
13586                 a '*' which matches any sequence of characters.
13587                 Double quotes can be used to collect strings with spaces
13588                 in them into a single string.</P
13589 ><P
13590 >If the send string in any part of the chat sequence
13591                 is a full stop ".",  then no string is sent. Similarly,
13592                 if the expect string is a full stop then no string is expected.</P
13593 ><P
13594 >If the <A
13595 HREF="#PAMPASSWORDCHANGE"
13596 ><TT
13597 CLASS="PARAMETER"
13598 ><I
13599 >pam
13600                 password change</I
13601 ></TT
13602 ></A
13603 > parameter is set to <TT
13604 CLASS="CONSTANT"
13605 >yes</TT
13606 >, the chat pairs
13607                 may be matched in any order, and success is determined by the PAM result,
13608                 not any particular output. The \n macro is ignored for PAM conversions.
13609                 </P
13610 ><P
13611 >See also <A
13612 HREF="#UNIXPASSWORDSYNC"
13613 ><TT
13614 CLASS="PARAMETER"
13615 ><I
13616 >unix password
13617                 sync</I
13618 ></TT
13619 ></A
13620 >, <A
13621 HREF="#PASSWDPROGRAM"
13622 ><TT
13623 CLASS="PARAMETER"
13624 ><I
13625 >               passwd program</I
13626 ></TT
13627 ></A
13628 > ,<A
13629 HREF="#PASSWDCHATDEBUG"
13630 >               <TT
13631 CLASS="PARAMETER"
13632 ><I
13633 >passwd chat debug</I
13634 ></TT
13635 ></A
13636 > and <A
13637 HREF="#PAMPASSWORDCHANGE"
13638 >               <TT
13639 CLASS="PARAMETER"
13640 ><I
13641 >pam password change</I
13642 ></TT
13643 ></A
13644 >.</P
13645 ><P
13646 >Default: <B
13647 CLASS="COMMAND"
13648 >passwd chat = *new*password* %n\n
13649                 *new*password* %n\n *changed*</B
13650 ></P
13651 ><P
13652 >Example: <B
13653 CLASS="COMMAND"
13654 >passwd chat = "*Enter OLD password*" %o\n
13655                 "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password
13656                 changed*"</B
13657 ></P
13658 ></DD
13659 ><DT
13660 ><A
13661 NAME="PASSWDCHATDEBUG"
13662 ></A
13663 >passwd chat debug (G)</DT
13664 ><DD
13665 ><P
13666 >This boolean specifies if the passwd chat script
13667                 parameter is run in <EM
13668 >debug</EM
13669 > mode. In this mode the
13670                 strings passed to and received from the passwd chat are printed
13671                 in the <A
13672 HREF="smbd.8.html"
13673 TARGET="_top"
13674 >smbd(8)</A
13675 > log with a
13676                 <A
13677 HREF="#DEBUGLEVEL"
13678 ><TT
13679 CLASS="PARAMETER"
13680 ><I
13681 >debug level</I
13682 ></TT
13683 ></A
13684 >
13685                 of 100. This is a dangerous option as it will allow plaintext passwords
13686                 to be seen in the <B
13687 CLASS="COMMAND"
13688 >smbd</B
13689 > log. It is available to help
13690                 Samba admins debug their <TT
13691 CLASS="PARAMETER"
13692 ><I
13693 >passwd chat</I
13694 ></TT
13695 > scripts
13696                 when calling the <TT
13697 CLASS="PARAMETER"
13698 ><I
13699 >passwd program</I
13700 ></TT
13701 > and should
13702                 be turned off after this has been done. This option has no effect if the
13703                 <A
13704 HREF="#PAMPASSWORDCHANGE"
13705 ><TT
13706 CLASS="PARAMETER"
13707 ><I
13708 >pam password change</I
13709 ></TT
13710 ></A
13711 >
13712                 paramter is set. This parameter is off by default.</P
13713 ><P
13714 >See also <A
13715 HREF="#PASSWDCHAT"
13716 ><TT
13717 CLASS="PARAMETER"
13718 ><I
13719 >passwd chat</I
13720 ></TT
13721 >
13722                 </A
13723 >, <A
13724 HREF="#PAMPASSWORDCHANGE"
13725 ><TT
13726 CLASS="PARAMETER"
13727 ><I
13728 >pam password change</I
13729 ></TT
13730 >
13731                 </A
13732 >, <A
13733 HREF="#PASSWDPROGRAM"
13734 ><TT
13735 CLASS="PARAMETER"
13736 ><I
13737 >passwd program</I
13738 ></TT
13739 >
13740                 </A
13741 >.</P
13742 ><P
13743 >Default: <B
13744 CLASS="COMMAND"
13745 >passwd chat debug = no</B
13746 ></P
13747 ></DD
13748 ><DT
13749 ><A
13750 NAME="PASSWDPROGRAM"
13751 ></A
13752 >passwd program (G)</DT
13753 ><DD
13754 ><P
13755 >The name of a program that can be used to set
13756                 UNIX user passwords.  Any occurrences of <TT
13757 CLASS="PARAMETER"
13758 ><I
13759 >%u</I
13760 ></TT
13761 >
13762                 will be replaced with the user name. The user name is checked for
13763                 existence before calling the password changing program.</P
13764 ><P
13765 >Also note that many passwd programs insist in <EM
13766 >reasonable
13767                 </EM
13768 > passwords, such as a minimum length, or the inclusion
13769                 of mixed case chars and digits. This can pose a problem as some clients
13770                 (such as Windows for Workgroups) uppercase the password before sending
13771                 it.</P
13772 ><P
13773 ><EM
13774 >Note</EM
13775 > that if the <TT
13776 CLASS="PARAMETER"
13777 ><I
13778 >unix
13779                 password sync</I
13780 ></TT
13781 > parameter is set to <TT
13782 CLASS="CONSTANT"
13783 >yes
13784                 </TT
13785 > then this program is called <EM
13786 >AS ROOT</EM
13787 >
13788                 before the SMB password in the <A
13789 HREF="smbpasswd.5.html"
13790 TARGET="_top"
13791 >smbpasswd(5)
13792                 </A
13793 > file is changed. If this UNIX password change fails, then
13794                 <B
13795 CLASS="COMMAND"
13796 >smbd</B
13797 > will fail to change the SMB password also
13798                 (this is by design).</P
13799 ><P
13800 >If the <TT
13801 CLASS="PARAMETER"
13802 ><I
13803 >unix password sync</I
13804 ></TT
13805 > parameter
13806                 is set this parameter <EM
13807 >MUST USE ABSOLUTE PATHS</EM
13808 >
13809                 for <EM
13810 >ALL</EM
13811 > programs called, and must be examined
13812                 for security implications. Note that by default <TT
13813 CLASS="PARAMETER"
13814 ><I
13815 >unix
13816                 password sync</I
13817 ></TT
13818 > is set to <TT
13819 CLASS="CONSTANT"
13820 >no</TT
13821 >.</P
13822 ><P
13823 >See also <A
13824 HREF="#UNIXPASSWORDSYNC"
13825 ><TT
13826 CLASS="PARAMETER"
13827 ><I
13828 >unix
13829                 password sync</I
13830 ></TT
13831 ></A
13832 >.</P
13833 ><P
13834 >Default: <B
13835 CLASS="COMMAND"
13836 >passwd program = /bin/passwd</B
13837 ></P
13838 ><P
13839 >Example: <B
13840 CLASS="COMMAND"
13841 >passwd program = /sbin/npasswd %u</B
13842 >
13843                 </P
13844 ></DD
13845 ><DT
13846 ><A
13847 NAME="PASSWORDLEVEL"
13848 ></A
13849 >password level (G)</DT
13850 ><DD
13851 ><P
13852 >Some client/server combinations have difficulty
13853                 with mixed-case passwords.  One offending client is Windows for
13854                 Workgroups, which for some reason forces passwords to upper
13855                 case when using the LANMAN1 protocol, but leaves them alone when
13856                 using COREPLUS!  Another problem child is the Windows 95/98
13857                 family of operating systems.  These clients upper case clear
13858                 text passwords even when NT LM 0.12 selected by the protocol
13859                 negotiation request/response.</P
13860 ><P
13861 >This parameter defines the maximum number of characters
13862                 that may be upper case in passwords.</P
13863 ><P
13864 >For example, say the password given was "FRED". If <TT
13865 CLASS="PARAMETER"
13866 ><I
13867 >               password level</I
13868 ></TT
13869 > is set to 1, the following combinations
13870                 would be tried if "FRED" failed:</P
13871 ><P
13872 >"Fred", "fred", "fRed", "frEd","freD"</P
13873 ><P
13874 >If <TT
13875 CLASS="PARAMETER"
13876 ><I
13877 >password level</I
13878 ></TT
13879 > was set to 2,
13880                 the following combinations would also be tried: </P
13881 ><P
13882 >"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</P
13883 ><P
13884 >And so on.</P
13885 ><P
13886 >The higher value this parameter is set to the more likely
13887                 it is that a mixed case password will be matched against a single
13888                 case password. However, you should be aware that use of this
13889                 parameter reduces security and increases the time taken to
13890                 process a new connection.</P
13891 ><P
13892 >A value of zero will cause only two attempts to be
13893                 made - the password as is and the password in all-lower case.</P
13894 ><P
13895 >Default: <B
13896 CLASS="COMMAND"
13897 >password level = 0</B
13898 ></P
13899 ><P
13900 >Example: <B
13901 CLASS="COMMAND"
13902 >password level = 4</B
13903 ></P
13904 ></DD
13905 ><DT
13906 ><A
13907 NAME="PASSWORDSERVER"
13908 ></A
13909 >password server (G)</DT
13910 ><DD
13911 ><P
13912 >By specifying the name of another SMB server (such
13913                 as a WinNT box) with this option, and using <B
13914 CLASS="COMMAND"
13915 >security = domain
13916                 </B
13917 > or <B
13918 CLASS="COMMAND"
13919 >security = server</B
13920 > you can get Samba
13921                 to do all its username/password validation via a remote server.</P
13922 ><P
13923 >This option sets the name of the password server to use.
13924                 It must be a NetBIOS name, so if the machine's NetBIOS name is
13925                 different from its Internet name then you may have to add its NetBIOS
13926                 name to the lmhosts  file which is stored in the same directory
13927                 as the <TT
13928 CLASS="FILENAME"
13929 >smb.conf</TT
13930 > file.</P
13931 ><P
13932 >The name of the password server is looked up using the
13933                 parameter <A
13934 HREF="#NAMERESOLVEORDER"
13935 ><TT
13936 CLASS="PARAMETER"
13937 ><I
13938 >name
13939                 resolve order</I
13940 ></TT
13941 ></A
13942 > and so may resolved
13943                 by any method and order described in that parameter.</P
13944 ><P
13945 >The password server much be a machine capable of using
13946                 the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in
13947                 user level security mode.</P
13948 ><P
13949 ><EM
13950 >NOTE:</EM
13951 > Using a password server
13952                 means your UNIX box (running Samba) is only as secure as your
13953                 password server. <EM
13954 >DO NOT CHOOSE A PASSWORD SERVER THAT
13955                 YOU DON'T COMPLETELY TRUST</EM
13956 >.</P
13957 ><P
13958 >Never point a Samba server at itself for password
13959                 serving. This will cause a loop and could lock up your Samba
13960                 server!</P
13961 ><P
13962 >The name of the password server takes the standard
13963                 substitutions, but probably the only useful one is <TT
13964 CLASS="PARAMETER"
13965 ><I
13966 >%m
13967                 </I
13968 ></TT
13969 >, which means the Samba server will use the incoming
13970                 client as the password server. If you use this then you better
13971                 trust your clients, and you had better restrict them with hosts allow!</P
13972 ><P
13973 >If the <TT
13974 CLASS="PARAMETER"
13975 ><I
13976 >security</I
13977 ></TT
13978 > parameter is set to
13979                 <TT
13980 CLASS="CONSTANT"
13981 >domain</TT
13982 >, then the list of machines in this
13983                 option must be a list of Primary or Backup Domain controllers for the
13984                 Domain or the character '*', as the Samba server is effectively
13985                 in that domain, and will use cryptographically authenticated RPC calls
13986                 to authenticate the user logging on. The advantage of using <B
13987 CLASS="COMMAND"
13988 >               security = domain</B
13989 > is that if you list several hosts in the
13990                 <TT
13991 CLASS="PARAMETER"
13992 ><I
13993 >password server</I
13994 ></TT
13995 > option then <B
13996 CLASS="COMMAND"
13997 >smbd
13998                 </B
13999 > will try each in turn till it finds one that responds. This
14000                 is useful in case your primary server goes down.</P
14001 ><P
14002 >If the <TT
14003 CLASS="PARAMETER"
14004 ><I
14005 >password server</I
14006 ></TT
14007 > option is set
14008                 to the character '*', then Samba will attempt to auto-locate the
14009                 Primary or Backup Domain controllers to authenticate against by
14010                 doing a query for the name <TT
14011 CLASS="CONSTANT"
14012 >WORKGROUP&#60;1C&#62;</TT
14013 >
14014                 and then contacting each server returned in the list of IP
14015                 addresses from the name resolution source. </P
14016 ><P
14017 >If the <TT
14018 CLASS="PARAMETER"
14019 ><I
14020 >security</I
14021 ></TT
14022 > parameter is
14023                 set to <TT
14024 CLASS="CONSTANT"
14025 >server</TT
14026 >, then there are different
14027                 restrictions that <B
14028 CLASS="COMMAND"
14029 >security = domain</B
14030 > doesn't
14031                 suffer from:</P
14032 ><P
14033 ></P
14034 ><UL
14035 ><LI
14036 ><P
14037 >You may list several password servers in
14038                         the <TT
14039 CLASS="PARAMETER"
14040 ><I
14041 >password server</I
14042 ></TT
14043 > parameter, however if an
14044                         <B
14045 CLASS="COMMAND"
14046 >smbd</B
14047 > makes a connection to a password server,
14048                         and then the password server fails, no more users will be able
14049                         to be authenticated from this <B
14050 CLASS="COMMAND"
14051 >smbd</B
14052 >.  This is a
14053                         restriction of the SMB/CIFS protocol when in <B
14054 CLASS="COMMAND"
14055 >security = server
14056                         </B
14057 > mode and cannot be fixed in Samba.</P
14058 ></LI
14059 ><LI
14060 ><P
14061 >If you are using a Windows NT server as your
14062                         password server then you will have to ensure that your users
14063                         are able to login from the Samba server, as when in <B
14064 CLASS="COMMAND"
14065 >                       security = server</B
14066 >  mode the network logon will appear to
14067                         come from there rather than from the users workstation.</P
14068 ></LI
14069 ></UL
14070 ><P
14071 >See also the <A
14072 HREF="#SECURITY"
14073 ><TT
14074 CLASS="PARAMETER"
14075 ><I
14076 >security
14077                 </I
14078 ></TT
14079 ></A
14080 > parameter.</P
14081 ><P
14082 >Default: <B
14083 CLASS="COMMAND"
14084 >password server = &#60;empty string&#62;</B
14085 >
14086                 </P
14087 ><P
14088 >Example: <B
14089 CLASS="COMMAND"
14090 >password server = NT-PDC, NT-BDC1, NT-BDC2
14091                 </B
14092 ></P
14093 ><P
14094 >Example: <B
14095 CLASS="COMMAND"
14096 >password server = *</B
14097 ></P
14098 ></DD
14099 ><DT
14100 ><A
14101 NAME="PATH"
14102 ></A
14103 >path (S)</DT
14104 ><DD
14105 ><P
14106 >This parameter specifies a directory to which
14107                 the user of the service is to be given access. In the case of
14108                 printable services, this is where print data will spool prior to
14109                 being submitted to the host for printing.</P
14110 ><P
14111 >For a printable service offering guest access, the service
14112                 should be readonly and the path should be world-writeable and
14113                 have the sticky bit set. This is not mandatory of course, but
14114                 you probably won't get the results you expect if you do
14115                 otherwise.</P
14116 ><P
14117 >Any occurrences of <TT
14118 CLASS="PARAMETER"
14119 ><I
14120 >%u</I
14121 ></TT
14122 > in the path
14123                 will be replaced with the UNIX username that the client is using
14124                 on this connection. Any occurrences of <TT
14125 CLASS="PARAMETER"
14126 ><I
14127 >%m</I
14128 ></TT
14129 >
14130                 will be replaced by the NetBIOS name of the machine they are
14131                 connecting from. These replacements are very useful for setting
14132                 up pseudo home directories for users.</P
14133 ><P
14134 >Note that this path will be based on <A
14135 HREF="#ROOTDIR"
14136 >               <TT
14137 CLASS="PARAMETER"
14138 ><I
14139 >root dir</I
14140 ></TT
14141 ></A
14142 > if one was specified.</P
14143 ><P
14144 >Default: <EM
14145 >none</EM
14146 ></P
14147 ><P
14148 >Example: <B
14149 CLASS="COMMAND"
14150 >path = /home/fred</B
14151 ></P
14152 ></DD
14153 ><DT
14154 ><A
14155 NAME="PIDDIRECTORY"
14156 ></A
14157 >pid directory (G)</DT
14158 ><DD
14159 ><P
14160 >This option specifies the directory where pid
14161                 files will be placed.  </P
14162 ><P
14163 >Default: <B
14164 CLASS="COMMAND"
14165 >pid directory = ${prefix}/var/locks</B
14166 ></P
14167 ><P
14168 >Example: <B
14169 CLASS="COMMAND"
14170 >pid directory = /var/run/</B
14171 >
14172                 </P
14173 ></DD
14174 ><DT
14175 ><A
14176 NAME="POSIXLOCKING"
14177 ></A
14178 >posix locking (S)</DT
14179 ><DD
14180 ><P
14181 >The <A
14182 HREF="smbd.8.html"
14183 TARGET="_top"
14184 ><B
14185 CLASS="COMMAND"
14186 >smbd(8)</B
14187 ></A
14188 >
14189                 daemon maintains an database of file locks obtained by SMB clients.
14190                 The default behavior is to map this internal database to POSIX
14191                 locks.  This means that file locks obtained by SMB clients are
14192                 consistent with those seen by POSIX compliant applications accessing
14193                 the files via a non-SMB method (e.g. NFS or local file access).
14194                 You should never need to disable this parameter.</P
14195 ><P
14196 >Default: <B
14197 CLASS="COMMAND"
14198 >posix locking = yes</B
14199 ></P
14200 ></DD
14201 ><DT
14202 ><A
14203 NAME="POSTEXEC"
14204 ></A
14205 >postexec (S)</DT
14206 ><DD
14207 ><P
14208 >This option specifies a command to be run
14209                 whenever the service is disconnected. It takes the usual
14210                 substitutions. The command may be run as the root on some
14211                 systems.</P
14212 ><P
14213 >An interesting example may be to unmount server
14214                 resources:</P
14215 ><P
14216 ><B
14217 CLASS="COMMAND"
14218 >postexec = /etc/umount /cdrom</B
14219 ></P
14220 ><P
14221 >See also <A
14222 HREF="#PREEXEC"
14223 ><TT
14224 CLASS="PARAMETER"
14225 ><I
14226 >preexec</I
14227 ></TT
14228 >
14229                 </A
14230 >.</P
14231 ><P
14232 >Default: <EM
14233 >none (no command executed)</EM
14234 >
14235                 </P
14236 ><P
14237 >Example: <B
14238 CLASS="COMMAND"
14239 >postexec = echo \"%u disconnected from %S
14240                 from %m (%I)\" &#62;&#62; /tmp/log</B
14241 ></P
14242 ></DD
14243 ><DT
14244 ><A
14245 NAME="POSTSCRIPT"
14246 ></A
14247 >postscript (S)</DT
14248 ><DD
14249 ><P
14250 >This parameter forces a printer to interpret
14251                 the print files as PostScript. This is done by adding a <TT
14252 CLASS="CONSTANT"
14253 >%!
14254                 </TT
14255 > to the start of print output.</P
14256 ><P
14257 >This is most useful when you have lots of PCs that persist
14258                 in putting a control-D at the start of print jobs, which then
14259                 confuses your printer.</P
14260 ><P
14261 >Default: <B
14262 CLASS="COMMAND"
14263 >postscript = no</B
14264 ></P
14265 ></DD
14266 ><DT
14267 ><A
14268 NAME="PREEXEC"
14269 ></A
14270 >preexec (S)</DT
14271 ><DD
14272 ><P
14273 >This option specifies a command to be run whenever
14274                 the service is connected to. It takes the usual substitutions.</P
14275 ><P
14276 >An interesting example is to send the users a welcome
14277                 message every time they log in. Maybe a message of the day? Here
14278                 is an example:</P
14279 ><P
14280 ><B
14281 CLASS="COMMAND"
14282 >preexec = csh -c 'echo \"Welcome to %S!\" |
14283                  /usr/local/samba/bin/smbclient -M %m -I %I' &#38; </B
14284 ></P
14285 ><P
14286 >Of course, this could get annoying after a while :-)</P
14287 ><P
14288 >See also <A
14289 HREF="#PREEXECCLOSE"
14290 ><TT
14291 CLASS="PARAMETER"
14292 ><I
14293 >preexec close
14294                 </I
14295 ></TT
14296 ></A
14297 > and <A
14298 HREF="#POSTEXEC"
14299 ><TT
14300 CLASS="PARAMETER"
14301 ><I
14302 >postexec
14303                 </I
14304 ></TT
14305 ></A
14306 >.</P
14307 ><P
14308 >Default: <EM
14309 >none (no command executed)</EM
14310 ></P
14311 ><P
14312 >Example: <B
14313 CLASS="COMMAND"
14314 >preexec = echo \"%u connected to %S from %m
14315                 (%I)\" &#62;&#62; /tmp/log</B
14316 ></P
14317 ></DD
14318 ><DT
14319 ><A
14320 NAME="PREEXECCLOSE"
14321 ></A
14322 >preexec close (S)</DT
14323 ><DD
14324 ><P
14325 >This boolean option controls whether a non-zero
14326                 return code from <A
14327 HREF="#PREEXEC"
14328 ><TT
14329 CLASS="PARAMETER"
14330 ><I
14331 >preexec
14332                 </I
14333 ></TT
14334 ></A
14335 > should close the service being connected to.</P
14336 ><P
14337 >Default: <B
14338 CLASS="COMMAND"
14339 >preexec close = no</B
14340 ></P
14341 ></DD
14342 ><DT
14343 ><A
14344 NAME="PREFERREDMASTER"
14345 ></A
14346 >preferred master (G)</DT
14347 ><DD
14348 ><P
14349 >This boolean parameter controls if <A
14350 HREF="nmbd.8.html"
14351 TARGET="_top"
14352 >nmbd(8)</A
14353 > is a preferred master browser
14354                 for its workgroup.</P
14355 ><P
14356 >If this is set to <TT
14357 CLASS="CONSTANT"
14358 >yes</TT
14359 >, on startup, <B
14360 CLASS="COMMAND"
14361 >nmbd</B
14362 >
14363                 will force an election, and it will have a slight advantage in
14364                 winning the election.  It is recommended that this parameter is
14365                 used in conjunction with <B
14366 CLASS="COMMAND"
14367 ><A
14368 HREF="#DOMAINMASTER"
14369 ><TT
14370 CLASS="PARAMETER"
14371 ><I
14372 >               domain master</I
14373 ></TT
14374 ></A
14375 > = yes</B
14376 >, so that <B
14377 CLASS="COMMAND"
14378 >               nmbd</B
14379 > can guarantee becoming a domain master.</P
14380 ><P
14381 >Use this option with caution, because if there are several
14382                 hosts (whether Samba servers, Windows 95 or NT) that are preferred
14383                 master browsers on the same subnet, they will each periodically
14384                 and continuously attempt to become the local master browser.
14385                 This will result in unnecessary broadcast traffic and reduced browsing
14386                 capabilities.</P
14387 ><P
14388 >See also <A
14389 HREF="#OSLEVEL"
14390 ><TT
14391 CLASS="PARAMETER"
14392 ><I
14393 >os level</I
14394 ></TT
14395 >
14396                 </A
14397 >.</P
14398 ><P
14399 >Default: <B
14400 CLASS="COMMAND"
14401 >preferred master = auto</B
14402 ></P
14403 ></DD
14404 ><DT
14405 ><A
14406 NAME="PREFEREDMASTER"
14407 ></A
14408 >prefered master (G)</DT
14409 ><DD
14410 ><P
14411 >Synonym for <A
14412 HREF="#PREFERREDMASTER"
14413 ><TT
14414 CLASS="PARAMETER"
14415 ><I
14416 >               preferred master</I
14417 ></TT
14418 ></A
14419 > for people who cannot spell :-).</P
14420 ></DD
14421 ><DT
14422 ><A
14423 NAME="PRELOAD"
14424 ></A
14425 >preload</DT
14426 ><DD
14427 ><P
14428 >This is a list of services that you want to be
14429                 automatically added to the browse lists. This is most useful
14430                 for homes and printers services that would otherwise not be
14431                 visible.</P
14432 ><P
14433 >Note that if you just want all printers in your
14434                 printcap file loaded then the <A
14435 HREF="#LOADPRINTERS"
14436 >               <TT
14437 CLASS="PARAMETER"
14438 ><I
14439 >load printers</I
14440 ></TT
14441 ></A
14442 > option is easier.</P
14443 ><P
14444 >Default: <EM
14445 >no preloaded services</EM
14446 ></P
14447 ><P
14448 >Example: <B
14449 CLASS="COMMAND"
14450 >preload = fred lp colorlp</B
14451 ></P
14452 ></DD
14453 ><DT
14454 ><A
14455 NAME="PRESERVECASE"
14456 ></A
14457 >preserve case (S)</DT
14458 ><DD
14459 ><P
14460 > This controls if new filenames are created
14461                 with the case that the client passes, or if they are forced to
14462                 be the <A
14463 HREF="#DEFAULTCASE"
14464 ><TT
14465 CLASS="PARAMETER"
14466 ><I
14467 >default case
14468                 </I
14469 ></TT
14470 ></A
14471 >.</P
14472 ><P
14473 >Default: <B
14474 CLASS="COMMAND"
14475 >preserve case = yes</B
14476 ></P
14477 ><P
14478 >See the section on <A
14479 HREF="#AEN203"
14480 >NAME
14481                 MANGLING</A
14482 > for a fuller discussion.</P
14483 ></DD
14484 ><DT
14485 ><A
14486 NAME="PRINTCOMMAND"
14487 ></A
14488 >print command (S)</DT
14489 ><DD
14490 ><P
14491 >After a print job has finished spooling to
14492                 a service, this command will be used via a <B
14493 CLASS="COMMAND"
14494 >system()</B
14495 >
14496                 call to process the spool file. Typically the command specified will
14497                 submit the spool file to the host's printing subsystem, but there
14498                 is no requirement that this be the case. The server will not remove
14499                 the spool file, so whatever command you specify should remove the
14500                 spool file when it has been processed, otherwise you will need to
14501                 manually remove old spool files.</P
14502 ><P
14503 >The print command is simply a text string. It will be used
14504                 verbatim after macro substitutions have been made:</P
14505 ><P
14506 >s, %p - the path to the spool
14507                 file name</P
14508 ><P
14509 >%p - the appropriate printer
14510                 name</P
14511 ><P
14512 >%J - the job
14513                 name as transmitted by the client.</P
14514 ><P
14515 >%c - The number of printed pages
14516                 of the spooled job (if known).</P
14517 ><P
14518 >%z - the size of the spooled
14519                 print job (in bytes)</P
14520 ><P
14521 >The print command <EM
14522 >MUST</EM
14523 > contain at least
14524                 one occurrence of <TT
14525 CLASS="PARAMETER"
14526 ><I
14527 >%s</I
14528 ></TT
14529 > or <TT
14530 CLASS="PARAMETER"
14531 ><I
14532 >%f
14533                 </I
14534 ></TT
14535 > - the <TT
14536 CLASS="PARAMETER"
14537 ><I
14538 >%p</I
14539 ></TT
14540 > is optional. At the time
14541                 a job is submitted, if no printer name is supplied the <TT
14542 CLASS="PARAMETER"
14543 ><I
14544 >%p
14545                 </I
14546 ></TT
14547 > will be silently removed from the printer command.</P
14548 ><P
14549 >If specified in the [global] section, the print command given
14550                 will be used for any printable service that does not have its own
14551                 print command specified.</P
14552 ><P
14553 >If there is neither a specified print command for a
14554                 printable service nor a global print command, spool files will
14555                 be created but not processed and (most importantly) not removed.</P
14556 ><P
14557 >Note that printing may fail on some UNIXes from the
14558                 <TT
14559 CLASS="CONSTANT"
14560 >nobody</TT
14561 > account. If this happens then create
14562                 an alternative guest account that can print and set the <A
14563 HREF="#GUESTACCOUNT"
14564 ><TT
14565 CLASS="PARAMETER"
14566 ><I
14567 >guest account</I
14568 ></TT
14569 ></A
14570 >
14571                 in the [global] section.</P
14572 ><P
14573 >You can form quite complex print commands by realizing
14574                 that they are just passed to a shell. For example the following
14575                 will log a print job, print the file, then remove it. Note that
14576                 ';' is the usual separator for command in shell scripts.</P
14577 ><P
14578 ><B
14579 CLASS="COMMAND"
14580 >print command = echo Printing %s &#62;&#62;
14581                 /tmp/print.log; lpr -P %p %s; rm %s</B
14582 ></P
14583 ><P
14584 >You may have to vary this command considerably depending
14585                 on how you normally print files on your system. The default for
14586                 the parameter varies depending on the setting of the <A
14587 HREF="#PRINTING"
14588 >               <TT
14589 CLASS="PARAMETER"
14590 ><I
14591 >printing</I
14592 ></TT
14593 ></A
14594 > parameter.</P
14595 ><P
14596 >Default: For <B
14597 CLASS="COMMAND"
14598 >printing = BSD, AIX, QNX, LPRNG
14599                 or PLP :</B
14600 ></P
14601 ><P
14602 ><B
14603 CLASS="COMMAND"
14604 >print command = lpr -r -P%p %s</B
14605 ></P
14606 ><P
14607 >For <B
14608 CLASS="COMMAND"
14609 >printing = SYSV or HPUX :</B
14610 ></P
14611 ><P
14612 ><B
14613 CLASS="COMMAND"
14614 >print command = lp -c -d%p %s; rm %s</B
14615 ></P
14616 ><P
14617 >For <B
14618 CLASS="COMMAND"
14619 >printing = SOFTQ :</B
14620 ></P
14621 ><P
14622 ><B
14623 CLASS="COMMAND"
14624 >print command = lp -d%p -s %s; rm %s</B
14625 ></P
14626 ><P
14627 >For printing = CUPS :   If SAMBA is compiled against
14628                 libcups, then <A
14629 HREF="#PRINTING"
14630 >printcap = cups</A
14631 >
14632                 uses the CUPS API to
14633                 submit jobs, etc.  Otherwise it maps to the System V
14634                 commands with the -oraw option for printing, i.e. it
14635                 uses <B
14636 CLASS="COMMAND"
14637 >lp -c -d%p -oraw; rm %s</B
14638 >.
14639                 With <B
14640 CLASS="COMMAND"
14641 >printing = cups</B
14642 >,
14643                 and if SAMBA is compiled against libcups, any manually
14644                 set print command will be ignored.</P
14645 ><P
14646 >Example: <B
14647 CLASS="COMMAND"
14648 >print command = /usr/local/samba/bin/myprintscript
14649                 %p %s</B
14650 ></P
14651 ></DD
14652 ><DT
14653 ><A
14654 NAME="PRINTOK"
14655 ></A
14656 >print ok (S)</DT
14657 ><DD
14658 ><P
14659 >Synonym for <A
14660 HREF="#PRINTABLE"
14661 >               <TT
14662 CLASS="PARAMETER"
14663 ><I
14664 >printable</I
14665 ></TT
14666 ></A
14667 >.</P
14668 ></DD
14669 ><DT
14670 ><A
14671 NAME="PRINTABLE"
14672 ></A
14673 >printable (S)</DT
14674 ><DD
14675 ><P
14676 >If this parameter is <TT
14677 CLASS="CONSTANT"
14678 >yes</TT
14679 >, then
14680                 clients may open, write to and submit spool files on the directory
14681                 specified for the service. </P
14682 ><P
14683 >Note that a printable service will ALWAYS allow writing
14684                 to the service path (user privileges permitting) via the spooling
14685                 of print data. The <A
14686 HREF="#READONLY"
14687 ><TT
14688 CLASS="PARAMETER"
14689 ><I
14690 >read only
14691                 </I
14692 ></TT
14693 ></A
14694 > parameter controls only non-printing access to
14695                 the resource.</P
14696 ><P
14697 >Default: <B
14698 CLASS="COMMAND"
14699 >printable = no</B
14700 ></P
14701 ></DD
14702 ><DT
14703 ><A
14704 NAME="PRINTCAP"
14705 ></A
14706 >printcap (G)</DT
14707 ><DD
14708 ><P
14709 >Synonym for    <A
14710 HREF="#PRINTCAPNAME"
14711 ><TT
14712 CLASS="PARAMETER"
14713 ><I
14714 >               printcap name</I
14715 ></TT
14716 ></A
14717 >.</P
14718 ></DD
14719 ><DT
14720 ><A
14721 NAME="PRINTCAPNAME"
14722 ></A
14723 >printcap name (G)</DT
14724 ><DD
14725 ><P
14726 >This parameter may be used to override the
14727                 compiled-in default printcap name used by the server (usually <TT
14728 CLASS="FILENAME"
14729 >               /etc/printcap</TT
14730 >). See the discussion of the <A
14731 HREF="#AEN79"
14732 >[printers]</A
14733 > section above for reasons
14734                 why you might want to do this.</P
14735 ><P
14736 >To use the CUPS printing interface set <B
14737 CLASS="COMMAND"
14738 >printcap name = cups
14739                 </B
14740 >. This should be supplemented by an addtional setting
14741                 <A
14742 HREF="#PRINTING"
14743 >printing = cups</A
14744 > in the [global]
14745                 section.  <B
14746 CLASS="COMMAND"
14747 >printcap name = cups</B
14748 > will use the
14749                 "dummy" printcap created by CUPS, as specified in your CUPS
14750                 configuration file.
14751                 </P
14752 ><P
14753 >On System V systems that use <B
14754 CLASS="COMMAND"
14755 >lpstat</B
14756 > to
14757                 list available printers you can use <B
14758 CLASS="COMMAND"
14759 >printcap name = lpstat
14760                 </B
14761 > to automatically obtain lists of available printers. This
14762                 is the default for systems that define SYSV at configure time in
14763                 Samba (this includes most System V based systems). If <TT
14764 CLASS="PARAMETER"
14765 ><I
14766 >               printcap name</I
14767 ></TT
14768 > is set to <B
14769 CLASS="COMMAND"
14770 >lpstat</B
14771 > on
14772                 these systems then Samba will launch <B
14773 CLASS="COMMAND"
14774 >lpstat -v</B
14775 > and
14776                 attempt to parse the output to obtain a printer list.</P
14777 ><P
14778 >A minimal printcap file would look something like this:</P
14779 ><P
14780 ><TABLE
14781 BORDER="0"
14782 BGCOLOR="#E0E0E0"
14783 WIDTH="90%"
14784 ><TR
14785 ><TD
14786 ><PRE
14787 CLASS="PROGRAMLISTING"
14788 >               print1|My Printer 1
14789                 print2|My Printer 2
14790                 print3|My Printer 3
14791                 print4|My Printer 4
14792                 print5|My Printer 5
14793                 </PRE
14794 ></TD
14795 ></TR
14796 ></TABLE
14797 ></P
14798 ><P
14799 >where the '|' separates aliases of a printer. The fact
14800                 that the second alias has a space in it gives a hint to Samba
14801                 that it's a comment.</P
14802 ><P
14803 ><EM
14804 >NOTE</EM
14805 >: Under AIX the default printcap
14806                 name is <TT
14807 CLASS="FILENAME"
14808 >/etc/qconfig</TT
14809 >. Samba will assume the
14810                 file is in AIX <TT
14811 CLASS="FILENAME"
14812 >qconfig</TT
14813 > format if the string
14814                 <TT
14815 CLASS="FILENAME"
14816 >qconfig</TT
14817 > appears in the printcap filename.</P
14818 ><P
14819 >Default: <B
14820 CLASS="COMMAND"
14821 >printcap name = /etc/printcap</B
14822 ></P
14823 ><P
14824 >Example: <B
14825 CLASS="COMMAND"
14826 >printcap name = /etc/myprintcap</B
14827 ></P
14828 ></DD
14829 ><DT
14830 ><A
14831 NAME="PRINTERADMIN"
14832 ></A
14833 >printer admin (S)</DT
14834 ><DD
14835 ><P
14836 >This is a list of users that can do anything to
14837                 printers via the remote administration interfaces offered by MS-RPC
14838                 (usually using a NT workstation). Note that the root user always
14839                 has admin rights.</P
14840 ><P
14841 >Default: <B
14842 CLASS="COMMAND"
14843 >printer admin = &#60;empty string&#62;</B
14844 >
14845                 </P
14846 ><P
14847 >Example: <B
14848 CLASS="COMMAND"
14849 >printer admin = admin, @staff</B
14850 ></P
14851 ></DD
14852 ><DT
14853 ><A
14854 NAME="PRINTERDRIVER"
14855 ></A
14856 >printer driver (S)</DT
14857 ><DD
14858 ><P
14859 ><EM
14860 >Note :</EM
14861 >This is a deprecated
14862                 parameter and will be removed in the next major release
14863                 following version 2.2.  Please see the instructions in
14864                 the <A
14865 HREF="printer_driver2.html"
14866 TARGET="_top"
14867 >Samba 2.2. Printing
14868                 HOWTO</A
14869 > for more information
14870                 on the new method of loading printer drivers onto a Samba server.
14871                 </P
14872 ><P
14873 >This option allows you to control the string
14874                 that clients receive when they ask the server for the printer driver
14875                 associated with a printer. If you are using Windows95 or Windows NT
14876                 then you can use this to automate the setup of printers on your
14877                 system.</P
14878 ><P
14879 >You need to set this parameter to the exact string (case
14880                 sensitive) that describes the appropriate printer driver for your
14881                 system. If you don't know the exact string to use then you should
14882                 first try with no <A
14883 HREF="#PRINTERDRIVER"
14884 ><TT
14885 CLASS="PARAMETER"
14886 ><I
14887 >               printer driver</I
14888 ></TT
14889 ></A
14890 > option set and the client will
14891                 give you a list of printer drivers. The appropriate strings are
14892                 shown in a scroll box after you have chosen the printer manufacturer.</P
14893 ><P
14894 >See also <A
14895 HREF="#PRINTERDRIVERFILE"
14896 ><TT
14897 CLASS="PARAMETER"
14898 ><I
14899 >printer
14900                 driver file</I
14901 ></TT
14902 ></A
14903 >.</P
14904 ><P
14905 >Example: <B
14906 CLASS="COMMAND"
14907 >printer driver = HP LaserJet 4L</B
14908 ></P
14909 ></DD
14910 ><DT
14911 ><A
14912 NAME="PRINTERDRIVERFILE"
14913 ></A
14914 >printer driver file (G)</DT
14915 ><DD
14916 ><P
14917 ><EM
14918 >Note :</EM
14919 >This is a deprecated
14920                 parameter and will be removed in the next major release
14921                 following version 2.2.  Please see the instructions in
14922                 the <A
14923 HREF="printer_driver2.html"
14924 TARGET="_top"
14925 >Samba 2.2. Printing
14926                 HOWTO</A
14927 > for more information
14928                 on the new method of loading printer drivers onto a Samba server.
14929                 </P
14930 ><P
14931 >This parameter tells Samba where the printer driver
14932                 definition file, used when serving drivers to Windows 95 clients, is
14933                 to be found. If this is not set, the default is :</P
14934 ><P
14935 ><TT
14936 CLASS="FILENAME"
14937 ><TT
14938 CLASS="REPLACEABLE"
14939 ><I
14940 >SAMBA_INSTALL_DIRECTORY</I
14941 ></TT
14942 >
14943                 /lib/printers.def</TT
14944 ></P
14945 ><P
14946 >This file is created from Windows 95 <TT
14947 CLASS="FILENAME"
14948 >msprint.inf
14949                 </TT
14950 > files found on the Windows 95 client system. For more
14951                 details on setting up serving of printer drivers to Windows 95
14952                 clients, see the outdated documentation file in the <TT
14953 CLASS="FILENAME"
14954 >docs/</TT
14955 >
14956                 directory, <TT
14957 CLASS="FILENAME"
14958 >PRINTER_DRIVER.txt</TT
14959 >.</P
14960 ><P
14961 >See also <A
14962 HREF="#PRINTERDRIVERLOCATION"
14963 ><TT
14964 CLASS="PARAMETER"
14965 ><I
14966 >               printer driver location</I
14967 ></TT
14968 ></A
14969 >.</P
14970 ><P
14971 >Default: <EM
14972 >None (set in compile).</EM
14973 ></P
14974 ><P
14975 >Example: <B
14976 CLASS="COMMAND"
14977 >printer driver file =
14978                 /usr/local/samba/printers/drivers.def</B
14979 ></P
14980 ></DD
14981 ><DT
14982 ><A
14983 NAME="PRINTERDRIVERLOCATION"
14984 ></A
14985 >printer driver location (S)</DT
14986 ><DD
14987 ><P
14988 ><EM
14989 >Note :</EM
14990 >This is a deprecated
14991                 parameter and will be removed in the next major release
14992                 following version 2.2.  Please see the instructions in
14993                 the <A
14994 HREF="printer_driver2.html"
14995 TARGET="_top"
14996 >Samba 2.2. Printing
14997                 HOWTO</A
14998 > for more information
14999                 on the new method of loading printer drivers onto a Samba server.
15000                 </P
15001 ><P
15002 >This parameter tells clients of a particular printer
15003                 share where to find the printer driver files for the automatic
15004                 installation of drivers for Windows 95 machines. If Samba is set up
15005                 to serve printer drivers to Windows 95 machines, this should be set to</P
15006 ><P
15007 ><B
15008 CLASS="COMMAND"
15009 >\\MACHINE\PRINTER$</B
15010 ></P
15011 ><P
15012 >Where MACHINE is the NetBIOS name of your Samba server,
15013                 and PRINTER$ is a share you set up for serving printer driver
15014                 files. For more details on setting this up see the outdated documentation
15015                 file in the <TT
15016 CLASS="FILENAME"
15017 >docs/</TT
15018 > directory, <TT
15019 CLASS="FILENAME"
15020 >               PRINTER_DRIVER.txt</TT
15021 >.</P
15022 ><P
15023 >See also <A
15024 HREF="#PRINTERDRIVERFILE"
15025 ><TT
15026 CLASS="PARAMETER"
15027 ><I
15028 >               printer driver file</I
15029 ></TT
15030 ></A
15031 >.</P
15032 ><P
15033 >Default: <B
15034 CLASS="COMMAND"
15035 >none</B
15036 ></P
15037 ><P
15038 >Example: <B
15039 CLASS="COMMAND"
15040 >printer driver location = \\MACHINE\PRINTER$
15041                 </B
15042 ></P
15043 ></DD
15044 ><DT
15045 ><A
15046 NAME="PRINTERNAME"
15047 ></A
15048 >printer name (S)</DT
15049 ><DD
15050 ><P
15051 >This parameter specifies the name of the printer
15052                 to which print jobs spooled through a printable service will be sent.</P
15053 ><P
15054 >If specified in the [global] section, the printer
15055                 name given will be used for any printable service that does
15056                 not have its own printer name specified.</P
15057 ><P
15058 >Default: <EM
15059 >none (but may be <TT
15060 CLASS="CONSTANT"
15061 >lp</TT
15062 >
15063                 on many systems)</EM
15064 ></P
15065 ><P
15066 >Example: <B
15067 CLASS="COMMAND"
15068 >printer name = laserwriter</B
15069 ></P
15070 ></DD
15071 ><DT
15072 ><A
15073 NAME="PRINTER"
15074 ></A
15075 >printer (S)</DT
15076 ><DD
15077 ><P
15078 >Synonym for <A
15079 HREF="#PRINTERNAME"
15080 ><TT
15081 CLASS="PARAMETER"
15082 ><I
15083 >               printer name</I
15084 ></TT
15085 ></A
15086 >.</P
15087 ></DD
15088 ><DT
15089 ><A
15090 NAME="PRINTING"
15091 ></A
15092 >printing (S)</DT
15093 ><DD
15094 ><P
15095 >This parameters controls how printer status
15096                 information is interpreted on your system. It also affects the
15097                 default values for the <TT
15098 CLASS="PARAMETER"
15099 ><I
15100 >print command</I
15101 ></TT
15102 >,
15103                 <TT
15104 CLASS="PARAMETER"
15105 ><I
15106 >lpq command</I
15107 ></TT
15108 >, <TT
15109 CLASS="PARAMETER"
15110 ><I
15111 >lppause command
15112                 </I
15113 ></TT
15114 >, <TT
15115 CLASS="PARAMETER"
15116 ><I
15117 >lpresume command</I
15118 ></TT
15119 >, and
15120                 <TT
15121 CLASS="PARAMETER"
15122 ><I
15123 >lprm command</I
15124 ></TT
15125 > if specified in the
15126                 [global] section.</P
15127 ><P
15128 >Currently nine printing styles are supported. They are
15129                 <TT
15130 CLASS="CONSTANT"
15131 >BSD</TT
15132 >, <TT
15133 CLASS="CONSTANT"
15134 >AIX</TT
15135 >,
15136                 <TT
15137 CLASS="CONSTANT"
15138 >LPRNG</TT
15139 >, <TT
15140 CLASS="CONSTANT"
15141 >PLP</TT
15142 >,
15143                 <TT
15144 CLASS="CONSTANT"
15145 >SYSV</TT
15146 >, <TT
15147 CLASS="CONSTANT"
15148 >HPUX</TT
15149 >,
15150                 <TT
15151 CLASS="CONSTANT"
15152 >QNX</TT
15153 >, <TT
15154 CLASS="CONSTANT"
15155 >SOFTQ</TT
15156 >,
15157                 and <TT
15158 CLASS="CONSTANT"
15159 >CUPS</TT
15160 >.</P
15161 ><P
15162 >To see what the defaults are for the other print
15163                 commands when using the various options use the <A
15164 HREF="testparm.1.html"
15165 TARGET="_top"
15166 >testparm(1)</A
15167 > program.</P
15168 ><P
15169 >This option can be set on a per printer basis</P
15170 ><P
15171 >See also the discussion in the <A
15172 HREF="#AEN79"
15173 >               [printers]</A
15174 > section.</P
15175 ></DD
15176 ><DT
15177 ><A
15178 NAME="PROFILEACLS"
15179 ></A
15180 >profile acls (S)</DT
15181 ><DD
15182 ><P
15183 >               This boolean parameter was added to fix the problems that people have been
15184                 having with storing user profiles on Samba shares from Windows 2000 or
15185                 Windows XP clients. New versions of Windows 2000 or Windows XP service
15186                 packs do security ACL checking on the owner and ability to write of the
15187                 profile directory stored on a local workstation when copied from a Samba
15188                 share. When not in domain mode with winbindd then the security info copied
15189                 onto the local workstation has no meaning to the logged in user (SID) on
15190                 that workstation so the profile storing fails. Adding this parameter
15191                 onto a share used for profile storage changes two things about the
15192                 returned Windows ACL. Firstly it changes the owner and group owner
15193                 of all reported files and directories to be BUILTIN\Administrators,
15194                 BUILTIN\Users respectively (SIDs S-1-5-32-544, S-1-5-32-545). Secondly
15195                 it adds an ACE entry of "Full Control" to the SID BUILTIN\Users to
15196                 every returned ACL. This will allow any Windows 2000 or XP workstation
15197                 user to access the profile. Note that if you have multiple users logging
15198                 on to a workstation then in order to prevent them from being able to access
15199                 each others profiles you must remove the "Bypass traverse checking" advanced
15200                 user right. This will prevent access to other users profile directories as
15201                 the top level profile directory (named after the user) is created by the
15202                 workstation profile code and has an ACL restricting entry to the directory
15203                 tree to the owning user.</P
15204 ><P
15205 >If you didn't understand the above text, you probably should not set
15206                 this parameter :-).</P
15207 ><P
15208 >Default <B
15209 CLASS="COMMAND"
15210 >profile acls = no</B
15211 ></P
15212 ></DD
15213 ><DT
15214 ><A
15215 NAME="PROTOCOL"
15216 ></A
15217 >protocol (G)</DT
15218 ><DD
15219 ><P
15220 >Synonym for <A
15221 HREF="#MAXPROTOCOL"
15222 >               <TT
15223 CLASS="PARAMETER"
15224 ><I
15225 >max protocol</I
15226 ></TT
15227 ></A
15228 >.</P
15229 ></DD
15230 ><DT
15231 ><A
15232 NAME="PUBLIC"
15233 ></A
15234 >public (S)</DT
15235 ><DD
15236 ><P
15237 >Synonym for <A
15238 HREF="#GUESTOK"
15239 ><TT
15240 CLASS="PARAMETER"
15241 ><I
15242 >guest
15243                 ok</I
15244 ></TT
15245 ></A
15246 >.</P
15247 ></DD
15248 ><DT
15249 ><A
15250 NAME="QUEUEPAUSECOMMAND"
15251 ></A
15252 >queuepause command (S)</DT
15253 ><DD
15254 ><P
15255 >This parameter specifies the command to be
15256                 executed on the server host in order to pause the printer queue.</P
15257 ><P
15258 >This command should be a program or script which takes
15259                 a printer name as its only parameter and stops the printer queue,
15260                 such that no longer jobs are submitted to the printer.</P
15261 ><P
15262 >This command is not supported by Windows for Workgroups,
15263                 but can be issued from the Printers window under Windows 95
15264                 and NT.</P
15265 ><P
15266 >If a <TT
15267 CLASS="PARAMETER"
15268 ><I
15269 >%p</I
15270 ></TT
15271 > is given then the printer name
15272                 is put in its place. Otherwise it is placed at the end of the command.
15273                 </P
15274 ><P
15275 >Note that it is good practice to include the absolute
15276                 path in the command as the PATH may not be available to the
15277                 server.</P
15278 ><P
15279 >Default: <EM
15280 >depends on the setting of <TT
15281 CLASS="PARAMETER"
15282 ><I
15283 >printing
15284                 </I
15285 ></TT
15286 ></EM
15287 ></P
15288 ><P
15289 >Example: <B
15290 CLASS="COMMAND"
15291 >queuepause command = disable %p</B
15292 ></P
15293 ></DD
15294 ><DT
15295 ><A
15296 NAME="QUEUERESUMECOMMAND"
15297 ></A
15298 >queueresume command (S)</DT
15299 ><DD
15300 ><P
15301 >This parameter specifies the command to be
15302                 executed on the server host in order to resume the printer queue. It
15303                 is the command to undo the behavior that is caused by the
15304                 previous parameter (<A
15305 HREF="#QUEUEPAUSECOMMAND"
15306 ><TT
15307 CLASS="PARAMETER"
15308 ><I
15309 >               queuepause command</I
15310 ></TT
15311 ></A
15312 >).</P
15313 ><P
15314 >This command should be a program or script which takes
15315                 a printer name as its only parameter and resumes the printer queue,
15316                 such that queued jobs are resubmitted to the printer.</P
15317 ><P
15318 >This command is not supported by Windows for Workgroups,
15319                 but can be issued from the Printers window under Windows 95
15320                 and NT.</P
15321 ><P
15322 >If a <TT
15323 CLASS="PARAMETER"
15324 ><I
15325 >%p</I
15326 ></TT
15327 > is given then the printer name
15328                 is put in its place. Otherwise it is placed at the end of the
15329                 command.</P
15330 ><P
15331 >Note that it is good practice to include the absolute
15332                 path in the command as the PATH may not be available to the
15333                 server.</P
15334 ><P
15335 >Default: <EM
15336 >depends on the setting of <A
15337 HREF="#PRINTING"
15338 ><TT
15339 CLASS="PARAMETER"
15340 ><I
15341 >printing</I
15342 ></TT
15343 ></A
15344 ></EM
15345 >
15346                 </P
15347 ><P
15348 >Example: <B
15349 CLASS="COMMAND"
15350 >queuepause command = enable %p
15351                 </B
15352 ></P
15353 ></DD
15354 ><DT
15355 ><A
15356 NAME="READBMPX"
15357 ></A
15358 >read bmpx (G)</DT
15359 ><DD
15360 ><P
15361 >This boolean parameter controls whether <A
15362 HREF="smbd.8.html"
15363 TARGET="_top"
15364 >smbd(8)</A
15365 > will support the "Read
15366                 Block Multiplex" SMB. This is now rarely used and defaults to
15367                 <TT
15368 CLASS="CONSTANT"
15369 >no</TT
15370 >. You should never need to set this
15371                 parameter.</P
15372 ><P
15373 >Default: <B
15374 CLASS="COMMAND"
15375 >read bmpx = no</B
15376 ></P
15377 ></DD
15378 ><DT
15379 ><A
15380 NAME="READLIST"
15381 ></A
15382 >read list (S)</DT
15383 ><DD
15384 ><P
15385 >This is a list of users that are given read-only
15386                 access to a service. If the connecting user is in this list then
15387                 they will not be given write access, no matter what the <A
15388 HREF="#READONLY"
15389 ><TT
15390 CLASS="PARAMETER"
15391 ><I
15392 >read only</I
15393 ></TT
15394 ></A
15395 >
15396                 option is set to. The list can include group names using the
15397                 syntax described in the <A
15398 HREF="#INVALIDUSERS"
15399 ><TT
15400 CLASS="PARAMETER"
15401 ><I
15402 >               invalid users</I
15403 ></TT
15404 ></A
15405 > parameter.</P
15406 ><P
15407 >See also the <A
15408 HREF="#WRITELIST"
15409 ><TT
15410 CLASS="PARAMETER"
15411 ><I
15412 >               write list</I
15413 ></TT
15414 ></A
15415 > parameter and the <A
15416 HREF="#INVALIDUSERS"
15417 ><TT
15418 CLASS="PARAMETER"
15419 ><I
15420 >invalid users</I
15421 ></TT
15422 >
15423                 </A
15424 > parameter.</P
15425 ><P
15426 >Default: <B
15427 CLASS="COMMAND"
15428 >read list = &#60;empty string&#62;</B
15429 ></P
15430 ><P
15431 >Example: <B
15432 CLASS="COMMAND"
15433 >read list = mary, @students</B
15434 ></P
15435 ></DD
15436 ><DT
15437 ><A
15438 NAME="READONLY"
15439 ></A
15440 >read only (S)</DT
15441 ><DD
15442 ><P
15443 >An inverted synonym is <A
15444 HREF="#WRITEABLE"
15445 >               <TT
15446 CLASS="PARAMETER"
15447 ><I
15448 >writeable</I
15449 ></TT
15450 ></A
15451 >.</P
15452 ><P
15453 >If this parameter is <TT
15454 CLASS="CONSTANT"
15455 >yes</TT
15456 >, then users
15457                 of a service may not create or modify files in the service's
15458                 directory.</P
15459 ><P
15460 >Note that a printable service (<B
15461 CLASS="COMMAND"
15462 >printable = yes</B
15463 >)
15464                 will <EM
15465 >ALWAYS</EM
15466 > allow writing to the directory
15467                 (user privileges permitting), but only via spooling operations.</P
15468 ><P
15469 >Default: <B
15470 CLASS="COMMAND"
15471 >read only = yes</B
15472 ></P
15473 ></DD
15474 ><DT
15475 ><A
15476 NAME="READRAW"
15477 ></A
15478 >read raw (G)</DT
15479 ><DD
15480 ><P
15481 >This parameter controls whether or not the server
15482                 will support the raw read SMB requests when transferring data
15483                 to clients.</P
15484 ><P
15485 >If enabled, raw reads allow reads of 65535 bytes in
15486                 one packet. This typically provides a major performance benefit.
15487                 </P
15488 ><P
15489 >However, some clients either negotiate the allowable
15490                 block size incorrectly or are incapable of supporting larger block
15491                 sizes, and for these clients you may need to disable raw reads.</P
15492 ><P
15493 >In general this parameter should be viewed as a system tuning
15494                 tool and left severely alone. See also <A
15495 HREF="#WRITERAW"
15496 >               <TT
15497 CLASS="PARAMETER"
15498 ><I
15499 >write raw</I
15500 ></TT
15501 ></A
15502 >.</P
15503 ><P
15504 >Default: <B
15505 CLASS="COMMAND"
15506 >read raw = yes</B
15507 ></P
15508 ></DD
15509 ><DT
15510 ><A
15511 NAME="READSIZE"
15512 ></A
15513 >read size (G)</DT
15514 ><DD
15515 ><P
15516 >The option <TT
15517 CLASS="PARAMETER"
15518 ><I
15519 >read size</I
15520 ></TT
15521 >
15522                 affects the overlap of disk reads/writes with network reads/writes.
15523                 If the amount of data being transferred in several of the SMB
15524                 commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger
15525                 than this value then the server begins writing the data before it
15526                 has received the whole packet from the network, or in the case of
15527                 SMBreadbraw, it begins writing to the network before all the data
15528                 has been read from disk.</P
15529 ><P
15530 >This overlapping works best when the speeds of disk and
15531                 network access are similar, having very little effect when the
15532                 speed of one is much greater than the other.</P
15533 ><P
15534 >The default value is 16384, but very little experimentation
15535                 has been done yet to determine the optimal value, and it is likely
15536                 that the best value will vary greatly between systems anyway.
15537                 A value over 65536 is pointless and will cause you to allocate
15538                 memory unnecessarily.</P
15539 ><P
15540 >Default: <B
15541 CLASS="COMMAND"
15542 >read size = 16384</B
15543 ></P
15544 ><P
15545 >Example: <B
15546 CLASS="COMMAND"
15547 >read size = 8192</B
15548 ></P
15549 ></DD
15550 ><DT
15551 ><A
15552 NAME="REMOTEANNOUNCE"
15553 ></A
15554 >remote announce (G)</DT
15555 ><DD
15556 ><P
15557 >This option allows you to setup <A
15558 HREF="nmbd.8.html"
15559 TARGET="_top"
15560 >nmbd(8)</A
15561 > to periodically announce itself
15562                 to arbitrary IP addresses with an arbitrary workgroup name.</P
15563 ><P
15564 >This is useful if you want your Samba server to appear
15565                 in a remote workgroup for which the normal browse propagation
15566                 rules don't work. The remote workgroup can be anywhere that you
15567                 can send IP packets to.</P
15568 ><P
15569 >For example:</P
15570 ><P
15571 ><B
15572 CLASS="COMMAND"
15573 >remote announce = 192.168.2.255/SERVERS
15574                 192.168.4.255/STAFF</B
15575 ></P
15576 ><P
15577 >the above line would cause <B
15578 CLASS="COMMAND"
15579 >nmbd</B
15580 > to announce itself
15581                 to the two given IP addresses using the given workgroup names.
15582                 If you leave out the workgroup name then the one given in
15583                 the <A
15584 HREF="#WORKGROUP"
15585 ><TT
15586 CLASS="PARAMETER"
15587 ><I
15588 >workgroup</I
15589 ></TT
15590 ></A
15591 >
15592                 parameter is used instead.</P
15593 ><P
15594 >The IP addresses you choose would normally be the broadcast
15595                 addresses of the remote networks, but can also be the IP addresses
15596                 of known browse masters if your network config is that stable.</P
15597 ><P
15598 >See the documentation file <TT
15599 CLASS="FILENAME"
15600 >BROWSING.txt</TT
15601 >
15602                 in the <TT
15603 CLASS="FILENAME"
15604 >docs/</TT
15605 > directory.</P
15606 ><P
15607 >Default: <B
15608 CLASS="COMMAND"
15609 >remote announce = &#60;empty string&#62;
15610                 </B
15611 ></P
15612 ></DD
15613 ><DT
15614 ><A
15615 NAME="REMOTEBROWSESYNC"
15616 ></A
15617 >remote browse sync (G)</DT
15618 ><DD
15619 ><P
15620 >This option allows you to setup <A
15621 HREF="nmbd.8.html"
15622 TARGET="_top"
15623 >nmbd(8)</A
15624 > to periodically request
15625                 synchronization of browse lists with the master browser of a Samba
15626                 server that is on a remote segment. This option will allow you to
15627                 gain browse lists for multiple workgroups across routed networks. This
15628                 is done in a manner that does not work with any non-Samba servers.</P
15629 ><P
15630 >This is useful if you want your Samba server and all local
15631                 clients to appear in a remote workgroup for which the normal browse
15632                 propagation rules don't work. The remote workgroup can be anywhere
15633                 that you can send IP packets to.</P
15634 ><P
15635 >For example:</P
15636 ><P
15637 ><B
15638 CLASS="COMMAND"
15639 >remote browse sync = 192.168.2.255 192.168.4.255
15640                 </B
15641 ></P
15642 ><P
15643 >the above line would cause <B
15644 CLASS="COMMAND"
15645 >nmbd</B
15646 > to request
15647                 the master browser on the specified subnets or addresses to
15648                 synchronize their browse lists with the local server.</P
15649 ><P
15650 >The IP addresses you choose would normally be the broadcast
15651                 addresses of the remote networks, but can also be the IP addresses
15652                 of known browse masters if your network config is that stable. If
15653                 a machine IP address is given Samba makes NO attempt to validate
15654                 that the remote machine is available, is listening, nor that it
15655                 is in fact the browse master on its segment.</P
15656 ><P
15657 >Default: <B
15658 CLASS="COMMAND"
15659 >remote browse sync = &#60;empty string&#62;
15660                 </B
15661 ></P
15662 ></DD
15663 ><DT
15664 ><A
15665 NAME="RESTRICTANONYMOUS"
15666 ></A
15667 >restrict anonymous (G)</DT
15668 ><DD
15669 ><P
15670 >This is a boolean parameter.  If it is <TT
15671 CLASS="CONSTANT"
15672 >yes</TT
15673 >, then
15674                 anonymous access to the server will be restricted, namely in the
15675                 case where the server is expecting the client to send a username,
15676                 but it doesn't.  Setting it to <TT
15677 CLASS="CONSTANT"
15678 >yes</TT
15679 > will force these anonymous
15680                 connections to be denied, and the client will be required to always
15681                 supply a username and password when connecting. Use of this parameter
15682                 is only recommended for homogeneous NT client environments.</P
15683 ><P
15684 >This parameter makes the use of macro expansions that rely
15685                 on the username (%U, %G, etc) consistent.  NT 4.0
15686                 likes to use anonymous connections when refreshing the share list,
15687                 and this is a way to work around that.</P
15688 ><P
15689 >When restrict anonymous is <TT
15690 CLASS="CONSTANT"
15691 >yes</TT
15692 >, all anonymous connections
15693                 are denied no matter what they are for.  This can effect the ability
15694                 of a machine to access the Samba Primary Domain Controller to revalidate
15695                 its machine account after someone else has logged on the client
15696                 interactively.  The NT client will display a message saying that
15697                 the machine's account in  the domain doesn't exist or the password is
15698                 bad.  The best way to deal  with this is to reboot NT client machines
15699                 between interactive logons,  using "Shutdown and Restart", rather
15700                 than "Close all programs and logon as a different user".</P
15701 ><P
15702 >Default: <B
15703 CLASS="COMMAND"
15704 >restrict anonymous = no</B
15705 ></P
15706 ></DD
15707 ><DT
15708 ><A
15709 NAME="ROOT"
15710 ></A
15711 >root (G)</DT
15712 ><DD
15713 ><P
15714 >Synonym for <A
15715 HREF="#ROOTDIRECTORY"
15716 >               <TT
15717 CLASS="PARAMETER"
15718 ><I
15719 >root directory"</I
15720 ></TT
15721 ></A
15722 >.</P
15723 ></DD
15724 ><DT
15725 ><A
15726 NAME="ROOTDIR"
15727 ></A
15728 >root dir (G)</DT
15729 ><DD
15730 ><P
15731 >Synonym for <A
15732 HREF="#ROOTDIRECTORY"
15733 >               <TT
15734 CLASS="PARAMETER"
15735 ><I
15736 >root directory"</I
15737 ></TT
15738 ></A
15739 >.</P
15740 ></DD
15741 ><DT
15742 ><A
15743 NAME="ROOTDIRECTORY"
15744 ></A
15745 >root directory (G)</DT
15746 ><DD
15747 ><P
15748 >The server will <B
15749 CLASS="COMMAND"
15750 >chroot()</B
15751 > (i.e.
15752                 Change its root directory) to this directory on startup. This is
15753                 not strictly necessary for secure operation. Even without it the
15754                 server will deny access to files not in one of the service entries.
15755                 It may also check for, and deny access to, soft links to other
15756                 parts of the filesystem, or attempts to use ".." in file names
15757                 to access other directories (depending on the setting of the <A
15758 HREF="#WIDELINKS"
15759 ><TT
15760 CLASS="PARAMETER"
15761 ><I
15762 >wide links</I
15763 ></TT
15764 ></A
15765 >
15766                 parameter).</P
15767 ><P
15768 >Adding a <TT
15769 CLASS="PARAMETER"
15770 ><I
15771 >root directory</I
15772 ></TT
15773 > entry other
15774                 than "/" adds an extra level of security, but at a price. It
15775                 absolutely ensures that no access is given to files not in the
15776                 sub-tree specified in the <TT
15777 CLASS="PARAMETER"
15778 ><I
15779 >root directory</I
15780 ></TT
15781 >
15782                 option, <EM
15783 >including</EM
15784 > some files needed for
15785                 complete operation of the server. To maintain full operability
15786                 of the server you will need to mirror some system files
15787                 into the <TT
15788 CLASS="PARAMETER"
15789 ><I
15790 >root directory</I
15791 ></TT
15792 > tree. In particular
15793                 you will need to mirror <TT
15794 CLASS="FILENAME"
15795 >/etc/passwd</TT
15796 > (or a
15797                 subset of it), and any binaries or configuration files needed for
15798                 printing (if required). The set of files that must be mirrored is
15799                 operating system dependent.</P
15800 ><P
15801 >Default: <B
15802 CLASS="COMMAND"
15803 >root directory = /</B
15804 ></P
15805 ><P
15806 >Example: <B
15807 CLASS="COMMAND"
15808 >root directory = /homes/smb</B
15809 ></P
15810 ></DD
15811 ><DT
15812 ><A
15813 NAME="ROOTPOSTEXEC"
15814 ></A
15815 >root postexec (S)</DT
15816 ><DD
15817 ><P
15818 >This is the same as the <TT
15819 CLASS="PARAMETER"
15820 ><I
15821 >postexec</I
15822 ></TT
15823 >
15824                 parameter except that the command is run as root. This
15825                 is useful for unmounting filesystems
15826                 (such as CDROMs) after a connection is closed.</P
15827 ><P
15828 >See also <A
15829 HREF="#POSTEXEC"
15830 ><TT
15831 CLASS="PARAMETER"
15832 ><I
15833 >               postexec</I
15834 ></TT
15835 ></A
15836 >.</P
15837 ><P
15838 >Default: <B
15839 CLASS="COMMAND"
15840 >root postexec = &#60;empty string&#62;
15841                 </B
15842 ></P
15843 ></DD
15844 ><DT
15845 ><A
15846 NAME="ROOTPREEXEC"
15847 ></A
15848 >root preexec (S)</DT
15849 ><DD
15850 ><P
15851 >This is the same as the <TT
15852 CLASS="PARAMETER"
15853 ><I
15854 >preexec</I
15855 ></TT
15856 >
15857                 parameter except that the command is run as root. This
15858                 is useful for mounting filesystems (such as CDROMs) when a
15859                 connection is opened.</P
15860 ><P
15861 >See also <A
15862 HREF="#PREEXEC"
15863 ><TT
15864 CLASS="PARAMETER"
15865 ><I
15866 >               preexec</I
15867 ></TT
15868 ></A
15869 > and <A
15870 HREF="#PREEXECCLOSE"
15871 >               <TT
15872 CLASS="PARAMETER"
15873 ><I
15874 >preexec close</I
15875 ></TT
15876 ></A
15877 >.</P
15878 ><P
15879 >Default: <B
15880 CLASS="COMMAND"
15881 >root preexec = &#60;empty string&#62;
15882                 </B
15883 ></P
15884 ></DD
15885 ><DT
15886 ><A
15887 NAME="ROOTPREEXECCLOSE"
15888 ></A
15889 >root preexec close (S)</DT
15890 ><DD
15891 ><P
15892 >This is the same as the <TT
15893 CLASS="PARAMETER"
15894 ><I
15895 >preexec close
15896                 </I
15897 ></TT
15898 > parameter except that the command is run as root.</P
15899 ><P
15900 >See also <A
15901 HREF="#PREEXEC"
15902 ><TT
15903 CLASS="PARAMETER"
15904 ><I
15905 >               preexec</I
15906 ></TT
15907 ></A
15908 > and <A
15909 HREF="#PREEXECCLOSE"
15910 >               <TT
15911 CLASS="PARAMETER"
15912 ><I
15913 >preexec close</I
15914 ></TT
15915 ></A
15916 >.</P
15917 ><P
15918 >Default: <B
15919 CLASS="COMMAND"
15920 >root preexec close = no</B
15921 ></P
15922 ></DD
15923 ><DT
15924 ><A
15925 NAME="SECURITY"
15926 ></A
15927 >security (G)</DT
15928 ><DD
15929 ><P
15930 >This option affects how clients respond to
15931                 Samba and is one of the most important settings in the <TT
15932 CLASS="FILENAME"
15933 >               smb.conf</TT
15934 > file.</P
15935 ><P
15936 >The option sets the "security mode bit" in replies to
15937                 protocol negotiations with <A
15938 HREF="smbd.8.html"
15939 TARGET="_top"
15940 >smbd(8)
15941                 </A
15942 > to turn share level security on or off. Clients decide
15943                 based on this bit whether (and how) to transfer user and password
15944                 information to the server.</P
15945 ><P
15946 >The default is <B
15947 CLASS="COMMAND"
15948 >security = user</B
15949 >, as this is
15950                 the most common setting needed when talking to Windows 98 and
15951                 Windows NT.</P
15952 ><P
15953 >The alternatives are <B
15954 CLASS="COMMAND"
15955 >security = share</B
15956 >,
15957                 <B
15958 CLASS="COMMAND"
15959 >security = server</B
15960 > or <B
15961 CLASS="COMMAND"
15962 >security = domain
15963                 </B
15964 >.</P
15965 ><P
15966 >In versions of Samba prior to 2.0.0, the default was
15967                 <B
15968 CLASS="COMMAND"
15969 >security = share</B
15970 > mainly because that was
15971                 the only option at one stage.</P
15972 ><P
15973 >There is a bug in WfWg that has relevance to this
15974                 setting. When in user or server level security a WfWg client
15975                 will totally ignore the password you type in the "connect
15976                 drive" dialog box. This makes it very difficult (if not impossible)
15977                 to connect to a Samba service as anyone except the user that
15978                 you are logged into WfWg as.</P
15979 ><P
15980 >If your PCs use usernames that are the same as their
15981                 usernames on the UNIX machine then you will want to use
15982                 <B
15983 CLASS="COMMAND"
15984 >security = user</B
15985 >. If you mostly use usernames
15986                 that don't exist on the UNIX box then use <B
15987 CLASS="COMMAND"
15988 >security =
15989                 share</B
15990 >.</P
15991 ><P
15992 >You should also use <B
15993 CLASS="COMMAND"
15994 >security = share</B
15995 > if you
15996                 want to mainly setup shares without a password (guest shares). This
15997                 is commonly used for a shared printer server. It is more difficult
15998                 to setup guest shares with <B
15999 CLASS="COMMAND"
16000 >security = user</B
16001 >, see
16002                 the <A
16003 HREF="#MAPTOGUEST"
16004 ><TT
16005 CLASS="PARAMETER"
16006 ><I
16007 >map to guest</I
16008 ></TT
16009 >
16010                 </A
16011 >parameter for details.</P
16012 ><P
16013 >It is possible to use <B
16014 CLASS="COMMAND"
16015 >smbd</B
16016 > in a <EM
16017 >               hybrid mode</EM
16018 > where it is offers both user and share
16019                 level security under different <A
16020 HREF="#NETBIOSALIASES"
16021 >               <TT
16022 CLASS="PARAMETER"
16023 ><I
16024 >NetBIOS aliases</I
16025 ></TT
16026 ></A
16027 >. </P
16028 ><P
16029 >The different settings will now be explained.</P
16030 ><P
16031 ><A
16032 NAME="SECURITYEQUALSSHARE"
16033 ></A
16034 ><EM
16035 >SECURITY = SHARE
16036                 </EM
16037 ></P
16038 ><P
16039 >When clients connect to a share level security server they
16040                 need not log onto the server with a valid username and password before
16041                 attempting to connect to a shared resource (although modern clients
16042                 such as Windows 95/98 and Windows NT will send a logon request with
16043                 a username but no password when talking to a <B
16044 CLASS="COMMAND"
16045 >security = share
16046                 </B
16047 > server). Instead, the clients send authentication information
16048                 (passwords) on a per-share basis, at the time they attempt to connect
16049                 to that share.</P
16050 ><P
16051 >Note that <B
16052 CLASS="COMMAND"
16053 >smbd</B
16054 > <EM
16055 >ALWAYS</EM
16056 >
16057                 uses a valid UNIX user to act on behalf of the client, even in
16058                 <B
16059 CLASS="COMMAND"
16060 >security = share</B
16061 > level security.</P
16062 ><P
16063 >As clients are not required to send a username to the server
16064                 in share level security, <B
16065 CLASS="COMMAND"
16066 >smbd</B
16067 > uses several
16068                 techniques to determine the correct UNIX user to use on behalf
16069                 of the client.</P
16070 ><P
16071 >A list of possible UNIX usernames to match with the given
16072                 client password is constructed using the following methods :</P
16073 ><P
16074 ></P
16075 ><UL
16076 ><LI
16077 ><P
16078 >If the <A
16079 HREF="#GUESTONLY"
16080 ><TT
16081 CLASS="PARAMETER"
16082 ><I
16083 >guest
16084                         only</I
16085 ></TT
16086 ></A
16087 > parameter is set, then all the other
16088                         stages are missed and only the <A
16089 HREF="#GUESTACCOUNT"
16090 >                       <TT
16091 CLASS="PARAMETER"
16092 ><I
16093 >guest account</I
16094 ></TT
16095 ></A
16096 > username is checked.
16097                         </P
16098 ></LI
16099 ><LI
16100 ><P
16101 >Is a username is sent with the share connection
16102                         request, then this username (after mapping - see <A
16103 HREF="#USERNAMEMAP"
16104 ><TT
16105 CLASS="PARAMETER"
16106 ><I
16107 >username map</I
16108 ></TT
16109 ></A
16110 >),
16111                         is added as a potential username.</P
16112 ></LI
16113 ><LI
16114 ><P
16115 >If the client did a previous <EM
16116 >logon
16117                         </EM
16118 > request (the SessionSetup SMB call) then the
16119                         username sent in this SMB will be added as a potential username.
16120                         </P
16121 ></LI
16122 ><LI
16123 ><P
16124 >The name of the service the client requested is
16125                         added as a potential username.</P
16126 ></LI
16127 ><LI
16128 ><P
16129 >The NetBIOS name of the client is added to
16130                         the list as a potential username.</P
16131 ></LI
16132 ><LI
16133 ><P
16134 >Any users on the <A
16135 HREF="#USER"
16136 ><TT
16137 CLASS="PARAMETER"
16138 ><I
16139 >                       user</I
16140 ></TT
16141 ></A
16142 > list are added as potential usernames.
16143                         </P
16144 ></LI
16145 ></UL
16146 ><P
16147 >If the <TT
16148 CLASS="PARAMETER"
16149 ><I
16150 >guest only</I
16151 ></TT
16152 > parameter is
16153                 not set, then this list is then tried with the supplied password.
16154                 The first user for whom the password matches will be used as the
16155                 UNIX user.</P
16156 ><P
16157 >If the <TT
16158 CLASS="PARAMETER"
16159 ><I
16160 >guest only</I
16161 ></TT
16162 > parameter is
16163                 set, or no username can be determined then if the share is marked
16164                 as available to the <TT
16165 CLASS="PARAMETER"
16166 ><I
16167 >guest account</I
16168 ></TT
16169 >, then this
16170                 guest user will be used, otherwise access is denied.</P
16171 ><P
16172 >Note that it can be <EM
16173 >very</EM
16174 > confusing
16175                 in share-level security as to which UNIX username will eventually
16176                 be used in granting access.</P
16177 ><P
16178 >See also the section <A
16179 HREF="#AEN241"
16180 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16181 >.</P
16182 ><P
16183 ><A
16184 NAME="SECURITYEQUALSUSER"
16185 ></A
16186 ><EM
16187 >SECURITY = USER
16188                 </EM
16189 ></P
16190 ><P
16191 >This is the default security setting in Samba 2.2.
16192                 With user-level security a client must first "log-on" with a
16193                 valid username and password (which can be mapped using the <A
16194 HREF="#USERNAMEMAP"
16195 ><TT
16196 CLASS="PARAMETER"
16197 ><I
16198 >username map</I
16199 ></TT
16200 ></A
16201 >
16202                 parameter). Encrypted passwords (see the <A
16203 HREF="#ENCRYPTPASSWORDS"
16204 >               <TT
16205 CLASS="PARAMETER"
16206 ><I
16207 >encrypted passwords</I
16208 ></TT
16209 ></A
16210 > parameter) can also
16211                 be used in this security mode. Parameters such as <A
16212 HREF="#USER"
16213 >               <TT
16214 CLASS="PARAMETER"
16215 ><I
16216 >user</I
16217 ></TT
16218 ></A
16219 > and <A
16220 HREF="#GUESTONLY"
16221 >               <TT
16222 CLASS="PARAMETER"
16223 ><I
16224 >guest only</I
16225 ></TT
16226 ></A
16227 > if set        are then applied and
16228                 may change the UNIX user to use on this connection, but only after
16229                 the user has been successfully authenticated.</P
16230 ><P
16231 ><EM
16232 >Note</EM
16233 > that the name of the resource being
16234                 requested is <EM
16235 >not</EM
16236 > sent to the server until after
16237                 the server has successfully authenticated the client. This is why
16238                 guest shares don't work in user level security without allowing
16239                 the server to automatically map unknown users into the <A
16240 HREF="#GUESTACCOUNT"
16241 ><TT
16242 CLASS="PARAMETER"
16243 ><I
16244 >guest account</I
16245 ></TT
16246 ></A
16247 >.
16248                 See the <A
16249 HREF="#MAPTOGUEST"
16250 ><TT
16251 CLASS="PARAMETER"
16252 ><I
16253 >map to guest</I
16254 ></TT
16255 >
16256                 </A
16257 > parameter for details on doing this.</P
16258 ><P
16259 >See also the section <A
16260 HREF="#AEN241"
16261 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16262 >.</P
16263 ><P
16264 ><A
16265 NAME="SECURITYEQUALSSERVER"
16266 ></A
16267 ><EM
16268 >SECURITY = SERVER
16269                 </EM
16270 ></P
16271 ><P
16272 >In this mode Samba will try to validate the username/password
16273                 by passing it to another SMB server, such as an NT box. If this
16274                 fails it will revert to <B
16275 CLASS="COMMAND"
16276 >security = user</B
16277 >, but note
16278                 that if encrypted passwords have been negotiated then Samba cannot
16279                 revert back to checking the UNIX password file, it must have a valid
16280                 <TT
16281 CLASS="FILENAME"
16282 >smbpasswd</TT
16283 > file to check users against. See the
16284                 documentation file in the <TT
16285 CLASS="FILENAME"
16286 >docs/</TT
16287 > directory
16288                 <TT
16289 CLASS="FILENAME"
16290 >ENCRYPTION.txt</TT
16291 > for details on how to set this
16292                 up.</P
16293 ><P
16294 ><EM
16295 >Note</EM
16296 > that from the client's point of
16297                 view <B
16298 CLASS="COMMAND"
16299 >security = server</B
16300 > is the same as <B
16301 CLASS="COMMAND"
16302 >               security = user</B
16303 >.  It only affects how the server deals
16304                 with the authentication, it does not in any way affect what the
16305                 client sees.</P
16306 ><P
16307 ><EM
16308 >Note</EM
16309 > that the name of the resource being
16310                 requested is <EM
16311 >not</EM
16312 > sent to the server until after
16313                 the server has successfully authenticated the client. This is why
16314                 guest shares don't work in user level security without allowing
16315                 the server to automatically map unknown users into the <A
16316 HREF="#GUESTACCOUNT"
16317 ><TT
16318 CLASS="PARAMETER"
16319 ><I
16320 >guest account</I
16321 ></TT
16322 ></A
16323 >.
16324                 See the <A
16325 HREF="#MAPTOGUEST"
16326 ><TT
16327 CLASS="PARAMETER"
16328 ><I
16329 >map to guest</I
16330 ></TT
16331 >
16332                 </A
16333 > parameter for details on doing this.</P
16334 ><P
16335 >See also the section <A
16336 HREF="#AEN241"
16337 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16338 >.</P
16339 ><P
16340 >See also the <A
16341 HREF="#PASSWORDSERVER"
16342 ><TT
16343 CLASS="PARAMETER"
16344 ><I
16345 >password
16346                 server</I
16347 ></TT
16348 ></A
16349 > parameter and the <A
16350 HREF="#ENCRYPTPASSWORDS"
16351 ><TT
16352 CLASS="PARAMETER"
16353 ><I
16354 >encrypted passwords</I
16355 ></TT
16356 >
16357                 </A
16358 > parameter.</P
16359 ><P
16360 ><A
16361 NAME="SECURITYEQUALSDOMAIN"
16362 ></A
16363 ><EM
16364 >SECURITY = DOMAIN
16365                 </EM
16366 ></P
16367 ><P
16368 >This mode will only work correctly if <A
16369 HREF="smbpasswd.8.html"
16370 TARGET="_top"
16371 >smbpasswd(8)</A
16372 > has been used to add this
16373                 machine into a Windows NT Domain. It expects the <A
16374 HREF="#ENCRYPTPASSWORDS"
16375 ><TT
16376 CLASS="PARAMETER"
16377 ><I
16378 >encrypted passwords</I
16379 ></TT
16380 >
16381                 </A
16382 > parameter to be set to <TT
16383 CLASS="CONSTANT"
16384 >yes</TT
16385 >. In this
16386                 mode Samba will try to validate the username/password by passing
16387                 it to a Windows NT Primary or Backup Domain Controller, in exactly
16388                 the same way that a Windows NT Server would do.</P
16389 ><P
16390 ><EM
16391 >Note</EM
16392 > that a valid UNIX user must still
16393                 exist as well as the account on the Domain Controller to allow
16394                 Samba to have a valid UNIX account to map file access to.</P
16395 ><P
16396 ><EM
16397 >Note</EM
16398 > that from the client's point
16399                 of view <B
16400 CLASS="COMMAND"
16401 >security = domain</B
16402 > is the same as <B
16403 CLASS="COMMAND"
16404 >security = user
16405                 </B
16406 >. It only affects how the server deals with the authentication,
16407                 it does not in any way affect what the client sees.</P
16408 ><P
16409 ><EM
16410 >Note</EM
16411 > that the name of the resource being
16412                 requested is <EM
16413 >not</EM
16414 > sent to the server until after
16415                 the server has successfully authenticated the client. This is why
16416                 guest shares don't work in user level security without allowing
16417                 the server to automatically map unknown users into the <A
16418 HREF="#GUESTACCOUNT"
16419 ><TT
16420 CLASS="PARAMETER"
16421 ><I
16422 >guest account</I
16423 ></TT
16424 ></A
16425 >.
16426                 See the <A
16427 HREF="#MAPTOGUEST"
16428 ><TT
16429 CLASS="PARAMETER"
16430 ><I
16431 >map to guest</I
16432 ></TT
16433 >
16434                 </A
16435 > parameter for details on doing this.</P
16436 ><P
16437 ><EM
16438 >BUG:</EM
16439 > There is currently a bug in the
16440                 implementation of <B
16441 CLASS="COMMAND"
16442 >security = domain</B
16443 > with respect
16444                 to multi-byte character set usernames. The communication with a
16445                 Domain Controller must be done in UNICODE and Samba currently
16446                 does not widen multi-byte user names to UNICODE correctly, thus
16447                 a multi-byte username will not be recognized correctly at the
16448                 Domain Controller. This issue will be addressed in a future release.</P
16449 ><P
16450 >See also the section <A
16451 HREF="#AEN241"
16452 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
16453 >.</P
16454 ><P
16455 >See also the <A
16456 HREF="#PASSWORDSERVER"
16457 ><TT
16458 CLASS="PARAMETER"
16459 ><I
16460 >password
16461                 server</I
16462 ></TT
16463 ></A
16464 > parameter and the <A
16465 HREF="#ENCRYPTPASSWORDS"
16466 ><TT
16467 CLASS="PARAMETER"
16468 ><I
16469 >encrypted passwords</I
16470 ></TT
16471 >
16472                 </A
16473 > parameter.</P
16474 ><P
16475 >Default: <B
16476 CLASS="COMMAND"
16477 >security = USER</B
16478 ></P
16479 ><P
16480 >Example: <B
16481 CLASS="COMMAND"
16482 >security = DOMAIN</B
16483 ></P
16484 ></DD
16485 ><DT
16486 ><A
16487 NAME="SECURITYMASK"
16488 ></A
16489 >security mask (S)</DT
16490 ><DD
16491 ><P
16492 >This parameter controls what UNIX permission
16493                 bits can be modified when a Windows NT client is manipulating
16494                 the UNIX permission on a file using the native NT security
16495                 dialog box.</P
16496 ><P
16497 >This parameter is applied as a mask (AND'ed with) to
16498                 the changed permission bits, thus preventing any bits not in
16499                 this mask from being modified. Essentially, zero bits in this
16500                 mask may be treated as a set of bits the user is not allowed
16501                 to change.</P
16502 ><P
16503 >If not set explicitly this parameter is 0777, allowing
16504                 a user to modify all the user/group/world permissions on a file.
16505                 </P
16506 ><P
16507 ><EM
16508 >Note</EM
16509 > that users who can access the
16510                 Samba server through other means can easily bypass this
16511                 restriction, so it is primarily useful for standalone
16512                 "appliance" systems.  Administrators of most normal systems will
16513                 probably want to leave it set to <TT
16514 CLASS="CONSTANT"
16515 >0777</TT
16516 >.</P
16517 ><P
16518 >See also the <A
16519 HREF="#FORCEDIRECTORYSECURITYMODE"
16520 >               <TT
16521 CLASS="PARAMETER"
16522 ><I
16523 >force directory security mode</I
16524 ></TT
16525 ></A
16526 >,
16527                 <A
16528 HREF="#DIRECTORYSECURITYMASK"
16529 ><TT
16530 CLASS="PARAMETER"
16531 ><I
16532 >directory
16533                 security mask</I
16534 ></TT
16535 ></A
16536 >, <A
16537 HREF="#FORCESECURITYMODE"
16538 >               <TT
16539 CLASS="PARAMETER"
16540 ><I
16541 >force security mode</I
16542 ></TT
16543 ></A
16544 > parameters.</P
16545 ><P
16546 >Default: <B
16547 CLASS="COMMAND"
16548 >security mask = 0777</B
16549 ></P
16550 ><P
16551 >Example: <B
16552 CLASS="COMMAND"
16553 >security mask = 0770</B
16554 ></P
16555 ></DD
16556 ><DT
16557 ><A
16558 NAME="SERVERSTRING"
16559 ></A
16560 >server string (G)</DT
16561 ><DD
16562 ><P
16563 >This controls what string will show up in the
16564                 printer comment box in print manager and next to the IPC connection
16565                 in <B
16566 CLASS="COMMAND"
16567 >net view</B
16568 >. It can be any string that you wish
16569                 to show to your users.</P
16570 ><P
16571 >It also sets what will appear in browse lists next
16572                 to the machine name.</P
16573 ><P
16574 >A <TT
16575 CLASS="PARAMETER"
16576 ><I
16577 >%v</I
16578 ></TT
16579 > will be replaced with the Samba
16580                 version number.</P
16581 ><P
16582 >A <TT
16583 CLASS="PARAMETER"
16584 ><I
16585 >%h</I
16586 ></TT
16587 > will be replaced with the
16588                 hostname.</P
16589 ><P
16590 >Default: <B
16591 CLASS="COMMAND"
16592 >server string = Samba %v</B
16593 ></P
16594 ><P
16595 >Example: <B
16596 CLASS="COMMAND"
16597 >server string = University of GNUs Samba
16598                 Server</B
16599 ></P
16600 ></DD
16601 ><DT
16602 ><A
16603 NAME="SETDIRECTORY"
16604 ></A
16605 >set directory (S)</DT
16606 ><DD
16607 ><P
16608 >If <B
16609 CLASS="COMMAND"
16610 >set directory = no</B
16611 >, then
16612                 users of the service may not use the setdir command to change
16613                 directory.</P
16614 ><P
16615 >The <B
16616 CLASS="COMMAND"
16617 >setdir</B
16618 > command is only implemented
16619                 in the Digital Pathworks client. See the Pathworks documentation
16620                 for details.</P
16621 ><P
16622 >Default: <B
16623 CLASS="COMMAND"
16624 >set directory = no</B
16625 ></P
16626 ></DD
16627 ><DT
16628 ><A
16629 NAME="SHAREMODES"
16630 ></A
16631 >share modes (S)</DT
16632 ><DD
16633 ><P
16634 >This enables or disables the honoring of
16635                 the <TT
16636 CLASS="PARAMETER"
16637 ><I
16638 >share modes</I
16639 ></TT
16640 > during a file open. These
16641                 modes are used by clients to gain exclusive read or write access
16642                 to a file.</P
16643 ><P
16644 >These open modes are not directly supported by UNIX, so
16645                 they are simulated using shared memory, or lock files if your
16646                 UNIX doesn't support shared memory (almost all do).</P
16647 ><P
16648 >The share modes that are enabled by this option are
16649                 <TT
16650 CLASS="CONSTANT"
16651 >DENY_DOS</TT
16652 >, <TT
16653 CLASS="CONSTANT"
16654 >DENY_ALL</TT
16655 >,
16656                 <TT
16657 CLASS="CONSTANT"
16658 >DENY_READ</TT
16659 >, <TT
16660 CLASS="CONSTANT"
16661 >DENY_WRITE</TT
16662 >,
16663                 <TT
16664 CLASS="CONSTANT"
16665 >DENY_NONE</TT
16666 > and <TT
16667 CLASS="CONSTANT"
16668 >DENY_FCB</TT
16669 >.
16670                 </P
16671 ><P
16672 >This option gives full share compatibility and enabled
16673                 by default.</P
16674 ><P
16675 >You should <EM
16676 >NEVER</EM
16677 > turn this parameter
16678                 off as many Windows applications will break if you do so.</P
16679 ><P
16680 >Default: <B
16681 CLASS="COMMAND"
16682 >share modes = yes</B
16683 ></P
16684 ></DD
16685 ><DT
16686 ><A
16687 NAME="SHORTPRESERVECASE"
16688 ></A
16689 >short preserve case (S)</DT
16690 ><DD
16691 ><P
16692 >This boolean parameter controls if new files
16693                 which conform to 8.3 syntax, that is all in upper case and of
16694                 suitable length, are created upper case, or if they are forced
16695                 to be the <A
16696 HREF="#DEFAULTCASE"
16697 ><TT
16698 CLASS="PARAMETER"
16699 ><I
16700 >default case
16701                 </I
16702 ></TT
16703 ></A
16704 >. This  option can be use with <A
16705 HREF="#PRESERVECASE"
16706 ><B
16707 CLASS="COMMAND"
16708 >preserve case = yes</B
16709 >
16710                 </A
16711 > to permit long filenames to retain their case, while short
16712                 names are lowered. </P
16713 ><P
16714 >See the section on <A
16715 HREF="#AEN203"
16716 >               NAME MANGLING</A
16717 >.</P
16718 ><P
16719 >Default: <B
16720 CLASS="COMMAND"
16721 >short preserve case = yes</B
16722 ></P
16723 ></DD
16724 ><DT
16725 ><A
16726 NAME="SHOWADDPRINTERWIZARD"
16727 ></A
16728 >show add printer wizard (G)</DT
16729 ><DD
16730 ><P
16731 >With the introduction of MS-RPC based printing support
16732                 for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will
16733                 appear on Samba hosts in the share listing.  Normally this folder will
16734                 contain an icon for the MS Add Printer Wizard (APW).  However, it is
16735                 possible to disable this feature regardless of the level of privilege
16736                 of the connected user.</P
16737 ><P
16738 >Under normal circumstances, the Windows NT/2000 client will
16739                 open a handle on the printer server with OpenPrinterEx() asking for
16740                 Administrator privileges.  If the user does not have administrative
16741                 access on the print server (i.e is not root or a member of the
16742                 <TT
16743 CLASS="PARAMETER"
16744 ><I
16745 >printer admin</I
16746 ></TT
16747 > group), the OpenPrinterEx()
16748                 call fails and the client makes another open call with a request for
16749                 a lower privilege level.  This should succeed, however the APW
16750                 icon will not be displayed.</P
16751 ><P
16752 >Disabling the <TT
16753 CLASS="PARAMETER"
16754 ><I
16755 >show add printer wizard</I
16756 ></TT
16757 >
16758                 parameter will always cause the OpenPrinterEx() on the server
16759                 to fail.  Thus the APW icon will never be displayed. <EM
16760 >               Note :</EM
16761 >This does not prevent the same user from having
16762                 administrative privilege on an individual printer.</P
16763 ><P
16764 >See also <A
16765 HREF="#ADDPRINTERCOMMAND"
16766 ><TT
16767 CLASS="PARAMETER"
16768 ><I
16769 >addprinter
16770                 command</I
16771 ></TT
16772 ></A
16773 >, <A
16774 HREF="#DELETEPRINTERCOMMAND"
16775 >               <TT
16776 CLASS="PARAMETER"
16777 ><I
16778 >deleteprinter command</I
16779 ></TT
16780 ></A
16781 >, <A
16782 HREF="#PRINTERADMIN"
16783 ><TT
16784 CLASS="PARAMETER"
16785 ><I
16786 >printer admin</I
16787 ></TT
16788 ></A
16789 ></P
16790 ><P
16791 >Default :<B
16792 CLASS="COMMAND"
16793 >show add printer wizard = yes</B
16794 ></P
16795 ></DD
16796 ><DT
16797 ><A
16798 NAME="SMBPASSWDFILE"
16799 ></A
16800 >smb passwd file (G)</DT
16801 ><DD
16802 ><P
16803 >This option sets the path to the encrypted
16804                 smbpasswd file.  By default the path to the smbpasswd file
16805                 is compiled into Samba.</P
16806 ><P
16807 >Default: <B
16808 CLASS="COMMAND"
16809 >smb passwd file = ${prefix}/private/smbpasswd
16810                 </B
16811 ></P
16812 ><P
16813 >Example: <B
16814 CLASS="COMMAND"
16815 >smb passwd file = /etc/samba/smbpasswd
16816                 </B
16817 ></P
16818 ></DD
16819 ><DT
16820 ><A
16821 NAME="SOCKETADDRESS"
16822 ></A
16823 >socket address (G)</DT
16824 ><DD
16825 ><P
16826 >This option allows you to control what
16827                 address Samba will listen for connections on. This is used to
16828                 support multiple virtual interfaces on the one server, each
16829                 with a different configuration.</P
16830 ><P
16831 >By default Samba will accept connections on any
16832                 address.</P
16833 ><P
16834 >Example: <B
16835 CLASS="COMMAND"
16836 >socket address = 192.168.2.20</B
16837 >
16838                 </P
16839 ></DD
16840 ><DT
16841 ><A
16842 NAME="SOCKETOPTIONS"
16843 ></A
16844 >socket options (G)</DT
16845 ><DD
16846 ><P
16847 >This option allows you to set socket options
16848                 to be used when talking with the client.</P
16849 ><P
16850 >Socket options are controls on the networking layer
16851                 of the operating systems which allow the connection to be
16852                 tuned.</P
16853 ><P
16854 >This option will typically be used to tune your Samba
16855                 server for optimal performance for your local network. There is
16856                 no way that Samba can know what the optimal parameters are for
16857                 your net, so you must experiment and choose them yourself. We
16858                 strongly suggest you read the appropriate documentation for your
16859                 operating system first (perhaps <B
16860 CLASS="COMMAND"
16861 >man setsockopt</B
16862 >
16863                 will help).</P
16864 ><P
16865 >You may find that on some systems Samba will say
16866                 "Unknown socket option" when you supply an option. This means you
16867                 either incorrectly  typed it or you need to add an include file
16868                 to includes.h for your OS.  If the latter is the case please
16869                 send the patch to <A
16870 HREF="mailto:samba@samba.org"
16871 TARGET="_top"
16872 >               samba@samba.org</A
16873 >.</P
16874 ><P
16875 >Any of the supported socket options may be combined
16876                 in any way you like, as long as your OS allows it.</P
16877 ><P
16878 >This is the list of socket options currently settable
16879                 using this option:</P
16880 ><P
16881 ></P
16882 ><UL
16883 ><LI
16884 ><P
16885 >SO_KEEPALIVE</P
16886 ></LI
16887 ><LI
16888 ><P
16889 >SO_REUSEADDR</P
16890 ></LI
16891 ><LI
16892 ><P
16893 >SO_BROADCAST</P
16894 ></LI
16895 ><LI
16896 ><P
16897 >TCP_NODELAY</P
16898 ></LI
16899 ><LI
16900 ><P
16901 >IPTOS_LOWDELAY</P
16902 ></LI
16903 ><LI
16904 ><P
16905 >IPTOS_THROUGHPUT</P
16906 ></LI
16907 ><LI
16908 ><P
16909 >SO_SNDBUF *</P
16910 ></LI
16911 ><LI
16912 ><P
16913 >SO_RCVBUF *</P
16914 ></LI
16915 ><LI
16916 ><P
16917 >SO_SNDLOWAT *</P
16918 ></LI
16919 ><LI
16920 ><P
16921 >SO_RCVLOWAT *</P
16922 ></LI
16923 ></UL
16924 ><P
16925 >Those marked with a <EM
16926 >'*'</EM
16927 > take an integer
16928                 argument. The others can optionally take a 1 or 0 argument to enable
16929                 or disable the option, by default they will be enabled if you
16930                 don't specify 1 or 0.</P
16931 ><P
16932 >To specify an argument use the syntax SOME_OPTION = VALUE
16933                 for example <B
16934 CLASS="COMMAND"
16935 >SO_SNDBUF = 8192</B
16936 >. Note that you must
16937                 not have any spaces before or after the = sign.</P
16938 ><P
16939 >If you are on a local network then a sensible option
16940                 might be</P
16941 ><P
16942 ><B
16943 CLASS="COMMAND"
16944 >socket options = IPTOS_LOWDELAY</B
16945 ></P
16946 ><P
16947 >If you have a local network then you could try:</P
16948 ><P
16949 ><B
16950 CLASS="COMMAND"
16951 >socket options = IPTOS_LOWDELAY TCP_NODELAY</B
16952 ></P
16953 ><P
16954 >If you are on a wide area network then perhaps try
16955                 setting IPTOS_THROUGHPUT. </P
16956 ><P
16957 >Note that several of the options may cause your Samba
16958                 server to fail completely. Use these options with caution!</P
16959 ><P
16960 >Default: <B
16961 CLASS="COMMAND"
16962 >socket options = TCP_NODELAY</B
16963 ></P
16964 ><P
16965 >Example: <B
16966 CLASS="COMMAND"
16967 >socket options = IPTOS_LOWDELAY</B
16968 ></P
16969 ></DD
16970 ><DT
16971 ><A
16972 NAME="SOURCEENVIRONMENT"
16973 ></A
16974 >source environment (G)</DT
16975 ><DD
16976 ><P
16977 >This parameter causes Samba to set environment
16978                 variables as per the content of the file named.</P
16979 ><P
16980 >If the value of this parameter starts with a "|" character
16981                 then Samba will treat that value as a pipe command to open and
16982                 will set the environment variables from the output of the pipe.</P
16983 ><P
16984 >The contents of the file or the output of the pipe should
16985                 be formatted as the output of the standard Unix <B
16986 CLASS="COMMAND"
16987 >env(1)
16988                 </B
16989 > command. This is of the form :</P
16990 ><P
16991 >Example environment entry:</P
16992 ><P
16993 ><B
16994 CLASS="COMMAND"
16995 >SAMBA_NETBIOS_NAME = myhostname</B
16996 ></P
16997 ><P
16998 >Default: <EM
16999 >No default value</EM
17000 ></P
17001 ><P
17002 >Examples: <B
17003 CLASS="COMMAND"
17004 >source environment = |/etc/smb.conf.sh
17005                 </B
17006 ></P
17007 ><P
17008 >Example: <B
17009 CLASS="COMMAND"
17010 >source environment =
17011                 /usr/local/smb_env_vars</B
17012 ></P
17013 ></DD
17014 ><DT
17015 ><A
17016 NAME="SSL"
17017 ></A
17018 >ssl (G)</DT
17019 ><DD
17020 ><P
17021 >This variable is part of SSL-enabled Samba. This
17022                 is only available if the SSL libraries have been compiled on your
17023                 system and the configure option <B
17024 CLASS="COMMAND"
17025 >--with-ssl</B
17026 > was
17027                 given at configure time.</P
17028 ><P
17029 >This variable enables or disables the entire SSL mode. If
17030                 it is set to <TT
17031 CLASS="CONSTANT"
17032 >no</TT
17033 >, the SSL-enabled Samba behaves
17034                 exactly like the non-SSL Samba. If set to <TT
17035 CLASS="CONSTANT"
17036 >yes</TT
17037 >,
17038                 it depends on the variables <A
17039 HREF="#SSLHOSTS"
17040 ><TT
17041 CLASS="PARAMETER"
17042 ><I
17043 >               ssl hosts</I
17044 ></TT
17045 ></A
17046 > and <A
17047 HREF="#SSLHOSTSRESIGN"
17048 >               <TT
17049 CLASS="PARAMETER"
17050 ><I
17051 >ssl hosts resign</I
17052 ></TT
17053 ></A
17054 > whether an SSL
17055                 connection will be required.</P
17056 ><P
17057 >Default: <B
17058 CLASS="COMMAND"
17059 >ssl = no</B
17060 ></P
17061 ></DD
17062 ><DT
17063 ><A
17064 NAME="SSLCACERTDIR"
17065 ></A
17066 >ssl CA certDir (G)</DT
17067 ><DD
17068 ><P
17069 >This variable is part of SSL-enabled Samba. This
17070                 is only available if the SSL libraries have been compiled on your
17071                 system and the configure option <B
17072 CLASS="COMMAND"
17073 >--with-ssl</B
17074 > was
17075                 given at configure time.</P
17076 ><P
17077 >This variable defines where to look up the Certification
17078                 Authorities. The given directory should contain one file for
17079                 each CA that Samba will trust.  The file name must be the hash
17080                 value over the "Distinguished Name" of the CA. How this directory
17081                 is set up is explained later in this document. All files within the
17082                 directory that don't fit into this naming scheme are ignored. You
17083                 don't need this variable if you don't verify client certificates.</P
17084 ><P
17085 >Default: <B
17086 CLASS="COMMAND"
17087 >ssl CA certDir = /usr/local/ssl/certs
17088                 </B
17089 ></P
17090 ></DD
17091 ><DT
17092 ><A
17093 NAME="SSLCACERTFILE"
17094 ></A
17095 >ssl CA certFile (G)</DT
17096 ><DD
17097 ><P
17098 >This variable is part of SSL-enabled Samba. This
17099                 is only available if the SSL libraries have been compiled on your
17100                 system and the configure option <B
17101 CLASS="COMMAND"
17102 >--with-ssl</B
17103 > was
17104                 given at configure time.</P
17105 ><P
17106 >This variable is a second way to define the trusted CAs.
17107                 The certificates of the trusted CAs are collected in one big
17108                 file and this variable points to the file. You will probably
17109                 only use one of the two ways to define your CAs. The first choice is
17110                 preferable if you have many CAs or want to be flexible, the second
17111                 is preferable if you only have one CA and want to keep things
17112                 simple (you won't need to create the hashed file names). You
17113                 don't need this variable if you don't verify client certificates.</P
17114 ><P
17115 >Default: <B
17116 CLASS="COMMAND"
17117 >ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem
17118                 </B
17119 ></P
17120 ></DD
17121 ><DT
17122 ><A
17123 NAME="SSLCIPHERS"
17124 ></A
17125 >ssl ciphers (G)</DT
17126 ><DD
17127 ><P
17128 >This variable is part of SSL-enabled Samba. This
17129                 is only available if the SSL libraries have been compiled on your
17130                 system and the configure option <B
17131 CLASS="COMMAND"
17132 >--with-ssl</B
17133 > was
17134                 given at configure time.</P
17135 ><P
17136 >This variable defines the ciphers that should be offered
17137                 during SSL negotiation. You should not set this variable unless
17138                 you know what you are doing.</P
17139 ></DD
17140 ><DT
17141 ><A
17142 NAME="SSLCLIENTCERT"
17143 ></A
17144 >ssl client cert (G)</DT
17145 ><DD
17146 ><P
17147 >This variable is part of SSL-enabled Samba. This
17148                 is only available if the SSL libraries have been compiled on your
17149                 system and the configure option <B
17150 CLASS="COMMAND"
17151 >--with-ssl</B
17152 > was
17153                 given at configure time.</P
17154 ><P
17155 >The certificate in this file is used by <A
17156 HREF="smbclient.1.html"
17157 TARGET="_top"
17158 >               <B
17159 CLASS="COMMAND"
17160 >smbclient(1)</B
17161 ></A
17162 > if it exists. It's needed
17163                 if the server requires a client certificate.</P
17164 ><P
17165 >Default: <B
17166 CLASS="COMMAND"
17167 >ssl client cert = /usr/local/ssl/certs/smbclient.pem
17168                 </B
17169 ></P
17170 ></DD
17171 ><DT
17172 ><A
17173 NAME="SSLCLIENTKEY"
17174 ></A
17175 >ssl client key (G)</DT
17176 ><DD
17177 ><P
17178 >This variable is part of SSL-enabled Samba. This
17179                 is only available if the SSL libraries have been compiled on your
17180                 system and the configure option <B
17181 CLASS="COMMAND"
17182 >--with-ssl</B
17183 > was
17184                 given at configure time.</P
17185 ><P
17186 >This is the private key for <A
17187 HREF="smbclient.1.html"
17188 TARGET="_top"
17189 >               <B
17190 CLASS="COMMAND"
17191 >smbclient(1)</B
17192 ></A
17193 >. It's only needed if the
17194                 client should have a certificate. </P
17195 ><P
17196 >Default: <B
17197 CLASS="COMMAND"
17198 >ssl client key = /usr/local/ssl/private/smbclient.pem
17199                 </B
17200 ></P
17201 ></DD
17202 ><DT
17203 ><A
17204 NAME="SSLCOMPATIBILITY"
17205 ></A
17206 >ssl compatibility (G)</DT
17207 ><DD
17208 ><P
17209 >This variable is part of SSL-enabled Samba. This
17210                 is only available if the SSL libraries have been compiled on your
17211                 system and the configure option <B
17212 CLASS="COMMAND"
17213 >--with-ssl</B
17214 > was
17215                 given at configure time.</P
17216 ><P
17217 >This variable defines whether OpenSSL should be configured
17218                 for bug compatibility with other SSL implementations. This is
17219                 probably not desirable because currently no clients with SSL
17220                 implementations other than OpenSSL exist.</P
17221 ><P
17222 >Default: <B
17223 CLASS="COMMAND"
17224 >ssl compatibility = no</B
17225 ></P
17226 ></DD
17227 ><DT
17228 ><A
17229 NAME="SSLEGDSOCKET"
17230 ></A
17231 >ssl egd socket (G)</DT
17232 ><DD
17233 ><P
17234 >This variable is part of SSL-enabled Samba. This
17235                 is only available if the SSL libraries have been compiled on your
17236                 system and the configure option <B
17237 CLASS="COMMAND"
17238 >--with-ssl</B
17239 > was
17240                 given at configure time.</P
17241 ><P
17242 >               This option is used to define the location of the communiation socket of
17243                 an EGD or PRNGD daemon, from which entropy can be retrieved. This option
17244                 can be used instead of or together with the <A
17245 HREF="#SSLENTROPYFILE"
17246 ><TT
17247 CLASS="PARAMETER"
17248 ><I
17249 >ssl entropy file</I
17250 ></TT
17251 ></A
17252 >
17253                 directive. 255 bytes of entropy will be retrieved from the daemon.
17254                 </P
17255 ><P
17256 >Default: <EM
17257 >none</EM
17258 ></P
17259 ></DD
17260 ><DT
17261 ><A
17262 NAME="SSLENTROPYBYTES"
17263 ></A
17264 >ssl entropy bytes (G)</DT
17265 ><DD
17266 ><P
17267 >This variable is part of SSL-enabled Samba. This
17268                 is only available if the SSL libraries have been compiled on your
17269                 system and the configure option <B
17270 CLASS="COMMAND"
17271 >--with-ssl</B
17272 > was
17273                 given at configure time.</P
17274 ><P
17275 >               This parameter is used to define the number of bytes which should
17276                 be read from the <A
17277 HREF="#SSLENTROPYFILE"
17278 ><TT
17279 CLASS="PARAMETER"
17280 ><I
17281 >ssl entropy
17282                 file</I
17283 ></TT
17284 ></A
17285 > If a -1 is specified, the entire file will
17286                 be read.
17287                 </P
17288 ><P
17289 >Default: <B
17290 CLASS="COMMAND"
17291 >ssl entropy bytes = 255</B
17292 ></P
17293 ></DD
17294 ><DT
17295 ><A
17296 NAME="SSLENTROPYFILE"
17297 ></A
17298 >ssl entropy file (G)</DT
17299 ><DD
17300 ><P
17301 >This variable is part of SSL-enabled Samba. This
17302                 is only available if the SSL libraries have been compiled on your
17303                 system and the configure option <B
17304 CLASS="COMMAND"
17305 >--with-ssl</B
17306 > was
17307                 given at configure time.</P
17308 ><P
17309 >               This parameter is used to specify a file from which processes will
17310                 read "random bytes" on startup.  In order to seed the internal pseudo
17311                 random number generator, entropy must be provided. On system with a
17312                 <TT
17313 CLASS="FILENAME"
17314 >/dev/urandom</TT
17315 > device file, the processes
17316                 will retrieve its entropy from the kernel. On systems without kernel
17317                 entropy support, a file can be supplied that will be read on startup
17318                 and that will be used to seed the PRNG.
17319                 </P
17320 ><P
17321 >Default: <EM
17322 >none</EM
17323 ></P
17324 ></DD
17325 ><DT
17326 ><A
17327 NAME="SSLHOSTS"
17328 ></A
17329 >ssl hosts (G)</DT
17330 ><DD
17331 ><P
17332 >See <A
17333 HREF="#SSLHOSTSRESIGN"
17334 ><TT
17335 CLASS="PARAMETER"
17336 ><I
17337 >               ssl hosts resign</I
17338 ></TT
17339 ></A
17340 >.</P
17341 ></DD
17342 ><DT
17343 ><A
17344 NAME="SSLHOSTSRESIGN"
17345 ></A
17346 >ssl hosts resign (G)</DT
17347 ><DD
17348 ><P
17349 >This variable is part of SSL-enabled Samba. This
17350                 is only available if the SSL libraries have been compiled on your
17351                 system and the configure option <B
17352 CLASS="COMMAND"
17353 >--with-ssl</B
17354 > was
17355                 given at configure time.</P
17356 ><P
17357 >These two variables define whether Samba will go
17358                 into SSL mode or not. If none of them is defined, Samba will
17359                 allow only SSL connections. If the <A
17360 HREF="#SSLHOSTS"
17361 >               <TT
17362 CLASS="PARAMETER"
17363 ><I
17364 >ssl hosts</I
17365 ></TT
17366 ></A
17367 > variable lists
17368                 hosts (by IP-address, IP-address range, net group or name),
17369                 only these hosts will be forced into SSL mode. If the <TT
17370 CLASS="PARAMETER"
17371 ><I
17372 >               ssl hosts resign</I
17373 ></TT
17374 > variable lists hosts, only these
17375                 hosts will <EM
17376 >NOT</EM
17377 > be forced into SSL mode. The syntax for these two
17378                 variables is the same as for the <A
17379 HREF="#HOSTSALLOW"
17380 ><TT
17381 CLASS="PARAMETER"
17382 ><I
17383 >               hosts allow</I
17384 ></TT
17385 ></A
17386 > and <A
17387 HREF="#HOSTSDENY"
17388 >               <TT
17389 CLASS="PARAMETER"
17390 ><I
17391 >hosts deny</I
17392 ></TT
17393 ></A
17394 > pair of variables, only
17395                 that the subject of the decision is different: It's not the access
17396                 right but whether SSL is used or not. </P
17397 ><P
17398 >The example below requires SSL connections from all hosts
17399                 outside the local net (which is 192.168.*.*).</P
17400 ><P
17401 >Default: <B
17402 CLASS="COMMAND"
17403 >ssl hosts = &#60;empty string&#62;</B
17404 ></P
17405 ><P
17406 ><B
17407 CLASS="COMMAND"
17408 >ssl hosts resign = &#60;empty string&#62;</B
17409 ></P
17410 ><P
17411 >Example: <B
17412 CLASS="COMMAND"
17413 >ssl hosts resign = 192.168.</B
17414 ></P
17415 ></DD
17416 ><DT
17417 ><A
17418 NAME="SSLREQUIRECLIENTCERT"
17419 ></A
17420 >ssl require clientcert (G)</DT
17421 ><DD
17422 ><P
17423 >This variable is part of SSL-enabled Samba. This
17424                 is only available if the SSL libraries have been compiled on your
17425                 system and the configure option <B
17426 CLASS="COMMAND"
17427 >--with-ssl</B
17428 > was
17429                 given at configure time.</P
17430 ><P
17431 >If this variable is set to <TT
17432 CLASS="CONSTANT"
17433 >yes</TT
17434 >, the
17435                 server will not tolerate connections from clients that don't
17436                 have a valid certificate. The directory/file given in <A
17437 HREF="#SSLCACERTDIR"
17438 ><TT
17439 CLASS="PARAMETER"
17440 ><I
17441 >ssl CA certDir</I
17442 ></TT
17443 >
17444                 </A
17445 > and <A
17446 HREF="#SSLCACERTFILE"
17447 ><TT
17448 CLASS="PARAMETER"
17449 ><I
17450 >ssl CA certFile
17451                 </I
17452 ></TT
17453 ></A
17454 > will be used to look up the CAs that issued
17455                 the client's certificate. If the certificate can't be verified
17456                 positively, the connection will be terminated.  If this variable
17457                 is set to <TT
17458 CLASS="CONSTANT"
17459 >no</TT
17460 >, clients don't need certificates.
17461                 Contrary to web applications you really <EM
17462 >should</EM
17463 >
17464                 require client certificates. In the web environment the client's
17465                 data is sensitive (credit card numbers) and the server must prove
17466                 to be trustworthy. In a file server environment the server's data
17467                 will be sensitive and the clients must prove to be trustworthy.</P
17468 ><P
17469 >Default: <B
17470 CLASS="COMMAND"
17471 >ssl require clientcert = no</B
17472 ></P
17473 ></DD
17474 ><DT
17475 ><A
17476 NAME="SSLREQUIRESERVERCERT"
17477 ></A
17478 >ssl require servercert (G)</DT
17479 ><DD
17480 ><P
17481 >This variable is part of SSL-enabled Samba. This
17482                 is only available if the SSL libraries have been compiled on your
17483                 system and the configure option <B
17484 CLASS="COMMAND"
17485 >--with-ssl</B
17486 > was
17487                 given at configure time.</P
17488 ><P
17489 >If this variable is set to <TT
17490 CLASS="CONSTANT"
17491 >yes</TT
17492 >, the
17493                 <A
17494 HREF="smbclient.1.html"
17495 TARGET="_top"
17496 ><B
17497 CLASS="COMMAND"
17498 >smbclient(1)</B
17499 >
17500                 </A
17501 > will request a certificate from the server. Same as
17502                 <A
17503 HREF="#SSLREQUIRECLIENTCERT"
17504 ><TT
17505 CLASS="PARAMETER"
17506 ><I
17507 >ssl require
17508                 clientcert</I
17509 ></TT
17510 ></A
17511 > for the server.</P
17512 ><P
17513 >Default: <B
17514 CLASS="COMMAND"
17515 >ssl require servercert = no</B
17516 >
17517                 </P
17518 ></DD
17519 ><DT
17520 ><A
17521 NAME="SSLSERVERCERT"
17522 ></A
17523 >ssl server cert (G)</DT
17524 ><DD
17525 ><P
17526 >This variable is part of SSL-enabled Samba. This
17527                 is only available if the SSL libraries have been compiled on your
17528                 system and the configure option <B
17529 CLASS="COMMAND"
17530 >--with-ssl</B
17531 > was
17532                 given at configure time.</P
17533 ><P
17534 >This is the file containing the server's certificate.
17535                 The server <EM
17536 >must</EM
17537 > have a certificate. The
17538                 file may also contain the server's private key. See later for
17539                 how certificates and private keys are created.</P
17540 ><P
17541 >Default: <B
17542 CLASS="COMMAND"
17543 >ssl server cert = &#60;empty string&#62;
17544                 </B
17545 ></P
17546 ></DD
17547 ><DT
17548 ><A
17549 NAME="SSLSERVERKEY"
17550 ></A
17551 >ssl server key (G)</DT
17552 ><DD
17553 ><P
17554 >This variable is part of SSL-enabled Samba. This
17555                 is only available if the SSL libraries have been compiled on your
17556                 system and the configure option <B
17557 CLASS="COMMAND"
17558 >--with-ssl</B
17559 > was
17560                 given at configure time.</P
17561 ><P
17562 >This file contains the private key of the server. If
17563                 this variable is not defined, the key is looked up in the
17564                 certificate file (it may be appended to the certificate).
17565                 The server <EM
17566 >must</EM
17567 > have a private key
17568                 and the certificate <EM
17569 >must</EM
17570 >
17571                 match this private key.</P
17572 ><P
17573 >Default: <B
17574 CLASS="COMMAND"
17575 >ssl server key = &#60;empty string&#62;
17576                 </B
17577 ></P
17578 ></DD
17579 ><DT
17580 ><A
17581 NAME="SSLVERSION"
17582 ></A
17583 >ssl version (G)</DT
17584 ><DD
17585 ><P
17586 >This variable is part of SSL-enabled Samba. This
17587                 is only available if the SSL libraries have been compiled on your
17588                 system and the configure option <B
17589 CLASS="COMMAND"
17590 >--with-ssl</B
17591 > was
17592                 given at configure time.</P
17593 ><P
17594 >This enumeration variable defines the versions of the
17595                 SSL protocol that will be used. <TT
17596 CLASS="CONSTANT"
17597 >ssl2or3</TT
17598 > allows
17599                 dynamic negotiation of SSL v2 or v3, <TT
17600 CLASS="CONSTANT"
17601 >ssl2</TT
17602 > results
17603                 in SSL v2, <TT
17604 CLASS="CONSTANT"
17605 >ssl3</TT
17606 > results in SSL v3 and
17607                 <TT
17608 CLASS="CONSTANT"
17609 >tls1</TT
17610 > results in TLS v1. TLS (Transport Layer
17611                 Security) is the new standard for SSL.</P
17612 ><P
17613 >Default: <B
17614 CLASS="COMMAND"
17615 >ssl version = "ssl2or3"</B
17616 ></P
17617 ></DD
17618 ><DT
17619 ><A
17620 NAME="STATCACHE"
17621 ></A
17622 >stat cache (G)</DT
17623 ><DD
17624 ><P
17625 >This parameter determines if <A
17626 HREF="smbd.8.html"
17627 TARGET="_top"
17628 >smbd(8)</A
17629 > will use a cache in order to
17630                 speed up case insensitive name mappings. You should never need
17631                 to change this parameter.</P
17632 ><P
17633 >Default: <B
17634 CLASS="COMMAND"
17635 >stat cache = yes</B
17636 ></P
17637 ></DD
17638 ><DT
17639 ><A
17640 NAME="STATCACHESIZE"
17641 ></A
17642 >stat cache size (G)</DT
17643 ><DD
17644 ><P
17645 >This parameter determines the number of
17646                 entries in the <TT
17647 CLASS="PARAMETER"
17648 ><I
17649 >stat cache</I
17650 ></TT
17651 >.  You should
17652                 never need to change this parameter.</P
17653 ><P
17654 >Default: <B
17655 CLASS="COMMAND"
17656 >stat cache size = 50</B
17657 ></P
17658 ></DD
17659 ><DT
17660 ><A
17661 NAME="STATUS"
17662 ></A
17663 >status (G)</DT
17664 ><DD
17665 ><P
17666 >This enables or disables logging of connections
17667                 to a status file that <A
17668 HREF="smbstatus.1.html"
17669 TARGET="_top"
17670 >smbstatus(1)</A
17671 >
17672                 can read.</P
17673 ><P
17674 >With this disabled <B
17675 CLASS="COMMAND"
17676 >smbstatus</B
17677 > won't be able
17678                 to tell you what connections are active. You should never need to
17679                 change this parameter.</P
17680 ><P
17681 >Default: <B
17682 CLASS="COMMAND"
17683 >status = yes</B
17684 ></P
17685 ></DD
17686 ><DT
17687 ><A
17688 NAME="STRICTALLOCATE"
17689 ></A
17690 >strict allocate (S)</DT
17691 ><DD
17692 ><P
17693 >This is a boolean that controls the handling of
17694                 disk space allocation in the server. When this is set to <TT
17695 CLASS="CONSTANT"
17696 >yes</TT
17697 >
17698                 the server will change from UNIX behaviour of not committing real
17699                 disk storage blocks when a file is extended to the Windows behaviour
17700                 of actually forcing the disk system to allocate real storage blocks
17701                 when a file is created or extended to be a given size. In UNIX
17702                 terminology this means that Samba will stop creating sparse files.
17703                 This can be slow on some systems.</P
17704 ><P
17705 >When strict allocate is <TT
17706 CLASS="CONSTANT"
17707 >no</TT
17708 > the server does sparse
17709                 disk block allocation when a file is extended.</P
17710 ><P
17711 >Setting this to <TT
17712 CLASS="CONSTANT"
17713 >yes</TT
17714 > can help Samba return
17715                 out of quota messages on systems that are restricting the disk quota
17716                 of users.</P
17717 ><P
17718 >Default: <B
17719 CLASS="COMMAND"
17720 >strict allocate = no</B
17721 ></P
17722 ></DD
17723 ><DT
17724 ><A
17725 NAME="STRICTLOCKING"
17726 ></A
17727 >strict locking (S)</DT
17728 ><DD
17729 ><P
17730 >This is a boolean that controls the handling of
17731                 file locking in the server. When this is set to <TT
17732 CLASS="CONSTANT"
17733 >yes</TT
17734 >
17735                 the server will check every read and write access for file locks, and
17736                 deny access if locks exist. This can be slow on some systems.</P
17737 ><P
17738 >When strict locking is <TT
17739 CLASS="CONSTANT"
17740 >no</TT
17741 > the server does file
17742                 lock checks only when the client explicitly asks for them.</P
17743 ><P
17744 >Well-behaved clients always ask for lock checks when it
17745                 is important, so in the vast majority of cases <B
17746 CLASS="COMMAND"
17747 >strict
17748                 locking = no</B
17749 > is preferable.</P
17750 ><P
17751 >Default: <B
17752 CLASS="COMMAND"
17753 >strict locking = no</B
17754 ></P
17755 ></DD
17756 ><DT
17757 ><A
17758 NAME="STRICTSYNC"
17759 ></A
17760 >strict sync (S)</DT
17761 ><DD
17762 ><P
17763 >Many Windows applications (including the Windows
17764                 98 explorer shell) seem to confuse flushing buffer contents to
17765                 disk with doing a sync to disk. Under UNIX, a sync call forces
17766                 the process to be suspended until the kernel has ensured that
17767                 all outstanding data in kernel disk buffers has been safely stored
17768                 onto stable storage. This is very slow and should only be done
17769                 rarely. Setting this parameter to <TT
17770 CLASS="CONSTANT"
17771 >no</TT
17772 > (the
17773                 default) means that <A
17774 HREF="smbd.8.html"
17775 TARGET="_top"
17776 >smbd</A
17777 > ignores the Windows applications requests for
17778                 a sync call. There is only a possibility of losing data if the
17779                 operating system itself that Samba is running on crashes, so there is
17780                 little danger in this default setting. In addition, this fixes many
17781                 performance problems that people have reported with the new Windows98
17782                 explorer shell file copies.</P
17783 ><P
17784 >See also the <A
17785 HREF="#SYNCALWAYS"
17786 ><TT
17787 CLASS="PARAMETER"
17788 ><I
17789 >sync
17790                 always&#62;</I
17791 ></TT
17792 ></A
17793 > parameter.</P
17794 ><P
17795 >Default: <B
17796 CLASS="COMMAND"
17797 >strict sync = no</B
17798 ></P
17799 ></DD
17800 ><DT
17801 ><A
17802 NAME="STRIPDOT"
17803 ></A
17804 >strip dot (G)</DT
17805 ><DD
17806 ><P
17807 >This parameter is now unused in Samba (2.2.5 and above).
17808                 It used strip trailing dots off UNIX filenames but was not correctly implmented.
17809                 In Samba 2.2.5 and above UNIX filenames ending in a dot are invalid Windows long
17810                 filenames (as they are in Windows NT and above) and are mangled to 8.3 before
17811                 being returned to a client.</P
17812 ><P
17813 >Default: <B
17814 CLASS="COMMAND"
17815 >strip dot = no</B
17816 ></P
17817 ></DD
17818 ><DT
17819 ><A
17820 NAME="SYNCALWAYS"
17821 ></A
17822 >sync always (S)</DT
17823 ><DD
17824 ><P
17825 >This is a boolean parameter that controls
17826                 whether writes will always be written to stable storage before
17827                 the write call returns. If this is <TT
17828 CLASS="CONSTANT"
17829 >no</TT
17830 > then the server will be
17831                 guided by the client's request in each write call (clients can
17832                 set a bit indicating that a particular write should be synchronous).
17833                 If this is <TT
17834 CLASS="CONSTANT"
17835 >yes</TT
17836 > then every write will be followed by a <B
17837 CLASS="COMMAND"
17838 >fsync()
17839                 </B
17840 > call to ensure the data is written to disk. Note that
17841                 the <TT
17842 CLASS="PARAMETER"
17843 ><I
17844 >strict sync</I
17845 ></TT
17846 > parameter must be set to
17847                 <TT
17848 CLASS="CONSTANT"
17849 >yes</TT
17850 > in order for this parameter to have
17851                 any affect.</P
17852 ><P
17853 >See also the <A
17854 HREF="#STRICTSYNC"
17855 ><TT
17856 CLASS="PARAMETER"
17857 ><I
17858 >strict
17859                 sync</I
17860 ></TT
17861 ></A
17862 > parameter.</P
17863 ><P
17864 >Default: <B
17865 CLASS="COMMAND"
17866 >sync always = no</B
17867 ></P
17868 ></DD
17869 ><DT
17870 ><A
17871 NAME="SYSLOG"
17872 ></A
17873 >syslog (G)</DT
17874 ><DD
17875 ><P
17876 >This parameter maps how Samba debug messages
17877                 are logged onto the system syslog logging levels. Samba debug
17878                 level zero maps onto syslog <TT
17879 CLASS="CONSTANT"
17880 >LOG_ERR</TT
17881 >, debug
17882                 level one maps onto <TT
17883 CLASS="CONSTANT"
17884 >LOG_WARNING</TT
17885 >, debug level
17886                 two maps onto <TT
17887 CLASS="CONSTANT"
17888 >LOG_NOTICE</TT
17889 >, debug level three
17890                 maps onto LOG_INFO. All higher levels are mapped to <TT
17891 CLASS="CONSTANT"
17892 >               LOG_DEBUG</TT
17893 >.</P
17894 ><P
17895 >This parameter sets the threshold for sending messages
17896                 to syslog.  Only messages with debug level less than this value
17897                 will be sent to syslog.</P
17898 ><P
17899 >Default: <B
17900 CLASS="COMMAND"
17901 >syslog = 1</B
17902 ></P
17903 ></DD
17904 ><DT
17905 ><A
17906 NAME="SYSLOGONLY"
17907 ></A
17908 >syslog only (G)</DT
17909 ><DD
17910 ><P
17911 >If this parameter is set then Samba debug
17912                 messages are logged into the system syslog only, and not to
17913                 the debug log files.</P
17914 ><P
17915 >Default: <B
17916 CLASS="COMMAND"
17917 >syslog only = no</B
17918 ></P
17919 ></DD
17920 ><DT
17921 ><A
17922 NAME="TEMPLATEHOMEDIR"
17923 ></A
17924 >template homedir (G)</DT
17925 ><DD
17926 ><P
17927 >When filling out the user information for a Windows NT
17928                 user, the <A
17929 HREF="winbindd.8.html"
17930 TARGET="_top"
17931 >winbindd(8)</A
17932 > daemon
17933                 uses this parameter to fill in the home directory for that user.
17934                 If the string <TT
17935 CLASS="PARAMETER"
17936 ><I
17937 >%D</I
17938 ></TT
17939 > is present it is substituted
17940                 with the user's Windows NT domain name.  If the string <TT
17941 CLASS="PARAMETER"
17942 ><I
17943 >%U
17944                 </I
17945 ></TT
17946 > is present it is substituted with the user's Windows
17947                 NT user name.</P
17948 ><P
17949 >Default: <B
17950 CLASS="COMMAND"
17951 >template homedir = /home/%D/%U</B
17952 ></P
17953 ></DD
17954 ><DT
17955 ><A
17956 NAME="TEMPLATESHELL"
17957 ></A
17958 >template shell (G)</DT
17959 ><DD
17960 ><P
17961 >When filling out the user information for a Windows NT
17962                 user, the <A
17963 HREF="winbindd.8.html"
17964 TARGET="_top"
17965 >winbindd(8)</A
17966 > daemon
17967                 uses this parameter to fill in the login shell for that user.</P
17968 ><P
17969 >Default: <B
17970 CLASS="COMMAND"
17971 >template shell = /bin/false</B
17972 ></P
17973 ></DD
17974 ><DT
17975 ><A
17976 NAME="TIMEOFFSET"
17977 ></A
17978 >time offset (G)</DT
17979 ><DD
17980 ><P
17981 >This parameter is a setting in minutes to add
17982                 to the normal GMT to local time conversion. This is useful if
17983                 you are serving a lot of PCs that have incorrect daylight
17984                 saving time handling.</P
17985 ><P
17986 >Default: <B
17987 CLASS="COMMAND"
17988 >time offset = 0</B
17989 ></P
17990 ><P
17991 >Example: <B
17992 CLASS="COMMAND"
17993 >time offset = 60</B
17994 ></P
17995 ></DD
17996 ><DT
17997 ><A
17998 NAME="TIMESERVER"
17999 ></A
18000 >time server (G)</DT
18001 ><DD
18002 ><P
18003 >This parameter determines if <A
18004 HREF="nmbd.8.html"
18005 TARGET="_top"
18006 >
18007                 nmbd(8)</A
18008 > advertises itself as a time server to Windows
18009                 clients.</P
18010 ><P
18011 >Default: <B
18012 CLASS="COMMAND"
18013 >time server = no</B
18014 ></P
18015 ></DD
18016 ><DT
18017 ><A
18018 NAME="TIMESTAMPLOGS"
18019 ></A
18020 >timestamp logs (G)</DT
18021 ><DD
18022 ><P
18023 >Synonym for <A
18024 HREF="#DEBUGTIMESTAMP"
18025 ><TT
18026 CLASS="PARAMETER"
18027 ><I
18028 >               debug timestamp</I
18029 ></TT
18030 ></A
18031 >.</P
18032 ></DD
18033 ><DT
18034 ><A
18035 NAME="TOTALPRINTJOBS"
18036 ></A
18037 >total print jobs (G)</DT
18038 ><DD
18039 ><P
18040 >This parameter accepts an integer value which defines
18041                 a limit on the maximum number of print jobs that will be accepted
18042                 system wide at any given time.  If a print job is submitted
18043                 by a client which will exceed this number, then <A
18044 HREF="smbd.8.html"
18045 TARGET="_top"
18046 >smbd</A
18047 > will return an
18048                 error indicating that no space is available on the server.  The
18049                 default value of 0 means that no such limit exists.  This parameter
18050                 can be used to prevent a server from exceeding its capacity and is
18051                 designed as a printing throttle.  See also
18052                 <A
18053 HREF="#MAXPRINTJOBS"
18054 ><TT
18055 CLASS="PARAMETER"
18056 ><I
18057 >max print jobs</I
18058 ></TT
18059 ></A
18060 >.
18061                 </P
18062 ><P
18063 >Default: <B
18064 CLASS="COMMAND"
18065 >total print jobs = 0</B
18066 ></P
18067 ><P
18068 >Example: <B
18069 CLASS="COMMAND"
18070 >total print jobs = 5000</B
18071 ></P
18072 ></DD
18073 ><DT
18074 ><A
18075 NAME="UNIXEXTENSIONS"
18076 ></A
18077 >unix extensions(G)</DT
18078 ><DD
18079 ><P
18080 >This boolean parameter controls whether Samba
18081                 implments the CIFS UNIX extensions, as defined by HP.
18082                 These extensions enable Samba to better serve UNIX CIFS clients
18083                 by supporting features such as symbolic links, hard links, etc...
18084                 These extensions require a similarly enabled client, and are of
18085                 no current use to Windows clients.</P
18086 ><P
18087 >Default: <B
18088 CLASS="COMMAND"
18089 >unix extensions = no</B
18090 ></P
18091 ></DD
18092 ><DT
18093 ><A
18094 NAME="UNIXPASSWORDSYNC"
18095 ></A
18096 >unix password sync (G)</DT
18097 ><DD
18098 ><P
18099 >This boolean parameter controls whether Samba
18100                 attempts to synchronize the UNIX password with the SMB password
18101                 when the encrypted SMB password in the smbpasswd file is changed.
18102                 If this is set to <TT
18103 CLASS="CONSTANT"
18104 >yes</TT
18105 > the program specified in the <TT
18106 CLASS="PARAMETER"
18107 ><I
18108 >passwd
18109                 program</I
18110 ></TT
18111 >parameter is called <EM
18112 >AS ROOT</EM
18113 > -
18114                 to allow the new UNIX password to be set without access to the
18115                 old UNIX password (as the SMB password change code has no
18116                 access to the old password cleartext, only the new).</P
18117 ><P
18118 >See also <A
18119 HREF="#PASSWDPROGRAM"
18120 ><TT
18121 CLASS="PARAMETER"
18122 ><I
18123 >passwd
18124                 program</I
18125 ></TT
18126 ></A
18127 >, <A
18128 HREF="#PASSWDCHAT"
18129 ><TT
18130 CLASS="PARAMETER"
18131 ><I
18132 >               passwd chat</I
18133 ></TT
18134 ></A
18135 >.</P
18136 ><P
18137 >Default: <B
18138 CLASS="COMMAND"
18139 >unix password sync = no</B
18140 ></P
18141 ></DD
18142 ><DT
18143 ><A
18144 NAME="UPDATEENCRYPTED"
18145 ></A
18146 >update encrypted (G)</DT
18147 ><DD
18148 ><P
18149 >This boolean parameter allows a user logging
18150                 on with a plaintext password to have their encrypted (hashed)
18151                 password in the smbpasswd file to be updated automatically as
18152                 they log on. This option allows a site to migrate from plaintext
18153                 password authentication (users authenticate with plaintext
18154                 password over the wire, and are checked against a UNIX account
18155                 database) to encrypted password authentication (the SMB
18156                 challenge/response authentication mechanism) without forcing
18157                 all users to re-enter their passwords via smbpasswd at the time the
18158                 change is made. This is a convenience option to allow the change over
18159                 to encrypted passwords to be made over a longer period. Once all users
18160                 have encrypted representations of their passwords in the smbpasswd
18161                 file this parameter should be set to <TT
18162 CLASS="CONSTANT"
18163 >no</TT
18164 >.</P
18165 ><P
18166 >In order for this parameter to work correctly the <A
18167 HREF="#ENCRYPTPASSWORDS"
18168 ><TT
18169 CLASS="PARAMETER"
18170 ><I
18171 >encrypt passwords</I
18172 ></TT
18173 >
18174                 </A
18175 > parameter must be set to <TT
18176 CLASS="CONSTANT"
18177 >no</TT
18178 > when
18179                 this parameter is set to <TT
18180 CLASS="CONSTANT"
18181 >yes</TT
18182 >.</P
18183 ><P
18184 >Note that even when this parameter is set a user
18185                 authenticating to <B
18186 CLASS="COMMAND"
18187 >smbd</B
18188 > must still enter a valid
18189                 password in order to connect correctly, and to update their hashed
18190                 (smbpasswd) passwords.</P
18191 ><P
18192 >Default: <B
18193 CLASS="COMMAND"
18194 >update encrypted = no</B
18195 ></P
18196 ></DD
18197 ><DT
18198 ><A
18199 NAME="USECLIENTDRIVER"
18200 ></A
18201 >use client driver (S)</DT
18202 ><DD
18203 ><P
18204 >This parameter applies only to Windows NT/2000
18205                 clients.  It has no affect on Windows 95/98/ME clients.  When
18206                 serving a printer to Windows NT/2000 clients without first installing
18207                 a valid printer driver on the Samba host, the client will be required
18208                 to install a local printer driver.  From this point on, the client
18209                 will treat the print as a local printer and not a network printer
18210                 connection.  This is much the same behavior that will occur
18211                 when <B
18212 CLASS="COMMAND"
18213 >disable spoolss = yes</B
18214 >.  </P
18215 ><P
18216 >The differentiating
18217                 factor is that under normal circumstances, the NT/2000 client will
18218                 attempt to open the network printer using MS-RPC.  The problem is that
18219                 because the client considers the printer to be local, it will attempt
18220                 to issue the OpenPrinterEx() call requesting access rights associated
18221                 with the logged on user. If the user possesses local administator rights
18222                 but not root privilegde on the Samba host (often the case), the OpenPrinterEx()
18223                 call will fail.  The result is that the client will now display an "Access
18224                 Denied; Unable to connect" message in the printer queue window (even though
18225                 jobs may successfully be printed).  </P
18226 ><P
18227 >If this parameter is enabled for a printer, then any attempt
18228                 to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
18229                 to PRINTER_ACCESS_USE instead.  Thus allowing the OpenPrinterEx()
18230                 call to succeed.  <EM
18231 >This parameter MUST not be able enabled
18232                 on a print share which has valid print driver installed on the Samba
18233                 server.</EM
18234 ></P
18235 ><P
18236 >See also <A
18237 HREF="#DISABLESPOOLSS"
18238 >disable spoolss</A
18239 >
18240                 </P
18241 ><P
18242 >Default: <B
18243 CLASS="COMMAND"
18244 >use client driver = no</B
18245 ></P
18246 ></DD
18247 ><DT
18248 ><A
18249 NAME="USEMMAP"
18250 ></A
18251 >use mmap (G)</DT
18252 ><DD
18253 ><P
18254 >This global parameter determines if the tdb internals of Samba can
18255                 depend on mmap working correctly on the running system. Samba requires a coherent
18256                 mmap/read-write system memory cache. Currently only HPUX does not have such a
18257                 coherent cache, and so this parameter is set to <TT
18258 CLASS="CONSTANT"
18259 >no</TT
18260 > by
18261                 default on HPUX. On all other systems this parameter should be left alone. This
18262                 parameter is provided to help the Samba developers track down problems with
18263                 the tdb internal code.
18264                 </P
18265 ><P
18266 >Default: <B
18267 CLASS="COMMAND"
18268 >use mmap = yes</B
18269 ></P
18270 ></DD
18271 ><DT
18272 ><A
18273 NAME="USERHOSTS"
18274 ></A
18275 >use rhosts (G)</DT
18276 ><DD
18277 ><P
18278 >If this global parameter is <TT
18279 CLASS="CONSTANT"
18280 >yes</TT
18281 >, it specifies
18282                 that the UNIX user's <TT
18283 CLASS="FILENAME"
18284 >.rhosts</TT
18285 > file in their home directory
18286                 will be read to find the names of hosts and users who will be allowed
18287                 access without specifying a password.</P
18288 ><P
18289 ><EM
18290 >NOTE:</EM
18291 > The use of <TT
18292 CLASS="PARAMETER"
18293 ><I
18294 >use rhosts
18295                 </I
18296 ></TT
18297 > can be a major security hole. This is because you are
18298                 trusting the PC to supply the correct username. It is very easy to
18299                 get a PC to supply a false username. I recommend that the <TT
18300 CLASS="PARAMETER"
18301 ><I
18302 >               use rhosts</I
18303 ></TT
18304 > option be only used if you really know what
18305                 you are doing.</P
18306 ><P
18307 >Default: <B
18308 CLASS="COMMAND"
18309 >use rhosts = no</B
18310 ></P
18311 ></DD
18312 ><DT
18313 ><A
18314 NAME="USER"
18315 ></A
18316 >user (S)</DT
18317 ><DD
18318 ><P
18319 >Synonym for <A
18320 HREF="#USERNAME"
18321 ><TT
18322 CLASS="PARAMETER"
18323 ><I
18324 >               username</I
18325 ></TT
18326 ></A
18327 >.</P
18328 ></DD
18329 ><DT
18330 ><A
18331 NAME="USERS"
18332 ></A
18333 >users (S)</DT
18334 ><DD
18335 ><P
18336 >Synonym for <A
18337 HREF="#USERNAME"
18338 ><TT
18339 CLASS="PARAMETER"
18340 ><I
18341 >               username</I
18342 ></TT
18343 ></A
18344 >.</P
18345 ></DD
18346 ><DT
18347 ><A
18348 NAME="USERNAME"
18349 ></A
18350 >username (S)</DT
18351 ><DD
18352 ><P
18353 >Multiple users may be specified in a comma-delimited
18354                 list, in which case the supplied password will be tested against
18355                 each username in turn (left to right).</P
18356 ><P
18357 >The <TT
18358 CLASS="PARAMETER"
18359 ><I
18360 >username</I
18361 ></TT
18362 > line is needed only when
18363                 the PC is unable to supply its own username. This is the case
18364                 for the COREPLUS protocol or where your users have different WfWg
18365                 usernames to UNIX usernames. In both these cases you may also be
18366                 better using the \\server\share%user syntax instead.</P
18367 ><P
18368 >The <TT
18369 CLASS="PARAMETER"
18370 ><I
18371 >username</I
18372 ></TT
18373 > line is not a great
18374                 solution in many cases as it means Samba will try to validate
18375                 the supplied password against each of the usernames in the
18376                 <TT
18377 CLASS="PARAMETER"
18378 ><I
18379 >username</I
18380 ></TT
18381 > line in turn. This is slow and
18382                 a bad idea for lots of users in case of duplicate passwords.
18383                 You may get timeouts or security breaches using this parameter
18384                 unwisely.</P
18385 ><P
18386 >Samba relies on the underlying UNIX security. This
18387                 parameter does not restrict who can login, it just offers hints
18388                 to the Samba server as to what usernames might correspond to the
18389                 supplied password. Users can login as whoever they please and
18390                 they will be able to do no more damage than if they started a
18391                 telnet session. The daemon runs as the user that they log in as,
18392                 so they cannot do anything that user cannot do.</P
18393 ><P
18394 >To restrict a service to a particular set of users you
18395                 can use the <A
18396 HREF="#VALIDUSERS"
18397 ><TT
18398 CLASS="PARAMETER"
18399 ><I
18400 >valid users
18401                 </I
18402 ></TT
18403 ></A
18404 > parameter.</P
18405 ><P
18406 >If any of the usernames begin with a '@' then the name
18407                 will be looked up first in the NIS netgroups list (if Samba
18408                 is compiled with netgroup support), followed by a lookup in
18409                 the UNIX groups database and will expand to a list of all users
18410                 in the group of that name.</P
18411 ><P
18412 >If any of the usernames begin with a '+' then the name
18413                 will be looked up only in the UNIX groups database and will
18414                 expand to a list of all users in the group of that name.</P
18415 ><P
18416 >If any of the usernames begin with a '&#38;'then the name
18417                 will be looked up only in the NIS netgroups database (if Samba
18418                 is compiled with netgroup support) and will expand to a list
18419                 of all users in the netgroup group of that name.</P
18420 ><P
18421 >Note that searching though a groups database can take
18422                 quite some time, and some clients may time out during the
18423                 search.</P
18424 ><P
18425 >See the section <A
18426 HREF="#AEN241"
18427 >NOTE ABOUT
18428                 USERNAME/PASSWORD VALIDATION</A
18429 > for more information on how
18430                 this parameter determines access to the services.</P
18431 ><P
18432 >Default: <B
18433 CLASS="COMMAND"
18434 >The guest account if a guest service,
18435                 else &#60;empty string&#62;.</B
18436 ></P
18437 ><P
18438 >Examples:<B
18439 CLASS="COMMAND"
18440 >username = fred, mary, jack, jane,
18441                 @users, @pcgroup</B
18442 ></P
18443 ></DD
18444 ><DT
18445 ><A
18446 NAME="USERNAMELEVEL"
18447 ></A
18448 >username level (G)</DT
18449 ><DD
18450 ><P
18451 >This option helps Samba to try and 'guess' at
18452                 the real UNIX username, as many DOS clients send an all-uppercase
18453                 username. By default Samba tries all lowercase, followed by the
18454                 username with the first letter capitalized, and fails if the
18455                 username is not found on the UNIX machine.</P
18456 ><P
18457 >If this parameter is set to non-zero the behavior changes.
18458                 This parameter is a number that specifies the number of uppercase
18459                 combinations to try while trying to determine the UNIX user name. The
18460                 higher the number the more combinations will be tried, but the slower
18461                 the discovery of usernames will be. Use this parameter when you have
18462                 strange usernames on your UNIX machine, such as <TT
18463 CLASS="CONSTANT"
18464 >AstrangeUser
18465                 </TT
18466 >.</P
18467 ><P
18468 >Default: <B
18469 CLASS="COMMAND"
18470 >username level = 0</B
18471 ></P
18472 ><P
18473 >Example: <B
18474 CLASS="COMMAND"
18475 >username level = 5</B
18476 ></P
18477 ></DD
18478 ><DT
18479 ><A
18480 NAME="USERNAMEMAP"
18481 ></A
18482 >username map (G)</DT
18483 ><DD
18484 ><P
18485 >This option allows you to specify a file containing
18486                 a mapping of usernames from the clients to the server. This can be
18487                 used for several purposes. The most common is to map usernames
18488                 that users use on DOS or Windows machines to those that the UNIX
18489                 box uses. The other is to map multiple users to a single username
18490                 so that they can more easily share files.</P
18491 ><P
18492 >The map file is parsed line by line. Each line should
18493                 contain a single UNIX username on the left then a '=' followed
18494                 by a list of usernames on the right. The list of usernames on the
18495                 right may contain names of the form @group in which case they
18496                 will match any UNIX username in that group. The special client
18497                 name '*' is a wildcard and matches any name. Each line of the
18498                 map file may be up to 1023 characters long.</P
18499 ><P
18500 >The file is processed on each line by taking the
18501                 supplied username and comparing it with each username on the right
18502                 hand side of the '=' signs. If the supplied name matches any of
18503                 the names on the right hand side then it is replaced with the name
18504                 on the left. Processing then continues with the next line.</P
18505 ><P
18506 >If any line begins with a '#' or a ';' then it is
18507                 ignored</P
18508 ><P
18509 >If any line begins with an '!' then the processing
18510                 will stop after that line if a mapping was done by the line.
18511                 Otherwise mapping continues with every line being processed.
18512                 Using '!' is most useful when you have a wildcard mapping line
18513                 later in the file.</P
18514 ><P
18515 >For example to map from the name <TT
18516 CLASS="CONSTANT"
18517 >admin</TT
18518 >
18519                 or <TT
18520 CLASS="CONSTANT"
18521 >administrator</TT
18522 > to the UNIX name <TT
18523 CLASS="CONSTANT"
18524 >               root</TT
18525 > you would use:</P
18526 ><P
18527 ><B
18528 CLASS="COMMAND"
18529 >root = admin administrator</B
18530 ></P
18531 ><P
18532 >Or to map anyone in the UNIX group <TT
18533 CLASS="CONSTANT"
18534 >system</TT
18535 >
18536                 to the UNIX name <TT
18537 CLASS="CONSTANT"
18538 >sys</TT
18539 > you would use:</P
18540 ><P
18541 ><B
18542 CLASS="COMMAND"
18543 >sys = @system</B
18544 ></P
18545 ><P
18546 >You can have as many mappings as you like in a username
18547                 map file.</P
18548 ><P
18549 >If your system supports the NIS NETGROUP option then
18550                 the netgroup database is checked before the <TT
18551 CLASS="FILENAME"
18552 >/etc/group
18553                 </TT
18554 > database for matching groups.</P
18555 ><P
18556 >You can map Windows usernames that have spaces in them
18557                  by using double quotes around the name. For example:</P
18558 ><P
18559 ><B
18560 CLASS="COMMAND"
18561 >tridge = "Andrew Tridgell"</B
18562 ></P
18563 ><P
18564 >would map the windows username "Andrew Tridgell" to the
18565                 unix username "tridge".</P
18566 ><P
18567 >The following example would map mary and fred to the
18568                 unix user sys, and map the rest to guest. Note the use of the
18569                 '!' to tell Samba to stop processing if it gets a match on
18570                 that line.</P
18571 ><P
18572 ><TABLE
18573 BORDER="0"
18574 BGCOLOR="#E0E0E0"
18575 WIDTH="90%"
18576 ><TR
18577 ><TD
18578 ><PRE
18579 CLASS="PROGRAMLISTING"
18580 >               !sys = mary fred
18581                 guest = *
18582                 </PRE
18583 ></TD
18584 ></TR
18585 ></TABLE
18586 ></P
18587 ><P
18588 >Note that the remapping is applied to all occurrences
18589                 of usernames. Thus if you connect to \\server\fred and <TT
18590 CLASS="CONSTANT"
18591 >               fred</TT
18592 > is remapped to <TT
18593 CLASS="CONSTANT"
18594 >mary</TT
18595 > then you
18596                 will actually be connecting to \\server\mary and will need to
18597                 supply a password suitable for <TT
18598 CLASS="CONSTANT"
18599 >mary</TT
18600 > not
18601                 <TT
18602 CLASS="CONSTANT"
18603 >fred</TT
18604 >. The only exception to this is the
18605                 username passed to the <A
18606 HREF="#PASSWORDSERVER"
18607 ><TT
18608 CLASS="PARAMETER"
18609 ><I
18610 >               password server</I
18611 ></TT
18612 ></A
18613 > (if you have one). The password
18614                 server will receive whatever username the client supplies without
18615                 modification.</P
18616 ><P
18617 >Also note that no reverse mapping is done. The main effect
18618                 this has is with printing. Users who have been mapped may have
18619                 trouble deleting print jobs as PrintManager under WfWg will think
18620                 they don't own the print job.</P
18621 ><P
18622 >Default: <EM
18623 >no username map</EM
18624 ></P
18625 ><P
18626 >Example: <B
18627 CLASS="COMMAND"
18628 >username map = /usr/local/samba/lib/users.map
18629                 </B
18630 ></P
18631 ></DD
18632 ><DT
18633 ><A
18634 NAME="USESENDFILE"
18635 ></A
18636 >use sendfile (S)</DT
18637 ><DD
18638 ><P
18639 >If this parameter is <TT
18640 CLASS="CONSTANT"
18641 >yes</TT
18642 >, and Samba
18643                 was built with the --with-sendfile-support option, and the underlying operating
18644                 system supports sendfile system call, then some SMB read calls (mainly ReadAndX
18645                 and ReadRaw) will use the more efficient sendfile system call for files that
18646                 are exclusively oplocked. This may make more efficient use of the system CPU's
18647                 and cause Samba to be faster. This is off by default as it's effects are unknown
18648                 as yet.
18649                 </P
18650 ><P
18651 >Default: <B
18652 CLASS="COMMAND"
18653 >use sendfile = no</B
18654 ></P
18655 ></DD
18656 ><DT
18657 ><A
18658 NAME="UTMP"
18659 ></A
18660 >utmp (G)</DT
18661 ><DD
18662 ><P
18663 >This boolean parameter is only available if
18664                 Samba has been configured and compiled  with the option <B
18665 CLASS="COMMAND"
18666 >               --with-utmp</B
18667 >. If set to <TT
18668 CLASS="CONSTANT"
18669 >yes</TT
18670 > then Samba will attempt
18671                 to add utmp or utmpx records (depending on the UNIX system) whenever a
18672                 connection is made to a Samba server. Sites may use this to record the
18673                 user connecting to a Samba share.</P
18674 ><P
18675 >See also the <A
18676 HREF="#UTMPDIRECTORY"
18677 ><TT
18678 CLASS="PARAMETER"
18679 ><I
18680 >               utmp directory</I
18681 ></TT
18682 ></A
18683 > parameter.</P
18684 ><P
18685 >Default: <B
18686 CLASS="COMMAND"
18687 >utmp = no</B
18688 ></P
18689 ></DD
18690 ><DT
18691 ><A
18692 NAME="UTMPDIRECTORY"
18693 ></A
18694 >utmp directory(G)</DT
18695 ><DD
18696 ><P
18697 >This parameter is only available if Samba has
18698                 been configured and compiled with the option <B
18699 CLASS="COMMAND"
18700 >               --with-utmp</B
18701 >. It specifies a directory pathname that is
18702                 used to store the utmp or utmpx files (depending on the UNIX system) that
18703                 record user connections to a Samba server. See also the <A
18704 HREF="#UTMP"
18705 >               <TT
18706 CLASS="PARAMETER"
18707 ><I
18708 >utmp</I
18709 ></TT
18710 ></A
18711 > parameter. By default this is
18712                 not set, meaning the system will use whatever utmp file the
18713                 native system is set to use (usually
18714                 <TT
18715 CLASS="FILENAME"
18716 >/var/run/utmp</TT
18717 > on Linux).</P
18718 ><P
18719 >Default: <EM
18720 >no utmp directory</EM
18721 ></P
18722 ></DD
18723 ><DT
18724 ><A
18725 NAME="VALIDCHARS"
18726 ></A
18727 >valid chars (G)</DT
18728 ><DD
18729 ><P
18730 >The option allows you to specify additional
18731                 characters that should be considered valid by the server in
18732                 filenames. This is particularly useful for national character
18733                 sets, such as adding u-umlaut or a-ring.</P
18734 ><P
18735 >The option takes a list of characters in either integer
18736                 or character form with spaces between them. If you give two
18737                 characters with a colon between them then it will be taken as
18738                 an lowercase:uppercase pair.</P
18739 ><P
18740 >If you have an editor capable of entering the characters
18741                 into the config file then it is probably easiest to use this
18742                 method. Otherwise you can specify the characters in octal,
18743                 decimal or hexadecimal form using the usual C notation.</P
18744 ><P
18745 >For example to add the single character 'Z' to the charset
18746                 (which is a pointless thing to do as it's already there) you could
18747                 do one of the following</P
18748 ><P
18749 ><TABLE
18750 BORDER="0"
18751 BGCOLOR="#E0E0E0"
18752 WIDTH="90%"
18753 ><TR
18754 ><TD
18755 ><PRE
18756 CLASS="PROGRAMLISTING"
18757 >               valid chars = Z
18758                 valid chars = z:Z
18759                 valid chars = 0132:0172
18760                 </PRE
18761 ></TD
18762 ></TR
18763 ></TABLE
18764 ></P
18765 ><P
18766 >The last two examples above actually add two characters,
18767                 and alter the uppercase and lowercase mappings appropriately.</P
18768 ><P
18769 >Note that you <EM
18770 >MUST</EM
18771 > specify this parameter
18772                 after the <TT
18773 CLASS="PARAMETER"
18774 ><I
18775 >client code page</I
18776 ></TT
18777 > parameter if you
18778                 have both set. If <TT
18779 CLASS="PARAMETER"
18780 ><I
18781 >client code page</I
18782 ></TT
18783 > is set after
18784                 the <TT
18785 CLASS="PARAMETER"
18786 ><I
18787 >valid chars</I
18788 ></TT
18789 > parameter the <TT
18790 CLASS="PARAMETER"
18791 ><I
18792 >valid
18793                 chars</I
18794 ></TT
18795 > settings will be overwritten.</P
18796 ><P
18797 >See also the <A
18798 HREF="#CLIENTCODEPAGE"
18799 ><TT
18800 CLASS="PARAMETER"
18801 ><I
18802 >client
18803                 code page</I
18804 ></TT
18805 ></A
18806 > parameter.</P
18807 ><P
18808 >Default: <EM
18809 >Samba defaults to using a reasonable set
18810                 of valid characters for English systems</EM
18811 ></P
18812 ><P
18813 >Example: <B
18814 CLASS="COMMAND"
18815 >valid chars = 0345:0305 0366:0326 0344:0304
18816                 </B
18817 ></P
18818 ><P
18819 >The above example allows filenames to have the Swedish
18820                 characters in them.</P
18821 ><P
18822 ><EM
18823 >NOTE:</EM
18824 > It is actually quite difficult to
18825                 correctly produce a <TT
18826 CLASS="PARAMETER"
18827 ><I
18828 >valid chars</I
18829 ></TT
18830 > line for
18831                 a particular system. To automate the process <A
18832 HREF="mailto:tino@augsburg.net"
18833 TARGET="_top"
18834 >tino@augsburg.net</A
18835 > has written
18836                 a package called <B
18837 CLASS="COMMAND"
18838 >validchars</B
18839 > which will automatically
18840                 produce a complete <TT
18841 CLASS="PARAMETER"
18842 ><I
18843 >valid chars</I
18844 ></TT
18845 > line for
18846                 a given client system. Look in the <TT
18847 CLASS="FILENAME"
18848 >examples/validchars/
18849                 </TT
18850 > subdirectory of your Samba source code distribution
18851                 for this package.</P
18852 ></DD
18853 ><DT
18854 ><A
18855 NAME="VALIDUSERS"
18856 ></A
18857 >valid users (S)</DT
18858 ><DD
18859 ><P
18860 >This is a list of users that should be allowed
18861                 to login to this service. Names starting with '@', '+' and  '&#38;'
18862                 are interpreted using the same rules as described in the
18863                 <TT
18864 CLASS="PARAMETER"
18865 ><I
18866 >invalid users</I
18867 ></TT
18868 > parameter.</P
18869 ><P
18870 >If this is empty (the default) then any user can login.
18871                 If a username is in both this list and the <TT
18872 CLASS="PARAMETER"
18873 ><I
18874 >invalid
18875                 users</I
18876 ></TT
18877 > list then access is denied for that user.</P
18878 ><P
18879 >The current servicename is substituted for <TT
18880 CLASS="PARAMETER"
18881 ><I
18882 >%S
18883                 </I
18884 ></TT
18885 >. This is useful in the [homes] section.</P
18886 ><P
18887 >See also <A
18888 HREF="#INVALIDUSERS"
18889 ><TT
18890 CLASS="PARAMETER"
18891 ><I
18892 >invalid users
18893                 </I
18894 ></TT
18895 ></A
18896 ></P
18897 ><P
18898 >Default: <EM
18899 >No valid users list (anyone can login)
18900                 </EM
18901 ></P
18902 ><P
18903 >Example: <B
18904 CLASS="COMMAND"
18905 >valid users = greg, @pcusers</B
18906 ></P
18907 ></DD
18908 ><DT
18909 ><A
18910 NAME="VETOFILES"
18911 ></A
18912 >veto files(S)</DT
18913 ><DD
18914 ><P
18915 >This is a list of files and directories that
18916                 are neither visible nor accessible.  Each entry in the list must
18917                 be separated by a '/', which allows spaces to be included
18918                 in the entry. '*' and '?' can be used to specify multiple files
18919                 or directories as in DOS wildcards.</P
18920 ><P
18921 >Each entry must be a unix path, not a DOS path and
18922                 must <EM
18923 >not</EM
18924 > include the  unix directory
18925                 separator '/'.</P
18926 ><P
18927 >Note that the <TT
18928 CLASS="PARAMETER"
18929 ><I
18930 >case sensitive</I
18931 ></TT
18932 > option
18933                 is applicable in vetoing files.</P
18934 ><P
18935 >One feature of the veto files parameter that it
18936                 is important to be aware of is Samba's behaviour when
18937                 trying to delete a directory. If a directory that is
18938                 to be deleted contains nothing but veto files this
18939                 deletion will <EM
18940 >fail</EM
18941 > unless you also set
18942                 the <TT
18943 CLASS="PARAMETER"
18944 ><I
18945 >delete veto files</I
18946 ></TT
18947 > parameter to
18948                 <TT
18949 CLASS="PARAMETER"
18950 ><I
18951 >yes</I
18952 ></TT
18953 >.</P
18954 ><P
18955 >Setting this parameter will affect the performance
18956                 of Samba, as it will be forced to check all files and directories
18957                 for a match as they are scanned.</P
18958 ><P
18959 >See also <A
18960 HREF="#HIDEFILES"
18961 ><TT
18962 CLASS="PARAMETER"
18963 ><I
18964 >hide files
18965                 </I
18966 ></TT
18967 ></A
18968 > and <A
18969 HREF="#CASESENSITIVE"
18970 ><TT
18971 CLASS="PARAMETER"
18972 ><I
18973 >               case sensitive</I
18974 ></TT
18975 ></A
18976 >.</P
18977 ><P
18978 >Default: <EM
18979 >No files or directories are vetoed.
18980                 </EM
18981 ></P
18982 ><P
18983 >Examples:<TABLE
18984 BORDER="0"
18985 BGCOLOR="#E0E0E0"
18986 WIDTH="90%"
18987 ><TR
18988 ><TD
18989 ><PRE
18990 CLASS="PROGRAMLISTING"
18991 >; Veto any files containing the word Security,
18992 ; any ending in .tmp, and any directory containing the
18993 ; word root.
18994 veto files = /*Security*/*.tmp/*root*/
18995
18996 ; Veto the Apple specific files that a NetAtalk server
18997 ; creates.
18998 veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/</PRE
18999 ></TD
19000 ></TR
19001 ></TABLE
19002 ></P
19003 ></DD
19004 ><DT
19005 ><A
19006 NAME="VETOOPLOCKFILES"
19007 ></A
19008 >veto oplock files (S)</DT
19009 ><DD
19010 ><P
19011 >This parameter is only valid when the <A
19012 HREF="#OPLOCKS"
19013 ><TT
19014 CLASS="PARAMETER"
19015 ><I
19016 >oplocks</I
19017 ></TT
19018 ></A
19019 >
19020                 parameter is turned on for a share. It allows the Samba administrator
19021                 to selectively turn off the granting of oplocks on selected files that
19022                 match a wildcarded list, similar to the wildcarded list used in the
19023                 <A
19024 HREF="#VETOFILES"
19025 ><TT
19026 CLASS="PARAMETER"
19027 ><I
19028 >veto files</I
19029 ></TT
19030 ></A
19031 >
19032                 parameter.</P
19033 ><P
19034 >Default: <EM
19035 >No files are vetoed for oplock
19036                 grants</EM
19037 ></P
19038 ><P
19039 >You might want to do this on files that you know will
19040                 be heavily contended for by clients. A good example of this
19041                 is in the NetBench SMB benchmark program, which causes heavy
19042                 client contention for files ending in <TT
19043 CLASS="FILENAME"
19044 >.SEM</TT
19045 >.
19046                 To cause Samba not to grant oplocks on these files you would use
19047                 the line (either in the [global] section or in the section for
19048                 the particular NetBench share :</P
19049 ><P
19050 >Example: <B
19051 CLASS="COMMAND"
19052 >veto oplock files = /*.SEM/
19053                 </B
19054 ></P
19055 ></DD
19056 ><DT
19057 ><A
19058 NAME="VFSOBJECT"
19059 ></A
19060 >vfs object (S)</DT
19061 ><DD
19062 ><P
19063 >This parameter specifies a shared object file that
19064                 is used for Samba VFS I/O operations.  By default, normal
19065                 disk I/O operations are used but these can be overloaded
19066                 with a VFS object.  The Samba VFS layer is new to Samba 2.2 and
19067                 must be enabled at compile time with --with-vfs.</P
19068 ><P
19069 >Default : <EM
19070 >no value</EM
19071 ></P
19072 ></DD
19073 ><DT
19074 ><A
19075 NAME="VFSOPTIONS"
19076 ></A
19077 >vfs options (S)</DT
19078 ><DD
19079 ><P
19080 >This parameter allows parameters to be passed
19081                 to the vfs layer at initialization time.  The Samba VFS layer
19082                 is new to Samba 2.2 and must be enabled at compile time
19083                 with --with-vfs.  See also <A
19084 HREF="#VFSOBJECT"
19085 ><TT
19086 CLASS="PARAMETER"
19087 ><I
19088 >               vfs object</I
19089 ></TT
19090 ></A
19091 >.</P
19092 ><P
19093 >Default : <EM
19094 >no value</EM
19095 ></P
19096 ></DD
19097 ><DT
19098 ><A
19099 NAME="VOLUME"
19100 ></A
19101 >volume (S)</DT
19102 ><DD
19103 ><P
19104 > This allows you to override the volume label
19105                 returned for a share. Useful for CDROMs with installation programs
19106                 that insist on a particular volume label.</P
19107 ><P
19108 >Default: <EM
19109 >the name of the share</EM
19110 ></P
19111 ></DD
19112 ><DT
19113 ><A
19114 NAME="WIDELINKS"
19115 ></A
19116 >wide links (S)</DT
19117 ><DD
19118 ><P
19119 >This parameter controls whether or not links
19120                 in the UNIX file system may be followed by the server. Links
19121                 that point to areas within the directory tree exported by the
19122                 server are always allowed; this parameter controls access only
19123                 to areas that are outside the directory tree being exported.</P
19124 ><P
19125 >Note that setting this parameter can have a negative
19126                 effect on your server performance due to the extra system calls
19127                 that Samba has to  do in order to perform the link checks.</P
19128 ><P
19129 >Default: <B
19130 CLASS="COMMAND"
19131 >wide links = yes</B
19132 ></P
19133 ></DD
19134 ><DT
19135 ><A
19136 NAME="WINBINDCACHETIME"
19137 ></A
19138 >winbind cache time (G)</DT
19139 ><DD
19140 ><P
19141 >This parameter specifies the number of seconds the
19142                 <A
19143 HREF="winbindd.8.html"
19144 TARGET="_top"
19145 >winbindd(8)</A
19146 > daemon will cache
19147                 user and group information before querying a Windows NT server
19148                 again.</P
19149 ><P
19150 >Default: <B
19151 CLASS="COMMAND"
19152 >winbind cache type = 15</B
19153 ></P
19154 ></DD
19155 ><DT
19156 ><A
19157 NAME="WINBINDENUMUSERS"
19158 ></A
19159 >winbind enum users (G)</DT
19160 ><DD
19161 ><P
19162 >On large installations using
19163                 <A
19164 HREF="winbindd.8.html"
19165 TARGET="_top"
19166 >winbindd(8)</A
19167 > it may be
19168                 necessary to suppress the enumeration of users through the
19169                 <B
19170 CLASS="COMMAND"
19171 > setpwent()</B
19172 >,
19173                 <B
19174 CLASS="COMMAND"
19175 >getpwent()</B
19176 > and
19177                 <B
19178 CLASS="COMMAND"
19179 >endpwent()</B
19180 > group of system calls.  If
19181                 the <TT
19182 CLASS="PARAMETER"
19183 ><I
19184 >winbind enum users</I
19185 ></TT
19186 > parameter is
19187                 <TT
19188 CLASS="CONSTANT"
19189 >no</TT
19190 >, calls to the <B
19191 CLASS="COMMAND"
19192 >getpwent</B
19193 > system call
19194                 will not return any data. </P
19195 ><P
19196 ><EM
19197 >Warning:</EM
19198 > Turning off user
19199                 enumeration may cause some programs to behave oddly.  For
19200                 example, the finger program relies on having access to the
19201                 full user list when searching for matching
19202                 usernames. </P
19203 ><P
19204 >Default: <B
19205 CLASS="COMMAND"
19206 >winbind enum users = yes </B
19207 ></P
19208 ></DD
19209 ><DT
19210 ><A
19211 NAME="WINBINDENUMGROUPS"
19212 ></A
19213 >winbind enum groups (G)</DT
19214 ><DD
19215 ><P
19216 >On large installations using
19217                 <A
19218 HREF="winbindd.8.html"
19219 TARGET="_top"
19220 >winbindd(8)</A
19221 > it may be
19222                 necessary to suppress the enumeration of groups through the
19223                 <B
19224 CLASS="COMMAND"
19225 > setgrent()</B
19226 >,
19227                 <B
19228 CLASS="COMMAND"
19229 >getgrent()</B
19230 > and
19231                 <B
19232 CLASS="COMMAND"
19233 >endgrent()</B
19234 > group of system calls.  If
19235                 the <TT
19236 CLASS="PARAMETER"
19237 ><I
19238 >winbind enum groups</I
19239 ></TT
19240 > parameter is
19241                 <TT
19242 CLASS="CONSTANT"
19243 >no</TT
19244 >, calls to the <B
19245 CLASS="COMMAND"
19246 >getgrent()</B
19247 > system
19248                 call will not return any data. </P
19249 ><P
19250 ><EM
19251 >Warning:</EM
19252 > Turning off group
19253                 enumeration may cause some programs to behave oddly.
19254                 </P
19255 ><P
19256 >Default: <B
19257 CLASS="COMMAND"
19258 >winbind enum groups = yes </B
19259 >
19260                 </P
19261 ></DD
19262 ><DT
19263 ><A
19264 NAME="WINBINDGID"
19265 ></A
19266 >winbind gid (G)</DT
19267 ><DD
19268 ><P
19269 >The winbind gid parameter specifies the range of group
19270                 ids that are allocated by the <A
19271 HREF="winbindd.8.html"
19272 TARGET="_top"
19273 >               winbindd(8)</A
19274 > daemon.  This range of group ids should have no
19275                 existing local or NIS groups within it as strange conflicts can
19276                 occur otherwise.</P
19277 ><P
19278 >Default: <B
19279 CLASS="COMMAND"
19280 >winbind gid = &#60;empty string&#62;
19281                 </B
19282 ></P
19283 ><P
19284 >Example: <B
19285 CLASS="COMMAND"
19286 >winbind gid = 10000-20000</B
19287 ></P
19288 ></DD
19289 ><DT
19290 ><A
19291 NAME="WINBINDSEPARATOR"
19292 ></A
19293 >winbind separator (G)</DT
19294 ><DD
19295 ><P
19296 >This parameter allows an admin to define the character
19297                 used when listing a username of the form of <TT
19298 CLASS="REPLACEABLE"
19299 ><I
19300 >DOMAIN
19301                 </I
19302 ></TT
19303 >\<TT
19304 CLASS="REPLACEABLE"
19305 ><I
19306 >user</I
19307 ></TT
19308 >.  This parameter
19309                 is only applicable when using the <TT
19310 CLASS="FILENAME"
19311 >pam_winbind.so</TT
19312 >
19313                 and <TT
19314 CLASS="FILENAME"
19315 >nss_winbind.so</TT
19316 > modules for UNIX services.
19317                 </P
19318 ><P
19319 >Please note that setting this parameter to + causes problems
19320                 with group membership at least on glibc systems, as the character +
19321                 is used as a special character for NIS in /etc/group.</P
19322 ><P
19323 >Default: <B
19324 CLASS="COMMAND"
19325 >winbind separator = '\'</B
19326 ></P
19327 ><P
19328 >Example: <B
19329 CLASS="COMMAND"
19330 >winbind separator = +</B
19331 ></P
19332 ></DD
19333 ><DT
19334 ><A
19335 NAME="WINBINDUID"
19336 ></A
19337 >winbind uid (G)</DT
19338 ><DD
19339 ><P
19340 >The winbind gid parameter specifies the range of group
19341                 ids that are allocated by the <A
19342 HREF="winbindd.8.html"
19343 TARGET="_top"
19344 >               winbindd(8)</A
19345 > daemon.  This range of ids should have no
19346                 existing local or NIS users within it as strange conflicts can
19347                 occur otherwise.</P
19348 ><P
19349 >Default: <B
19350 CLASS="COMMAND"
19351 >winbind uid = &#60;empty string&#62;
19352                 </B
19353 ></P
19354 ><P
19355 >Example: <B
19356 CLASS="COMMAND"
19357 >winbind uid = 10000-20000</B
19358 ></P
19359 ></DD
19360 ><DT
19361 >winbind use default domain, <A
19362 NAME="WINBINDUSEDEFAULTDOMAIN"
19363 ></A
19364 >winbind use default domain</DT
19365 ><DD
19366 ><P
19367 >This parameter specifies whether the <A
19368 HREF="winbindd.8.html"
19369 TARGET="_top"
19370 >               winbindd(8)</A
19371 >
19372                 daemon should operate on users without domain component in their username.
19373                 Users without a domain component are treated as is part of the winbindd server's
19374                 own domain.  While this does not benifit Windows users, it makes SSH, FTP and e-mail
19375                 function in a way much closer to the way they would in a native unix system.</P
19376 ><P
19377 >Default: <B
19378 CLASS="COMMAND"
19379 >winbind use default domain = &#60;no&#62;
19380                 </B
19381 ></P
19382 ><P
19383 >Example: <B
19384 CLASS="COMMAND"
19385 >winbind use default domain = yes</B
19386 ></P
19387 ></DD
19388 ><DT
19389 ><A
19390 NAME="WINSHOOK"
19391 ></A
19392 >wins hook (G)</DT
19393 ><DD
19394 ><P
19395 >When Samba is running as a WINS server this
19396                 allows you to call an external program for all changes to the
19397                 WINS database. The primary use for this option is to allow the
19398                 dynamic update of external name resolution databases such as
19399                 dynamic DNS.</P
19400 ><P
19401 >The wins hook parameter specifies the name of a script
19402                 or executable that will be called as follows:</P
19403 ><P
19404 ><B
19405 CLASS="COMMAND"
19406 >wins_hook operation name nametype ttl IP_list
19407                 </B
19408 ></P
19409 ><P
19410 ></P
19411 ><UL
19412 ><LI
19413 ><P
19414 >The first argument is the operation and is one
19415                         of "add", "delete", or "refresh". In most cases the operation can
19416                         be ignored as the rest of the parameters provide sufficient
19417                         information. Note that "refresh" may sometimes be called when the
19418                         name has not previously been added, in that case it should be treated
19419                         as an add.</P
19420 ></LI
19421 ><LI
19422 ><P
19423 >The second argument is the NetBIOS name. If the
19424                         name is not a legal name then the wins hook is not called.
19425                         Legal names contain only  letters, digits, hyphens, underscores
19426                         and periods.</P
19427 ></LI
19428 ><LI
19429 ><P
19430 >The third argument is the NetBIOS name
19431                         type as a 2 digit hexadecimal number. </P
19432 ></LI
19433 ><LI
19434 ><P
19435 >The fourth argument is the TTL (time to live)
19436                         for the name in seconds.</P
19437 ></LI
19438 ><LI
19439 ><P
19440 >The fifth and subsequent arguments are the IP
19441                         addresses currently registered for that name. If this list is
19442                         empty then the name should be deleted.</P
19443 ></LI
19444 ></UL
19445 ><P
19446 >An example script that calls the BIND dynamic DNS update
19447                 program <B
19448 CLASS="COMMAND"
19449 >nsupdate</B
19450 > is provided in the examples
19451                 directory of the Samba source code. </P
19452 ></DD
19453 ><DT
19454 ><A
19455 NAME="WINSPROXY"
19456 ></A
19457 >wins proxy (G)</DT
19458 ><DD
19459 ><P
19460 >This is a boolean that controls if <A
19461 HREF="nmbd.8.html"
19462 TARGET="_top"
19463 >nmbd(8)</A
19464 > will respond to broadcast name
19465                 queries on behalf of  other hosts. You may need to set this
19466                 to <TT
19467 CLASS="CONSTANT"
19468 >yes</TT
19469 > for some older clients.</P
19470 ><P
19471 >Default: <B
19472 CLASS="COMMAND"
19473 >wins proxy = no</B
19474 ></P
19475 ></DD
19476 ><DT
19477 ><A
19478 NAME="WINSSERVER"
19479 ></A
19480 >wins server (G)</DT
19481 ><DD
19482 ><P
19483 >This specifies the IP address (or DNS name: IP
19484                 address for preference) of the WINS server that <A
19485 HREF="nmbd.8.html"
19486 TARGET="_top"
19487 >               nmbd(8)</A
19488 > should register with. If you have a WINS server on
19489                 your network then you should set this to the WINS server's IP.</P
19490 ><P
19491 >You should point this at your WINS server if you have a
19492                 multi-subnetted network.</P
19493 ><P
19494 ><EM
19495 >NOTE</EM
19496 >. You need to set up Samba to point
19497                 to a WINS server if you have multiple subnets and wish cross-subnet
19498                 browsing to work correctly.</P
19499 ><P
19500 >See the documentation file <TT
19501 CLASS="FILENAME"
19502 >BROWSING.txt</TT
19503 >
19504                 in the docs/ directory of your Samba source distribution.</P
19505 ><P
19506 >Default: <EM
19507 >not enabled</EM
19508 ></P
19509 ><P
19510 >Example: <B
19511 CLASS="COMMAND"
19512 >wins server = 192.9.200.1</B
19513 ></P
19514 ></DD
19515 ><DT
19516 ><A
19517 NAME="WINSSUPPORT"
19518 ></A
19519 >wins support (G)</DT
19520 ><DD
19521 ><P
19522 >This boolean controls if the <A
19523 HREF="nmbd.8.html"
19524 TARGET="_top"
19525 >
19526                 nmbd(8)</A
19527 > process in Samba will act as a WINS server. You should
19528                 not set this to <TT
19529 CLASS="CONSTANT"
19530 >yes</TT
19531 > unless you have a multi-subnetted network and
19532                 you wish a particular <B
19533 CLASS="COMMAND"
19534 >nmbd</B
19535 > to be your WINS server.
19536                 Note that you should <EM
19537 >NEVER</EM
19538 > set this to <TT
19539 CLASS="CONSTANT"
19540 >yes</TT
19541 >
19542                 on more than one machine in your network.</P
19543 ><P
19544 >Default: <B
19545 CLASS="COMMAND"
19546 >wins support = no</B
19547 ></P
19548 ></DD
19549 ><DT
19550 ><A
19551 NAME="WORKGROUP"
19552 ></A
19553 >workgroup (G)</DT
19554 ><DD
19555 ><P
19556 >This controls what workgroup your server will
19557                 appear to be in when queried by clients. Note that this parameter
19558                 also controls the Domain name used with the <A
19559 HREF="#SECURITYEQUALSDOMAIN"
19560 ><B
19561 CLASS="COMMAND"
19562 >security = domain</B
19563 ></A
19564 >
19565                 setting.</P
19566 ><P
19567 >Default: <EM
19568 >set at compile time to WORKGROUP</EM
19569 ></P
19570 ><P
19571 >Example: <B
19572 CLASS="COMMAND"
19573 >workgroup = MYGROUP</B
19574 ></P
19575 ></DD
19576 ><DT
19577 ><A
19578 NAME="WRITABLE"
19579 ></A
19580 >writable (S)</DT
19581 ><DD
19582 ><P
19583 >Synonym for <A
19584 HREF="#WRITEABLE"
19585 ><TT
19586 CLASS="PARAMETER"
19587 ><I
19588 >               writeable</I
19589 ></TT
19590 ></A
19591 > for people who can't spell :-).</P
19592 ></DD
19593 ><DT
19594 ><A
19595 NAME="WRITECACHESIZE"
19596 ></A
19597 >write cache size (S)</DT
19598 ><DD
19599 ><P
19600 >If this integer parameter is set to non-zero value,
19601                 Samba will create an in-memory cache for each oplocked file
19602                 (it does <EM
19603 >not</EM
19604 > do this for
19605                 non-oplocked files). All writes that the client does not request
19606                 to be flushed directly to disk will be stored in this cache if possible.
19607                 The cache is flushed onto disk when a write comes in whose offset
19608                 would not fit into the cache or when the file is closed by the client.
19609                 Reads for the file are also served from this cache if the data is stored
19610                 within it.</P
19611 ><P
19612 >This cache allows Samba to batch client writes into a more
19613                 efficient write size for RAID disks (i.e. writes may be tuned to
19614                 be the RAID stripe size) and can improve performance on systems
19615                 where the disk subsystem is a bottleneck but there is free
19616                 memory for userspace programs.</P
19617 ><P
19618 >The integer parameter specifies the size of this cache
19619                 (per oplocked file) in bytes.</P
19620 ><P
19621 >Default: <B
19622 CLASS="COMMAND"
19623 >write cache size = 0</B
19624 ></P
19625 ><P
19626 >Example: <B
19627 CLASS="COMMAND"
19628 >write cache size = 262144</B
19629 ></P
19630 ><P
19631 >for a 256k cache size per file.</P
19632 ></DD
19633 ><DT
19634 ><A
19635 NAME="WRITELIST"
19636 ></A
19637 >write list (S)</DT
19638 ><DD
19639 ><P
19640 >This is a list of users that are given read-write
19641                 access to a service. If the connecting user is in this list then
19642                 they will be given write access, no matter what the <A
19643 HREF="#READONLY"
19644 ><TT
19645 CLASS="PARAMETER"
19646 ><I
19647 >read only</I
19648 ></TT
19649 ></A
19650 >
19651                 option is set to. The list can include group names using the
19652                 @group syntax.</P
19653 ><P
19654 >Note that if a user is in both the read list and the
19655                 write list then they will be given write access.</P
19656 ><P
19657 >See also the <A
19658 HREF="#READLIST"
19659 ><TT
19660 CLASS="PARAMETER"
19661 ><I
19662 >read list
19663                 </I
19664 ></TT
19665 ></A
19666 > option.</P
19667 ><P
19668 >Default: <B
19669 CLASS="COMMAND"
19670 >write list = &#60;empty string&#62;
19671                 </B
19672 ></P
19673 ><P
19674 >Example: <B
19675 CLASS="COMMAND"
19676 >write list = admin, root, @staff
19677                 </B
19678 ></P
19679 ></DD
19680 ><DT
19681 ><A
19682 NAME="WRITEOK"
19683 ></A
19684 >write ok (S)</DT
19685 ><DD
19686 ><P
19687 >Inverted synonym for <A
19688 HREF="#READONLY"
19689 ><TT
19690 CLASS="PARAMETER"
19691 ><I
19692 >               read only</I
19693 ></TT
19694 ></A
19695 >.</P
19696 ></DD
19697 ><DT
19698 ><A
19699 NAME="WRITERAW"
19700 ></A
19701 >write raw (G)</DT
19702 ><DD
19703 ><P
19704 >This parameter controls whether or not the server
19705                 will support raw write SMB's when transferring data from clients.
19706                 You should never need to change this parameter.</P
19707 ><P
19708 >Default: <B
19709 CLASS="COMMAND"
19710 >write raw = yes</B
19711 ></P
19712 ></DD
19713 ><DT
19714 ><A
19715 NAME="WRITEABLE"
19716 ></A
19717 >writeable (S)</DT
19718 ><DD
19719 ><P
19720 >Inverted synonym for <A
19721 HREF="#READONLY"
19722 ><TT
19723 CLASS="PARAMETER"
19724 ><I
19725 >               read only</I
19726 ></TT
19727 ></A
19728 >.</P
19729 ></DD
19730 ></DL
19731 ></DIV
19732 ></DIV
19733 ><DIV
19734 CLASS="REFSECT1"
19735 ><A
19736 NAME="AEN6235"
19737 ></A
19738 ><H2
19739 >WARNINGS</H2
19740 ><P
19741 >Although the configuration file permits service names
19742         to contain spaces, your client software may not. Spaces will
19743         be ignored in comparisons anyway, so it shouldn't be a
19744         problem - but be aware of the possibility.</P
19745 ><P
19746 >On a similar note, many clients - especially DOS clients -
19747         limit service names to eight characters. <A
19748 HREF="smbd.8.html"
19749 TARGET="_top"
19750 >smbd(8)
19751         </A
19752 > has no such limitation, but attempts to connect from such
19753         clients will fail if they truncate the service names.  For this reason
19754         you should probably keep your service names down to eight characters
19755         in length.</P
19756 ><P
19757 >Use of the [homes] and [printers] special sections make life
19758         for an administrator easy, but the various combinations of default
19759         attributes can be tricky. Take extreme care when designing these
19760         sections. In particular, ensure that the permissions on spool
19761         directories are correct.</P
19762 ></DIV
19763 ><DIV
19764 CLASS="REFSECT1"
19765 ><A
19766 NAME="AEN6241"
19767 ></A
19768 ><H2
19769 >VERSION</H2
19770 ><P
19771 >This man page is correct for version 2.2 of
19772         the Samba suite.</P
19773 ></DIV
19774 ><DIV
19775 CLASS="REFSECT1"
19776 ><A
19777 NAME="AEN6244"
19778 ></A
19779 ><H2
19780 >SEE ALSO</H2
19781 ><P
19782 ><A
19783 HREF="samba.7.html"
19784 TARGET="_top"
19785 >samba(7)</A
19786 >,
19787         <A
19788 HREF="smbpasswd.8.html"
19789 TARGET="_top"
19790 ><B
19791 CLASS="COMMAND"
19792 >smbpasswd(8)</B
19793 ></A
19794 >,
19795         <A
19796 HREF="swat.8.html"
19797 TARGET="_top"
19798 ><B
19799 CLASS="COMMAND"
19800 >swat(8)</B
19801 ></A
19802 >,
19803         <A
19804 HREF="smbd.8.html"
19805 TARGET="_top"
19806 ><B
19807 CLASS="COMMAND"
19808 >smbd(8)</B
19809 ></A
19810 >,
19811         <A
19812 HREF="nmbd.8.html"
19813 TARGET="_top"
19814 ><B
19815 CLASS="COMMAND"
19816 >nmbd(8)</B
19817 ></A
19818 >,
19819         <A
19820 HREF="smbclient.1.html"
19821 TARGET="_top"
19822 ><B
19823 CLASS="COMMAND"
19824 >smbclient(1)</B
19825 ></A
19826 >,
19827         <A
19828 HREF="nmblookup.1.html"
19829 TARGET="_top"
19830 ><B
19831 CLASS="COMMAND"
19832 >nmblookup(1)</B
19833 ></A
19834 >,
19835         <A
19836 HREF="testparm.1.html"
19837 TARGET="_top"
19838 ><B
19839 CLASS="COMMAND"
19840 >testparm(1)</B
19841 ></A
19842 >,
19843         <A
19844 HREF="testprns.1.html"
19845 TARGET="_top"
19846 ><B
19847 CLASS="COMMAND"
19848 >testprns(1)</B
19849 ></A
19850 >
19851         </P
19852 ></DIV
19853 ><DIV
19854 CLASS="REFSECT1"
19855 ><A
19856 NAME="AEN6264"
19857 ></A
19858 ><H2
19859 >AUTHOR</H2
19860 ><P
19861 >The original Samba software and related utilities
19862         were created by Andrew Tridgell. Samba is now developed
19863         by the Samba Team as an Open Source project similar
19864         to the way the Linux kernel is developed.</P
19865 ><P
19866 >The original Samba man pages were written by Karl Auer.
19867         The man page sources were converted to YODL format (another
19868         excellent piece of Open Source software, available at
19869         <A
19870 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
19871 TARGET="_top"
19872 >       ftp://ftp.icce.rug.nl/pub/unix/</A
19873 >) and updated for the Samba 2.0
19874         release by Jeremy Allison.  The conversion to DocBook for
19875         Samba 2.2 was done by Gerald Carter</P
19876 ></DIV
19877 ></BODY
19878 ></HTML
19879 >