docs/htmldocs/smb.conf.5.html

   1 <HTML
   2 ><HEAD
   3 ><TITLE
   4 >smb.conf</TITLE
   5 ><META
   6 NAME="GENERATOR"
   7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
   8 ><BODY
   9 CLASS="REFENTRY"
  10 BGCOLOR="#FFFFFF"
  11 TEXT="#000000"
  12 LINK="#0000FF"
  13 VLINK="#840084"
  14 ALINK="#0000FF"
  15 ><H1
  16 ><A
  17 NAME="SMB.CONF"
  18 >smb.conf</A
  19 ></H1
  20 ><DIV
  21 CLASS="REFNAMEDIV"
  22 ><A
  23 NAME="AEN5"
  24 ></A
  25 ><H2
  26 >Name</H2
  27 >smb.conf&nbsp;--&nbsp;The configuration file for the Samba suite</DIV
  28 ><DIV
  29 CLASS="REFSECT1"
  30 ><A
  31 NAME="AEN8"
  32 ></A
  33 ><H2
  34 >SYNOPSIS</H2
  35 ><P
  36 >The <TT
  37 CLASS="FILENAME"
  38 >smb.conf</TT
  39 > file is a configuration
  40         file for the Samba suite. <TT
  41 CLASS="FILENAME"
  42 >smb.conf</TT
  43 > contains
  44         runtime configuration information for the Samba programs. The
  45         <TT
  46 CLASS="FILENAME"
  47 >smb.conf</TT
  48 > file is designed to be configured and
  49         administered by the <A
  50 HREF="swat.8.html"
  51 TARGET="_top"
  52 ><B
  53 CLASS="COMMAND"
  54 >swat(8)</B
  55 >
  56         </A
  57 > program. The complete description of the file format and
  58         possible parameters held within are here for reference purposes.</P
  59 ></DIV
  60 ><DIV
  61 CLASS="REFSECT1"
  62 ><A
  63 NAME="AEN16"
  64 ></A
  65 ><H2
  66 >FILE FORMAT</H2
  67 ><P
  68 >The file consists of sections and parameters. A section
  69         begins with the name of the section in square brackets and continues
  70         until the next section begins. Sections contain parameters of the
  71         form</P
  72 ><P
  73 ><TT
  74 CLASS="REPLACEABLE"
  75 ><I
  76 >name</I
  77 ></TT
  78 > = <TT
  79 CLASS="REPLACEABLE"
  80 ><I
  81 >value
  82         </I
  83 ></TT
  84 ></P
  85 ><P
  86 >The file is line-based - that is, each newline-terminated
  87         line represents either a comment, a section name or a parameter.</P
  88 ><P
  89 >Section and parameter names are not case sensitive.</P
  90 ><P
  91 >Only the first equals sign in a parameter is significant.
  92         Whitespace before or after the first equals sign is discarded.
  93         Leading, trailing and internal whitespace in section and parameter
  94         names is irrelevant. Leading and trailing whitespace in a parameter
  95         value is discarded. Internal whitespace within a parameter value
  96         is retained verbatim.</P
  97 ><P
  98 >Any line beginning with a semicolon (';') or a hash ('#')
  99         character is ignored, as are lines containing only whitespace.</P
 100 ><P
 101 >Any line ending in a '\' is continued
 102         on the next line in the customary UNIX fashion.</P
 103 ><P
 104 >The values following the equals sign in parameters are all
 105         either a string (no quotes needed) or a boolean, which may be given
 106         as yes/no, 0/1 or true/false. Case is not significant in boolean
 107         values, but is preserved in string values. Some items such as
 108         create modes are numeric.</P
 109 ></DIV
 110 ><DIV
 111 CLASS="REFSECT1"
 112 ><A
 113 NAME="AEN28"
 114 ></A
 115 ><H2
 116 >SECTION DESCRIPTIONS</H2
 117 ><P
 118 >Each section in the configuration file (except for the
 119         [global] section) describes a shared resource (known
 120         as a "share"). The section name is the name of the
 121         shared resource and the parameters within the section define
 122         the shares attributes.</P
 123 ><P
 124 >There are three special sections, [global],
 125         [homes] and [printers], which are
 126         described under <EM
 127 >special sections</EM
 128 >. The
 129         following notes apply to ordinary section descriptions.</P
 130 ><P
 131 >A share consists of a directory to which access is being
 132         given plus a description of the access rights which are granted
 133         to the user of the service. Some housekeeping options are
 134         also specifiable.</P
 135 ><P
 136 >Sections are either file share services (used by the
 137         client as an extension of their native file systems) or
 138         printable services (used by the client to access print services
 139         on the host running the server).</P
 140 ><P
 141 >Sections may be designated <EM
 142 >guest</EM
 143 > services,
 144         in which case no password is required to access them. A specified
 145         UNIX <EM
 146 >guest account</EM
 147 > is used to define access
 148         privileges in this case.</P
 149 ><P
 150 >Sections other than guest services will require a password
 151         to access them. The client provides the username. As older clients
 152         only provide passwords and not usernames, you may specify a list
 153         of usernames to check against the password using the "user="
 154         option in the share definition. For modern clients such as
 155         Windows 95/98/ME/NT/2000, this should not be necessary.</P
 156 ><P
 157 >Note that the access rights granted by the server are
 158         masked by the access rights granted to the specified or guest
 159         UNIX user by the host system. The server does not grant more
 160         access than the host system grants.</P
 161 ><P
 162 >The following sample section defines a file space share.
 163         The user has write access to the path <TT
 164 CLASS="FILENAME"
 165 >/home/bar</TT
 166 >.
 167         The share is accessed via the share name "foo":</P
 168 ><TABLE
 169 BORDER="0"
 170 BGCOLOR="#E0E0E0"
 171 WIDTH="100%"
 172 ><TR
 173 ><TD
 174 ><PRE
 175 CLASS="SCREEN"
 176 >       <TT
 177 CLASS="COMPUTEROUTPUT"
 178 >       [foo]
 179                 path = /home/bar
 180                 writeable = true
 181         </TT
 182 >
 183         </PRE
 184 ></TD
 185 ></TR
 186 ></TABLE
 187 ><P
 188 >The following sample section defines a printable share.
 189         The share is readonly, but printable. That is, the only write
 190         access permitted is via calls to open, write to and close a
 191         spool file. The <EM
 192 >guest ok</EM
 193 > parameter means
 194         access will be permitted as the default guest user (specified
 195         elsewhere):</P
 196 ><TABLE
 197 BORDER="0"
 198 BGCOLOR="#E0E0E0"
 199 WIDTH="100%"
 200 ><TR
 201 ><TD
 202 ><PRE
 203 CLASS="SCREEN"
 204 >       <TT
 205 CLASS="COMPUTEROUTPUT"
 206 >       [aprinter]
 207                 path = /usr/spool/public
 208                 writeable = false
 209                 printable = true
 210                 guest ok = true
 211         </TT
 212 >
 213         </PRE
 214 ></TD
 215 ></TR
 216 ></TABLE
 217 ></DIV
 218 ><DIV
 219 CLASS="REFSECT1"
 220 ><A
 221 NAME="AEN48"
 222 ></A
 223 ><H2
 224 >SPECIAL SECTIONS</H2
 225 ><DIV
 226 CLASS="REFSECT2"
 227 ><A
 228 NAME="AEN50"
 229 ></A
 230 ><H3
 231 >The [global] section</H3
 232 ><P
 233 >parameters in this section apply to the server
 234                 as a whole, or are defaults for sections which do not
 235                 specifically define certain items. See the notes
 236                 under PARAMETERS for more information.</P
 237 ></DIV
 238 ><DIV
 239 CLASS="REFSECT2"
 240 ><A
 241 NAME="AEN53"
 242 ></A
 243 ><H3
 244 >The [homes] section</H3
 245 ><P
 246 >If a section called homes is included in the
 247                 configuration file, services connecting clients to their
 248                 home directories can be created on the fly by the server.</P
 249 ><P
 250 >When the connection request is made, the existing
 251                 sections are scanned. If a match is found, it is used. If no
 252                 match is found, the requested section name is treated as a
 253                 user name and looked up in the local password file. If the
 254                 name exists and the correct password has been given, a share is
 255                 created by cloning the [homes] section.</P
 256 ><P
 257 >Some modifications are then made to the newly
 258                 created share:</P
 259 ><P
 260 ></P
 261 ><UL
 262 ><LI
 263 ><P
 264 >The share name is changed from homes to
 265                 the located username.</P
 266 ></LI
 267 ><LI
 268 ><P
 269 >If no path was given, the path is set to
 270                 the user's home directory.</P
 271 ></LI
 272 ></UL
 273 ><P
 274 >If you decide to use a <EM
 275 >path=</EM
 276 > line
 277                 in your [homes] section then you may find it useful
 278                 to use the %S macro. For example :</P
 279 ><P
 280 ><TT
 281 CLASS="USERINPUT"
 282 ><B
 283 >path=/data/pchome/%S</B
 284 ></TT
 285 ></P
 286 ><P
 287 >would be useful if you have different home directories
 288                 for your PCs than for UNIX access.</P
 289 ><P
 290 >This is a fast and simple way to give a large number
 291                 of clients access to their home directories with a minimum
 292                 of fuss.</P
 293 ><P
 294 >A similar process occurs if the requested section
 295                 name is "homes", except that the share name is not
 296                 changed to that of the requesting user. This method of using
 297                 the [homes] section works well if different users share
 298                 a client PC.</P
 299 ><P
 300 >The [homes] section can specify all the parameters
 301                 a normal service section can specify, though some make more sense
 302                 than others. The following is a typical and suitable [homes]
 303                 section:</P
 304 ><TABLE
 305 BORDER="0"
 306 BGCOLOR="#E0E0E0"
 307 WIDTH="100%"
 308 ><TR
 309 ><TD
 310 ><PRE
 311 CLASS="SCREEN"
 312 >               <TT
 313 CLASS="COMPUTEROUTPUT"
 314 >               [homes]
 315                         writeable = yes
 316                 </TT
 317 >
 318                 </PRE
 319 ></TD
 320 ></TR
 321 ></TABLE
 322 ><P
 323 >An important point is that if guest access is specified
 324                 in the [homes] section, all home directories will be
 325                 visible to all clients <EM
 326 >without a password</EM
 327 >.
 328                 In the very unlikely event that this is actually desirable, it
 329                 would be wise to also specify <EM
 330 >read only
 331                 access</EM
 332 >.</P
 333 ><P
 334 >Note that the <EM
 335 >browseable</EM
 336 > flag for
 337                 auto home directories will be inherited from the global browseable
 338                 flag, not the [homes] browseable flag. This is useful as
 339                 it means setting browseable=no in the [homes] section
 340                 will hide the [homes] share but make any auto home
 341                 directories visible.</P
 342 ></DIV
 343 ><DIV
 344 CLASS="REFSECT2"
 345 ><A
 346 NAME="AEN78"
 347 ></A
 348 ><H3
 349 >The [printers] section</H3
 350 ><P
 351 >This section works like [homes],
 352                 but for printers.</P
 353 ><P
 354 >If a [printers] section occurs in the
 355                 configuration file, users are able to connect to any printer
 356                 specified in the local host's printcap file.</P
 357 ><P
 358 >When a connection request is made, the existing sections
 359                 are scanned. If a match is found, it is used. If no match is found,
 360                 but a [homes] section exists, it is used as described
 361                 above. Otherwise, the requested section name is treated as a
 362                 printer name and the appropriate printcap file is scanned to see
 363                 if the requested section name is a valid printer share name. If
 364                 a match is found, a new printer share is created by cloning
 365                 the [printers] section.</P
 366 ><P
 367 >A few modifications are then made to the newly created
 368                 share:</P
 369 ><P
 370 ></P
 371 ><UL
 372 ><LI
 373 ><P
 374 >The share name is set to the located printer
 375                 name</P
 376 ></LI
 377 ><LI
 378 ><P
 379 >If no printer name was given, the printer name
 380                 is set to the located printer name</P
 381 ></LI
 382 ><LI
 383 ><P
 384 >If the share does not permit guest access and
 385                 no username was given, the username is set to the located
 386                 printer name.</P
 387 ></LI
 388 ></UL
 389 ><P
 390 >Note that the [printers] service MUST be
 391                 printable - if you specify otherwise, the server will refuse
 392                 to load the configuration file.</P
 393 ><P
 394 >Typically the path specified would be that of a
 395                 world-writeable spool directory with the sticky bit set on
 396                 it. A typical [printers] entry would look like
 397                 this:</P
 398 ><TABLE
 399 BORDER="0"
 400 BGCOLOR="#E0E0E0"
 401 WIDTH="100%"
 402 ><TR
 403 ><TD
 404 ><PRE
 405 CLASS="SCREEN"
 406 ><TT
 407 CLASS="COMPUTEROUTPUT"
 408 >               [printers]
 409                         path = /usr/spool/public
 410                         guest ok = yes
 411                         printable = yes
 412                 </TT
 413 ></PRE
 414 ></TD
 415 ></TR
 416 ></TABLE
 417 ><P
 418 >All aliases given for a printer in the printcap file
 419                 are legitimate printer names as far as the server is concerned.
 420                 If your printing subsystem doesn't work like that, you will have
 421                 to set up a pseudo-printcap. This is a file consisting of one or
 422                 more lines like this:</P
 423 ><TABLE
 424 BORDER="0"
 425 BGCOLOR="#E0E0E0"
 426 WIDTH="100%"
 427 ><TR
 428 ><TD
 429 ><PRE
 430 CLASS="SCREEN"
 431 >               <TT
 432 CLASS="COMPUTEROUTPUT"
 433 >               alias|alias|alias|alias...
 434                 </TT
 435 >
 436                 </PRE
 437 ></TD
 438 ></TR
 439 ></TABLE
 440 ><P
 441 >Each alias should be an acceptable printer name for
 442                 your printing subsystem. In the [global] section, specify
 443                 the new file as your printcap.  The server will then only recognize
 444                 names found in your pseudo-printcap, which of course can contain
 445                 whatever aliases you like. The same technique could be used
 446                 simply to limit access to a subset of your local printers.</P
 447 ><P
 448 >An alias, by the way, is defined as any component of the
 449                 first entry of a printcap record. Records are separated by newlines,
 450                 components (if there are more than one) are separated by vertical
 451                 bar symbols ('|').</P
 452 ><P
 453 >NOTE: On SYSV systems which use lpstat to determine what
 454                 printers are defined on the system you may be able to use
 455                 "printcap name = lpstat" to automatically obtain a list
 456                 of printers. See the "printcap name" option
 457                 for more details.</P
 458 ></DIV
 459 ></DIV
 460 ><DIV
 461 CLASS="REFSECT1"
 462 ><A
 463 NAME="AEN101"
 464 ></A
 465 ><H2
 466 >PARAMETERS</H2
 467 ><P
 468 >parameters define the specific attributes of sections.</P
 469 ><P
 470 >Some parameters are specific to the [global] section
 471         (e.g., <EM
 472 >security</EM
 473 >).  Some parameters are usable
 474         in all sections (e.g., <EM
 475 >create mode</EM
 476 >). All others
 477         are permissible only in normal sections. For the purposes of the
 478         following descriptions the [homes] and [printers]
 479         sections will be considered normal.  The letter <EM
 480 >G</EM
 481 >
 482         in parentheses indicates that a parameter is specific to the
 483         [global] section. The letter <EM
 484 >S</EM
 485 >
 486         indicates that a parameter can be specified in a service specific
 487         section. Note that all <EM
 488 >S</EM
 489 > parameters can also be specified in
 490         the [global] section - in which case they will define
 491         the default behavior for all services.</P
 492 ><P
 493 >parameters are arranged here in alphabetical order - this may
 494         not create best bedfellows, but at least you can find them! Where
 495         there are synonyms, the preferred synonym is described, others refer
 496         to the preferred synonym.</P
 497 ></DIV
 498 ><DIV
 499 CLASS="REFSECT1"
 500 ><A
 501 NAME="AEN111"
 502 ></A
 503 ><H2
 504 >VARIABLE SUBSTITUTIONS</H2
 505 ><P
 506 >Many of the strings that are settable in the config file
 507         can take substitutions. For example the option "path =
 508         /tmp/%u" would be interpreted as "path =
 509         /tmp/john" if the user connected with the username john.</P
 510 ><P
 511 >These substitutions are mostly noted in the descriptions below,
 512         but there are some general substitutions which apply whenever they
 513         might be relevant. These are:</P
 514 ><P
 515 ></P
 516 ><DIV
 517 CLASS="VARIABLELIST"
 518 ><DL
 519 ><DT
 520 >%S</DT
 521 ><DD
 522 ><P
 523 >the name of the current service, if any.</P
 524 ></DD
 525 ><DT
 526 >%P</DT
 527 ><DD
 528 ><P
 529 >the root directory of the current service,
 530                 if any.</P
 531 ></DD
 532 ><DT
 533 >%u</DT
 534 ><DD
 535 ><P
 536 >user name of the current service, if any.</P
 537 ></DD
 538 ><DT
 539 >%g</DT
 540 ><DD
 541 ><P
 542 >primary group name of %u.</P
 543 ></DD
 544 ><DT
 545 >%U</DT
 546 ><DD
 547 ><P
 548 >session user name (the user name that the client
 549                 wanted, not necessarily the same as the one they got).</P
 550 ></DD
 551 ><DT
 552 >%G</DT
 553 ><DD
 554 ><P
 555 >primary group name of %U.</P
 556 ></DD
 557 ><DT
 558 >%H</DT
 559 ><DD
 560 ><P
 561 >the home directory of the user given
 562                 by %u.</P
 563 ></DD
 564 ><DT
 565 >%v</DT
 566 ><DD
 567 ><P
 568 >the Samba version.</P
 569 ></DD
 570 ><DT
 571 >%h</DT
 572 ><DD
 573 ><P
 574 >the Internet hostname that Samba is running
 575                 on.</P
 576 ></DD
 577 ><DT
 578 >%m</DT
 579 ><DD
 580 ><P
 581 >the NetBIOS name of the client machine
 582                 (very useful).</P
 583 ></DD
 584 ><DT
 585 >%L</DT
 586 ><DD
 587 ><P
 588 >the NetBIOS name of the server. This allows you
 589                 to change your config based on what the client calls you. Your
 590                 server can have a "dual personality".</P
 591 ></DD
 592 ><DT
 593 >%M</DT
 594 ><DD
 595 ><P
 596 >the Internet name of the client machine.
 597                 </P
 598 ></DD
 599 ><DT
 600 >%N</DT
 601 ><DD
 602 ><P
 603 >the name of your NIS home directory server.
 604                 This is obtained from your NIS auto.map entry.  If you have
 605                 not compiled Samba with the <EM
 606 >--with-automount</EM
 607 >
 608                 option then this value will be the same as %.</P
 609 ></DD
 610 ><DT
 611 >%p</DT
 612 ><DD
 613 ><P
 614 >the path of the service's home directory,
 615                 obtained from your NIS auto.map entry. The NIS auto.map entry
 616                 is split up as "%N:%p".</P
 617 ></DD
 618 ><DT
 619 >%R</DT
 620 ><DD
 621 ><P
 622 >the selected protocol level after
 623                 protocol negotiation. It can be one of CORE, COREPLUS,
 624                 LANMAN1, LANMAN2 or NT1.</P
 625 ></DD
 626 ><DT
 627 >%d</DT
 628 ><DD
 629 ><P
 630 >The process id of the current server
 631                 process.</P
 632 ></DD
 633 ><DT
 634 >%a</DT
 635 ><DD
 636 ><P
 637 >the architecture of the remote
 638                 machine. Only some are recognized, and those may not be
 639                 100% reliable. It currently recognizes Samba, WfWg,
 640                 WinNT and Win95. Anything else will be known as
 641                 "UNKNOWN". If it gets it wrong then sending a level
 642                 3 log to <A
 643 HREF="mailto:samba@samba.org"
 644 TARGET="_top"
 645 >samba@samba.org
 646                 </A
 647 > should allow it to be fixed.</P
 648 ></DD
 649 ><DT
 650 >%I</DT
 651 ><DD
 652 ><P
 653 >The IP address of the client machine.</P
 654 ></DD
 655 ><DT
 656 >%T</DT
 657 ><DD
 658 ><P
 659 >the current date and time.</P
 660 ></DD
 661 ><DT
 662 >%$(<TT
 663 CLASS="REPLACEABLE"
 664 ><I
 665 >envvar</I
 666 ></TT
 667 >)</DT
 668 ><DD
 669 ><P
 670 >The value of the environment variable
 671                 <TT
 672 CLASS="REPLACEABLE"
 673 ><I
 674 >envar</I
 675 ></TT
 676 >.</P
 677 ></DD
 678 ></DL
 679 ></DIV
 680 ><P
 681 >There are some quite creative things that can be done
 682         with these substitutions and other smb.conf options.</P
 683 ></DIV
 684 ><DIV
 685 CLASS="REFSECT1"
 686 ><A
 687 NAME="AEN201"
 688 ></A
 689 ><H2
 690 >NAME MANGLING</H2
 691 ><P
 692 >Samba supports "name mangling" so that DOS and
 693         Windows clients can use files that don't conform to the 8.3 format.
 694         It can also be set to adjust the case of 8.3 format filenames.</P
 695 ><P
 696 >There are several options that control the way mangling is
 697         performed, and they are grouped here rather than listed separately.
 698         For the defaults look at the output of the testparm program. </P
 699 ><P
 700 >All of these options can be set separately for each service
 701         (or globally, of course). </P
 702 ><P
 703 >The options are: </P
 704 ><P
 705 ></P
 706 ><DIV
 707 CLASS="VARIABLELIST"
 708 ><DL
 709 ><DT
 710 >mangle case= yes/no</DT
 711 ><DD
 712 ><P
 713 > controls if names that have characters that
 714                 aren't of the "default" case are mangled. For example,
 715                 if this is yes then a name like "Mail" would be mangled.
 716                 Default <EM
 717 >no</EM
 718 >.</P
 719 ></DD
 720 ><DT
 721 >case sensitive = yes/no</DT
 722 ><DD
 723 ><P
 724 >controls whether filenames are case sensitive. If
 725                 they aren't then Samba must do a filename search and match on passed
 726                 names. Default <EM
 727 >no</EM
 728 >.</P
 729 ></DD
 730 ><DT
 731 >default case = upper/lower</DT
 732 ><DD
 733 ><P
 734 >controls what the default case is for new
 735                 filenames. Default <EM
 736 >lower</EM
 737 >.</P
 738 ></DD
 739 ><DT
 740 >preserve case = yes/no</DT
 741 ><DD
 742 ><P
 743 >controls if new files are created with the
 744                 case that the client passes, or if they are forced to be the
 745                 "default" case. Default <EM
 746 >yes</EM
 747 >.
 748                 </P
 749 ></DD
 750 ><DT
 751 >short preserve case = yes/no</DT
 752 ><DD
 753 ><P
 754 >controls if new files which conform to 8.3 syntax,
 755                 that is all in upper case and of suitable length, are created
 756                 upper case, or if they are forced to be the "default"
 757                 case. This option can be use with "preserve case = yes"
 758                 to permit long filenames to retain their case, while short names
 759                 are lowered. Default <EM
 760 >yes</EM
 761 >.</P
 762 ></DD
 763 ></DL
 764 ></DIV
 765 ><P
 766 >By default, Samba 2.2 has the same semantics as a Windows
 767         NT server, in that it is case insensitive but case preserving.</P
 768 ></DIV
 769 ><DIV
 770 CLASS="REFSECT1"
 771 ><A
 772 NAME="AEN234"
 773 ></A
 774 ><H2
 775 >NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2
 776 ><P
 777 >There are a number of ways in which a user can connect
 778         to a service. The server uses the following steps in determining
 779         if it will allow a connection to a specified service. If all the
 780         steps fail, then the connection request is rejected.  However, if one of the
 781         steps succeeds, then the following steps are not checked.</P
 782 ><P
 783 >If the service is marked "guest only = yes" then
 784         steps 1 to 5 are skipped.</P
 785 ><P
 786 ></P
 787 ><OL
 788 TYPE="1"
 789 ><LI
 790 ><P
 791 >If the client has passed a username/password
 792                 pair and that username/password pair is validated by the UNIX
 793                 system's password programs then the connection is made as that
 794                 username. Note that this includes the
 795                 \\server\service%<TT
 796 CLASS="REPLACEABLE"
 797 ><I
 798 >username</I
 799 ></TT
 800 > method of passing
 801                 a username.</P
 802 ></LI
 803 ><LI
 804 ><P
 805 >If the client has previously registered a username
 806                 with the system and now supplies a correct password for that
 807                 username then the connection is allowed.</P
 808 ></LI
 809 ><LI
 810 ><P
 811 >The client's netbios name and any previously
 812                 used user names are checked against the supplied password, if
 813                 they match then the connection is allowed as the corresponding
 814                 user.</P
 815 ></LI
 816 ><LI
 817 ><P
 818 >If the client has previously validated a
 819                 username/password pair with the server and the client has passed
 820                 the validation token then that username is used. </P
 821 ></LI
 822 ><LI
 823 ><P
 824 >If a "user = " field is given in the
 825                 <TT
 826 CLASS="FILENAME"
 827 >smb.conf</TT
 828 > file for the service and the client
 829                 has supplied a password, and that password matches (according to
 830                 the UNIX system's password checking) with one of the usernames
 831                 from the "user=" field then the connection is made as
 832                 the username in the "user=" line. If one
 833                 of the username in the "user=" list begins with a
 834                 '@' then that name expands to a list of names in
 835                 the group of the same name.</P
 836 ></LI
 837 ><LI
 838 ><P
 839 >If the service is a guest service then a
 840                 connection is made as the username given in the "guest
 841                 account =" for the service, irrespective of the
 842                 supplied password.</P
 843 ></LI
 844 ></OL
 845 ></DIV
 846 ><DIV
 847 CLASS="REFSECT1"
 848 ><A
 849 NAME="AEN253"
 850 ></A
 851 ><H2
 852 >COMPLETE LIST OF GLOBAL PARAMETERS</H2
 853 ><P
 854 >Here is a list of all global parameters. See the section of
 855         each parameter for details.  Note that some are synonyms.</P
 856 ><P
 857 ></P
 858 ><UL
 859 ><LI
 860 ><P
 861 ><A
 862 HREF="#ADDPRINTERCOMMAND"
 863 ><TT
 864 CLASS="PARAMETER"
 865 ><I
 866 >add printer command</I
 867 ></TT
 868 ></A
 869 ></P
 870 ></LI
 871 ><LI
 872 ><P
 873 ><A
 874 HREF="#ADDSHARECOMMAND"
 875 ><TT
 876 CLASS="PARAMETER"
 877 ><I
 878 >add share command</I
 879 ></TT
 880 ></A
 881 ></P
 882 ></LI
 883 ><LI
 884 ><P
 885 ><A
 886 HREF="#ADDUSERSCRIPT"
 887 ><TT
 888 CLASS="PARAMETER"
 889 ><I
 890 >add user script</I
 891 ></TT
 892 ></A
 893 ></P
 894 ></LI
 895 ><LI
 896 ><P
 897 ><A
 898 HREF="#ALLOWTRUSTEDDOMAINS"
 899 ><TT
 900 CLASS="PARAMETER"
 901 ><I
 902 >allow trusted domains</I
 903 ></TT
 904 ></A
 905 ></P
 906 ></LI
 907 ><LI
 908 ><P
 909 ><A
 910 HREF="#ANNOUNCEAS"
 911 ><TT
 912 CLASS="PARAMETER"
 913 ><I
 914 >announce as</I
 915 ></TT
 916 ></A
 917 ></P
 918 ></LI
 919 ><LI
 920 ><P
 921 ><A
 922 HREF="#ANNOUNCEVERSION"
 923 ><TT
 924 CLASS="PARAMETER"
 925 ><I
 926 >announce version</I
 927 ></TT
 928 ></A
 929 ></P
 930 ></LI
 931 ><LI
 932 ><P
 933 ><A
 934 HREF="#AUTOSERVICES"
 935 ><TT
 936 CLASS="PARAMETER"
 937 ><I
 938 >auto services</I
 939 ></TT
 940 ></A
 941 ></P
 942 ></LI
 943 ><LI
 944 ><P
 945 ><A
 946 HREF="#BINDINTERFACESONLY"
 947 ><TT
 948 CLASS="PARAMETER"
 949 ><I
 950 >bind interfaces only</I
 951 ></TT
 952 ></A
 953 ></P
 954 ></LI
 955 ><LI
 956 ><P
 957 ><A
 958 HREF="#BROWSELIST"
 959 ><TT
 960 CLASS="PARAMETER"
 961 ><I
 962 >browse list</I
 963 ></TT
 964 ></A
 965 ></P
 966 ></LI
 967 ><LI
 968 ><P
 969 ><A
 970 HREF="#CHANGENOTIFYTIMEOUT"
 971 ><TT
 972 CLASS="PARAMETER"
 973 ><I
 974 >change notify timeout</I
 975 ></TT
 976 ></A
 977 ></P
 978 ></LI
 979 ><LI
 980 ><P
 981 ><A
 982 HREF="#CHANGESHARECOMMAND"
 983 ><TT
 984 CLASS="PARAMETER"
 985 ><I
 986 >change share command</I
 987 ></TT
 988 ></A
 989 ></P
 990 ></LI
 991 ><LI
 992 ><P
 993 ><A
 994 HREF="#CHARACTERSET"
 995 ><TT
 996 CLASS="PARAMETER"
 997 ><I
 998 >character set</I
 999 ></TT
1000 ></A
1001 ></P
1002 ></LI
1003 ><LI
1004 ><P
1005 ><A
1006 HREF="#CLIENTCODEPAGE"
1007 ><TT
1008 CLASS="PARAMETER"
1009 ><I
1010 >client code page</I
1011 ></TT
1012 ></A
1013 ></P
1014 ></LI
1015 ><LI
1016 ><P
1017 ><A
1018 HREF="#CODEPAGEDIRECTORY"
1019 ><TT
1020 CLASS="PARAMETER"
1021 ><I
1022 >code page directory</I
1023 ></TT
1024 ></A
1025 ></P
1026 ></LI
1027 ><LI
1028 ><P
1029 ><A
1030 HREF="#CODINGSYSTEM"
1031 ><TT
1032 CLASS="PARAMETER"
1033 ><I
1034 >coding system</I
1035 ></TT
1036 ></A
1037 ></P
1038 ></LI
1039 ><LI
1040 ><P
1041 ><A
1042 HREF="#CONFIGFILE"
1043 ><TT
1044 CLASS="PARAMETER"
1045 ><I
1046 >config file</I
1047 ></TT
1048 ></A
1049 ></P
1050 ></LI
1051 ><LI
1052 ><P
1053 ><A
1054 HREF="#DEADTIME"
1055 ><TT
1056 CLASS="PARAMETER"
1057 ><I
1058 >deadtime</I
1059 ></TT
1060 ></A
1061 ></P
1062 ></LI
1063 ><LI
1064 ><P
1065 ><A
1066 HREF="#DEBUGHIRESTIMESTAMP"
1067 ><TT
1068 CLASS="PARAMETER"
1069 ><I
1070 >debug hires timestamp</I
1071 ></TT
1072 ></A
1073 ></P
1074 ></LI
1075 ><LI
1076 ><P
1077 ><A
1078 HREF="#DEBUGPID"
1079 ><TT
1080 CLASS="PARAMETER"
1081 ><I
1082 >debug pid</I
1083 ></TT
1084 ></A
1085 ></P
1086 ></LI
1087 ><LI
1088 ><P
1089 ><A
1090 HREF="#DEBUGTIMESTAMP"
1091 ><TT
1092 CLASS="PARAMETER"
1093 ><I
1094 >debug timestamp</I
1095 ></TT
1096 ></A
1097 ></P
1098 ></LI
1099 ><LI
1100 ><P
1101 ><A
1102 HREF="#DEBUGUID"
1103 ><TT
1104 CLASS="PARAMETER"
1105 ><I
1106 >debug uid</I
1107 ></TT
1108 ></A
1109 ></P
1110 ></LI
1111 ><LI
1112 ><P
1113 ><A
1114 HREF="#DEBUGLEVEL"
1115 ><TT
1116 CLASS="PARAMETER"
1117 ><I
1118 >debuglevel</I
1119 ></TT
1120 ></A
1121 ></P
1122 ></LI
1123 ><LI
1124 ><P
1125 ><A
1126 HREF="#DEFAULT"
1127 ><TT
1128 CLASS="PARAMETER"
1129 ><I
1130 >default</I
1131 ></TT
1132 ></A
1133 ></P
1134 ></LI
1135 ><LI
1136 ><P
1137 ><A
1138 HREF="#DEFAULTSERVICE"
1139 ><TT
1140 CLASS="PARAMETER"
1141 ><I
1142 >default service</I
1143 ></TT
1144 ></A
1145 ></P
1146 ></LI
1147 ><LI
1148 ><P
1149 ><A
1150 HREF="#DELETEPRINTERCOMMAND"
1151 ><TT
1152 CLASS="PARAMETER"
1153 ><I
1154 >delete printer command</I
1155 ></TT
1156 ></A
1157 ></P
1158 ></LI
1159 ><LI
1160 ><P
1161 ><A
1162 HREF="#DELETESHARECOMMAND"
1163 ><TT
1164 CLASS="PARAMETER"
1165 ><I
1166 >delete share command</I
1167 ></TT
1168 ></A
1169 ></P
1170 ></LI
1171 ><LI
1172 ><P
1173 ><A
1174 HREF="#DELETEUSERSCRIPT"
1175 ><TT
1176 CLASS="PARAMETER"
1177 ><I
1178 >delete user script</I
1179 ></TT
1180 ></A
1181 ></P
1182 ></LI
1183 ><LI
1184 ><P
1185 ><A
1186 HREF="#DFREECOMMAND"
1187 ><TT
1188 CLASS="PARAMETER"
1189 ><I
1190 >dfree command</I
1191 ></TT
1192 ></A
1193 ></P
1194 ></LI
1195 ><LI
1196 ><P
1197 ><A
1198 HREF="#DNSPROXY"
1199 ><TT
1200 CLASS="PARAMETER"
1201 ><I
1202 >dns proxy</I
1203 ></TT
1204 ></A
1205 ></P
1206 ></LI
1207 ><LI
1208 ><P
1209 ><A
1210 HREF="#DOMAINADMINGROUP"
1211 ><TT
1212 CLASS="PARAMETER"
1213 ><I
1214 >domain admin group</I
1215 ></TT
1216 ></A
1217 ></P
1218 ></LI
1219 ><LI
1220 ><P
1221 ><A
1222 HREF="#DOMAINGUESTGROUP"
1223 ><TT
1224 CLASS="PARAMETER"
1225 ><I
1226 >domain guest group</I
1227 ></TT
1228 ></A
1229 ></P
1230 ></LI
1231 ><LI
1232 ><P
1233 ><A
1234 HREF="#DOMAINLOGONS"
1235 ><TT
1236 CLASS="PARAMETER"
1237 ><I
1238 >domain logons</I
1239 ></TT
1240 ></A
1241 ></P
1242 ></LI
1243 ><LI
1244 ><P
1245 ><A
1246 HREF="#DOMAINMASTER"
1247 ><TT
1248 CLASS="PARAMETER"
1249 ><I
1250 >domain master</I
1251 ></TT
1252 ></A
1253 ></P
1254 ></LI
1255 ><LI
1256 ><P
1257 ><A
1258 HREF="#ENCRYPTPASSWORDS"
1259 ><TT
1260 CLASS="PARAMETER"
1261 ><I
1262 >encrypt passwords</I
1263 ></TT
1264 ></A
1265 ></P
1266 ></LI
1267 ><LI
1268 ><P
1269 ><A
1270 HREF="#ENHANCEDBROWSING"
1271 ><TT
1272 CLASS="PARAMETER"
1273 ><I
1274 >enhanced browsing</I
1275 ></TT
1276 ></A
1277 ></P
1278 ></LI
1279 ><LI
1280 ><P
1281 ><A
1282 HREF="#ENUMPORTSCOMMAND"
1283 ><TT
1284 CLASS="PARAMETER"
1285 ><I
1286 >enumports command</I
1287 ></TT
1288 ></A
1289 ></P
1290 ></LI
1291 ><LI
1292 ><P
1293 ><A
1294 HREF="#GETWDCACHE"
1295 ><TT
1296 CLASS="PARAMETER"
1297 ><I
1298 >getwd cache</I
1299 ></TT
1300 ></A
1301 ></P
1302 ></LI
1303 ><LI
1304 ><P
1305 ><A
1306 HREF="#HIDELOCALUSERS"
1307 ><TT
1308 CLASS="PARAMETER"
1309 ><I
1310 >hide local users</I
1311 ></TT
1312 ></A
1313 ></P
1314 ></LI
1315 ><LI
1316 ><P
1317 ><A
1318 HREF="#HOMEDIRMAP"
1319 ><TT
1320 CLASS="PARAMETER"
1321 ><I
1322 >homedir map</I
1323 ></TT
1324 ></A
1325 ></P
1326 ></LI
1327 ><LI
1328 ><P
1329 ><A
1330 HREF="#HOSTMSDFS"
1331 ><TT
1332 CLASS="PARAMETER"
1333 ><I
1334 >host msdfs</I
1335 ></TT
1336 ></A
1337 ></P
1338 ></LI
1339 ><LI
1340 ><P
1341 ><A
1342 HREF="#HOSTSEQUIV"
1343 ><TT
1344 CLASS="PARAMETER"
1345 ><I
1346 >hosts equiv</I
1347 ></TT
1348 ></A
1349 ></P
1350 ></LI
1351 ><LI
1352 ><P
1353 ><A
1354 HREF="#INTERFACES"
1355 ><TT
1356 CLASS="PARAMETER"
1357 ><I
1358 >interfaces</I
1359 ></TT
1360 ></A
1361 ></P
1362 ></LI
1363 ><LI
1364 ><P
1365 ><A
1366 HREF="#KEEPALIVE"
1367 ><TT
1368 CLASS="PARAMETER"
1369 ><I
1370 >keepalive</I
1371 ></TT
1372 ></A
1373 ></P
1374 ></LI
1375 ><LI
1376 ><P
1377 ><A
1378 HREF="#KERNELOPLOCKS"
1379 ><TT
1380 CLASS="PARAMETER"
1381 ><I
1382 >kernel oplocks</I
1383 ></TT
1384 ></A
1385 ></P
1386 ></LI
1387 ><LI
1388 ><P
1389 ><A
1390 HREF="#LANMANAUTH"
1391 ><TT
1392 CLASS="PARAMETER"
1393 ><I
1394 >lanman auth</I
1395 ></TT
1396 ></A
1397 ></P
1398 ></LI
1399 ><LI
1400 ><P
1401 ><A
1402 HREF="#LMANNOUNCE"
1403 ><TT
1404 CLASS="PARAMETER"
1405 ><I
1406 >lm announce</I
1407 ></TT
1408 ></A
1409 ></P
1410 ></LI
1411 ><LI
1412 ><P
1413 ><A
1414 HREF="#LMINTERVAL"
1415 ><TT
1416 CLASS="PARAMETER"
1417 ><I
1418 >lm interval</I
1419 ></TT
1420 ></A
1421 ></P
1422 ></LI
1423 ><LI
1424 ><P
1425 ><A
1426 HREF="#LOADPRINTERS"
1427 ><TT
1428 CLASS="PARAMETER"
1429 ><I
1430 >load printers</I
1431 ></TT
1432 ></A
1433 ></P
1434 ></LI
1435 ><LI
1436 ><P
1437 ><A
1438 HREF="#LOCALMASTER"
1439 ><TT
1440 CLASS="PARAMETER"
1441 ><I
1442 >local master</I
1443 ></TT
1444 ></A
1445 ></P
1446 ></LI
1447 ><LI
1448 ><P
1449 ><A
1450 HREF="#LOCKDIR"
1451 ><TT
1452 CLASS="PARAMETER"
1453 ><I
1454 >lock dir</I
1455 ></TT
1456 ></A
1457 ></P
1458 ></LI
1459 ><LI
1460 ><P
1461 ><A
1462 HREF="#LOCKDIRECTORY"
1463 ><TT
1464 CLASS="PARAMETER"
1465 ><I
1466 >lock directory</I
1467 ></TT
1468 ></A
1469 ></P
1470 ></LI
1471 ><LI
1472 ><P
1473 ><A
1474 HREF="#LOGFILE"
1475 ><TT
1476 CLASS="PARAMETER"
1477 ><I
1478 >log file</I
1479 ></TT
1480 ></A
1481 ></P
1482 ></LI
1483 ><LI
1484 ><P
1485 ><A
1486 HREF="#LOGLEVEL"
1487 ><TT
1488 CLASS="PARAMETER"
1489 ><I
1490 >log level</I
1491 ></TT
1492 ></A
1493 ></P
1494 ></LI
1495 ><LI
1496 ><P
1497 ><A
1498 HREF="#LOGONDRIVE"
1499 ><TT
1500 CLASS="PARAMETER"
1501 ><I
1502 >logon drive</I
1503 ></TT
1504 ></A
1505 ></P
1506 ></LI
1507 ><LI
1508 ><P
1509 ><A
1510 HREF="#LOGONHOME"
1511 ><TT
1512 CLASS="PARAMETER"
1513 ><I
1514 >logon home</I
1515 ></TT
1516 ></A
1517 ></P
1518 ></LI
1519 ><LI
1520 ><P
1521 ><A
1522 HREF="#LOGONPATH"
1523 ><TT
1524 CLASS="PARAMETER"
1525 ><I
1526 >logon path</I
1527 ></TT
1528 ></A
1529 ></P
1530 ></LI
1531 ><LI
1532 ><P
1533 ><A
1534 HREF="#LOGONSCRIPT"
1535 ><TT
1536 CLASS="PARAMETER"
1537 ><I
1538 >logon script</I
1539 ></TT
1540 ></A
1541 ></P
1542 ></LI
1543 ><LI
1544 ><P
1545 ><A
1546 HREF="#LPQCACHETIME"
1547 ><TT
1548 CLASS="PARAMETER"
1549 ><I
1550 >lpq cache time</I
1551 ></TT
1552 ></A
1553 ></P
1554 ></LI
1555 ><LI
1556 ><P
1557 ><A
1558 HREF="#MACHINEPASSWORDTIMEOUT"
1559 ><TT
1560 CLASS="PARAMETER"
1561 ><I
1562 >machine password timeout</I
1563 ></TT
1564 ></A
1565 ></P
1566 ></LI
1567 ><LI
1568 ><P
1569 ><A
1570 HREF="#MANGLEDSTACK"
1571 ><TT
1572 CLASS="PARAMETER"
1573 ><I
1574 >mangled stack</I
1575 ></TT
1576 ></A
1577 ></P
1578 ></LI
1579 ><LI
1580 ><P
1581 ><A
1582 HREF="#MAPTOGUEST"
1583 ><TT
1584 CLASS="PARAMETER"
1585 ><I
1586 >map to guest</I
1587 ></TT
1588 ></A
1589 ></P
1590 ></LI
1591 ><LI
1592 ><P
1593 ><A
1594 HREF="#MAXDISKSIZE"
1595 ><TT
1596 CLASS="PARAMETER"
1597 ><I
1598 >max disk size</I
1599 ></TT
1600 ></A
1601 ></P
1602 ></LI
1603 ><LI
1604 ><P
1605 ><A
1606 HREF="#MAXLOGSIZE"
1607 ><TT
1608 CLASS="PARAMETER"
1609 ><I
1610 >max log size</I
1611 ></TT
1612 ></A
1613 ></P
1614 ></LI
1615 ><LI
1616 ><P
1617 ><A
1618 HREF="#MAXMUX"
1619 ><TT
1620 CLASS="PARAMETER"
1621 ><I
1622 >max mux</I
1623 ></TT
1624 ></A
1625 ></P
1626 ></LI
1627 ><LI
1628 ><P
1629 ><A
1630 HREF="#MAXOPENFILES"
1631 ><TT
1632 CLASS="PARAMETER"
1633 ><I
1634 >max open files</I
1635 ></TT
1636 ></A
1637 ></P
1638 ></LI
1639 ><LI
1640 ><P
1641 ><A
1642 HREF="#MAXPROTOCOL"
1643 ><TT
1644 CLASS="PARAMETER"
1645 ><I
1646 >max protocol</I
1647 ></TT
1648 ></A
1649 ></P
1650 ></LI
1651 ><LI
1652 ><P
1653 ><A
1654 HREF="#MAXSMBDPROCESSES"
1655 ><TT
1656 CLASS="PARAMETER"
1657 ><I
1658 >max smbd processes</I
1659 ></TT
1660 ></A
1661 ></P
1662 ></LI
1663 ><LI
1664 ><P
1665 ><A
1666 HREF="#MAXTTL"
1667 ><TT
1668 CLASS="PARAMETER"
1669 ><I
1670 >max ttl</I
1671 ></TT
1672 ></A
1673 ></P
1674 ></LI
1675 ><LI
1676 ><P
1677 ><A
1678 HREF="#MAXWINSTTL"
1679 ><TT
1680 CLASS="PARAMETER"
1681 ><I
1682 >max wins ttl</I
1683 ></TT
1684 ></A
1685 ></P
1686 ></LI
1687 ><LI
1688 ><P
1689 ><A
1690 HREF="#MAXXMIT"
1691 ><TT
1692 CLASS="PARAMETER"
1693 ><I
1694 >max xmit</I
1695 ></TT
1696 ></A
1697 ></P
1698 ></LI
1699 ><LI
1700 ><P
1701 ><A
1702 HREF="#MESSAGECOMMAND"
1703 ><TT
1704 CLASS="PARAMETER"
1705 ><I
1706 >message command</I
1707 ></TT
1708 ></A
1709 ></P
1710 ></LI
1711 ><LI
1712 ><P
1713 ><A
1714 HREF="#MINPASSWDLENGTH"
1715 ><TT
1716 CLASS="PARAMETER"
1717 ><I
1718 >min passwd length</I
1719 ></TT
1720 ></A
1721 ></P
1722 ></LI
1723 ><LI
1724 ><P
1725 ><A
1726 HREF="#MINPASSWORDLENGTH"
1727 ><TT
1728 CLASS="PARAMETER"
1729 ><I
1730 >min password length</I
1731 ></TT
1732 ></A
1733 ></P
1734 ></LI
1735 ><LI
1736 ><P
1737 ><A
1738 HREF="#MINPROTOCOL"
1739 ><TT
1740 CLASS="PARAMETER"
1741 ><I
1742 >min protocol</I
1743 ></TT
1744 ></A
1745 ></P
1746 ></LI
1747 ><LI
1748 ><P
1749 ><A
1750 HREF="#MINWINSTTL"
1751 ><TT
1752 CLASS="PARAMETER"
1753 ><I
1754 >min wins ttl</I
1755 ></TT
1756 ></A
1757 ></P
1758 ></LI
1759 ><LI
1760 ><P
1761 ><A
1762 HREF="#NAMERESOLVEORDER"
1763 ><TT
1764 CLASS="PARAMETER"
1765 ><I
1766 >name resolve order</I
1767 ></TT
1768 ></A
1769 ></P
1770 ></LI
1771 ><LI
1772 ><P
1773 ><A
1774 HREF="#NETBIOSALIASES"
1775 ><TT
1776 CLASS="PARAMETER"
1777 ><I
1778 >netbios aliases</I
1779 ></TT
1780 ></A
1781 ></P
1782 ></LI
1783 ><LI
1784 ><P
1785 ><A
1786 HREF="#NETBIOSNAME"
1787 ><TT
1788 CLASS="PARAMETER"
1789 ><I
1790 >netbios name</I
1791 ></TT
1792 ></A
1793 ></P
1794 ></LI
1795 ><LI
1796 ><P
1797 ><A
1798 HREF="#NETBIOSSCOPE"
1799 ><TT
1800 CLASS="PARAMETER"
1801 ><I
1802 >netbios scope</I
1803 ></TT
1804 ></A
1805 ></P
1806 ></LI
1807 ><LI
1808 ><P
1809 ><A
1810 HREF="#NISHOMEDIR"
1811 ><TT
1812 CLASS="PARAMETER"
1813 ><I
1814 >nis homedir</I
1815 ></TT
1816 ></A
1817 ></P
1818 ></LI
1819 ><LI
1820 ><P
1821 ><A
1822 HREF="#NTACLSUPPORT"
1823 ><TT
1824 CLASS="PARAMETER"
1825 ><I
1826 >nt acl support</I
1827 ></TT
1828 ></A
1829 ></P
1830 ></LI
1831 ><LI
1832 ><P
1833 ><A
1834 HREF="#NTPIPESUPPORT"
1835 ><TT
1836 CLASS="PARAMETER"
1837 ><I
1838 >nt pipe support</I
1839 ></TT
1840 ></A
1841 ></P
1842 ></LI
1843 ><LI
1844 ><P
1845 ><A
1846 HREF="#NTSMBSUPPORT"
1847 ><TT
1848 CLASS="PARAMETER"
1849 ><I
1850 >nt smb support</I
1851 ></TT
1852 ></A
1853 ></P
1854 ></LI
1855 ><LI
1856 ><P
1857 ><A
1858 HREF="#NULLPASSWORDS"
1859 ><TT
1860 CLASS="PARAMETER"
1861 ><I
1862 >null passwords</I
1863 ></TT
1864 ></A
1865 ></P
1866 ></LI
1867 ><LI
1868 ><P
1869 ><A
1870 HREF="#OBEYPAMRESTRICTIONS"
1871 ><TT
1872 CLASS="PARAMETER"
1873 ><I
1874 >obey pam restrictions</I
1875 ></TT
1876 ></A
1877 ></P
1878 ></LI
1879 ><LI
1880 ><P
1881 ><A
1882 HREF="#OPLOCKBREAKWAITTIME"
1883 ><TT
1884 CLASS="PARAMETER"
1885 ><I
1886 >oplock break wait time</I
1887 ></TT
1888 ></A
1889 ></P
1890 ></LI
1891 ><LI
1892 ><P
1893 ><A
1894 HREF="#OSLEVEL"
1895 ><TT
1896 CLASS="PARAMETER"
1897 ><I
1898 >os level</I
1899 ></TT
1900 ></A
1901 ></P
1902 ></LI
1903 ><LI
1904 ><P
1905 ><A
1906 HREF="#OS2DRIVERMAP"
1907 ><TT
1908 CLASS="PARAMETER"
1909 ><I
1910 >os2 driver map</I
1911 ></TT
1912 ></A
1913 ></P
1914 ></LI
1915 ><LI
1916 ><P
1917 ><A
1918 HREF="#PAMPASSWORDCHANGE"
1919 ><TT
1920 CLASS="PARAMETER"
1921 ><I
1922 >pam password change</I
1923 ></TT
1924 ></A
1925 ></P
1926 ></LI
1927 ><LI
1928 ><P
1929 ><A
1930 HREF="#PANICACTION"
1931 ><TT
1932 CLASS="PARAMETER"
1933 ><I
1934 >panic action</I
1935 ></TT
1936 ></A
1937 ></P
1938 ></LI
1939 ><LI
1940 ><P
1941 ><A
1942 HREF="#PASSWDCHAT"
1943 ><TT
1944 CLASS="PARAMETER"
1945 ><I
1946 >passwd chat</I
1947 ></TT
1948 ></A
1949 ></P
1950 ></LI
1951 ><LI
1952 ><P
1953 ><A
1954 HREF="#PASSWDCHATDEBUG"
1955 ><TT
1956 CLASS="PARAMETER"
1957 ><I
1958 >passwd chat debug</I
1959 ></TT
1960 ></A
1961 ></P
1962 ></LI
1963 ><LI
1964 ><P
1965 ><A
1966 HREF="#PASSWDPROGRAM"
1967 ><TT
1968 CLASS="PARAMETER"
1969 ><I
1970 >passwd program</I
1971 ></TT
1972 ></A
1973 ></P
1974 ></LI
1975 ><LI
1976 ><P
1977 ><A
1978 HREF="#PASSWORDLEVEL"
1979 ><TT
1980 CLASS="PARAMETER"
1981 ><I
1982 >password level</I
1983 ></TT
1984 ></A
1985 ></P
1986 ></LI
1987 ><LI
1988 ><P
1989 ><A
1990 HREF="#PASSWORDSERVER"
1991 ><TT
1992 CLASS="PARAMETER"
1993 ><I
1994 >password server</I
1995 ></TT
1996 ></A
1997 ></P
1998 ></LI
1999 ><LI
2000 ><P
2001 ><A
2002 HREF="#PREFEREDMASTER"
2003 ><TT
2004 CLASS="PARAMETER"
2005 ><I
2006 >prefered master</I
2007 ></TT
2008 ></A
2009 ></P
2010 ></LI
2011 ><LI
2012 ><P
2013 ><A
2014 HREF="#PREFERREDMASTER"
2015 ><TT
2016 CLASS="PARAMETER"
2017 ><I
2018 >preferred master</I
2019 ></TT
2020 ></A
2021 ></P
2022 ></LI
2023 ><LI
2024 ><P
2025 ><A
2026 HREF="#PRELOAD"
2027 ><TT
2028 CLASS="PARAMETER"
2029 ><I
2030 >preload</I
2031 ></TT
2032 ></A
2033 ></P
2034 ></LI
2035 ><LI
2036 ><P
2037 ><A
2038 HREF="#PRINTCAP"
2039 ><TT
2040 CLASS="PARAMETER"
2041 ><I
2042 >printcap</I
2043 ></TT
2044 ></A
2045 ></P
2046 ></LI
2047 ><LI
2048 ><P
2049 ><A
2050 HREF="#PRINTCAPNAME"
2051 ><TT
2052 CLASS="PARAMETER"
2053 ><I
2054 >printcap name</I
2055 ></TT
2056 ></A
2057 ></P
2058 ></LI
2059 ><LI
2060 ><P
2061 ><A
2062 HREF="#PRINTERDRIVERFILE"
2063 ><TT
2064 CLASS="PARAMETER"
2065 ><I
2066 >printer driver file</I
2067 ></TT
2068 ></A
2069 ></P
2070 ></LI
2071 ><LI
2072 ><P
2073 ><A
2074 HREF="#PROTOCOL"
2075 ><TT
2076 CLASS="PARAMETER"
2077 ><I
2078 >protocol</I
2079 ></TT
2080 ></A
2081 ></P
2082 ></LI
2083 ><LI
2084 ><P
2085 ><A
2086 HREF="#READBMPX"
2087 ><TT
2088 CLASS="PARAMETER"
2089 ><I
2090 >read bmpx</I
2091 ></TT
2092 ></A
2093 ></P
2094 ></LI
2095 ><LI
2096 ><P
2097 ><A
2098 HREF="#READRAW"
2099 ><TT
2100 CLASS="PARAMETER"
2101 ><I
2102 >read raw</I
2103 ></TT
2104 ></A
2105 ></P
2106 ></LI
2107 ><LI
2108 ><P
2109 ><A
2110 HREF="#READSIZE"
2111 ><TT
2112 CLASS="PARAMETER"
2113 ><I
2114 >read size</I
2115 ></TT
2116 ></A
2117 ></P
2118 ></LI
2119 ><LI
2120 ><P
2121 ><A
2122 HREF="#REMOTEANNOUNCE"
2123 ><TT
2124 CLASS="PARAMETER"
2125 ><I
2126 >remote announce</I
2127 ></TT
2128 ></A
2129 ></P
2130 ></LI
2131 ><LI
2132 ><P
2133 ><A
2134 HREF="#REMOTEBROWSESYNC"
2135 ><TT
2136 CLASS="PARAMETER"
2137 ><I
2138 >remote browse sync</I
2139 ></TT
2140 ></A
2141 ></P
2142 ></LI
2143 ><LI
2144 ><P
2145 ><A
2146 HREF="#RESTRICTANONYMOUS"
2147 ><TT
2148 CLASS="PARAMETER"
2149 ><I
2150 >restrict anonymous</I
2151 ></TT
2152 ></A
2153 ></P
2154 ></LI
2155 ><LI
2156 ><P
2157 ><A
2158 HREF="#ROOT"
2159 ><TT
2160 CLASS="PARAMETER"
2161 ><I
2162 >root</I
2163 ></TT
2164 ></A
2165 ></P
2166 ></LI
2167 ><LI
2168 ><P
2169 ><A
2170 HREF="#ROOTDIR"
2171 ><TT
2172 CLASS="PARAMETER"
2173 ><I
2174 >root dir</I
2175 ></TT
2176 ></A
2177 ></P
2178 ></LI
2179 ><LI
2180 ><P
2181 ><A
2182 HREF="#ROOTDIRECTORY"
2183 ><TT
2184 CLASS="PARAMETER"
2185 ><I
2186 >root directory</I
2187 ></TT
2188 ></A
2189 ></P
2190 ></LI
2191 ><LI
2192 ><P
2193 ><A
2194 HREF="#SECURITY"
2195 ><TT
2196 CLASS="PARAMETER"
2197 ><I
2198 >security</I
2199 ></TT
2200 ></A
2201 ></P
2202 ></LI
2203 ><LI
2204 ><P
2205 ><A
2206 HREF="#SERVERSTRING"
2207 ><TT
2208 CLASS="PARAMETER"
2209 ><I
2210 >server string</I
2211 ></TT
2212 ></A
2213 ></P
2214 ></LI
2215 ><LI
2216 ><P
2217 ><A
2218 HREF="#SHOWADDPRINTERWIZARD"
2219 ><TT
2220 CLASS="PARAMETER"
2221 ><I
2222 >show add printer wizard</I
2223 ></TT
2224 ></A
2225 ></P
2226 ></LI
2227 ><LI
2228 ><P
2229 ><A
2230 HREF="#SMBPASSWDFILE"
2231 ><TT
2232 CLASS="PARAMETER"
2233 ><I
2234 >smb passwd file</I
2235 ></TT
2236 ></A
2237 ></P
2238 ></LI
2239 ><LI
2240 ><P
2241 ><A
2242 HREF="#SOCKETADDRESS"
2243 ><TT
2244 CLASS="PARAMETER"
2245 ><I
2246 >socket address</I
2247 ></TT
2248 ></A
2249 ></P
2250 ></LI
2251 ><LI
2252 ><P
2253 ><A
2254 HREF="#SOCKETOPTIONS"
2255 ><TT
2256 CLASS="PARAMETER"
2257 ><I
2258 >socket options</I
2259 ></TT
2260 ></A
2261 ></P
2262 ></LI
2263 ><LI
2264 ><P
2265 ><A
2266 HREF="#SOURCEENVIRONMENT"
2267 ><TT
2268 CLASS="PARAMETER"
2269 ><I
2270 >source environment</I
2271 ></TT
2272 ></A
2273 ></P
2274 ></LI
2275 ><LI
2276 ><P
2277 ><A
2278 HREF="#SSL"
2279 ><TT
2280 CLASS="PARAMETER"
2281 ><I
2282 >ssl</I
2283 ></TT
2284 ></A
2285 ></P
2286 ></LI
2287 ><LI
2288 ><P
2289 ><A
2290 HREF="#SSLCACERTDIR"
2291 ><TT
2292 CLASS="PARAMETER"
2293 ><I
2294 >ssl CA certDir</I
2295 ></TT
2296 ></A
2297 ></P
2298 ></LI
2299 ><LI
2300 ><P
2301 ><A
2302 HREF="#SSLCACERTFILE"
2303 ><TT
2304 CLASS="PARAMETER"
2305 ><I
2306 >ssl CA certFile</I
2307 ></TT
2308 ></A
2309 ></P
2310 ></LI
2311 ><LI
2312 ><P
2313 ><A
2314 HREF="#SSLCIPHERS"
2315 ><TT
2316 CLASS="PARAMETER"
2317 ><I
2318 >ssl ciphers</I
2319 ></TT
2320 ></A
2321 ></P
2322 ></LI
2323 ><LI
2324 ><P
2325 ><A
2326 HREF="#SSLCLIENTCERT"
2327 ><TT
2328 CLASS="PARAMETER"
2329 ><I
2330 >ssl client cert</I
2331 ></TT
2332 ></A
2333 ></P
2334 ></LI
2335 ><LI
2336 ><P
2337 ><A
2338 HREF="#SSLCLIENTKEY"
2339 ><TT
2340 CLASS="PARAMETER"
2341 ><I
2342 >ssl client key</I
2343 ></TT
2344 ></A
2345 ></P
2346 ></LI
2347 ><LI
2348 ><P
2349 ><A
2350 HREF="#SSLCOMPATIBILITY"
2351 ><TT
2352 CLASS="PARAMETER"
2353 ><I
2354 >ssl compatibility</I
2355 ></TT
2356 ></A
2357 ></P
2358 ></LI
2359 ><LI
2360 ><P
2361 ><A
2362 HREF="#SSLHOSTS"
2363 ><TT
2364 CLASS="PARAMETER"
2365 ><I
2366 >ssl hosts</I
2367 ></TT
2368 ></A
2369 ></P
2370 ></LI
2371 ><LI
2372 ><P
2373 ><A
2374 HREF="#SSLHOSTSRESIGN"
2375 ><TT
2376 CLASS="PARAMETER"
2377 ><I
2378 >ssl hosts resign</I
2379 ></TT
2380 ></A
2381 ></P
2382 ></LI
2383 ><LI
2384 ><P
2385 ><A
2386 HREF="#SSLREQUIRECLIENTCERT"
2387 ><TT
2388 CLASS="PARAMETER"
2389 ><I
2390 >ssl require clientcert</I
2391 ></TT
2392 ></A
2393 ></P
2394 ></LI
2395 ><LI
2396 ><P
2397 ><A
2398 HREF="#SSLREQUIRESERVERCERT"
2399 ><TT
2400 CLASS="PARAMETER"
2401 ><I
2402 >ssl require servercert</I
2403 ></TT
2404 ></A
2405 ></P
2406 ></LI
2407 ><LI
2408 ><P
2409 ><A
2410 HREF="#SSLSERVERCERT"
2411 ><TT
2412 CLASS="PARAMETER"
2413 ><I
2414 >ssl server cert</I
2415 ></TT
2416 ></A
2417 ></P
2418 ></LI
2419 ><LI
2420 ><P
2421 ><A
2422 HREF="#SSLSERVERKEY"
2423 ><TT
2424 CLASS="PARAMETER"
2425 ><I
2426 >ssl server key</I
2427 ></TT
2428 ></A
2429 ></P
2430 ></LI
2431 ><LI
2432 ><P
2433 ><A
2434 HREF="#SSLVERSION"
2435 ><TT
2436 CLASS="PARAMETER"
2437 ><I
2438 >ssl version</I
2439 ></TT
2440 ></A
2441 ></P
2442 ></LI
2443 ><LI
2444 ><P
2445 ><A
2446 HREF="#STATCACHE"
2447 ><TT
2448 CLASS="PARAMETER"
2449 ><I
2450 >stat cache</I
2451 ></TT
2452 ></A
2453 ></P
2454 ></LI
2455 ><LI
2456 ><P
2457 ><A
2458 HREF="#STATCACHESIZE"
2459 ><TT
2460 CLASS="PARAMETER"
2461 ><I
2462 >stat cache size</I
2463 ></TT
2464 ></A
2465 ></P
2466 ></LI
2467 ><LI
2468 ><P
2469 ><A
2470 HREF="#STRIPDOT"
2471 ><TT
2472 CLASS="PARAMETER"
2473 ><I
2474 >strip dot</I
2475 ></TT
2476 ></A
2477 ></P
2478 ></LI
2479 ><LI
2480 ><P
2481 ><A
2482 HREF="#SYSLOG"
2483 ><TT
2484 CLASS="PARAMETER"
2485 ><I
2486 >syslog</I
2487 ></TT
2488 ></A
2489 ></P
2490 ></LI
2491 ><LI
2492 ><P
2493 ><A
2494 HREF="#SYSLOGONLY"
2495 ><TT
2496 CLASS="PARAMETER"
2497 ><I
2498 >syslog only</I
2499 ></TT
2500 ></A
2501 ></P
2502 ></LI
2503 ><LI
2504 ><P
2505 ><A
2506 HREF="#TEMPLATEHOMEDIR"
2507 ><TT
2508 CLASS="PARAMETER"
2509 ><I
2510 >template homedir</I
2511 ></TT
2512 ></A
2513 ></P
2514 ></LI
2515 ><LI
2516 ><P
2517 ><A
2518 HREF="#TEMPLATESHELL"
2519 ><TT
2520 CLASS="PARAMETER"
2521 ><I
2522 >template shell</I
2523 ></TT
2524 ></A
2525 ></P
2526 ></LI
2527 ><LI
2528 ><P
2529 ><A
2530 HREF="#TIMEOFFSET"
2531 ><TT
2532 CLASS="PARAMETER"
2533 ><I
2534 >time offset</I
2535 ></TT
2536 ></A
2537 ></P
2538 ></LI
2539 ><LI
2540 ><P
2541 ><A
2542 HREF="#TIMESERVER"
2543 ><TT
2544 CLASS="PARAMETER"
2545 ><I
2546 >time server</I
2547 ></TT
2548 ></A
2549 ></P
2550 ></LI
2551 ><LI
2552 ><P
2553 ><A
2554 HREF="#TIMESTAMPLOGS"
2555 ><TT
2556 CLASS="PARAMETER"
2557 ><I
2558 >timestamp logs</I
2559 ></TT
2560 ></A
2561 ></P
2562 ></LI
2563 ><LI
2564 ><P
2565 ><A
2566 HREF="#TOTALPRINTJOBS"
2567 ><TT
2568 CLASS="PARAMETER"
2569 ><I
2570 >total print jobs</I
2571 ></TT
2572 ></A
2573 ></P
2574 ></LI
2575 ><LI
2576 ><P
2577 ><A
2578 HREF="#UNIXPASSWORDSYNC"
2579 ><TT
2580 CLASS="PARAMETER"
2581 ><I
2582 >unix password sync</I
2583 ></TT
2584 ></A
2585 ></P
2586 ></LI
2587 ><LI
2588 ><P
2589 ><A
2590 HREF="#UPDATEENCRYPTED"
2591 ><TT
2592 CLASS="PARAMETER"
2593 ><I
2594 >update encrypted</I
2595 ></TT
2596 ></A
2597 ></P
2598 ></LI
2599 ><LI
2600 ><P
2601 ><A
2602 HREF="#USERHOSTS"
2603 ><TT
2604 CLASS="PARAMETER"
2605 ><I
2606 >use rhosts</I
2607 ></TT
2608 ></A
2609 ></P
2610 ></LI
2611 ><LI
2612 ><P
2613 ><A
2614 HREF="#USERNAMELEVEL"
2615 ><TT
2616 CLASS="PARAMETER"
2617 ><I
2618 >username level</I
2619 ></TT
2620 ></A
2621 ></P
2622 ></LI
2623 ><LI
2624 ><P
2625 ><A
2626 HREF="#USERNAMEMAP"
2627 ><TT
2628 CLASS="PARAMETER"
2629 ><I
2630 >username map</I
2631 ></TT
2632 ></A
2633 ></P
2634 ></LI
2635 ><LI
2636 ><P
2637 ><A
2638 HREF="#UTMPDIRECTORY"
2639 ><TT
2640 CLASS="PARAMETER"
2641 ><I
2642 >utmp directory</I
2643 ></TT
2644 ></A
2645 ></P
2646 ></LI
2647 ><LI
2648 ><P
2649 ><A
2650 HREF="#VALIDCHARS"
2651 ><TT
2652 CLASS="PARAMETER"
2653 ><I
2654 >valid chars</I
2655 ></TT
2656 ></A
2657 ></P
2658 ></LI
2659 ><LI
2660 ><P
2661 ><A
2662 HREF="#WINBINDCACHETIME"
2663 ><TT
2664 CLASS="PARAMETER"
2665 ><I
2666 >winbind cache time</I
2667 ></TT
2668 ></A
2669 ></P
2670 ></LI
2671 ><LI
2672 ><P
2673 ><A
2674 HREF="#WINBINDGID"
2675 ><TT
2676 CLASS="PARAMETER"
2677 ><I
2678 >winbind gid</I
2679 ></TT
2680 ></A
2681 ></P
2682 ></LI
2683 ><LI
2684 ><P
2685 ><A
2686 HREF="#WINBINDSEPARATOR"
2687 ><TT
2688 CLASS="PARAMETER"
2689 ><I
2690 >winbind separator</I
2691 ></TT
2692 ></A
2693 ></P
2694 ></LI
2695 ><LI
2696 ><P
2697 ><A
2698 HREF="#WINBINDUID"
2699 ><TT
2700 CLASS="PARAMETER"
2701 ><I
2702 >winbind uid</I
2703 ></TT
2704 ></A
2705 ></P
2706 ></LI
2707 ><LI
2708 ><P
2709 ><A
2710 HREF="#WINSHOOK"
2711 ><TT
2712 CLASS="PARAMETER"
2713 ><I
2714 >wins hook</I
2715 ></TT
2716 ></A
2717 ></P
2718 ></LI
2719 ><LI
2720 ><P
2721 ><A
2722 HREF="#WINSPROXY"
2723 ><TT
2724 CLASS="PARAMETER"
2725 ><I
2726 >wins proxy</I
2727 ></TT
2728 ></A
2729 ></P
2730 ></LI
2731 ><LI
2732 ><P
2733 ><A
2734 HREF="#WINSSERVER"
2735 ><TT
2736 CLASS="PARAMETER"
2737 ><I
2738 >wins server</I
2739 ></TT
2740 ></A
2741 ></P
2742 ></LI
2743 ><LI
2744 ><P
2745 ><A
2746 HREF="#WINSSUPPORT"
2747 ><TT
2748 CLASS="PARAMETER"
2749 ><I
2750 >wins support</I
2751 ></TT
2752 ></A
2753 ></P
2754 ></LI
2755 ><LI
2756 ><P
2757 ><A
2758 HREF="#WORKGROUP"
2759 ><TT
2760 CLASS="PARAMETER"
2761 ><I
2762 >workgroup</I
2763 ></TT
2764 ></A
2765 ></P
2766 ></LI
2767 ><LI
2768 ><P
2769 ><A
2770 HREF="#WRITERAW"
2771 ><TT
2772 CLASS="PARAMETER"
2773 ><I
2774 >write raw</I
2775 ></TT
2776 ></A
2777 ></P
2778 ></LI
2779 ></UL
2780 ></DIV
2781 ><DIV
2782 CLASS="REFSECT1"
2783 ><A
2784 NAME="AEN897"
2785 ></A
2786 ><H2
2787 >COMPLETE LIST OF SERVICE PARAMETERS</H2
2788 ><P
2789 >Here is a list of all service parameters. See the section on
2790         each parameter for details. Note that some are synonyms.</P
2791 ><P
2792 ></P
2793 ><UL
2794 ><LI
2795 ><P
2796 ><A
2797 HREF="#ADMINUSERS"
2798 ><TT
2799 CLASS="PARAMETER"
2800 ><I
2801 >admin users</I
2802 ></TT
2803 ></A
2804 ></P
2805 ></LI
2806 ><LI
2807 ><P
2808 ><A
2809 HREF="#ALLOWHOSTS"
2810 ><TT
2811 CLASS="PARAMETER"
2812 ><I
2813 >allow hosts</I
2814 ></TT
2815 ></A
2816 ></P
2817 ></LI
2818 ><LI
2819 ><P
2820 ><A
2821 HREF="#AVAILABLE"
2822 ><TT
2823 CLASS="PARAMETER"
2824 ><I
2825 >available</I
2826 ></TT
2827 ></A
2828 ></P
2829 ></LI
2830 ><LI
2831 ><P
2832 ><A
2833 HREF="#BLOCKINGLOCKS"
2834 ><TT
2835 CLASS="PARAMETER"
2836 ><I
2837 >blocking locks</I
2838 ></TT
2839 ></A
2840 ></P
2841 ></LI
2842 ><LI
2843 ><P
2844 ><A
2845 HREF="#BROWSABLE"
2846 ><TT
2847 CLASS="PARAMETER"
2848 ><I
2849 >browsable</I
2850 ></TT
2851 ></A
2852 ></P
2853 ></LI
2854 ><LI
2855 ><P
2856 ><A
2857 HREF="#BROWSEABLE"
2858 ><TT
2859 CLASS="PARAMETER"
2860 ><I
2861 >browseable</I
2862 ></TT
2863 ></A
2864 ></P
2865 ></LI
2866 ><LI
2867 ><P
2868 ><A
2869 HREF="#CASESENSITIVE"
2870 ><TT
2871 CLASS="PARAMETER"
2872 ><I
2873 >case sensitive</I
2874 ></TT
2875 ></A
2876 ></P
2877 ></LI
2878 ><LI
2879 ><P
2880 ><A
2881 HREF="#CASESIGNAMES"
2882 ><TT
2883 CLASS="PARAMETER"
2884 ><I
2885 >casesignames</I
2886 ></TT
2887 ></A
2888 ></P
2889 ></LI
2890 ><LI
2891 ><P
2892 ><A
2893 HREF="#COMMENT"
2894 ><TT
2895 CLASS="PARAMETER"
2896 ><I
2897 >comment</I
2898 ></TT
2899 ></A
2900 ></P
2901 ></LI
2902 ><LI
2903 ><P
2904 ><A
2905 HREF="#COPY"
2906 ><TT
2907 CLASS="PARAMETER"
2908 ><I
2909 >copy</I
2910 ></TT
2911 ></A
2912 ></P
2913 ></LI
2914 ><LI
2915 ><P
2916 ><A
2917 HREF="#CREATEMASK"
2918 ><TT
2919 CLASS="PARAMETER"
2920 ><I
2921 >create mask</I
2922 ></TT
2923 ></A
2924 ></P
2925 ></LI
2926 ><LI
2927 ><P
2928 ><A
2929 HREF="#CREATEMODE"
2930 ><TT
2931 CLASS="PARAMETER"
2932 ><I
2933 >create mode</I
2934 ></TT
2935 ></A
2936 ></P
2937 ></LI
2938 ><LI
2939 ><P
2940 ><A
2941 HREF="#DEFAULTCASE"
2942 ><TT
2943 CLASS="PARAMETER"
2944 ><I
2945 >default case</I
2946 ></TT
2947 ></A
2948 ></P
2949 ></LI
2950 ><LI
2951 ><P
2952 ><A
2953 HREF="#DELETEREADONLY"
2954 ><TT
2955 CLASS="PARAMETER"
2956 ><I
2957 >delete readonly</I
2958 ></TT
2959 ></A
2960 ></P
2961 ></LI
2962 ><LI
2963 ><P
2964 ><A
2965 HREF="#DELETEVETOFILES"
2966 ><TT
2967 CLASS="PARAMETER"
2968 ><I
2969 >delete veto files</I
2970 ></TT
2971 ></A
2972 ></P
2973 ></LI
2974 ><LI
2975 ><P
2976 ><A
2977 HREF="#DENYHOSTS"
2978 ><TT
2979 CLASS="PARAMETER"
2980 ><I
2981 >deny hosts</I
2982 ></TT
2983 ></A
2984 ></P
2985 ></LI
2986 ><LI
2987 ><P
2988 ><A
2989 HREF="#DIRECTORY"
2990 ><TT
2991 CLASS="PARAMETER"
2992 ><I
2993 >directory</I
2994 ></TT
2995 ></A
2996 ></P
2997 ></LI
2998 ><LI
2999 ><P
3000 ><A
3001 HREF="#DIRECTORYMASK"
3002 ><TT
3003 CLASS="PARAMETER"
3004 ><I
3005 >directory mask</I
3006 ></TT
3007 ></A
3008 ></P
3009 ></LI
3010 ><LI
3011 ><P
3012 ><A
3013 HREF="#DIRECTORYMODE"
3014 ><TT
3015 CLASS="PARAMETER"
3016 ><I
3017 >directory mode</I
3018 ></TT
3019 ></A
3020 ></P
3021 ></LI
3022 ><LI
3023 ><P
3024 ><A
3025 HREF="#DIRECTORYSECURITYMASK"
3026 ><TT
3027 CLASS="PARAMETER"
3028 ><I
3029 >directory security mask</I
3030 ></TT
3031 ></A
3032 ></P
3033 ></LI
3034 ><LI
3035 ><P
3036 ><A
3037 HREF="#DONTDESCEND"
3038 ><TT
3039 CLASS="PARAMETER"
3040 ><I
3041 >dont descend</I
3042 ></TT
3043 ></A
3044 ></P
3045 ></LI
3046 ><LI
3047 ><P
3048 ><A
3049 HREF="#DOSFILEMODE"
3050 ><TT
3051 CLASS="PARAMETER"
3052 ><I
3053 >dos filemode</I
3054 ></TT
3055 ></A
3056 ></P
3057 ></LI
3058 ><LI
3059 ><P
3060 ><A
3061 HREF="#DOSFILETIMERESOLUTION"
3062 ><TT
3063 CLASS="PARAMETER"
3064 ><I
3065 >dos filetime resolution</I
3066 ></TT
3067 ></A
3068 ></P
3069 ></LI
3070 ><LI
3071 ><P
3072 ><A
3073 HREF="#DOSFILETIMES"
3074 ><TT
3075 CLASS="PARAMETER"
3076 ><I
3077 >dos filetimes</I
3078 ></TT
3079 ></A
3080 ></P
3081 ></LI
3082 ><LI
3083 ><P
3084 ><A
3085 HREF="#EXEC"
3086 ><TT
3087 CLASS="PARAMETER"
3088 ><I
3089 >exec</I
3090 ></TT
3091 ></A
3092 ></P
3093 ></LI
3094 ><LI
3095 ><P
3096 ><A
3097 HREF="#FAKEDIRECTORYCREATETIMES"
3098 ><TT
3099 CLASS="PARAMETER"
3100 ><I
3101 >fake directory create times</I
3102 ></TT
3103 ></A
3104 ></P
3105 ></LI
3106 ><LI
3107 ><P
3108 ><A
3109 HREF="#FAKEOPLOCKS"
3110 ><TT
3111 CLASS="PARAMETER"
3112 ><I
3113 >fake oplocks</I
3114 ></TT
3115 ></A
3116 ></P
3117 ></LI
3118 ><LI
3119 ><P
3120 ><A
3121 HREF="#FOLLOWSYMLINKS"
3122 ><TT
3123 CLASS="PARAMETER"
3124 ><I
3125 >follow symlinks</I
3126 ></TT
3127 ></A
3128 ></P
3129 ></LI
3130 ><LI
3131 ><P
3132 ><A
3133 HREF="#FORCECREATEMODE"
3134 ><TT
3135 CLASS="PARAMETER"
3136 ><I
3137 >force create mode</I
3138 ></TT
3139 ></A
3140 ></P
3141 ></LI
3142 ><LI
3143 ><P
3144 ><A
3145 HREF="#FORCEDIRECTORYMODE"
3146 ><TT
3147 CLASS="PARAMETER"
3148 ><I
3149 >force directory mode</I
3150 ></TT
3151 ></A
3152 ></P
3153 ></LI
3154 ><LI
3155 ><P
3156 ><A
3157 HREF="#FORCEDIRECTORYSECURITYMODE"
3158 ><TT
3159 CLASS="PARAMETER"
3160 ><I
3161 >force directory security mode</I
3162 ></TT
3163 ></A
3164 ></P
3165 ></LI
3166 ><LI
3167 ><P
3168 ><A
3169 HREF="#FORCEGROUP"
3170 ><TT
3171 CLASS="PARAMETER"
3172 ><I
3173 >force group</I
3174 ></TT
3175 ></A
3176 ></P
3177 ></LI
3178 ><LI
3179 ><P
3180 ><A
3181 HREF="#FORCESECURITYMODE"
3182 ><TT
3183 CLASS="PARAMETER"
3184 ><I
3185 >force security mode</I
3186 ></TT
3187 ></A
3188 ></P
3189 ></LI
3190 ><LI
3191 ><P
3192 ><A
3193 HREF="#FORCEUSER"
3194 ><TT
3195 CLASS="PARAMETER"
3196 ><I
3197 >force user</I
3198 ></TT
3199 ></A
3200 ></P
3201 ></LI
3202 ><LI
3203 ><P
3204 ><A
3205 HREF="#FSTYPE"
3206 ><TT
3207 CLASS="PARAMETER"
3208 ><I
3209 >fstype</I
3210 ></TT
3211 ></A
3212 ></P
3213 ></LI
3214 ><LI
3215 ><P
3216 ><A
3217 HREF="#GROUP"
3218 ><TT
3219 CLASS="PARAMETER"
3220 ><I
3221 >group</I
3222 ></TT
3223 ></A
3224 ></P
3225 ></LI
3226 ><LI
3227 ><P
3228 ><A
3229 HREF="#GUESTACCOUNT"
3230 ><TT
3231 CLASS="PARAMETER"
3232 ><I
3233 >guest account</I
3234 ></TT
3235 ></A
3236 ></P
3237 ></LI
3238 ><LI
3239 ><P
3240 ><A
3241 HREF="#GUESTOK"
3242 ><TT
3243 CLASS="PARAMETER"
3244 ><I
3245 >guest ok</I
3246 ></TT
3247 ></A
3248 ></P
3249 ></LI
3250 ><LI
3251 ><P
3252 ><A
3253 HREF="#GUESTONLY"
3254 ><TT
3255 CLASS="PARAMETER"
3256 ><I
3257 >guest only</I
3258 ></TT
3259 ></A
3260 ></P
3261 ></LI
3262 ><LI
3263 ><P
3264 ><A
3265 HREF="#HIDEDOTFILES"
3266 ><TT
3267 CLASS="PARAMETER"
3268 ><I
3269 >hide dot files</I
3270 ></TT
3271 ></A
3272 ></P
3273 ></LI
3274 ><LI
3275 ><P
3276 ><A
3277 HREF="#HIDEFILES"
3278 ><TT
3279 CLASS="PARAMETER"
3280 ><I
3281 >hide files</I
3282 ></TT
3283 ></A
3284 ></P
3285 ></LI
3286 ><LI
3287 ><P
3288 ><A
3289 HREF="#HOSTSALLOW"
3290 ><TT
3291 CLASS="PARAMETER"
3292 ><I
3293 >hosts allow</I
3294 ></TT
3295 ></A
3296 ></P
3297 ></LI
3298 ><LI
3299 ><P
3300 ><A
3301 HREF="#HOSTSDENY"
3302 ><TT
3303 CLASS="PARAMETER"
3304 ><I
3305 >hosts deny</I
3306 ></TT
3307 ></A
3308 ></P
3309 ></LI
3310 ><LI
3311 ><P
3312 ><A
3313 HREF="#INCLUDE"
3314 ><TT
3315 CLASS="PARAMETER"
3316 ><I
3317 >include</I
3318 ></TT
3319 ></A
3320 ></P
3321 ></LI
3322 ><LI
3323 ><P
3324 ><A
3325 HREF="#INHERITPERMISSIONS"
3326 ><TT
3327 CLASS="PARAMETER"
3328 ><I
3329 >inherit permissions</I
3330 ></TT
3331 ></A
3332 ></P
3333 ></LI
3334 ><LI
3335 ><P
3336 ><A
3337 HREF="#INVALIDUSERS"
3338 ><TT
3339 CLASS="PARAMETER"
3340 ><I
3341 >invalid users</I
3342 ></TT
3343 ></A
3344 ></P
3345 ></LI
3346 ><LI
3347 ><P
3348 ><A
3349 HREF="#LEVEL2OPLOCKS"
3350 ><TT
3351 CLASS="PARAMETER"
3352 ><I
3353 >level2 oplocks</I
3354 ></TT
3355 ></A
3356 ></P
3357 ></LI
3358 ><LI
3359 ><P
3360 ><A
3361 HREF="#LOCKING"
3362 ><TT
3363 CLASS="PARAMETER"
3364 ><I
3365 >locking</I
3366 ></TT
3367 ></A
3368 ></P
3369 ></LI
3370 ><LI
3371 ><P
3372 ><A
3373 HREF="#LPPAUSECOMMAND"
3374 ><TT
3375 CLASS="PARAMETER"
3376 ><I
3377 >lppause command</I
3378 ></TT
3379 ></A
3380 ></P
3381 ></LI
3382 ><LI
3383 ><P
3384 ><A
3385 HREF="#LPQCOMMAND"
3386 ><TT
3387 CLASS="PARAMETER"
3388 ><I
3389 >lpq command</I
3390 ></TT
3391 ></A
3392 ></P
3393 ></LI
3394 ><LI
3395 ><P
3396 ><A
3397 HREF="#LPRESUMECOMMAND"
3398 ><TT
3399 CLASS="PARAMETER"
3400 ><I
3401 >lpresume command</I
3402 ></TT
3403 ></A
3404 ></P
3405 ></LI
3406 ><LI
3407 ><P
3408 ><A
3409 HREF="#LPRMCOMMAND"
3410 ><TT
3411 CLASS="PARAMETER"
3412 ><I
3413 >lprm command</I
3414 ></TT
3415 ></A
3416 ></P
3417 ></LI
3418 ><LI
3419 ><P
3420 ><A
3421 HREF="#MAGICOUTPUT"
3422 ><TT
3423 CLASS="PARAMETER"
3424 ><I
3425 >magic output</I
3426 ></TT
3427 ></A
3428 ></P
3429 ></LI
3430 ><LI
3431 ><P
3432 ><A
3433 HREF="#MAGICSCRIPT"
3434 ><TT
3435 CLASS="PARAMETER"
3436 ><I
3437 >magic script</I
3438 ></TT
3439 ></A
3440 ></P
3441 ></LI
3442 ><LI
3443 ><P
3444 ><A
3445 HREF="#MANGLECASE"
3446 ><TT
3447 CLASS="PARAMETER"
3448 ><I
3449 >mangle case</I
3450 ></TT
3451 ></A
3452 ></P
3453 ></LI
3454 ><LI
3455 ><P
3456 ><A
3457 HREF="#MANGLEDMAP"
3458 ><TT
3459 CLASS="PARAMETER"
3460 ><I
3461 >mangled map</I
3462 ></TT
3463 ></A
3464 ></P
3465 ></LI
3466 ><LI
3467 ><P
3468 ><A
3469 HREF="#MANGLEDNAMES"
3470 ><TT
3471 CLASS="PARAMETER"
3472 ><I
3473 >mangled names</I
3474 ></TT
3475 ></A
3476 ></P
3477 ></LI
3478 ><LI
3479 ><P
3480 ><A
3481 HREF="#MANGLINGCHAR"
3482 ><TT
3483 CLASS="PARAMETER"
3484 ><I
3485 >mangling char</I
3486 ></TT
3487 ></A
3488 ></P
3489 ></LI
3490 ><LI
3491 ><P
3492 ><A
3493 HREF="#MAPARCHIVE"
3494 ><TT
3495 CLASS="PARAMETER"
3496 ><I
3497 >map archive</I
3498 ></TT
3499 ></A
3500 ></P
3501 ></LI
3502 ><LI
3503 ><P
3504 ><A
3505 HREF="#MAPHIDDEN"
3506 ><TT
3507 CLASS="PARAMETER"
3508 ><I
3509 >map hidden</I
3510 ></TT
3511 ></A
3512 ></P
3513 ></LI
3514 ><LI
3515 ><P
3516 ><A
3517 HREF="#MAPSYSTEM"
3518 ><TT
3519 CLASS="PARAMETER"
3520 ><I
3521 >map system</I
3522 ></TT
3523 ></A
3524 ></P
3525 ></LI
3526 ><LI
3527 ><P
3528 ><A
3529 HREF="#MAXCONNECTIONS"
3530 ><TT
3531 CLASS="PARAMETER"
3532 ><I
3533 >max connections</I
3534 ></TT
3535 ></A
3536 ></P
3537 ></LI
3538 ><LI
3539 ><P
3540 ><A
3541 HREF="#MAXPRINTJOBS"
3542 ><TT
3543 CLASS="PARAMETER"
3544 ><I
3545 >max print jobs</I
3546 ></TT
3547 ></A
3548 ></P
3549 ></LI
3550 ><LI
3551 ><P
3552 ><A
3553 HREF="#MINPRINTSPACE"
3554 ><TT
3555 CLASS="PARAMETER"
3556 ><I
3557 >min print space</I
3558 ></TT
3559 ></A
3560 ></P
3561 ></LI
3562 ><LI
3563 ><P
3564 ><A
3565 HREF="#MSDFSROOT"
3566 ><TT
3567 CLASS="PARAMETER"
3568 ><I
3569 >msdfs root</I
3570 ></TT
3571 ></A
3572 ></P
3573 ></LI
3574 ><LI
3575 ><P
3576 ><A
3577 HREF="#ONLYGUEST"
3578 ><TT
3579 CLASS="PARAMETER"
3580 ><I
3581 >only guest</I
3582 ></TT
3583 ></A
3584 ></P
3585 ></LI
3586 ><LI
3587 ><P
3588 ><A
3589 HREF="#ONLYUSER"
3590 ><TT
3591 CLASS="PARAMETER"
3592 ><I
3593 >only user</I
3594 ></TT
3595 ></A
3596 ></P
3597 ></LI
3598 ><LI
3599 ><P
3600 ><A
3601 HREF="#OPLOCKCONTENTIONLIMIT"
3602 ><TT
3603 CLASS="PARAMETER"
3604 ><I
3605 >oplock contention limit</I
3606 ></TT
3607 ></A
3608 ></P
3609 ></LI
3610 ><LI
3611 ><P
3612 ><A
3613 HREF="#OPLOCKS"
3614 ><TT
3615 CLASS="PARAMETER"
3616 ><I
3617 >oplocks</I
3618 ></TT
3619 ></A
3620 ></P
3621 ></LI
3622 ><LI
3623 ><P
3624 ><A
3625 HREF="#PATH"
3626 ><TT
3627 CLASS="PARAMETER"
3628 ><I
3629 >path</I
3630 ></TT
3631 ></A
3632 ></P
3633 ></LI
3634 ><LI
3635 ><P
3636 ><A
3637 HREF="#POSIXLOCKING"
3638 ><TT
3639 CLASS="PARAMETER"
3640 ><I
3641 >posix locking</I
3642 ></TT
3643 ></A
3644 ></P
3645 ></LI
3646 ><LI
3647 ><P
3648 ><A
3649 HREF="#POSTEXEC"
3650 ><TT
3651 CLASS="PARAMETER"
3652 ><I
3653 >postexec</I
3654 ></TT
3655 ></A
3656 ></P
3657 ></LI
3658 ><LI
3659 ><P
3660 ><A
3661 HREF="#POSTSCRIPT"
3662 ><TT
3663 CLASS="PARAMETER"
3664 ><I
3665 >postscript</I
3666 ></TT
3667 ></A
3668 ></P
3669 ></LI
3670 ><LI
3671 ><P
3672 ><A
3673 HREF="#PREEXEC"
3674 ><TT
3675 CLASS="PARAMETER"
3676 ><I
3677 >preexec</I
3678 ></TT
3679 ></A
3680 ></P
3681 ></LI
3682 ><LI
3683 ><P
3684 ><A
3685 HREF="#PREEXECCLOSE"
3686 ><TT
3687 CLASS="PARAMETER"
3688 ><I
3689 >preexec close</I
3690 ></TT
3691 ></A
3692 ></P
3693 ></LI
3694 ><LI
3695 ><P
3696 ><A
3697 HREF="#PRESERVECASE"
3698 ><TT
3699 CLASS="PARAMETER"
3700 ><I
3701 >preserve case</I
3702 ></TT
3703 ></A
3704 ></P
3705 ></LI
3706 ><LI
3707 ><P
3708 ><A
3709 HREF="#PRINTCOMMAND"
3710 ><TT
3711 CLASS="PARAMETER"
3712 ><I
3713 >print command</I
3714 ></TT
3715 ></A
3716 ></P
3717 ></LI
3718 ><LI
3719 ><P
3720 ><A
3721 HREF="#PRINTOK"
3722 ><TT
3723 CLASS="PARAMETER"
3724 ><I
3725 >print ok</I
3726 ></TT
3727 ></A
3728 ></P
3729 ></LI
3730 ><LI
3731 ><P
3732 ><A
3733 HREF="#PRINTABLE"
3734 ><TT
3735 CLASS="PARAMETER"
3736 ><I
3737 >printable</I
3738 ></TT
3739 ></A
3740 ></P
3741 ></LI
3742 ><LI
3743 ><P
3744 ><A
3745 HREF="#PRINTER"
3746 ><TT
3747 CLASS="PARAMETER"
3748 ><I
3749 >printer</I
3750 ></TT
3751 ></A
3752 ></P
3753 ></LI
3754 ><LI
3755 ><P
3756 ><A
3757 HREF="#PRINTERADMIN"
3758 ><TT
3759 CLASS="PARAMETER"
3760 ><I
3761 >printer admin</I
3762 ></TT
3763 ></A
3764 ></P
3765 ></LI
3766 ><LI
3767 ><P
3768 ><A
3769 HREF="#PRINTERDRIVER"
3770 ><TT
3771 CLASS="PARAMETER"
3772 ><I
3773 >printer driver</I
3774 ></TT
3775 ></A
3776 ></P
3777 ></LI
3778 ><LI
3779 ><P
3780 ><A
3781 HREF="#PRINTERDRIVERLOCATION"
3782 ><TT
3783 CLASS="PARAMETER"
3784 ><I
3785 >printer driver location</I
3786 ></TT
3787 ></A
3788 ></P
3789 ></LI
3790 ><LI
3791 ><P
3792 ><A
3793 HREF="#PRINTERNAME"
3794 ><TT
3795 CLASS="PARAMETER"
3796 ><I
3797 >printer name</I
3798 ></TT
3799 ></A
3800 ></P
3801 ></LI
3802 ><LI
3803 ><P
3804 ><A
3805 HREF="#PRINTING"
3806 ><TT
3807 CLASS="PARAMETER"
3808 ><I
3809 >printing</I
3810 ></TT
3811 ></A
3812 ></P
3813 ></LI
3814 ><LI
3815 ><P
3816 ><A
3817 HREF="#PUBLIC"
3818 ><TT
3819 CLASS="PARAMETER"
3820 ><I
3821 >public</I
3822 ></TT
3823 ></A
3824 ></P
3825 ></LI
3826 ><LI
3827 ><P
3828 ><A
3829 HREF="#QUEUEPAUSECOMMAND"
3830 ><TT
3831 CLASS="PARAMETER"
3832 ><I
3833 >queuepause command</I
3834 ></TT
3835 ></A
3836 ></P
3837 ></LI
3838 ><LI
3839 ><P
3840 ><A
3841 HREF="#QUEUERESUMECOMMAND"
3842 ><TT
3843 CLASS="PARAMETER"
3844 ><I
3845 >queueresume command</I
3846 ></TT
3847 ></A
3848 ></P
3849 ></LI
3850 ><LI
3851 ><P
3852 ><A
3853 HREF="#READLIST"
3854 ><TT
3855 CLASS="PARAMETER"
3856 ><I
3857 >read list</I
3858 ></TT
3859 ></A
3860 ></P
3861 ></LI
3862 ><LI
3863 ><P
3864 ><A
3865 HREF="#READONLY"
3866 ><TT
3867 CLASS="PARAMETER"
3868 ><I
3869 >read only</I
3870 ></TT
3871 ></A
3872 ></P
3873 ></LI
3874 ><LI
3875 ><P
3876 ><A
3877 HREF="#RESTRICTACLWITHMASK"
3878 ><TT
3879 CLASS="PARAMETER"
3880 ><I
3881 >restrict acl with mask</I
3882 ></TT
3883 ></A
3884 ></P
3885 ></LI
3886 ><LI
3887 ><P
3888 ><A
3889 HREF="#ROOTPOSTEXEC"
3890 ><TT
3891 CLASS="PARAMETER"
3892 ><I
3893 >root postexec</I
3894 ></TT
3895 ></A
3896 ></P
3897 ></LI
3898 ><LI
3899 ><P
3900 ><A
3901 HREF="#ROOTPREEXEC"
3902 ><TT
3903 CLASS="PARAMETER"
3904 ><I
3905 >root preexec</I
3906 ></TT
3907 ></A
3908 ></P
3909 ></LI
3910 ><LI
3911 ><P
3912 ><A
3913 HREF="#ROOTPREEXECCLOSE"
3914 ><TT
3915 CLASS="PARAMETER"
3916 ><I
3917 >root preexec close</I
3918 ></TT
3919 ></A
3920 ></P
3921 ></LI
3922 ><LI
3923 ><P
3924 ><A
3925 HREF="#SECURITYMASK"
3926 ><TT
3927 CLASS="PARAMETER"
3928 ><I
3929 >security mask</I
3930 ></TT
3931 ></A
3932 ></P
3933 ></LI
3934 ><LI
3935 ><P
3936 ><A
3937 HREF="#SETDIRECTORY"
3938 ><TT
3939 CLASS="PARAMETER"
3940 ><I
3941 >set directory</I
3942 ></TT
3943 ></A
3944 ></P
3945 ></LI
3946 ><LI
3947 ><P
3948 ><A
3949 HREF="#SHAREMODES"
3950 ><TT
3951 CLASS="PARAMETER"
3952 ><I
3953 >share modes</I
3954 ></TT
3955 ></A
3956 ></P
3957 ></LI
3958 ><LI
3959 ><P
3960 ><A
3961 HREF="#SHORTPRESERVECASE"
3962 ><TT
3963 CLASS="PARAMETER"
3964 ><I
3965 >short preserve case</I
3966 ></TT
3967 ></A
3968 ></P
3969 ></LI
3970 ><LI
3971 ><P
3972 ><A
3973 HREF="#STATUS"
3974 ><TT
3975 CLASS="PARAMETER"
3976 ><I
3977 >status</I
3978 ></TT
3979 ></A
3980 ></P
3981 ></LI
3982 ><LI
3983 ><P
3984 ><A
3985 HREF="#STRICTLOCKING"
3986 ><TT
3987 CLASS="PARAMETER"
3988 ><I
3989 >strict locking</I
3990 ></TT
3991 ></A
3992 ></P
3993 ></LI
3994 ><LI
3995 ><P
3996 ><A
3997 HREF="#STRICTSYNC"
3998 ><TT
3999 CLASS="PARAMETER"
4000 ><I
4001 >strict sync</I
4002 ></TT
4003 ></A
4004 ></P
4005 ></LI
4006 ><LI
4007 ><P
4008 ><A
4009 HREF="#SYNCALWAYS"
4010 ><TT
4011 CLASS="PARAMETER"
4012 ><I
4013 >sync always</I
4014 ></TT
4015 ></A
4016 ></P
4017 ></LI
4018 ><LI
4019 ><P
4020 ><A
4021 HREF="#USER"
4022 ><TT
4023 CLASS="PARAMETER"
4024 ><I
4025 >user</I
4026 ></TT
4027 ></A
4028 ></P
4029 ></LI
4030 ><LI
4031 ><P
4032 ><A
4033 HREF="#USERNAME"
4034 ><TT
4035 CLASS="PARAMETER"
4036 ><I
4037 >username</I
4038 ></TT
4039 ></A
4040 ></P
4041 ></LI
4042 ><LI
4043 ><P
4044 ><A
4045 HREF="#USERS"
4046 ><TT
4047 CLASS="PARAMETER"
4048 ><I
4049 >users</I
4050 ></TT
4051 ></A
4052 ></P
4053 ></LI
4054 ><LI
4055 ><P
4056 ><A
4057 HREF="#UTMP"
4058 ><TT
4059 CLASS="PARAMETER"
4060 ><I
4061 >utmp</I
4062 ></TT
4063 ></A
4064 ></P
4065 ></LI
4066 ><LI
4067 ><P
4068 ><A
4069 HREF="#VALIDUSERS"
4070 ><TT
4071 CLASS="PARAMETER"
4072 ><I
4073 >valid users</I
4074 ></TT
4075 ></A
4076 ></P
4077 ></LI
4078 ><LI
4079 ><P
4080 ><A
4081 HREF="#VETOFILES"
4082 ><TT
4083 CLASS="PARAMETER"
4084 ><I
4085 >veto files</I
4086 ></TT
4087 ></A
4088 ></P
4089 ></LI
4090 ><LI
4091 ><P
4092 ><A
4093 HREF="#VETOOPLOCKFILES"
4094 ><TT
4095 CLASS="PARAMETER"
4096 ><I
4097 >veto oplock files</I
4098 ></TT
4099 ></A
4100 ></P
4101 ></LI
4102 ><LI
4103 ><P
4104 ><A
4105 HREF="#VFSOBJECT"
4106 ><TT
4107 CLASS="PARAMETER"
4108 ><I
4109 >vfs object</I
4110 ></TT
4111 ></A
4112 ></P
4113 ></LI
4114 ><LI
4115 ><P
4116 ><A
4117 HREF="#VFSOPTIONS"
4118 ><TT
4119 CLASS="PARAMETER"
4120 ><I
4121 >vfs options</I
4122 ></TT
4123 ></A
4124 ></P
4125 ></LI
4126 ><LI
4127 ><P
4128 ><A
4129 HREF="#VOLUME"
4130 ><TT
4131 CLASS="PARAMETER"
4132 ><I
4133 >volume</I
4134 ></TT
4135 ></A
4136 ></P
4137 ></LI
4138 ><LI
4139 ><P
4140 ><A
4141 HREF="#WIDELINKS"
4142 ><TT
4143 CLASS="PARAMETER"
4144 ><I
4145 >wide links</I
4146 ></TT
4147 ></A
4148 ></P
4149 ></LI
4150 ><LI
4151 ><P
4152 ><A
4153 HREF="#WRITABLE"
4154 ><TT
4155 CLASS="PARAMETER"
4156 ><I
4157 >writable</I
4158 ></TT
4159 ></A
4160 ></P
4161 ></LI
4162 ><LI
4163 ><P
4164 ><A
4165 HREF="#WRITECACHESIZE"
4166 ><TT
4167 CLASS="PARAMETER"
4168 ><I
4169 >write cache size</I
4170 ></TT
4171 ></A
4172 ></P
4173 ></LI
4174 ><LI
4175 ><P
4176 ><A
4177 HREF="#WRITELIST"
4178 ><TT
4179 CLASS="PARAMETER"
4180 ><I
4181 >write list</I
4182 ></TT
4183 ></A
4184 ></P
4185 ></LI
4186 ><LI
4187 ><P
4188 ><A
4189 HREF="#WRITEOK"
4190 ><TT
4191 CLASS="PARAMETER"
4192 ><I
4193 >write ok</I
4194 ></TT
4195 ></A
4196 ></P
4197 ></LI
4198 ><LI
4199 ><P
4200 ><A
4201 HREF="#WRITEABLE"
4202 ><TT
4203 CLASS="PARAMETER"
4204 ><I
4205 >writeable</I
4206 ></TT
4207 ></A
4208 ></P
4209 ></LI
4210 ></UL
4211 ></DIV
4212 ><DIV
4213 CLASS="REFSECT1"
4214 ><A
4215 NAME="AEN1373"
4216 ></A
4217 ><H2
4218 >EXPLANATION OF EACH PARAMETER</H2
4219 ><P
4220 ></P
4221 ><DIV
4222 CLASS="VARIABLELIST"
4223 ><DL
4224 ><DT
4225 ><A
4226 NAME="ADDPRINTERCOMMAND"
4227 ></A
4228 >add printer command (G)</DT
4229 ><DD
4230 ><P
4231 >With the introduction of MS-RPC based printing
4232                 support for Windows NT/2000 clients in Samba 2.2, The MS Add
4233                 Printer Wizard (APW) icon is now also available in the
4234                 "Printers..." folder displayed a share listing.  The APW
4235                 allows for printers to be add remotely to a Samba or Windows
4236                 NT/2000 print server.</P
4237 ><P
4238 >For a Samba host this means that the printer must be
4239                 physically added to underlying printing system.  The <TT
4240 CLASS="PARAMETER"
4241 ><I
4242 >add
4243                 printer command</I
4244 ></TT
4245 > defines a script to be run which
4246                 will perform the necessary operations for adding the printer
4247                 to the print system and to add the appropriate service definition
4248                 to the  <TT
4249 CLASS="FILENAME"
4250 >smb.conf</TT
4251 > file in order that it can be
4252                 shared by <A
4253 HREF="smbd.8.html"
4254 TARGET="_top"
4255 ><B
4256 CLASS="COMMAND"
4257 >smbd(8)</B
4258 >
4259                 </A
4260 >.</P
4261 ><P
4262 >The <TT
4263 CLASS="PARAMETER"
4264 ><I
4265 >add printer command</I
4266 ></TT
4267 > is
4268                 automatically invoked with the following parameter (in
4269                 order:</P
4270 ><P
4271 ></P
4272 ><UL
4273 ><LI
4274 ><P
4275 ><TT
4276 CLASS="PARAMETER"
4277 ><I
4278 >printer name</I
4279 ></TT
4280 ></P
4281 ></LI
4282 ><LI
4283 ><P
4284 ><TT
4285 CLASS="PARAMETER"
4286 ><I
4287 >share name</I
4288 ></TT
4289 ></P
4290 ></LI
4291 ><LI
4292 ><P
4293 ><TT
4294 CLASS="PARAMETER"
4295 ><I
4296 >port name</I
4297 ></TT
4298 ></P
4299 ></LI
4300 ><LI
4301 ><P
4302 ><TT
4303 CLASS="PARAMETER"
4304 ><I
4305 >driver name</I
4306 ></TT
4307 ></P
4308 ></LI
4309 ><LI
4310 ><P
4311 ><TT
4312 CLASS="PARAMETER"
4313 ><I
4314 >location</I
4315 ></TT
4316 ></P
4317 ></LI
4318 ><LI
4319 ><P
4320 ><TT
4321 CLASS="PARAMETER"
4322 ><I
4323 >Windows 9x driver location</I
4324 ></TT
4325 >
4326                         </P
4327 ></LI
4328 ></UL
4329 ><P
4330 >All parameters are filled in from the PRINTER_INFO_2 structure sent
4331                 by the Windows NT/2000 client with one exception.  The "Windows 9x
4332                 driver location" parameter is included for backwards compatibility
4333                 only.  The remaining fields in the structure are generated from answers
4334                 to the APW questions.</P
4335 ><P
4336 >Once the <TT
4337 CLASS="PARAMETER"
4338 ><I
4339 >add printer command</I
4340 ></TT
4341 > has
4342                 been executed, <B
4343 CLASS="COMMAND"
4344 >smbd</B
4345 > will reparse the <TT
4346 CLASS="FILENAME"
4347 >               smb.conf</TT
4348 > to determine if the share defined by the APW
4349                 exists.  If the sharename is still invalid, then <B
4350 CLASS="COMMAND"
4351 >smbd
4352                 </B
4353 > will return an ACCESS_DENIED error to the client.</P
4354 ><P
4355 >See also <A
4356 HREF="#DELETEPRINTERCOMMAND"
4357 ><TT
4358 CLASS="PARAMETER"
4359 ><I
4360 >               delete printer command</I
4361 ></TT
4362 ></A
4363 >, <A
4364 HREF="#PRINTING"
4365 ><TT
4366 CLASS="PARAMETER"
4367 ><I
4368 >printing</I
4369 ></TT
4370 ></A
4371 >,
4372                 <A
4373 HREF="#SHOWADDPRINTERWIZARD"
4374 ><TT
4375 CLASS="PARAMETER"
4376 ><I
4377 >show add
4378                 printer wizard</I
4379 ></TT
4380 ></A
4381 ></P
4382 ><P
4383 >Default: <EM
4384 >none</EM
4385 ></P
4386 ><P
4387 >Example: <B
4388 CLASS="COMMAND"
4389 >addprinter command = /usr/bin/addprinter
4390                 </B
4391 ></P
4392 ></DD
4393 ><DT
4394 ><A
4395 NAME="ADDSHARECOMMAND"
4396 ></A
4397 >add share command (G)</DT
4398 ><DD
4399 ><P
4400 >Samba 2.2.0 introduced the ability to dynamically
4401                 add and delete shares via the Windows NT 4.0 Server Manager.  The
4402                 <TT
4403 CLASS="PARAMETER"
4404 ><I
4405 >add share command</I
4406 ></TT
4407 > is used to define an
4408                 external program or script which will add a new service definition
4409                 to <TT
4410 CLASS="FILENAME"
4411 >smb.conf</TT
4412 >.  In order to successfully
4413                 execute the <TT
4414 CLASS="PARAMETER"
4415 ><I
4416 >add share command</I
4417 ></TT
4418 >, <B
4419 CLASS="COMMAND"
4420 >smbd</B
4421 >
4422                 requires that the administrator be connected using a root account (i.e.
4423                 uid == 0).
4424                 </P
4425 ><P
4426 >               When executed, <B
4427 CLASS="COMMAND"
4428 >smbd</B
4429 > will automatically invoke the
4430                 <TT
4431 CLASS="PARAMETER"
4432 ><I
4433 >add share command</I
4434 ></TT
4435 > with four parameters.
4436                 </P
4437 ><P
4438 ></P
4439 ><UL
4440 ><LI
4441 ><P
4442 ><TT
4443 CLASS="PARAMETER"
4444 ><I
4445 >configFile</I
4446 ></TT
4447 > - the location
4448                         of the global <TT
4449 CLASS="FILENAME"
4450 >smb.conf</TT
4451 > file.
4452                         </P
4453 ></LI
4454 ><LI
4455 ><P
4456 ><TT
4457 CLASS="PARAMETER"
4458 ><I
4459 >shareName</I
4460 ></TT
4461 > - the name of the new
4462                         share.
4463                         </P
4464 ></LI
4465 ><LI
4466 ><P
4467 ><TT
4468 CLASS="PARAMETER"
4469 ><I
4470 >pathName</I
4471 ></TT
4472 > - path to an **existing**
4473                         directory on disk.
4474                         </P
4475 ></LI
4476 ><LI
4477 ><P
4478 ><TT
4479 CLASS="PARAMETER"
4480 ><I
4481 >comment</I
4482 ></TT
4483 > - comment string to associate
4484                         with the new share.
4485                         </P
4486 ></LI
4487 ></UL
4488 ><P
4489 >               This parameter is only used for add file shares.  To add printer shares,
4490                 see the <A
4491 HREF="#ADDPRINTERCOMMAND"
4492 ><TT
4493 CLASS="PARAMETER"
4494 ><I
4495 >add printer
4496                 command</I
4497 ></TT
4498 ></A
4499 >.
4500                 </P
4501 ><P
4502 >               See also <A
4503 HREF="#CHANGESHARECOMMAND"
4504 ><TT
4505 CLASS="PARAMETER"
4506 ><I
4507 >change share
4508                 command</I
4509 ></TT
4510 ></A
4511 >, <A
4512 HREF="#DELETESHARECOMMAND"
4513 ><TT
4514 CLASS="PARAMETER"
4515 ><I
4516 >delete share
4517                 command</I
4518 ></TT
4519 ></A
4520 >.
4521                 </P
4522 ><P
4523 >Default: <EM
4524 >none</EM
4525 ></P
4526 ><P
4527 >Example: <B
4528 CLASS="COMMAND"
4529 >add share command = /usr/local/bin/addshare</B
4530 ></P
4531 ></DD
4532 ><DT
4533 ><A
4534 NAME="ADDUSERSCRIPT"
4535 ></A
4536 >add user script (G)</DT
4537 ><DD
4538 ><P
4539 >This is the full pathname to a script that will
4540                 be run <EM
4541 >AS ROOT</EM
4542 > by <A
4543 HREF="smbd.8.html"
4544 TARGET="_top"
4545 >smbd(8)
4546                 </A
4547 > under special circumstances described below.</P
4548 ><P
4549 >Normally, a Samba server requires that UNIX users are
4550                 created for all users accessing files on this server. For sites
4551                 that use Windows NT account databases as their primary user database
4552                 creating these users and keeping the user list in sync with the
4553                 Windows NT PDC is an onerous task. This option allows <A
4554 HREF="smbd.8.html"
4555 TARGET="_top"
4556 >smbd</A
4557 > to create the required UNIX users
4558                 <EM
4559 >ON DEMAND</EM
4560 > when a user accesses the Samba server.</P
4561 ><P
4562 >In order to use this option, <A
4563 HREF="smbd.8.html"
4564 TARGET="_top"
4565 >smbd</A
4566 >
4567                 must be set to <TT
4568 CLASS="PARAMETER"
4569 ><I
4570 >security=server</I
4571 ></TT
4572 > or <TT
4573 CLASS="PARAMETER"
4574 ><I
4575 >               security=domain</I
4576 ></TT
4577 > and <TT
4578 CLASS="PARAMETER"
4579 ><I
4580 >add user script</I
4581 ></TT
4582 >
4583                 must be set to a full pathname for a script that will create a UNIX
4584                 user given one argument of <TT
4585 CLASS="PARAMETER"
4586 ><I
4587 >%u</I
4588 ></TT
4589 >, which expands into
4590                 the UNIX user name to create.</P
4591 ><P
4592 >When the Windows user attempts to access the Samba server,
4593                 at login (session setup in the SMB protocol) time, <A
4594 HREF="smbd.8.html"
4595 TARGET="_top"
4596 >               smbd</A
4597 > contacts the <TT
4598 CLASS="PARAMETER"
4599 ><I
4600 >password server</I
4601 ></TT
4602 > and
4603                 attempts to authenticate the given user with the given password. If the
4604                 authentication succeeds then <B
4605 CLASS="COMMAND"
4606 >smbd</B
4607 >
4608                 attempts to find a UNIX user in the UNIX password database to map the
4609                 Windows user into. If this lookup fails, and <TT
4610 CLASS="PARAMETER"
4611 ><I
4612 >add user script
4613                 </I
4614 ></TT
4615 > is set then <B
4616 CLASS="COMMAND"
4617 >smbd</B
4618 > will
4619                 call the specified script <EM
4620 >AS ROOT</EM
4621 >, expanding
4622                 any <TT
4623 CLASS="PARAMETER"
4624 ><I
4625 >%u</I
4626 ></TT
4627 > argument to be the user name to create.</P
4628 ><P
4629 >If this script successfully creates the user then <B
4630 CLASS="COMMAND"
4631 >smbd
4632                 </B
4633 > will continue on as though the UNIX user
4634                 already existed. In this way, UNIX users are dynamically created to
4635                 match existing Windows NT accounts.</P
4636 ><P
4637 >See also <A
4638 HREF="#SECURITY"
4639 ><TT
4640 CLASS="PARAMETER"
4641 ><I
4642 >               security</I
4643 ></TT
4644 ></A
4645 >, <A
4646 HREF="#PASSWORDSERVER"
4647 >               <TT
4648 CLASS="PARAMETER"
4649 ><I
4650 >password server</I
4651 ></TT
4652 ></A
4653 >,
4654                 <A
4655 HREF="#DELETEUSERSCRIPT"
4656 ><TT
4657 CLASS="PARAMETER"
4658 ><I
4659 >delete user
4660                 script</I
4661 ></TT
4662 ></A
4663 >.</P
4664 ><P
4665 >Default: <B
4666 CLASS="COMMAND"
4667 >add user script = &#60;empty string&#62;
4668                 </B
4669 ></P
4670 ><P
4671 >Example: <B
4672 CLASS="COMMAND"
4673 >add user script = /usr/local/samba/bin/add_user
4674                 %u</B
4675 ></P
4676 ></DD
4677 ><DT
4678 ><A
4679 NAME="ADMINUSERS"
4680 ></A
4681 >admin users (S)</DT
4682 ><DD
4683 ><P
4684 >This is a list of users who will be granted
4685                 administrative privileges on the share. This means that they
4686                 will do all file operations as the super-user (root).</P
4687 ><P
4688 >You should use this option very carefully, as any user in
4689                 this list will be able to do anything they like on the share,
4690                 irrespective of file permissions.</P
4691 ><P
4692 >Default: <EM
4693 >no admin users</EM
4694 ></P
4695 ><P
4696 >Example: <B
4697 CLASS="COMMAND"
4698 >admin users = jason</B
4699 ></P
4700 ></DD
4701 ><DT
4702 ><A
4703 NAME="ALLOWHOSTS"
4704 ></A
4705 >allow hosts (S)</DT
4706 ><DD
4707 ><P
4708 >Synonym for <A
4709 HREF="#HOSTSALLOW"
4710 >               <TT
4711 CLASS="PARAMETER"
4712 ><I
4713 >hosts allow</I
4714 ></TT
4715 ></A
4716 >.</P
4717 ></DD
4718 ><DT
4719 ><A
4720 NAME="ALLOWTRUSTEDDOMAINS"
4721 ></A
4722 >allow trusted domains (G)</DT
4723 ><DD
4724 ><P
4725 >This option only takes effect when the <A
4726 HREF="#SECURITY"
4727 ><TT
4728 CLASS="PARAMETER"
4729 ><I
4730 >security</I
4731 ></TT
4732 ></A
4733 > option is set to
4734                 <TT
4735 CLASS="CONSTANT"
4736 >server</TT
4737 > or <TT
4738 CLASS="CONSTANT"
4739 >domain</TT
4740 >.
4741                 If it is set to no, then attempts to connect to a resource from
4742                 a domain or workgroup other than the one which smbd is running
4743                 in will fail, even if that domain is trusted by the remote server
4744                 doing the authentication.</P
4745 ><P
4746 >This is useful if you only want your Samba server to
4747                 serve resources to users in the domain it is a member of. As
4748                 an example, suppose that there are two domains DOMA and DOMB.  DOMB
4749                 is trusted by DOMA, which contains the Samba server.  Under normal
4750                 circumstances, a user with an account in DOMB can then access the
4751                 resources of a UNIX account with the same account name on the
4752                 Samba server even if they do not have an account in DOMA.  This
4753                 can make implementing a security boundary difficult.</P
4754 ><P
4755 >Default: <B
4756 CLASS="COMMAND"
4757 >allow trusted domains = yes</B
4758 ></P
4759 ></DD
4760 ><DT
4761 ><A
4762 NAME="ANNOUNCEAS"
4763 ></A
4764 >announce as (G)</DT
4765 ><DD
4766 ><P
4767 >This specifies what type of server
4768                 <A
4769 HREF="nmbd.8.html"
4770 TARGET="_top"
4771 ><B
4772 CLASS="COMMAND"
4773 >nmbd</B
4774 ></A
4775 >
4776                 will announce itself as, to a network neighborhood browse
4777                 list. By default this is set to Windows NT. The valid options
4778                 are : "NT Server" (which can also be written as "NT"),
4779                 "NT Workstation", "Win95" or "WfW" meaning Windows NT Server,
4780                 Windows NT Workstation, Windows 95 and Windows for Workgroups
4781                 respectively. Do not change this parameter unless you have a
4782                 specific need to stop Samba appearing as an NT server as this
4783                 may prevent Samba servers from participating as browser servers
4784                 correctly.</P
4785 ><P
4786 >Default: <B
4787 CLASS="COMMAND"
4788 >announce as = NT Server</B
4789 ></P
4790 ><P
4791 >Example: <B
4792 CLASS="COMMAND"
4793 >announce as = Win95</B
4794 ></P
4795 ></DD
4796 ><DT
4797 ><A
4798 NAME="ANNOUNCEVERSION"
4799 ></A
4800 >annouce version (G)</DT
4801 ><DD
4802 ><P
4803 >This specifies the major and minor version numbers
4804                 that nmbd will use when announcing itself as a server. The default
4805                 is 4.2.  Do not change this parameter unless you have a specific
4806                 need to set a Samba server to be a downlevel server.</P
4807 ><P
4808 >Default: <B
4809 CLASS="COMMAND"
4810 >announce version = 4.2</B
4811 ></P
4812 ><P
4813 >Example: <B
4814 CLASS="COMMAND"
4815 >announce version = 2.0</B
4816 ></P
4817 ></DD
4818 ><DT
4819 ><A
4820 NAME="AUTOSERVICES"
4821 ></A
4822 >auto services (G)</DT
4823 ><DD
4824 ><P
4825 >This is a synonym for the <A
4826 HREF="#PRELOAD"
4827 >               <TT
4828 CLASS="PARAMETER"
4829 ><I
4830 >preload</I
4831 ></TT
4832 ></A
4833 >.</P
4834 ></DD
4835 ><DT
4836 ><A
4837 NAME="AVAILABLE"
4838 ></A
4839 >available (S)</DT
4840 ><DD
4841 ><P
4842 >This parameter lets you "turn off" a service. If
4843                 <TT
4844 CLASS="PARAMETER"
4845 ><I
4846 >available = no</I
4847 ></TT
4848 >, then <EM
4849 >ALL</EM
4850 >
4851                 attempts to connect to the service will fail. Such failures are
4852                 logged.</P
4853 ><P
4854 >Default: <B
4855 CLASS="COMMAND"
4856 >available = yes</B
4857 ></P
4858 ></DD
4859 ><DT
4860 ><A
4861 NAME="BINDINTERFACESONLY"
4862 ></A
4863 >bind interfaces only (G)</DT
4864 ><DD
4865 ><P
4866 >This global parameter allows the Samba admin
4867                 to limit what interfaces on a machine will serve smb requests. If
4868                 affects file service <A
4869 HREF="smbd.8.html"
4870 TARGET="_top"
4871 >smbd(8)</A
4872 > and
4873                 name service <A
4874 HREF="nmbd.8.html"
4875 TARGET="_top"
4876 >nmbd(8)</A
4877 > in slightly
4878                 different ways.</P
4879 ><P
4880 >For name service it causes <B
4881 CLASS="COMMAND"
4882 >nmbd</B
4883 > to bind
4884                 to ports 137 and 138 on the interfaces listed in the <A
4885 HREF="#INTERFACES"
4886 >interfaces</A
4887 > parameter. <B
4888 CLASS="COMMAND"
4889 >nmbd
4890                 </B
4891 > also binds to the "all addresses" interface (0.0.0.0)
4892                 on ports 137 and 138 for the purposes of reading broadcast messages.
4893                 If this option is not set then <B
4894 CLASS="COMMAND"
4895 >nmbd</B
4896 > will service
4897                 name requests on all of these sockets. If <TT
4898 CLASS="PARAMETER"
4899 ><I
4900 >bind interfaces
4901                 only</I
4902 ></TT
4903 > is set then <B
4904 CLASS="COMMAND"
4905 >nmbd</B
4906 > will check the
4907                 source address of any packets coming in on the broadcast sockets
4908                 and discard any that don't match the broadcast addresses of the
4909                 interfaces in the <TT
4910 CLASS="PARAMETER"
4911 ><I
4912 >interfaces</I
4913 ></TT
4914 > parameter list.
4915                 As unicast packets are received on the other sockets it allows
4916                 <B
4917 CLASS="COMMAND"
4918 >nmbd</B
4919 > to refuse to serve names to machines that
4920                 send packets that arrive through any interfaces not listed in the
4921                 <TT
4922 CLASS="PARAMETER"
4923 ><I
4924 >interfaces</I
4925 ></TT
4926 > list.  IP Source address spoofing
4927                 does defeat this simple check, however so it must not be used
4928                 seriously as a security feature for <B
4929 CLASS="COMMAND"
4930 >nmbd</B
4931 >.</P
4932 ><P
4933 >For file service it causes <A
4934 HREF="smbd.8.html"
4935 TARGET="_top"
4936 >smbd(8)</A
4937 >
4938                 to bind only to the interface list given in the <A
4939 HREF="#INTERFACES"
4940 >               interfaces</A
4941 > parameter. This restricts the networks that
4942                 <B
4943 CLASS="COMMAND"
4944 >smbd</B
4945 > will serve to packets coming in those
4946                 interfaces.  Note that you should not use this parameter for machines
4947                 that are serving PPP or other intermittent or non-broadcast network
4948                 interfaces as it will not cope with non-permanent interfaces.</P
4949 ><P
4950 >If <TT
4951 CLASS="PARAMETER"
4952 ><I
4953 >bind interfaces only</I
4954 ></TT
4955 > is set then
4956                 unless the network address <EM
4957 >127.0.0.1</EM
4958 > is added
4959                 to the <TT
4960 CLASS="PARAMETER"
4961 ><I
4962 >interfaces</I
4963 ></TT
4964 > parameter list <A
4965 HREF="smbpasswd.8.html"
4966 TARGET="_top"
4967 ><B
4968 CLASS="COMMAND"
4969 >smbpasswd(8)</B
4970 ></A
4971 >
4972                 and <A
4973 HREF="swat.8.html"
4974 TARGET="_top"
4975 ><B
4976 CLASS="COMMAND"
4977 >swat(8)</B
4978 ></A
4979 > may
4980                 not work as expected due to the reasons covered below.</P
4981 ><P
4982 >To change a users SMB password, the <B
4983 CLASS="COMMAND"
4984 >smbpasswd</B
4985 >
4986                 by default connects to the <EM
4987 >localhost - 127.0.0.1</EM
4988 >
4989                 address as an SMB client to issue the password change request. If
4990                 <TT
4991 CLASS="PARAMETER"
4992 ><I
4993 >bind interfaces only</I
4994 ></TT
4995 > is set then unless the
4996                 network address <EM
4997 >127.0.0.1</EM
4998 > is added to the
4999                 <TT
5000 CLASS="PARAMETER"
5001 ><I
5002 >interfaces</I
5003 ></TT
5004 > parameter list then <B
5005 CLASS="COMMAND"
5006 >               smbpasswd</B
5007 > will fail to connect in it's default mode.
5008                 <B
5009 CLASS="COMMAND"
5010 >smbpasswd</B
5011 > can be forced to use the primary IP interface
5012                 of the local host by using its <A
5013 HREF="smbpasswd.8.html#minusr"
5014 TARGET="_top"
5015 >               <TT
5016 CLASS="PARAMETER"
5017 ><I
5018 >-r <TT
5019 CLASS="REPLACEABLE"
5020 ><I
5021 >remote machine</I
5022 ></TT
5023 ></I
5024 ></TT
5025 >
5026                 </A
5027 > parameter, with <TT
5028 CLASS="REPLACEABLE"
5029 ><I
5030 >remote machine</I
5031 ></TT
5032 > set
5033                 to the IP name of the primary interface of the local host.</P
5034 ><P
5035 >The <B
5036 CLASS="COMMAND"
5037 >swat</B
5038 > status page tries to connect with
5039                 <B
5040 CLASS="COMMAND"
5041 >smbd</B
5042 > and <B
5043 CLASS="COMMAND"
5044 >nmbd</B
5045 > at the address
5046                 <EM
5047 >127.0.0.1</EM
5048 > to determine if they are running.
5049                 Not adding <EM
5050 >127.0.0.1</EM
5051 >  will cause <B
5052 CLASS="COMMAND"
5053 >               smbd</B
5054 > and <B
5055 CLASS="COMMAND"
5056 >nmbd</B
5057 > to always show
5058                 "not running" even if they really are.  This can prevent <B
5059 CLASS="COMMAND"
5060 >               swat</B
5061 > from starting/stopping/restarting <B
5062 CLASS="COMMAND"
5063 >smbd</B
5064 >
5065                 and <B
5066 CLASS="COMMAND"
5067 >nmbd</B
5068 >.</P
5069 ><P
5070 >Default: <B
5071 CLASS="COMMAND"
5072 >bind interfaces only = no</B
5073 ></P
5074 ></DD
5075 ><DT
5076 ><A
5077 NAME="BLOCKINGLOCKS"
5078 ></A
5079 >blocking locks (S)</DT
5080 ><DD
5081 ><P
5082 >This parameter controls the behavior of <A
5083 HREF="smbd.8.html"
5084 TARGET="_top"
5085 >smbd(8)</A
5086 > when given a request by a client
5087                 to obtain a byte range lock on a region of an open file, and the
5088                 request has a time limit associated with it.</P
5089 ><P
5090 >If this parameter is set and the lock range requested
5091                 cannot be immediately satisfied, Samba 2.2 will internally
5092                 queue the lock request, and periodically attempt to obtain
5093                 the lock until the timeout period expires.</P
5094 ><P
5095 >If this parameter is set to <TT
5096 CLASS="CONSTANT"
5097 >False</TT
5098 >, then
5099                 Samba 2.2 will behave as previous versions of Samba would and
5100                 will fail the lock request immediately if the lock range
5101                 cannot be obtained.</P
5102 ><P
5103 >Default: <B
5104 CLASS="COMMAND"
5105 >blocking locks = yes</B
5106 ></P
5107 ></DD
5108 ><DT
5109 ><A
5110 NAME="BROWSABLE"
5111 ></A
5112 >browsable (S)</DT
5113 ><DD
5114 ><P
5115 >See the <A
5116 HREF="#BROWSEABLE"
5117 ><TT
5118 CLASS="PARAMETER"
5119 ><I
5120 >               browseable</I
5121 ></TT
5122 ></A
5123 >.</P
5124 ></DD
5125 ><DT
5126 ><A
5127 NAME="BROWSELIST"
5128 ></A
5129 >browse list (G)</DT
5130 ><DD
5131 ><P
5132 >This controls whether <A
5133 HREF="smbd.8.html"
5134 TARGET="_top"
5135 >               <B
5136 CLASS="COMMAND"
5137 >smbd(8)</B
5138 ></A
5139 > will serve a browse list to
5140                 a client doing a <B
5141 CLASS="COMMAND"
5142 >NetServerEnum</B
5143 > call. Normally
5144                 set to <TT
5145 CLASS="CONSTANT"
5146 >true</TT
5147 >. You should never need to change
5148                 this.</P
5149 ><P
5150 >Default: <B
5151 CLASS="COMMAND"
5152 >browse list = yes</B
5153 ></P
5154 ></DD
5155 ><DT
5156 ><A
5157 NAME="BROWSEABLE"
5158 ></A
5159 >browseable (S)</DT
5160 ><DD
5161 ><P
5162 >This controls whether this share is seen in
5163                 the list of available shares in a net view and in the browse list.</P
5164 ><P
5165 >Default: <B
5166 CLASS="COMMAND"
5167 >browseable = yes</B
5168 ></P
5169 ></DD
5170 ><DT
5171 ><A
5172 NAME="CASESENSITIVE"
5173 ></A
5174 >case sensitive (S)</DT
5175 ><DD
5176 ><P
5177 >See the discussion in the section <A
5178 HREF="#AEN201"
5179 >NAME MANGLING</A
5180 >.</P
5181 ><P
5182 >Default: <B
5183 CLASS="COMMAND"
5184 >case sensitive = no</B
5185 ></P
5186 ></DD
5187 ><DT
5188 ><A
5189 NAME="CASESIGNAMES"
5190 ></A
5191 >casesignames (S)</DT
5192 ><DD
5193 ><P
5194 >Synonym for <A
5195 HREF="#CASESENSITIVE"
5196 >case
5197                 sensitive</A
5198 >.</P
5199 ></DD
5200 ><DT
5201 ><A
5202 NAME="CHANGENOTIFYTIMEOUT"
5203 ></A
5204 >change notify timeout (G)</DT
5205 ><DD
5206 ><P
5207 >This SMB allows a client to tell a server to
5208                 "watch" a particular directory for any changes and only reply to
5209                 the SMB request when a change has occurred. Such constant scanning of
5210                 a directory is expensive under UNIX, hence an <A
5211 HREF="smbd.8.html"
5212 TARGET="_top"
5213 >               <B
5214 CLASS="COMMAND"
5215 >smbd(8)</B
5216 ></A
5217 > daemon only performs such a scan
5218                 on each requested directory once every <TT
5219 CLASS="PARAMETER"
5220 ><I
5221 >change notify
5222                 timeout</I
5223 ></TT
5224 > seconds.</P
5225 ><P
5226 >Default: <B
5227 CLASS="COMMAND"
5228 >change notify timeout = 60</B
5229 ></P
5230 ><P
5231 >Example: <B
5232 CLASS="COMMAND"
5233 >change notify timeout = 300</B
5234 ></P
5235 ><P
5236 >Would change the scan time to every 5 minutes.</P
5237 ></DD
5238 ><DT
5239 ><A
5240 NAME="CHANGESHARECOMMAND"
5241 ></A
5242 >change share command (G)</DT
5243 ><DD
5244 ><P
5245 >Samba 2.2.0 introduced the ability to dynamically
5246                 add and delete shares via the Windows NT 4.0 Server Manager.  The
5247                 <TT
5248 CLASS="PARAMETER"
5249 ><I
5250 >change share command</I
5251 ></TT
5252 > is used to define an
5253                 external program or script which will modify an existing service definition
5254                 in <TT
5255 CLASS="FILENAME"
5256 >smb.conf</TT
5257 >.  In order to successfully
5258                 execute the <TT
5259 CLASS="PARAMETER"
5260 ><I
5261 >change share command</I
5262 ></TT
5263 >, <B
5264 CLASS="COMMAND"
5265 >smbd</B
5266 >
5267                 requires that the administrator be connected using a root account (i.e.
5268                 uid == 0).
5269                 </P
5270 ><P
5271 >               When executed, <B
5272 CLASS="COMMAND"
5273 >smbd</B
5274 > will automatically invoke the
5275                 <TT
5276 CLASS="PARAMETER"
5277 ><I
5278 >change share command</I
5279 ></TT
5280 > with four parameters.
5281                 </P
5282 ><P
5283 ></P
5284 ><UL
5285 ><LI
5286 ><P
5287 ><TT
5288 CLASS="PARAMETER"
5289 ><I
5290 >configFile</I
5291 ></TT
5292 > - the location
5293                         of the global <TT
5294 CLASS="FILENAME"
5295 >smb.conf</TT
5296 > file.
5297                         </P
5298 ></LI
5299 ><LI
5300 ><P
5301 ><TT
5302 CLASS="PARAMETER"
5303 ><I
5304 >shareName</I
5305 ></TT
5306 > - the name of the new
5307                         share.
5308                         </P
5309 ></LI
5310 ><LI
5311 ><P
5312 ><TT
5313 CLASS="PARAMETER"
5314 ><I
5315 >pathName</I
5316 ></TT
5317 > - path to an **existing**
5318                         directory on disk.
5319                         </P
5320 ></LI
5321 ><LI
5322 ><P
5323 ><TT
5324 CLASS="PARAMETER"
5325 ><I
5326 >comment</I
5327 ></TT
5328 > - comment string to associate
5329                         with the new share.
5330                         </P
5331 ></LI
5332 ></UL
5333 ><P
5334 >               This parameter is only used modify existing file shares definitions.  To modify
5335                 printer shares, use the "Printers..." folder as seen when browsing the Samba host.
5336                 </P
5337 ><P
5338 >               See also <A
5339 HREF="#ADDSHARECOMMAND"
5340 ><TT
5341 CLASS="PARAMETER"
5342 ><I
5343 >add share
5344                 command</I
5345 ></TT
5346 ></A
5347 >, <A
5348 HREF="#DELETESHARECOMMAND"
5349 ><TT
5350 CLASS="PARAMETER"
5351 ><I
5352 >delete
5353                 share command</I
5354 ></TT
5355 ></A
5356 >.
5357                 </P
5358 ><P
5359 >Default: <EM
5360 >none</EM
5361 ></P
5362 ><P
5363 >Example: <B
5364 CLASS="COMMAND"
5365 >change share command = /usr/local/bin/addshare</B
5366 ></P
5367 ></DD
5368 ><DT
5369 ><A
5370 NAME="CHARACTERSET"
5371 ></A
5372 >character set (G)</DT
5373 ><DD
5374 ><P
5375 >This allows a smbd to map incoming filenames
5376                 from a DOS Code page (see the <A
5377 HREF="#CLIENTCODEPAGE"
5378 >client
5379                 code page</A
5380 > parameter) to several built in UNIX character sets.
5381                 The built in code page translations are:</P
5382 ><P
5383 ></P
5384 ><UL
5385 ><LI
5386 ><P
5387 ><TT
5388 CLASS="CONSTANT"
5389 >ISO8859-1</TT
5390 > : Western European
5391                         UNIX character set. The parameter <TT
5392 CLASS="PARAMETER"
5393 ><I
5394 >client code page</I
5395 ></TT
5396 >
5397                         <EM
5398 >MUST</EM
5399 > be set to code page 850 if the
5400                         <TT
5401 CLASS="PARAMETER"
5402 ><I
5403 >character set</I
5404 ></TT
5405 > parameter is set to
5406                         <TT
5407 CLASS="CONSTANT"
5408 >ISO8859-1</TT
5409 > in order for the conversion to the
5410                         UNIX character set to be done correctly.</P
5411 ></LI
5412 ><LI
5413 ><P
5414 ><TT
5415 CLASS="CONSTANT"
5416 >ISO8859-2</TT
5417 > : Eastern European
5418                         UNIX character set. The parameter <TT
5419 CLASS="PARAMETER"
5420 ><I
5421 >client code page
5422                         </I
5423 ></TT
5424 > <EM
5425 >MUST</EM
5426 > be set to code page 852 if
5427                         the <TT
5428 CLASS="PARAMETER"
5429 ><I
5430 > character set</I
5431 ></TT
5432 > parameter is set
5433                         to <TT
5434 CLASS="CONSTANT"
5435 >ISO8859-2</TT
5436 > in order for the conversion
5437                         to the UNIX character set to be done correctly. </P
5438 ></LI
5439 ><LI
5440 ><P
5441 ><TT
5442 CLASS="CONSTANT"
5443 >ISO8859-5</TT
5444 > : Russian Cyrillic
5445                         UNIX character set. The parameter <TT
5446 CLASS="PARAMETER"
5447 ><I
5448 >client code page
5449                         </I
5450 ></TT
5451 > <EM
5452 >MUST</EM
5453 > be set to code page
5454                         866 if the <TT
5455 CLASS="PARAMETER"
5456 ><I
5457 >character set </I
5458 ></TT
5459 > parameter is
5460                         set to <TT
5461 CLASS="CONSTANT"
5462 >ISO8859-5</TT
5463 > in order for the conversion
5464                         to the UNIX character set to be done correctly. </P
5465 ></LI
5466 ><LI
5467 ><P
5468 ><TT
5469 CLASS="CONSTANT"
5470 >ISO8859-7</TT
5471 > : Greek UNIX
5472                         character set. The parameter <TT
5473 CLASS="PARAMETER"
5474 ><I
5475 >client code page
5476                         </I
5477 ></TT
5478 > <EM
5479 >MUST</EM
5480 > be set to code page
5481                         737 if the <TT
5482 CLASS="PARAMETER"
5483 ><I
5484 >character set</I
5485 ></TT
5486 > parameter is
5487                         set to <TT
5488 CLASS="CONSTANT"
5489 >ISO8859-7</TT
5490 > in order for the conversion
5491                         to the UNIX character set to be done correctly.</P
5492 ></LI
5493 ><LI
5494 ><P
5495 ><TT
5496 CLASS="CONSTANT"
5497 >KOI8-R</TT
5498 > : Alternate mapping
5499                         for Russian Cyrillic UNIX character set. The parameter
5500                         <TT
5501 CLASS="PARAMETER"
5502 ><I
5503 >client code page</I
5504 ></TT
5505 > <EM
5506 >MUST</EM
5507 >
5508                         be set to code page 866 if the <TT
5509 CLASS="PARAMETER"
5510 ><I
5511 >character set</I
5512 ></TT
5513 >
5514                         parameter is set to <TT
5515 CLASS="CONSTANT"
5516 >KOI8-R</TT
5517 > in order for the
5518                         conversion to the UNIX character set to be done correctly.</P
5519 ></LI
5520 ></UL
5521 ><P
5522 ><EM
5523 >BUG</EM
5524 >. These MSDOS code page to UNIX character
5525                 set mappings should be dynamic, like the loading of MS DOS code pages,
5526                 not static.</P
5527 ><P
5528 >Normally this parameter is not set, meaning no filename
5529                 translation is done.</P
5530 ><P
5531 >Default: <B
5532 CLASS="COMMAND"
5533 >character set = &#60;empty string&#62;</B
5534 ></P
5535 ><P
5536 >Example: <B
5537 CLASS="COMMAND"
5538 >character set = ISO8859-1</B
5539 ></P
5540 ></DD
5541 ><DT
5542 ><A
5543 NAME="CLIENTCODEPAGE"
5544 ></A
5545 >client code page (G)</DT
5546 ><DD
5547 ><P
5548 >This parameter specifies the DOS code page
5549                 that the clients accessing Samba are using. To determine what code
5550                 page a Windows or DOS client is using, open a DOS command prompt
5551                 and type the command <B
5552 CLASS="COMMAND"
5553 >chcp</B
5554 >. This will output
5555                 the code page. The default for USA MS-DOS, Windows 95, and
5556                 Windows NT releases is code page 437. The default for western
5557                 European releases of the above operating systems is code page 850.</P
5558 ><P
5559 >This parameter tells <A
5560 HREF="smbd.8.html"
5561 TARGET="_top"
5562 >smbd(8)</A
5563 >
5564                 which of the <TT
5565 CLASS="FILENAME"
5566 >codepage.<TT
5567 CLASS="REPLACEABLE"
5568 ><I
5569 >XXX</I
5570 ></TT
5571 >
5572                 </TT
5573 > files to dynamically load on startup. These files,
5574                 described more fully in the manual page <A
5575 HREF="make_smbcodepage.1.html"
5576 TARGET="_top"
5577 >               <B
5578 CLASS="COMMAND"
5579 >make_smbcodepage(1)</B
5580 ></A
5581 >, tell <B
5582 CLASS="COMMAND"
5583 >               smbd</B
5584 > how to map lower to upper case characters to provide
5585                 the case insensitivity of filenames that Windows clients expect.</P
5586 ><P
5587 >Samba currently ships with the following code page files :</P
5588 ><P
5589 ></P
5590 ><UL
5591 ><LI
5592 ><P
5593 >Code Page 437 - MS-DOS Latin US</P
5594 ></LI
5595 ><LI
5596 ><P
5597 >Code Page 737 - Windows '95 Greek</P
5598 ></LI
5599 ><LI
5600 ><P
5601 >Code Page 850 - MS-DOS Latin 1</P
5602 ></LI
5603 ><LI
5604 ><P
5605 >Code Page 852 - MS-DOS Latin 2</P
5606 ></LI
5607 ><LI
5608 ><P
5609 >Code Page 861 - MS-DOS Icelandic</P
5610 ></LI
5611 ><LI
5612 ><P
5613 >Code Page 866 - MS-DOS Cyrillic</P
5614 ></LI
5615 ><LI
5616 ><P
5617 >Code Page 932 - MS-DOS Japanese SJIS</P
5618 ></LI
5619 ><LI
5620 ><P
5621 >Code Page 936 - MS-DOS Simplified Chinese</P
5622 ></LI
5623 ><LI
5624 ><P
5625 >Code Page 949 - MS-DOS Korean Hangul</P
5626 ></LI
5627 ><LI
5628 ><P
5629 >Code Page 950 - MS-DOS Traditional Chinese</P
5630 ></LI
5631 ></UL
5632 ><P
5633 >Thus this parameter may have any of the values 437, 737, 850, 852,
5634                 861, 932, 936, 949, or 950.  If you don't find the codepage you need,
5635                 read the comments in one of the other codepage files and the
5636                 <B
5637 CLASS="COMMAND"
5638 >make_smbcodepage(1)</B
5639 > man page and write one. Please
5640                 remember to donate it back to the Samba user community.</P
5641 ><P
5642 >This parameter co-operates with the <TT
5643 CLASS="PARAMETER"
5644 ><I
5645 >valid
5646                 chars</I
5647 ></TT
5648 > parameter in determining what characters are
5649                 valid in filenames and how capitalization is done. If you set both
5650                 this parameter and the <TT
5651 CLASS="PARAMETER"
5652 ><I
5653 >valid chars</I
5654 ></TT
5655 > parameter
5656                 the <TT
5657 CLASS="PARAMETER"
5658 ><I
5659 >client code page</I
5660 ></TT
5661 > parameter
5662                 <EM
5663 >MUST</EM
5664 > be set before the <TT
5665 CLASS="PARAMETER"
5666 ><I
5667 >valid
5668                 chars</I
5669 ></TT
5670 > parameter in the <TT
5671 CLASS="FILENAME"
5672 >smb.conf</TT
5673 >
5674                 file. The <TT
5675 CLASS="PARAMETER"
5676 ><I
5677 >valid chars</I
5678 ></TT
5679 > string will then
5680                 augment the character settings in the <TT
5681 CLASS="PARAMETER"
5682 ><I
5683 >client code page</I
5684 ></TT
5685 >
5686                 parameter.</P
5687 ><P
5688 >If not set, <TT
5689 CLASS="PARAMETER"
5690 ><I
5691 >client code page</I
5692 ></TT
5693 > defaults
5694                 to 850.</P
5695 ><P
5696 >See also : <A
5697 HREF="#VALIDCHARS"
5698 ><TT
5699 CLASS="PARAMETER"
5700 ><I
5701 >valid
5702                 chars</I
5703 ></TT
5704 ></A
5705 >, <A
5706 HREF="#CODEPAGEDIRECTORY"
5707 >               <TT
5708 CLASS="PARAMETER"
5709 ><I
5710 >code page directory</I
5711 ></TT
5712 ></A
5713 ></P
5714 ><P
5715 >Default: <B
5716 CLASS="COMMAND"
5717 >client code page = 850</B
5718 ></P
5719 ><P
5720 >Example: <B
5721 CLASS="COMMAND"
5722 >client code page = 936</B
5723 ></P
5724 ></DD
5725 ><DT
5726 ><A
5727 NAME="CODEPAGEDIRECTORY"
5728 ></A
5729 >code page directory (G)</DT
5730 ><DD
5731 ><P
5732 >Define the location of the various client code page
5733                 files.</P
5734 ><P
5735 >See also <A
5736 HREF="#CLIENTCODEPAGE"
5737 ><TT
5738 CLASS="PARAMETER"
5739 ><I
5740 >client
5741                 code page</I
5742 ></TT
5743 ></A
5744 ></P
5745 ><P
5746 >Default: <B
5747 CLASS="COMMAND"
5748 >code page directory = ${prefix}/lib/codepages
5749                 </B
5750 ></P
5751 ><P
5752 >Example: <B
5753 CLASS="COMMAND"
5754 >code page directory = /usr/share/samba/codepages
5755                 </B
5756 ></P
5757 ></DD
5758 ><DT
5759 ><A
5760 NAME="CODINGSYSTEM"
5761 ></A
5762 >codingsystem (G)</DT
5763 ><DD
5764 ><P
5765 >This parameter is used to determine how incoming
5766                 Shift-JIS Japanese characters are mapped from the incoming <A
5767 HREF="#CLIENTCODEPAGE"
5768 ><TT
5769 CLASS="PARAMETER"
5770 ><I
5771 >client code page</I
5772 ></TT
5773 >
5774                 </A
5775 > used by the client, into file names in the UNIX filesystem.
5776                 Only useful if <TT
5777 CLASS="PARAMETER"
5778 ><I
5779 >client code page</I
5780 ></TT
5781 > is set to
5782                 932 (Japanese Shift-JIS).  The options are :</P
5783 ><P
5784 ></P
5785 ><UL
5786 ><LI
5787 ><P
5788 ><TT
5789 CLASS="CONSTANT"
5790 >SJIS</TT
5791 >  - Shift-JIS. Does no
5792                         conversion of the incoming filename.</P
5793 ></LI
5794 ><LI
5795 ><P
5796 ><TT
5797 CLASS="CONSTANT"
5798 >JIS8, J8BB, J8BH, J8@B,
5799                         J8@J, J8@H </TT
5800 > - Convert from incoming Shift-JIS to eight
5801                         bit JIS code with different shift-in, shift out codes.</P
5802 ></LI
5803 ><LI
5804 ><P
5805 ><TT
5806 CLASS="CONSTANT"
5807 >JIS7, J7BB, J7BH, J7@B, J7@J,
5808                         J7@H </TT
5809 > - Convert from incoming Shift-JIS to seven bit
5810                         JIS code with different shift-in, shift out codes.</P
5811 ></LI
5812 ><LI
5813 ><P
5814 ><TT
5815 CLASS="CONSTANT"
5816 >JUNET, JUBB, JUBH, JU@B, JU@J, JU@H </TT
5817 >
5818                         - Convert from incoming Shift-JIS to JUNET code with different shift-in,
5819                         shift out codes.</P
5820 ></LI
5821 ><LI
5822 ><P
5823 ><TT
5824 CLASS="CONSTANT"
5825 >EUC</TT
5826 > - Convert an incoming
5827                         Shift-JIS character to EUC code.</P
5828 ></LI
5829 ><LI
5830 ><P
5831 ><TT
5832 CLASS="CONSTANT"
5833 >HEX</TT
5834 > - Convert an incoming
5835                         Shift-JIS character to a 3 byte hex representation, i.e.
5836                         <TT
5837 CLASS="CONSTANT"
5838 >:AB</TT
5839 >.</P
5840 ></LI
5841 ><LI
5842 ><P
5843 ><TT
5844 CLASS="CONSTANT"
5845 >CAP</TT
5846 > - Convert an incoming
5847                         Shift-JIS character to the 3 byte hex representation used by
5848                         the Columbia AppleTalk Program (CAP), i.e. <TT
5849 CLASS="CONSTANT"
5850 >:AB</TT
5851 >.
5852                         This is used for compatibility between Samba and CAP.</P
5853 ></LI
5854 ></UL
5855 ><P
5856 >Default: <B
5857 CLASS="COMMAND"
5858 >coding system = &#60;empty value&#62;</B
5859 >
5860                 </P
5861 ></DD
5862 ><DT
5863 ><A
5864 NAME="COMMENT"
5865 ></A
5866 >comment (S)</DT
5867 ><DD
5868 ><P
5869 >This is a text field that is seen next to a share
5870                 when a client does a queries the server, either via the network
5871                 neighborhood or via <B
5872 CLASS="COMMAND"
5873 >net view</B
5874 > to list what shares
5875                 are available.</P
5876 ><P
5877 >If you want to set the string that is displayed next to the
5878                 machine name then see the <A
5879 HREF="#SERVERSTRING"
5880 ><TT
5881 CLASS="PARAMETER"
5882 ><I
5883 >               server string</I
5884 ></TT
5885 ></A
5886 > parameter.</P
5887 ><P
5888 >Default: <EM
5889 >No comment string</EM
5890 ></P
5891 ><P
5892 >Example: <B
5893 CLASS="COMMAND"
5894 >comment = Fred's Files</B
5895 ></P
5896 ></DD
5897 ><DT
5898 ><A
5899 NAME="CONFIGFILE"
5900 ></A
5901 >config file (G)</DT
5902 ><DD
5903 ><P
5904 >This allows you to override the config file
5905                 to use, instead of the default (usually <TT
5906 CLASS="FILENAME"
5907 >smb.conf</TT
5908 >).
5909                 There is a chicken and egg problem here as this option is set
5910                 in the config file!</P
5911 ><P
5912 >For this reason, if the name of the config file has changed
5913                 when the parameters are loaded then it will reload them from
5914                 the new config file.</P
5915 ><P
5916 >This option takes the usual substitutions, which can
5917                 be very useful.</P
5918 ><P
5919 >If the config file doesn't exist then it won't be loaded
5920                 (allowing you to special case the config files of just a few
5921                 clients).</P
5922 ><P
5923 >Example: <B
5924 CLASS="COMMAND"
5925 >config file = /usr/local/samba/lib/smb.conf.%m
5926                 </B
5927 ></P
5928 ></DD
5929 ><DT
5930 ><A
5931 NAME="COPY"
5932 ></A
5933 >copy (S)</DT
5934 ><DD
5935 ><P
5936 >This parameter allows you to "clone" service
5937                 entries. The specified service is simply duplicated under the
5938                 current service's name. Any parameters specified in the current
5939                 section will override those in the section being copied.</P
5940 ><P
5941 >This feature lets you set up a 'template' service and
5942                 create similar services easily. Note that the service being
5943                 copied must occur earlier in the configuration file than the
5944                 service doing the copying.</P
5945 ><P
5946 >Default: <EM
5947 >no value</EM
5948 ></P
5949 ><P
5950 >Example: <B
5951 CLASS="COMMAND"
5952 >copy = otherservice</B
5953 ></P
5954 ></DD
5955 ><DT
5956 ><A
5957 NAME="CREATEMASK"
5958 ></A
5959 >create mask (S)</DT
5960 ><DD
5961 ><P
5962 >A synonym for this parameter is
5963                 <A
5964 HREF="#CREATEMODE"
5965 ><TT
5966 CLASS="PARAMETER"
5967 ><I
5968 >create mode</I
5969 ></TT
5970 >
5971                 </A
5972 >.</P
5973 ><P
5974 >When a file is created, the necessary permissions are
5975                 calculated according to the mapping from DOS modes to UNIX
5976                 permissions, and the resulting UNIX mode is then bit-wise 'AND'ed
5977                 with this parameter. This parameter may be thought of as a bit-wise
5978                 MASK for the UNIX modes of a file. Any bit <EM
5979 >not</EM
5980 >
5981                 set here will be removed from the modes set on a file when it is
5982                 created.</P
5983 ><P
5984 >The default value of this parameter removes the
5985                 'group' and 'other' write and execute bits from the UNIX modes.</P
5986 ><P
5987 >Following this Samba will bit-wise 'OR' the UNIX mode created
5988                 from this parameter with the value of the <A
5989 HREF="#FORCECREATEMODE"
5990 ><TT
5991 CLASS="PARAMETER"
5992 ><I
5993 >force create mode</I
5994 ></TT
5995 ></A
5996 >
5997                 parameter which is set to 000 by default.</P
5998 ><P
5999 >This parameter does not affect directory modes. See the
6000                 parameter <A
6001 HREF="#DIRECTORYMODE"
6002 ><TT
6003 CLASS="PARAMETER"
6004 ><I
6005 >directory mode
6006                 </I
6007 ></TT
6008 ></A
6009 > for details.</P
6010 ><P
6011 >See also the <A
6012 HREF="#FORCECREATEMODE"
6013 ><TT
6014 CLASS="PARAMETER"
6015 ><I
6016 >force
6017                 create mode</I
6018 ></TT
6019 ></A
6020 > parameter for forcing particular mode
6021                 bits to be set on created files. See also the <A
6022 HREF="#DIRECTORYMODE"
6023 >               <TT
6024 CLASS="PARAMETER"
6025 ><I
6026 >directory mode"</I
6027 ></TT
6028 ></A
6029 > parameter for masking
6030                 mode bits on created directories.  See also the <A
6031 HREF="#INHERITPERMISSIONS"
6032 >               <TT
6033 CLASS="PARAMETER"
6034 ><I
6035 >inherit permissions</I
6036 ></TT
6037 ></A
6038 > parameter.</P
6039 ><P
6040 >Note that by default this parameter does not apply to permissions
6041                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
6042                 this mask on access control lists also, they need to set the <A
6043 HREF="#RESTRICTACLWITHMASK"
6044 ><TT
6045 CLASS="PARAMETER"
6046 ><I
6047 >restrict acl with
6048                 mask</I
6049 ></TT
6050 ></A
6051 > to true.</P
6052 ><P
6053 >Default: <B
6054 CLASS="COMMAND"
6055 >create mask = 0744</B
6056 ></P
6057 ><P
6058 >Example: <B
6059 CLASS="COMMAND"
6060 >create mask = 0775</B
6061 ></P
6062 ></DD
6063 ><DT
6064 ><A
6065 NAME="CREATEMODE"
6066 ></A
6067 >create mode (S)</DT
6068 ><DD
6069 ><P
6070 >This is a synonym for <A
6071 HREF="#CREATEMASK"
6072 ><TT
6073 CLASS="PARAMETER"
6074 ><I
6075 >               create mask</I
6076 ></TT
6077 ></A
6078 >.</P
6079 ></DD
6080 ><DT
6081 ><A
6082 NAME="DEADTIME"
6083 ></A
6084 >deadtime (G)</DT
6085 ><DD
6086 ><P
6087 >The value of the parameter (a decimal integer)
6088                 represents the number of minutes of inactivity before a connection
6089                 is considered dead, and it is disconnected. The deadtime only takes
6090                 effect if the number of open files is zero.</P
6091 ><P
6092 >This is useful to stop a server's resources being
6093                 exhausted by a large number of inactive connections.</P
6094 ><P
6095 >Most clients have an auto-reconnect feature when a
6096                 connection is broken so in most cases this parameter should be
6097                 transparent to users.</P
6098 ><P
6099 >Using this parameter with a timeout of a few minutes
6100                 is recommended for most systems.</P
6101 ><P
6102 >A deadtime of zero indicates that no auto-disconnection
6103                 should be performed.</P
6104 ><P
6105 >Default: <B
6106 CLASS="COMMAND"
6107 >deadtime = 0</B
6108 ></P
6109 ><P
6110 >Example: <B
6111 CLASS="COMMAND"
6112 >deadtime = 15</B
6113 ></P
6114 ></DD
6115 ><DT
6116 ><A
6117 NAME="DEBUGHIRESTIMESTAMP"
6118 ></A
6119 >debug hires timestamp (G)</DT
6120 ><DD
6121 ><P
6122 >Sometimes the timestamps in the log messages
6123                 are needed with a resolution of higher that seconds, this
6124                 boolean parameter adds microsecond resolution to the timestamp
6125                 message header when turned on.</P
6126 ><P
6127 >Note that the parameter <A
6128 HREF="#DEBUGTIMESTAMP"
6129 ><TT
6130 CLASS="PARAMETER"
6131 ><I
6132 >               debug timestamp</I
6133 ></TT
6134 ></A
6135 > must be on for this to have an
6136                 effect.</P
6137 ><P
6138 >Default: <B
6139 CLASS="COMMAND"
6140 >debug hires timestamp = no</B
6141 ></P
6142 ></DD
6143 ><DT
6144 ><A
6145 NAME="DEBUGPID"
6146 ></A
6147 >debug pid (G)</DT
6148 ><DD
6149 ><P
6150 >When using only one log file for more then one
6151                 forked smbd-process there may be hard to follow which process
6152                 outputs which message. This boolean parameter is adds the process-id
6153                 to the timestamp message headers in the logfile when turned on.</P
6154 ><P
6155 >Note that the parameter <A
6156 HREF="#DEBUGTIMESTAMP"
6157 ><TT
6158 CLASS="PARAMETER"
6159 ><I
6160 >               debug timestamp</I
6161 ></TT
6162 ></A
6163 > must be on for this to have an
6164                 effect.</P
6165 ><P
6166 >Default: <B
6167 CLASS="COMMAND"
6168 >debug pid = no</B
6169 ></P
6170 ></DD
6171 ><DT
6172 ><A
6173 NAME="DEBUGTIMESTAMP"
6174 ></A
6175 >debug timestamp (G)</DT
6176 ><DD
6177 ><P
6178 >Samba 2.2 debug log messages are timestamped
6179                 by default. If you are running at a high <A
6180 HREF="#DEBUGLEVEL"
6181 >               <TT
6182 CLASS="PARAMETER"
6183 ><I
6184 >debug level</I
6185 ></TT
6186 ></A
6187 > these timestamps
6188                 can be distracting. This boolean parameter allows timestamping
6189                 to be turned off.</P
6190 ><P
6191 >Default: <B
6192 CLASS="COMMAND"
6193 >debug timestamp = yes</B
6194 ></P
6195 ></DD
6196 ><DT
6197 ><A
6198 NAME="DEBUGUID"
6199 ></A
6200 >debug uid (G)</DT
6201 ><DD
6202 ><P
6203 >Samba is sometimes run as root and sometime
6204                 run as the connected user, this boolean parameter inserts the
6205                 current euid, egid, uid and gid to the timestamp message headers
6206                 in the log file if turned on.</P
6207 ><P
6208 >Note that the parameter <A
6209 HREF="#DEBUGTIMESTAMP"
6210 ><TT
6211 CLASS="PARAMETER"
6212 ><I
6213 >               debug timestamp</I
6214 ></TT
6215 ></A
6216 > must be on for this to have an
6217                 effect.</P
6218 ><P
6219 >Default: <B
6220 CLASS="COMMAND"
6221 >debug uid = no</B
6222 ></P
6223 ></DD
6224 ><DT
6225 ><A
6226 NAME="DEBUGLEVEL"
6227 ></A
6228 >debuglevel (G)</DT
6229 ><DD
6230 ><P
6231 >The value of the parameter (an integer) allows
6232                 the debug level (logging level) to be specified in the
6233                 <TT
6234 CLASS="FILENAME"
6235 >smb.conf</TT
6236 > file. This is to give greater
6237                 flexibility in the configuration of the system.</P
6238 ><P
6239 >The default will be the debug level specified on
6240                 the command line or level zero if none was specified.</P
6241 ><P
6242 >Example: <B
6243 CLASS="COMMAND"
6244 >debug level = 3</B
6245 ></P
6246 ></DD
6247 ><DT
6248 ><A
6249 NAME="DEFAULT"
6250 ></A
6251 >default (G)</DT
6252 ><DD
6253 ><P
6254 >A synonym for <A
6255 HREF="#DEFAULTSERVICE"
6256 ><TT
6257 CLASS="PARAMETER"
6258 ><I
6259 >               default service</I
6260 ></TT
6261 ></A
6262 >.</P
6263 ></DD
6264 ><DT
6265 ><A
6266 NAME="DEFAULTCASE"
6267 ></A
6268 >default case (S)</DT
6269 ><DD
6270 ><P
6271 >See the section on <A
6272 HREF="#AEN201"
6273 >               NAME MANGLING</A
6274 >. Also note the <A
6275 HREF="#SHORTPRESERVECASE"
6276 >               <TT
6277 CLASS="PARAMETER"
6278 ><I
6279 >short preserve case"</I
6280 ></TT
6281 ></A
6282 > parameter.</P
6283 ><P
6284 >Default: <B
6285 CLASS="COMMAND"
6286 >default case = lower</B
6287 ></P
6288 ></DD
6289 ><DT
6290 ><A
6291 NAME="DEFAULTSERVICE"
6292 ></A
6293 >default service (G)</DT
6294 ><DD
6295 ><P
6296 >This parameter specifies the name of a service
6297                 which will be connected to if the service actually requested cannot
6298                 be found. Note that the square brackets are <EM
6299 >NOT</EM
6300 >
6301                 given in the parameter value (see example below).</P
6302 ><P
6303 >There is no default value for this parameter. If this
6304                 parameter is not given, attempting to connect to a nonexistent
6305                 service results in an error.</P
6306 ><P
6307 >Typically the default service would be a <A
6308 HREF="#GUESTOK"
6309 >               <TT
6310 CLASS="PARAMETER"
6311 ><I
6312 >guest ok</I
6313 ></TT
6314 ></A
6315 >, <A
6316 HREF="#READONLY"
6317 >               <TT
6318 CLASS="PARAMETER"
6319 ><I
6320 >read-only</I
6321 ></TT
6322 ></A
6323 > service.</P
6324 ><P
6325 >Also note that the apparent service name will be changed
6326                 to equal that of the requested service, this is very useful as it
6327                 allows you to use macros like <TT
6328 CLASS="PARAMETER"
6329 ><I
6330 >%S</I
6331 ></TT
6332 > to make
6333                 a wildcard service.</P
6334 ><P
6335 >Note also that any "_" characters in the name of the service
6336                 used in the default service will get mapped to a "/". This allows for
6337                 interesting things.</P
6338 ><P
6339 >Example:</P
6340 ><P
6341 ><TABLE
6342 BORDER="0"
6343 BGCOLOR="#E0E0E0"
6344 WIDTH="90%"
6345 ><TR
6346 ><TD
6347 ><PRE
6348 CLASS="PROGRAMLISTING"
6349 >[global]
6350         default service = pub
6351
6352 [pub]
6353         path = /%S
6354                 </PRE
6355 ></TD
6356 ></TR
6357 ></TABLE
6358 ></P
6359 ></DD
6360 ><DT
6361 ><A
6362 NAME="DELETEPRINTERCOMMAND"
6363 ></A
6364 >delete printer command (G)</DT
6365 ><DD
6366 ><P
6367 >With the introduction of MS-RPC based printer
6368                 support for Windows NT/2000 clients in Samba 2.2, it is now
6369                 possible to delete printer at run time by issuing the
6370                 DeletePrinter() RPC call.</P
6371 ><P
6372 >For a Samba host this means that the printer must be
6373                 physically deleted from underlying printing system.  The <TT
6374 CLASS="PARAMETER"
6375 ><I
6376 >               deleteprinter command</I
6377 ></TT
6378 > defines a script to be run which
6379                 will perform the necessary operations for removing the printer
6380                 from the print system and from <TT
6381 CLASS="FILENAME"
6382 >smb.conf</TT
6383 >.
6384                 </P
6385 ><P
6386 >The <TT
6387 CLASS="PARAMETER"
6388 ><I
6389 >delete printer command</I
6390 ></TT
6391 > is
6392                 automatically called with only one parameter: <TT
6393 CLASS="PARAMETER"
6394 ><I
6395 >               "printer name"</I
6396 ></TT
6397 >.</P
6398 ><P
6399 >Once the <TT
6400 CLASS="PARAMETER"
6401 ><I
6402 >delete printer command</I
6403 ></TT
6404 > has
6405                 been executed, <B
6406 CLASS="COMMAND"
6407 >smbd</B
6408 > will reparse the <TT
6409 CLASS="FILENAME"
6410 >               smb.conf</TT
6411 > to associated printer no longer exists.
6412                 If the sharename is still valid, then <B
6413 CLASS="COMMAND"
6414 >smbd
6415                 </B
6416 > will return an ACCESS_DENIED error to the client.</P
6417 ><P
6418 >See also <A
6419 HREF="#ADDPRINTERCOMMAND"
6420 ><TT
6421 CLASS="PARAMETER"
6422 ><I
6423 >               add printer command</I
6424 ></TT
6425 ></A
6426 >, <A
6427 HREF="#PRINTING"
6428 ><TT
6429 CLASS="PARAMETER"
6430 ><I
6431 >printing</I
6432 ></TT
6433 ></A
6434 >,
6435                 <A
6436 HREF="#SHOWADDPRINTERWIZARD"
6437 ><TT
6438 CLASS="PARAMETER"
6439 ><I
6440 >show add
6441                 printer wizard</I
6442 ></TT
6443 ></A
6444 ></P
6445 ><P
6446 >Default: <EM
6447 >none</EM
6448 ></P
6449 ><P
6450 >Example: <B
6451 CLASS="COMMAND"
6452 >deleteprinter command = /usr/bin/removeprinter
6453                 </B
6454 ></P
6455 ></DD
6456 ><DT
6457 ><A
6458 NAME="DELETEREADONLY"
6459 ></A
6460 >delete readonly (S)</DT
6461 ><DD
6462 ><P
6463 >This parameter allows readonly files to be deleted.
6464                 This is not normal DOS semantics, but is allowed by UNIX.</P
6465 ><P
6466 >This option may be useful for running applications such
6467                 as rcs, where UNIX file ownership prevents changing file
6468                 permissions, and DOS semantics prevent deletion of a read only file.</P
6469 ><P
6470 >Default: <B
6471 CLASS="COMMAND"
6472 >delete readonly = no</B
6473 ></P
6474 ></DD
6475 ><DT
6476 ><A
6477 NAME="DELETESHARECOMMAND"
6478 ></A
6479 >delete share command (G)</DT
6480 ><DD
6481 ><P
6482 >Samba 2.2.0 introduced the ability to dynamically
6483                 add and delete shares via the Windows NT 4.0 Server Manager.  The
6484                 <TT
6485 CLASS="PARAMETER"
6486 ><I
6487 >delete share command</I
6488 ></TT
6489 > is used to define an
6490                 external program or script which will remove an existing service
6491                 definition from <TT
6492 CLASS="FILENAME"
6493 >smb.conf</TT
6494 >.  In order to successfully
6495                 execute the <TT
6496 CLASS="PARAMETER"
6497 ><I
6498 >delete share command</I
6499 ></TT
6500 >, <B
6501 CLASS="COMMAND"
6502 >smbd</B
6503 >
6504                 requires that the administrator be connected using a root account (i.e.
6505                 uid == 0).
6506                 </P
6507 ><P
6508 >               When executed, <B
6509 CLASS="COMMAND"
6510 >smbd</B
6511 > will automatically invoke the
6512                 <TT
6513 CLASS="PARAMETER"
6514 ><I
6515 >delete share command</I
6516 ></TT
6517 > with two parameters.
6518                 </P
6519 ><P
6520 ></P
6521 ><UL
6522 ><LI
6523 ><P
6524 ><TT
6525 CLASS="PARAMETER"
6526 ><I
6527 >configFile</I
6528 ></TT
6529 > - the location
6530                         of the global <TT
6531 CLASS="FILENAME"
6532 >smb.conf</TT
6533 > file.
6534                         </P
6535 ></LI
6536 ><LI
6537 ><P
6538 ><TT
6539 CLASS="PARAMETER"
6540 ><I
6541 >shareName</I
6542 ></TT
6543 > - the name of
6544                         the existing service.
6545                         </P
6546 ></LI
6547 ></UL
6548 ><P
6549 >               This parameter is only used to remove file shares.  To delete printer shares,
6550                 see the <A
6551 HREF="#DELETEPRINTERCOMMAND"
6552 ><TT
6553 CLASS="PARAMETER"
6554 ><I
6555 >delete printer
6556                 command</I
6557 ></TT
6558 ></A
6559 >.
6560                 </P
6561 ><P
6562 >               See also <A
6563 HREF="#ADDSHARECOMMAND"
6564 ><TT
6565 CLASS="PARAMETER"
6566 ><I
6567 >delete share
6568                 command</I
6569 ></TT
6570 ></A
6571 >, <A
6572 HREF="#CHANGESHARECOMMAND"
6573 ><TT
6574 CLASS="PARAMETER"
6575 ><I
6576 >change
6577                 share</I
6578 ></TT
6579 ></A
6580 >.
6581                 </P
6582 ><P
6583 >Default: <EM
6584 >none</EM
6585 ></P
6586 ><P
6587 >Example: <B
6588 CLASS="COMMAND"
6589 >delete share command = /usr/local/bin/delshare</B
6590 ></P
6591 ></DD
6592 ><DT
6593 ><A
6594 NAME="DELETEUSERSCRIPT"
6595 ></A
6596 >delete user script (G)</DT
6597 ><DD
6598 ><P
6599 >This is the full pathname to a script that will
6600                 be run <EM
6601 >AS ROOT</EM
6602 > by <A
6603 HREF="smbd.8.html"
6604 TARGET="_top"
6605 >               <B
6606 CLASS="COMMAND"
6607 >smbd(8)</B
6608 ></A
6609 > under special circumstances
6610                 described below.</P
6611 ><P
6612 >Normally, a Samba server requires that UNIX users are
6613                 created for all users accessing files on this server. For sites
6614                 that use Windows NT account databases as their primary user database
6615                 creating these users and keeping the user list in sync with the
6616                 Windows NT PDC is an onerous task. This option allows <B
6617 CLASS="COMMAND"
6618 >               smbd</B
6619 > to delete the required UNIX users <EM
6620 >ON
6621                 DEMAND</EM
6622 > when a user accesses the Samba server and the
6623                 Windows NT user no longer exists.</P
6624 ><P
6625 >In order to use this option, <B
6626 CLASS="COMMAND"
6627 >smbd</B
6628 > must be
6629                 set to <TT
6630 CLASS="PARAMETER"
6631 ><I
6632 >security=domain</I
6633 ></TT
6634 > and <TT
6635 CLASS="PARAMETER"
6636 ><I
6637 >delete
6638                 user script</I
6639 ></TT
6640 > must be set to a full pathname for a script
6641                 that will delete a UNIX user given one argument of <TT
6642 CLASS="PARAMETER"
6643 ><I
6644 >%u
6645                 </I
6646 ></TT
6647 >, which expands into the UNIX user name to delete.
6648                 <EM
6649 >NOTE</EM
6650 > that this is different to the <A
6651 HREF="#ADDUSERSCRIPT"
6652 ><TT
6653 CLASS="PARAMETER"
6654 ><I
6655 >add user script</I
6656 ></TT
6657 ></A
6658 >
6659                 which will work with the <TT
6660 CLASS="PARAMETER"
6661 ><I
6662 >security=server</I
6663 ></TT
6664 > option
6665                 as well as <TT
6666 CLASS="PARAMETER"
6667 ><I
6668 >security=domain</I
6669 ></TT
6670 >. The reason for this
6671                 is only when Samba is a domain member does it get the information
6672                 on an attempted user logon that a user no longer exists. In the
6673                 <TT
6674 CLASS="PARAMETER"
6675 ><I
6676 >security=server</I
6677 ></TT
6678 > mode a missing user
6679                 is treated the same as an invalid password logon attempt. Deleting
6680                 the user in this circumstance would not be a good idea.</P
6681 ><P
6682 >When the Windows user attempts to access the Samba server,
6683                 at <EM
6684 >login</EM
6685 > (session setup in the SMB protocol)
6686                 time, <B
6687 CLASS="COMMAND"
6688 >smbd</B
6689 > contacts the <A
6690 HREF="#PASSWORDSERVER"
6691 >               <TT
6692 CLASS="PARAMETER"
6693 ><I
6694 >password server</I
6695 ></TT
6696 ></A
6697 > and attempts to authenticate
6698                 the given user with the given password. If the authentication fails
6699                 with the specific Domain error code meaning that the user no longer
6700                 exists then <B
6701 CLASS="COMMAND"
6702 >smbd</B
6703 > attempts to find a UNIX user in
6704                 the UNIX password database that matches the Windows user account. If
6705                 this lookup succeeds, and <TT
6706 CLASS="PARAMETER"
6707 ><I
6708 >delete user script</I
6709 ></TT
6710 > is
6711                 set then <B
6712 CLASS="COMMAND"
6713 >smbd</B
6714 > will all the specified script
6715                 <EM
6716 >AS ROOT</EM
6717 >, expanding any <TT
6718 CLASS="PARAMETER"
6719 ><I
6720 >%u</I
6721 ></TT
6722 >
6723                 argument to be the user name to delete.</P
6724 ><P
6725 >This script should delete the given UNIX username. In this way,
6726                 UNIX users are dynamically deleted to match existing Windows NT
6727                 accounts.</P
6728 ><P
6729 >See also <A
6730 HREF="#SECURITYEQUALSDOMAIN"
6731 >security=domain</A
6732 >,
6733                 <A
6734 HREF="#PASSWORDSERVER"
6735 ><TT
6736 CLASS="PARAMETER"
6737 ><I
6738 >password server</I
6739 ></TT
6740 >
6741                 </A
6742 >, <A
6743 HREF="#ADDUSERSCRIPT"
6744 ><TT
6745 CLASS="PARAMETER"
6746 ><I
6747 >add user script</I
6748 ></TT
6749 >
6750                 </A
6751 >.</P
6752 ><P
6753 >Default: <B
6754 CLASS="COMMAND"
6755 >delete user script = &#60;empty string&#62;
6756                 </B
6757 ></P
6758 ><P
6759 >Example: <B
6760 CLASS="COMMAND"
6761 >delete user script = /usr/local/samba/bin/del_user
6762                 %u</B
6763 ></P
6764 ></DD
6765 ><DT
6766 ><A
6767 NAME="DELETEVETOFILES"
6768 ></A
6769 >delete veto files (S)</DT
6770 ><DD
6771 ><P
6772 >This option is used when Samba is attempting to
6773                 delete a directory that contains one or more vetoed directories
6774                 (see the <A
6775 HREF="#VETOFILES"
6776 ><TT
6777 CLASS="PARAMETER"
6778 ><I
6779 >veto files</I
6780 ></TT
6781 ></A
6782 >
6783                 option).  If this option is set to False (the default) then if a vetoed
6784                 directory contains any non-vetoed files or directories then the
6785                 directory delete will fail. This is usually what you want.</P
6786 ><P
6787 >If this option is set to <TT
6788 CLASS="CONSTANT"
6789 >True</TT
6790 >, then Samba
6791                 will attempt to recursively delete any files and directories within
6792                 the vetoed directory. This can be useful for integration with file
6793                 serving systems such as NetAtalk which create meta-files within
6794                 directories you might normally veto DOS/Windows users from seeing
6795                 (e.g. <TT
6796 CLASS="FILENAME"
6797 >.AppleDouble</TT
6798 >)</P
6799 ><P
6800 >Setting <B
6801 CLASS="COMMAND"
6802 >delete veto files = yes</B
6803 > allows these
6804                 directories to be  transparently deleted when the parent directory
6805                 is deleted (so long as the user has permissions to do so).</P
6806 ><P
6807 >See also the <A
6808 HREF="#VETOFILES"
6809 ><TT
6810 CLASS="PARAMETER"
6811 ><I
6812 >veto
6813                 files</I
6814 ></TT
6815 ></A
6816 > parameter.</P
6817 ><P
6818 >Default: <B
6819 CLASS="COMMAND"
6820 >delete veto files = no</B
6821 ></P
6822 ></DD
6823 ><DT
6824 ><A
6825 NAME="DENYHOSTS"
6826 ></A
6827 >deny hosts (S)</DT
6828 ><DD
6829 ><P
6830 >Synonym for <A
6831 HREF="#HOSTSDENY"
6832 ><TT
6833 CLASS="PARAMETER"
6834 ><I
6835 >hosts
6836                 deny</I
6837 ></TT
6838 ></A
6839 >.</P
6840 ></DD
6841 ><DT
6842 ><A
6843 NAME="DFREECOMMAND"
6844 ></A
6845 >dfree command (G)</DT
6846 ><DD
6847 ><P
6848 >The <TT
6849 CLASS="PARAMETER"
6850 ><I
6851 >dfree command</I
6852 ></TT
6853 > setting should
6854                 only be used on systems where a problem occurs with the internal
6855                 disk space calculations. This has been known to happen with Ultrix,
6856                 but may occur with other operating systems. The symptom that was
6857                 seen was an error of "Abort Retry Ignore" at the end of each
6858                 directory listing.</P
6859 ><P
6860 >This setting allows the replacement of the internal routines to
6861                 calculate the total disk space and amount available with an external
6862                 routine. The example below gives a possible script that might fulfill
6863                 this function.</P
6864 ><P
6865 >The external program will be passed a single parameter indicating
6866                 a directory in the filesystem being queried. This will typically consist
6867                 of the string <TT
6868 CLASS="FILENAME"
6869 >./</TT
6870 >. The script should return two
6871                 integers in ASCII. The first should be the total disk space in blocks,
6872                 and the second should be the number of available blocks. An optional
6873                 third return value can give the block size in bytes. The default
6874                 blocksize is 1024 bytes.</P
6875 ><P
6876 >Note: Your script should <EM
6877 >NOT</EM
6878 > be setuid or
6879                 setgid and should be owned by (and writeable only by) root!</P
6880 ><P
6881 >Default: <EM
6882 >By default internal routines for
6883                 determining the disk capacity and remaining space will be used.
6884                 </EM
6885 ></P
6886 ><P
6887 >Example: <B
6888 CLASS="COMMAND"
6889 >dfree command = /usr/local/samba/bin/dfree
6890                 </B
6891 ></P
6892 ><P
6893 >Where the script dfree (which must be made executable) could be:</P
6894 ><P
6895 ><TABLE
6896 BORDER="0"
6897 BGCOLOR="#E0E0E0"
6898 WIDTH="90%"
6899 ><TR
6900 ><TD
6901 ><PRE
6902 CLASS="PROGRAMLISTING"
6903 >
6904                 #!/bin/sh
6905                 df $1 | tail -1 | awk '{print $2" "$4}'
6906                 </PRE
6907 ></TD
6908 ></TR
6909 ></TABLE
6910 ></P
6911 ><P
6912 >or perhaps (on Sys V based systems):</P
6913 ><P
6914 ><TABLE
6915 BORDER="0"
6916 BGCOLOR="#E0E0E0"
6917 WIDTH="90%"
6918 ><TR
6919 ><TD
6920 ><PRE
6921 CLASS="PROGRAMLISTING"
6922 >
6923                 #!/bin/sh
6924                 /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
6925                 </PRE
6926 ></TD
6927 ></TR
6928 ></TABLE
6929 ></P
6930 ><P
6931 >Note that you may have to replace the command names
6932                 with full path names on some systems.</P
6933 ></DD
6934 ><DT
6935 ><A
6936 NAME="DIRECTORY"
6937 ></A
6938 >directory (S)</DT
6939 ><DD
6940 ><P
6941 >Synonym for <A
6942 HREF="#PATH"
6943 ><TT
6944 CLASS="PARAMETER"
6945 ><I
6946 >path
6947                 </I
6948 ></TT
6949 ></A
6950 >.</P
6951 ></DD
6952 ><DT
6953 ><A
6954 NAME="DIRECTORYMASK"
6955 ></A
6956 >directory mask (S)</DT
6957 ><DD
6958 ><P
6959 >This parameter is the octal modes which are
6960                 used when converting DOS modes to UNIX modes when creating UNIX
6961                 directories.</P
6962 ><P
6963 >When a directory is created, the necessary permissions are
6964                 calculated according to the mapping from DOS modes to UNIX permissions,
6965                 and the resulting UNIX mode is then bit-wise 'AND'ed with this
6966                 parameter. This parameter may be thought of as a bit-wise MASK for
6967                 the UNIX modes of a directory. Any bit <EM
6968 >not</EM
6969 > set
6970                 here will be removed from the modes set on a directory when it is
6971                 created.</P
6972 ><P
6973 >The default value of this parameter removes the 'group'
6974                 and 'other' write bits from the UNIX mode, allowing only the
6975                 user who owns the directory to modify it.</P
6976 ><P
6977 >Following this Samba will bit-wise 'OR' the UNIX mode
6978                 created from this parameter with the value of the <A
6979 HREF="#FORCEDIRECTORYMODE"
6980 ><TT
6981 CLASS="PARAMETER"
6982 ><I
6983 >force directory mode
6984                 </I
6985 ></TT
6986 ></A
6987 > parameter. This parameter is set to 000 by
6988                 default (i.e. no extra mode bits are added).</P
6989 ><P
6990 >Note that by default this parameter does not apply to permissions
6991                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
6992                 this mask on access control lists also, they need to set the <A
6993 HREF="#RESTRICTACLWITHMASK"
6994 ><TT
6995 CLASS="PARAMETER"
6996 ><I
6997 >restrict acl with
6998                 mask</I
6999 ></TT
7000 ></A
7001 > to true.</P
7002 ><P
7003 >See the <A
7004 HREF="#FORCEDIRECTORYMODE"
7005 ><TT
7006 CLASS="PARAMETER"
7007 ><I
7008 >force
7009                 directory mode</I
7010 ></TT
7011 ></A
7012 > parameter to cause particular mode
7013                 bits to always be set on created directories.</P
7014 ><P
7015 >See also the <A
7016 HREF="#CREATEMODE"
7017 ><TT
7018 CLASS="PARAMETER"
7019 ><I
7020 >create mode
7021                 </I
7022 ></TT
7023 ></A
7024 > parameter for masking mode bits on created files,
7025                 and the <A
7026 HREF="#DIRECTORYSECURITYMASK"
7027 ><TT
7028 CLASS="PARAMETER"
7029 ><I
7030 >directory
7031                 security mask</I
7032 ></TT
7033 ></A
7034 > parameter.</P
7035 ><P
7036 >Also refer to the <A
7037 HREF="#INHERITPERMISSIONS"
7038 ><TT
7039 CLASS="PARAMETER"
7040 ><I
7041 >               inherit permissions</I
7042 ></TT
7043 ></A
7044 > parameter.</P
7045 ><P
7046 >Default: <B
7047 CLASS="COMMAND"
7048 >directory mask = 0755</B
7049 ></P
7050 ><P
7051 >Example: <B
7052 CLASS="COMMAND"
7053 >directory mask = 0775</B
7054 ></P
7055 ></DD
7056 ><DT
7057 ><A
7058 NAME="DIRECTORYMODE"
7059 ></A
7060 >directory mode (S)</DT
7061 ><DD
7062 ><P
7063 >Synonym for <A
7064 HREF="#DIRECTORYMASK"
7065 ><TT
7066 CLASS="PARAMETER"
7067 ><I
7068 >               directory mask</I
7069 ></TT
7070 ></A
7071 ></P
7072 ></DD
7073 ><DT
7074 ><A
7075 NAME="DIRECTORYSECURITYMASK"
7076 ></A
7077 >directory security mask (S)</DT
7078 ><DD
7079 ><P
7080 >This parameter controls what UNIX permission bits
7081                 can be modified when a Windows NT client is manipulating the UNIX
7082                 permission on a directory using the native NT security dialog
7083                 box.</P
7084 ><P
7085 >This parameter is applied as a mask (AND'ed with) to
7086                 the changed permission bits, thus preventing any bits not in
7087                 this mask from being modified. Essentially, zero bits in this
7088                 mask may be treated as a set of bits the user is not allowed
7089                 to change.</P
7090 ><P
7091 >If not set explicitly this parameter is set to the same
7092                 value as the <A
7093 HREF="#DIRECTORYMASK"
7094 ><TT
7095 CLASS="PARAMETER"
7096 ><I
7097 >directory
7098                 mask</I
7099 ></TT
7100 ></A
7101 > parameter. To allow a user to
7102                 modify all the user/group/world permissions on a directory, set
7103                 this parameter to 0777.</P
7104 ><P
7105 ><EM
7106 >Note</EM
7107 > that users who can access the
7108                 Samba server through other means can easily bypass this restriction,
7109                 so it is primarily useful for standalone "appliance" systems.
7110                 Administrators of most normal systems will probably want to set
7111                 it to 0777.</P
7112 ><P
7113 >See also the <A
7114 HREF="#FORCEDIRECTORYSECURITYMODE"
7115 ><TT
7116 CLASS="PARAMETER"
7117 ><I
7118 >               force directory security mode</I
7119 ></TT
7120 ></A
7121 >, <A
7122 HREF="#SECURITYMASK"
7123 ><TT
7124 CLASS="PARAMETER"
7125 ><I
7126 >security mask</I
7127 ></TT
7128 ></A
7129 >,
7130                 <A
7131 HREF="#FORCESECURITYMODE"
7132 ><TT
7133 CLASS="PARAMETER"
7134 ><I
7135 >force security mode
7136                 </I
7137 ></TT
7138 ></A
7139 > parameters.</P
7140 ><P
7141 >Default: <B
7142 CLASS="COMMAND"
7143 >directory security mask = &#60;same as
7144                 directory mask&#62;</B
7145 ></P
7146 ><P
7147 >Example: <B
7148 CLASS="COMMAND"
7149 >directory security mask = 0777</B
7150 ></P
7151 ></DD
7152 ><DT
7153 ><A
7154 NAME="DNSPROXY"
7155 ></A
7156 >dns proxy (G)</DT
7157 ><DD
7158 ><P
7159 >Specifies that <A
7160 HREF="nmbd.8.html"
7161 TARGET="_top"
7162 >nmbd(8)</A
7163 >
7164                 when acting as a WINS server and finding that a NetBIOS name has not
7165                 been registered, should treat the NetBIOS name word-for-word as a DNS
7166                 name and do a lookup with the DNS server for that name on behalf of
7167                 the name-querying client.</P
7168 ><P
7169 >Note that the maximum length for a NetBIOS name is 15
7170                 characters, so the DNS name (or DNS alias) can likewise only be
7171                 15 characters, maximum.</P
7172 ><P
7173 ><B
7174 CLASS="COMMAND"
7175 >nmbd</B
7176 > spawns a second copy of itself to do the
7177                 DNS name lookup requests, as doing a name lookup is a blocking
7178                 action.</P
7179 ><P
7180 >See also the parameter <A
7181 HREF="#WINSSUPPORT"
7182 ><TT
7183 CLASS="PARAMETER"
7184 ><I
7185 >               wins support</I
7186 ></TT
7187 ></A
7188 >.</P
7189 ><P
7190 >Default: <B
7191 CLASS="COMMAND"
7192 >dns proxy = yes</B
7193 ></P
7194 ></DD
7195 ><DT
7196 ><A
7197 NAME="DOMAINADMINGROUP"
7198 ></A
7199 >domain admin group (G)</DT
7200 ><DD
7201 ><P
7202 >This parameter is intended as a temporary solution
7203                 to enable users to be a member of the "Domain Admins" group when
7204                 a Samba host is acting as a PDC.  A complete solution will be provided
7205                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7206                 Please note that this parameter has a somewhat confusing name.  It
7207                 accepts a list of usernames and of group names in standard
7208                 <TT
7209 CLASS="FILENAME"
7210 >smb.conf</TT
7211 >       notation.
7212                 </P
7213 ><P
7214 >See also <A
7215 HREF="#DOMAINGUESTGROUP"
7216 ><TT
7217 CLASS="PARAMETER"
7218 ><I
7219 >domain
7220                 guest group</I
7221 ></TT
7222 ></A
7223 >, <A
7224 HREF="#DOMAINLOGONS"
7225 ><TT
7226 CLASS="PARAMETER"
7227 ><I
7228 >domain
7229                 logons</I
7230 ></TT
7231 ></A
7232 >
7233                 </P
7234 ><P
7235 >Default: <EM
7236 >no domain administrators</EM
7237 ></P
7238 ><P
7239 >Example: <B
7240 CLASS="COMMAND"
7241 >domain admin group = root @wheel</B
7242 ></P
7243 ></DD
7244 ><DT
7245 ><A
7246 NAME="DOMAINGUESTGROUP"
7247 ></A
7248 >domain guest group (G)</DT
7249 ><DD
7250 ><P
7251 >This parameter is intended as a temporary solution
7252                 to enable users to be a member of the "Domain Guests" group when
7253                 a Samba host is acting as a PDC.  A complete solution will be provided
7254                 by a system for mapping Windows NT/2000 groups onto UNIX groups.
7255                 Please note that this parameter has a somewhat confusing name.  It
7256                 accepts a list of usernames and of group names in standard
7257                 <TT
7258 CLASS="FILENAME"
7259 >smb.conf</TT
7260 >       notation.
7261                 </P
7262 ><P
7263 >See also <A
7264 HREF="#DOMAINADMINGROUP"
7265 ><TT
7266 CLASS="PARAMETER"
7267 ><I
7268 >domain
7269                 admin group</I
7270 ></TT
7271 ></A
7272 >, <A
7273 HREF="#DOMAINLOGONS"
7274 ><TT
7275 CLASS="PARAMETER"
7276 ><I
7277 >domain
7278                 logons</I
7279 ></TT
7280 ></A
7281 >
7282                 </P
7283 ><P
7284 >Default: <EM
7285 >no domain guests</EM
7286 ></P
7287 ><P
7288 >Example: <B
7289 CLASS="COMMAND"
7290 >domain guest group = nobody @guest</B
7291 ></P
7292 ></DD
7293 ><DT
7294 ><A
7295 NAME="DOMAINLOGONS"
7296 ></A
7297 >domain logons (G)</DT
7298 ><DD
7299 ><P
7300 >If set to true, the Samba server will serve
7301                 Windows 95/98 Domain logons for the <A
7302 HREF="#WORKGROUP"
7303 >               <TT
7304 CLASS="PARAMETER"
7305 ><I
7306 >workgroup</I
7307 ></TT
7308 ></A
7309 > it is in. Samba 2.2 also
7310                 has limited capability to act as a domain controller for Windows
7311                 NT 4 Domains.  For more details on setting up this feature see
7312                 the file DOMAINS.txt in the Samba documentation directory <TT
7313 CLASS="FILENAME"
7314 >docs/
7315                 </TT
7316 > shipped with the source code.</P
7317 ><P
7318 >Default: <B
7319 CLASS="COMMAND"
7320 >domain logons = no</B
7321 ></P
7322 ></DD
7323 ><DT
7324 ><A
7325 NAME="DOMAINMASTER"
7326 ></A
7327 >domain master (G)</DT
7328 ><DD
7329 ><P
7330 >Tell <A
7331 HREF="nmbd.8.html"
7332 TARGET="_top"
7333 ><B
7334 CLASS="COMMAND"
7335 >               nmbd(8)</B
7336 ></A
7337 > to enable WAN-wide browse list
7338                 collation. Setting this option causes <B
7339 CLASS="COMMAND"
7340 >nmbd</B
7341 > to
7342                 claim a special domain specific NetBIOS name that identifies
7343                 it as a domain master browser for its given <A
7344 HREF="#WORKGROUP"
7345 >               <TT
7346 CLASS="PARAMETER"
7347 ><I
7348 >workgroup</I
7349 ></TT
7350 ></A
7351 >. Local master browsers
7352                 in the same <TT
7353 CLASS="PARAMETER"
7354 ><I
7355 >workgroup</I
7356 ></TT
7357 > on broadcast-isolated
7358                 subnets will give this <B
7359 CLASS="COMMAND"
7360 >nmbd</B
7361 > their local browse lists,
7362                 and then ask <A
7363 HREF="smbd.8.html"
7364 TARGET="_top"
7365 ><B
7366 CLASS="COMMAND"
7367 >smbd(8)</B
7368 ></A
7369 >
7370                 for a complete copy of the browse list for the whole wide area
7371                 network.  Browser clients will then contact their local master browser,
7372                 and will receive the domain-wide browse list, instead of just the list
7373                 for their broadcast-isolated subnet.</P
7374 ><P
7375 >Note that Windows NT Primary Domain Controllers expect to be
7376                 able to claim this <TT
7377 CLASS="PARAMETER"
7378 ><I
7379 >workgroup</I
7380 ></TT
7381 > specific special
7382                 NetBIOS name that identifies them as domain master browsers for
7383                 that <TT
7384 CLASS="PARAMETER"
7385 ><I
7386 >workgroup</I
7387 ></TT
7388 > by default (i.e. there is no
7389                 way to prevent a Windows NT PDC from attempting to do this). This
7390                 means that if this parameter is set and <B
7391 CLASS="COMMAND"
7392 >nmbd</B
7393 > claims
7394                 the special name for a <TT
7395 CLASS="PARAMETER"
7396 ><I
7397 >workgroup</I
7398 ></TT
7399 > before a Windows
7400                 NT PDC is able to do so then cross subnet browsing will behave
7401                 strangely and may fail.</P
7402 ><P
7403 >If <A
7404 HREF="#DOMAINLOGONS"
7405 ><B
7406 CLASS="COMMAND"
7407 >domain logons = yes</B
7408 >
7409                 </A
7410 >, then the default behavior is to enable the <TT
7411 CLASS="PARAMETER"
7412 ><I
7413 >domain
7414                 master</I
7415 ></TT
7416 > parameter.  If <TT
7417 CLASS="PARAMETER"
7418 ><I
7419 >domain logons</I
7420 ></TT
7421 > is
7422                 not enabled (the default setting), then neither will <TT
7423 CLASS="PARAMETER"
7424 ><I
7425 >domain
7426                 master</I
7427 ></TT
7428 > be enabled by default.</P
7429 ><P
7430 >Default: <B
7431 CLASS="COMMAND"
7432 >domain master = auto</B
7433 ></P
7434 ></DD
7435 ><DT
7436 ><A
7437 NAME="DONTDESCEND"
7438 ></A
7439 >dont descend (S)</DT
7440 ><DD
7441 ><P
7442 >There are certain directories on some systems
7443                 (e.g., the <TT
7444 CLASS="FILENAME"
7445 >/proc</TT
7446 > tree under Linux) that are either not
7447                 of interest to clients or are infinitely deep (recursive). This
7448                 parameter allows you to specify a comma-delimited list of directories
7449                 that the server should always show as empty.</P
7450 ><P
7451 >Note that Samba can be very fussy about the exact format
7452                 of the "dont descend" entries. For example you may need <TT
7453 CLASS="FILENAME"
7454 >               ./proc</TT
7455 > instead of just <TT
7456 CLASS="FILENAME"
7457 >/proc</TT
7458 >.
7459                 Experimentation is the best policy :-)  </P
7460 ><P
7461 >Default: <EM
7462 >none (i.e., all directories are OK
7463                 to descend)</EM
7464 ></P
7465 ><P
7466 >Example: <B
7467 CLASS="COMMAND"
7468 >dont descend = /proc,/dev</B
7469 ></P
7470 ></DD
7471 ><DT
7472 ><A
7473 NAME="DOSFILEMODE"
7474 ></A
7475 >dos filemode (S)</DT
7476 ><DD
7477 ><P
7478 > The default behavior in Samba is to provide
7479                 UNIX-like behavor where only the owner of a file/directory is
7480                 able to change the permissions on it.  However, this behavior
7481                 is often confusing to  DOS/Windows users.  Enabling this parameter
7482                 allows a user who has write access to the file (by whatever
7483                 means) to modify the permissions on it.  Note that a user
7484                 belonging to the group owning the file will not be allowed to
7485                 change permissions if the group is only granted read access.
7486                 Ownership of the file/directory is not changed, only the permissions
7487                 are modified.</P
7488 ><P
7489 >Default: <B
7490 CLASS="COMMAND"
7491 >dos filemode = no</B
7492 ></P
7493 ></DD
7494 ><DT
7495 ><A
7496 NAME="DOSFILETIMERESOLUTION"
7497 ></A
7498 >dos filetime resolution (S)</DT
7499 ><DD
7500 ><P
7501 >Under the DOS and Windows FAT filesystem, the finest
7502                 granularity on time resolution is two seconds. Setting this parameter
7503                 for a share causes Samba to round the reported time down to the
7504                 nearest two second boundary when a query call that requires one second
7505                 resolution is made to <A
7506 HREF="smbd.8.html"
7507 TARGET="_top"
7508 ><B
7509 CLASS="COMMAND"
7510 >smbd(8)</B
7511 >
7512                 </A
7513 >.</P
7514 ><P
7515 >This option is mainly used as a compatibility option for Visual
7516                 C++ when used against Samba shares. If oplocks are enabled on a
7517                 share, Visual C++ uses two different time reading calls to check if a
7518                 file has changed since it was last read. One of these calls uses a
7519                 one-second granularity, the other uses a two second granularity. As
7520                 the two second call rounds any odd second down, then if the file has a
7521                 timestamp of an odd number of seconds then the two timestamps will not
7522                 match and Visual C++ will keep reporting the file has changed. Setting
7523                 this option causes the two timestamps to match, and Visual C++ is
7524                 happy.</P
7525 ><P
7526 >Default: <B
7527 CLASS="COMMAND"
7528 >dos filetime resolution = no</B
7529 ></P
7530 ></DD
7531 ><DT
7532 ><A
7533 NAME="DOSFILETIMES"
7534 ></A
7535 >dos filetimes (S)</DT
7536 ><DD
7537 ><P
7538 >Under DOS and Windows, if a user can write to a
7539                 file they can change the timestamp on it. Under POSIX semantics,
7540                 only the owner of the file or root may change the timestamp. By
7541                 default, Samba runs with POSIX semantics and refuses to change the
7542                 timestamp on a file if the user <B
7543 CLASS="COMMAND"
7544 >smbd</B
7545 > is acting
7546                 on behalf of is not the file owner. Setting this option to <TT
7547 CLASS="CONSTANT"
7548 >               True</TT
7549 > allows DOS semantics and smbd will change the file
7550                 timestamp as DOS requires.</P
7551 ><P
7552 >Default: <B
7553 CLASS="COMMAND"
7554 >dos filetimes = no</B
7555 ></P
7556 ></DD
7557 ><DT
7558 ><A
7559 NAME="ENCRYPTPASSWORDS"
7560 ></A
7561 >encrypt passwords (G)</DT
7562 ><DD
7563 ><P
7564 >This boolean controls whether encrypted passwords
7565                 will be negotiated with the client. Note that Windows NT 4.0 SP3 and
7566                 above and also Windows 98 will by default expect encrypted passwords
7567                 unless a registry entry is changed. To use encrypted passwords in
7568                 Samba see the file ENCRYPTION.txt in the Samba documentation
7569                 directory <TT
7570 CLASS="FILENAME"
7571 >docs/</TT
7572 > shipped with the source code.</P
7573 ><P
7574 >In order for encrypted passwords to work correctly
7575                 <A
7576 HREF="smbd.8.html"
7577 TARGET="_top"
7578 ><B
7579 CLASS="COMMAND"
7580 >smbd(8)</B
7581 ></A
7582 > must either
7583                 have access to a local <A
7584 HREF="smbpasswd.5.html"
7585 TARGET="_top"
7586 ><TT
7587 CLASS="FILENAME"
7588 >smbpasswd(5)
7589                 </TT
7590 ></A
7591 > file (see the <A
7592 HREF="smbpasswd.8.html"
7593 TARGET="_top"
7594 ><B
7595 CLASS="COMMAND"
7596 >               smbpasswd(8)</B
7597 ></A
7598 > program for information on how to set up
7599                 and maintain this file), or set the <A
7600 HREF="#SECURITY"
7601 >security=[serve|domain]</A
7602 > parameter which
7603                 causes <B
7604 CLASS="COMMAND"
7605 >smbd</B
7606 > to authenticate against another
7607                 server.</P
7608 ><P
7609 >Default: <B
7610 CLASS="COMMAND"
7611 >encrypt passwords = no</B
7612 ></P
7613 ></DD
7614 ><DT
7615 ><A
7616 NAME="ENHANCEDBROWSING"
7617 ></A
7618 >enhanced browsing (G)</DT
7619 ><DD
7620 ><P
7621 >This option enables a couple of enhancements to
7622                 cross-subnet browse propogation that have been added in Samba
7623                 but which are not standard in Microsoft implementations.
7624                 <EM
7625 >These enhancements are currently only available in
7626                 the HEAD Samba CVS tree (not Samba 2.2.x).</EM
7627 ></P
7628 ><P
7629 >The first enhancement to browse propogation consists of a regular
7630                 wildcard query to a Samba WINS server for all Domain Master Browsers,
7631                 followed by a browse synchronisation with each of the returned
7632                 DMBs. The second enhancement consists of a regular randomised browse
7633                 synchronisation with all currently known DMBs.</P
7634 ><P
7635 >You may wish to disable this option if you have a problem with empty
7636                 workgroups not disappearing from browse lists. Due to the restrictions
7637                 of the browse protocols these enhancements can cause a empty workgroup
7638                 to stay around forever which can be annoying.</P
7639 ><P
7640 >In general you should leave this option enabled as it makes
7641                 cross-subnet browse propogation much more reliable.</P
7642 ><P
7643 >Default: <B
7644 CLASS="COMMAND"
7645 >enhanced browsing = yes</B
7646 ></P
7647 ></DD
7648 ><DT
7649 ><A
7650 NAME="ENUMPORTSCOMMAND"
7651 ></A
7652 >enumports command (G)</DT
7653 ><DD
7654 ><P
7655 >The concept of a "port" is fairly foreign
7656                 to UNIX hosts.  Under Windows NT/2000 print servers, a port
7657                 is associated with a port monitor and generally takes the form of
7658                 a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
7659                 (i.e. LPD Port Monitor, etc...).  By default, Samba has only one
7660                 port defined--<TT
7661 CLASS="CONSTANT"
7662 >"Samba Printer Port"</TT
7663 >.  Under
7664                 Windows NT/2000, all printers must have a valid port name.
7665                 If you wish to have a list of ports displayed (<B
7666 CLASS="COMMAND"
7667 >smbd
7668                 </B
7669 > does not use a port name for anything) other than
7670                 the default <TT
7671 CLASS="CONSTANT"
7672 >"Samba Printer Port"</TT
7673 >, you
7674                 can define <TT
7675 CLASS="PARAMETER"
7676 ><I
7677 >enumports command</I
7678 ></TT
7679 > to point to
7680                 a program which should generate a list of ports, one per line,
7681                 to standard output.  This listing will then be used in response
7682                 to the level 1 and 2 EnumPorts() RPC.</P
7683 ><P
7684 >Default: <EM
7685 >no enumports command</EM
7686 ></P
7687 ><P
7688 >Example: <B
7689 CLASS="COMMAND"
7690 >enumports command = /usr/bin/listports
7691                 </B
7692 ></P
7693 ></DD
7694 ><DT
7695 ><A
7696 NAME="EXEC"
7697 ></A
7698 >exec (S)</DT
7699 ><DD
7700 ><P
7701 >This is a synonym for <A
7702 HREF="#PREEXEC"
7703 >               <TT
7704 CLASS="PARAMETER"
7705 ><I
7706 >preexec</I
7707 ></TT
7708 ></A
7709 >.</P
7710 ></DD
7711 ><DT
7712 ><A
7713 NAME="FAKEDIRECTORYCREATETIMES"
7714 ></A
7715 >fake directory create times (S)</DT
7716 ><DD
7717 ><P
7718 >NTFS and Windows VFAT file systems keep a create
7719                 time for all files and directories. This is not the same as the
7720                 ctime - status change time - that Unix keeps, so Samba by default
7721                 reports the earliest of the various times Unix does keep. Setting
7722                 this parameter for a share causes Samba to always report midnight
7723                 1-1-1980 as the create time for directories.</P
7724 ><P
7725 >This option is mainly used as a compatibility option for
7726                 Visual C++ when used against Samba shares. Visual C++ generated
7727                 makefiles have the object directory as a dependency for each object
7728                 file, and a make rule to create the directory. Also, when NMAKE
7729                 compares timestamps it uses the creation time when examining a
7730                 directory. Thus the object directory will be created if it does not
7731                 exist, but once it does exist it will always have an earlier
7732                 timestamp than the object files it contains.</P
7733 ><P
7734 >However, Unix time semantics mean that the create time
7735                 reported by Samba will be updated whenever a file is created or
7736                 or deleted in the directory.  NMAKE finds all object files in
7737                 the object directory.  The timestamp of the last one built is then
7738                 compared to the timestamp of the object dircetory.  If the
7739                 directory's timestamp if newer, then all object files
7740                 will be rebuilt.  Enabling this option
7741                 ensures directories always predate their contents and an NMAKE build
7742                 will proceed as expected.</P
7743 ><P
7744 >Default: <B
7745 CLASS="COMMAND"
7746 >fake directory create times = no</B
7747 ></P
7748 ></DD
7749 ><DT
7750 ><A
7751 NAME="FAKEOPLOCKS"
7752 ></A
7753 >fake oplocks (S)</DT
7754 ><DD
7755 ><P
7756 >Oplocks are the way that SMB clients get permission
7757                 from a server to locally cache file operations. If a server grants
7758                 an oplock (opportunistic lock) then the client is free to assume
7759                 that it is the only one accessing the file and it will aggressively
7760                 cache file data. With some oplock types the client may even cache
7761                 file open/close operations. This can give enormous performance benefits.
7762                 </P
7763 ><P
7764 >When you set <B
7765 CLASS="COMMAND"
7766 >fake oplocks = yes</B
7767 >, <A
7768 HREF="smbd.8.html"
7769 TARGET="_top"
7770 ><B
7771 CLASS="COMMAND"
7772 >smbd(8)</B
7773 ></A
7774 > will
7775                 always grant oplock requests no matter how many clients are using
7776                 the file.</P
7777 ><P
7778 >It is generally much better to use the real <A
7779 HREF="#OPLOCKS"
7780 ><TT
7781 CLASS="PARAMETER"
7782 ><I
7783 >oplocks</I
7784 ></TT
7785 ></A
7786 > support rather
7787                 than this parameter.</P
7788 ><P
7789 >If you enable this option on all read-only shares or
7790                 shares that you know will only be accessed from one client at a
7791                 time such as physically read-only media like CDROMs, you will see
7792                 a big performance improvement on many operations. If you enable
7793                 this option on shares where multiple clients may be accessing the
7794                 files read-write at the same time you can get data corruption. Use
7795                 this option carefully!</P
7796 ><P
7797 >Default: <B
7798 CLASS="COMMAND"
7799 >fake oplocks = no</B
7800 ></P
7801 ></DD
7802 ><DT
7803 ><A
7804 NAME="FOLLOWSYMLINKS"
7805 ></A
7806 >follow symlinks (S)</DT
7807 ><DD
7808 ><P
7809 >This parameter allows the Samba administrator
7810                 to stop <A
7811 HREF="smbd.8.html"
7812 TARGET="_top"
7813 ><B
7814 CLASS="COMMAND"
7815 >smbd(8)</B
7816 ></A
7817 >
7818                 from following symbolic links in a particular share. Setting this
7819                 parameter to <TT
7820 CLASS="CONSTANT"
7821 >no</TT
7822 > prevents any file or directory
7823                 that is a symbolic link from being followed (the user will get an
7824                 error).  This option is very useful to stop users from adding a
7825                 symbolic link to <TT
7826 CLASS="FILENAME"
7827 >/etc/passwd</TT
7828 > in their home
7829                 directory for instance.  However it will slow filename lookups
7830                 down slightly.</P
7831 ><P
7832 >This option is enabled (i.e. <B
7833 CLASS="COMMAND"
7834 >smbd</B
7835 > will
7836                 follow symbolic links) by default.</P
7837 ><P
7838 >Default: <B
7839 CLASS="COMMAND"
7840 >follow symlinks = yes</B
7841 ></P
7842 ></DD
7843 ><DT
7844 ><A
7845 NAME="FORCECREATEMODE"
7846 ></A
7847 >force create mode (S)</DT
7848 ><DD
7849 ><P
7850 >This parameter specifies a set of UNIX mode bit
7851                 permissions that will <EM
7852 >always</EM
7853 > be set on a
7854                 file created by Samba. This is done by bitwise 'OR'ing these bits onto
7855                 the mode bits of a file that is being created or having its
7856                 permissions changed. The default for this parameter is (in octal)
7857                 000. The modes in this parameter are bitwise 'OR'ed onto the file
7858                 mode after the mask set in the <TT
7859 CLASS="PARAMETER"
7860 ><I
7861 >create mask</I
7862 ></TT
7863 >
7864                 parameter is applied.</P
7865 ><P
7866 >Note that by default this parameter does not apply to permissions
7867                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
7868                 this mask on access control lists also, they need to set the <A
7869 HREF="#RESTRICTACLWITHMASK"
7870 ><TT
7871 CLASS="PARAMETER"
7872 ><I
7873 >restrict acl with
7874                 mask</I
7875 ></TT
7876 ></A
7877 > to true.</P
7878 ><P
7879 >See also the parameter <A
7880 HREF="#CREATEMASK"
7881 ><TT
7882 CLASS="PARAMETER"
7883 ><I
7884 >create
7885                 mask</I
7886 ></TT
7887 ></A
7888 > for details on masking mode bits on files.</P
7889 ><P
7890 >See also the <A
7891 HREF="#INHERITPERMISSIONS"
7892 ><TT
7893 CLASS="PARAMETER"
7894 ><I
7895 >inherit
7896                 permissions</I
7897 ></TT
7898 ></A
7899 > parameter.</P
7900 ><P
7901 >Default: <B
7902 CLASS="COMMAND"
7903 >force create mode = 000</B
7904 ></P
7905 ><P
7906 >Example: <B
7907 CLASS="COMMAND"
7908 >force create mode = 0755</B
7909 ></P
7910 ><P
7911 >would force all created files to have read and execute
7912                 permissions set for 'group' and 'other' as well as the
7913                 read/write/execute bits set for the 'user'.</P
7914 ></DD
7915 ><DT
7916 ><A
7917 NAME="FORCEDIRECTORYMODE"
7918 ></A
7919 >force directory mode (S)</DT
7920 ><DD
7921 ><P
7922 >This parameter specifies a set of UNIX mode bit
7923                 permissions that will <EM
7924 >always</EM
7925 > be set on a directory
7926                 created by Samba. This is done by bitwise 'OR'ing these bits onto the
7927                 mode bits of a directory that is being created. The default for this
7928                 parameter is (in octal) 0000 which will not add any extra permission
7929                 bits to a created directory. This operation is done after the mode
7930                 mask in the parameter <TT
7931 CLASS="PARAMETER"
7932 ><I
7933 >directory mask</I
7934 ></TT
7935 > is
7936                 applied.</P
7937 ><P
7938 >Note that by default this parameter does not apply to permissions
7939                 set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
7940                 this mask on access control lists also, they need to set the <A
7941 HREF="#RESTRICTACLWITHMASK"
7942 ><TT
7943 CLASS="PARAMETER"
7944 ><I
7945 >restrict acl with
7946                 mask</I
7947 ></TT
7948 ></A
7949 > to true.</P
7950 ><P
7951 >See also the parameter <A
7952 HREF="#DIRECTORYMASK"
7953 ><TT
7954 CLASS="PARAMETER"
7955 ><I
7956 >               directory mask</I
7957 ></TT
7958 ></A
7959 > for details on masking mode bits
7960                 on created directories.</P
7961 ><P
7962 >See also the <A
7963 HREF="#INHERITPERMISSIONS"
7964 ><TT
7965 CLASS="PARAMETER"
7966 ><I
7967 >               inherit permissions</I
7968 ></TT
7969 ></A
7970 > parameter.</P
7971 ><P
7972 >Default: <B
7973 CLASS="COMMAND"
7974 >force directory mode = 000</B
7975 ></P
7976 ><P
7977 >Example: <B
7978 CLASS="COMMAND"
7979 >force directory mode = 0755</B
7980 ></P
7981 ><P
7982 >would force all created directories to have read and execute
7983                 permissions set for 'group' and 'other' as well as the
7984                 read/write/execute bits set for the 'user'.</P
7985 ></DD
7986 ><DT
7987 ><A
7988 NAME="FORCEDIRECTORYSECURITYMODE"
7989 ></A
7990 >force directory
7991                 security mode (S)</DT
7992 ><DD
7993 ><P
7994 >This parameter controls what UNIX permission bits
7995                 can be modified when a Windows NT client is manipulating the UNIX
7996                 permission on a directory using the native NT security dialog box.</P
7997 ><P
7998 >This parameter is applied as a mask (OR'ed with) to the
7999                 changed permission bits, thus forcing any bits in this mask that
8000                 the user may have modified to be on. Essentially, one bits in this
8001                 mask may be treated as a set of bits that, when modifying security
8002                 on a directory, the user has always set to be 'on'.</P
8003 ><P
8004 >If not set explicitly this parameter is set to the same
8005                 value as the <A
8006 HREF="#FORCEDIRECTORYMODE"
8007 ><TT
8008 CLASS="PARAMETER"
8009 ><I
8010 >force
8011                 directory mode</I
8012 ></TT
8013 ></A
8014 > parameter. To allow
8015                 a user to modify all the user/group/world permissions on a
8016                 directory without restrictions, set this parameter to 000.</P
8017 ><P
8018 ><EM
8019 >Note</EM
8020 > that users who can access the
8021                 Samba server through other means can easily bypass this restriction,
8022                 so it is primarily useful for standalone "appliance" systems.
8023                 Administrators of most normal systems will probably want to set
8024                 it to 0000.</P
8025 ><P
8026 >See also the <A
8027 HREF="#DIRECTORYSECURITYMASK"
8028 ><TT
8029 CLASS="PARAMETER"
8030 ><I
8031 >               directory security mask</I
8032 ></TT
8033 ></A
8034 >, <A
8035 HREF="#SECURITYMASK"
8036 >               <TT
8037 CLASS="PARAMETER"
8038 ><I
8039 >security mask</I
8040 ></TT
8041 ></A
8042 >,
8043                 <A
8044 HREF="#FORCESECURITYMODE"
8045 ><TT
8046 CLASS="PARAMETER"
8047 ><I
8048 >force security mode
8049                 </I
8050 ></TT
8051 ></A
8052 > parameters.</P
8053 ><P
8054 >Default: <B
8055 CLASS="COMMAND"
8056 >force directory security mode = &#60;same as
8057                 force directory mode&#62;</B
8058 ></P
8059 ><P
8060 >Example: <B
8061 CLASS="COMMAND"
8062 >force directory security mode = 0</B
8063 ></P
8064 ></DD
8065 ><DT
8066 ><A
8067 NAME="FORCEGROUP"
8068 ></A
8069 >force group (S)</DT
8070 ><DD
8071 ><P
8072 >This specifies a UNIX group name that will be
8073                 assigned as the default primary group for all users connecting
8074                 to this service. This is useful for sharing files by ensuring
8075                 that all access to files on service will use the named group for
8076                 their permissions checking. Thus, by assigning permissions for this
8077                 group to the files and directories within this service the Samba
8078                 administrator can restrict or allow sharing of these files.</P
8079 ><P
8080 >In Samba 2.0.5 and above this parameter has extended
8081                 functionality in the following way. If the group name listed here
8082                 has a '+' character prepended to it then the current user accessing
8083                 the share only has the primary group default assigned to this group
8084                 if they are already assigned as a member of that group. This allows
8085                 an administrator to decide that only users who are already in a
8086                 particular group will create files with group ownership set to that
8087                 group. This gives a finer granularity of ownership assignment. For
8088                 example, the setting <TT
8089 CLASS="FILENAME"
8090 >force group = +sys</TT
8091 > means
8092                 that only users who are already in group sys will have their default
8093                 primary group assigned to sys when accessing this Samba share. All
8094                 other users will retain their ordinary primary group.</P
8095 ><P
8096 >If the <A
8097 HREF="#FORCEUSER"
8098 ><TT
8099 CLASS="PARAMETER"
8100 ><I
8101 >force user
8102                 </I
8103 ></TT
8104 ></A
8105 > parameter is also set the group specified in
8106                 <TT
8107 CLASS="PARAMETER"
8108 ><I
8109 >force group</I
8110 ></TT
8111 > will override the primary group
8112                 set in <TT
8113 CLASS="PARAMETER"
8114 ><I
8115 >force user</I
8116 ></TT
8117 >.</P
8118 ><P
8119 >See also <A
8120 HREF="#FORCEUSER"
8121 ><TT
8122 CLASS="PARAMETER"
8123 ><I
8124 >force
8125                 user</I
8126 ></TT
8127 ></A
8128 >.</P
8129 ><P
8130 >Default: <EM
8131 >no forced group</EM
8132 ></P
8133 ><P
8134 >Example: <B
8135 CLASS="COMMAND"
8136 >force group = agroup</B
8137 ></P
8138 ></DD
8139 ><DT
8140 ><A
8141 NAME="FORCESECURITYMODE"
8142 ></A
8143 >force security mode (S)</DT
8144 ><DD
8145 ><P
8146 >This parameter controls what UNIX permission
8147                 bits can be modified when a Windows NT client is manipulating
8148                 the UNIX permission on a file using the native NT security dialog
8149                 box.</P
8150 ><P
8151 >This parameter is applied as a mask (OR'ed with) to the
8152                 changed permission bits, thus forcing any bits in this mask that
8153                 the user may have modified to be on. Essentially, one bits in this
8154                 mask may be treated as a set of bits that, when modifying security
8155                 on a file, the user has always set to be 'on'.</P
8156 ><P
8157 >If not set explicitly this parameter is set to the same
8158                 value as the <A
8159 HREF="#FORCECREATEMODE"
8160 ><TT
8161 CLASS="PARAMETER"
8162 ><I
8163 >force
8164                 create mode</I
8165 ></TT
8166 ></A
8167 > parameter. To allow a user to
8168                 modify all the user/group/world permissions on a file, with no
8169                 restrictions set this parameter to 000.</P
8170 ><P
8171 ><EM
8172 >Note</EM
8173 > that users who can access
8174                 the Samba server through other means can easily bypass this restriction,
8175                 so it is primarily useful for standalone "appliance" systems.
8176                 Administrators of most normal systems will probably want to set
8177                 it to 0000.</P
8178 ><P
8179 >See also the <A
8180 HREF="#FORCEDIRECTORYSECURITYMODE"
8181 ><TT
8182 CLASS="PARAMETER"
8183 ><I
8184 >               force directory security mode</I
8185 ></TT
8186 ></A
8187 >,
8188                 <A
8189 HREF="#DIRECTORYSECURITYMASK"
8190 ><TT
8191 CLASS="PARAMETER"
8192 ><I
8193 >directory security
8194                 mask</I
8195 ></TT
8196 ></A
8197 >, <A
8198 HREF="#SECURITYMASK"
8199 ><TT
8200 CLASS="PARAMETER"
8201 ><I
8202 >               security mask</I
8203 ></TT
8204 ></A
8205 > parameters.</P
8206 ><P
8207 >Default: <B
8208 CLASS="COMMAND"
8209 >force security mode = &#60;same as force
8210                 create mode&#62;</B
8211 ></P
8212 ><P
8213 >Example: <B
8214 CLASS="COMMAND"
8215 >force security mode = 0</B
8216 ></P
8217 ></DD
8218 ><DT
8219 ><A
8220 NAME="FORCEUSER"
8221 ></A
8222 >force user (S)</DT
8223 ><DD
8224 ><P
8225 >This specifies a UNIX user name that will be
8226                 assigned as the default user for all users connecting to this service.
8227                 This is useful for sharing files. You should also use it carefully
8228                 as using it incorrectly can cause security problems.</P
8229 ><P
8230 >This user name only gets used once a connection is established.
8231                 Thus clients still need to connect as a valid user and supply a
8232                 valid password. Once connected, all file operations will be performed
8233                 as the "forced user", no matter what username the client connected
8234                 as.  This can be very useful.</P
8235 ><P
8236 >In Samba 2.0.5 and above this parameter also causes the
8237                 primary group of the forced user to be used as the primary group
8238                 for all file activity. Prior to 2.0.5 the primary group was left
8239                 as the primary group of the connecting user (this was a bug).</P
8240 ><P
8241 >See also <A
8242 HREF="#FORCEGROUP"
8243 ><TT
8244 CLASS="PARAMETER"
8245 ><I
8246 >force group
8247                 </I
8248 ></TT
8249 ></A
8250 ></P
8251 ><P
8252 >Default: <EM
8253 >no forced user</EM
8254 ></P
8255 ><P
8256 >Example: <B
8257 CLASS="COMMAND"
8258 >force user = auser</B
8259 ></P
8260 ></DD
8261 ><DT
8262 ><A
8263 NAME="FSTYPE"
8264 ></A
8265 >fstype (S)</DT
8266 ><DD
8267 ><P
8268 >This parameter allows the administrator to
8269                 configure the string that specifies the type of filesystem a share
8270                 is using that is reported by <A
8271 HREF="smbd.8.html"
8272 TARGET="_top"
8273 ><B
8274 CLASS="COMMAND"
8275 >smbd(8)
8276                 </B
8277 ></A
8278 > when a client queries the filesystem type
8279                 for a share. The default type is <TT
8280 CLASS="CONSTANT"
8281 >NTFS</TT
8282 > for
8283                 compatibility with Windows NT but this can be changed to other
8284                 strings such as <TT
8285 CLASS="CONSTANT"
8286 >Samba</TT
8287 > or <TT
8288 CLASS="CONSTANT"
8289 >FAT
8290                 </TT
8291 > if required.</P
8292 ><P
8293 >Default: <B
8294 CLASS="COMMAND"
8295 >fstype = NTFS</B
8296 ></P
8297 ><P
8298 >Example: <B
8299 CLASS="COMMAND"
8300 >fstype = Samba</B
8301 ></P
8302 ></DD
8303 ><DT
8304 ><A
8305 NAME="GETWDCACHE"
8306 ></A
8307 >getwd cache (G)</DT
8308 ><DD
8309 ><P
8310 >This is a tuning option. When this is enabled a
8311                 caching algorithm will be used to reduce the time taken for getwd()
8312                 calls. This can have a significant impact on performance, especially
8313                 when the <A
8314 HREF="#WIDELINKS"
8315 ><TT
8316 CLASS="PARAMETER"
8317 ><I
8318 >wide links</I
8319 ></TT
8320 >
8321                 </A
8322 >parameter is set to <TT
8323 CLASS="CONSTANT"
8324 >False</TT
8325 >.</P
8326 ><P
8327 >Default: <B
8328 CLASS="COMMAND"
8329 >getwd cache = yes</B
8330 ></P
8331 ></DD
8332 ><DT
8333 ><A
8334 NAME="GROUP"
8335 ></A
8336 >group (S)</DT
8337 ><DD
8338 ><P
8339 >Synonym for <A
8340 HREF="#FORCEGROUP"
8341 ><TT
8342 CLASS="PARAMETER"
8343 ><I
8344 >force
8345                 group</I
8346 ></TT
8347 ></A
8348 >.</P
8349 ></DD
8350 ><DT
8351 ><A
8352 NAME="GUESTACCOUNT"
8353 ></A
8354 >guest account (S)</DT
8355 ><DD
8356 ><P
8357 >This is a username which will be used for access
8358                 to services which are specified as <A
8359 HREF="#GUESTOK"
8360 ><TT
8361 CLASS="PARAMETER"
8362 ><I
8363 >               guest ok</I
8364 ></TT
8365 ></A
8366 > (see below). Whatever privileges this
8367                 user has will be available to any client connecting to the guest service.
8368                 Typically this user will exist in the password file, but will not
8369                 have a valid login. The user account "ftp" is often a good choice
8370                 for this parameter. If a username is specified in a given service,
8371                 the specified username overrides this one.</P
8372 ><P
8373 >One some systems the default guest account "nobody" may not
8374                 be able to print. Use another account in this case. You should test
8375                 this by trying to log in as your guest user (perhaps by using the
8376                 <B
8377 CLASS="COMMAND"
8378 >su -</B
8379 > command) and trying to print using the
8380                 system print command such as <B
8381 CLASS="COMMAND"
8382 >lpr(1)</B
8383 > or <B
8384 CLASS="COMMAND"
8385 >               lp(1)</B
8386 >.</P
8387 ><P
8388 >Default: <EM
8389 >specified at compile time, usually
8390                 "nobody"</EM
8391 ></P
8392 ><P
8393 >Example: <B
8394 CLASS="COMMAND"
8395 >guest account = ftp</B
8396 ></P
8397 ></DD
8398 ><DT
8399 ><A
8400 NAME="GUESTOK"
8401 ></A
8402 >guest ok (S)</DT
8403 ><DD
8404 ><P
8405 >If this parameter is <TT
8406 CLASS="CONSTANT"
8407 >yes</TT
8408 > for
8409                 a service, then no password is required to connect to the service.
8410                 Privileges will be those of the <A
8411 HREF="#GUESTACCOUNT"
8412 ><TT
8413 CLASS="PARAMETER"
8414 ><I
8415 >               guest account</I
8416 ></TT
8417 ></A
8418 >.</P
8419 ><P
8420 >See the section below on <A
8421 HREF="#SECURITY"
8422 ><TT
8423 CLASS="PARAMETER"
8424 ><I
8425 >               security</I
8426 ></TT
8427 ></A
8428 > for more information about this option.
8429                 </P
8430 ><P
8431 >Default: <B
8432 CLASS="COMMAND"
8433 >guest ok = no</B
8434 ></P
8435 ></DD
8436 ><DT
8437 ><A
8438 NAME="GUESTONLY"
8439 ></A
8440 >guest only (S)</DT
8441 ><DD
8442 ><P
8443 >If this parameter is <TT
8444 CLASS="CONSTANT"
8445 >yes</TT
8446 > for
8447                 a service, then only guest connections to the service are permitted.
8448                 This parameter will have no effect if <A
8449 HREF="#GUESTOK"
8450 >               <TT
8451 CLASS="PARAMETER"
8452 ><I
8453 >guest ok</I
8454 ></TT
8455 ></A
8456 > is not set for the service.</P
8457 ><P
8458 >See the section below on <A
8459 HREF="#SECURITY"
8460 ><TT
8461 CLASS="PARAMETER"
8462 ><I
8463 >               security</I
8464 ></TT
8465 ></A
8466 > for more information about this option.
8467                 </P
8468 ><P
8469 >Default: <B
8470 CLASS="COMMAND"
8471 >guest only = no</B
8472 ></P
8473 ></DD
8474 ><DT
8475 ><A
8476 NAME="HIDEDOTFILES"
8477 ></A
8478 >hide dot files (S)</DT
8479 ><DD
8480 ><P
8481 >This is a boolean parameter that controls whether
8482                 files starting with a dot appear as hidden files.</P
8483 ><P
8484 >Default: <B
8485 CLASS="COMMAND"
8486 >hide dot files = yes</B
8487 ></P
8488 ></DD
8489 ><DT
8490 ><A
8491 NAME="HIDEFILES"
8492 ></A
8493 >hide files(S)</DT
8494 ><DD
8495 ><P
8496 >This is a list of files or directories that are not
8497                 visible but are accessible.  The DOS 'hidden' attribute is applied
8498                 to any files or directories that match.</P
8499 ><P
8500 >Each entry in the list must be separated by a '/',
8501                 which allows spaces to be included in the entry.  '*'
8502                 and '?' can be used to specify multiple files or directories
8503                 as in DOS wildcards.</P
8504 ><P
8505 >Each entry must be a Unix path, not a DOS path and must
8506                 not include the Unix directory separator '/'.</P
8507 ><P
8508 >Note that the case sensitivity option is applicable
8509                 in hiding files.</P
8510 ><P
8511 >Setting this parameter will affect the performance of Samba,
8512                 as it will be forced to check all files and directories for a match
8513                 as they are scanned.</P
8514 ><P
8515 >See also <A
8516 HREF="#HIDEDOTFILES"
8517 ><TT
8518 CLASS="PARAMETER"
8519 ><I
8520 >hide
8521                 dot files</I
8522 ></TT
8523 ></A
8524 >, <A
8525 HREF="#VETOFILES"
8526 ><TT
8527 CLASS="PARAMETER"
8528 ><I
8529 >               veto files</I
8530 ></TT
8531 ></A
8532 > and <A
8533 HREF="#CASESENSITIVE"
8534 >               <TT
8535 CLASS="PARAMETER"
8536 ><I
8537 >case sensitive</I
8538 ></TT
8539 ></A
8540 >.</P
8541 ><P
8542 >Default: <EM
8543 >no file are hidden</EM
8544 ></P
8545 ><P
8546 >Example: <B
8547 CLASS="COMMAND"
8548 >hide files =
8549                 /.*/DesktopFolderDB/TrashFor%m/resource.frk/</B
8550 ></P
8551 ><P
8552 >The above example is based on files that the Macintosh
8553                 SMB client (DAVE) available from <A
8554 HREF="http://www.thursby.com"
8555 TARGET="_top"
8556 >
8557                 Thursby</A
8558 > creates for internal use, and also still hides
8559                 all files beginning with a dot.</P
8560 ></DD
8561 ><DT
8562 ><A
8563 NAME="HIDELOCALUSERS"
8564 ></A
8565 >hide local users(G)</DT
8566 ><DD
8567 ><P
8568 >This parameter toggles the hiding of local UNIX
8569                 users (root, wheel, floppy, etc) from remote clients.</P
8570 ><P
8571 >Default: <B
8572 CLASS="COMMAND"
8573 >hide local users = no</B
8574 ></P
8575 ></DD
8576 ><DT
8577 ><A
8578 NAME="HOMEDIRMAP"
8579 ></A
8580 >homedir map (G)</DT
8581 ><DD
8582 ><P
8583 >If<A
8584 HREF="#NISHOMEDIR"
8585 ><TT
8586 CLASS="PARAMETER"
8587 ><I
8588 >nis homedir
8589                 </I
8590 ></TT
8591 ></A
8592 > is <TT
8593 CLASS="CONSTANT"
8594 >True</TT
8595 >, and <A
8596 HREF="smbd.8.html"
8597 TARGET="_top"
8598 ><B
8599 CLASS="COMMAND"
8600 >smbd(8)</B
8601 ></A
8602 > is also acting
8603                 as a Win95/98 <TT
8604 CLASS="PARAMETER"
8605 ><I
8606 >logon server</I
8607 ></TT
8608 > then this parameter
8609                 specifies the NIS (or YP) map from which the server for the user's
8610                 home directory should be extracted.  At present, only the Sun
8611                 auto.home map format is understood. The form of the map is:</P
8612 ><P
8613 ><B
8614 CLASS="COMMAND"
8615 >username       server:/some/file/system</B
8616 ></P
8617 ><P
8618 >and the program will extract the servername from before
8619                 the first ':'.  There should probably be a better parsing system
8620                 that copes with different map formats and also Amd (another
8621                 automounter) maps.</P
8622 ><P
8623 ><EM
8624 >NOTE :</EM
8625 >A working NIS client is required on
8626                 the system for this option to work.</P
8627 ><P
8628 >See also <A
8629 HREF="#NISHOMEDIR"
8630 ><TT
8631 CLASS="PARAMETER"
8632 ><I
8633 >nis homedir</I
8634 ></TT
8635 >
8636                 </A
8637 >, <A
8638 HREF="#DOMAINLOGONS"
8639 ><TT
8640 CLASS="PARAMETER"
8641 ><I
8642 >domain logons</I
8643 ></TT
8644 >
8645                 </A
8646 >.</P
8647 ><P
8648 >Default: <B
8649 CLASS="COMMAND"
8650 >homedir map = &#60;empty string&#62;</B
8651 ></P
8652 ><P
8653 >Example: <B
8654 CLASS="COMMAND"
8655 >homedir map = amd.homedir</B
8656 ></P
8657 ></DD
8658 ><DT
8659 ><A
8660 NAME="HOSTMSDFS"
8661 ></A
8662 >host msdfs (G)</DT
8663 ><DD
8664 ><P
8665 >This boolean parameter is only available
8666                 if Samba has been configured and compiled with the <B
8667 CLASS="COMMAND"
8668 >               --with-msdfs</B
8669 > option. If set to <TT
8670 CLASS="CONSTANT"
8671 >yes</TT
8672 >,
8673                 Samba will act as a Dfs server, and  allow Dfs-aware clients
8674                 to browse Dfs trees hosted on the server.</P
8675 ><P
8676 >See also the <A
8677 HREF="#MSDFSROOT"
8678 ><TT
8679 CLASS="PARAMETER"
8680 ><I
8681 >               msdfs root</I
8682 ></TT
8683 ></A
8684 > share  level  parameter.  For
8685                 more  information  on  setting  up a Dfs tree on Samba,
8686                 refer to <A
8687 HREF="msdfs_setup.html"
8688 TARGET="_top"
8689 >msdfs_setup.html</A
8690 >.
8691                 </P
8692 ><P
8693 >Default: <B
8694 CLASS="COMMAND"
8695 >host msdfs = no</B
8696 ></P
8697 ></DD
8698 ><DT
8699 ><A
8700 NAME="HOSTSALLOW"
8701 ></A
8702 >hosts allow (S)</DT
8703 ><DD
8704 ><P
8705 >A synonym for this parameter is <TT
8706 CLASS="PARAMETER"
8707 ><I
8708 >allow
8709                 hosts</I
8710 ></TT
8711 >.</P
8712 ><P
8713 >This parameter is a comma, space, or tab delimited
8714                 set of hosts which are permitted to access a service.</P
8715 ><P
8716 >If specified in the [global] section then it will
8717                 apply to all services, regardless of whether the individual
8718                 service has a different setting.</P
8719 ><P
8720 >You can specify the hosts by name or IP number. For
8721                 example, you could restrict access to only the hosts on a
8722                 Class C subnet with something like <B
8723 CLASS="COMMAND"
8724 >allow hosts = 150.203.5.
8725                 </B
8726 >. The full syntax of the list is described in the man
8727                 page <TT
8728 CLASS="FILENAME"
8729 >hosts_access(5)</TT
8730 >. Note that this man
8731                 page may not be present on your system, so a brief description will
8732                 be given here also.</P
8733 ><P
8734 >Note that the localhost address 127.0.0.1 will always
8735                 be allowed access unless specifically denied by a <A
8736 HREF="#HOSTSDENY"
8737 ><TT
8738 CLASS="PARAMETER"
8739 ><I
8740 >hosts deny</I
8741 ></TT
8742 ></A
8743 > option.</P
8744 ><P
8745 >You can also specify hosts by network/netmask pairs and
8746                 by netgroup names if your system supports netgroups. The
8747                 <EM
8748 >EXCEPT</EM
8749 > keyword can also be used to limit a
8750                 wildcard list. The following examples may provide some help:</P
8751 ><P
8752 >Example 1: allow all IPs in 150.203.*.*; except one</P
8753 ><P
8754 ><B
8755 CLASS="COMMAND"
8756 >hosts allow = 150.203. EXCEPT 150.203.6.66</B
8757 ></P
8758 ><P
8759 >Example 2: allow hosts that match the given network/netmask</P
8760 ><P
8761 ><B
8762 CLASS="COMMAND"
8763 >hosts allow = 150.203.15.0/255.255.255.0</B
8764 ></P
8765 ><P
8766 >Example 3: allow a couple of hosts</P
8767 ><P
8768 ><B
8769 CLASS="COMMAND"
8770 >hosts allow = lapland, arvidsjaur</B
8771 ></P
8772 ><P
8773 >Example 4: allow only hosts in NIS netgroup "foonet", but
8774                 deny access from one particular host</P
8775 ><P
8776 ><B
8777 CLASS="COMMAND"
8778 >hosts allow = @foonet</B
8779 ></P
8780 ><P
8781 ><B
8782 CLASS="COMMAND"
8783 >hosts deny = pirate</B
8784 ></P
8785 ><P
8786 >Note that access still requires suitable user-level passwords.</P
8787 ><P
8788 >See <A
8789 HREF="testparm.1.html"
8790 TARGET="_top"
8791 ><B
8792 CLASS="COMMAND"
8793 >testparm(1)</B
8794 >
8795                 </A
8796 > for a way of testing your host access to see if it does
8797                 what you expect.</P
8798 ><P
8799 >Default: <EM
8800 >none (i.e., all hosts permitted access)
8801                 </EM
8802 ></P
8803 ><P
8804 >Example: <B
8805 CLASS="COMMAND"
8806 >allow hosts = 150.203.5. myhost.mynet.edu.au
8807                 </B
8808 ></P
8809 ></DD
8810 ><DT
8811 ><A
8812 NAME="HOSTSDENY"
8813 ></A
8814 >hosts deny (S)</DT
8815 ><DD
8816 ><P
8817 >The opposite of <TT
8818 CLASS="PARAMETER"
8819 ><I
8820 >hosts allow</I
8821 ></TT
8822 >
8823                 - hosts listed here are <EM
8824 >NOT</EM
8825 > permitted access to
8826                 services unless the specific services have their own lists to override
8827                 this one. Where the lists conflict, the <TT
8828 CLASS="PARAMETER"
8829 ><I
8830 >allow</I
8831 ></TT
8832 >
8833                 list takes precedence.</P
8834 ><P
8835 >Default: <EM
8836 >none (i.e., no hosts specifically excluded)
8837                 </EM
8838 ></P
8839 ><P
8840 >Example: <B
8841 CLASS="COMMAND"
8842 >hosts deny = 150.203.4. badhost.mynet.edu.au
8843                 </B
8844 ></P
8845 ></DD
8846 ><DT
8847 ><A
8848 NAME="HOSTSEQUIV"
8849 ></A
8850 >hosts equiv (G)</DT
8851 ><DD
8852 ><P
8853 >If this global parameter is a non-null string,
8854                 it specifies the name of a file to read for the names of hosts
8855                 and users who will be allowed access without specifying a password.
8856                 </P
8857 ><P
8858 >This is not be confused with <A
8859 HREF="#HOSTSALLOW"
8860 >               <TT
8861 CLASS="PARAMETER"
8862 ><I
8863 >hosts allow</I
8864 ></TT
8865 ></A
8866 > which is about hosts
8867                 access to services and is more useful for guest services. <TT
8868 CLASS="PARAMETER"
8869 ><I
8870 >               hosts equiv</I
8871 ></TT
8872 > may be useful for NT clients which will
8873                 not supply passwords to samba.</P
8874 ><P
8875 ><EM
8876 >NOTE :</EM
8877 > The use of <TT
8878 CLASS="PARAMETER"
8879 ><I
8880 >hosts equiv
8881                 </I
8882 ></TT
8883 > can be a major security hole. This is because you are
8884                 trusting the PC to supply the correct username. It is very easy to
8885                 get a PC to supply a false username. I recommend that the
8886                 <TT
8887 CLASS="PARAMETER"
8888 ><I
8889 >hosts equiv</I
8890 ></TT
8891 > option be only used if you really
8892                 know what you are doing, or perhaps on a home network where you trust
8893                 your spouse and kids. And only if you <EM
8894 >really</EM
8895 > trust
8896                 them :-).</P
8897 ><P
8898 >Default: <EM
8899 >no host equivalences</EM
8900 ></P
8901 ><P
8902 >Example: <B
8903 CLASS="COMMAND"
8904 >hosts equiv = /etc/hosts.equiv</B
8905 ></P
8906 ></DD
8907 ><DT
8908 ><A
8909 NAME="INCLUDE"
8910 ></A
8911 >include (G)</DT
8912 ><DD
8913 ><P
8914 >This allows you to include one config file
8915                 inside another.  The file is included literally, as though typed
8916                 in place.</P
8917 ><P
8918 >It takes the standard substitutions, except <TT
8919 CLASS="PARAMETER"
8920 ><I
8921 >%u
8922                 </I
8923 ></TT
8924 >, <TT
8925 CLASS="PARAMETER"
8926 ><I
8927 >%P</I
8928 ></TT
8929 > and <TT
8930 CLASS="PARAMETER"
8931 ><I
8932 >%S</I
8933 ></TT
8934 >.
8935                 </P
8936 ><P
8937 >Default: <EM
8938 >no file included</EM
8939 ></P
8940 ><P
8941 >Example: <B
8942 CLASS="COMMAND"
8943 >include = /usr/local/samba/lib/admin_smb.conf
8944                 </B
8945 ></P
8946 ></DD
8947 ><DT
8948 ><A
8949 NAME="INHERITPERMISSIONS"
8950 ></A
8951 >inherit permissions (S)</DT
8952 ><DD
8953 ><P
8954 >The permissions on new files and directories
8955                 are normally governed by <A
8956 HREF="#CREATEMASK"
8957 ><TT
8958 CLASS="PARAMETER"
8959 ><I
8960 >               create mask</I
8961 ></TT
8962 ></A
8963 >, <A
8964 HREF="#DIRECTORYMASK"
8965 >               <TT
8966 CLASS="PARAMETER"
8967 ><I
8968 >directory mask</I
8969 ></TT
8970 ></A
8971 >, <A
8972 HREF="#FORCECREATEMODE"
8973 ><TT
8974 CLASS="PARAMETER"
8975 ><I
8976 >force create mode</I
8977 ></TT
8978 >
8979                 </A
8980 > and <A
8981 HREF="#FORCEDIRECTORYMODE"
8982 ><TT
8983 CLASS="PARAMETER"
8984 ><I
8985 >force
8986                 directory mode</I
8987 ></TT
8988 ></A
8989 > but the boolean inherit
8990                 permissions parameter overrides this.</P
8991 ><P
8992 >New directories inherit the mode of the parent directory,
8993                 including bits such as setgid.</P
8994 ><P
8995 >New files inherit their read/write bits from the parent
8996                 directory.  Their execute bits continue to be determined by
8997                 <A
8998 HREF="#MAPARCHIVE"
8999 ><TT
9000 CLASS="PARAMETER"
9001 ><I
9002 >map archive</I
9003 ></TT
9004 >
9005                 </A
9006 >, <A
9007 HREF="#MAPHIDDEN"
9008 ><TT
9009 CLASS="PARAMETER"
9010 ><I
9011 >map hidden</I
9012 ></TT
9013 >
9014                 </A
9015 > and <A
9016 HREF="#MAPSYSTEM"
9017 ><TT
9018 CLASS="PARAMETER"
9019 ><I
9020 >map system</I
9021 ></TT
9022 >
9023                 </A
9024 > as usual.</P
9025 ><P
9026 >Note that the setuid bit is <EM
9027 >never</EM
9028 > set via
9029                 inheritance (the code explicitly prohibits this).</P
9030 ><P
9031 >This can be particularly useful on large systems with
9032                 many users, perhaps several thousand,to allow a single [homes]
9033                 share to be used flexibly by each user.</P
9034 ><P
9035 >See also <A
9036 HREF="#CREATEMASK"
9037 ><TT
9038 CLASS="PARAMETER"
9039 ><I
9040 >create mask
9041                 </I
9042 ></TT
9043 ></A
9044 >, <A
9045 HREF="#DIRECTORYMASK"
9046 ><TT
9047 CLASS="PARAMETER"
9048 ><I
9049 >               directory mask</I
9050 ></TT
9051 ></A
9052 >, <A
9053 HREF="#FORCECREATEMODE"
9054 >               <TT
9055 CLASS="PARAMETER"
9056 ><I
9057 >force create mode</I
9058 ></TT
9059 ></A
9060 > and <A
9061 HREF="#FORCEDIRECTORYMODE"
9062 ><TT
9063 CLASS="PARAMETER"
9064 ><I
9065 >force directory mode</I
9066 ></TT
9067 >
9068                 </A
9069 >.</P
9070 ><P
9071 >Default: <B
9072 CLASS="COMMAND"
9073 >inherit permissions = no</B
9074 ></P
9075 ></DD
9076 ><DT
9077 ><A
9078 NAME="INTERFACES"
9079 ></A
9080 >interfaces (G)</DT
9081 ><DD
9082 ><P
9083 >This option allows you to override the default
9084                 network interfaces list that Samba will use for browsing, name
9085                 registration and other NBT traffic. By default Samba will query
9086                 the kernel for the list of all active interfaces and use any
9087                 interfaces except 127.0.0.1 that are broadcast capable.</P
9088 ><P
9089 >The option takes a list of interface strings. Each string
9090                 can be in any of the following forms:</P
9091 ><P
9092 ></P
9093 ><UL
9094 ><LI
9095 ><P
9096 >a network interface name (such as eth0).
9097                         This may include shell-like wildcards so eth* will match
9098                         any interface starting with the substring "eth"</P
9099 ></LI
9100 ><LI
9101 ><P
9102 >an IP address. In this case the netmask is
9103                         determined from the list of interfaces obtained from the
9104                         kernel</P
9105 ></LI
9106 ><LI
9107 ><P
9108 >an IP/mask pair. </P
9109 ></LI
9110 ><LI
9111 ><P
9112 >a broadcast/mask pair.</P
9113 ></LI
9114 ></UL
9115 ><P
9116 >The "mask" parameters can either be a bit length (such
9117                 as 24 for a C class network) or a full netmask in dotted
9118                 decimal form.</P
9119 ><P
9120 >The "IP" parameters above can either be a full dotted
9121                 decimal IP address or a hostname which will be looked up via
9122                 the OS's normal hostname resolution mechanisms.</P
9123 ><P
9124 >For example, the following line:</P
9125 ><P
9126 ><B
9127 CLASS="COMMAND"
9128 >interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
9129                 </B
9130 ></P
9131 ><P
9132 >would configure three network interfaces corresponding
9133                 to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10.
9134                 The netmasks of the latter two interfaces would be set to 255.255.255.0.</P
9135 ><P
9136 >See also <A
9137 HREF="#BINDINTERFACESONLY"
9138 ><TT
9139 CLASS="PARAMETER"
9140 ><I
9141 >bind
9142                 interfaces only</I
9143 ></TT
9144 ></A
9145 >.</P
9146 ><P
9147 >Default: <EM
9148 >all active interfaces except 127.0.0.1
9149                 that are broadcast capable</EM
9150 ></P
9151 ></DD
9152 ><DT
9153 ><A
9154 NAME="INVALIDUSERS"
9155 ></A
9156 >invalid users (S)</DT
9157 ><DD
9158 ><P
9159 >This is a list of users that should not be allowed
9160                 to login to this service. This is really a <EM
9161 >paranoid</EM
9162 >
9163                 check to absolutely ensure an improper setting does not breach
9164                 your security.</P
9165 ><P
9166 >A name starting with a '@' is interpreted as an NIS
9167                 netgroup first (if your system supports NIS), and then as a UNIX
9168                 group if the name was not found in the NIS netgroup database.</P
9169 ><P
9170 >A name starting with '+' is interpreted only
9171                 by looking in the UNIX group database. A name starting with
9172                 '&#38;' is interpreted only by looking in the NIS netgroup database
9173                 (this requires NIS to be working on your system). The characters
9174                 '+' and '&#38;' may be used at the start of the name in either order
9175                 so the value <TT
9176 CLASS="PARAMETER"
9177 ><I
9178 >+&#38;group</I
9179 ></TT
9180 > means check the
9181                 UNIX group database, followed by the NIS netgroup database, and
9182                 the value <TT
9183 CLASS="PARAMETER"
9184 ><I
9185 >&#38;+group"</I
9186 ></TT
9187 > means check the NIS
9188                 netgroup database, followed by the UNIX group database (the
9189                 same as the '@' prefix).</P
9190 ><P
9191 >The current servicename is substituted for <TT
9192 CLASS="PARAMETER"
9193 ><I
9194 >%S</I
9195 ></TT
9196 >.
9197                 This is useful in the [homes] section.</P
9198 ><P
9199 >See also <A
9200 HREF="#VALIDUSERS"
9201 ><TT
9202 CLASS="PARAMETER"
9203 ><I
9204 >valid users
9205                 </I
9206 ></TT
9207 ></A
9208 >.</P
9209 ><P
9210 >Default: <EM
9211 >no invalid users</EM
9212 ></P
9213 ><P
9214 >Example: <B
9215 CLASS="COMMAND"
9216 >invalid users = root fred admin @wheel
9217                 </B
9218 ></P
9219 ></DD
9220 ><DT
9221 ><A
9222 NAME="KEEPALIVE"
9223 ></A
9224 >keepalive (G)</DT
9225 ><DD
9226 ><P
9227 >The value of the parameter (an integer) represents
9228                 the number of seconds between <TT
9229 CLASS="PARAMETER"
9230 ><I
9231 >keepalive</I
9232 ></TT
9233 >
9234                 packets. If this parameter is zero, no keepalive packets will be
9235                 sent. Keepalive packets, if sent, allow the server to tell whether
9236                 a client is still present and responding.</P
9237 ><P
9238 >Keepalives should, in general, not be needed if the socket
9239                 being used has the SO_KEEPALIVE attribute set on it (see <A
9240 HREF="#SOCKETOPTIONS"
9241 ><TT
9242 CLASS="PARAMETER"
9243 ><I
9244 >socket options</I
9245 ></TT
9246 ></A
9247 >).
9248                 Basically you should only use this option if you strike difficulties.</P
9249 ><P
9250 >Default: <B
9251 CLASS="COMMAND"
9252 >keepalive = 300</B
9253 ></P
9254 ><P
9255 >Example: <B
9256 CLASS="COMMAND"
9257 >keepalive = 600</B
9258 ></P
9259 ></DD
9260 ><DT
9261 ><A
9262 NAME="KERNELOPLOCKS"
9263 ></A
9264 >kernel oplocks (G)</DT
9265 ><DD
9266 ><P
9267 >For UNIXes that support kernel based <A
9268 HREF="#OPLOCKS"
9269 ><TT
9270 CLASS="PARAMETER"
9271 ><I
9272 >oplocks</I
9273 ></TT
9274 ></A
9275 >
9276                 (currently only IRIX and the Linux 2.4 kernel), this parameter
9277                 allows the use of them to be turned on or off.</P
9278 ><P
9279 >Kernel oplocks support allows Samba <TT
9280 CLASS="PARAMETER"
9281 ><I
9282 >oplocks
9283                 </I
9284 ></TT
9285 > to be broken whenever a local UNIX process or NFS operation
9286                 accesses a file that <A
9287 HREF="smbd.8.html"
9288 TARGET="_top"
9289 ><B
9290 CLASS="COMMAND"
9291 >smbd(8)</B
9292 >
9293                 </A
9294 > has oplocked. This allows complete data consistency between
9295                 SMB/CIFS, NFS and local file access (and is a <EM
9296 >very</EM
9297 >
9298                 cool feature :-).</P
9299 ><P
9300 >This parameter defaults to <TT
9301 CLASS="CONSTANT"
9302 >on</TT
9303 > on systems
9304                 that have the support, and <TT
9305 CLASS="CONSTANT"
9306 >off</TT
9307 > on systems that
9308                 don't. You should never need to touch this parameter.</P
9309 ><P
9310 >See also the <A
9311 HREF="#OPLOCKS"
9312 ><TT
9313 CLASS="PARAMETER"
9314 ><I
9315 >oplocks</I
9316 ></TT
9317 >
9318                 </A
9319 > and <A
9320 HREF="#LEVEL2OPLOCKS"
9321 ><TT
9322 CLASS="PARAMETER"
9323 ><I
9324 >level2 oplocks
9325                 </I
9326 ></TT
9327 ></A
9328 > parameters.</P
9329 ><P
9330 >Default: <B
9331 CLASS="COMMAND"
9332 >kernel oplocks = yes</B
9333 ></P
9334 ></DD
9335 ><DT
9336 ><A
9337 NAME="LANMANAUTH"
9338 ></A
9339 >lanman auth (G)</DT
9340 ><DD
9341 ><P
9342 >This parameter determines whether or not smbd will
9343                 attempt to authentication users using the LANMAN password hash.
9344                 If disabled, only clients which support NT password hashes (e.g. Windows
9345                 NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS
9346                 network client) will be able to connect to the Samba host.</P
9347 ><P
9348 >Default : <B
9349 CLASS="COMMAND"
9350 >lanman auth = yes</B
9351 ></P
9352 ></DD
9353 ><DT
9354 ><A
9355 NAME="LEVEL2OPLOCKS"
9356 ></A
9357 >level2 oplocks (S)</DT
9358 ><DD
9359 ><P
9360 >This parameter controls whether Samba supports
9361                 level2 (read-only) oplocks on a share.</P
9362 ><P
9363 >Level2, or read-only oplocks allow Windows NT clients
9364                 that have an oplock on a file to downgrade from a read-write oplock
9365                 to a read-only oplock once a second client opens the file (instead
9366                 of releasing all oplocks on a second open, as in traditional,
9367                 exclusive oplocks). This allows all openers of the file that
9368                 support level2 oplocks to cache the file for read-ahead only (ie.
9369                 they may not cache writes or lock requests) and increases performance
9370                 for many accesses of files that are not commonly written (such as
9371                 application .EXE files).</P
9372 ><P
9373 >Once one of the clients which have a read-only oplock
9374                 writes to the file all clients are notified (no reply is needed
9375                 or waited for) and told to break their oplocks to "none" and
9376                 delete any read-ahead caches.</P
9377 ><P
9378 >It is recommended that this parameter be turned on
9379                 to speed access to shared executables.</P
9380 ><P
9381 >For more discussions on level2 oplocks see the CIFS spec.</P
9382 ><P
9383 >Currently, if <A
9384 HREF="#KERNELOPLOCKS"
9385 ><TT
9386 CLASS="PARAMETER"
9387 ><I
9388 >kernel
9389                 oplocks</I
9390 ></TT
9391 ></A
9392 > are supported then level2 oplocks are
9393                 not granted (even if this parameter is set to <TT
9394 CLASS="CONSTANT"
9395 >yes</TT
9396 >).
9397                 Note also, the <A
9398 HREF="#OPLOCKS"
9399 ><TT
9400 CLASS="PARAMETER"
9401 ><I
9402 >oplocks</I
9403 ></TT
9404 >
9405                 </A
9406 > parameter must be set to "true" on this share in order for
9407                 this parameter to have any effect.</P
9408 ><P
9409 >See also the <A
9410 HREF="#OPLOCKS"
9411 ><TT
9412 CLASS="PARAMETER"
9413 ><I
9414 >oplocks</I
9415 ></TT
9416 >
9417                 </A
9418 > and <A
9419 HREF="#OPLOCKS"
9420 ><TT
9421 CLASS="PARAMETER"
9422 ><I
9423 >kernel oplocks</I
9424 ></TT
9425 >
9426                 </A
9427 > parameters.</P
9428 ><P
9429 >Default: <B
9430 CLASS="COMMAND"
9431 >level2 oplocks = yes</B
9432 ></P
9433 ></DD
9434 ><DT
9435 ><A
9436 NAME="LMANNOUNCE"
9437 ></A
9438 >lm announce (G)</DT
9439 ><DD
9440 ><P
9441 >This parameter determines if <A
9442 HREF="nmbd.8.html"
9443 TARGET="_top"
9444 >               <B
9445 CLASS="COMMAND"
9446 >nmbd(8)</B
9447 ></A
9448 > will produce Lanman announce
9449                 broadcasts that are needed by OS/2 clients in order for them to see
9450                 the Samba server in their browse list. This parameter can have three
9451                 values, <TT
9452 CLASS="CONSTANT"
9453 >true</TT
9454 >, <TT
9455 CLASS="CONSTANT"
9456 >false</TT
9457 >, or
9458                 <TT
9459 CLASS="CONSTANT"
9460 >auto</TT
9461 >. The default is <TT
9462 CLASS="CONSTANT"
9463 >auto</TT
9464 >.
9465                 If set to <TT
9466 CLASS="CONSTANT"
9467 >false</TT
9468 > Samba will never produce these
9469                 broadcasts. If set to <TT
9470 CLASS="CONSTANT"
9471 >true</TT
9472 > Samba will produce
9473                 Lanman announce broadcasts at a frequency set by the parameter
9474                 <TT
9475 CLASS="PARAMETER"
9476 ><I
9477 >lm interval</I
9478 ></TT
9479 >. If set to <TT
9480 CLASS="CONSTANT"
9481 >auto</TT
9482 >
9483                 Samba will not send Lanman announce broadcasts by default but will
9484                 listen for them. If it hears such a broadcast on the wire it will
9485                 then start sending them at a frequency set by the parameter
9486                 <TT
9487 CLASS="PARAMETER"
9488 ><I
9489 >lm interval</I
9490 ></TT
9491 >.</P
9492 ><P
9493 >See also <A
9494 HREF="#LMINTERVAL"
9495 ><TT
9496 CLASS="PARAMETER"
9497 ><I
9498 >lm interval
9499                 </I
9500 ></TT
9501 ></A
9502 >.</P
9503 ><P
9504 >Default: <B
9505 CLASS="COMMAND"
9506 >lm announce = auto</B
9507 ></P
9508 ><P
9509 >Example: <B
9510 CLASS="COMMAND"
9511 >lm announce = yes</B
9512 ></P
9513 ></DD
9514 ><DT
9515 ><A
9516 NAME="LMINTERVAL"
9517 ></A
9518 >lm interval (G)</DT
9519 ><DD
9520 ><P
9521 >If Samba is set to produce Lanman announce
9522                 broadcasts needed by OS/2 clients (see the <A
9523 HREF="#LMANNOUNCE"
9524 >               <TT
9525 CLASS="PARAMETER"
9526 ><I
9527 >lm announce</I
9528 ></TT
9529 ></A
9530 > parameter) then this
9531                 parameter defines the frequency in seconds with which they will be
9532                 made.  If this is set to zero then no Lanman announcements will be
9533                 made despite the setting of the <TT
9534 CLASS="PARAMETER"
9535 ><I
9536 >lm announce</I
9537 ></TT
9538 >
9539                 parameter.</P
9540 ><P
9541 >See also <A
9542 HREF="#LMANNOUNCE"
9543 ><TT
9544 CLASS="PARAMETER"
9545 ><I
9546 >lm
9547                 announce</I
9548 ></TT
9549 ></A
9550 >.</P
9551 ><P
9552 >Default: <B
9553 CLASS="COMMAND"
9554 >lm interval = 60</B
9555 ></P
9556 ><P
9557 >Example: <B
9558 CLASS="COMMAND"
9559 >lm interval = 120</B
9560 ></P
9561 ></DD
9562 ><DT
9563 ><A
9564 NAME="LOADPRINTERS"
9565 ></A
9566 >load printers (G)</DT
9567 ><DD
9568 ><P
9569 >A boolean variable that controls whether all
9570                 printers in the printcap will be loaded for browsing by default.
9571                 See the <A
9572 HREF="#AEN78"
9573 >printers</A
9574 > section for
9575                 more details.</P
9576 ><P
9577 >Default: <B
9578 CLASS="COMMAND"
9579 >load printers = yes</B
9580 ></P
9581 ></DD
9582 ><DT
9583 ><A
9584 NAME="LOCALMASTER"
9585 ></A
9586 >local master (G)</DT
9587 ><DD
9588 ><P
9589 >This option allows <A
9590 HREF="nmbd.8.html"
9591 TARGET="_top"
9592 ><B
9593 CLASS="COMMAND"
9594 >               nmbd(8)</B
9595 ></A
9596 > to try and become a local master browser
9597                 on a subnet. If set to <TT
9598 CLASS="CONSTANT"
9599 >False</TT
9600 > then <B
9601 CLASS="COMMAND"
9602 >               nmbd</B
9603 > will not attempt to become a local master browser
9604                 on a subnet and will also lose in all browsing elections. By
9605                 default this value is set to true. Setting this value to true doesn't
9606                 mean that Samba will <EM
9607 >become</EM
9608 > the local master
9609                 browser on a subnet, just that <B
9610 CLASS="COMMAND"
9611 >nmbd</B
9612 > will <EM
9613 >               participate</EM
9614 > in elections for local master browser.</P
9615 ><P
9616 >Setting this value to False will cause <B
9617 CLASS="COMMAND"
9618 >nmbd</B
9619 >
9620                 <EM
9621 >never</EM
9622 > to become a local master browser.</P
9623 ><P
9624 >Default: <B
9625 CLASS="COMMAND"
9626 >local master = yes</B
9627 ></P
9628 ></DD
9629 ><DT
9630 ><A
9631 NAME="LOCKDIR"
9632 ></A
9633 >lock dir (G)</DT
9634 ><DD
9635 ><P
9636 >Synonym for <A
9637 HREF="#LOCKDIRECTORY"
9638 ><TT
9639 CLASS="PARAMETER"
9640 ><I
9641 >               lock directory</I
9642 ></TT
9643 ></A
9644 >.</P
9645 ></DD
9646 ><DT
9647 ><A
9648 NAME="LOCKDIRECTORY"
9649 ></A
9650 >lock directory (G)</DT
9651 ><DD
9652 ><P
9653 >This option specifies the directory where lock
9654                 files will be placed.  The lock files are used to implement the
9655                 <A
9656 HREF="#MAXCONNECTIONS"
9657 ><TT
9658 CLASS="PARAMETER"
9659 ><I
9660 >max connections</I
9661 ></TT
9662 >
9663                 </A
9664 > option.</P
9665 ><P
9666 >Default: <B
9667 CLASS="COMMAND"
9668 >lock directory = ${prefix}/var/locks</B
9669 ></P
9670 ><P
9671 >Example: <B
9672 CLASS="COMMAND"
9673 >lock directory = /var/run/samba/locks</B
9674 >
9675                 </P
9676 ></DD
9677 ><DT
9678 ><A
9679 NAME="LOCKING"
9680 ></A
9681 >locking (S)</DT
9682 ><DD
9683 ><P
9684 >This controls whether or not locking will be
9685                 performed by the server in response to lock requests from the
9686                 client.</P
9687 ><P
9688 >If <B
9689 CLASS="COMMAND"
9690 >locking = no</B
9691 >, all lock and unlock
9692                 requests will appear to succeed and all lock queries will report
9693                 that the file in question is available for locking.</P
9694 ><P
9695 >If <B
9696 CLASS="COMMAND"
9697 >locking = yes</B
9698 >, real locking will be performed
9699                 by the server.</P
9700 ><P
9701 >This option <EM
9702 >may</EM
9703 > be useful for read-only
9704                 filesystems which <EM
9705 >may</EM
9706 > not need locking (such as
9707                 cdrom drives), although setting this parameter of <TT
9708 CLASS="CONSTANT"
9709 >no</TT
9710 >
9711                 is not really recommended even in this case.</P
9712 ><P
9713 >Be careful about disabling locking either globally or in a
9714                 specific service, as lack of locking may result in data corruption.
9715                 You should never need to set this parameter.</P
9716 ><P
9717 >Default: <B
9718 CLASS="COMMAND"
9719 >locking = yes</B
9720 ></P
9721 ></DD
9722 ><DT
9723 ><A
9724 NAME="LOGFILE"
9725 ></A
9726 >log file (G)</DT
9727 ><DD
9728 ><P
9729 >This option allows you to override the name
9730                 of the Samba log file (also known as the debug file).</P
9731 ><P
9732 >This option takes the standard substitutions, allowing
9733                 you to have separate log files for each user or machine.</P
9734 ><P
9735 >Example: <B
9736 CLASS="COMMAND"
9737 >log file = /usr/local/samba/var/log.%m
9738                 </B
9739 ></P
9740 ></DD
9741 ><DT
9742 ><A
9743 NAME="LOGLEVEL"
9744 ></A
9745 >log level (G)</DT
9746 ><DD
9747 ><P
9748 >Synonym for <A
9749 HREF="#DEBUGLEVEL"
9750 ><TT
9751 CLASS="PARAMETER"
9752 ><I
9753 >               debug level</I
9754 ></TT
9755 ></A
9756 >.</P
9757 ></DD
9758 ><DT
9759 ><A
9760 NAME="LOGONDRIVE"
9761 ></A
9762 >logon drive (G)</DT
9763 ><DD
9764 ><P
9765 >This parameter specifies the local path to
9766                 which the home directory will be connected (see <A
9767 HREF="#LOGONHOME"
9768 ><TT
9769 CLASS="PARAMETER"
9770 ><I
9771 >logon home</I
9772 ></TT
9773 ></A
9774 >)
9775                 and is only used by NT Workstations. </P
9776 ><P
9777 >Note that this option is only useful if Samba is set up as a
9778                 logon server.</P
9779 ><P
9780 >Default: <B
9781 CLASS="COMMAND"
9782 >logon drive = z:</B
9783 ></P
9784 ><P
9785 >Example: <B
9786 CLASS="COMMAND"
9787 >logon drive = h:</B
9788 ></P
9789 ></DD
9790 ><DT
9791 ><A
9792 NAME="LOGONHOME"
9793 ></A
9794 >logon home (G)</DT
9795 ><DD
9796 ><P
9797 >This parameter specifies the home directory
9798                 location when a Win95/98 or NT Workstation logs into a Samba PDC.
9799                 It allows you to do </P
9800 ><P
9801 ><TT
9802 CLASS="PROMPT"
9803 >C:\&#62; </TT
9804 ><TT
9805 CLASS="USERINPUT"
9806 ><B
9807 >NET USE H: /HOME</B
9808 ></TT
9809 >
9810                 </P
9811 ><P
9812 >from a command prompt, for example.</P
9813 ><P
9814 >This option takes the standard substitutions, allowing
9815                 you to have separate logon scripts for each user or machine.</P
9816 ><P
9817 >This parameter can be used with Win9X workstations to ensure
9818                 that roaming profiles are stored in a subdirectory of the user's
9819                 home directory.  This is done in the following way:</P
9820 ><P
9821 ><B
9822 CLASS="COMMAND"
9823 >logon home = \\%N\%U\profile</B
9824 ></P
9825 ><P
9826 >This tells Samba to return the above string, with
9827                 substitutions made when a client requests the info, generally
9828                 in a NetUserGetInfo request.  Win9X clients truncate the info to
9829                 \\server\share when a user does <B
9830 CLASS="COMMAND"
9831 >net use /home"</B
9832 >
9833                 but use the whole string when dealing with profiles.</P
9834 ><P
9835 >Note that in prior versions of Samba, the <A
9836 HREF="#LOGONPATH"
9837 >               <TT
9838 CLASS="PARAMETER"
9839 ><I
9840 >logon path</I
9841 ></TT
9842 ></A
9843 > was returned rather than
9844                 <TT
9845 CLASS="PARAMETER"
9846 ><I
9847 >logon home</I
9848 ></TT
9849 >.  This broke <B
9850 CLASS="COMMAND"
9851 >net use
9852                 /home</B
9853 > but allowed profiles outside the home directory.
9854                 The current implementation is correct, and can be used for
9855                 profiles if you use the above trick.</P
9856 ><P
9857 >This option is only useful if Samba is set up as a logon
9858                 server.</P
9859 ><P
9860 >Default: <B
9861 CLASS="COMMAND"
9862 >logon home = "\\%N\%U"</B
9863 ></P
9864 ><P
9865 >Example: <B
9866 CLASS="COMMAND"
9867 >logon home = "\\remote_smb_server\%U"</B
9868 >
9869                 </P
9870 ></DD
9871 ><DT
9872 ><A
9873 NAME="LOGONPATH"
9874 ></A
9875 >logon path (G)</DT
9876 ><DD
9877 ><P
9878 >This parameter specifies the home directory
9879                 where roaming profiles (NTuser.dat etc files for Windows NT) are
9880                 stored.  Contrary to previous versions of these manual pages, it has
9881                 nothing to do with Win 9X roaming profiles.  To find out how to
9882                 handle roaming profiles for Win 9X system, see the <A
9883 HREF="#LOGONHOME"
9884 >               <TT
9885 CLASS="PARAMETER"
9886 ><I
9887 >logon home</I
9888 ></TT
9889 ></A
9890 > parameter.</P
9891 ><P
9892 >This option takes the standard substitutions, allowing you
9893                 to have separate logon scripts for each user or machine.  It also
9894                 specifies the directory from which the "Application Data",
9895                 (<TT
9896 CLASS="FILENAME"
9897 >desktop</TT
9898 >, <TT
9899 CLASS="FILENAME"
9900 >start menu</TT
9901 >,
9902                 <TT
9903 CLASS="FILENAME"
9904 >network neighborhood</TT
9905 >, <TT
9906 CLASS="FILENAME"
9907 >programs</TT
9908 >
9909                 and other folders, and their contents, are loaded and displayed on
9910                 your Windows NT client.</P
9911 ><P
9912 >The share and the path must be readable by the user for
9913                 the preferences and directories to be loaded onto the Windows NT
9914                 client.  The share must be writeable when the logs in for the first
9915                 time, in order that the Windows NT client can create the NTuser.dat
9916                 and other directories.</P
9917 ><P
9918 >Thereafter, the directories and any of the contents can,
9919                 if required, be made read-only.  It is not advisable that the
9920                 NTuser.dat file be made read-only - rename it to NTuser.man to
9921                 achieve the desired effect (a <EM
9922 >MAN</EM
9923 >datory
9924                 profile). </P
9925 ><P
9926 >Windows clients can sometimes maintain a connection to
9927                 the [homes] share, even though there is no user logged in.
9928                 Therefore, it is vital that the logon path does not include a
9929                 reference to the homes share (i.e. setting this parameter to
9930                 \%N\%U\profile_path will cause problems).</P
9931 ><P
9932 >This option takes the standard substitutions, allowing
9933                 you to have separate logon scripts for each user or machine.</P
9934 ><P
9935 >Note that this option is only useful if Samba is set up
9936                 as a logon server.</P
9937 ><P
9938 >Default: <B
9939 CLASS="COMMAND"
9940 >logon path = \\%N\%U\profile</B
9941 ></P
9942 ><P
9943 >Example: <B
9944 CLASS="COMMAND"
9945 >logon path = \\PROFILESERVER\PROFILE\%U</B
9946 ></P
9947 ></DD
9948 ><DT
9949 ><A
9950 NAME="LOGONSCRIPT"
9951 ></A
9952 >logon script (G)</DT
9953 ><DD
9954 ><P
9955 >This parameter specifies the batch file (.bat) or
9956                 NT command file (.cmd) to be downloaded and run on a machine when
9957                 a user successfully logs in.  The file must contain the DOS
9958                 style cr/lf line endings. Using a DOS-style editor to create the
9959                 file is recommended.</P
9960 ><P
9961 >The script must be a relative path to the [netlogon]
9962                 service.  If the [netlogon] service specifies a <A
9963 HREF="#PATH"
9964 >               <TT
9965 CLASS="PARAMETER"
9966 ><I
9967 >path</I
9968 ></TT
9969 ></A
9970 > of <TT
9971 CLASS="FILENAME"
9972 >/usr/local/samba/netlogon
9973                 </TT
9974 >, and <B
9975 CLASS="COMMAND"
9976 >logon script = STARTUP.BAT</B
9977 >, then
9978                 the file that will be downloaded is:</P
9979 ><P
9980 ><TT
9981 CLASS="FILENAME"
9982 >/usr/local/samba/netlogon/STARTUP.BAT</TT
9983 ></P
9984 ><P
9985 >The contents of the batch file is entirely your choice.  A
9986                 suggested command would be to add <B
9987 CLASS="COMMAND"
9988 >NET TIME \\SERVER /SET
9989                 /YES</B
9990 >, to force every machine to synchronize clocks with
9991                 the same time server.  Another use would be to add <B
9992 CLASS="COMMAND"
9993 >NET USE
9994                 U: \\SERVER\UTILS</B
9995 > for commonly used utilities, or <B
9996 CLASS="COMMAND"
9997 >               NET USE Q: \\SERVER\ISO9001_QA</B
9998 > for example.</P
9999 ><P
10000 >Note that it is particularly important not to allow write
10001                 access to the [netlogon] share, or to grant users write permission
10002                 on the batch files in a secure environment, as this would allow
10003                 the batch files to be arbitrarily modified and security to be
10004                 breached.</P
10005 ><P
10006 >This option takes the standard substitutions, allowing you
10007                 to have separate logon scripts for each user or machine.</P
10008 ><P
10009 >This option is only useful if Samba is set up as a logon
10010                 server.</P
10011 ><P
10012 >Default: <EM
10013 >no logon script defined</EM
10014 ></P
10015 ><P
10016 >Example: <B
10017 CLASS="COMMAND"
10018 >logon script = scripts\%U.bat</B
10019 ></P
10020 ></DD
10021 ><DT
10022 ><A
10023 NAME="LPPAUSECOMMAND"
10024 ></A
10025 >lppause command (S)</DT
10026 ><DD
10027 ><P
10028 >This parameter specifies the command to be
10029                 executed on the server host in order to stop printing or spooling
10030                 a specific print job.</P
10031 ><P
10032 >This command should be a program or script which takes
10033                 a printer name and job number to pause the print job. One way
10034                 of implementing this is by using job priorities, where jobs
10035                 having a too low priority won't be sent to the printer.</P
10036 ><P
10037 >If a <TT
10038 CLASS="PARAMETER"
10039 ><I
10040 >%p</I
10041 ></TT
10042 > is given then the printername
10043                 is put in its place. A <TT
10044 CLASS="PARAMETER"
10045 ><I
10046 >%j</I
10047 ></TT
10048 > is replaced with
10049                 the job number (an integer).  On HPUX (see <TT
10050 CLASS="PARAMETER"
10051 ><I
10052 >printing=hpux
10053                 </I
10054 ></TT
10055 >), if the <TT
10056 CLASS="PARAMETER"
10057 ><I
10058 >-p%p</I
10059 ></TT
10060 > option is added
10061                 to the lpq command, the job will show up with the correct status, i.e.
10062                 if the job priority is lower than the set fence priority it will
10063                 have the PAUSED status, whereas if  the priority is equal or higher it
10064                 will have the SPOOLED or PRINTING status.</P
10065 ><P
10066 >Note that it is good practice to include the absolute path
10067                 in the lppause command as the PATH may not be available to the server.</P
10068 ><P
10069 >See also the <A
10070 HREF="#PRINTING"
10071 ><TT
10072 CLASS="PARAMETER"
10073 ><I
10074 >printing
10075                 </I
10076 ></TT
10077 ></A
10078 > parameter.</P
10079 ><P
10080 >Default: Currently no default value is given to
10081                 this string, unless the value of the <TT
10082 CLASS="PARAMETER"
10083 ><I
10084 >printing</I
10085 ></TT
10086 >
10087                 parameter is <TT
10088 CLASS="CONSTANT"
10089 >SYSV</TT
10090 >, in which case the default is :</P
10091 ><P
10092 ><B
10093 CLASS="COMMAND"
10094 >lp -i %p-%j -H hold</B
10095 ></P
10096 ><P
10097 >or if the value of the <TT
10098 CLASS="PARAMETER"
10099 ><I
10100 >printing</I
10101 ></TT
10102 > parameter
10103                 is <TT
10104 CLASS="CONSTANT"
10105 >SOFTQ</TT
10106 >, then the default is:</P
10107 ><P
10108 ><B
10109 CLASS="COMMAND"
10110 >qstat -s -j%j -h</B
10111 ></P
10112 ><P
10113 >Example for HPUX: <B
10114 CLASS="COMMAND"
10115 >lppause command = /usr/bin/lpalt
10116                 %p-%j -p0</B
10117 ></P
10118 ></DD
10119 ><DT
10120 ><A
10121 NAME="LPQCACHETIME"
10122 ></A
10123 >lpq cache time (G)</DT
10124 ><DD
10125 ><P
10126 >This controls how long lpq info will be cached
10127                 for to prevent the <B
10128 CLASS="COMMAND"
10129 >lpq</B
10130 > command being called too
10131                 often. A separate cache is kept for each variation of the <B
10132 CLASS="COMMAND"
10133 >               lpq</B
10134 > command used by the system, so if you use different
10135                 <B
10136 CLASS="COMMAND"
10137 >lpq</B
10138 > commands for different users then they won't
10139                 share cache information.</P
10140 ><P
10141 >The cache files are stored in <TT
10142 CLASS="FILENAME"
10143 >/tmp/lpq.xxxx</TT
10144 >
10145                 where xxxx is a hash of the <B
10146 CLASS="COMMAND"
10147 >lpq</B
10148 > command in use.</P
10149 ><P
10150 >The default is 10 seconds, meaning that the cached results
10151                 of a previous identical <B
10152 CLASS="COMMAND"
10153 >lpq</B
10154 > command will be used
10155                 if the cached data is less than 10 seconds old. A large value may
10156                 be advisable if your <B
10157 CLASS="COMMAND"
10158 >lpq</B
10159 > command is very slow.</P
10160 ><P
10161 >A value of 0 will disable caching completely.</P
10162 ><P
10163 >See also the <A
10164 HREF="#PRINTING"
10165 ><TT
10166 CLASS="PARAMETER"
10167 ><I
10168 >printing
10169                 </I
10170 ></TT
10171 ></A
10172 > parameter.</P
10173 ><P
10174 >Default: <B
10175 CLASS="COMMAND"
10176 >lpq cache time = 10</B
10177 ></P
10178 ><P
10179 >Example: <B
10180 CLASS="COMMAND"
10181 >lpq cache time = 30</B
10182 ></P
10183 ></DD
10184 ><DT
10185 ><A
10186 NAME="LPQCOMMAND"
10187 ></A
10188 >lpq command (S)</DT
10189 ><DD
10190 ><P
10191 >This parameter specifies the command to be
10192                 executed on the server host in order to obtain <B
10193 CLASS="COMMAND"
10194 >lpq
10195                 </B
10196 >-style printer status information.</P
10197 ><P
10198 >This command should be a program or script which
10199                 takes a printer name as its only parameter and outputs printer
10200                 status information.</P
10201 ><P
10202 >Currently eight styles of printer status information
10203                 are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX and SOFTQ.
10204                 This covers most UNIX systems. You control which type is expected
10205                 using the <TT
10206 CLASS="PARAMETER"
10207 ><I
10208 >printing =</I
10209 ></TT
10210 > option.</P
10211 ><P
10212 >Some clients (notably Windows for Workgroups) may not
10213                 correctly send the connection number for the printer they are
10214                 requesting status information about. To get around this, the
10215                 server reports on the first printer service connected to by the
10216                 client. This only happens if the connection number sent is invalid.</P
10217 ><P
10218 >If a <TT
10219 CLASS="PARAMETER"
10220 ><I
10221 >%p</I
10222 ></TT
10223 > is given then the printername
10224                 is put in its place. Otherwise it is placed at the end of the
10225                 command.</P
10226 ><P
10227 >Note that it is good practice to include the absolute path
10228                 in the <TT
10229 CLASS="PARAMETER"
10230 ><I
10231 >lpq command</I
10232 ></TT
10233 > as the <TT
10234 CLASS="ENVAR"
10235 >$PATH
10236                 </TT
10237 > may not be available to the server.</P
10238 ><P
10239 >See also the <A
10240 HREF="#PRINTING"
10241 ><TT
10242 CLASS="PARAMETER"
10243 ><I
10244 >printing
10245                 </I
10246 ></TT
10247 ></A
10248 > parameter.</P
10249 ><P
10250 >Default: <EM
10251 >depends on the setting of <TT
10252 CLASS="PARAMETER"
10253 ><I
10254 >               printing</I
10255 ></TT
10256 ></EM
10257 ></P
10258 ><P
10259 >Example: <B
10260 CLASS="COMMAND"
10261 >lpq command = /usr/bin/lpq -P%p</B
10262 ></P
10263 ></DD
10264 ><DT
10265 ><A
10266 NAME="LPRESUMECOMMAND"
10267 ></A
10268 >lpresume command (S)</DT
10269 ><DD
10270 ><P
10271 >This parameter specifies the command to be
10272                 executed on the server host in order to restart or continue
10273                 printing or spooling a specific print job.</P
10274 ><P
10275 >This command should be a program or script which takes
10276                 a printer name and job number to resume the print job. See
10277                 also the <A
10278 HREF="#LPPAUSECOMMAND"
10279 ><TT
10280 CLASS="PARAMETER"
10281 ><I
10282 >lppause command
10283                 </I
10284 ></TT
10285 ></A
10286 > parameter.</P
10287 ><P
10288 >If a <TT
10289 CLASS="PARAMETER"
10290 ><I
10291 >%p</I
10292 ></TT
10293 > is given then the printername
10294                 is put in its place. A <TT
10295 CLASS="PARAMETER"
10296 ><I
10297 >%j</I
10298 ></TT
10299 > is replaced with
10300                 the job number (an integer).</P
10301 ><P
10302 >Note that it is good practice to include the absolute path
10303                 in the <TT
10304 CLASS="PARAMETER"
10305 ><I
10306 >lpresume command</I
10307 ></TT
10308 > as the PATH may not
10309                 be available to the server.</P
10310 ><P
10311 >See also the <A
10312 HREF="#PRINTING"
10313 ><TT
10314 CLASS="PARAMETER"
10315 ><I
10316 >printing
10317                 </I
10318 ></TT
10319 ></A
10320 > parameter.</P
10321 ><P
10322 >Default: Currently no default value is given
10323                 to this string, unless the value of the <TT
10324 CLASS="PARAMETER"
10325 ><I
10326 >printing</I
10327 ></TT
10328 >
10329                 parameter is <TT
10330 CLASS="CONSTANT"
10331 >SYSV</TT
10332 >, in which case the default is :</P
10333 ><P
10334 ><B
10335 CLASS="COMMAND"
10336 >lp -i %p-%j -H resume</B
10337 ></P
10338 ><P
10339 >or if the value of the <TT
10340 CLASS="PARAMETER"
10341 ><I
10342 >printing</I
10343 ></TT
10344 > parameter
10345                 is <TT
10346 CLASS="CONSTANT"
10347 >SOFTQ</TT
10348 >, then the default is:</P
10349 ><P
10350 ><B
10351 CLASS="COMMAND"
10352 >qstat -s -j%j -r</B
10353 ></P
10354 ><P
10355 >Example for HPUX: <B
10356 CLASS="COMMAND"
10357 >lpresume command = /usr/bin/lpalt
10358                 %p-%j -p2</B
10359 ></P
10360 ></DD
10361 ><DT
10362 ><A
10363 NAME="LPRMCOMMAND"
10364 ></A
10365 >lprm command (S)</DT
10366 ><DD
10367 ><P
10368 >This parameter specifies the command to be
10369                 executed on the server host in order to delete a print job.</P
10370 ><P
10371 >This command should be a program or script which takes
10372                 a printer name and job number, and deletes the print job.</P
10373 ><P
10374 >If a <TT
10375 CLASS="PARAMETER"
10376 ><I
10377 >%p</I
10378 ></TT
10379 > is given then the printername
10380                 is put in its place. A <TT
10381 CLASS="PARAMETER"
10382 ><I
10383 >%j</I
10384 ></TT
10385 > is replaced with
10386                 the job number (an integer).</P
10387 ><P
10388 >Note that it is good practice to include the absolute
10389                 path in the <TT
10390 CLASS="PARAMETER"
10391 ><I
10392 >lprm command</I
10393 ></TT
10394 > as the PATH may not be
10395                 available to the server.</P
10396 ><P
10397 >See also the <A
10398 HREF="#PRINTING"
10399 ><TT
10400 CLASS="PARAMETER"
10401 ><I
10402 >printing
10403                 </I
10404 ></TT
10405 ></A
10406 > parameter.</P
10407 ><P
10408 >Default: <EM
10409 >depends on the setting of <TT
10410 CLASS="PARAMETER"
10411 ><I
10412 >printing
10413                 </I
10414 ></TT
10415 ></EM
10416 ></P
10417 ><P
10418 >Example 1: <B
10419 CLASS="COMMAND"
10420 >lprm command = /usr/bin/lprm -P%p %j
10421                 </B
10422 ></P
10423 ><P
10424 >Example 2: <B
10425 CLASS="COMMAND"
10426 >lprm command = /usr/bin/cancel %p-%j
10427                 </B
10428 ></P
10429 ></DD
10430 ><DT
10431 ><A
10432 NAME="MACHINEPASSWORDTIMEOUT"
10433 ></A
10434 >machine password timeout (G)</DT
10435 ><DD
10436 ><P
10437 >If a Samba server is a member of an Windows
10438                 NT Domain (see the <A
10439 HREF="#SECURITYEQUALSDOMAIN"
10440 >security=domain</A
10441 >)
10442                 parameter) then periodically a running <A
10443 HREF="smbd.8.html"
10444 TARGET="_top"
10445 >               smbd(8)</A
10446 > process will try and change the MACHINE ACCOUNT
10447                 PASSWORD stored in the TDB called <TT
10448 CLASS="FILENAME"
10449 >private/secrets.tdb
10450                 </TT
10451 >.  This parameter specifies how often this password
10452                 will be changed, in seconds. The default is one week (expressed in
10453                 seconds), the same as a Windows NT Domain member server.</P
10454 ><P
10455 >See also <A
10456 HREF="smbpasswd.8.html"
10457 TARGET="_top"
10458 ><B
10459 CLASS="COMMAND"
10460 >smbpasswd(8)
10461                 </B
10462 ></A
10463 >, and the <A
10464 HREF="#SECURITYEQUALSDOMAIN"
10465 >               security=domain</A
10466 >) parameter.</P
10467 ><P
10468 >Default: <B
10469 CLASS="COMMAND"
10470 >machine password timeout = 604800</B
10471 ></P
10472 ></DD
10473 ><DT
10474 ><A
10475 NAME="MAGICOUTPUT"
10476 ></A
10477 >magic output (S)</DT
10478 ><DD
10479 ><P
10480 >This parameter specifies the name of a file
10481                 which will contain output created by a magic script (see the
10482                 <A
10483 HREF="#MAGICSCRIPT"
10484 ><TT
10485 CLASS="PARAMETER"
10486 ><I
10487 >magic script</I
10488 ></TT
10489 ></A
10490 >
10491                 parameter below).</P
10492 ><P
10493 >Warning: If two clients use the same <TT
10494 CLASS="PARAMETER"
10495 ><I
10496 >magic script
10497                 </I
10498 ></TT
10499 > in the same directory the output file content
10500                 is undefined.</P
10501 ><P
10502 >Default: <B
10503 CLASS="COMMAND"
10504 >magic output = &#60;magic script name&#62;.out
10505                 </B
10506 ></P
10507 ><P
10508 >Example: <B
10509 CLASS="COMMAND"
10510 >magic output = myfile.txt</B
10511 ></P
10512 ></DD
10513 ><DT
10514 ><A
10515 NAME="MAGICSCRIPT"
10516 ></A
10517 >magic script (S)</DT
10518 ><DD
10519 ><P
10520 >This parameter specifies the name of a file which,
10521                 if opened, will be executed by the server when the file is closed.
10522                 This allows a UNIX script to be sent to the Samba host and
10523                 executed on behalf of the connected user.</P
10524 ><P
10525 >Scripts executed in this way will be deleted upon
10526                 completion assuming that the user has the appripriate level
10527                 of priviledge and the ile permissions allow the deletion.</P
10528 ><P
10529 >If the script generates output, output will be sent to
10530                 the file specified by the <A
10531 HREF="#MAGICOUTPUT"
10532 ><TT
10533 CLASS="PARAMETER"
10534 ><I
10535 >               magic output</I
10536 ></TT
10537 ></A
10538 > parameter (see above).</P
10539 ><P
10540 >Note that some shells are unable to interpret scripts
10541                 containing CR/LF instead of CR as
10542                 the end-of-line marker. Magic scripts must be executable
10543                 <EM
10544 >as is</EM
10545 > on the host, which for some hosts and
10546                 some shells will require filtering at the DOS end.</P
10547 ><P
10548 >Magic scripts are <EM
10549 >EXPERIMENTAL</EM
10550 > and
10551                 should <EM
10552 >NOT</EM
10553 > be relied upon.</P
10554 ><P
10555 >Default: <EM
10556 >None. Magic scripts disabled.</EM
10557 ></P
10558 ><P
10559 >Example: <B
10560 CLASS="COMMAND"
10561 >magic script = user.csh</B
10562 ></P
10563 ></DD
10564 ><DT
10565 ><A
10566 NAME="MANGLECASE"
10567 ></A
10568 >mangle case (S)</DT
10569 ><DD
10570 ><P
10571 >See the section on <A
10572 HREF="#AEN201"
10573 >               NAME MANGLING</A
10574 ></P
10575 ><P
10576 >Default: <B
10577 CLASS="COMMAND"
10578 >mangle case = no</B
10579 ></P
10580 ></DD
10581 ><DT
10582 ><A
10583 NAME="MANGLEDMAP"
10584 ></A
10585 >mangled map (S)</DT
10586 ><DD
10587 ><P
10588 >This is for those who want to directly map UNIX
10589                 file names which can not be represented on Windows/DOS.  The mangling
10590                 of names is not always what is needed.  In particular you may have
10591                 documents with file extensions that differ between DOS and UNIX.
10592                 For example, under UNIX it is common to use <TT
10593 CLASS="FILENAME"
10594 >.html</TT
10595 >
10596                 for HTML files, whereas under Windows/DOS <TT
10597 CLASS="FILENAME"
10598 >.htm</TT
10599 >
10600                 is more commonly used.</P
10601 ><P
10602 >So to map <TT
10603 CLASS="FILENAME"
10604 >html</TT
10605 > to <TT
10606 CLASS="FILENAME"
10607 >htm</TT
10608 >
10609                 you would use:</P
10610 ><P
10611 ><B
10612 CLASS="COMMAND"
10613 >mangled map = (*.html *.htm)</B
10614 ></P
10615 ><P
10616 >One very useful case is to remove the annoying <TT
10617 CLASS="FILENAME"
10618 >;1
10619                 </TT
10620 > off the ends of filenames on some CDROMS (only visible
10621                 under some UNIXes). To do this use a map of (*;1 *;).</P
10622 ><P
10623 >Default: <EM
10624 >no mangled map</EM
10625 ></P
10626 ><P
10627 >Example: <B
10628 CLASS="COMMAND"
10629 >mangled map = (*;1 *;)</B
10630 ></P
10631 ></DD
10632 ><DT
10633 ><A
10634 NAME="MANGLEDNAMES"
10635 ></A
10636 >mangled names (S)</DT
10637 ><DD
10638 ><P
10639 >This controls whether non-DOS names under UNIX
10640                 should be mapped to DOS-compatible names ("mangled") and made visible,
10641                 or whether non-DOS names should simply be ignored.</P
10642 ><P
10643 >See the section on <A
10644 HREF="#AEN201"
10645 >               NAME MANGLING</A
10646 > for details on how to control the mangling process.</P
10647 ><P
10648 >If mangling is used then the mangling algorithm is as follows:</P
10649 ><P
10650 ></P
10651 ><UL
10652 ><LI
10653 ><P
10654 >The first (up to) five alphanumeric characters
10655                         before the rightmost dot of the filename are preserved, forced
10656                         to upper case, and appear as the first (up to) five characters
10657                         of the mangled name.</P
10658 ></LI
10659 ><LI
10660 ><P
10661 >A tilde "~" is appended to the first part of the mangled
10662                         name, followed by a two-character unique sequence, based on the
10663                         original root name (i.e., the original filename minus its final
10664                         extension). The final extension is included in the hash calculation
10665                         only if it contains any upper case characters or is longer than three
10666                         characters.</P
10667 ><P
10668 >Note that the character to use may be specified using
10669                         the <A
10670 HREF="#MANGLINGCHAR"
10671 ><TT
10672 CLASS="PARAMETER"
10673 ><I
10674 >mangling char</I
10675 ></TT
10676 >
10677                         </A
10678 > option, if you don't like '~'.</P
10679 ></LI
10680 ><LI
10681 ><P
10682 >The first three alphanumeric characters of the final
10683                         extension are preserved, forced to upper case and appear as the
10684                         extension of the mangled name. The final extension is defined as that
10685                         part of the original filename after the rightmost dot. If there are no
10686                         dots in the filename, the mangled name will have no extension (except
10687                         in the case of "hidden files" - see below).</P
10688 ></LI
10689 ><LI
10690 ><P
10691 >Files whose UNIX name begins with a dot will be
10692                         presented as DOS hidden files. The mangled name will be created as
10693                         for other filenames, but with the leading dot removed and "___" as
10694                         its extension regardless of actual original extension (that's three
10695                         underscores).</P
10696 ></LI
10697 ></UL
10698 ><P
10699 >The two-digit hash value consists of upper case
10700                 alphanumeric characters.</P
10701 ><P
10702 >This algorithm can cause name collisions only if files
10703                 in a directory share the same first five alphanumeric characters.
10704                 The probability of such a clash is 1/1300.</P
10705 ><P
10706 >The name mangling (if enabled) allows a file to be
10707                 copied between UNIX directories from Windows/DOS while retaining
10708                 the long UNIX filename. UNIX files can be renamed to a new extension
10709                 from Windows/DOS and will retain the same basename. Mangled names
10710                 do not change between sessions.</P
10711 ><P
10712 >Default: <B
10713 CLASS="COMMAND"
10714 >mangled names = yes</B
10715 ></P
10716 ></DD
10717 ><DT
10718 ><A
10719 NAME="MANGLEDSTACK"
10720 ></A
10721 >mangled stack (G)</DT
10722 ><DD
10723 ><P
10724 >This parameter controls the number of mangled names
10725                 that should be cached in the Samba server <A
10726 HREF="smbd.8.html"
10727 TARGET="_top"
10728 >               smbd(8)</A
10729 >.</P
10730 ><P
10731 >This stack is a list of recently mangled base names
10732                 (extensions are only maintained if they are longer than 3 characters
10733                 or contains upper case characters).</P
10734 ><P
10735 >The larger this value, the more likely it is that mangled
10736                 names can be successfully converted to correct long UNIX names.
10737                 However, large stack sizes will slow most directory access. Smaller
10738                 stacks save memory in the server (each stack element costs 256 bytes).
10739                 </P
10740 ><P
10741 >It is not possible to absolutely guarantee correct long
10742                 file names, so be prepared for some surprises!</P
10743 ><P
10744 >Default: <B
10745 CLASS="COMMAND"
10746 >mangled stack = 50</B
10747 ></P
10748 ><P
10749 >Example: <B
10750 CLASS="COMMAND"
10751 >mangled stack = 100</B
10752 ></P
10753 ></DD
10754 ><DT
10755 ><A
10756 NAME="MANGLINGCHAR"
10757 ></A
10758 >mangling char (S)</DT
10759 ><DD
10760 ><P
10761 >This controls what character is used as
10762                 the <EM
10763 >magic</EM
10764 > character in <A
10765 HREF="#AEN201"
10766 >name mangling</A
10767 >. The default is a '~'
10768                 but this may interfere with some software. Use this option to set
10769                 it to whatever you prefer.</P
10770 ><P
10771 >Default: <B
10772 CLASS="COMMAND"
10773 >mangling char = ~</B
10774 ></P
10775 ><P
10776 >Example: <B
10777 CLASS="COMMAND"
10778 >mangling char = ^</B
10779 ></P
10780 ></DD
10781 ><DT
10782 ><A
10783 NAME="MAPARCHIVE"
10784 ></A
10785 >map archive (S)</DT
10786 ><DD
10787 ><P
10788 >This controls whether the DOS archive attribute
10789                 should be mapped to the UNIX owner execute bit.  The DOS archive bit
10790                 is set when a file has been modified since its last backup.  One
10791                 motivation for this option it to keep Samba/your PC from making
10792                 any file it touches from becoming executable under UNIX.  This can
10793                 be quite annoying for shared source code, documents, etc...</P
10794 ><P
10795 >Note that this requires the <TT
10796 CLASS="PARAMETER"
10797 ><I
10798 >create mask</I
10799 ></TT
10800 >
10801                 parameter to be set such that owner execute bit is not masked out
10802                 (i.e. it must include 100). See the parameter <A
10803 HREF="#CREATEMASK"
10804 >               <TT
10805 CLASS="PARAMETER"
10806 ><I
10807 >create mask</I
10808 ></TT
10809 ></A
10810 > for details.</P
10811 ><P
10812 >Default: <B
10813 CLASS="COMMAND"
10814 >map archive = yes</B
10815 ></P
10816 ></DD
10817 ><DT
10818 ><A
10819 NAME="MAPHIDDEN"
10820 ></A
10821 >map hidden (S)</DT
10822 ><DD
10823 ><P
10824 >This controls whether DOS style hidden files
10825                 should be mapped to the UNIX world execute bit.</P
10826 ><P
10827 >Note that this requires the <TT
10828 CLASS="PARAMETER"
10829 ><I
10830 >create mask</I
10831 ></TT
10832 >
10833                 to be set such that the world execute bit is not masked out (i.e.
10834                 it must include 001). See the parameter <A
10835 HREF="#CREATEMASK"
10836 >               <TT
10837 CLASS="PARAMETER"
10838 ><I
10839 >create mask</I
10840 ></TT
10841 ></A
10842 > for details.</P
10843 ><P
10844 >Default: <B
10845 CLASS="COMMAND"
10846 >map hidden = no</B
10847 ></P
10848 ></DD
10849 ><DT
10850 ><A
10851 NAME="MAPSYSTEM"
10852 ></A
10853 >map system (S)</DT
10854 ><DD
10855 ><P
10856 >This controls whether DOS style system files
10857                 should be mapped to the UNIX group execute bit.</P
10858 ><P
10859 >Note that this requires the <TT
10860 CLASS="PARAMETER"
10861 ><I
10862 >create mask</I
10863 ></TT
10864 >
10865                 to be set such that the group execute bit is not masked out (i.e.
10866                 it must include 010). See the parameter <A
10867 HREF="#CREATEMASK"
10868 >               <TT
10869 CLASS="PARAMETER"
10870 ><I
10871 >create mask</I
10872 ></TT
10873 ></A
10874 > for details.</P
10875 ><P
10876 >Default: <B
10877 CLASS="COMMAND"
10878 >map system = no</B
10879 ></P
10880 ></DD
10881 ><DT
10882 ><A
10883 NAME="MAPTOGUEST"
10884 ></A
10885 >map to guest (G)</DT
10886 ><DD
10887 ><P
10888 >This parameter is only useful in <A
10889 HREF="#SECURITY"
10890 >               security</A
10891 > modes other than <TT
10892 CLASS="PARAMETER"
10893 ><I
10894 >security=share</I
10895 ></TT
10896 >
10897                 - i.e. <TT
10898 CLASS="CONSTANT"
10899 >user</TT
10900 >, <TT
10901 CLASS="CONSTANT"
10902 >server</TT
10903 >,
10904                 and <TT
10905 CLASS="CONSTANT"
10906 >domain</TT
10907 >.</P
10908 ><P
10909 >This parameter can take three different values, which tell
10910                 <A
10911 HREF="smbd.8.html"
10912 TARGET="_top"
10913 >smbd(8)</A
10914 > what to do with user
10915                 login requests that don't match a valid UNIX user in some way.</P
10916 ><P
10917 >The three settings are :</P
10918 ><P
10919 ></P
10920 ><UL
10921 ><LI
10922 ><P
10923 ><TT
10924 CLASS="CONSTANT"
10925 >Never</TT
10926 > - Means user login
10927                         requests with an invalid password are rejected. This is the
10928                         default.</P
10929 ></LI
10930 ><LI
10931 ><P
10932 ><TT
10933 CLASS="CONSTANT"
10934 >Bad User</TT
10935 > - Means user
10936                         logins with an invalid password are rejected, unless the username
10937                         does not exist, in which case it is treated as a guest login and
10938                         mapped into the <A
10939 HREF="#GUESTACCOUNT"
10940 ><TT
10941 CLASS="PARAMETER"
10942 ><I
10943 >                       guest account</I
10944 ></TT
10945 ></A
10946 >.</P
10947 ></LI
10948 ><LI
10949 ><P
10950 ><TT
10951 CLASS="CONSTANT"
10952 >Bad Password</TT
10953 > - Means user logins
10954                         with an invalid password are treated as a guest login and mapped
10955                         into the <A
10956 HREF="#GUESTACCOUNT"
10957 >guest account</A
10958 >. Note that
10959                         this can cause problems as it means that any user incorrectly typing
10960                         their password will be silently logged on as "guest" - and
10961                         will not know the reason they cannot access files they think
10962                         they should - there will have been no message given to them
10963                         that they got their password wrong. Helpdesk services will
10964                         <EM
10965 >hate</EM
10966 > you if you set the <TT
10967 CLASS="PARAMETER"
10968 ><I
10969 >map to
10970                         guest</I
10971 ></TT
10972 > parameter this way :-).</P
10973 ></LI
10974 ></UL
10975 ><P
10976 >Note that this parameter is needed to set up "Guest"
10977                 share services when using <TT
10978 CLASS="PARAMETER"
10979 ><I
10980 >security</I
10981 ></TT
10982 > modes other than
10983                 share. This is because in these modes the name of the resource being
10984                 requested is <EM
10985 >not</EM
10986 > sent to the server until after
10987                 the server has successfully authenticated the client so the server
10988                 cannot make authentication decisions at the correct time (connection
10989                 to the share) for "Guest" shares.</P
10990 ><P
10991 >For people familiar with the older Samba releases, this
10992                 parameter maps to the old compile-time setting of the <TT
10993 CLASS="CONSTANT"
10994 >               GUEST_SESSSETUP</TT
10995 > value in local.h.</P
10996 ><P
10997 >Default: <B
10998 CLASS="COMMAND"
10999 >map to guest = Never</B
11000 ></P
11001 ><P
11002 >Example: <B
11003 CLASS="COMMAND"
11004 >map to guest = Bad User</B
11005 ></P
11006 ></DD
11007 ><DT
11008 ><A
11009 NAME="MAXCONNECTIONS"
11010 ></A
11011 >max connections (S)</DT
11012 ><DD
11013 ><P
11014 >This option allows the number of simultaneous
11015                 connections to a service to be limited. If <TT
11016 CLASS="PARAMETER"
11017 ><I
11018 >max connections
11019                 </I
11020 ></TT
11021 > is greater than 0 then connections will be refused if
11022                 this number of connections to the service are already open. A value
11023                 of zero mean an unlimited number of connections may be made.</P
11024 ><P
11025 >Record lock files are used to implement this feature. The
11026                 lock files will be stored in the directory specified by the <A
11027 HREF="#LOCKDIRECTORY"
11028 ><TT
11029 CLASS="PARAMETER"
11030 ><I
11031 >lock directory</I
11032 ></TT
11033 ></A
11034 >
11035                 option.</P
11036 ><P
11037 >Default: <B
11038 CLASS="COMMAND"
11039 >max connections = 0</B
11040 ></P
11041 ><P
11042 >Example: <B
11043 CLASS="COMMAND"
11044 >max connections = 10</B
11045 ></P
11046 ></DD
11047 ><DT
11048 ><A
11049 NAME="MAXDISKSIZE"
11050 ></A
11051 >max disk size (G)</DT
11052 ><DD
11053 ><P
11054 >This option allows you to put an upper limit
11055                 on the apparent size of disks. If you set this option to 100
11056                 then all shares will appear to be not larger than 100 MB in
11057                 size.</P
11058 ><P
11059 >Note that this option does not limit the amount of
11060                 data you can put on the disk. In the above case you could still
11061                 store much more than 100 MB on the disk, but if a client ever asks
11062                 for the amount of free disk space or the total disk size then the
11063                 result will be bounded by the amount specified in <TT
11064 CLASS="PARAMETER"
11065 ><I
11066 >max
11067                 disk size</I
11068 ></TT
11069 >.</P
11070 ><P
11071 >This option is primarily useful to work around bugs
11072                 in some pieces of software that can't handle very large disks,
11073                 particularly disks over 1GB in size.</P
11074 ><P
11075 >A <TT
11076 CLASS="PARAMETER"
11077 ><I
11078 >max disk size</I
11079 ></TT
11080 > of 0 means no limit.</P
11081 ><P
11082 >Default: <B
11083 CLASS="COMMAND"
11084 >max disk size = 0</B
11085 ></P
11086 ><P
11087 >Example: <B
11088 CLASS="COMMAND"
11089 >max disk size = 1000</B
11090 ></P
11091 ></DD
11092 ><DT
11093 ><A
11094 NAME="MAXLOGSIZE"
11095 ></A
11096 >max log size (G)</DT
11097 ><DD
11098 ><P
11099 >This option (an integer in kilobytes) specifies
11100                 the max size the log file should grow to. Samba periodically checks
11101                 the size and if it is exceeded it will rename the file, adding
11102                 a <TT
11103 CLASS="FILENAME"
11104 >.old</TT
11105 > extension.</P
11106 ><P
11107 >A size of 0 means no limit.</P
11108 ><P
11109 >Default: <B
11110 CLASS="COMMAND"
11111 >max log size = 5000</B
11112 ></P
11113 ><P
11114 >Example: <B
11115 CLASS="COMMAND"
11116 >max log size = 1000</B
11117 ></P
11118 ></DD
11119 ><DT
11120 ><A
11121 NAME="MAXMUX"
11122 ></A
11123 >max mux (G)</DT
11124 ><DD
11125 ><P
11126 >This option controls the maximum number of
11127                 outstanding simultaneous SMB operations that samba tells the client
11128                 it will allow. You should never need to set this parameter.</P
11129 ><P
11130 >Default: <B
11131 CLASS="COMMAND"
11132 >max mux = 50</B
11133 ></P
11134 ></DD
11135 ><DT
11136 ><A
11137 NAME="MAXOPENFILES"
11138 ></A
11139 >max open files (G)</DT
11140 ><DD
11141 ><P
11142 >This parameter limits the maximum number of
11143                 open files that one <A
11144 HREF="smbd.8.html"
11145 TARGET="_top"
11146 >smbd(8)</A
11147 > file
11148                 serving process may have open for a client at any one time. The
11149                 default for this parameter is set very high (10,000) as Samba uses
11150                 only one bit per unopened file.</P
11151 ><P
11152 >The limit of the number of open files is usually set
11153                 by the UNIX per-process file descriptor limit rather than
11154                 this parameter so you should never need to touch this parameter.</P
11155 ><P
11156 >Default: <B
11157 CLASS="COMMAND"
11158 >max open files = 10000</B
11159 ></P
11160 ></DD
11161 ><DT
11162 ><A
11163 NAME="MAXPRINTJOBS"
11164 ></A
11165 >max print jobs (S)</DT
11166 ><DD
11167 ><P
11168 >This parameter limits the maximum number of
11169                 jobs allowable in a Samba printer queue at any given moment.
11170                 If this number is exceeded, <A
11171 HREF="smbd.8.html"
11172 TARGET="_top"
11173 ><B
11174 CLASS="COMMAND"
11175 >               smbd(8)</B
11176 ></A
11177 > will remote "Out of Space" to the client.
11178                 See all <A
11179 HREF="#TOTALPRINTJOBS"
11180 ><TT
11181 CLASS="PARAMETER"
11182 ><I
11183 >total
11184                 print jobs</I
11185 ></TT
11186 ></A
11187 >.
11188                 </P
11189 ><P
11190 >Default: <B
11191 CLASS="COMMAND"
11192 >max print jobs = 1000</B
11193 ></P
11194 ><P
11195 >Example: <B
11196 CLASS="COMMAND"
11197 >max print jobs = 5000</B
11198 ></P
11199 ></DD
11200 ><DT
11201 ><A
11202 NAME="MAXPROTOCOL"
11203 ></A
11204 >max protocol (G)</DT
11205 ><DD
11206 ><P
11207 >The value of the parameter (a string) is the highest
11208                 protocol level that will be supported by the server.</P
11209 ><P
11210 >Possible values are :</P
11211 ><P
11212 ></P
11213 ><UL
11214 ><LI
11215 ><P
11216 ><TT
11217 CLASS="CONSTANT"
11218 >CORE</TT
11219 >: Earliest version. No
11220                         concept of user names.</P
11221 ></LI
11222 ><LI
11223 ><P
11224 ><TT
11225 CLASS="CONSTANT"
11226 >COREPLUS</TT
11227 >: Slight improvements on
11228                         CORE for efficiency.</P
11229 ></LI
11230 ><LI
11231 ><P
11232 ><TT
11233 CLASS="CONSTANT"
11234 >LANMAN1</TT
11235 >: First <EM
11236 >                       modern</EM
11237 > version of the protocol. Long filename
11238                         support.</P
11239 ></LI
11240 ><LI
11241 ><P
11242 ><TT
11243 CLASS="CONSTANT"
11244 >LANMAN2</TT
11245 >: Updates to Lanman1 protocol.
11246                         </P
11247 ></LI
11248 ><LI
11249 ><P
11250 ><TT
11251 CLASS="CONSTANT"
11252 >NT1</TT
11253 >: Current up to date version of
11254                         the protocol. Used by Windows NT. Known as CIFS.</P
11255 ></LI
11256 ></UL
11257 ><P
11258 >Normally this option should not be set as the automatic
11259                 negotiation phase in the SMB protocol takes care of choosing
11260                 the appropriate protocol.</P
11261 ><P
11262 >See also <A
11263 HREF="#MINPROTOCOL"
11264 ><TT
11265 CLASS="PARAMETER"
11266 ><I
11267 >min
11268                 protocol</I
11269 ></TT
11270 ></A
11271 ></P
11272 ><P
11273 >Default: <B
11274 CLASS="COMMAND"
11275 >max protocol = NT1</B
11276 ></P
11277 ><P
11278 >Example: <B
11279 CLASS="COMMAND"
11280 >max protocol = LANMAN1</B
11281 ></P
11282 ></DD
11283 ><DT
11284 ><A
11285 NAME="MAXSMBDPROCESSES"
11286 ></A
11287 >max smbd processes (G)</DT
11288 ><DD
11289 ><P
11290 >This parameter limits the maximum number of
11291                 <A
11292 HREF="smbd.8.html"
11293 TARGET="_top"
11294 ><B
11295 CLASS="COMMAND"
11296 >smbd(8)</B
11297 ></A
11298 >
11299                 processes concurrently running on a system and is intended
11300                 as a stop gap to prevent degrading service to clients in the event
11301                 that the server has insufficient resources to handle more than this
11302                 number of connections.  Remember that under normal operating
11303                 conditions, each user will have an smbd associated with him or her
11304                 to handle connections to all shares from a given host.
11305                 </P
11306 ><P
11307 >Default: <B
11308 CLASS="COMMAND"
11309 >max smbd processes = 0</B
11310 >   ## no limit</P
11311 ><P
11312 >Example: <B
11313 CLASS="COMMAND"
11314 >max smbd processes = 1000</B
11315 ></P
11316 ></DD
11317 ><DT
11318 ><A
11319 NAME="MAXTTL"
11320 ></A
11321 >max ttl (G)</DT
11322 ><DD
11323 ><P
11324 >This option tells <A
11325 HREF="nmbd.8.html"
11326 TARGET="_top"
11327 >nmbd(8)</A
11328 >
11329                 what the default 'time to live' of NetBIOS names should be (in seconds)
11330                 when <B
11331 CLASS="COMMAND"
11332 >nmbd</B
11333 > is requesting a name using either a
11334                 broadcast packet or from a WINS server. You should never need to
11335                 change this parameter. The default is 3 days.</P
11336 ><P
11337 >Default: <B
11338 CLASS="COMMAND"
11339 >max ttl = 259200</B
11340 ></P
11341 ></DD
11342 ><DT
11343 ><A
11344 NAME="MAXWINSTTL"
11345 ></A
11346 >max wins ttl (G)</DT
11347 ><DD
11348 ><P
11349 >This option tells <A
11350 HREF="nmbd.8.html"
11351 TARGET="_top"
11352 >nmbd(8)
11353                 </A
11354 > when acting as a WINS server (<A
11355 HREF="#WINSSUPPORT"
11356 >               <TT
11357 CLASS="PARAMETER"
11358 ><I
11359 >wins support=yes</I
11360 ></TT
11361 ></A
11362 >) what the maximum
11363                 'time to live' of NetBIOS names that <B
11364 CLASS="COMMAND"
11365 >nmbd</B
11366 >
11367                 will grant will be (in seconds). You should never need to change this
11368                 parameter.  The default is 6 days (518400 seconds).</P
11369 ><P
11370 >See also the <A
11371 HREF="#MINWINSTTL"
11372 ><TT
11373 CLASS="PARAMETER"
11374 ><I
11375 >min
11376                 wins ttl"</I
11377 ></TT
11378 ></A
11379 > parameter.</P
11380 ><P
11381 >Default: <B
11382 CLASS="COMMAND"
11383 >max wins ttl = 518400</B
11384 ></P
11385 ></DD
11386 ><DT
11387 ><A
11388 NAME="MAXXMIT"
11389 ></A
11390 >max xmit (G)</DT
11391 ><DD
11392 ><P
11393 >This option controls the maximum packet size
11394                 that will be negotiated by Samba. The default is 65535, which
11395                 is the maximum. In some cases you may find you get better performance
11396                 with a smaller value. A value below 2048 is likely to cause problems.
11397                 </P
11398 ><P
11399 >Default: <B
11400 CLASS="COMMAND"
11401 >max xmit = 65535</B
11402 ></P
11403 ><P
11404 >Example: <B
11405 CLASS="COMMAND"
11406 >max xmit = 8192</B
11407 ></P
11408 ></DD
11409 ><DT
11410 ><A
11411 NAME="MESSAGECOMMAND"
11412 ></A
11413 >message command (G)</DT
11414 ><DD
11415 ><P
11416 >This specifies what command to run when the
11417                 server receives a WinPopup style message.</P
11418 ><P
11419 >This would normally be a command that would
11420                 deliver the message somehow. How this is to be done is
11421                 up to your imagination.</P
11422 ><P
11423 >An example is:</P
11424 ><P
11425 ><B
11426 CLASS="COMMAND"
11427 >message command = csh -c 'xedit %s;rm %s' &#38;</B
11428 >
11429                 </P
11430 ><P
11431 >This delivers the message using <B
11432 CLASS="COMMAND"
11433 >xedit</B
11434 >, then
11435                 removes it afterwards. <EM
11436 >NOTE THAT IT IS VERY IMPORTANT
11437                 THAT THIS COMMAND RETURN IMMEDIATELY</EM
11438 >. That's why I
11439                 have the '&#38;' on the end. If it doesn't return immediately then
11440                 your PCs may freeze when sending messages (they should recover
11441                 after 30secs, hopefully).</P
11442 ><P
11443 >All messages are delivered as the global guest user.
11444                 The command takes the standard substitutions, although <TT
11445 CLASS="PARAMETER"
11446 ><I
11447 >               %u</I
11448 ></TT
11449 > won't work (<TT
11450 CLASS="PARAMETER"
11451 ><I
11452 >%U</I
11453 ></TT
11454 > may be better
11455                 in this case).</P
11456 ><P
11457 >Apart from the standard substitutions, some additional
11458                 ones apply. In particular:</P
11459 ><P
11460 ></P
11461 ><UL
11462 ><LI
11463 ><P
11464 ><TT
11465 CLASS="PARAMETER"
11466 ><I
11467 >%s</I
11468 ></TT
11469 > = the filename containing
11470                         the message.</P
11471 ></LI
11472 ><LI
11473 ><P
11474 ><TT
11475 CLASS="PARAMETER"
11476 ><I
11477 >%t</I
11478 ></TT
11479 > = the destination that
11480                         the message was sent to (probably the server name).</P
11481 ></LI
11482 ><LI
11483 ><P
11484 ><TT
11485 CLASS="PARAMETER"
11486 ><I
11487 >%f</I
11488 ></TT
11489 > = who the message
11490                         is from.</P
11491 ></LI
11492 ></UL
11493 ><P
11494 >You could make this command send mail, or whatever else
11495                 takes your fancy. Please let us know of any really interesting
11496                 ideas you have.</P
11497 ><P
11498 >Here's a way of sending the messages as mail to root:</P
11499 ><P
11500 ><B
11501 CLASS="COMMAND"
11502 >message command = /bin/mail -s 'message from %f on
11503                 %m' root &#60; %s; rm %s</B
11504 ></P
11505 ><P
11506 >If you don't have a message command then the message
11507                 won't be delivered and Samba will tell the sender there was
11508                 an error. Unfortunately WfWg totally ignores the error code
11509                 and carries on regardless, saying that the message was delivered.
11510                 </P
11511 ><P
11512 >If you want to silently delete it then try:</P
11513 ><P
11514 ><B
11515 CLASS="COMMAND"
11516 >message command = rm %s</B
11517 ></P
11518 ><P
11519 >Default: <EM
11520 >no message command</EM
11521 ></P
11522 ><P
11523 >Example: <B
11524 CLASS="COMMAND"
11525 >message command = csh -c 'xedit %s;
11526                 rm %s' &#38;</B
11527 ></P
11528 ></DD
11529 ><DT
11530 ><A
11531 NAME="MINPASSWDLENGTH"
11532 ></A
11533 >min passwd length (G)</DT
11534 ><DD
11535 ><P
11536 >Synonym for <A
11537 HREF="#MINPASSWORDLENGTH"
11538 >               <TT
11539 CLASS="PARAMETER"
11540 ><I
11541 >min password length</I
11542 ></TT
11543 ></A
11544 >.</P
11545 ></DD
11546 ><DT
11547 ><A
11548 NAME="MINPASSWORDLENGTH"
11549 ></A
11550 >min password length (G)</DT
11551 ><DD
11552 ><P
11553 >This option sets the minimum length in characters
11554                 of a plaintext password that <B
11555 CLASS="COMMAND"
11556 >smbd</B
11557 > will accept when performing
11558                 UNIX password changing.</P
11559 ><P
11560 >See also <A
11561 HREF="#UNIXPASSWORDSYNC"
11562 ><TT
11563 CLASS="PARAMETER"
11564 ><I
11565 >unix
11566                 password sync</I
11567 ></TT
11568 ></A
11569 >, <A
11570 HREF="#PASSWDPROGRAM"
11571 >               <TT
11572 CLASS="PARAMETER"
11573 ><I
11574 >passwd program</I
11575 ></TT
11576 ></A
11577 > and <A
11578 HREF="#PASSWDCHATDEBUG"
11579 ><TT
11580 CLASS="PARAMETER"
11581 ><I
11582 >passwd chat debug</I
11583 ></TT
11584 >
11585                 </A
11586 >.</P
11587 ><P
11588 >Default: <B
11589 CLASS="COMMAND"
11590 >min password length = 5</B
11591 ></P
11592 ></DD
11593 ><DT
11594 ><A
11595 NAME="MINPRINTSPACE"
11596 ></A
11597 >min print space (S)</DT
11598 ><DD
11599 ><P
11600 >This sets the minimum amount of free disk
11601                 space that must be available before a user will be able to spool
11602                 a print job. It is specified in kilobytes. The default is 0, which
11603                 means a user can always spool a print job.</P
11604 ><P
11605 >See also the <A
11606 HREF="#PRINTING"
11607 ><TT
11608 CLASS="PARAMETER"
11609 ><I
11610 >printing
11611                 </I
11612 ></TT
11613 ></A
11614 > parameter.</P
11615 ><P
11616 >Default: <B
11617 CLASS="COMMAND"
11618 >min print space = 0</B
11619 ></P
11620 ><P
11621 >Example: <B
11622 CLASS="COMMAND"
11623 >min print space = 2000</B
11624 ></P
11625 ></DD
11626 ><DT
11627 ><A
11628 NAME="MINPROTOCOL"
11629 ></A
11630 >min protocol (G)</DT
11631 ><DD
11632 ><P
11633 >The value of the parameter (a string) is the
11634                 lowest SMB protocol dialect than Samba will support.  Please refer
11635                 to the <A
11636 HREF="#MAXPROTOCOL"
11637 ><TT
11638 CLASS="PARAMETER"
11639 ><I
11640 >max protocol</I
11641 ></TT
11642 ></A
11643 >
11644                 parameter for a list of valid protocol names and a brief description
11645                 of each.  You may also wish to refer to the C source code in
11646                 <TT
11647 CLASS="FILENAME"
11648 >source/smbd/negprot.c</TT
11649 > for a listing of known protocol
11650                 dialects supported by clients.</P
11651 ><P
11652 >If you are viewing this parameter as a security measure, you should
11653                 also refer to the <A
11654 HREF="#LANMANAUTH"
11655 ><TT
11656 CLASS="PARAMETER"
11657 ><I
11658 >lanman
11659                 auth</I
11660 ></TT
11661 ></A
11662 > parameter.  Otherwise, you should never need
11663                 to change this parameter.</P
11664 ><P
11665 >Default : <B
11666 CLASS="COMMAND"
11667 >min protocol = CORE</B
11668 ></P
11669 ><P
11670 >Example : <B
11671 CLASS="COMMAND"
11672 >min protocol = NT1</B
11673 >  # disable DOS
11674                 clients</P
11675 ></DD
11676 ><DT
11677 ><A
11678 NAME="MINWINSTTL"
11679 ></A
11680 >min wins ttl (G)</DT
11681 ><DD
11682 ><P
11683 >This option tells <A
11684 HREF="nmbd.8.html"
11685 TARGET="_top"
11686 >nmbd(8)</A
11687 >
11688                 when acting as a WINS server (<A
11689 HREF="#WINSSUPPORT"
11690 ><TT
11691 CLASS="PARAMETER"
11692 ><I
11693 >               wins support = yes</I
11694 ></TT
11695 ></A
11696 >) what the minimum 'time to live'
11697                 of NetBIOS names that <B
11698 CLASS="COMMAND"
11699 >nmbd</B
11700 > will grant will be (in
11701                 seconds). You should never need to change this parameter.  The default
11702                 is 6 hours (21600 seconds).</P
11703 ><P
11704 >Default: <B
11705 CLASS="COMMAND"
11706 >min wins ttl = 21600</B
11707 ></P
11708 ></DD
11709 ><DT
11710 ><A
11711 NAME="MSDFSROOT"
11712 ></A
11713 >msdfs root (S)</DT
11714 ><DD
11715 ><P
11716 >This boolean parameter is only available if
11717                 Samba is configured  and  compiled with the <B
11718 CLASS="COMMAND"
11719 >               --with-msdfs</B
11720 > option.  If set to <TT
11721 CLASS="CONSTANT"
11722 >yes&#62;</TT
11723 >,
11724                 Samba treats the share as a Dfs root and  allows clients to browse
11725                 the distributed file system tree rooted at the share directory.
11726                 Dfs links are specified  in  the share directory by symbolic
11727                 links of the form <TT
11728 CLASS="FILENAME"
11729 >msdfs:serverA\shareA,serverB\shareB
11730                 </TT
11731 > and so on.  For more information on setting up a Dfs tree
11732                 on Samba,  refer to <A
11733 HREF="msdfs_setup.html"
11734 TARGET="_top"
11735 >msdfs_setup.html
11736                 </A
11737 >.</P
11738 ><P
11739 >See also <A
11740 HREF="#HOSTMSDFS"
11741 ><TT
11742 CLASS="PARAMETER"
11743 ><I
11744 >host msdfs
11745                 </I
11746 ></TT
11747 ></A
11748 ></P
11749 ><P
11750 >Default: <B
11751 CLASS="COMMAND"
11752 >msdfs root = no</B
11753 ></P
11754 ></DD
11755 ><DT
11756 ><A
11757 NAME="NAMERESOLVEORDER"
11758 ></A
11759 >name resolve order (G)</DT
11760 ><DD
11761 ><P
11762 >This option is used by the programs in the Samba
11763                 suite to determine what naming services to use and in what order
11764                 to resolve host names to IP addresses. The option takes a space
11765                 separated string of name resolution options.</P
11766 ><P
11767 >The options are :"lmhosts", "host", "wins" and "bcast". They
11768                 cause names to be resolved as follows :</P
11769 ><P
11770 ></P
11771 ><UL
11772 ><LI
11773 ><P
11774 ><TT
11775 CLASS="CONSTANT"
11776 >lmhosts</TT
11777 > : Lookup an IP
11778                         address in the Samba lmhosts file. If the line in lmhosts has
11779                         no name type attached to the NetBIOS name (see the <A
11780 HREF="lmhosts.5.html"
11781 TARGET="_top"
11782 >lmhosts(5)</A
11783 > for details) then
11784                         any name type matches for lookup.</P
11785 ></LI
11786 ><LI
11787 ><P
11788 ><TT
11789 CLASS="CONSTANT"
11790 >host</TT
11791 > : Do a standard host
11792                         name to IP address resolution, using the system <TT
11793 CLASS="FILENAME"
11794 >/etc/hosts
11795                         </TT
11796 >, NIS, or DNS lookups. This method of name resolution
11797                         is operating system depended for instance on IRIX or Solaris this
11798                         may be controlled by the <TT
11799 CLASS="FILENAME"
11800 >/etc/nsswitch.conf</TT
11801 >
11802                         file).  Note that this method is only used if the NetBIOS name
11803                         type being queried is the 0x20 (server) name type, otherwise
11804                         it is ignored.</P
11805 ></LI
11806 ><LI
11807 ><P
11808 ><TT
11809 CLASS="CONSTANT"
11810 >wins</TT
11811 > : Query a name with
11812                         the IP address listed in the <A
11813 HREF="#WINSSERVER"
11814 ><TT
11815 CLASS="PARAMETER"
11816 ><I
11817 >                       wins server</I
11818 ></TT
11819 ></A
11820 > parameter.  If no WINS server has
11821                         been specified this method will be ignored.</P
11822 ></LI
11823 ><LI
11824 ><P
11825 ><TT
11826 CLASS="CONSTANT"
11827 >bcast</TT
11828 > : Do a broadcast on
11829                         each of the known local interfaces listed in the <A
11830 HREF="#INTERFACES"
11831 ><TT
11832 CLASS="PARAMETER"
11833 ><I
11834 >interfaces</I
11835 ></TT
11836 ></A
11837 >
11838                         parameter. This is the least reliable of the name resolution
11839                         methods as it depends on the target host being on a locally
11840                         connected subnet.</P
11841 ></LI
11842 ></UL
11843 ><P
11844 >Default: <B
11845 CLASS="COMMAND"
11846 >name resolve order = lmhosts host wins bcast
11847                 </B
11848 ></P
11849 ><P
11850 >Example: <B
11851 CLASS="COMMAND"
11852 >name resolve order = lmhosts bcast host
11853                 </B
11854 ></P
11855 ><P
11856 >This will cause the local lmhosts file to be examined
11857                 first, followed by a broadcast attempt, followed by a normal
11858                 system hostname lookup.</P
11859 ></DD
11860 ><DT
11861 ><A
11862 NAME="NETBIOSALIASES"
11863 ></A
11864 >netbios aliases (G)</DT
11865 ><DD
11866 ><P
11867 >This is a list of NetBIOS names that <A
11868 HREF="nmbd.8.html"
11869 TARGET="_top"
11870 >nmbd(8)</A
11871 > will advertise as additional
11872                 names by which the Samba server is known. This allows one machine
11873                 to appear in browse lists under multiple names. If a machine is
11874                 acting as a browse server or logon server none
11875                 of these names will be advertised as either browse server or logon
11876                 servers, only the primary name of the machine will be advertised
11877                 with these capabilities.</P
11878 ><P
11879 >See also <A
11880 HREF="#NETBIOSNAME"
11881 ><TT
11882 CLASS="PARAMETER"
11883 ><I
11884 >netbios
11885                 name</I
11886 ></TT
11887 ></A
11888 >.</P
11889 ><P
11890 >Default: <EM
11891 >empty string (no additional names)</EM
11892 ></P
11893 ><P
11894 >Example: <B
11895 CLASS="COMMAND"
11896 >netbios aliases = TEST TEST1 TEST2</B
11897 ></P
11898 ></DD
11899 ><DT
11900 ><A
11901 NAME="NETBIOSNAME"
11902 ></A
11903 >netbios name (G)</DT
11904 ><DD
11905 ><P
11906 >This sets the NetBIOS name by which a Samba
11907                 server is known. By default it is the same as the first component
11908                 of the host's DNS name. If a machine is a browse server or
11909                 logon server this name (or the first component
11910                 of the hosts DNS name) will be the name that these services are
11911                 advertised under.</P
11912 ><P
11913 >See also <A
11914 HREF="#NETBIOSALIASES"
11915 ><TT
11916 CLASS="PARAMETER"
11917 ><I
11918 >netbios
11919                 aliases</I
11920 ></TT
11921 ></A
11922 >.</P
11923 ><P
11924 >Default: <EM
11925 >machine DNS name</EM
11926 ></P
11927 ><P
11928 >Example: <B
11929 CLASS="COMMAND"
11930 >netbios name = MYNAME</B
11931 ></P
11932 ></DD
11933 ><DT
11934 ><A
11935 NAME="NETBIOSSCOPE"
11936 ></A
11937 >netbios scope (G)</DT
11938 ><DD
11939 ><P
11940 >This sets the NetBIOS scope that Samba will
11941                 operate under. This should not be set unless every machine
11942                 on your LAN also sets this value.</P
11943 ></DD
11944 ><DT
11945 ><A
11946 NAME="NISHOMEDIR"
11947 ></A
11948 >nis homedir (G)</DT
11949 ><DD
11950 ><P
11951 >Get the home share server from a NIS map. For
11952                 UNIX systems that use an automounter, the user's home directory
11953                 will often be mounted on a workstation on demand from a remote
11954                 server. </P
11955 ><P
11956 >When the Samba logon server is not the actual home directory
11957                 server, but is mounting the home directories via NFS then two
11958                 network hops would be required to access the users home directory
11959                 if the logon server told the client to use itself as the SMB server
11960                 for home directories (one over SMB and one over NFS). This can
11961                 be very slow.</P
11962 ><P
11963 >This option allows Samba to return the home share as
11964                 being on a different server to the logon server and as
11965                 long as a Samba daemon is running on the home directory server,
11966                 it will be mounted on the Samba client directly from the directory
11967                 server. When Samba is returning the home share to the client, it
11968                 will consult the NIS map specified in <A
11969 HREF="#HOMEDIRMAP"
11970 >               <TT
11971 CLASS="PARAMETER"
11972 ><I
11973 >homedir map</I
11974 ></TT
11975 ></A
11976 > and return the server
11977                 listed there.</P
11978 ><P
11979 >Note that for this option to work there must be a working
11980                 NIS system and the Samba server with this option must also
11981                 be a logon server.</P
11982 ><P
11983 >Default: <B
11984 CLASS="COMMAND"
11985 >nis homedir = no</B
11986 ></P
11987 ></DD
11988 ><DT
11989 ><A
11990 NAME="NTACLSUPPORT"
11991 ></A
11992 >nt acl support (G)</DT
11993 ><DD
11994 ><P
11995 >This boolean parameter controls whether
11996                 <A
11997 HREF="smbd.8.html"
11998 TARGET="_top"
11999 >smbd(8)</A
12000 > will attempt to map
12001                 UNIX permissions into Windows NT access control lists.</P
12002 ><P
12003 >Default: <B
12004 CLASS="COMMAND"
12005 >nt acl support = yes</B
12006 ></P
12007 ></DD
12008 ><DT
12009 ><A
12010 NAME="NTPIPESUPPORT"
12011 ></A
12012 >nt pipe support (G)</DT
12013 ><DD
12014 ><P
12015 >This boolean parameter controls whether
12016                 <A
12017 HREF="smbd.8.html"
12018 TARGET="_top"
12019 >smbd(8)</A
12020 > will allow Windows NT
12021                 clients to connect to the NT SMB specific <TT
12022 CLASS="CONSTANT"
12023 >IPC$</TT
12024 >
12025                 pipes. This is a developer debugging option and can be left
12026                 alone.</P
12027 ><P
12028 >Default: <B
12029 CLASS="COMMAND"
12030 >nt pipe support = yes</B
12031 ></P
12032 ></DD
12033 ><DT
12034 ><A
12035 NAME="NTSMBSUPPORT"
12036 ></A
12037 >nt smb support (G)</DT
12038 ><DD
12039 ><P
12040 >This boolean parameter controls whether <A
12041 HREF="smbd.8.html"
12042 TARGET="_top"
12043 >smbd(8)</A
12044 > will negotiate NT specific SMB
12045                 support with Windows NT clients. Although this is a developer
12046                 debugging option and should be left alone, benchmarking has discovered
12047                 that Windows NT clients give faster performance with this option
12048                 set to <TT
12049 CLASS="CONSTANT"
12050 >no</TT
12051 >. This is still being investigated.
12052                 If this option is set to <TT
12053 CLASS="CONSTANT"
12054 >no</TT
12055 > then Samba offers
12056                 exactly the same SMB calls that versions prior to Samba 2.0 offered.
12057                 This information may be of use if any users are having problems
12058                 with NT SMB support.</P
12059 ><P
12060 >You should not need to ever disable this parameter.</P
12061 ><P
12062 >Default: <B
12063 CLASS="COMMAND"
12064 >nt smb support = yes</B
12065 ></P
12066 ></DD
12067 ><DT
12068 ><A
12069 NAME="NULLPASSWORDS"
12070 ></A
12071 >null passwords (G)</DT
12072 ><DD
12073 ><P
12074 >Allow or disallow client access to accounts
12075                 that have null passwords. </P
12076 ><P
12077 >See also <A
12078 HREF="smbpasswd.5.html"
12079 TARGET="_top"
12080 >smbpasswd (5)</A
12081 >.</P
12082 ><P
12083 >Default: <B
12084 CLASS="COMMAND"
12085 >null passwords = no</B
12086 ></P
12087 ></DD
12088 ><DT
12089 ><A
12090 NAME="OBEYPAMRESTRICTIONS"
12091 ></A
12092 >obey pam restrictions (G)</DT
12093 ><DD
12094 ><P
12095 >When Samba 2.2 is configure to enable PAM support
12096                 (i.e. --with-pam), this parameter will control whether or not Samba
12097                 should obey PAM's account and session management directives.  The
12098                 default behavior is to use PAM for clear text authentication only
12099                 and to ignore any account or session management.  Note that Samba
12100                 always ignores PAM for authentication in the case of <A
12101 HREF="#ENCRYPTPASSWORDS"
12102 ><TT
12103 CLASS="PARAMETER"
12104 ><I
12105 >encrypt passwords = yes</I
12106 ></TT
12107 >
12108                 </A
12109 >.  The reason is that PAM modules cannot support the challenge/response
12110                 authentication mechanism needed in the presence of SMB password encryption.
12111                 </P
12112 ><P
12113 >Default: <B
12114 CLASS="COMMAND"
12115 >obey pam restrictions = no</B
12116 ></P
12117 ></DD
12118 ><DT
12119 ><A
12120 NAME="ONLYUSER"
12121 ></A
12122 >only user (S)</DT
12123 ><DD
12124 ><P
12125 >This is a boolean option that controls whether
12126                 connections with usernames not in the <TT
12127 CLASS="PARAMETER"
12128 ><I
12129 >user</I
12130 ></TT
12131 >
12132                 list will be allowed. By default this option is disabled so that a
12133                 client can supply a username to be used by the server.  Enabling
12134                 this parameter will force the server to only user the login
12135                 names from the <TT
12136 CLASS="PARAMETER"
12137 ><I
12138 >user</I
12139 ></TT
12140 > list and is only really
12141                 useful in <A
12142 HREF="#SECURITYEQUALSSHARE"
12143 >shave level</A
12144 >
12145                 security.</P
12146 ><P
12147 >Note that this also means Samba won't try to deduce
12148                 usernames from the service name. This can be annoying for
12149                 the [homes] section. To get around this you could use <B
12150 CLASS="COMMAND"
12151 >user =
12152                 %S</B
12153 > which means your <TT
12154 CLASS="PARAMETER"
12155 ><I
12156 >user</I
12157 ></TT
12158 > list
12159                 will be just the service name, which for home directories is the
12160                 name of the user.</P
12161 ><P
12162 >See also the <A
12163 HREF="#USER"
12164 ><TT
12165 CLASS="PARAMETER"
12166 ><I
12167 >user</I
12168 ></TT
12169 >
12170                 </A
12171 > parameter.</P
12172 ><P
12173 >Default: <B
12174 CLASS="COMMAND"
12175 >only user = no</B
12176 ></P
12177 ></DD
12178 ><DT
12179 ><A
12180 NAME="ONLYGUEST"
12181 ></A
12182 >only guest (S)</DT
12183 ><DD
12184 ><P
12185 >A synonym for <A
12186 HREF="#GUESTONLY"
12187 ><TT
12188 CLASS="PARAMETER"
12189 ><I
12190 >               guest only</I
12191 ></TT
12192 ></A
12193 >.</P
12194 ></DD
12195 ><DT
12196 ><A
12197 NAME="OPLOCKBREAKWAITTIME"
12198 ></A
12199 >oplock break wait time (G)</DT
12200 ><DD
12201 ><P
12202 >This is a tuning parameter added due to bugs in
12203                 both Windows 9x and WinNT. If Samba responds to a client too
12204                 quickly when that client issues an SMB that can cause an oplock
12205                 break request, then the network client can fail and not respond
12206                 to the break request. This tuning parameter (which is set in milliseconds)
12207                 is the amount of time Samba will wait before sending an oplock break
12208                 request to such (broken) clients.</P
12209 ><P
12210 ><EM
12211 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
12212                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
12213 >.</P
12214 ><P
12215 >Default: <B
12216 CLASS="COMMAND"
12217 >oplock break wait time = 0</B
12218 ></P
12219 ></DD
12220 ><DT
12221 ><A
12222 NAME="OPLOCKCONTENTIONLIMIT"
12223 ></A
12224 >oplock contention limit (S)</DT
12225 ><DD
12226 ><P
12227 >This is a <EM
12228 >very</EM
12229 > advanced
12230                 <A
12231 HREF="smbd.8.html"
12232 TARGET="_top"
12233 >smbd(8)</A
12234 > tuning option to
12235                 improve the efficiency of the granting of oplocks under multiple
12236                 client contention for the same file.</P
12237 ><P
12238 >In brief it specifies a number, which causes smbd not to
12239                 grant an oplock even when requested if the approximate number of
12240                 clients contending for an oplock on the same file goes over this
12241                 limit. This causes <B
12242 CLASS="COMMAND"
12243 >smbd</B
12244 > to behave in a similar
12245                 way to Windows NT.</P
12246 ><P
12247 ><EM
12248 >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
12249                 AND UNDERSTOOD THE SAMBA OPLOCK CODE</EM
12250 >.</P
12251 ><P
12252 >Default: <B
12253 CLASS="COMMAND"
12254 >oplock contention limit = 2</B
12255 ></P
12256 ></DD
12257 ><DT
12258 ><A
12259 NAME="OPLOCKS"
12260 ></A
12261 >oplocks (S)</DT
12262 ><DD
12263 ><P
12264 >This boolean option tells smbd whether to
12265                 issue oplocks (opportunistic locks) to file open requests on this
12266                 share. The oplock code can dramatically (approx. 30% or more) improve
12267                 the speed of access to files on Samba servers. It allows the clients
12268                 to aggressively cache files locally and you may want to disable this
12269                 option for unreliable network environments (it is turned on by
12270                 default in Windows NT Servers).  For more information see the file
12271                 <TT
12272 CLASS="FILENAME"
12273 >Speed.txt</TT
12274 > in the Samba <TT
12275 CLASS="FILENAME"
12276 >docs/</TT
12277 >
12278                 directory.</P
12279 ><P
12280 >Oplocks may be selectively turned off on certain files with a
12281                 share. See the <A
12282 HREF="#VETOOPLOCKFILES"
12283 ><TT
12284 CLASS="PARAMETER"
12285 ><I
12286 >               veto oplock files</I
12287 ></TT
12288 ></A
12289 > parameter. On some systems
12290                 oplocks are recognized by the underlying operating system. This
12291                 allows data synchronization between all access to oplocked files,
12292                 whether it be via Samba or NFS or a local UNIX process. See the
12293                 <TT
12294 CLASS="PARAMETER"
12295 ><I
12296 >kernel oplocks</I
12297 ></TT
12298 > parameter for details.</P
12299 ><P
12300 >See also the <A
12301 HREF="#KERNELOPLOCKS"
12302 ><TT
12303 CLASS="PARAMETER"
12304 ><I
12305 >kernel
12306                 oplocks</I
12307 ></TT
12308 ></A
12309 > and <A
12310 HREF="#LEVEL2OPLOCKS"
12311 ><TT
12312 CLASS="PARAMETER"
12313 ><I
12314 >               level2 oplocks</I
12315 ></TT
12316 ></A
12317 > parameters.</P
12318 ><P
12319 >Default: <B
12320 CLASS="COMMAND"
12321 >oplocks = yes</B
12322 ></P
12323 ></DD
12324 ><DT
12325 ><A
12326 NAME="OSLEVEL"
12327 ></A
12328 >os level (G)</DT
12329 ><DD
12330 ><P
12331 >This integer value controls what level Samba
12332                 advertises itself as for browse elections. The value of this
12333                 parameter determines whether <A
12334 HREF="nmbd.8.html"
12335 TARGET="_top"
12336 >nmbd(8)</A
12337 >
12338                 has a chance of becoming a local master browser for the <TT
12339 CLASS="PARAMETER"
12340 ><I
12341 >               WORKGROUP</I
12342 ></TT
12343 > in the local broadcast area.</P
12344 ><P
12345 ><EM
12346 >Note :</EM
12347 >By default, Samba will win
12348                 a local master browsing election over all Microsoft operating
12349                 systems except a Windows NT 4.0/2000 Domain Controller.  This
12350                 means that a misconfigured Samba host can effectively isolate
12351                 a subnet for browsing purposes.  See <TT
12352 CLASS="FILENAME"
12353 >BROWSING.txt
12354                 </TT
12355 > in the Samba <TT
12356 CLASS="FILENAME"
12357 >docs/</TT
12358 > directory
12359                 for details.</P
12360 ><P
12361 >Default: <B
12362 CLASS="COMMAND"
12363 >os level = 20</B
12364 ></P
12365 ><P
12366 >Example: <B
12367 CLASS="COMMAND"
12368 >os level = 65 </B
12369 ></P
12370 ></DD
12371 ><DT
12372 ><A
12373 NAME="OS2DRIVERMAP"
12374 ></A
12375 >os2 driver map (G)</DT
12376 ><DD
12377 ><P
12378 >The parameter is used to define the absolute
12379                 path to a file containing a mapping of Windows NT printer driver
12380                 names to OS/2 printer driver names.  The format is:</P
12381 ><P
12382 >&#60;nt driver name&#62; = &#60;os2 driver
12383                 name&#62;.&#60;device name&#62;</P
12384 ><P
12385 >For example, a valid entry using the HP LaserJet 5
12386                 printer driver woudl appear as <B
12387 CLASS="COMMAND"
12388 >HP LaserJet 5L = LASERJET.HP
12389                 LaserJet 5L</B
12390 >.</P
12391 ><P
12392 >The need for the file is due to the printer driver namespace
12393                 problem described in the <A
12394 HREF="printer_driver2.html"
12395 TARGET="_top"
12396 >Samba
12397                 Printing HOWTO</A
12398 >.  For more details on OS/2 clients, please
12399                 refer to the <A
12400 HREF="OS2-Client-HOWTO.html"
12401 TARGET="_top"
12402 >OS2-Client-HOWTO
12403                 </A
12404 > containing in the Samba documentation.</P
12405 ><P
12406 >Default: <B
12407 CLASS="COMMAND"
12408 >os2 driver map = &#60;empty string&#62;
12409                 </B
12410 ></P
12411 ></DD
12412 ><DT
12413 ><A
12414 NAME="PAMPASSWORDCHANGE"
12415 ></A
12416 >pam password change (G)</DT
12417 ><DD
12418 ><P
12419 >With the addition of better PAM support in Samba 2.2,
12420                 this parameter, it is possible to use PAM's password change control
12421                 flag for Samba.  If enabled, then PAM will be used for password
12422                 changes when requested by an SMB client, and  the <A
12423 HREF="#PASSWDCHAT"
12424 ><TT
12425 CLASS="PARAMETER"
12426 ><I
12427 >passwd chat</I
12428 ></TT
12429 ></A
12430 > string will
12431                 be ignored.
12432                 </P
12433 ><P
12434 >Default: <B
12435 CLASS="COMMAND"
12436 >pam password change = no</B
12437 ></P
12438 ></DD
12439 ><DT
12440 ><A
12441 NAME="PANICACTION"
12442 ></A
12443 >panic action (G)</DT
12444 ><DD
12445 ><P
12446 >This is a Samba developer option that allows a
12447                 system command to be called when either <A
12448 HREF="smbd.8.html"
12449 TARGET="_top"
12450 >               smbd(8)</A
12451 > or <A
12452 HREF="nmbd.8.html"
12453 TARGET="_top"
12454 >nmbd(8)</A
12455 >
12456                 crashes. This is usually used to draw attention to the fact that
12457                 a problem occurred.</P
12458 ><P
12459 >Default: <B
12460 CLASS="COMMAND"
12461 >panic action = &#60;empty string&#62;</B
12462 ></P
12463 ><P
12464 >Example: <B
12465 CLASS="COMMAND"
12466 >panic action = "/bin/sleep 90000"</B
12467 ></P
12468 ></DD
12469 ><DT
12470 ><A
12471 NAME="PASSWDCHAT"
12472 ></A
12473 >passwd chat (G)</DT
12474 ><DD
12475 ><P
12476 >This string controls the <EM
12477 >"chat"</EM
12478 >
12479                 conversation that takes places between <A
12480 HREF="smbd.8.html"
12481 TARGET="_top"
12482 >smbd</A
12483 > and the local password changing
12484                 program to change the users password. The string describes a
12485                 sequence of response-receive pairs that <A
12486 HREF="smbd.8.html"
12487 TARGET="_top"
12488 >               smbd(8)</A
12489 > uses to determine what to send to the
12490                 <A
12491 HREF="#PASSWDPROGRAM"
12492 ><TT
12493 CLASS="PARAMETER"
12494 ><I
12495 >passwd program</I
12496 ></TT
12497 >
12498                 </A
12499 > and what to expect back. If the expected output is not
12500                 received then the password is not changed.</P
12501 ><P
12502 >This chat sequence is often quite site specific, depending
12503                 on what local methods are used for password control (such as NIS
12504                 etc).</P
12505 ><P
12506 >The string can contain the macros <TT
12507 CLASS="PARAMETER"
12508 ><I
12509 >%o</I
12510 ></TT
12511 >
12512                 and <TT
12513 CLASS="PARAMETER"
12514 ><I
12515 >%n</I
12516 ></TT
12517 > which are substituted for the old
12518                 and new passwords respectively. It can also contain the standard
12519                 macros <TT
12520 CLASS="CONSTANT"
12521 >\n</TT
12522 >, <TT
12523 CLASS="CONSTANT"
12524 >\r</TT
12525 >, <TT
12526 CLASS="CONSTANT"
12527 >               \t</TT
12528 > and <TT
12529 CLASS="CONSTANT"
12530 >%s</TT
12531 > to give line-feed,
12532                 carriage-return, tab and space.</P
12533 ><P
12534 >The string can also contain a '*' which matches
12535                 any sequence of characters.</P
12536 ><P
12537 >Double quotes can be used to collect strings with spaces
12538                 in them into a single string.</P
12539 ><P
12540 >If the send string in any part of the chat sequence
12541                 is a fullstop ".",  then no string is sent. Similarly,
12542                 if the expect string is a fullstop then no string is expected.</P
12543 ><P
12544 >Note that if the <A
12545 HREF="#UNIXPASSWORDSYNC"
12546 ><TT
12547 CLASS="PARAMETER"
12548 ><I
12549 >unix
12550                 password sync</I
12551 ></TT
12552 ></A
12553 > parameter is set to true, then this
12554                 sequence is called <EM
12555 >AS ROOT</EM
12556 > when the SMB password
12557                 in the smbpasswd file is being changed, without access to the old
12558                 password cleartext. In this case the old password cleartext is set
12559                 to "" (the empty string).</P
12560 ><P
12561 >See also <A
12562 HREF="#UNIXPASSWORDSYNC"
12563 ><TT
12564 CLASS="PARAMETER"
12565 ><I
12566 >unix password
12567                 sync</I
12568 ></TT
12569 ></A
12570 >, <A
12571 HREF="#PASSWDPROGRAM"
12572 ><TT
12573 CLASS="PARAMETER"
12574 ><I
12575 >               passwd program</I
12576 ></TT
12577 ></A
12578 > and <A
12579 HREF="#PASSWDCHATDEBUG"
12580 >               <TT
12581 CLASS="PARAMETER"
12582 ><I
12583 >passwd chat debug</I
12584 ></TT
12585 ></A
12586 >.</P
12587 ><P
12588 >Default: <B
12589 CLASS="COMMAND"
12590 >passwd chat = *new*password* %n\n
12591                 *new*password* %n\n *changed*</B
12592 ></P
12593 ><P
12594 >Example: <B
12595 CLASS="COMMAND"
12596 >passwd chat = "*Enter OLD password*" %o\n
12597                 "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password
12598                 changed*"</B
12599 ></P
12600 ></DD
12601 ><DT
12602 ><A
12603 NAME="PASSWDCHATDEBUG"
12604 ></A
12605 >passwd chat debug (G)</DT
12606 ><DD
12607 ><P
12608 >This boolean specifies if the passwd chat script
12609                 parameter is run in <EM
12610 >debug</EM
12611 > mode. In this mode the
12612                 strings passed to and received from the passwd chat are printed
12613                 in the <A
12614 HREF="smbd.8.html"
12615 TARGET="_top"
12616 >smbd(8)</A
12617 > log with a
12618                 <A
12619 HREF="#DEBUGLEVEL"
12620 ><TT
12621 CLASS="PARAMETER"
12622 ><I
12623 >debug level</I
12624 ></TT
12625 ></A
12626 >
12627                 of 100. This is a dangerous option as it will allow plaintext passwords
12628                 to be seen in the <B
12629 CLASS="COMMAND"
12630 >smbd</B
12631 > log. It is available to help
12632                 Samba admins debug their <TT
12633 CLASS="PARAMETER"
12634 ><I
12635 >passwd chat</I
12636 ></TT
12637 > scripts
12638                 when calling the <TT
12639 CLASS="PARAMETER"
12640 ><I
12641 >passwd program</I
12642 ></TT
12643 > and should
12644                 be turned off after this has been done. This parameter is off by
12645                 default.</P
12646 ><P
12647 >See also &#60;<A
12648 HREF="#PASSWDCHAT"
12649 ><TT
12650 CLASS="PARAMETER"
12651 ><I
12652 >passwd chat</I
12653 ></TT
12654 >
12655                 </A
12656 >, <A
12657 HREF="#PASSWDPROGRAM"
12658 ><TT
12659 CLASS="PARAMETER"
12660 ><I
12661 >passwd program</I
12662 ></TT
12663 >
12664                 </A
12665 >.</P
12666 ><P
12667 >Default: <B
12668 CLASS="COMMAND"
12669 >passwd chat debug = no</B
12670 ></P
12671 ></DD
12672 ><DT
12673 ><A
12674 NAME="PASSWDPROGRAM"
12675 ></A
12676 >passwd program (G)</DT
12677 ><DD
12678 ><P
12679 >The name of a program that can be used to set
12680                 UNIX user passwords.  Any occurrences of <TT
12681 CLASS="PARAMETER"
12682 ><I
12683 >%u</I
12684 ></TT
12685 >
12686                 will be replaced with the user name. The user name is checked for
12687                 existence before calling the password changing program.</P
12688 ><P
12689 >Also note that many passwd programs insist in <EM
12690 >reasonable
12691                 </EM
12692 > passwords, such as a minimum length, or the inclusion
12693                 of mixed case chars and digits. This can pose a problem as some clients
12694                 (such as Windows for Workgroups) uppercase the password before sending
12695                 it.</P
12696 ><P
12697 ><EM
12698 >Note</EM
12699 > that if the <TT
12700 CLASS="PARAMETER"
12701 ><I
12702 >unix
12703                 password sync</I
12704 ></TT
12705 > parameter is set to <TT
12706 CLASS="CONSTANT"
12707 >True
12708                 </TT
12709 > then this program is called <EM
12710 >AS ROOT</EM
12711 >
12712                 before the SMB password in the <A
12713 HREF="smbpasswd.5.html"
12714 TARGET="_top"
12715 >smbpasswd(5)
12716                 </A
12717 > file is changed. If this UNIX password change fails, then
12718                 <B
12719 CLASS="COMMAND"
12720 >smbd</B
12721 > will fail to change the SMB password also
12722                 (this is by design).</P
12723 ><P
12724 >If the <TT
12725 CLASS="PARAMETER"
12726 ><I
12727 >unix password sync</I
12728 ></TT
12729 > parameter
12730                 is set this parameter <EM
12731 >MUST USE ABSOLUTE PATHS</EM
12732 >
12733                 for <EM
12734 >ALL</EM
12735 > programs called, and must be examined
12736                 for security implications. Note that by default <TT
12737 CLASS="PARAMETER"
12738 ><I
12739 >unix
12740                 password sync</I
12741 ></TT
12742 > is set to <TT
12743 CLASS="CONSTANT"
12744 >False</TT
12745 >.</P
12746 ><P
12747 >See also <A
12748 HREF="#UNIXPASSWORDSYNC"
12749 ><TT
12750 CLASS="PARAMETER"
12751 ><I
12752 >unix
12753                 password sync</I
12754 ></TT
12755 ></A
12756 >.</P
12757 ><P
12758 >Default: <B
12759 CLASS="COMMAND"
12760 >passwd program = /bin/passwd</B
12761 ></P
12762 ><P
12763 >Example: <B
12764 CLASS="COMMAND"
12765 >passwd program = /sbin/npasswd %u</B
12766 >
12767                 </P
12768 ></DD
12769 ><DT
12770 ><A
12771 NAME="PASSWORDLEVEL"
12772 ></A
12773 >password level (G)</DT
12774 ><DD
12775 ><P
12776 >Some client/server combinations have difficulty
12777                 with mixed-case passwords.  One offending client is Windows for
12778                 Workgroups, which for some reason forces passwords to upper
12779                 case when using the LANMAN1 protocol, but leaves them alone when
12780                 using COREPLUS!  Another problem child is the Windows 95/98
12781                 family of operating systems.  These clients upper case clear
12782                 text passwords even when NT LM 0.12 selected by the protocol
12783                 negotiation request/response.</P
12784 ><P
12785 >This parameter defines the maximum number of characters
12786                 that may be upper case in passwords.</P
12787 ><P
12788 >For example, say the password given was "FRED". If <TT
12789 CLASS="PARAMETER"
12790 ><I
12791 >               password level</I
12792 ></TT
12793 > is set to 1, the following combinations
12794                 would be tried if "FRED" failed:</P
12795 ><P
12796 >"Fred", "fred", "fRed", "frEd","freD"</P
12797 ><P
12798 >If <TT
12799 CLASS="PARAMETER"
12800 ><I
12801 >password level</I
12802 ></TT
12803 > was set to 2,
12804                 the following combinations would also be tried: </P
12805 ><P
12806 >"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</P
12807 ><P
12808 >And so on.</P
12809 ><P
12810 >The higher value this parameter is set to the more likely
12811                 it is that a mixed case password will be matched against a single
12812                 case password. However, you should be aware that use of this
12813                 parameter reduces security and increases the time taken to
12814                 process a new connection.</P
12815 ><P
12816 >A value of zero will cause only two attempts to be
12817                 made - the password as is and the password in all-lower case.</P
12818 ><P
12819 >Default: <B
12820 CLASS="COMMAND"
12821 >password level = 0</B
12822 ></P
12823 ><P
12824 >Example: <B
12825 CLASS="COMMAND"
12826 >password level = 4</B
12827 ></P
12828 ></DD
12829 ><DT
12830 ><A
12831 NAME="PASSWORDSERVER"
12832 ></A
12833 >password server (G)</DT
12834 ><DD
12835 ><P
12836 >By specifying the name of another SMB server (such
12837                 as a WinNT box) with this option, and using <B
12838 CLASS="COMMAND"
12839 >security = domain
12840                 </B
12841 > or <B
12842 CLASS="COMMAND"
12843 >security = server</B
12844 > you can get Samba
12845                 to do all its username/password validation via a remote server.</P
12846 ><P
12847 >This option sets the name of the password server to use.
12848                 It must be a NetBIOS name, so if the machine's NetBIOS name is
12849                 different from its Internet name then you may have to add its NetBIOS
12850                 name to the lmhosts  file which is stored in the same directory
12851                 as the <TT
12852 CLASS="FILENAME"
12853 >smb.conf</TT
12854 > file.</P
12855 ><P
12856 >The name of the password server is looked up using the
12857                 parameter <A
12858 HREF="#NAMERESOLVEORDER"
12859 ><TT
12860 CLASS="PARAMETER"
12861 ><I
12862 >name
12863                 resolve order</I
12864 ></TT
12865 ></A
12866 > and so may resolved
12867                 by any method and order described in that parameter.</P
12868 ><P
12869 >The password server much be a machine capable of using
12870                 the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in
12871                 user level security mode.</P
12872 ><P
12873 ><EM
12874 >NOTE:</EM
12875 > Using a password server
12876                 means your UNIX box (running Samba) is only as secure as your
12877                 password server. <EM
12878 >DO NOT CHOOSE A PASSWORD SERVER THAT
12879                 YOU DON'T COMPLETELY TRUST</EM
12880 >.</P
12881 ><P
12882 >Never point a Samba server at itself for password
12883                 serving. This will cause a loop and could lock up your Samba
12884                 server!</P
12885 ><P
12886 >The name of the password server takes the standard
12887                 substitutions, but probably the only useful one is <TT
12888 CLASS="PARAMETER"
12889 ><I
12890 >%m
12891                 </I
12892 ></TT
12893 >, which means the Samba server will use the incoming
12894                 client as the password server. If you use this then you better
12895                 trust your clients, and you had better restrict them with hosts allow!</P
12896 ><P
12897 >If the <TT
12898 CLASS="PARAMETER"
12899 ><I
12900 >security</I
12901 ></TT
12902 > parameter is set to
12903                 <TT
12904 CLASS="CONSTANT"
12905 >domain</TT
12906 >, then the list of machines in this
12907                 option must be a list of Primary or Backup Domain controllers for the
12908                 Domain or the character '*', as the Samba server is effectively
12909                 in that domain, and will use cryptographically authenticated RPC calls
12910                 to authenticate the user logging on. The advantage of using <B
12911 CLASS="COMMAND"
12912 >               security = domain</B
12913 > is that if you list several hosts in the
12914                 <TT
12915 CLASS="PARAMETER"
12916 ><I
12917 >password server</I
12918 ></TT
12919 > option then <B
12920 CLASS="COMMAND"
12921 >smbd
12922                 </B
12923 > will try each in turn till it finds one that responds. This
12924                 is useful in case your primary server goes down.</P
12925 ><P
12926 >If the <TT
12927 CLASS="PARAMETER"
12928 ><I
12929 >password server</I
12930 ></TT
12931 > option is set
12932                 to the character '*', then Samba will attempt to auto-locate the
12933                 Primary or Backup Domain controllers to authenticate against by
12934                 doing a query for the name <TT
12935 CLASS="CONSTANT"
12936 >WORKGROUP&#60;1C&#62;</TT
12937 >
12938                 and then contacting each server returned in the list of IP
12939                 addresses from the name resolution source. </P
12940 ><P
12941 >If the <TT
12942 CLASS="PARAMETER"
12943 ><I
12944 >security</I
12945 ></TT
12946 > parameter is
12947                 set to <TT
12948 CLASS="CONSTANT"
12949 >server</TT
12950 >, then there are different
12951                 restrictions that <B
12952 CLASS="COMMAND"
12953 >security = domain</B
12954 > doesn't
12955                 suffer from:</P
12956 ><P
12957 ></P
12958 ><UL
12959 ><LI
12960 ><P
12961 >You may list several password servers in
12962                         the <TT
12963 CLASS="PARAMETER"
12964 ><I
12965 >password server</I
12966 ></TT
12967 > parameter, however if an
12968                         <B
12969 CLASS="COMMAND"
12970 >smbd</B
12971 > makes a connection to a password server,
12972                         and then the password server fails, no more users will be able
12973                         to be authenticated from this <B
12974 CLASS="COMMAND"
12975 >smbd</B
12976 >.  This is a
12977                         restriction of the SMB/CIFS protocol when in <B
12978 CLASS="COMMAND"
12979 >security=server
12980                         </B
12981 > mode and cannot be fixed in Samba.</P
12982 ></LI
12983 ><LI
12984 ><P
12985 >If you are using a Windows NT server as your
12986                         password server then you will have to ensure that your users
12987                         are able to login from the Samba server, as when in <B
12988 CLASS="COMMAND"
12989 >                       security=server</B
12990 >  mode the network logon will appear to
12991                         come from there rather than from the users workstation.</P
12992 ></LI
12993 ></UL
12994 ><P
12995 >See also the <A
12996 HREF="#SECURITY"
12997 ><TT
12998 CLASS="PARAMETER"
12999 ><I
13000 >security
13001                 </I
13002 ></TT
13003 ></A
13004 > parameter.</P
13005 ><P
13006 >Default: <B
13007 CLASS="COMMAND"
13008 >password server = &#60;empty string&#62;</B
13009 >
13010                 </P
13011 ><P
13012 >Example: <B
13013 CLASS="COMMAND"
13014 >password server = NT-PDC, NT-BDC1, NT-BDC2
13015                 </B
13016 ></P
13017 ><P
13018 >Example: <B
13019 CLASS="COMMAND"
13020 >password server = *</B
13021 ></P
13022 ></DD
13023 ><DT
13024 ><A
13025 NAME="PATH"
13026 ></A
13027 >path (S)</DT
13028 ><DD
13029 ><P
13030 >This parameter specifies a directory to which
13031                 the user of the service is to be given access. In the case of
13032                 printable services, this is where print data will spool prior to
13033                 being submitted to the host for printing.</P
13034 ><P
13035 >For a printable service offering guest access, the service
13036                 should be readonly and the path should be world-writeable and
13037                 have the sticky bit set. This is not mandatory of course, but
13038                 you probably won't get the results you expect if you do
13039                 otherwise.</P
13040 ><P
13041 >Any occurrences of <TT
13042 CLASS="PARAMETER"
13043 ><I
13044 >%u</I
13045 ></TT
13046 > in the path
13047                 will be replaced with the UNIX username that the client is using
13048                 on this connection. Any occurrences of <TT
13049 CLASS="PARAMETER"
13050 ><I
13051 >%m</I
13052 ></TT
13053 >
13054                 will be replaced by the NetBIOS name of the machine they are
13055                 connecting from. These replacements are very useful for setting
13056                 up pseudo home directories for users.</P
13057 ><P
13058 >Note that this path will be based on <A
13059 HREF="#ROOTDIR"
13060 >               <TT
13061 CLASS="PARAMETER"
13062 ><I
13063 >root dir</I
13064 ></TT
13065 ></A
13066 > if one was specified.</P
13067 ><P
13068 >Default: <EM
13069 >none</EM
13070 ></P
13071 ><P
13072 >Example: <B
13073 CLASS="COMMAND"
13074 >path = /home/fred</B
13075 ></P
13076 ></DD
13077 ><DT
13078 ><A
13079 NAME="POSIXLOCKING"
13080 ></A
13081 >posix locking (S)</DT
13082 ><DD
13083 ><P
13084 >The <A
13085 HREF="smbd.8.html"
13086 TARGET="_top"
13087 ><B
13088 CLASS="COMMAND"
13089 >smbd(8)</B
13090 ></A
13091 >
13092                 daemon maintains an database of file locks obtained by SMB clients.
13093                 The default behavior is to map this internal database to POSIX
13094                 locks.  This means that file locks obtained by SMB clients are
13095                 consistent with those seen by POSIX compliant applications accessing
13096                 the files via a non-SMB method (e.g. NFS or local file access).
13097                 You should never need to disable this parameter.</P
13098 ><P
13099 >Default: <B
13100 CLASS="COMMAND"
13101 >posix locking = yes</B
13102 ></P
13103 ></DD
13104 ><DT
13105 ><A
13106 NAME="POSTEXEC"
13107 ></A
13108 >postexec (S)</DT
13109 ><DD
13110 ><P
13111 >This option specifies a command to be run
13112                 whenever the service is disconnected. It takes the usual
13113                 substitutions. The command may be run as the root on some
13114                 systems.</P
13115 ><P
13116 >An interesting example may be do unmount server
13117                 resources:</P
13118 ><P
13119 ><B
13120 CLASS="COMMAND"
13121 >postexec = /etc/umount /cdrom</B
13122 ></P
13123 ><P
13124 >See also <A
13125 HREF="#PREEXEC"
13126 ><TT
13127 CLASS="PARAMETER"
13128 ><I
13129 >preexec</I
13130 ></TT
13131 >
13132                 </A
13133 >.</P
13134 ><P
13135 >Default: <EM
13136 >none (no command executed)</EM
13137 >
13138                 </P
13139 ><P
13140 >Example: <B
13141 CLASS="COMMAND"
13142 >postexec = echo \"%u disconnected from %S
13143                 from %m (%I)\" &#62;&#62; /tmp/log</B
13144 ></P
13145 ></DD
13146 ><DT
13147 ><A
13148 NAME="POSTSCRIPT"
13149 ></A
13150 >postscript (S)</DT
13151 ><DD
13152 ><P
13153 >This parameter forces a printer to interpret
13154                 the print files as postscript. This is done by adding a <TT
13155 CLASS="CONSTANT"
13156 >%!
13157                 </TT
13158 > to the start of print output.</P
13159 ><P
13160 >This is most useful when you have lots of PCs that persist
13161                 in putting a control-D at the start of print jobs, which then
13162                 confuses your printer.</P
13163 ><P
13164 >Default: <B
13165 CLASS="COMMAND"
13166 >postscript = no</B
13167 ></P
13168 ></DD
13169 ><DT
13170 ><A
13171 NAME="PREEXEC"
13172 ></A
13173 >preexec (S)</DT
13174 ><DD
13175 ><P
13176 >This option specifies a command to be run whenever
13177                 the service is connected to. It takes the usual substitutions.</P
13178 ><P
13179 >An interesting example is to send the users a welcome
13180                 message every time they log in. Maybe a message of the day? Here
13181                 is an example:</P
13182 ><P
13183 ><B
13184 CLASS="COMMAND"
13185 >preexec = csh -c 'echo \"Welcome to %S!\" |
13186                  /usr/local/samba/bin/smbclient -M %m -I %I' &#38; </B
13187 ></P
13188 ><P
13189 >Of course, this could get annoying after a while :-)</P
13190 ><P
13191 >See also <A
13192 HREF="#PREEXECCLOSE"
13193 ><TT
13194 CLASS="PARAMETER"
13195 ><I
13196 >preexec close
13197                 </I
13198 ></TT
13199 ></A
13200 > and <A
13201 HREF="#POSTEXEC"
13202 ><TT
13203 CLASS="PARAMETER"
13204 ><I
13205 >postexec
13206                 </I
13207 ></TT
13208 ></A
13209 >.</P
13210 ><P
13211 >Default: <EM
13212 >none (no command executed)</EM
13213 ></P
13214 ><P
13215 >Example: <B
13216 CLASS="COMMAND"
13217 >preexec = echo \"%u connected to %S from %m
13218                 (%I)\" &#62;&#62; /tmp/log</B
13219 ></P
13220 ></DD
13221 ><DT
13222 ><A
13223 NAME="PREEXECCLOSE"
13224 ></A
13225 >preexec close (S)</DT
13226 ><DD
13227 ><P
13228 >This boolean option controls whether a non-zero
13229                 return code from <A
13230 HREF="#PREEXEC"
13231 ><TT
13232 CLASS="PARAMETER"
13233 ><I
13234 >preexec
13235                 </I
13236 ></TT
13237 ></A
13238 > should close the service being connected to.</P
13239 ><P
13240 >Default: <B
13241 CLASS="COMMAND"
13242 >preexec close = no</B
13243 ></P
13244 ></DD
13245 ><DT
13246 ><A
13247 NAME="PREFERREDMASTER"
13248 ></A
13249 >preferred master (G)</DT
13250 ><DD
13251 ><P
13252 >This boolean parameter controls if <A
13253 HREF="nmbd.8.html"
13254 TARGET="_top"
13255 >nmbd(8)</A
13256 > is a preferred master browser
13257                 for its workgroup.</P
13258 ><P
13259 >If this is set to true, on startup, <B
13260 CLASS="COMMAND"
13261 >nmbd</B
13262 >
13263                 will force an election, and it will have a slight advantage in
13264                 winning the election.  It is recommended that this parameter is
13265                 used in conjunction with <B
13266 CLASS="COMMAND"
13267 ><A
13268 HREF="#DOMAINMASTER"
13269 ><TT
13270 CLASS="PARAMETER"
13271 ><I
13272 >               domain master</I
13273 ></TT
13274 ></A
13275 > = yes</B
13276 >, so that <B
13277 CLASS="COMMAND"
13278 >               nmbd</B
13279 > can guarantee becoming a domain master.</P
13280 ><P
13281 >Use this option with caution, because if there are several
13282                 hosts (whether Samba servers, Windows 95 or NT) that are preferred
13283                 master browsers on the same subnet, they will each periodically
13284                 and continuously attempt to become the local master browser.
13285                 This will result in unnecessary broadcast traffic and reduced browsing
13286                 capabilities.</P
13287 ><P
13288 >See also <A
13289 HREF="#OSLEVEL"
13290 ><TT
13291 CLASS="PARAMETER"
13292 ><I
13293 >os level</I
13294 ></TT
13295 >
13296                 </A
13297 >.</P
13298 ><P
13299 >Default: <B
13300 CLASS="COMMAND"
13301 >preferred master = auto</B
13302 ></P
13303 ></DD
13304 ><DT
13305 ><A
13306 NAME="PREFEREDMASTER"
13307 ></A
13308 >prefered master (G)</DT
13309 ><DD
13310 ><P
13311 >Synonym for <A
13312 HREF="#PREFERREDMASTER"
13313 ><TT
13314 CLASS="PARAMETER"
13315 ><I
13316 >               preferred master</I
13317 ></TT
13318 ></A
13319 > for people who cannot spell :-).</P
13320 ></DD
13321 ><DT
13322 ><A
13323 NAME="PRELOAD"
13324 ></A
13325 >preload</DT
13326 ><DD
13327 ><P
13328 >This is a list of services that you want to be
13329                 automatically added to the browse lists. This is most useful
13330                 for homes and printers services that would otherwise not be
13331                 visible.</P
13332 ><P
13333 >Note that if you just want all printers in your
13334                 printcap file loaded then the <A
13335 HREF="#LOADPRINTERS"
13336 >               <TT
13337 CLASS="PARAMETER"
13338 ><I
13339 >load printers</I
13340 ></TT
13341 ></A
13342 > option is easier.</P
13343 ><P
13344 >Default: <EM
13345 >no preloaded services</EM
13346 ></P
13347 ><P
13348 >Example: <B
13349 CLASS="COMMAND"
13350 >preload = fred lp colorlp</B
13351 ></P
13352 ></DD
13353 ><DT
13354 ><A
13355 NAME="PRESERVECASE"
13356 ></A
13357 >preserve case (S)</DT
13358 ><DD
13359 ><P
13360 > This controls if new filenames are created
13361                 with the case that the client passes, or if they are forced to
13362                 be the <A
13363 HREF="#DEFAULTCASE"
13364 ><TT
13365 CLASS="PARAMETER"
13366 ><I
13367 >default case
13368                 </I
13369 ></TT
13370 ></A
13371 >.</P
13372 ><P
13373 >Default: <B
13374 CLASS="COMMAND"
13375 >preserve case = yes</B
13376 ></P
13377 ><P
13378 >See the section on <A
13379 HREF="#AEN201"
13380 >NAME
13381                 MANGLING</A
13382 > for a fuller discussion.</P
13383 ></DD
13384 ><DT
13385 ><A
13386 NAME="PRINTCOMMAND"
13387 ></A
13388 >print command (S)</DT
13389 ><DD
13390 ><P
13391 >After a print job has finished spooling to
13392                 a service, this command will be used via a <B
13393 CLASS="COMMAND"
13394 >system()</B
13395 >
13396                 call to process the spool file. Typically the command specified will
13397                 submit the spool file to the host's printing subsystem, but there
13398                 is no requirement that this be the case. The server will not remove
13399                 the spool file, so whatever command you specify should remove the
13400                 spool file when it has been processed, otherwise you will need to
13401                 manually remove old spool files.</P
13402 ><P
13403 >The print command is simply a text string. It will be used
13404                 verbatim, with two exceptions: All occurrences of <TT
13405 CLASS="PARAMETER"
13406 ><I
13407 >%s
13408                 </I
13409 ></TT
13410 > and <TT
13411 CLASS="PARAMETER"
13412 ><I
13413 >%f</I
13414 ></TT
13415 > will be replaced by the
13416                 appropriate spool file name, and all occurrences of <TT
13417 CLASS="PARAMETER"
13418 ><I
13419 >%p
13420                 </I
13421 ></TT
13422 > will be replaced by the appropriate printer name. The
13423                 spool file name is generated automatically by the server, the printer
13424                 name is discussed below.</P
13425 ><P
13426 >The print command <EM
13427 >MUST</EM
13428 > contain at least
13429                 one occurrence of <TT
13430 CLASS="PARAMETER"
13431 ><I
13432 >%s</I
13433 ></TT
13434 > or <TT
13435 CLASS="PARAMETER"
13436 ><I
13437 >%f
13438                 </I
13439 ></TT
13440 > - the <TT
13441 CLASS="PARAMETER"
13442 ><I
13443 >%p</I
13444 ></TT
13445 > is optional. At the time
13446                 a job is submitted, if no printer name is supplied the <TT
13447 CLASS="PARAMETER"
13448 ><I
13449 >%p
13450                 </I
13451 ></TT
13452 > will be silently removed from the printer command.</P
13453 ><P
13454 >If specified in the [global] section, the print command given
13455                 will be used for any printable service that does not have its own
13456                 print command specified.</P
13457 ><P
13458 >If there is neither a specified print command for a
13459                 printable service nor a global print command, spool files will
13460                 be created but not processed and (most importantly) not removed.</P
13461 ><P
13462 >Note that printing may fail on some UNIXes from the
13463                 <TT
13464 CLASS="CONSTANT"
13465 >nobody</TT
13466 > account. If this happens then create
13467                 an alternative guest account that can print and set the <A
13468 HREF="#GUESTACCOUNT"
13469 ><TT
13470 CLASS="PARAMETER"
13471 ><I
13472 >guest account</I
13473 ></TT
13474 ></A
13475 >
13476                 in the [global] section.</P
13477 ><P
13478 >You can form quite complex print commands by realizing
13479                 that they are just passed to a shell. For example the following
13480                 will log a print job, print the file, then remove it. Note that
13481                 ';' is the usual separator for command in shell scripts.</P
13482 ><P
13483 ><B
13484 CLASS="COMMAND"
13485 >print command = echo Printing %s &#62;&#62;
13486                 /tmp/print.log; lpr -P %p %s; rm %s</B
13487 ></P
13488 ><P
13489 >You may have to vary this command considerably depending
13490                 on how you normally print files on your system. The default for
13491                 the parameter varies depending on the setting of the <A
13492 HREF="#PRINTING"
13493 >               <TT
13494 CLASS="PARAMETER"
13495 ><I
13496 >printing</I
13497 ></TT
13498 ></A
13499 > parameter.</P
13500 ><P
13501 >Default: For <B
13502 CLASS="COMMAND"
13503 >printing= BSD, AIX, QNX, LPRNG
13504                 or PLP :</B
13505 ></P
13506 ><P
13507 ><B
13508 CLASS="COMMAND"
13509 >print command = lpr -r -P%p %s</B
13510 ></P
13511 ><P
13512 >For <B
13513 CLASS="COMMAND"
13514 >printing= SYS or HPUX :</B
13515 ></P
13516 ><P
13517 ><B
13518 CLASS="COMMAND"
13519 >print command = lp -c -d%p %s; rm %s</B
13520 ></P
13521 ><P
13522 >For <B
13523 CLASS="COMMAND"
13524 >printing=SOFTQ :</B
13525 ></P
13526 ><P
13527 ><B
13528 CLASS="COMMAND"
13529 >print command = lp -d%p -s %s; rm %s</B
13530 ></P
13531 ><P
13532 >Example: <B
13533 CLASS="COMMAND"
13534 >print command = /usr/local/samba/bin/myprintscript
13535                 %p %s</B
13536 ></P
13537 ></DD
13538 ><DT
13539 ><A
13540 NAME="PRINTOK"
13541 ></A
13542 >print ok (S)</DT
13543 ><DD
13544 ><P
13545 >Synonym for <A
13546 HREF="#PRINTABLE"
13547 >               <TT
13548 CLASS="PARAMETER"
13549 ><I
13550 >printable</I
13551 ></TT
13552 ></A
13553 >.</P
13554 ></DD
13555 ><DT
13556 ><A
13557 NAME="PRINTABLE"
13558 ></A
13559 >printable (S)</DT
13560 ><DD
13561 ><P
13562 >If this parameter is <TT
13563 CLASS="CONSTANT"
13564 >yes</TT
13565 >, then
13566                 clients may open, write to and submit spool files on the directory
13567                 specified for the service. </P
13568 ><P
13569 >Note that a printable service will ALWAYS allow writing
13570                 to the service path (user privileges permitting) via the spooling
13571                 of print data. The <A
13572 HREF="#WRITEABLE"
13573 ><TT
13574 CLASS="PARAMETER"
13575 ><I
13576 >writeable
13577                 </I
13578 ></TT
13579 ></A
13580 > parameter controls only non-printing access to
13581                 the resource.</P
13582 ><P
13583 >Default: <B
13584 CLASS="COMMAND"
13585 >printable = no</B
13586 ></P
13587 ></DD
13588 ><DT
13589 ><A
13590 NAME="PRINTCAP"
13591 ></A
13592 >printcap (G)</DT
13593 ><DD
13594 ><P
13595 >Synonym for    <A
13596 HREF="#PRINTCAPNAME"
13597 ><TT
13598 CLASS="PARAMETER"
13599 ><I
13600 >               printcap name</I
13601 ></TT
13602 ></A
13603 >.</P
13604 ></DD
13605 ><DT
13606 ><A
13607 NAME="PRINTCAPNAME"
13608 ></A
13609 >printcap name (G)</DT
13610 ><DD
13611 ><P
13612 >This parameter may be used to override the
13613                 compiled-in default printcap name used by the server (usually <TT
13614 CLASS="FILENAME"
13615 >               /etc/printcap</TT
13616 >). See the discussion of the <A
13617 HREF="#AEN78"
13618 >[printers]</A
13619 > section above for reasons
13620                 why you might want to do this.</P
13621 ><P
13622 >On System V systems that use <B
13623 CLASS="COMMAND"
13624 >lpstat</B
13625 > to
13626                 list available printers you can use <B
13627 CLASS="COMMAND"
13628 >printcap name = lpstat
13629                 </B
13630 > to automatically obtain lists of available printers. This
13631                 is the default for systems that define SYSV at configure time in
13632                 Samba (this includes most System V based systems). If <TT
13633 CLASS="PARAMETER"
13634 ><I
13635 >               printcap name</I
13636 ></TT
13637 > is set to <B
13638 CLASS="COMMAND"
13639 >lpstat</B
13640 > on
13641                 these systems then Samba will launch <B
13642 CLASS="COMMAND"
13643 >lpstat -v</B
13644 > and
13645                 attempt to parse the output to obtain a printer list.</P
13646 ><P
13647 >A minimal printcap file would look something like this:</P
13648 ><P
13649 ><TABLE
13650 BORDER="0"
13651 BGCOLOR="#E0E0E0"
13652 WIDTH="90%"
13653 ><TR
13654 ><TD
13655 ><PRE
13656 CLASS="PROGRAMLISTING"
13657 >               print1|My Printer 1
13658                 print2|My Printer 2
13659                 print3|My Printer 3
13660                 print4|My Printer 4
13661                 print5|My Printer 5
13662                 </PRE
13663 ></TD
13664 ></TR
13665 ></TABLE
13666 ></P
13667 ><P
13668 >where the '|' separates aliases of a printer. The fact
13669                 that the second alias has a space in it gives a hint to Samba
13670                 that it's a comment.</P
13671 ><P
13672 ><EM
13673 >NOTE</EM
13674 >: Under AIX the default printcap
13675                 name is <TT
13676 CLASS="FILENAME"
13677 >/etc/qconfig</TT
13678 >. Samba will assume the
13679                 file is in AIX <TT
13680 CLASS="FILENAME"
13681 >qconfig</TT
13682 > format if the string
13683                 <TT
13684 CLASS="FILENAME"
13685 >qconfig</TT
13686 > appears in the printcap filename.</P
13687 ><P
13688 >Default: <B
13689 CLASS="COMMAND"
13690 >printcap name = /etc/printcap</B
13691 ></P
13692 ><P
13693 >Example: <B
13694 CLASS="COMMAND"
13695 >printcap name = /etc/myprintcap</B
13696 ></P
13697 ></DD
13698 ><DT
13699 ><A
13700 NAME="PRINTERADMIN"
13701 ></A
13702 >printer admin (S)</DT
13703 ><DD
13704 ><P
13705 >This is a list of users that can do anything to
13706                 printers via the remote administration interfaces offered by MS-RPC
13707                 (usually using a NT workstation). Note that the root user always
13708                 has admin rights.</P
13709 ><P
13710 >Default: <B
13711 CLASS="COMMAND"
13712 >printer admin = &#60;empty string&#62;</B
13713 >
13714                 </P
13715 ><P
13716 >Example: <B
13717 CLASS="COMMAND"
13718 >printer admin = admin, @staff</B
13719 ></P
13720 ></DD
13721 ><DT
13722 ><A
13723 NAME="PRINTERDRIVER"
13724 ></A
13725 >printer driver (S)</DT
13726 ><DD
13727 ><P
13728 ><EM
13729 >Note :</EM
13730 >This is a depreciated
13731                 parameter and will be removed in the next major release
13732                 following version 2.2.  Please see the instructions in
13733                 <TT
13734 CLASS="FILENAME"
13735 >PRINTER_DRIVER2.txt</TT
13736 > in the <TT
13737 CLASS="FILENAME"
13738 >docs
13739                 </TT
13740 > of the Samba distribution for more information
13741                 on the new method of loading printer drivers onto a Samba server.
13742                 </P
13743 ><P
13744 >This option allows you to control the string
13745                 that clients receive when they ask the server for the printer driver
13746                 associated with a printer. If you are using Windows95 or Windows NT
13747                 then you can use this to automate the setup of printers on your
13748                 system.</P
13749 ><P
13750 >You need to set this parameter to the exact string (case
13751                 sensitive) that describes the appropriate printer driver for your
13752                 system. If you don't know the exact string to use then you should
13753                 first try with no <A
13754 HREF="#PRINTERDRIVER"
13755 ><TT
13756 CLASS="PARAMETER"
13757 ><I
13758 >               printer driver</I
13759 ></TT
13760 ></A
13761 > option set and the client will
13762                 give you a list of printer drivers. The appropriate strings are
13763                 shown in a scroll box after you have chosen the printer manufacturer.</P
13764 ><P
13765 >See also <A
13766 HREF="#PRINTERDRIVERFILE"
13767 ><TT
13768 CLASS="PARAMETER"
13769 ><I
13770 >printer
13771                 driver file</I
13772 ></TT
13773 ></A
13774 >.</P
13775 ><P
13776 >Example: <B
13777 CLASS="COMMAND"
13778 >printer driver = HP LaserJet 4L</B
13779 ></P
13780 ></DD
13781 ><DT
13782 ><A
13783 NAME="PRINTERDRIVERFILE"
13784 ></A
13785 >printer driver file (G)</DT
13786 ><DD
13787 ><P
13788 ><EM
13789 >Note :</EM
13790 >This is a depreciated
13791                 parameter and will be removed in the next major release
13792                 following version 2.2.  Please see the instructions in
13793                 <TT
13794 CLASS="FILENAME"
13795 >PRINTER_DRIVER2.txt</TT
13796 > in the <TT
13797 CLASS="FILENAME"
13798 >docs
13799                 </TT
13800 > of the Samba distribution for more information
13801                 on the new method of loading printer drivers onto a Samba server.
13802                 </P
13803 ><P
13804 >This parameter tells Samba where the printer driver
13805                 definition file, used when serving drivers to Windows 95 clients, is
13806                 to be found. If this is not set, the default is :</P
13807 ><P
13808 ><TT
13809 CLASS="FILENAME"
13810 ><TT
13811 CLASS="REPLACEABLE"
13812 ><I
13813 >SAMBA_INSTALL_DIRECTORY</I
13814 ></TT
13815 >
13816                 /lib/printers.def</TT
13817 ></P
13818 ><P
13819 >This file is created from Windows 95 <TT
13820 CLASS="FILENAME"
13821 >msprint.inf
13822                 </TT
13823 > files found on the Windows 95 client system. For more
13824                 details on setting up serving of printer drivers to Windows 95
13825                 clients, see the documentation file in the <TT
13826 CLASS="FILENAME"
13827 >docs/</TT
13828 >
13829                 directory, <TT
13830 CLASS="FILENAME"
13831 >PRINTER_DRIVER.txt</TT
13832 >.</P
13833 ><P
13834 >See also <A
13835 HREF="#PRINTERDRIVERLOCATION"
13836 ><TT
13837 CLASS="PARAMETER"
13838 ><I
13839 >               printer driver location</I
13840 ></TT
13841 ></A
13842 >.</P
13843 ><P
13844 >Default: <EM
13845 >None (set in compile).</EM
13846 ></P
13847 ><P
13848 >Example: <B
13849 CLASS="COMMAND"
13850 >printer driver file =
13851                 /usr/local/samba/printers/drivers.def</B
13852 ></P
13853 ></DD
13854 ><DT
13855 ><A
13856 NAME="PRINTERDRIVERLOCATION"
13857 ></A
13858 >printer driver location (S)</DT
13859 ><DD
13860 ><P
13861 ><EM
13862 >Note :</EM
13863 >This is a depreciated
13864                 parameter and will be removed in the next major release
13865                 following version 2.2.  Please see the instructions in
13866                 <TT
13867 CLASS="FILENAME"
13868 >PRINTER_DRIVER2.txt</TT
13869 > in the <TT
13870 CLASS="FILENAME"
13871 >docs
13872                 </TT
13873 > of the Samba distribution for more information
13874                 on the new method of loading printer drivers onto a Samba server.
13875                 </P
13876 ><P
13877 >This parameter tells clients of a particular printer
13878                 share where to find the printer driver files for the automatic
13879                 installation of drivers for Windows 95 machines. If Samba is set up
13880                 to serve printer drivers to Windows 95 machines, this should be set to</P
13881 ><P
13882 ><B
13883 CLASS="COMMAND"
13884 >\\MACHINE\PRINTER$</B
13885 ></P
13886 ><P
13887 >Where MACHINE is the NetBIOS name of your Samba server,
13888                 and PRINTER$ is a share you set up for serving printer driver
13889                 files. For more details on setting this up see the documentation
13890                 file in the <TT
13891 CLASS="FILENAME"
13892 >docs/</TT
13893 > directory, <TT
13894 CLASS="FILENAME"
13895 >               PRINTER_DRIVER.txt</TT
13896 >.</P
13897 ><P
13898 >See also <A
13899 HREF="#PRINTERDRIVERFILE"
13900 ><TT
13901 CLASS="PARAMETER"
13902 ><I
13903 >               printer driver file</I
13904 ></TT
13905 ></A
13906 >.</P
13907 ><P
13908 >Default: <B
13909 CLASS="COMMAND"
13910 >none</B
13911 ></P
13912 ><P
13913 >Example: <B
13914 CLASS="COMMAND"
13915 >printer driver location = \\MACHINE\PRINTER$
13916                 </B
13917 ></P
13918 ></DD
13919 ><DT
13920 ><A
13921 NAME="PRINTERNAME"
13922 ></A
13923 >printer name (S)</DT
13924 ><DD
13925 ><P
13926 >This parameter specifies the name of the printer
13927                 to which print jobs spooled through a printable service will be sent.</P
13928 ><P
13929 >If specified in the [global] section, the printer
13930                 name given will be used for any printable service that does
13931                 not have its own printer name specified.</P
13932 ><P
13933 >Default: <EM
13934 >none (but may be <TT
13935 CLASS="CONSTANT"
13936 >lp</TT
13937 >
13938                 on many systems)</EM
13939 ></P
13940 ><P
13941 >Example: <B
13942 CLASS="COMMAND"
13943 >printer name = laserwriter</B
13944 ></P
13945 ></DD
13946 ><DT
13947 ><A
13948 NAME="PRINTER"
13949 ></A
13950 >printer (S)</DT
13951 ><DD
13952 ><P
13953 >Synonym for <A
13954 HREF="#PRINTERNAME"
13955 ><TT
13956 CLASS="PARAMETER"
13957 ><I
13958 >               printer name</I
13959 ></TT
13960 ></A
13961 >.</P
13962 ></DD
13963 ><DT
13964 ><A
13965 NAME="PRINTING"
13966 ></A
13967 >printing (S)</DT
13968 ><DD
13969 ><P
13970 >This parameters controls how printer status
13971                 information is interpreted on your system. It also affects the
13972                 default values for the <TT
13973 CLASS="PARAMETER"
13974 ><I
13975 >print command</I
13976 ></TT
13977 >,
13978                 <TT
13979 CLASS="PARAMETER"
13980 ><I
13981 >lpq command</I
13982 ></TT
13983 >, <TT
13984 CLASS="PARAMETER"
13985 ><I
13986 >lppause command
13987                 </I
13988 ></TT
13989 >, <TT
13990 CLASS="PARAMETER"
13991 ><I
13992 >lpresume command</I
13993 ></TT
13994 >, and
13995                 <TT
13996 CLASS="PARAMETER"
13997 ><I
13998 >lprm command</I
13999 ></TT
14000 > if specified in the
14001                 [global]f&#62; section.</P
14002 ><P
14003 >Currently eight printing styles are supported. They are
14004                 <TT
14005 CLASS="CONSTANT"
14006 >BSD</TT
14007 >, <TT
14008 CLASS="CONSTANT"
14009 >AIX</TT
14010 >,
14011                 <TT
14012 CLASS="CONSTANT"
14013 >LPRNG</TT
14014 >, <TT
14015 CLASS="CONSTANT"
14016 >PLP</TT
14017 >,
14018                 <TT
14019 CLASS="CONSTANT"
14020 >SYSV</TT
14021 >, <TT
14022 CLASS="CONSTANT"
14023 >HPUX</TT
14024 >,
14025                 <TT
14026 CLASS="CONSTANT"
14027 >QNX</TT
14028 >, <TT
14029 CLASS="CONSTANT"
14030 >SOFTQ</TT
14031 >,
14032                 and <TT
14033 CLASS="CONSTANT"
14034 >CUPS</TT
14035 >.</P
14036 ><P
14037 >To see what the defaults are for the other print
14038                 commands when using the various options use the <A
14039 HREF="testparm.1.html"
14040 TARGET="_top"
14041 >testparm(1)</A
14042 > program.</P
14043 ><P
14044 >This option can be set on a per printer basis</P
14045 ><P
14046 >See also the discussion in the <A
14047 HREF="#AEN78"
14048 >               [printers]</A
14049 > section.</P
14050 ></DD
14051 ><DT
14052 ><A
14053 NAME="PROTOCOL"
14054 ></A
14055 >protocol (G)</DT
14056 ><DD
14057 ><P
14058 >Synonym for <A
14059 HREF="#MAXPROTOCOL"
14060 >               <TT
14061 CLASS="PARAMETER"
14062 ><I
14063 >max protocol</I
14064 ></TT
14065 ></A
14066 >.</P
14067 ></DD
14068 ><DT
14069 ><A
14070 NAME="PUBLIC"
14071 ></A
14072 >public (S)</DT
14073 ><DD
14074 ><P
14075 >Synonym for <A
14076 HREF="#GUESTOK"
14077 ><TT
14078 CLASS="PARAMETER"
14079 ><I
14080 >guest
14081                 ok</I
14082 ></TT
14083 ></A
14084 >.</P
14085 ></DD
14086 ><DT
14087 ><A
14088 NAME="QUEUEPAUSECOMMAND"
14089 ></A
14090 >queuepause command (S)</DT
14091 ><DD
14092 ><P
14093 >This parameter specifies the command to be
14094                 executed on the server host in order to pause the printerqueue.</P
14095 ><P
14096 >This command should be a program or script which takes
14097                 a printer name as its only parameter and stops the printerqueue,
14098                 such that no longer jobs are submitted to the printer.</P
14099 ><P
14100 >This command is not supported by Windows for Workgroups,
14101                 but can be issued from the Printer's window under Windows 95
14102                 and NT.</P
14103 ><P
14104 >If a <TT
14105 CLASS="PARAMETER"
14106 ><I
14107 >%p</I
14108 ></TT
14109 > is given then the printername
14110                 is put in its place. Otherwise it is placed at the end of the command.
14111                 </P
14112 ><P
14113 >Note that it is good practice to include the absolute
14114                 path in the command as the PATH may not be available to the
14115                 server.</P
14116 ><P
14117 >Default: <EM
14118 >depends on the setting of <TT
14119 CLASS="PARAMETER"
14120 ><I
14121 >printing
14122                 </I
14123 ></TT
14124 ></EM
14125 ></P
14126 ><P
14127 >Example: <B
14128 CLASS="COMMAND"
14129 >queuepause command = disable %p</B
14130 ></P
14131 ></DD
14132 ><DT
14133 ><A
14134 NAME="QUEUERESUMECOMMAND"
14135 ></A
14136 >queueresume command (S)</DT
14137 ><DD
14138 ><P
14139 >This parameter specifies the command to be
14140                 executed on the server host in order to resume the printerqueue. It
14141                 is the command to undo the behavior that is caused by the
14142                 previous parameter (<A
14143 HREF="#QUEUEPAUSECOMMAND"
14144 ><TT
14145 CLASS="PARAMETER"
14146 ><I
14147 >               queuepause command</I
14148 ></TT
14149 ></A
14150 >).</P
14151 ><P
14152 >This command should be a program or script which takes
14153                 a printer name as its only parameter and resumes the printerqueue,
14154                 such that queued jobs are resubmitted to the printer.</P
14155 ><P
14156 >This command is not supported by Windows for Workgroups,
14157                 but can be issued from the Printer's window under Windows 95
14158                 and NT.</P
14159 ><P
14160 >If a <TT
14161 CLASS="PARAMETER"
14162 ><I
14163 >%p</I
14164 ></TT
14165 > is given then the printername
14166                 is put in its place. Otherwise it is placed at the end of the
14167                 command.</P
14168 ><P
14169 >Note that it is good practice to include the absolute
14170                 path in the command as the PATH may not be available to the
14171                 server.</P
14172 ><P
14173 >Default: <EM
14174 >depends on the setting of <A
14175 HREF="#PRINTING"
14176 ><TT
14177 CLASS="PARAMETER"
14178 ><I
14179 >printing</I
14180 ></TT
14181 ></A
14182 ></EM
14183 >
14184                 </P
14185 ><P
14186 >Example: <B
14187 CLASS="COMMAND"
14188 >queuepause command = enable %p
14189                 </B
14190 ></P
14191 ></DD
14192 ><DT
14193 ><A
14194 NAME="READBMPX"
14195 ></A
14196 >read bmpx (G)</DT
14197 ><DD
14198 ><P
14199 >This boolean parameter controls whether <A
14200 HREF="smbd.8.html"
14201 TARGET="_top"
14202 >smbd(8)</A
14203 > will support the "Read
14204                 Block Multiplex" SMB. This is now rarely used and defaults to
14205                 <TT
14206 CLASS="CONSTANT"
14207 >no</TT
14208 >. You should never need to set this
14209                 parameter.</P
14210 ><P
14211 >Default: <B
14212 CLASS="COMMAND"
14213 >read bmpx = no</B
14214 ></P
14215 ></DD
14216 ><DT
14217 ><A
14218 NAME="READLIST"
14219 ></A
14220 >read list (S)</DT
14221 ><DD
14222 ><P
14223 >This is a list of users that are given read-only
14224                 access to a service. If the connecting user is in this list then
14225                 they will not be given write access, no matter what the <A
14226 HREF="#WRITEABLE"
14227 ><TT
14228 CLASS="PARAMETER"
14229 ><I
14230 >writeable</I
14231 ></TT
14232 ></A
14233 >
14234                 option is set to. The list can include group names using the
14235                 syntax described in the <A
14236 HREF="#INVALIDUSERS"
14237 ><TT
14238 CLASS="PARAMETER"
14239 ><I
14240 >               invalid users</I
14241 ></TT
14242 ></A
14243 > parameter.</P
14244 ><P
14245 >See also the <A
14246 HREF="#WRITELIST"
14247 ><TT
14248 CLASS="PARAMETER"
14249 ><I
14250 >               write list</I
14251 ></TT
14252 ></A
14253 > parameter and the <A
14254 HREF="#INVALIDUSERS"
14255 ><TT
14256 CLASS="PARAMETER"
14257 ><I
14258 >invalid users</I
14259 ></TT
14260 >
14261                 </A
14262 > parameter.</P
14263 ><P
14264 >Default: <B
14265 CLASS="COMMAND"
14266 >read list = &#60;empty string&#62;</B
14267 ></P
14268 ><P
14269 >Example: <B
14270 CLASS="COMMAND"
14271 >read list = mary, @students</B
14272 ></P
14273 ></DD
14274 ><DT
14275 ><A
14276 NAME="READONLY"
14277 ></A
14278 >read only (S)</DT
14279 ><DD
14280 ><P
14281 >Note that this is an inverted synonym for <A
14282 HREF="#WRITEABLE"
14283 ><TT
14284 CLASS="PARAMETER"
14285 ><I
14286 >writeable</I
14287 ></TT
14288 ></A
14289 >.</P
14290 ></DD
14291 ><DT
14292 ><A
14293 NAME="READRAW"
14294 ></A
14295 >read raw (G)</DT
14296 ><DD
14297 ><P
14298 >This parameter controls whether or not the server
14299                 will support the raw read SMB requests when transferring data
14300                 to clients.</P
14301 ><P
14302 >If enabled, raw reads allow reads of 65535 bytes in
14303                 one packet. This typically provides a major performance benefit.
14304                 </P
14305 ><P
14306 >However, some clients either negotiate the allowable
14307                 block size incorrectly or are incapable of supporting larger block
14308                 sizes, and for these clients you may need to disable raw reads.</P
14309 ><P
14310 >In general this parameter should be viewed as a system tuning
14311                 tool and left severely alone. See also <A
14312 HREF="#WRITERAW"
14313 >               <TT
14314 CLASS="PARAMETER"
14315 ><I
14316 >write raw</I
14317 ></TT
14318 ></A
14319 >.</P
14320 ><P
14321 >Default: <B
14322 CLASS="COMMAND"
14323 >read raw = yes</B
14324 ></P
14325 ></DD
14326 ><DT
14327 ><A
14328 NAME="READSIZE"
14329 ></A
14330 >read size (G)</DT
14331 ><DD
14332 ><P
14333 >The option <TT
14334 CLASS="PARAMETER"
14335 ><I
14336 >read size</I
14337 ></TT
14338 >
14339                 affects the overlap of disk reads/writes with network reads/writes.
14340                 If the amount of data being transferred in several of the SMB
14341                 commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger
14342                 than this value then the server begins writing the data before it
14343                 has received the whole packet from the network, or in the case of
14344                 SMBreadbraw, it begins writing to the network before all the data
14345                 has been read from disk.</P
14346 ><P
14347 >This overlapping works best when the speeds of disk and
14348                 network access are similar, having very little effect when the
14349                 speed of one is much greater than the other.</P
14350 ><P
14351 >The default value is 16384, but very little experimentation
14352                 has been done yet to determine the optimal value, and it is likely
14353                 that the best value will vary greatly between systems anyway.
14354                 A value over 65536 is pointless and will cause you to allocate
14355                 memory unnecessarily.</P
14356 ><P
14357 >Default: <B
14358 CLASS="COMMAND"
14359 >read size = 16384</B
14360 ></P
14361 ><P
14362 >Example: <B
14363 CLASS="COMMAND"
14364 >read size = 8192</B
14365 ></P
14366 ></DD
14367 ><DT
14368 ><A
14369 NAME="REMOTEANNOUNCE"
14370 ></A
14371 >remote announce (G)</DT
14372 ><DD
14373 ><P
14374 >This option allows you to setup <A
14375 HREF="nmbd.8.html"
14376 TARGET="_top"
14377 >nmbd(8)</A
14378 > to periodically announce itself
14379                 to arbitrary IP addresses with an arbitrary workgroup name.</P
14380 ><P
14381 >This is useful if you want your Samba server to appear
14382                 in a remote workgroup for which the normal browse propagation
14383                 rules don't work. The remote workgroup can be anywhere that you
14384                 can send IP packets to.</P
14385 ><P
14386 >For example:</P
14387 ><P
14388 ><B
14389 CLASS="COMMAND"
14390 >remote announce = 192.168.2.255/SERVERS
14391                 192.168.4.255/STAFF</B
14392 ></P
14393 ><P
14394 >the above line would cause nmbd to announce itself
14395                 to the two given IP addresses using the given workgroup names.
14396                 If you leave out the workgroup name then the one given in
14397                 the <A
14398 HREF="#WORKGROUP"
14399 ><TT
14400 CLASS="PARAMETER"
14401 ><I
14402 >workgroup</I
14403 ></TT
14404 ></A
14405 >
14406                 parameter is used instead.</P
14407 ><P
14408 >The IP addresses you choose would normally be the broadcast
14409                 addresses of the remote networks, but can also be the IP addresses
14410                 of known browse masters if your network config is that stable.</P
14411 ><P
14412 >See the documentation file <TT
14413 CLASS="FILENAME"
14414 >BROWSING.txt</TT
14415 >
14416                 in the <TT
14417 CLASS="FILENAME"
14418 >docs/</TT
14419 > directory.</P
14420 ><P
14421 >Default: <B
14422 CLASS="COMMAND"
14423 >remote announce = &#60;empty string&#62;
14424                 </B
14425 ></P
14426 ></DD
14427 ><DT
14428 ><A
14429 NAME="REMOTEBROWSESYNC"
14430 ></A
14431 >remote browse sync (G)</DT
14432 ><DD
14433 ><P
14434 >This option allows you to setup <A
14435 HREF="nmbd.8.html"
14436 TARGET="_top"
14437 >nmbd(8)</A
14438 > to periodically request
14439                 synchronization of browse lists with the master browser of a samba
14440                 server that is on a remote segment. This option will allow you to
14441                 gain browse lists for multiple workgroups across routed networks. This
14442                 is done in a manner that does not work with any non-samba servers.</P
14443 ><P
14444 >This is useful if you want your Samba server and all local
14445                 clients to appear in a remote workgroup for which the normal browse
14446                 propagation rules don't work. The remote workgroup can be anywhere
14447                 that you can send IP packets to.</P
14448 ><P
14449 >For example:</P
14450 ><P
14451 ><B
14452 CLASS="COMMAND"
14453 >remote browse sync = 192.168.2.255 192.168.4.255
14454                 </B
14455 ></P
14456 ><P
14457 >the above line would cause <B
14458 CLASS="COMMAND"
14459 >nmbd</B
14460 > to request
14461                 the master browser on the specified subnets or addresses to
14462                 synchronize their browse lists with the local server.</P
14463 ><P
14464 >The IP addresses you choose would normally be the broadcast
14465                 addresses of the remote networks, but can also be the IP addresses
14466                 of known browse masters if your network config is that stable. If
14467                 a machine IP address is given Samba makes NO attempt to validate
14468                 that the remote machine is available, is listening, nor that it
14469                 is in fact the browse master on it's segment.</P
14470 ><P
14471 >Default: <B
14472 CLASS="COMMAND"
14473 >remote browse sync = &#60;empty string&#62;
14474                 </B
14475 ></P
14476 ></DD
14477 ><DT
14478 ><A
14479 NAME="RESTRICTACLWITHMASK"
14480 ></A
14481 >restrict acl with mask (S)</DT
14482 ><DD
14483 ><P
14484 >This is a boolean parameter.  If set to false (default), then
14485                 Creation of files with access control lists (ACLS) and modification of ACLs
14486                 using the Windows NT/2000 ACL editor will be applied directly to the file
14487                 or directory.</P
14488 ><P
14489 >If set to True, then all requests to set an ACL on a file will have the
14490                 parameters <A
14491 HREF="#CREATEMASK"
14492 ><TT
14493 CLASS="PARAMETER"
14494 ><I
14495 >create mask</I
14496 ></TT
14497 ></A
14498 >,
14499                 <A
14500 HREF="#FORCECREATEMODE"
14501 ><TT
14502 CLASS="PARAMETER"
14503 ><I
14504 >force create mode</I
14505 ></TT
14506 ></A
14507 >
14508                 applied before setting the ACL, and all requests to set an ACL on a directory will
14509                 have the parameters <A
14510 HREF="#DIRECTORYMASK"
14511 ><TT
14512 CLASS="PARAMETER"
14513 ><I
14514 >directory
14515                 mask</I
14516 ></TT
14517 ></A
14518 >, <A
14519 HREF="#FORCEDIRECTORYMODE"
14520 ><TT
14521 CLASS="PARAMETER"
14522 ><I
14523 >force
14524                 directory mode</I
14525 ></TT
14526 ></A
14527 > applied before setting the ACL.
14528                 </P
14529 ><P
14530 >See also <A
14531 HREF="#CREATEMASK"
14532 ><TT
14533 CLASS="PARAMETER"
14534 ><I
14535 >create mask</I
14536 ></TT
14537 ></A
14538 >,
14539                 <A
14540 HREF="#FORCECREATEMODE"
14541 ><TT
14542 CLASS="PARAMETER"
14543 ><I
14544 >force create mode</I
14545 ></TT
14546 ></A
14547 >,
14548                 <A
14549 HREF="#DIRECTORYMASK"
14550 ><TT
14551 CLASS="PARAMETER"
14552 ><I
14553 >directory mask</I
14554 ></TT
14555 ></A
14556 >,
14557                 <A
14558 HREF="#FORCEDIRECTORYMODE"
14559 ><TT
14560 CLASS="PARAMETER"
14561 ><I
14562 >force directory mode</I
14563 ></TT
14564 ></A
14565 >
14566                 </P
14567 ><P
14568 >Default: <B
14569 CLASS="COMMAND"
14570 >restrict acl with mask = no</B
14571 ></P
14572 ></DD
14573 ><DT
14574 ><A
14575 NAME="RESTRICTANONYMOUS"
14576 ></A
14577 >restrict anonymous (G)</DT
14578 ><DD
14579 ><P
14580 >This is a boolean parameter.  If it is true, then
14581                 anonymous access to the server will be restricted, namely in the
14582                 case where the server is expecting the client to send a username,
14583                 but it doesn't.  Setting it to true will force these anonymous
14584                 connections to be denied, and the client will be required to always
14585                 supply a username and password when connecting. Use of this parameter
14586                 is only recommended for homogeneous NT client environments.</P
14587 ><P
14588 >This parameter makes the use of macro expansions that rely
14589                 on the username (%U, %G, etc) consistent.  NT 4.0
14590                 likes to use anonymous connections when refreshing the share list,
14591                 and this is a way to work around that.</P
14592 ><P
14593 >When restrict anonymous is true, all anonymous connections
14594                 are denied no matter what they are for.  This can effect the ability
14595                 of a machine to access the samba Primary Domain Controller to revalidate
14596                 it's machine account after someone else has logged on the client
14597                 interactively.  The NT client will display a message saying that
14598                 the machine's account in  the domain doesn't exist or the password is
14599                 bad.  The best way to deal  with this is to reboot NT client machines
14600                 between interactive logons,  using "Shutdown and Restart", rather
14601                 than "Close all programs and logon as a different user".</P
14602 ><P
14603 >Default: <B
14604 CLASS="COMMAND"
14605 >restrict anonymous = no</B
14606 ></P
14607 ></DD
14608 ><DT
14609 ><A
14610 NAME="ROOT"
14611 ></A
14612 >root (G)</DT
14613 ><DD
14614 ><P
14615 >Synonym for <A
14616 HREF="#ROOTDIRECTORY"
14617 >               <TT
14618 CLASS="PARAMETER"
14619 ><I
14620 >root directory"</I
14621 ></TT
14622 ></A
14623 >.</P
14624 ></DD
14625 ><DT
14626 ><A
14627 NAME="ROOTDIR"
14628 ></A
14629 >root dir (G)</DT
14630 ><DD
14631 ><P
14632 >Synonym for <A
14633 HREF="#ROOTDIRECTORY"
14634 >               <TT
14635 CLASS="PARAMETER"
14636 ><I
14637 >root directory"</I
14638 ></TT
14639 ></A
14640 >.</P
14641 ></DD
14642 ><DT
14643 ><A
14644 NAME="ROOTDIRECTORY"
14645 ></A
14646 >root directory (G)</DT
14647 ><DD
14648 ><P
14649 >The server will <B
14650 CLASS="COMMAND"
14651 >chroot()</B
14652 > (i.e.
14653                 Change it's root directory) to this directory on startup. This is
14654                 not strictly necessary for secure operation. Even without it the
14655                 server will deny access to files not in one of the service entries.
14656                 It may also check for, and deny access to, soft links to other
14657                 parts of the filesystem, or attempts to use ".." in file names
14658                 to access other directories (depending on the setting of the <A
14659 HREF="#WIDELINKS"
14660 ><TT
14661 CLASS="PARAMETER"
14662 ><I
14663 >wide links</I
14664 ></TT
14665 ></A
14666 >
14667                 parameter).</P
14668 ><P
14669 >Adding a <TT
14670 CLASS="PARAMETER"
14671 ><I
14672 >root directory</I
14673 ></TT
14674 > entry other
14675                 than "/" adds an extra level of security, but at a price. It
14676                 absolutely ensures that no access is given to files not in the
14677                 sub-tree specified in the <TT
14678 CLASS="PARAMETER"
14679 ><I
14680 >root directory</I
14681 ></TT
14682 >
14683                 option, <EM
14684 >including</EM
14685 > some files needed for
14686                 complete operation of the server. To maintain full operability
14687                 of the server you will need to mirror some system files
14688                 into the <TT
14689 CLASS="PARAMETER"
14690 ><I
14691 >root directory</I
14692 ></TT
14693 > tree. In particular
14694                 you will need to mirror <TT
14695 CLASS="FILENAME"
14696 >/etc/passwd</TT
14697 > (or a
14698                 subset of it), and any binaries or configuration files needed for
14699                 printing (if required). The set of files that must be mirrored is
14700                 operating system dependent.</P
14701 ><P
14702 >Default: <B
14703 CLASS="COMMAND"
14704 >root directory = /</B
14705 ></P
14706 ><P
14707 >Example: <B
14708 CLASS="COMMAND"
14709 >root directory = /homes/smb</B
14710 ></P
14711 ></DD
14712 ><DT
14713 ><A
14714 NAME="ROOTPOSTEXEC"
14715 ></A
14716 >root postexec (S)</DT
14717 ><DD
14718 ><P
14719 >This is the same as the <TT
14720 CLASS="PARAMETER"
14721 ><I
14722 >postexec</I
14723 ></TT
14724 >
14725                 parameter except that the command is run as root. This
14726                 is useful for unmounting filesystems
14727                 (such as cdroms) after a connection is closed.</P
14728 ><P
14729 >See also <A
14730 HREF="#POSTEXEC"
14731 ><TT
14732 CLASS="PARAMETER"
14733 ><I
14734 >               postexec</I
14735 ></TT
14736 ></A
14737 >.</P
14738 ><P
14739 >Default: <B
14740 CLASS="COMMAND"
14741 >root postexec = &#60;empty string&#62;
14742                 </B
14743 ></P
14744 ></DD
14745 ><DT
14746 ><A
14747 NAME="ROOTPREEXEC"
14748 ></A
14749 >root preexec (S)</DT
14750 ><DD
14751 ><P
14752 >This is the same as the <TT
14753 CLASS="PARAMETER"
14754 ><I
14755 >preexec</I
14756 ></TT
14757 >
14758                 parameter except that the command is run as root. This
14759                 is useful for mounting filesystems (such as cdroms) after a
14760                 connection is closed.</P
14761 ><P
14762 >See also <A
14763 HREF="#PREEXEC"
14764 ><TT
14765 CLASS="PARAMETER"
14766 ><I
14767 >               preexec</I
14768 ></TT
14769 ></A
14770 > and <A
14771 HREF="#PREEXECCLOSE"
14772 >               <TT
14773 CLASS="PARAMETER"
14774 ><I
14775 >preexec close</I
14776 ></TT
14777 ></A
14778 >.</P
14779 ><P
14780 >Default: <B
14781 CLASS="COMMAND"
14782 >root preexec = &#60;empty string&#62;
14783                 </B
14784 ></P
14785 ></DD
14786 ><DT
14787 ><A
14788 NAME="ROOTPREEXECCLOSE"
14789 ></A
14790 >root preexec close (S)</DT
14791 ><DD
14792 ><P
14793 >This is the same as the <TT
14794 CLASS="PARAMETER"
14795 ><I
14796 >preexec close
14797                 </I
14798 ></TT
14799 > parameter except that the command is run as root.</P
14800 ><P
14801 >See also <A
14802 HREF="#PREEXEC"
14803 ><TT
14804 CLASS="PARAMETER"
14805 ><I
14806 >               preexec</I
14807 ></TT
14808 ></A
14809 > and <A
14810 HREF="#PREEXECCLOSE"
14811 >               <TT
14812 CLASS="PARAMETER"
14813 ><I
14814 >preexec close</I
14815 ></TT
14816 ></A
14817 >.</P
14818 ><P
14819 >Default: <B
14820 CLASS="COMMAND"
14821 >root preexec close = no</B
14822 ></P
14823 ></DD
14824 ><DT
14825 ><A
14826 NAME="SECURITY"
14827 ></A
14828 >security (G)</DT
14829 ><DD
14830 ><P
14831 >This option affects how clients respond to
14832                 Samba and is one of the most important settings in the <TT
14833 CLASS="FILENAME"
14834 >               smb.conf</TT
14835 > file.</P
14836 ><P
14837 >The option sets the "security mode bit" in replies to
14838                 protocol negotiations with <A
14839 HREF="smbd.8.html"
14840 TARGET="_top"
14841 >smbd(8)
14842                 </A
14843 > to turn share level security on or off. Clients decide
14844                 based on this bit whether (and how) to transfer user and password
14845                 information to the server.</P
14846 ><P
14847 >The default is <B
14848 CLASS="COMMAND"
14849 >security = user</B
14850 >, as this is
14851                 the most common setting needed when talking to Windows 98 and
14852                 Windows NT.</P
14853 ><P
14854 >The alternatives are <B
14855 CLASS="COMMAND"
14856 >security = share</B
14857 >,
14858                 <B
14859 CLASS="COMMAND"
14860 >security = server</B
14861 > or <B
14862 CLASS="COMMAND"
14863 >security=domain
14864                 </B
14865 >.</P
14866 ><P
14867 >In versions of Samba prior to 2..0, the default was
14868                 <B
14869 CLASS="COMMAND"
14870 >security = share</B
14871 > mainly because that was
14872                 the only option at one stage.</P
14873 ><P
14874 >There is a bug in WfWg that has relevance to this
14875                 setting. When in user or server level security a WfWg client
14876                 will totally ignore the password you type in the "connect
14877                 drive" dialog box. This makes it very difficult (if not impossible)
14878                 to connect to a Samba service as anyone except the user that
14879                 you are logged into WfWg as.</P
14880 ><P
14881 >If your PCs use usernames that are the same as their
14882                 usernames on the UNIX machine then you will want to use
14883                 <B
14884 CLASS="COMMAND"
14885 >security = user</B
14886 >. If you mostly use usernames
14887                 that don't exist on the UNIX box then use <B
14888 CLASS="COMMAND"
14889 >security =
14890                 share</B
14891 >.</P
14892 ><P
14893 >You should also use <B
14894 CLASS="COMMAND"
14895 >security = share</B
14896 > if you
14897                 want to mainly setup shares without a password (guest shares). This
14898                 is commonly used for a shared printer server. It is more difficult
14899                 to setup guest shares with <B
14900 CLASS="COMMAND"
14901 >security = user</B
14902 >, see
14903                 the <A
14904 HREF="#MAPTOGUEST"
14905 ><TT
14906 CLASS="PARAMETER"
14907 ><I
14908 >map to guest</I
14909 ></TT
14910 >
14911                 </A
14912 >parameter for details.</P
14913 ><P
14914 >It is possible to use <B
14915 CLASS="COMMAND"
14916 >smbd</B
14917 > in a <EM
14918 >               hybrid mode</EM
14919 > where it is offers both user and share
14920                 level security under different <A
14921 HREF="#NETBIOSALIASES"
14922 >               <TT
14923 CLASS="PARAMETER"
14924 ><I
14925 >NetBIOS aliases</I
14926 ></TT
14927 ></A
14928 >. </P
14929 ><P
14930 >The different settings will now be explained.</P
14931 ><P
14932 ><A
14933 NAME="SECURITYEQUALSSHARE"
14934 ></A
14935 ><EM
14936 >SECURITY = SHARE
14937                 </EM
14938 ></P
14939 ><P
14940 >When clients connect to a share level security server then
14941                 need not log onto the server with a valid username and password before
14942                 attempting to connect to a shared resource (although modern clients
14943                 such as Windows 95/98 and Windows NT will send a logon request with
14944                 a username but no password when talking to a <B
14945 CLASS="COMMAND"
14946 >security = share
14947                 </B
14948 > server). Instead, the clients send authentication information
14949                 (passwords) on a per-share basis, at the time they attempt to connect
14950                 to that share.</P
14951 ><P
14952 >Note that <B
14953 CLASS="COMMAND"
14954 >smbd</B
14955 > <EM
14956 >ALWAYS</EM
14957 >
14958                 uses a valid UNIX user to act on behalf of the client, even in
14959                 <B
14960 CLASS="COMMAND"
14961 >security = share</B
14962 > level security.</P
14963 ><P
14964 >As clients are not required to send a username to the server
14965                 in share level security, <B
14966 CLASS="COMMAND"
14967 >smbd</B
14968 > uses several
14969                 techniques to determine the correct UNIX user to use on behalf
14970                 of the client.</P
14971 ><P
14972 >A list of possible UNIX usernames to match with the given
14973                 client password is constructed using the following methods :</P
14974 ><P
14975 ></P
14976 ><UL
14977 ><LI
14978 ><P
14979 >If the <A
14980 HREF="#GUESTONLY"
14981 ><TT
14982 CLASS="PARAMETER"
14983 ><I
14984 >guest
14985                         only</I
14986 ></TT
14987 ></A
14988 > parameter is set, then all the other
14989                         stages are missed and only the <A
14990 HREF="#GUESTACCOUNT"
14991 >                       <TT
14992 CLASS="PARAMETER"
14993 ><I
14994 >guest account</I
14995 ></TT
14996 ></A
14997 > username is checked.
14998                         </P
14999 ></LI
15000 ><LI
15001 ><P
15002 >Is a username is sent with the share connection
15003                         request, then this username (after mapping - see <A
15004 HREF="#USERNAMEMAP"
15005 ><TT
15006 CLASS="PARAMETER"
15007 ><I
15008 >username map</I
15009 ></TT
15010 ></A
15011 >),
15012                         is added as a potential username.</P
15013 ></LI
15014 ><LI
15015 ><P
15016 >If the client did a previous <EM
15017 >logon
15018                         </EM
15019 > request (the SessionSetup SMB call) then the
15020                         username sent in this SMB will be added as a potential username.
15021                         </P
15022 ></LI
15023 ><LI
15024 ><P
15025 >The name of the service the client requested is
15026                         added as a potential username.</P
15027 ></LI
15028 ><LI
15029 ><P
15030 >The NetBIOS name of the client is added to
15031                         the list as a potential username.</P
15032 ></LI
15033 ><LI
15034 ><P
15035 >Any users on the <A
15036 HREF="#USER"
15037 ><TT
15038 CLASS="PARAMETER"
15039 ><I
15040 >                       user</I
15041 ></TT
15042 ></A
15043 > list are added as potential usernames.
15044                         </P
15045 ></LI
15046 ></UL
15047 ><P
15048 >If the <TT
15049 CLASS="PARAMETER"
15050 ><I
15051 >guest only</I
15052 ></TT
15053 > parameter is
15054                 not set, then this list is then tried with the supplied password.
15055                 The first user for whom the password matches will be used as the
15056                 UNIX user.</P
15057 ><P
15058 >If the <TT
15059 CLASS="PARAMETER"
15060 ><I
15061 >guest only</I
15062 ></TT
15063 > parameter is
15064                 set, or no username can be determined then if the share is marked
15065                 as available to the <TT
15066 CLASS="PARAMETER"
15067 ><I
15068 >guest account</I
15069 ></TT
15070 >, then this
15071                 guest user will be used, otherwise access is denied.</P
15072 ><P
15073 >Note that it can be <EM
15074 >very</EM
15075 > confusing
15076                 in share-level security as to which UNIX username will eventually
15077                 be used in granting access.</P
15078 ><P
15079 >See also the section <A
15080 HREF="#AEN234"
15081 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15082 >.</P
15083 ><P
15084 ><A
15085 NAME="SECURITYEQUALSUSER"
15086 ></A
15087 ><EM
15088 >SECURIYT = USER
15089                 </EM
15090 ></P
15091 ><P
15092 >This is the default security setting in Samba 2.2.
15093                 With user-level security a client must first "log=on" with a
15094                 valid username and password (which can be mapped using the <A
15095 HREF="#USERNAMEMAP"
15096 ><TT
15097 CLASS="PARAMETER"
15098 ><I
15099 >username map</I
15100 ></TT
15101 ></A
15102 >
15103                 parameter). Encrypted passwords (see the <A
15104 HREF="#ENCRYPTPASSWORDS"
15105 >               <TT
15106 CLASS="PARAMETER"
15107 ><I
15108 >encrypted passwords</I
15109 ></TT
15110 ></A
15111 > parameter) can also
15112                 be used in this security mode. Parameters such as <A
15113 HREF="#USER"
15114 >               <TT
15115 CLASS="PARAMETER"
15116 ><I
15117 >user</I
15118 ></TT
15119 ></A
15120 > and <A
15121 HREF="#GUESTONLY"
15122 >               <TT
15123 CLASS="PARAMETER"
15124 ><I
15125 >guest only</I
15126 ></TT
15127 ></A
15128 > if set        are then applied and
15129                 may change the UNIX user to use on this connection, but only after
15130                 the user has been successfully authenticated.</P
15131 ><P
15132 ><EM
15133 >Note</EM
15134 > that the name of the resource being
15135                 requested is <EM
15136 >not</EM
15137 > sent to the server until after
15138                 the server has successfully authenticated the client. This is why
15139                 guest shares don't work in user level security without allowing
15140                 the server to automatically map unknown users into the <A
15141 HREF="#GUESTACCOUNT"
15142 ><TT
15143 CLASS="PARAMETER"
15144 ><I
15145 >guest account</I
15146 ></TT
15147 ></A
15148 >.
15149                 See the <A
15150 HREF="#MAPTOGUEST"
15151 ><TT
15152 CLASS="PARAMETER"
15153 ><I
15154 >map to guest</I
15155 ></TT
15156 >
15157                 </A
15158 > parameter for details on doing this.</P
15159 ><P
15160 >See also the section <A
15161 HREF="#AEN234"
15162 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15163 >.</P
15164 ><P
15165 ><A
15166 NAME="SECURITYEQUALSSERVER"
15167 ></A
15168 ><EM
15169 >SECURITY = SERVER
15170                 </EM
15171 ></P
15172 ><P
15173 >In this mode Samba will try to validate the username/password
15174                 by passing it to another SMB server, such as an NT box. If this
15175                 fails it will revert to <B
15176 CLASS="COMMAND"
15177 >security = user</B
15178 >, but note
15179                 that if encrypted passwords have been negotiated then Samba cannot
15180                 revert back to checking the UNIX password file, it must have a valid
15181                 <TT
15182 CLASS="FILENAME"
15183 >smbpasswd</TT
15184 > file to check users against. See the
15185                 documentation file in the <TT
15186 CLASS="FILENAME"
15187 >docs/</TT
15188 > directory
15189                 <TT
15190 CLASS="FILENAME"
15191 >ENCRYPTION.txt</TT
15192 > for details on how to set this
15193                 up.</P
15194 ><P
15195 ><EM
15196 >Note</EM
15197 > that from the clients point of
15198                 view <B
15199 CLASS="COMMAND"
15200 >security = server</B
15201 > is the same as <B
15202 CLASS="COMMAND"
15203 >               security = user</B
15204 >.  It only affects how the server deals
15205                 with the authentication, it does not in any way affect what the
15206                 client sees.</P
15207 ><P
15208 ><EM
15209 >Note</EM
15210 > that the name of the resource being
15211                 requested is <EM
15212 >not</EM
15213 > sent to the server until after
15214                 the server has successfully authenticated the client. This is why
15215                 guest shares don't work in user level security without allowing
15216                 the server to automatically map unknown users into the <A
15217 HREF="#GUESTACCOUNT"
15218 ><TT
15219 CLASS="PARAMETER"
15220 ><I
15221 >guest account</I
15222 ></TT
15223 ></A
15224 >.
15225                 See the <A
15226 HREF="#MAPTOGUEST"
15227 ><TT
15228 CLASS="PARAMETER"
15229 ><I
15230 >map to guest</I
15231 ></TT
15232 >
15233                 </A
15234 > parameter for details on doing this.</P
15235 ><P
15236 >See also the section <A
15237 HREF="#AEN234"
15238 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15239 >.</P
15240 ><P
15241 >See also the <A
15242 HREF="#PASSWORDSERVER"
15243 ><TT
15244 CLASS="PARAMETER"
15245 ><I
15246 >password
15247                 server</I
15248 ></TT
15249 ></A
15250 > parameter and the <A
15251 HREF="#ENCRYPTPASSWORDS"
15252 ><TT
15253 CLASS="PARAMETER"
15254 ><I
15255 >encrypted passwords</I
15256 ></TT
15257 >
15258                 </A
15259 > parameter.</P
15260 ><P
15261 ><A
15262 NAME="SECURITYEQUALSDOMAIN"
15263 ></A
15264 ><EM
15265 >SECURITY = DOMAIN
15266                 </EM
15267 ></P
15268 ><P
15269 >This mode will only work correctly if <A
15270 HREF="smbpasswd.8.html"
15271 TARGET="_top"
15272 >smbpasswd(8)</A
15273 > has been used to add this
15274                 machine into a Windows NT Domain. It expects the <A
15275 HREF="#ENCRYPTPASSWORDS"
15276 ><TT
15277 CLASS="PARAMETER"
15278 ><I
15279 >encrypted passwords</I
15280 ></TT
15281 >
15282                 </A
15283 > parameter to be set to <TT
15284 CLASS="CONSTANT"
15285 >true</TT
15286 >. In this
15287                 mode Samba will try to validate the username/password by passing
15288                 it to a Windows NT Primary or Backup Domain Controller, in exactly
15289                 the same way that a Windows NT Server would do.</P
15290 ><P
15291 ><EM
15292 >Note</EM
15293 > that a valid UNIX user must still
15294                 exist as well as the account on the Domain Controller to allow
15295                 Samba to have a valid UNIX account to map file access to.</P
15296 ><P
15297 ><EM
15298 >Note</EM
15299 > that from the clients point
15300                 of view <B
15301 CLASS="COMMAND"
15302 >security = domain</B
15303 > is the same as <B
15304 CLASS="COMMAND"
15305 >security = user
15306                 </B
15307 >. It only affects how the server deals with the authentication,
15308                 it does not in any way affect what the client sees.</P
15309 ><P
15310 ><EM
15311 >Note</EM
15312 > that the name of the resource being
15313                 requested is <EM
15314 >not</EM
15315 > sent to the server until after
15316                 the server has successfully authenticated the client. This is why
15317                 guest shares don't work in user level security without allowing
15318                 the server to automatically map unknown users into the <A
15319 HREF="#GUESTACCOUNT"
15320 ><TT
15321 CLASS="PARAMETER"
15322 ><I
15323 >guest account</I
15324 ></TT
15325 ></A
15326 >.
15327                 See the <A
15328 HREF="#MAPTOGUEST"
15329 ><TT
15330 CLASS="PARAMETER"
15331 ><I
15332 >map to guest</I
15333 ></TT
15334 >
15335                 </A
15336 > parameter for details on doing this.</P
15337 ><P
15338 ><EM
15339 >BUG:</EM
15340 > There is currently a bug in the
15341                 implementation of <B
15342 CLASS="COMMAND"
15343 >security = domain</B
15344 > with respect
15345                 to multi-byte character set usernames. The communication with a
15346                 Domain Controller must be done in UNICODE and Samba currently
15347                 does not widen multi-byte user names to UNICODE correctly, thus
15348                 a multi-byte username will not be recognized correctly at the
15349                 Domain Controller. This issue will be addressed in a future release.</P
15350 ><P
15351 >See also the section <A
15352 HREF="#AEN234"
15353 >               NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
15354 >.</P
15355 ><P
15356 >See also the <A
15357 HREF="#PASSWORDSERVER"
15358 ><TT
15359 CLASS="PARAMETER"
15360 ><I
15361 >password
15362                 server</I
15363 ></TT
15364 ></A
15365 > parameter and the <A
15366 HREF="#ENCRYPTPASSWORDS"
15367 ><TT
15368 CLASS="PARAMETER"
15369 ><I
15370 >encrypted passwords</I
15371 ></TT
15372 >
15373                 </A
15374 > parameter.</P
15375 ><P
15376 >Default: <B
15377 CLASS="COMMAND"
15378 >security = USER</B
15379 ></P
15380 ><P
15381 >Example: <B
15382 CLASS="COMMAND"
15383 >security = DOMAIN</B
15384 ></P
15385 ></DD
15386 ><DT
15387 ><A
15388 NAME="SECURITYMASK"
15389 ></A
15390 >security mask (S)</DT
15391 ><DD
15392 ><P
15393 >This parameter controls what UNIX permission
15394                 bits can be modified when a Windows NT client is manipulating
15395                 the UNIX permission on a file using the native NT security
15396                 dialog box.</P
15397 ><P
15398 >This parameter is applied as a mask (AND'ed with) to
15399                 the changed permission bits, thus preventing any bits not in
15400                 this mask from being modified. Essentially, zero bits in this
15401                 mask may be treated as a set of bits the user is not allowed
15402                 to change.</P
15403 ><P
15404 >If not set explicitly this parameter is set to the same
15405                 value as the <A
15406 HREF="#CREATEMASK"
15407 ><TT
15408 CLASS="PARAMETER"
15409 ><I
15410 >create mask
15411                 </I
15412 ></TT
15413 ></A
15414 > parameter. To allow a user to modify all the
15415                 user/group/world permissions on a file, set this parameter to
15416                 0777.</P
15417 ><P
15418 ><EM
15419 >Note</EM
15420 > that users who can access the
15421                 Samba server through other means can easily bypass this
15422                 restriction, so it is primarily useful for standalone
15423                 "appliance" systems.  Administrators of most normal systems will
15424                 probably want to set it to 0777.</P
15425 ><P
15426 >See also the <A
15427 HREF="#FORCEDIRECTORYSECURITYMODE"
15428 >               <TT
15429 CLASS="PARAMETER"
15430 ><I
15431 >force directory security mode</I
15432 ></TT
15433 ></A
15434 >,
15435                 <A
15436 HREF="#DIRECTORYSECURITYMASK"
15437 ><TT
15438 CLASS="PARAMETER"
15439 ><I
15440 >directory
15441                 security mask</I
15442 ></TT
15443 ></A
15444 >, <A
15445 HREF="#FORCESECURITYMODE"
15446 >               <TT
15447 CLASS="PARAMETER"
15448 ><I
15449 >force security mode</I
15450 ></TT
15451 ></A
15452 > parameters.</P
15453 ><P
15454 >Default: <B
15455 CLASS="COMMAND"
15456 >security mask = &#60;same as create mask&#62;
15457                 </B
15458 ></P
15459 ><P
15460 >Example: <B
15461 CLASS="COMMAND"
15462 >security mask = 0777</B
15463 ></P
15464 ></DD
15465 ><DT
15466 ><A
15467 NAME="SERVERSTRING"
15468 ></A
15469 >server string (G)</DT
15470 ><DD
15471 ><P
15472 >This controls what string will show up in the
15473                 printer comment box in print manager and next to the IPC connection
15474                 in <B
15475 CLASS="COMMAND"
15476 >net view"</B
15477 >. It can be any string that you wish
15478                 to show to your users.</P
15479 ><P
15480 >It also sets what will appear in browse lists next
15481                 to the machine name.</P
15482 ><P
15483 >A <TT
15484 CLASS="PARAMETER"
15485 ><I
15486 >%v</I
15487 ></TT
15488 > will be replaced with the Samba
15489                 version number.</P
15490 ><P
15491 >A <TT
15492 CLASS="PARAMETER"
15493 ><I
15494 >%h</I
15495 ></TT
15496 > will be replaced with the
15497                 hostname.</P
15498 ><P
15499 >Default: <B
15500 CLASS="COMMAND"
15501 >server string = Samba %v</B
15502 ></P
15503 ><P
15504 >Example: <B
15505 CLASS="COMMAND"
15506 >server string = University of GNUs Samba
15507                 Server</B
15508 ></P
15509 ></DD
15510 ><DT
15511 ><A
15512 NAME="SETDIRECTORY"
15513 ></A
15514 >set directory (S)</DT
15515 ><DD
15516 ><P
15517 >If <B
15518 CLASS="COMMAND"
15519 >set directory = no</B
15520 >, then
15521                 users of the service may not use the setdir command to change
15522                 directory.</P
15523 ><P
15524 >The <B
15525 CLASS="COMMAND"
15526 >setdir</B
15527 > command is only implemented
15528                 in the Digital Pathworks client. See the Pathworks documentation
15529                 for details.</P
15530 ><P
15531 >Default: <B
15532 CLASS="COMMAND"
15533 >set directory = no</B
15534 ></P
15535 ></DD
15536 ><DT
15537 ><A
15538 NAME="SHAREMODES"
15539 ></A
15540 >share modes (S)</DT
15541 ><DD
15542 ><P
15543 >This enables or disables the honoring of
15544                 the <TT
15545 CLASS="PARAMETER"
15546 ><I
15547 >share modes</I
15548 ></TT
15549 > during a file open. These
15550                 modes are used by clients to gain exclusive read or write access
15551                 to a file.</P
15552 ><P
15553 >These open modes are not directly supported by UNIX, so
15554                 they are simulated using shared memory, or lock files if your
15555                 UNIX doesn't support shared memory (almost all do).</P
15556 ><P
15557 >The share modes that are enabled by this option are
15558                 <TT
15559 CLASS="CONSTANT"
15560 >DENY_DOS</TT
15561 >, <TT
15562 CLASS="CONSTANT"
15563 >DENY_ALL</TT
15564 >,
15565                 <TT
15566 CLASS="CONSTANT"
15567 >DENY_READ</TT
15568 >, <TT
15569 CLASS="CONSTANT"
15570 >DENY_WRITE</TT
15571 >,
15572                 <TT
15573 CLASS="CONSTANT"
15574 >DENY_NONE</TT
15575 > and <TT
15576 CLASS="CONSTANT"
15577 >DENY_FCB</TT
15578 >.
15579                 </P
15580 ><P
15581 >This option gives full share compatibility and enabled
15582                 by default.</P
15583 ><P
15584 >You should <EM
15585 >NEVER</EM
15586 > turn this parameter
15587                 off as many Windows applications will break if you do so.</P
15588 ><P
15589 >Default: <B
15590 CLASS="COMMAND"
15591 >share modes = yes</B
15592 ></P
15593 ></DD
15594 ><DT
15595 ><A
15596 NAME="SHORTPRESERVECASE"
15597 ></A
15598 >short preserve case (S)</DT
15599 ><DD
15600 ><P
15601 >This boolean parameter controls if new files
15602                 which conform to 8.3 syntax, that is all in upper case and of
15603                 suitable length, are created upper case, or if they are forced
15604                 to be the <A
15605 HREF="#DEFAULTCASE"
15606 ><TT
15607 CLASS="PARAMETER"
15608 ><I
15609 >default case
15610                 </I
15611 ></TT
15612 ></A
15613 >. This  option can be use with <A
15614 HREF="#PRESERVECASE"
15615 ><B
15616 CLASS="COMMAND"
15617 >preserve case = yes</B
15618 >
15619                 </A
15620 > to permit long filenames to retain their case, while short
15621                 names are lowered. </P
15622 ><P
15623 >See the section on <A
15624 HREF="#AEN201"
15625 >               NAME MANGLING</A
15626 >.</P
15627 ><P
15628 >Default: <B
15629 CLASS="COMMAND"
15630 >short preserve case = yes</B
15631 ></P
15632 ></DD
15633 ><DT
15634 ><A
15635 NAME="SHOWADDPRINTERWIZARD"
15636 ></A
15637 >show add printer wizard (G)</DT
15638 ><DD
15639 ><P
15640 >With the introduction of MS-RPC based printing support
15641                 for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will
15642                 appear on Samba hosts in the share listing.  Normally this folder will
15643                 contain an icon for the MS Add Printer Wizard (APW).  However, it is
15644                 possible to disable this feature regardless of the level of privilege
15645                 of the connected user.</P
15646 ><P
15647 >Under normal circumstances, the Windows NT/2000 client will
15648                 open a handle on the printer server with OpenPrinterEx() asking for
15649                 Administrator privileges.  If the user does not have administrative
15650                 access on the print server (i.e is not root or a member of the
15651                 <TT
15652 CLASS="PARAMETER"
15653 ><I
15654 >printer admin</I
15655 ></TT
15656 > group), the OpenPrinterEx()
15657                 call fails and the clients another open call with a request for
15658                 a lower privilege level.  This should succeed, however the APW
15659                 icon will not be displayed.</P
15660 ><P
15661 >Disabling the <TT
15662 CLASS="PARAMETER"
15663 ><I
15664 >show add printer wizard</I
15665 ></TT
15666 >
15667                 parameter will always cause the OpenPrinterEx() on the server
15668                 to fail.  Thus the APW icon will never be displayed. <EM
15669 >               Note :</EM
15670 >This does not prevent the same user from having
15671                 administrative privilege on an individual printer.</P
15672 ><P
15673 >See also <A
15674 HREF="#ADDPRINTERCOMMAND"
15675 ><TT
15676 CLASS="PARAMETER"
15677 ><I
15678 >addprinter
15679                 command</I
15680 ></TT
15681 ></A
15682 >, <A
15683 HREF="#DELETEPRINTERCOMMAND"
15684 >               <TT
15685 CLASS="PARAMETER"
15686 ><I
15687 >deleteprinter command</I
15688 ></TT
15689 ></A
15690 >, <A
15691 HREF="#PRINTERADMIN"
15692 ><TT
15693 CLASS="PARAMETER"
15694 ><I
15695 >printer admin</I
15696 ></TT
15697 ></A
15698 ></P
15699 ><P
15700 >Default :<B
15701 CLASS="COMMAND"
15702 >show add printer wizard = yes</B
15703 ></P
15704 ></DD
15705 ><DT
15706 ><A
15707 NAME="SMBPASSWDFILE"
15708 ></A
15709 >smb passwd file (G)</DT
15710 ><DD
15711 ><P
15712 >This option sets the path to the encrypted
15713                 smbpasswd file.  By default the path to the smbpasswd file
15714                 is compiled into Samba.</P
15715 ><P
15716 >Default: <B
15717 CLASS="COMMAND"
15718 >smb passwd file = ${prefix}/private/smbpasswd
15719                 </B
15720 ></P
15721 ><P
15722 >Example: <B
15723 CLASS="COMMAND"
15724 >smb passwd file = /etc/samba/smbpasswd
15725                 </B
15726 ></P
15727 ></DD
15728 ><DT
15729 ><A
15730 NAME="SOCKETADDRESS"
15731 ></A
15732 >socket address (G)</DT
15733 ><DD
15734 ><P
15735 >This option allows you to control what
15736                 address Samba will listen for connections on. This is used to
15737                 support multiple virtual interfaces on the one server, each
15738                 with a different configuration.</P
15739 ><P
15740 >By default samba will accept connections on any
15741                 address.</P
15742 ><P
15743 >Example: <B
15744 CLASS="COMMAND"
15745 >socket address = 192.168.2.20</B
15746 >
15747                 </P
15748 ></DD
15749 ><DT
15750 ><A
15751 NAME="SOCKETOPTIONS"
15752 ></A
15753 >socket options (G)</DT
15754 ><DD
15755 ><P
15756 >This option allows you to set socket options
15757                 to be used when talking with the client.</P
15758 ><P
15759 >Socket options are controls on the networking layer
15760                 of the operating systems which allow the connection to be
15761                 tuned.</P
15762 ><P
15763 >This option will typically be used to tune your Samba
15764                 server for optimal performance for your local network. There is
15765                 no way that Samba can know what the optimal parameters are for
15766                 your net, so you must experiment and choose them yourself. We
15767                 strongly suggest you read the appropriate documentation for your
15768                 operating system first (perhaps <B
15769 CLASS="COMMAND"
15770 >man setsockopt</B
15771 >
15772                 will help).</P
15773 ><P
15774 >You may find that on some systems Samba will say
15775                 "Unknown socket option" when you supply an option. This means you
15776                 either incorrectly  typed it or you need to add an include file
15777                 to includes.h for your OS.  If the latter is the case please
15778                 send the patch to <A
15779 HREF="mailto:samba@samba.org"
15780 TARGET="_top"
15781 >               samba@samba.org</A
15782 >.</P
15783 ><P
15784 >Any of the supported socket options may be combined
15785                 in any way you like, as long as your OS allows it.</P
15786 ><P
15787 >This is the list of socket options currently settable
15788                 using this option:</P
15789 ><P
15790 ></P
15791 ><UL
15792 ><LI
15793 ><P
15794 >SO_KEEPALIVE</P
15795 ></LI
15796 ><LI
15797 ><P
15798 >SO_REUSEADDR</P
15799 ></LI
15800 ><LI
15801 ><P
15802 >SO_BROADCAST</P
15803 ></LI
15804 ><LI
15805 ><P
15806 >TCP_NODELAY</P
15807 ></LI
15808 ><LI
15809 ><P
15810 >IPTOS_LOWDELAY</P
15811 ></LI
15812 ><LI
15813 ><P
15814 >IPTOS_THROUGHPUT</P
15815 ></LI
15816 ><LI
15817 ><P
15818 >SO_SNDBUF *</P
15819 ></LI
15820 ><LI
15821 ><P
15822 >SO_RCVBUF *</P
15823 ></LI
15824 ><LI
15825 ><P
15826 >SO_SNDLOWAT *</P
15827 ></LI
15828 ><LI
15829 ><P
15830 >SO_RCVLOWAT *</P
15831 ></LI
15832 ></UL
15833 ><P
15834 >Those marked with a <EM
15835 >'*'</EM
15836 > take an integer
15837                 argument. The others can optionally take a 1 or 0 argument to enable
15838                 or disable the option, by default they will be enabled if you
15839                 don't specify 1 or 0.</P
15840 ><P
15841 >To specify an argument use the syntax SOME_OPTION=VALUE
15842                 for example <B
15843 CLASS="COMMAND"
15844 >SO_SNDBUF=8192</B
15845 >. Note that you must
15846                 not have any spaces before or after the = sign.</P
15847 ><P
15848 >If you are on a local network then a sensible option
15849                 might be</P
15850 ><P
15851 ><B
15852 CLASS="COMMAND"
15853 >socket options = IPTOS_LOWDELAY</B
15854 ></P
15855 ><P
15856 >If you have a local network then you could try:</P
15857 ><P
15858 ><B
15859 CLASS="COMMAND"
15860 >socket options = IPTOS_LOWDELAY TCP_NODELAY</B
15861 ></P
15862 ><P
15863 >If you are on a wide area network then perhaps try
15864                 setting IPTOS_THROUGHPUT. </P
15865 ><P
15866 >Note that several of the options may cause your Samba
15867                 server to fail completely. Use these options with caution!</P
15868 ><P
15869 >Default: <B
15870 CLASS="COMMAND"
15871 >socket options = TCP_NODELAY</B
15872 ></P
15873 ><P
15874 >Example: <B
15875 CLASS="COMMAND"
15876 >socket options = IPTOS_LOWDELAY</B
15877 ></P
15878 ></DD
15879 ><DT
15880 ><A
15881 NAME="SOURCEENVIRONMENT"
15882 ></A
15883 >source environment (G)</DT
15884 ><DD
15885 ><P
15886 >This parameter causes Samba to set environment
15887                 variables as per the content of the file named.</P
15888 ><P
15889 >If the value of this parameter starts with a "|" character
15890                 then Samba will treat that value as a pipe command to open and
15891                 will set the environment variables from the output of the pipe.</P
15892 ><P
15893 >The contents of the file or the output of the pipe should
15894                 be formatted as the output of the standard Unix <B
15895 CLASS="COMMAND"
15896 >env(1)
15897                 </B
15898 > command. This is of the form :</P
15899 ><P
15900 >Example environment entry:</P
15901 ><P
15902 ><B
15903 CLASS="COMMAND"
15904 >SAMBA_NETBIOS_NAME=myhostname</B
15905 ></P
15906 ><P
15907 >Default: <EM
15908 >No default value</EM
15909 ></P
15910 ><P
15911 >Examples: <B
15912 CLASS="COMMAND"
15913 >source environment = |/etc/smb.conf.sh
15914                 </B
15915 ></P
15916 ><P
15917 >Example: <B
15918 CLASS="COMMAND"
15919 >source environment =
15920                 /usr/local/smb_env_vars</B
15921 ></P
15922 ></DD
15923 ><DT
15924 ><A
15925 NAME="SSL"
15926 ></A
15927 >ssl (G)</DT
15928 ><DD
15929 ><P
15930 >This variable is part of SSL-enabled Samba. This
15931                 is only available if the SSL libraries have been compiled on your
15932                 system and the configure option <B
15933 CLASS="COMMAND"
15934 >--with-ssl</B
15935 > was
15936                 given at configure time.</P
15937 ><P
15938 ><EM
15939 >Note</EM
15940 > that for export control reasons
15941                 this code is <EM
15942 >NOT</EM
15943 > enabled by default in any
15944                 current binary version of Samba.</P
15945 ><P
15946 >This variable enables or disables the entire SSL mode. If
15947                 it is set to <TT
15948 CLASS="CONSTANT"
15949 >no</TT
15950 >, the SSL enabled samba behaves
15951                 exactly like the non-SSL samba. If set to <TT
15952 CLASS="CONSTANT"
15953 >yes</TT
15954 >,
15955                 it depends on the variables <A
15956 HREF="#SSLHOSTS"
15957 ><TT
15958 CLASS="PARAMETER"
15959 ><I
15960 >               ssl hosts</I
15961 ></TT
15962 ></A
15963 > and <A
15964 HREF="#SSLHOSTSRESIGN"
15965 >               <TT
15966 CLASS="PARAMETER"
15967 ><I
15968 >ssl hosts resign</I
15969 ></TT
15970 ></A
15971 > whether an SSL
15972                 connection will be required.</P
15973 ><P
15974 >Default: <B
15975 CLASS="COMMAND"
15976 >ssl=no</B
15977 ></P
15978 ></DD
15979 ><DT
15980 ><A
15981 NAME="SSLCACERTDIR"
15982 ></A
15983 >ssl CA certDir (G)</DT
15984 ><DD
15985 ><P
15986 >This variable is part of SSL-enabled Samba. This
15987                 is only available if the SSL libraries have been compiled on your
15988                 system and the configure option <B
15989 CLASS="COMMAND"
15990 >--with-ssl</B
15991 > was
15992                 given at configure time.</P
15993 ><P
15994 ><EM
15995 >Note</EM
15996 > that for export control reasons
15997                 this code is <EM
15998 >NOT</EM
15999 > enabled by default in any
16000                 current binary version of Samba.</P
16001 ><P
16002 >This variable defines where to look up the Certification
16003                 Authorities. The given directory should contain one file for
16004                 each CA that samba will trust.  The file name must be the hash
16005                 value over the "Distinguished Name" of the CA. How this directory
16006                 is set up is explained later in this document. All files within the
16007                 directory that don't fit into this naming scheme are ignored. You
16008                 don't need this variable if you don't verify client certificates.</P
16009 ><P
16010 >Default: <B
16011 CLASS="COMMAND"
16012 >ssl CA certDir = /usr/local/ssl/certs
16013                 </B
16014 ></P
16015 ></DD
16016 ><DT
16017 ><A
16018 NAME="SSLCACERTFILE"
16019 ></A
16020 >ssl CA certFile (G)</DT
16021 ><DD
16022 ><P
16023 >This variable is part of SSL-enabled Samba. This
16024                 is only available if the SSL libraries have been compiled on your
16025                 system and the configure option <B
16026 CLASS="COMMAND"
16027 >--with-ssl</B
16028 > was
16029                 given at configure time.</P
16030 ><P
16031 ><EM
16032 >Note</EM
16033 > that for export control reasons
16034                 this code is <EM
16035 >NOT</EM
16036 > enabled by default in any
16037                 current binary version of Samba.</P
16038 ><P
16039 >This variable is a second way to define the trusted CAs.
16040                 The certificates of the trusted CAs are collected in one big
16041                 file and this variable points to the file. You will probably
16042                 only use one of the two ways to define your CAs. The first choice is
16043                 preferable if you have many CAs or want to be flexible, the second
16044                 is preferable if you only have one CA and want to keep things
16045                 simple (you won't need to create the hashed file names). You
16046                 don't need this variable if you don't verify client certificates.</P
16047 ><P
16048 >Default: <B
16049 CLASS="COMMAND"
16050 >ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem
16051                 </B
16052 ></P
16053 ></DD
16054 ><DT
16055 ><A
16056 NAME="SSLCIPHERS"
16057 ></A
16058 >ssl ciphers (G)</DT
16059 ><DD
16060 ><P
16061 >This variable is part of SSL-enabled Samba. This
16062                 is only available if the SSL libraries have been compiled on your
16063                 system and the configure option <B
16064 CLASS="COMMAND"
16065 >--with-ssl</B
16066 > was
16067                 given at configure time.</P
16068 ><P
16069 ><EM
16070 >Note</EM
16071 > that for export control reasons
16072                 this code is <EM
16073 >NOT</EM
16074 > enabled by default in any
16075                 current binary version of Samba.</P
16076 ><P
16077 >This variable defines the ciphers that should be offered
16078                 during SSL negotiation. You should not set this variable unless
16079                 you know what you are doing.</P
16080 ></DD
16081 ><DT
16082 ><A
16083 NAME="SSLCLIENTCERT"
16084 ></A
16085 >ssl client cert (G)</DT
16086 ><DD
16087 ><P
16088 >This variable is part of SSL-enabled Samba. This
16089                 is only available if the SSL libraries have been compiled on your
16090                 system and the configure option <B
16091 CLASS="COMMAND"
16092 >--with-ssl</B
16093 > was
16094                 given at configure time.</P
16095 ><P
16096 ><EM
16097 >Note</EM
16098 > that for export control reasons
16099                 this code is <EM
16100 >NOT</EM
16101 > enabled by default in any
16102                 current binary version of Samba.</P
16103 ><P
16104 >The certificate in this file is used by <A
16105 HREF="smbclient.1.html"
16106 TARGET="_top"
16107 >               <B
16108 CLASS="COMMAND"
16109 >smbclient(1)</B
16110 ></A
16111 > if it exists. It's needed
16112                 if the server requires a client certificate.</P
16113 ><P
16114 >Default: <B
16115 CLASS="COMMAND"
16116 >ssl client cert = /usr/local/ssl/certs/smbclient.pem
16117                 </B
16118 ></P
16119 ></DD
16120 ><DT
16121 ><A
16122 NAME="SSLCLIENTKEY"
16123 ></A
16124 >ssl client key (G)</DT
16125 ><DD
16126 ><P
16127 >This variable is part of SSL-enabled Samba. This
16128                 is only available if the SSL libraries have been compiled on your
16129                 system and the configure option <B
16130 CLASS="COMMAND"
16131 >--with-ssl</B
16132 > was
16133                 given at configure time.</P
16134 ><P
16135 ><EM
16136 >Note</EM
16137 > that for export control reasons
16138                 this code is <EM
16139 >NOT</EM
16140 > enabled by default in any
16141                 current binary version of Samba.</P
16142 ><P
16143 >This is the private key for <A
16144 HREF="smbclient.1.html"
16145 TARGET="_top"
16146 >               <B
16147 CLASS="COMMAND"
16148 >smbclient(1)</B
16149 ></A
16150 >. It's only needed if the
16151                 client should have a certificate. </P
16152 ><P
16153 >Default: <B
16154 CLASS="COMMAND"
16155 >ssl client key = /usr/local/ssl/private/smbclient.pem
16156                 </B
16157 ></P
16158 ></DD
16159 ><DT
16160 ><A
16161 NAME="SSLCOMPATIBILITY"
16162 ></A
16163 >ssl compatibility (G)</DT
16164 ><DD
16165 ><P
16166 >This variable is part of SSL-enabled Samba. This
16167                 is only available if the SSL libraries have been compiled on your
16168                 system and the configure option <B
16169 CLASS="COMMAND"
16170 >--with-ssl</B
16171 > was
16172                 given at configure time.</P
16173 ><P
16174 ><EM
16175 >Note</EM
16176 > that for export control reasons
16177                 this code is <EM
16178 >NOT</EM
16179 > enabled by default in any
16180                 current binary version of Samba.</P
16181 ><P
16182 >This variable defines whether SSLeay should be configured
16183                 for bug compatibility with other SSL implementations. This is
16184                 probably not desirable because currently no clients with SSL
16185                 implementations other than SSLeay exist.</P
16186 ><P
16187 >Default: <B
16188 CLASS="COMMAND"
16189 >ssl compatibility = no</B
16190 ></P
16191 ></DD
16192 ><DT
16193 ><A
16194 NAME="SSLHOSTS"
16195 ></A
16196 >ssl hosts (G)</DT
16197 ><DD
16198 ><P
16199 >See <A
16200 HREF="#SSLHOSTSRESIGN"
16201 ><TT
16202 CLASS="PARAMETER"
16203 ><I
16204 >               ssl hosts resign</I
16205 ></TT
16206 ></A
16207 >.</P
16208 ></DD
16209 ><DT
16210 ><A
16211 NAME="SSLHOSTSRESIGN"
16212 ></A
16213 >ssl hosts resign (G)</DT
16214 ><DD
16215 ><P
16216 >This variable is part of SSL-enabled Samba. This
16217                 is only available if the SSL libraries have been compiled on your
16218                 system and the configure option <B
16219 CLASS="COMMAND"
16220 >--with-ssl</B
16221 > was
16222                 given at configure time.</P
16223 ><P
16224 ><EM
16225 >Note</EM
16226 > that for export control reasons
16227                 this code is <EM
16228 >NOT</EM
16229 > enabled by default in any
16230                 current binary version of Samba.</P
16231 ><P
16232 >These two variables define whether samba will go
16233                 into SSL mode or not. If none of them is defined, samba will
16234                 allow only SSL connections. If the <A
16235 HREF="#SSLHOSTS"
16236 >               <TT
16237 CLASS="PARAMETER"
16238 ><I
16239 >ssl hosts</I
16240 ></TT
16241 ></A
16242 > variable lists
16243                 hosts (by IP-address, IP-address range, net group or name),
16244                 only these hosts will be forced into SSL mode. If the <TT
16245 CLASS="PARAMETER"
16246 ><I
16247 >               ssl hosts resign</I
16248 ></TT
16249 > variable lists hosts, only these
16250                 hosts will NOT be forced into SSL mode. The syntax for these two
16251                 variables is the same as for the <A
16252 HREF="#HOSTSALLOW"
16253 ><TT
16254 CLASS="PARAMETER"
16255 ><I
16256 >               hosts allow</I
16257 ></TT
16258 ></A
16259 > and <A
16260 HREF="#HOSTSDENY"
16261 >               <TT
16262 CLASS="PARAMETER"
16263 ><I
16264 >hosts deny</I
16265 ></TT
16266 ></A
16267 > pair of variables, only
16268                 that the subject of the decision is different: It's not the access
16269                 right but whether SSL is used or not. </P
16270 ><P
16271 >The example below requires SSL connections from all hosts
16272                 outside the local net (which is 192.168.*.*).</P
16273 ><P
16274 >Default: <B
16275 CLASS="COMMAND"
16276 >ssl hosts = &#60;empty string&#62;</B
16277 ></P
16278 ><P
16279 ><B
16280 CLASS="COMMAND"
16281 >ssl hosts resign = &#60;empty string&#62;</B
16282 ></P
16283 ><P
16284 >Example: <B
16285 CLASS="COMMAND"
16286 >ssl hosts resign = 192.168.</B
16287 ></P
16288 ></DD
16289 ><DT
16290 ><A
16291 NAME="SSLREQUIRECLIENTCERT"
16292 ></A
16293 >ssl require clientcert (G)</DT
16294 ><DD
16295 ><P
16296 >This variable is part of SSL-enabled Samba. This
16297                 is only available if the SSL libraries have been compiled on your
16298                 system and the configure option <B
16299 CLASS="COMMAND"
16300 >--with-ssl</B
16301 > was
16302                 given at configure time.</P
16303 ><P
16304 ><EM
16305 >Note</EM
16306 > that for export control reasons
16307                 this code is <EM
16308 >NOT</EM
16309 > enabled by default in any
16310                 current binary version of Samba.</P
16311 ><P
16312 >If this variable is set to <TT
16313 CLASS="CONSTANT"
16314 >yes</TT
16315 >, the
16316                 server will not tolerate connections from clients that don't
16317                 have a valid certificate. The directory/file given in <A
16318 HREF="#SSLCACERTDIR"
16319 ><TT
16320 CLASS="PARAMETER"
16321 ><I
16322 >ssl CA certDir</I
16323 ></TT
16324 >
16325                 </A
16326 > and <A
16327 HREF="#SSLCACERTFILE"
16328 ><TT
16329 CLASS="PARAMETER"
16330 ><I
16331 >ssl CA certFile
16332                 </I
16333 ></TT
16334 ></A
16335 > will be used to look up the CAs that issued
16336                 the client's certificate. If the certificate can't be verified
16337                 positively, the connection will be terminated.  If this variable
16338                 is set to <TT
16339 CLASS="CONSTANT"
16340 >no</TT
16341 >, clients don't need certificates.
16342                 Contrary to web applications you really <EM
16343 >should</EM
16344 >
16345                 require client certificates. In the web environment the client's
16346                 data is sensitive (credit card numbers) and the server must prove
16347                 to be trustworthy. In a file server environment the server's data
16348                 will be sensitive and the clients must prove to be trustworthy.</P
16349 ><P
16350 >Default: <B
16351 CLASS="COMMAND"
16352 >ssl require clientcert = no</B
16353 ></P
16354 ></DD
16355 ><DT
16356 ><A
16357 NAME="SSLREQUIRESERVERCERT"
16358 ></A
16359 >ssl require servercert (G)</DT
16360 ><DD
16361 ><P
16362 >This variable is part of SSL-enabled Samba. This
16363                 is only available if the SSL libraries have been compiled on your
16364                 system and the configure option <B
16365 CLASS="COMMAND"
16366 >--with-ssl</B
16367 > was
16368                 given at configure time.</P
16369 ><P
16370 ><EM
16371 >Note</EM
16372 > that for export control reasons
16373                 this code is <EM
16374 >NOT</EM
16375 > enabled by default in any
16376                 current binary version of Samba.</P
16377 ><P
16378 >If this variable is set to <TT
16379 CLASS="CONSTANT"
16380 >yes</TT
16381 >, the
16382                 <A
16383 HREF="smbclient.1.html"
16384 TARGET="_top"
16385 ><B
16386 CLASS="COMMAND"
16387 >smbclient(1)</B
16388 >
16389                 </A
16390 > will request a certificate from the server. Same as
16391                 <A
16392 HREF="#SSLREQUIRECLIENTCERT"
16393 ><TT
16394 CLASS="PARAMETER"
16395 ><I
16396 >ssl require
16397                 clientcert</I
16398 ></TT
16399 ></A
16400 > for the server.</P
16401 ><P
16402 >Default: <B
16403 CLASS="COMMAND"
16404 >ssl require servercert = no</B
16405 >
16406                 </P
16407 ></DD
16408 ><DT
16409 ><A
16410 NAME="SSLSERVERCERT"
16411 ></A
16412 >ssl server cert (G)</DT
16413 ><DD
16414 ><P
16415 >This variable is part of SSL-enabled Samba. This
16416                 is only available if the SSL libraries have been compiled on your
16417                 system and the configure option <B
16418 CLASS="COMMAND"
16419 >--with-ssl</B
16420 > was
16421                 given at configure time.</P
16422 ><P
16423 ><EM
16424 >Note</EM
16425 > that for export control reasons
16426                 this code is <EM
16427 >NOT</EM
16428 > enabled by default in any
16429                 current binary version of Samba.</P
16430 ><P
16431 >This is the file containing the server's certificate.
16432                 The server <EM
16433 >must</EM
16434 > have a certificate. The
16435                 file may also contain the server's private key. See later for
16436                 how certificates and private keys are created.</P
16437 ><P
16438 >Default: <B
16439 CLASS="COMMAND"
16440 >ssl server cert = &#60;empty string&#62;
16441                 </B
16442 ></P
16443 ></DD
16444 ><DT
16445 ><A
16446 NAME="SSLSERVERKEY"
16447 ></A
16448 >ssl server key (G)</DT
16449 ><DD
16450 ><P
16451 >This variable is part of SSL-enabled Samba. This
16452                 is only available if the SSL libraries have been compiled on your
16453                 system and the configure option <B
16454 CLASS="COMMAND"
16455 >--with-ssl</B
16456 > was
16457                 given at configure time.</P
16458 ><P
16459 ><EM
16460 >Note</EM
16461 > that for export control reasons
16462                 this code is <EM
16463 >NOT</EM
16464 > enabled by default in any
16465                 current binary version of Samba.</P
16466 ><P
16467 >This file contains the private key of the server. If
16468                 this variable is not defined, the key is looked up in the
16469                 certificate file (it may be appended to the certificate).
16470                 The server <EM
16471 >must</EM
16472 > have a private key
16473                 and the certificate <EM
16474 >must</EM
16475 >
16476                 match this private key.</P
16477 ><P
16478 >Default: <B
16479 CLASS="COMMAND"
16480 >ssl server key = &#60;empty string&#62;
16481                 </B
16482 ></P
16483 ></DD
16484 ><DT
16485 ><A
16486 NAME="SSLVERSION"
16487 ></A
16488 >ssl version (G)</DT
16489 ><DD
16490 ><P
16491 >This variable is part of SSL-enabled Samba. This
16492                 is only available if the SSL libraries have been compiled on your
16493                 system and the configure option <B
16494 CLASS="COMMAND"
16495 >--with-ssl</B
16496 > was
16497                 given at configure time.</P
16498 ><P
16499 ><EM
16500 >Note</EM
16501 > that for export control reasons
16502                 this code is <EM
16503 >NOT</EM
16504 > enabled by default in any
16505                 current binary version of Samba.</P
16506 ><P
16507 >This enumeration variable defines the versions of the
16508                 SSL protocol that will be used. <TT
16509 CLASS="CONSTANT"
16510 >ssl2or3</TT
16511 > allows
16512                 dynamic negotiation of SSL v2 or v3, <TT
16513 CLASS="CONSTANT"
16514 >ssl2</TT
16515 > results
16516                 in SSL v2, <TT
16517 CLASS="CONSTANT"
16518 >ssl3</TT
16519 > results in SSL v3 and
16520                 <TT
16521 CLASS="CONSTANT"
16522 >tls1</TT
16523 > results in TLS v1. TLS (Transport Layer
16524                 Security) is the new standard for SSL.</P
16525 ><P
16526 >Default: <B
16527 CLASS="COMMAND"
16528 >ssl version = "ssl2or3"</B
16529 ></P
16530 ></DD
16531 ><DT
16532 ><A
16533 NAME="STATCACHE"
16534 ></A
16535 >stat cache (G)</DT
16536 ><DD
16537 ><P
16538 >This parameter determines if <A
16539 HREF="smbd.8.html"
16540 TARGET="_top"
16541 >smbd(8)</A
16542 > will use a cache in order to
16543                 speed up case insensitive name mappings. You should never need
16544                 to change this parameter.</P
16545 ><P
16546 >Default: <B
16547 CLASS="COMMAND"
16548 >stat cache = yes</B
16549 ></P
16550 ></DD
16551 ><DT
16552 ><A
16553 NAME="STATCACHESIZE"
16554 ></A
16555 >stat cache size (G)</DT
16556 ><DD
16557 ><P
16558 >This parameter determines the number of
16559                 entries in the <TT
16560 CLASS="PARAMETER"
16561 ><I
16562 >stat cache</I
16563 ></TT
16564 >.  You should
16565                 never need to change this parameter.</P
16566 ><P
16567 >Default: <B
16568 CLASS="COMMAND"
16569 >stat cache size = 50</B
16570 ></P
16571 ></DD
16572 ><DT
16573 ><A
16574 NAME="STATUS"
16575 ></A
16576 >status (G)</DT
16577 ><DD
16578 ><P
16579 >This enables or disables logging of connections
16580                 to a status file that <A
16581 HREF="smbstatus.1.html"
16582 TARGET="_top"
16583 >smbstatus(1)</A
16584 >
16585                 can read.</P
16586 ><P
16587 >With this disabled <B
16588 CLASS="COMMAND"
16589 >smbstatus</B
16590 > won't be able
16591                 to tell you what connections are active. You should never need to
16592                 change this parameter.</P
16593 ><P
16594 >Default: <B
16595 CLASS="COMMAND"
16596 >status = yes</B
16597 ></P
16598 ></DD
16599 ><DT
16600 ><A
16601 NAME="STRICTLOCKING"
16602 ></A
16603 >strict locking (S)</DT
16604 ><DD
16605 ><P
16606 >This is a boolean that controls the handling of
16607                 file locking in the server. When this is set to <TT
16608 CLASS="CONSTANT"
16609 >yes</TT
16610 >
16611                 the server will check every read and write access for file locks, and
16612                 deny access if locks exist. This can be slow on some systems.</P
16613 ><P
16614 >When strict locking is <TT
16615 CLASS="CONSTANT"
16616 >no</TT
16617 > the server does file
16618                 lock checks only when the client explicitly asks for them.</P
16619 ><P
16620 >Well behaved clients always ask for lock checks when it
16621                 is important, so in the vast majority of cases <B
16622 CLASS="COMMAND"
16623 >strict
16624                 locking = no</B
16625 > is preferable.</P
16626 ><P
16627 >Default: <B
16628 CLASS="COMMAND"
16629 >strict locking = no</B
16630 ></P
16631 ></DD
16632 ><DT
16633 ><A
16634 NAME="STRICTSYNC"
16635 ></A
16636 >strict sync (S)</DT
16637 ><DD
16638 ><P
16639 >Many Windows applications (including the Windows
16640                 98 explorer shell) seem to confuse flushing buffer contents to
16641                 disk with doing a sync to disk. Under UNIX, a sync call forces
16642                 the process to be suspended until the kernel has ensured that
16643                 all outstanding data in kernel disk buffers has been safely stored
16644                 onto stable storage. This is very slow and should only be done
16645                 rarely. Setting this parameter to <TT
16646 CLASS="CONSTANT"
16647 >no</TT
16648 > (the
16649                 default) means that smbd ignores the Windows applications requests for
16650                 a sync call. There is only a possibility of losing data if the
16651                 operating system itself that Samba is running on crashes, so there is
16652                 little danger in this default setting. In addition, this fixes many
16653                 performance problems that people have reported with the new Windows98
16654                 explorer shell file copies.</P
16655 ><P
16656 >See also the <A
16657 HREF="#SYNCALWAYS"
16658 ><TT
16659 CLASS="PARAMETER"
16660 ><I
16661 >sync
16662                 always&#62;</I
16663 ></TT
16664 ></A
16665 > parameter.</P
16666 ><P
16667 >Default: <B
16668 CLASS="COMMAND"
16669 >strict sync = no</B
16670 ></P
16671 ></DD
16672 ><DT
16673 ><A
16674 NAME="STRIPDOT"
16675 ></A
16676 >strip dot (G)</DT
16677 ><DD
16678 ><P
16679 >This is a boolean that controls whether to
16680                 strip trailing dots off UNIX filenames. This helps with some
16681                 CDROMs that have filenames ending in a single dot.</P
16682 ><P
16683 >Default: <B
16684 CLASS="COMMAND"
16685 >strip dot = no</B
16686 ></P
16687 ></DD
16688 ><DT
16689 ><A
16690 NAME="SYNCALWAYS"
16691 ></A
16692 >sync always (S)</DT
16693 ><DD
16694 ><P
16695 >This is a boolean parameter that controls
16696                 whether writes will always be written to stable storage before
16697                 the write call returns. If this is false then the server will be
16698                 guided by the client's request in each write call (clients can
16699                 set a bit indicating that a particular write should be synchronous).
16700                 If this is true then every write will be followed by a <B
16701 CLASS="COMMAND"
16702 >fsync()
16703                 </B
16704 > call to ensure the data is written to disk. Note that
16705                 the <TT
16706 CLASS="PARAMETER"
16707 ><I
16708 >strict sync</I
16709 ></TT
16710 > parameter must be set to
16711                 <TT
16712 CLASS="CONSTANT"
16713 >yes</TT
16714 > in order for this parameter to have
16715                 any affect.</P
16716 ><P
16717 >See also the <A
16718 HREF="#STRICTSYNC"
16719 ><TT
16720 CLASS="PARAMETER"
16721 ><I
16722 >strict
16723                 sync</I
16724 ></TT
16725 ></A
16726 > parameter.</P
16727 ><P
16728 >Default: <B
16729 CLASS="COMMAND"
16730 >sync always = no</B
16731 ></P
16732 ></DD
16733 ><DT
16734 ><A
16735 NAME="SYSLOG"
16736 ></A
16737 >syslog (G)</DT
16738 ><DD
16739 ><P
16740 >This parameter maps how Samba debug messages
16741                 are logged onto the system syslog logging levels. Samba debug
16742                 level zero maps onto syslog <TT
16743 CLASS="CONSTANT"
16744 >LOG_ERR</TT
16745 >, debug
16746                 level one maps onto <TT
16747 CLASS="CONSTANT"
16748 >LOG_WARNING</TT
16749 >, debug level
16750                 two maps onto <TT
16751 CLASS="CONSTANT"
16752 >LOG_NOTICE</TT
16753 >, debug level three
16754                 maps onto LOG_INFO. All higher levels are mapped to <TT
16755 CLASS="CONSTANT"
16756 >               LOG_DEBUG</TT
16757 >.</P
16758 ><P
16759 >This parameter sets the threshold for sending messages
16760                 to syslog.  Only messages with debug level less than this value
16761                 will be sent to syslog.</P
16762 ><P
16763 >Default: <B
16764 CLASS="COMMAND"
16765 >syslog = 1</B
16766 ></P
16767 ></DD
16768 ><DT
16769 ><A
16770 NAME="SYSLOGONLY"
16771 ></A
16772 >syslog only (G)</DT
16773 ><DD
16774 ><P
16775 >If this parameter is set then Samba debug
16776                 messages are logged into the system syslog only, and not to
16777                 the debug log files.</P
16778 ><P
16779 >Default: <B
16780 CLASS="COMMAND"
16781 >syslog only = no</B
16782 ></P
16783 ></DD
16784 ><DT
16785 ><A
16786 NAME="TEMPLATEHOMEDIR"
16787 ></A
16788 >template homedir (G)</DT
16789 ><DD
16790 ><P
16791 ><EM
16792 >NOTE:</EM
16793 > this parameter is
16794                 only available in Samba 3.0.</P
16795 ><P
16796 >When filling out the user information for a Windows NT
16797                 user, the <A
16798 HREF="winbindd.8.html"
16799 TARGET="_top"
16800 >winbindd(8)</A
16801 > daemon
16802                 uses this parameter to fill in the home directory for that user.
16803                 If the string <TT
16804 CLASS="PARAMETER"
16805 ><I
16806 >%D</I
16807 ></TT
16808 > is present it is substituted
16809                 with the user's Windows NT domain name.  If the string <TT
16810 CLASS="PARAMETER"
16811 ><I
16812 >%U
16813                 </I
16814 ></TT
16815 > is present it is substituted with the user's Windows
16816                 NT user name.</P
16817 ><P
16818 >Default: <B
16819 CLASS="COMMAND"
16820 >template homedir = /home/%D/%U</B
16821 ></P
16822 ></DD
16823 ><DT
16824 ><A
16825 NAME="TEMPLATESHELL"
16826 ></A
16827 >template shell (G)</DT
16828 ><DD
16829 ><P
16830 ><EM
16831 >NOTE:</EM
16832 > this parameter is
16833                 only available in Samba 3.0.</P
16834 ><P
16835 >When filling out the user information for a Windows NT
16836                 user, the <A
16837 HREF="winbindd.8.html"
16838 TARGET="_top"
16839 >winbindd(8)</A
16840 > daemon
16841                 uses this parameter to fill in the login shell for that user.</P
16842 ><P
16843 >Default: <B
16844 CLASS="COMMAND"
16845 >template shell = /bin/false</B
16846 ></P
16847 ></DD
16848 ><DT
16849 ><A
16850 NAME="TIMEOFFSET"
16851 ></A
16852 >time offset (G)</DT
16853 ><DD
16854 ><P
16855 >This parameter is a setting in minutes to add
16856                 to the normal GMT to local time conversion. This is useful if
16857                 you are serving a lot of PCs that have incorrect daylight
16858                 saving time handling.</P
16859 ><P
16860 >Default: <B
16861 CLASS="COMMAND"
16862 >time offset = 0</B
16863 ></P
16864 ><P
16865 >Example: <B
16866 CLASS="COMMAND"
16867 >time offset = 60</B
16868 ></P
16869 ></DD
16870 ><DT
16871 ><A
16872 NAME="TIMESERVER"
16873 ></A
16874 >time server (G)</DT
16875 ><DD
16876 ><P
16877 >This parameter determines if <A
16878 HREF="nmbd.8.html"
16879 TARGET="_top"
16880 >
16881                 nmbd(8)</A
16882 > advertises itself as a time server to Windows
16883                 clients.</P
16884 ><P
16885 >Default: <B
16886 CLASS="COMMAND"
16887 >time server = no</B
16888 ></P
16889 ></DD
16890 ><DT
16891 ><A
16892 NAME="TIMESTAMPLOGS"
16893 ></A
16894 >timestamp logs (G)</DT
16895 ><DD
16896 ><P
16897 >Synonym for <A
16898 HREF="#DEBUGTIMESTAMP"
16899 ><TT
16900 CLASS="PARAMETER"
16901 ><I
16902 >               debug timestamp</I
16903 ></TT
16904 ></A
16905 >.</P
16906 ></DD
16907 ><DT
16908 ><A
16909 NAME="TOTALPRINTJOBS"
16910 ></A
16911 >total print jobs (G)</DT
16912 ><DD
16913 ><P
16914 >This parameter accepts an integer value which defines
16915                 a limit on the maximum number of print jobs that will be accepted
16916                 system wide at any given time.  If a print job is submitted
16917                 by a client which will exceed this number, then smbd will return an
16918                 error indicating that no space is available on the server.  The
16919                 default value of 0 means that no such limit exists.  This parameter
16920                 can be used to prevent a server from exceeding its capacity and is
16921                 designed as a printing throttle.  See also
16922                 <A
16923 HREF="#MAXPRINTJOBS"
16924 ><TT
16925 CLASS="PARAMETER"
16926 ><I
16927 >max print jobs</I
16928 ></TT
16929 ></A
16930 >.
16931                 </P
16932 ><P
16933 >Default: <B
16934 CLASS="COMMAND"
16935 >total print jobs = 0</B
16936 ></P
16937 ><P
16938 >Example: <B
16939 CLASS="COMMAND"
16940 >total print jobs = 5000</B
16941 ></P
16942 ></DD
16943 ><DT
16944 ><A
16945 NAME="UNIXPASSWORDSYNC"
16946 ></A
16947 >unix password sync (G)</DT
16948 ><DD
16949 ><P
16950 >This boolean parameter controls whether Samba
16951                 attempts to synchronize the UNIX password with the SMB password
16952                 when the encrypted SMB password in the smbpasswd file is changed.
16953                 If this is set to true the program specified in the <TT
16954 CLASS="PARAMETER"
16955 ><I
16956 >passwd
16957                 program</I
16958 ></TT
16959 >parameter is called <EM
16960 >AS ROOT</EM
16961 > -
16962                 to allow the new UNIX password to be set without access to the
16963                 old UNIX password (as the SMB password has change code has no
16964                 access to the old password cleartext, only the new).</P
16965 ><P
16966 >See also <A
16967 HREF="#PASSWDPROGRAM"
16968 ><TT
16969 CLASS="PARAMETER"
16970 ><I
16971 >passwd
16972                 program</I
16973 ></TT
16974 ></A
16975 >, <A
16976 HREF="#PASSWDCHAT"
16977 ><TT
16978 CLASS="PARAMETER"
16979 ><I
16980 >               passwd chat</I
16981 ></TT
16982 ></A
16983 >.</P
16984 ><P
16985 >Default: <B
16986 CLASS="COMMAND"
16987 >unix password sync = no</B
16988 ></P
16989 ></DD
16990 ><DT
16991 ><A
16992 NAME="UPDATEENCRYPTED"
16993 ></A
16994 >update encrypted (G)</DT
16995 ><DD
16996 ><P
16997 >This boolean parameter allows a user logging
16998                 on with a plaintext password to have their encrypted (hashed)
16999                 password in the smbpasswd file to be updated automatically as
17000                 they log on. This option allows a site to migrate from plaintext
17001                 password authentication (users authenticate with plaintext
17002                 password over the wire, and are checked against a UNIX account
17003                 database) to encrypted password authentication (the SMB
17004                 challenge/response authentication mechanism) without forcing
17005                 all users to re-enter their passwords via smbpasswd at the time the
17006                 change is made. This is a convenience option to allow the change over
17007                 to encrypted passwords to be made over a longer period. Once all users
17008                 have encrypted representations of their passwords in the smbpasswd
17009                 file this parameter should be set to <TT
17010 CLASS="CONSTANT"
17011 >no</TT
17012 >.</P
17013 ><P
17014 >In order for this parameter to work correctly the <A
17015 HREF="#ENCRYPTPASSWORDS"
17016 ><TT
17017 CLASS="PARAMETER"
17018 ><I
17019 >encrypt passwords</I
17020 ></TT
17021 >
17022                 </A
17023 > parameter must be set to <TT
17024 CLASS="CONSTANT"
17025 >no</TT
17026 > when
17027                 this parameter is set to <TT
17028 CLASS="CONSTANT"
17029 >yes</TT
17030 >.</P
17031 ><P
17032 >Note that even when this parameter is set a user
17033                 authenticating to <B
17034 CLASS="COMMAND"
17035 >smbd</B
17036 > must still enter a valid
17037                 password in order to connect correctly, and to update their hashed
17038                 (smbpasswd) passwords.</P
17039 ><P
17040 >Default: <B
17041 CLASS="COMMAND"
17042 >update encrypted = no</B
17043 ></P
17044 ></DD
17045 ><DT
17046 ><A
17047 NAME="USERHOSTS"
17048 ></A
17049 >use rhosts (G)</DT
17050 ><DD
17051 ><P
17052 >If this global parameter is a true, it specifies
17053                 that the UNIX users <TT
17054 CLASS="FILENAME"
17055 >.rhosts</TT
17056 > file in their home directory
17057                 will be read to find the names of hosts and users who will be allowed
17058                 access without specifying a password.</P
17059 ><P
17060 ><EM
17061 >NOTE:</EM
17062 > The use of <TT
17063 CLASS="PARAMETER"
17064 ><I
17065 >use rhosts
17066                 </I
17067 ></TT
17068 > can be a major security hole. This is because you are
17069                 trusting the PC to supply the correct username. It is very easy to
17070                 get a PC to supply a false username. I recommend that the <TT
17071 CLASS="PARAMETER"
17072 ><I
17073 >               use rhosts</I
17074 ></TT
17075 > option be only used if you really know what
17076                 you are doing.</P
17077 ><P
17078 >Default: <B
17079 CLASS="COMMAND"
17080 >use rhosts = no</B
17081 ></P
17082 ></DD
17083 ><DT
17084 ><A
17085 NAME="USER"
17086 ></A
17087 >user (S)</DT
17088 ><DD
17089 ><P
17090 >Synonym for <A
17091 HREF="#USERNAME"
17092 ><TT
17093 CLASS="PARAMETER"
17094 ><I
17095 >               username</I
17096 ></TT
17097 ></A
17098 >.</P
17099 ></DD
17100 ><DT
17101 ><A
17102 NAME="USERS"
17103 ></A
17104 >users (S)</DT
17105 ><DD
17106 ><P
17107 >Synonym for <A
17108 HREF="#USERNAME"
17109 ><TT
17110 CLASS="PARAMETER"
17111 ><I
17112 >               username</I
17113 ></TT
17114 ></A
17115 >.</P
17116 ></DD
17117 ><DT
17118 ><A
17119 NAME="USERNAME"
17120 ></A
17121 >username (S)</DT
17122 ><DD
17123 ><P
17124 >Multiple users may be specified in a comma-delimited
17125                 list, in which case the supplied password will be tested against
17126                 each username in turn (left to right).</P
17127 ><P
17128 >The <TT
17129 CLASS="PARAMETER"
17130 ><I
17131 >username</I
17132 ></TT
17133 > line is needed only when
17134                 the PC is unable to supply its own username. This is the case
17135                 for the COREPLUS protocol or where your users have different WfWg
17136                 usernames to UNIX usernames. In both these cases you may also be
17137                 better using the \\server\share%user syntax instead.</P
17138 ><P
17139 >The <TT
17140 CLASS="PARAMETER"
17141 ><I
17142 >username</I
17143 ></TT
17144 > line is not a great
17145                 solution in many cases as it means Samba will try to validate
17146                 the supplied password against each of the usernames in the
17147                 <TT
17148 CLASS="PARAMETER"
17149 ><I
17150 >username</I
17151 ></TT
17152 > line in turn. This is slow and
17153                 a bad idea for lots of users in case of duplicate passwords.
17154                 You may get timeouts or security breaches using this parameter
17155                 unwisely.</P
17156 ><P
17157 >Samba relies on the underlying UNIX security. This
17158                 parameter does not restrict who can login, it just offers hints
17159                 to the Samba server as to what usernames might correspond to the
17160                 supplied password. Users can login as whoever they please and
17161                 they will be able to do no more damage than if they started a
17162                 telnet session. The daemon runs as the user that they log in as,
17163                 so they cannot do anything that user cannot do.</P
17164 ><P
17165 >To restrict a service to a particular set of users you
17166                 can use the <A
17167 HREF="#VALIDUSERS"
17168 ><TT
17169 CLASS="PARAMETER"
17170 ><I
17171 >valid users
17172                 </I
17173 ></TT
17174 ></A
17175 > parameter.</P
17176 ><P
17177 >If any of the usernames begin with a '@' then the name
17178                 will be looked up first in the yp netgroups list (if Samba
17179                 is compiled with netgroup support), followed by a lookup in
17180                 the UNIX groups database and will expand to a list of all users
17181                 in the group of that name.</P
17182 ><P
17183 >If any of the usernames begin with a '+' then the name
17184                 will be looked up only in the UNIX groups database and will
17185                 expand to a list of all users in the group of that name.</P
17186 ><P
17187 >If any of the usernames begin with a '&#38;'then the name
17188                 will be looked up only in the yp netgroups database (if Samba
17189                 is compiled with netgroup support) and will expand to a list
17190                 of all users in the netgroup group of that name.</P
17191 ><P
17192 >Note that searching though a groups database can take
17193                 quite some time, and some clients may time out during the
17194                 search.</P
17195 ><P
17196 >See the section <A
17197 HREF="#AEN234"
17198 >NOTE ABOUT
17199                 USERNAME/PASSWORD VALIDATION</A
17200 > for more information on how
17201                 this parameter determines access to the services.</P
17202 ><P
17203 >Default: <B
17204 CLASS="COMMAND"
17205 >The guest account if a guest service,
17206                 else &#60;empty string&#62;.</B
17207 ></P
17208 ><P
17209 >Examples:<B
17210 CLASS="COMMAND"
17211 >username = fred, mary, jack, jane,
17212                 @users, @pcgroup</B
17213 ></P
17214 ></DD
17215 ><DT
17216 ><A
17217 NAME="USERNAMELEVEL"
17218 ></A
17219 >username level (G)</DT
17220 ><DD
17221 ><P
17222 >This option helps Samba to try and 'guess' at
17223                 the real UNIX username, as many DOS clients send an all-uppercase
17224                 username. By default Samba tries all lowercase, followed by the
17225                 username with the first letter capitalized, and fails if the
17226                 username is not found on the UNIX machine.</P
17227 ><P
17228 >If this parameter is set to non-zero the behavior changes.
17229                 This parameter is a number that specifies the number of uppercase
17230                 combinations to try while trying to determine the UNIX user name. The
17231                 higher the number the more combinations will be tried, but the slower
17232                 the discovery of usernames will be. Use this parameter when you have
17233                 strange usernames on your UNIX machine, such as <TT
17234 CLASS="CONSTANT"
17235 >AstrangeUser
17236                 </TT
17237 >.</P
17238 ><P
17239 >Default: <B
17240 CLASS="COMMAND"
17241 >username level = 0</B
17242 ></P
17243 ><P
17244 >Example: <B
17245 CLASS="COMMAND"
17246 >username level = 5</B
17247 ></P
17248 ></DD
17249 ><DT
17250 ><A
17251 NAME="USERNAMEMAP"
17252 ></A
17253 >username map (G)</DT
17254 ><DD
17255 ><P
17256 >This option allows you to specify a file containing
17257                 a mapping of usernames from the clients to the server. This can be
17258                 used for several purposes. The most common is to map usernames
17259                 that users use on DOS or Windows machines to those that the UNIX
17260                 box uses. The other is to map multiple users to a single username
17261                 so that they can more easily share files.</P
17262 ><P
17263 >The map file is parsed line by line. Each line should
17264                 contain a single UNIX username on the left then a '=' followed
17265                 by a list of usernames on the right. The list of usernames on the
17266                 right may contain names of the form @group in which case they
17267                 will match any UNIX username in that group. The special client
17268                 name '*' is a wildcard and matches any name. Each line of the
17269                 map file may be up to 1023 characters long.</P
17270 ><P
17271 >The file is processed on each line by taking the
17272                 supplied username and comparing it with each username on the right
17273                 hand side of the '=' signs. If the supplied name matches any of
17274                 the names on the right hand side then it is replaced with the name
17275                 on the left. Processing then continues with the next line.</P
17276 ><P
17277 >If any line begins with a '#' or a ';' then it is
17278                 ignored</P
17279 ><P
17280 >If any line begins with an '!' then the processing
17281                 will stop after that line if a mapping was done by the line.
17282                 Otherwise mapping continues with every line being processed.
17283                 Using '!' is most useful when you have a wildcard mapping line
17284                 later in the file.</P
17285 ><P
17286 >For example to map from the name <TT
17287 CLASS="CONSTANT"
17288 >admin</TT
17289 >
17290                 or <TT
17291 CLASS="CONSTANT"
17292 >administrator</TT
17293 > to the UNIX name <TT
17294 CLASS="CONSTANT"
17295 >               root</TT
17296 > you would use:</P
17297 ><P
17298 ><B
17299 CLASS="COMMAND"
17300 >root = admin administrator</B
17301 ></P
17302 ><P
17303 >Or to map anyone in the UNIX group <TT
17304 CLASS="CONSTANT"
17305 >system</TT
17306 >
17307                 to the UNIX name <TT
17308 CLASS="CONSTANT"
17309 >sys</TT
17310 > you would use:</P
17311 ><P
17312 ><B
17313 CLASS="COMMAND"
17314 >sys = @system</B
17315 ></P
17316 ><P
17317 >You can have as many mappings as you like in a username
17318                 map file.</P
17319 ><P
17320 >If your system supports the NIS NETGROUP option then
17321                 the netgroup database is checked before the <TT
17322 CLASS="FILENAME"
17323 >/etc/group
17324                 </TT
17325 > database for matching groups.</P
17326 ><P
17327 >You can map Windows usernames that have spaces in them
17328                  by using double quotes around the name. For example:</P
17329 ><P
17330 ><B
17331 CLASS="COMMAND"
17332 >tridge = "Andrew Tridgell"</B
17333 ></P
17334 ><P
17335 >would map the windows username "Andrew Tridgell" to the
17336                 unix username "tridge".</P
17337 ><P
17338 >The following example would map mary and fred to the
17339                 unix user sys, and map the rest to guest. Note the use of the
17340                 '!' to tell Samba to stop processing if it gets a match on
17341                 that line.</P
17342 ><P
17343 ><TABLE
17344 BORDER="0"
17345 BGCOLOR="#E0E0E0"
17346 WIDTH="90%"
17347 ><TR
17348 ><TD
17349 ><PRE
17350 CLASS="PROGRAMLISTING"
17351 >               !sys = mary fred
17352                 guest = *
17353                 </PRE
17354 ></TD
17355 ></TR
17356 ></TABLE
17357 ></P
17358 ><P
17359 >Note that the remapping is applied to all occurrences
17360                 of usernames. Thus if you connect to \\server\fred and <TT
17361 CLASS="CONSTANT"
17362 >               fred</TT
17363 > is remapped to <TT
17364 CLASS="CONSTANT"
17365 >mary</TT
17366 > then you
17367                 will actually be connecting to \\server\mary and will need to
17368                 supply a password suitable for <TT
17369 CLASS="CONSTANT"
17370 >mary</TT
17371 > not
17372                 <TT
17373 CLASS="CONSTANT"
17374 >fred</TT
17375 >. The only exception to this is the
17376                 username passed to the <A
17377 HREF="#PASSWORDSERVER"
17378 ><TT
17379 CLASS="PARAMETER"
17380 ><I
17381 >               password server</I
17382 ></TT
17383 ></A
17384 > (if you have one). The password
17385                 server will receive whatever username the client supplies without
17386                 modification.</P
17387 ><P
17388 >Also note that no reverse mapping is done. The main effect
17389                 this has is with printing. Users who have been mapped may have
17390                 trouble deleting print jobs as PrintManager under WfWg will think
17391                 they don't own the print job.</P
17392 ><P
17393 >Default: <EM
17394 >no username map</EM
17395 ></P
17396 ><P
17397 >Example: <B
17398 CLASS="COMMAND"
17399 >username map = /usr/local/samba/lib/users.map
17400                 </B
17401 ></P
17402 ></DD
17403 ><DT
17404 ><A
17405 NAME="UTMP"
17406 ></A
17407 >utmp (S)</DT
17408 ><DD
17409 ><P
17410 >This boolean parameter is only available if
17411                 Samba has been configured and compiled  with the option <B
17412 CLASS="COMMAND"
17413 >               --with-utmp</B
17414 >. If set to True then Samba will attempt
17415                 to add utmp or utmpx records (depending on the UNIX system) whenever a
17416                 connection is made to a Samba server. Sites may use this to record the
17417                 user connecting to a Samba share.</P
17418 ><P
17419 >See also the <A
17420 HREF="#UTMPDIRECTORY"
17421 ><TT
17422 CLASS="PARAMETER"
17423 ><I
17424 >               utmp directory</I
17425 ></TT
17426 ></A
17427 > parameter.</P
17428 ><P
17429 >Default: <B
17430 CLASS="COMMAND"
17431 >utmp = no</B
17432 ></P
17433 ></DD
17434 ><DT
17435 ><A
17436 NAME="UTMPDIRECTORY"
17437 ></A
17438 >utmp directory(G)</DT
17439 ><DD
17440 ><P
17441 >This parameter is only available if Samba has
17442                 been configured and compiled with the option <B
17443 CLASS="COMMAND"
17444 >               --with-utmp</B
17445 >. It specifies a directory pathname that is
17446                 used to store the utmp or utmpx files (depending on the UNIX system) that
17447                 record user connections to a Samba server. See also the <A
17448 HREF="#UTMP"
17449 >               <TT
17450 CLASS="PARAMETER"
17451 ><I
17452 >utmp</I
17453 ></TT
17454 ></A
17455 > parameter. By default this is
17456                 not set, meaning the system will use whatever utmp file the
17457                 native system is set to use (usually
17458                 <TT
17459 CLASS="FILENAME"
17460 >/var/run/utmp</TT
17461 > on Linux).</P
17462 ><P
17463 >Default: <EM
17464 >no utmp directory</EM
17465 ></P
17466 ></DD
17467 ><DT
17468 ><A
17469 NAME="VALIDCHARS"
17470 ></A
17471 >valid chars (G)</DT
17472 ><DD
17473 ><P
17474 >The option allows you to specify additional
17475                 characters that should be considered valid by the server in
17476                 filenames. This is particularly useful for national character
17477                 sets, such as adding u-umlaut or a-ring.</P
17478 ><P
17479 >The option takes a list of characters in either integer
17480                 or character form with spaces between them. If you give two
17481                 characters with a colon between them then it will be taken as
17482                 an lowercase:uppercase pair.</P
17483 ><P
17484 >If you have an editor capable of entering the characters
17485                 into the config file then it is probably easiest to use this
17486                 method. Otherwise you can specify the characters in octal,
17487                 decimal or hexadecimal form using the usual C notation.</P
17488 ><P
17489 >For example to add the single character 'Z' to the charset
17490                 (which is a pointless thing to do as it's already there) you could
17491                 do one of the following</P
17492 ><P
17493 ><TABLE
17494 BORDER="0"
17495 BGCOLOR="#E0E0E0"
17496 WIDTH="90%"
17497 ><TR
17498 ><TD
17499 ><PRE
17500 CLASS="PROGRAMLISTING"
17501 >               valid chars = Z
17502                 valid chars = z:Z
17503                 valid chars = 0132:0172
17504                 </PRE
17505 ></TD
17506 ></TR
17507 ></TABLE
17508 ></P
17509 ><P
17510 >The last two examples above actually add two characters,
17511                 and alter the uppercase and lowercase mappings appropriately.</P
17512 ><P
17513 >Note that you <EM
17514 >MUST</EM
17515 > specify this parameter
17516                 after the <TT
17517 CLASS="PARAMETER"
17518 ><I
17519 >client code page</I
17520 ></TT
17521 > parameter if you
17522                 have both set. If <TT
17523 CLASS="PARAMETER"
17524 ><I
17525 >client code page</I
17526 ></TT
17527 > is set after
17528                 the <TT
17529 CLASS="PARAMETER"
17530 ><I
17531 >valid chars</I
17532 ></TT
17533 > parameter the <TT
17534 CLASS="PARAMETER"
17535 ><I
17536 >valid
17537                 chars</I
17538 ></TT
17539 > settings will be overwritten.</P
17540 ><P
17541 >See also the <A
17542 HREF="#CLIENTCODEPAGE"
17543 ><TT
17544 CLASS="PARAMETER"
17545 ><I
17546 >client
17547                 code page</I
17548 ></TT
17549 ></A
17550 > parameter.</P
17551 ><P
17552 >Default: <EM
17553 >Samba defaults to using a reasonable set
17554                 of valid characters for English systems</EM
17555 ></P
17556 ><P
17557 >Example: <B
17558 CLASS="COMMAND"
17559 >valid chars = 0345:0305 0366:0326 0344:0304
17560                 </B
17561 ></P
17562 ><P
17563 >The above example allows filenames to have the Swedish
17564                 characters in them.</P
17565 ><P
17566 ><EM
17567 >NOTE:</EM
17568 > It is actually quite difficult to
17569                 correctly produce a <TT
17570 CLASS="PARAMETER"
17571 ><I
17572 >valid chars</I
17573 ></TT
17574 > line for
17575                 a particular system. To automate the process <A
17576 HREF="mailto:tino@augsburg.net"
17577 TARGET="_top"
17578 >tino@augsburg.net</A
17579 > has written
17580                 a package called <B
17581 CLASS="COMMAND"
17582 >validchars</B
17583 > which will automatically
17584                 produce a complete <TT
17585 CLASS="PARAMETER"
17586 ><I
17587 >valid chars</I
17588 ></TT
17589 > line for
17590                 a given client system. Look in the <TT
17591 CLASS="FILENAME"
17592 >examples/validchars/
17593                 </TT
17594 > subdirectory of your Samba source code distribution
17595                 for this package.</P
17596 ></DD
17597 ><DT
17598 ><A
17599 NAME="VALIDUSERS"
17600 ></A
17601 >valid users (S)</DT
17602 ><DD
17603 ><P
17604 >This is a list of users that should be allowed
17605                 to login to this service. Names starting with '@', '+' and  '&#38;'
17606                 are interpreted using the same rules as described in the
17607                 <TT
17608 CLASS="PARAMETER"
17609 ><I
17610 >invalid users</I
17611 ></TT
17612 > parameter.</P
17613 ><P
17614 >If this is empty (the default) then any user can login.
17615                 If a username is in both this list and the <TT
17616 CLASS="PARAMETER"
17617 ><I
17618 >invalid
17619                 users</I
17620 ></TT
17621 > list then access is denied for that user.</P
17622 ><P
17623 >The current servicename is substituted for <TT
17624 CLASS="PARAMETER"
17625 ><I
17626 >%S
17627                 </I
17628 ></TT
17629 >. This is useful in the [homes] section.</P
17630 ><P
17631 >See also <A
17632 HREF="#INVALIDUSERS"
17633 ><TT
17634 CLASS="PARAMETER"
17635 ><I
17636 >invalid users
17637                 </I
17638 ></TT
17639 ></A
17640 ></P
17641 ><P
17642 >Default: <EM
17643 >No valid users list (anyone can login)
17644                 </EM
17645 ></P
17646 ><P
17647 >Example: <B
17648 CLASS="COMMAND"
17649 >valid users = greg, @pcusers</B
17650 ></P
17651 ></DD
17652 ><DT
17653 ><A
17654 NAME="VETOFILES"
17655 ></A
17656 >veto files(S)</DT
17657 ><DD
17658 ><P
17659 >This is a list of files and directories that
17660                 are neither visible nor accessible.  Each entry in the list must
17661                 be separated by a '/', which allows spaces to be included
17662                 in the entry. '*' and '?' can be used to specify multiple files
17663                 or directories as in DOS wildcards.</P
17664 ><P
17665 >Each entry must be a unix path, not a DOS path and
17666                 must <EM
17667 >not</EM
17668 > include the  unix directory
17669                 separator '/'.</P
17670 ><P
17671 >Note that the <TT
17672 CLASS="PARAMETER"
17673 ><I
17674 >case sensitive</I
17675 ></TT
17676 > option
17677                 is applicable in vetoing files.</P
17678 ><P
17679 >One feature of the veto files parameter that it is important
17680                 to be aware of, is that if a directory contains nothing but files
17681                 that match the veto files parameter (which means that Windows/DOS
17682                 clients cannot ever see them) is deleted, the veto files within
17683                 that directory <EM
17684 >are automatically deleted</EM
17685 > along
17686                 with it, if the user has UNIX permissions to do so.</P
17687 ><P
17688 >Setting this parameter will affect the performance
17689                 of Samba, as it will be forced to check all files and directories
17690                 for a match as they are scanned.</P
17691 ><P
17692 >See also <A
17693 HREF="#HIDEFILES"
17694 ><TT
17695 CLASS="PARAMETER"
17696 ><I
17697 >hide files
17698                 </I
17699 ></TT
17700 ></A
17701 > and <A
17702 HREF="#CASESENSITIVE"
17703 ><TT
17704 CLASS="PARAMETER"
17705 ><I
17706 >               case sensitive</I
17707 ></TT
17708 ></A
17709 >.</P
17710 ><P
17711 >Default: <EM
17712 >No files or directories are vetoed.
17713                 </EM
17714 ></P
17715 ><P
17716 >Examples:<TABLE
17717 BORDER="0"
17718 BGCOLOR="#E0E0E0"
17719 WIDTH="90%"
17720 ><TR
17721 ><TD
17722 ><PRE
17723 CLASS="PROGRAMLISTING"
17724 >          ; Veto any files containing the word Security,
17725         ; any ending in .tmp, and any directory containing the
17726         ; word root.
17727                 veto files = /*Security*/*.tmp/*root*/
17728
17729                 ; Veto the Apple specific files that a NetAtalk server
17730         ; creates.
17731                 veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
17732                 </PRE
17733 ></TD
17734 ></TR
17735 ></TABLE
17736 ></P
17737 ></DD
17738 ><DT
17739 ><A
17740 NAME="VETOOPLOCKFILES"
17741 ></A
17742 >veto oplock files (S)</DT
17743 ><DD
17744 ><P
17745 >This parameter is only valid when the <A
17746 HREF="#OPLOCKS"
17747 ><TT
17748 CLASS="PARAMETER"
17749 ><I
17750 >oplocks</I
17751 ></TT
17752 ></A
17753 >
17754                 parameter is turned on for a share. It allows the Samba administrator
17755                 to selectively turn off the granting of oplocks on selected files that
17756                 match a wildcarded list, similar to the wildcarded list used in the
17757                 <A
17758 HREF="#VETOFILES"
17759 ><TT
17760 CLASS="PARAMETER"
17761 ><I
17762 >veto files</I
17763 ></TT
17764 ></A
17765 >
17766                 parameter.</P
17767 ><P
17768 >Default: <EM
17769 >No files are vetoed for oplock
17770                 grants</EM
17771 ></P
17772 ><P
17773 >You might want to do this on files that you know will
17774                 be heavily contended for by clients. A good example of this
17775                 is in the NetBench SMB benchmark program, which causes heavy
17776                 client contention for files ending in <TT
17777 CLASS="FILENAME"
17778 >.SEM</TT
17779 >.
17780                 To cause Samba not to grant oplocks on these files you would use
17781                 the line (either in the [global] section or in the section for
17782                 the particular NetBench share :</P
17783 ><P
17784 >Example: <B
17785 CLASS="COMMAND"
17786 >veto oplock files = /*;.SEM/
17787                 </B
17788 ></P
17789 ></DD
17790 ><DT
17791 ><A
17792 NAME="VFSOBJECT"
17793 ></A
17794 >vfs object (S)</DT
17795 ><DD
17796 ><P
17797 >This parameter specifies a shared object file that
17798                 is used for Samba VFS I/O operations.  By default, normal
17799                 disk I/O operations are used but these can be overloaded
17800                 with a VFS object.  The Samba VFS layer is new to Samba 2.2 and
17801                 must be enabled at compile time with --with-vfs.</P
17802 ><P
17803 >Default : <EM
17804 >no value</EM
17805 ></P
17806 ></DD
17807 ><DT
17808 ><A
17809 NAME="VFSOPTIONS"
17810 ></A
17811 >vfs options (S)</DT
17812 ><DD
17813 ><P
17814 >This parameter allows parameters to be passed
17815                 to the vfs layer at initialisation time.  The Samba VFS layer
17816                 is new to Samba 2.2 and must be enabled at compile time
17817                 with --with-vfs.  See also <A
17818 HREF="#VFSOBJECT"
17819 ><TT
17820 CLASS="PARAMETER"
17821 ><I
17822 >               vfs object</I
17823 ></TT
17824 ></A
17825 >.</P
17826 ><P
17827 >Default : <EM
17828 >no value</EM
17829 ></P
17830 ></DD
17831 ><DT
17832 ><A
17833 NAME="VOLUME"
17834 ></A
17835 >volume (S)</DT
17836 ><DD
17837 ><P
17838 > This allows you to override the volume label
17839                 returned for a share. Useful for CDROMs with installation programs
17840                 that insist on a particular volume label.</P
17841 ><P
17842 >Default: <EM
17843 >the name of the share</EM
17844 ></P
17845 ></DD
17846 ><DT
17847 ><A
17848 NAME="WIDELINKS"
17849 ></A
17850 >wide links (S)</DT
17851 ><DD
17852 ><P
17853 >This parameter controls whether or not links
17854                 in the UNIX file system may be followed by the server. Links
17855                 that point to areas within the directory tree exported by the
17856                 server are always allowed; this parameter controls access only
17857                 to areas that are outside the directory tree being exported.</P
17858 ><P
17859 >Note that setting this parameter can have a negative
17860                 effect on your server performance due to the extra system calls
17861                 that Samba has to  do in order to perform the link checks.</P
17862 ><P
17863 >Default: <B
17864 CLASS="COMMAND"
17865 >wide links = yes</B
17866 ></P
17867 ></DD
17868 ><DT
17869 ><A
17870 NAME="WINBINDCACHETIME"
17871 ></A
17872 >winbind cache time</DT
17873 ><DD
17874 ><P
17875 ><EM
17876 >NOTE:</EM
17877 > this parameter is only
17878                 available in Samba 3.0.</P
17879 ><P
17880 >This parameter specifies the number of seconds the
17881                 <A
17882 HREF="winbindd.8.html"
17883 TARGET="_top"
17884 >winbindd(8)</A
17885 > daemon will cache
17886                 user and group information before querying a Windows NT server
17887                 again.</P
17888 ><P
17889 >Default: <B
17890 CLASS="COMMAND"
17891 >winbind cache type = 15</B
17892 ></P
17893 ></DD
17894 ><DT
17895 ><A
17896 NAME="WINBINDGID"
17897 ></A
17898 >winbind gid</DT
17899 ><DD
17900 ><P
17901 ><EM
17902 >NOTE:</EM
17903 > this parameter is only
17904                 available in Samba 3.0.</P
17905 ><P
17906 >The winbind gid parameter specifies the range of group
17907                 ids that are allocated by the <A
17908 HREF="winbindd.8.html"
17909 TARGET="_top"
17910 >               winbindd(8)</A
17911 > daemon.  This range of group ids should have no
17912                 existing local or nis groups within it as strange conflicts can
17913                 occur otherwise.</P
17914 ><P
17915 >Default: <B
17916 CLASS="COMMAND"
17917 >winbind gid = &#60;empty string&#62;
17918                 </B
17919 ></P
17920 ><P
17921 >Example: <B
17922 CLASS="COMMAND"
17923 >winbind gid = 10000-20000</B
17924 ></P
17925 ></DD
17926 ><DT
17927 ><A
17928 NAME="WINBINDSEPARATOR"
17929 ></A
17930 >winbind separator</DT
17931 ><DD
17932 ><P
17933 ><EM
17934 >NOTE:</EM
17935 > this parameter is only
17936                 available in Samba 3.0.</P
17937 ><P
17938 >This parameter allows an admin to define the character
17939                 used when listing a username of the form of <TT
17940 CLASS="REPLACEABLE"
17941 ><I
17942 >DOMAIN
17943                 </I
17944 ></TT
17945 >\<TT
17946 CLASS="REPLACEABLE"
17947 ><I
17948 >user</I
17949 ></TT
17950 >.  This parameter
17951                 is only applicable when using the <TT
17952 CLASS="FILENAME"
17953 >pam_winbind.so</TT
17954 >
17955                 and <TT
17956 CLASS="FILENAME"
17957 >nss_winbind.so</TT
17958 > modules for UNIX services.
17959                 </P
17960 ><P
17961 >Example: <B
17962 CLASS="COMMAND"
17963 >winbind separator = \</B
17964 ></P
17965 ><P
17966 >Example: <B
17967 CLASS="COMMAND"
17968 >winbind separator = +</B
17969 ></P
17970 ></DD
17971 ><DT
17972 ><A
17973 NAME="WINBINDUID"
17974 ></A
17975 >winbind uid</DT
17976 ><DD
17977 ><P
17978 ><EM
17979 >NOTE:</EM
17980 > this parameter is only
17981                 available in Samba 3.0.</P
17982 ><P
17983 >The winbind gid parameter specifies the range of group
17984                 ids that are allocated by the <A
17985 HREF="winbindd.8.html"
17986 TARGET="_top"
17987 >               winbindd(8)</A
17988 > daemon.  This range of ids should have no
17989                 existing local or nis users within it as strange conflicts can
17990                 occur otherwise.</P
17991 ><P
17992 >Default: <B
17993 CLASS="COMMAND"
17994 >winbind uid = &#60;empty string&#62;
17995                 </B
17996 ></P
17997 ><P
17998 >Example: <B
17999 CLASS="COMMAND"
18000 >winbind uid = 10000-20000</B
18001 ></P
18002 ></DD
18003 ><DT
18004 ><A
18005 NAME="WINSHOOK"
18006 ></A
18007 >wins hook (G)</DT
18008 ><DD
18009 ><P
18010 >When Samba is running as a WINS server this
18011                 allows you to call an external program for all changes to the
18012                 WINS database. The primary use for this option is to allow the
18013                 dynamic update of external name resolution databases such as
18014                 dynamic DNS.</P
18015 ><P
18016 >The wins hook parameter specifies the name of a script
18017                 or executable that will be called as follows:</P
18018 ><P
18019 ><B
18020 CLASS="COMMAND"
18021 >wins_hook operation name nametype ttl IP_list
18022                 </B
18023 ></P
18024 ><P
18025 ></P
18026 ><UL
18027 ><LI
18028 ><P
18029 >The first argument is the operation and is one
18030                         of "add", "delete", or "refresh". In most cases the operation can
18031                         be ignored as the rest of the parameters provide sufficient
18032                         information. Note that "refresh" may sometimes be called when the
18033                         name has not previously been added, in that case it should be treated
18034                         as an add.</P
18035 ></LI
18036 ><LI
18037 ><P
18038 >The second argument is the netbios name. If the
18039                         name is not a legal name then the wins hook is not called.
18040                         Legal names contain only  letters, digits, hyphens, underscores
18041                         and periods.</P
18042 ></LI
18043 ><LI
18044 ><P
18045 >The third argument is the netbios name
18046                         type as a 2 digit hexadecimal number. </P
18047 ></LI
18048 ><LI
18049 ><P
18050 >The fourth argument is the TTL (time to live)
18051                         for the name in seconds.</P
18052 ></LI
18053 ><LI
18054 ><P
18055 >The fifth and subsequent arguments are the IP
18056                         addresses currently registered for that name. If this list is
18057                         empty then the name should be deleted.</P
18058 ></LI
18059 ></UL
18060 ><P
18061 >An example script that calls the BIND dynamic DNS update
18062                 program <B
18063 CLASS="COMMAND"
18064 >nsupdate</B
18065 > is provided in the examples
18066                 directory of the Samba source code. </P
18067 ></DD
18068 ><DT
18069 ><A
18070 NAME="WINSPROXY"
18071 ></A
18072 >wins proxy (G)</DT
18073 ><DD
18074 ><P
18075 >This is a boolean that controls if <A
18076 HREF="nmbd.8.html"
18077 TARGET="_top"
18078 >nmbd(8)</A
18079 > will respond to broadcast name
18080                 queries on behalf of  other hosts. You may need to set this
18081                 to <TT
18082 CLASS="CONSTANT"
18083 >yes</TT
18084 > for some older clients.</P
18085 ><P
18086 >Default: <B
18087 CLASS="COMMAND"
18088 >wins proxy = no</B
18089 ></P
18090 ></DD
18091 ><DT
18092 ><A
18093 NAME="WINSSERVER"
18094 ></A
18095 >wins server (G)</DT
18096 ><DD
18097 ><P
18098 >This specifies the IP address (or DNS name: IP
18099                 address for preference) of the WINS server that <A
18100 HREF="nmbd.8.html"
18101 TARGET="_top"
18102 >               nmbd(8)</A
18103 > should register with. If you have a WINS server on
18104                 your network then you should set this to the WINS server's IP.</P
18105 ><P
18106 >You should point this at your WINS server if you have a
18107                 multi-subnetted network.</P
18108 ><P
18109 ><EM
18110 >NOTE</EM
18111 >. You need to set up Samba to point
18112                 to a WINS server if you have multiple subnets and wish cross-subnet
18113                 browsing to work correctly.</P
18114 ><P
18115 >See the documentation file <TT
18116 CLASS="FILENAME"
18117 >BROWSING.txt</TT
18118 >
18119                 in the docs/ directory of your Samba source distribution.</P
18120 ><P
18121 >Default: <EM
18122 >not enabled</EM
18123 ></P
18124 ><P
18125 >Example: <B
18126 CLASS="COMMAND"
18127 >wins server = 192.9.200.1</B
18128 ></P
18129 ></DD
18130 ><DT
18131 ><A
18132 NAME="WINSSUPPORT"
18133 ></A
18134 >wins support (G)</DT
18135 ><DD
18136 ><P
18137 >This boolean controls if the <A
18138 HREF="nmbd.8.html"
18139 TARGET="_top"
18140 >
18141                 nmbd(8)</A
18142 > process in Samba will act as a WINS server. You should
18143                 not set this to true unless you have a multi-subnetted network and
18144                 you wish a particular <B
18145 CLASS="COMMAND"
18146 >nmbd</B
18147 > to be your WINS server.
18148                 Note that you should <EM
18149 >NEVER</EM
18150 > set this to true
18151                 on more than one machine in your network.</P
18152 ><P
18153 >Default: <B
18154 CLASS="COMMAND"
18155 >wins support = no</B
18156 ></P
18157 ></DD
18158 ><DT
18159 ><A
18160 NAME="WORKGROUP"
18161 ></A
18162 >workgroup (G)</DT
18163 ><DD
18164 ><P
18165 >This controls what workgroup your server will
18166                 appear to be in when queried by clients. Note that this parameter
18167                 also controls the Domain name used with the <A
18168 HREF="#SECURITYEQUALSDOMAIN"
18169 ><B
18170 CLASS="COMMAND"
18171 >security=domain</B
18172 ></A
18173 >
18174                 setting.</P
18175 ><P
18176 >Default: <EM
18177 >set at compile time to WORKGROUP</EM
18178 ></P
18179 ><P
18180 >Example: <B
18181 CLASS="COMMAND"
18182 >workgroup = MYGROUP</B
18183 ></P
18184 ></DD
18185 ><DT
18186 ><A
18187 NAME="WRITABLE"
18188 ></A
18189 >writable (S)</DT
18190 ><DD
18191 ><P
18192 >Synonym for <A
18193 HREF="#WRITEABLE"
18194 ><TT
18195 CLASS="PARAMETER"
18196 ><I
18197 >               writeable</I
18198 ></TT
18199 ></A
18200 > for people who can't spell :-).</P
18201 ></DD
18202 ><DT
18203 ><A
18204 NAME="WRITECACHESIZE"
18205 ></A
18206 >write cache size (S)</DT
18207 ><DD
18208 ><P
18209 >If this integer parameter is set to non-zero value,
18210                 Samba will create an in-memory cache for each oplocked file
18211                 (it does <EM
18212 >not</EM
18213 > do this for
18214                 non-oplocked files). All writes that the client does not request
18215                 to be flushed directly to disk will be stored in this cache if possible.
18216                 The cache is flushed onto disk when a write comes in whose offset
18217                 would not fit into the cache or when the file is closed by the client.
18218                 Reads for the file are also served from this cache if the data is stored
18219                 within it.</P
18220 ><P
18221 >This cache allows Samba to batch client writes into a more
18222                 efficient write size for RAID disks (ie. writes may be tuned to
18223                 be the RAID stripe size) and can improve performance on systems
18224                 where the disk subsystem is a bottleneck but there is free
18225                 memory for userspace programs.</P
18226 ><P
18227 >The integer parameter specifies the size of this cache
18228                 (per oplocked file) in bytes.</P
18229 ><P
18230 >Default: <B
18231 CLASS="COMMAND"
18232 >write cache size = 0</B
18233 ></P
18234 ><P
18235 >Example: <B
18236 CLASS="COMMAND"
18237 >write cache size = 262144</B
18238 ></P
18239 ><P
18240 >for a 256k cache size per file.</P
18241 ></DD
18242 ><DT
18243 ><A
18244 NAME="WRITELIST"
18245 ></A
18246 >write list (S)</DT
18247 ><DD
18248 ><P
18249 >This is a list of users that are given read-write
18250                 access to a service. If the connecting user is in this list then
18251                 they will be given write access, no matter what the <A
18252 HREF="#WRITEABLE"
18253 ><TT
18254 CLASS="PARAMETER"
18255 ><I
18256 >writeable</I
18257 ></TT
18258 ></A
18259 >
18260                 option is set to. The list can include group names using the
18261                 @group syntax.</P
18262 ><P
18263 >Note that if a user is in both the read list and the
18264                 write list then they will be given write access.</P
18265 ><P
18266 >See also the <A
18267 HREF="#READLIST"
18268 ><TT
18269 CLASS="PARAMETER"
18270 ><I
18271 >read list
18272                 </I
18273 ></TT
18274 ></A
18275 > option.</P
18276 ><P
18277 >Default: <B
18278 CLASS="COMMAND"
18279 >write list = &#60;empty string&#62;
18280                 </B
18281 ></P
18282 ><P
18283 >Example: <B
18284 CLASS="COMMAND"
18285 >write list = admin, root, @staff
18286                 </B
18287 ></P
18288 ></DD
18289 ><DT
18290 ><A
18291 NAME="WRITEOK"
18292 ></A
18293 >write ok (S)</DT
18294 ><DD
18295 ><P
18296 >Synonym for <A
18297 HREF="#WRITEABLE"
18298 ><TT
18299 CLASS="PARAMETER"
18300 ><I
18301 >               writeable</I
18302 ></TT
18303 ></A
18304 >.</P
18305 ></DD
18306 ><DT
18307 ><A
18308 NAME="WRITERAW"
18309 ></A
18310 >write raw (G)</DT
18311 ><DD
18312 ><P
18313 >This parameter controls whether or not the server
18314                 will support raw writes SMB's when transferring data from clients.
18315                 You should never need to change this parameter.</P
18316 ><P
18317 >Default: <B
18318 CLASS="COMMAND"
18319 >write raw = yes</B
18320 ></P
18321 ></DD
18322 ><DT
18323 ><A
18324 NAME="WRITEABLE"
18325 ></A
18326 >writeable (S)</DT
18327 ><DD
18328 ><P
18329 >An inverted synonym is <A
18330 HREF="#READONLY"
18331 >               <TT
18332 CLASS="PARAMETER"
18333 ><I
18334 >read only</I
18335 ></TT
18336 ></A
18337 >.</P
18338 ><P
18339 >If this parameter is <TT
18340 CLASS="CONSTANT"
18341 >no</TT
18342 >, then users
18343                 of a service may not create or modify files in the service's
18344                 directory.</P
18345 ><P
18346 >Note that a printable service (<B
18347 CLASS="COMMAND"
18348 >printable = yes</B
18349 >)
18350                 will <EM
18351 >ALWAYS</EM
18352 > allow writing to the directory
18353                 (user privileges permitting), but only via spooling operations.</P
18354 ><P
18355 >Default: <B
18356 CLASS="COMMAND"
18357 >writeable = no</B
18358 ></P
18359 ></DD
18360 ></DL
18361 ></DIV
18362 ></DIV
18363 ><DIV
18364 CLASS="REFSECT1"
18365 ><A
18366 NAME="AEN5798"
18367 ></A
18368 ><H2
18369 >WARNINGS</H2
18370 ><P
18371 >Although the configuration file permits service names
18372         to contain spaces, your client software may not. Spaces will
18373         be ignored in comparisons anyway, so it shouldn't be a
18374         problem - but be aware of the possibility.</P
18375 ><P
18376 >On a similar note, many clients - especially DOS clients -
18377         limit service names to eight characters. <A
18378 HREF="smbd.8.html"
18379 TARGET="_top"
18380 >smbd(8)
18381         </A
18382 > has no such limitation, but attempts to connect from such
18383         clients will fail if they truncate the service names.  For this reason
18384         you should probably keep your service names down to eight characters
18385         in length.</P
18386 ><P
18387 >Use of the [homes] and [printers] special sections make life
18388         for an administrator easy, but the various combinations of default
18389         attributes can be tricky. Take extreme care when designing these
18390         sections. In particular, ensure that the permissions on spool
18391         directories are correct.</P
18392 ></DIV
18393 ><DIV
18394 CLASS="REFSECT1"
18395 ><A
18396 NAME="AEN5804"
18397 ></A
18398 ><H2
18399 >VERSION</H2
18400 ><P
18401 >This man page is correct for version 2.2 of
18402         the Samba suite.</P
18403 ></DIV
18404 ><DIV
18405 CLASS="REFSECT1"
18406 ><A
18407 NAME="AEN5807"
18408 ></A
18409 ><H2
18410 >SEE ALSO</H2
18411 ><P
18412 ><A
18413 HREF="samba.7.html"
18414 TARGET="_top"
18415 >samba(7)</A
18416 >,
18417         <A
18418 HREF="smbpasswd.8.html"
18419 TARGET="_top"
18420 ><B
18421 CLASS="COMMAND"
18422 >smbpasswd(8)</B
18423 ></A
18424 >,
18425         <A
18426 HREF="swat.8.html"
18427 TARGET="_top"
18428 ><B
18429 CLASS="COMMAND"
18430 >swat(8)</B
18431 ></A
18432 >,
18433         <A
18434 HREF="smbd.8.html"
18435 TARGET="_top"
18436 ><B
18437 CLASS="COMMAND"
18438 >smbd(8)</B
18439 ></A
18440 >,
18441         <A
18442 HREF="nmbd.8.html"
18443 TARGET="_top"
18444 ><B
18445 CLASS="COMMAND"
18446 >nmbd(8)</B
18447 ></A
18448 >,
18449         <A
18450 HREF="smbclient.1.html"
18451 TARGET="_top"
18452 ><B
18453 CLASS="COMMAND"
18454 >smbclient(1)</B
18455 ></A
18456 >,
18457         <A
18458 HREF="nmblookup.1.html"
18459 TARGET="_top"
18460 ><B
18461 CLASS="COMMAND"
18462 >nmblookup(1)</B
18463 ></A
18464 >,
18465         <A
18466 HREF="testparm.1.html"
18467 TARGET="_top"
18468 ><B
18469 CLASS="COMMAND"
18470 >testparm(1)</B
18471 ></A
18472 >,
18473         <A
18474 HREF="testprns.1.html"
18475 TARGET="_top"
18476 ><B
18477 CLASS="COMMAND"
18478 >testprns(1)</B
18479 ></A
18480 >
18481         </P
18482 ></DIV
18483 ><DIV
18484 CLASS="REFSECT1"
18485 ><A
18486 NAME="AEN5827"
18487 ></A
18488 ><H2
18489 >AUTHOR</H2
18490 ><P
18491 >The original Samba software and related utilities
18492         were created by Andrew Tridgell. Samba is now developed
18493         by the Samba Team as an Open Source project similar
18494         to the way the Linux kernel is developed.</P
18495 ><P
18496 >The original Samba man pages were written by Karl Auer.
18497         The man page sources were converted to YODL format (another
18498         excellent piece of Open Source software, available at
18499         <A
18500 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
18501 TARGET="_top"
18502 >       ftp://ftp.icce.rug.nl/pub/unix/</A
18503 >) and updated for the Samba 2.0
18504         release by Jeremy Allison.  The conversion to DocBook for
18505         Samba 2.2 was done by Gerald Carter</P
18506 ></DIV
18507 ></BODY
18508 ></HTML
18509 >