docs/htmldocs/smbd.8.html

   1 <HTML
   2 ><HEAD
   3 ><TITLE
   4 >smbd</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="SMBD"
  18 >smbd</A
  19 ></H1
  20 ><DIV
  21 CLASS="REFNAMEDIV"
  22 ><A
  23 NAME="AEN5"
  24 ></A
  25 ><H2
  26 >Name</H2
  27 >smbd&nbsp;--&nbsp;server to provide SMB/CIFS services to clients</DIV
  28 ><DIV
  29 CLASS="REFSYNOPSISDIV"
  30 ><A
  31 NAME="AEN8"
  32 ></A
  33 ><H2
  34 >Synopsis</H2
  35 ><P
  36 ><B
  37 CLASS="COMMAND"
  38 >smbd</B
  39 >  [-D] [-a] [-o] [-P] [-h] [-V] [-d &#60;debug level&#62;] [-l &#60;log directory&#62;] [-p &#60;port number&#62;] [-O &#60;socket option&#62;] [-s &#60;configuration file&#62;]</P
  40 ></DIV
  41 ><DIV
  42 CLASS="REFSECT1"
  43 ><A
  44 NAME="AEN22"
  45 ></A
  46 ><H2
  47 >DESCRIPTION</H2
  48 ><P
  49 >This program is part of the Samba suite.</P
  50 ><P
  51 ><B
  52 CLASS="COMMAND"
  53 >smbd</B
  54 > is the server daemon that
  55         provides filesharing and printing services to Windows clients.
  56         The server provides filespace and printer services to
  57         clients using the SMB (or CIFS) protocol. This is compatible
  58         with the LanManager protocol, and can service LanManager
  59         clients.  These include MSCLIENT 3.0 for DOS, Windows for
  60         Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
  61         OS/2, DAVE for Macintosh, and smbfs for Linux.</P
  62 ><P
  63 >An extensive description of the services that the
  64         server can provide is given in the man page for the
  65         configuration file controlling the attributes of those
  66         services (see <A
  67 HREF="smb.conf.5.html"
  68 TARGET="_top"
  69 ><TT
  70 CLASS="FILENAME"
  71 >smb.conf(5)
  72         </TT
  73 ></A
  74 >.  This man page will not describe the
  75         services, but will concentrate on the administrative aspects
  76         of running the server.</P
  77 ><P
  78 >Please note that there are significant security
  79         implications to running this server, and the <A
  80 HREF="smb.conf.5.html"
  81 TARGET="_top"
  82 ><TT
  83 CLASS="FILENAME"
  84 >smb.conf(5)</TT
  85 ></A
  86 >
  87         manpage should be regarded as mandatory reading before
  88         proceeding with installation.</P
  89 ><P
  90 >A session is created whenever a client requests one.
  91         Each client gets a copy of the server for each session. This
  92         copy then services all connections made by the client during
  93         that session. When all connections from its client are closed,
  94         the copy of the server for that client terminates.</P
  95 ><P
  96 >The configuration file, and any files that it includes,
  97         are automatically reloaded every minute, if they change.  You
  98         can force a reload by sending a SIGHUP to the server.  Reloading
  99         the configuration file will not affect connections to any service
 100         that is already established.  Either the user will have to
 101         disconnect from the service, or <B
 102 CLASS="COMMAND"
 103 >smbd</B
 104 > killed and restarted.</P
 105 ></DIV
 106 ><DIV
 107 CLASS="REFSECT1"
 108 ><A
 109 NAME="AEN36"
 110 ></A
 111 ><H2
 112 >OPTIONS</H2
 113 ><P
 114 ></P
 115 ><DIV
 116 CLASS="VARIABLELIST"
 117 ><DL
 118 ><DT
 119 >-D</DT
 120 ><DD
 121 ><P
 122 >If specified, this parameter causes
 123                 the server to operate as a daemon. That is, it detaches
 124                 itself and runs in the background, fielding requests
 125                 on the appropriate port. Operating the server as a
 126                 daemon is the recommended way of running <B
 127 CLASS="COMMAND"
 128 >smbd</B
 129 > for
 130                 servers that provide more than casual use file and
 131                 print services.  This switch is assumed if <B
 132 CLASS="COMMAND"
 133 >smbd
 134                 </B
 135 > is executed on the command line of a shell.
 136                 </P
 137 ></DD
 138 ><DT
 139 >-a</DT
 140 ><DD
 141 ><P
 142 >If this parameter is specified, each new
 143                 connection will append log messages to the log file.
 144                 This is the default.</P
 145 ></DD
 146 ><DT
 147 >-o</DT
 148 ><DD
 149 ><P
 150 >If this parameter is specified, the
 151                 log files will be overwritten when opened.  By default,
 152                 <B
 153 CLASS="COMMAND"
 154 >smbd</B
 155 > will append entries to the log
 156                 files.</P
 157 ></DD
 158 ><DT
 159 >-P</DT
 160 ><DD
 161 ><P
 162 >Passive option. Causes <B
 163 CLASS="COMMAND"
 164 >smbd</B
 165 > not to
 166                 send any network traffic out. Used for debugging by
 167                 the developers only.</P
 168 ></DD
 169 ><DT
 170 >-h</DT
 171 ><DD
 172 ><P
 173 >Prints the help information (usage)
 174                 for <B
 175 CLASS="COMMAND"
 176 >smbd</B
 177 >.</P
 178 ></DD
 179 ><DT
 180 >-v</DT
 181 ><DD
 182 ><P
 183 >Prints the version number for
 184                 <B
 185 CLASS="COMMAND"
 186 >smbd</B
 187 >.</P
 188 ></DD
 189 ><DT
 190 >-d &#60;debug level&#62;</DT
 191 ><DD
 192 ><P
 193 ><TT
 194 CLASS="REPLACEABLE"
 195 ><I
 196 >debuglevel</I
 197 ></TT
 198 > is an integer
 199                 from 0 to 10.  The default value if this parameter is
 200                 not specified is zero.</P
 201 ><P
 202 >The higher this value, the more detail will be
 203                 logged to the log files about the activities of the
 204                 server. At level 0, only critical errors and serious
 205                 warnings will be logged. Level 1 is a reasonable level for
 206                 day to day running - it generates a small amount of
 207                 information about operations carried out.</P
 208 ><P
 209 >Levels above 1 will generate considerable
 210                 amounts of log data, and should only be used when
 211                 investigating a problem. Levels above 3 are designed for
 212                 use only by developers and generate HUGE amounts of log
 213                 data, most of which is extremely cryptic.</P
 214 ><P
 215 >Note that specifying this parameter here will
 216                 override the <A
 217 HREF="smb.conf.5.html#loglevel"
 218 TARGET="_top"
 219 >log
 220                 level</A
 221 > parameter in the <A
 222 HREF="smb.conf.5.html"
 223 TARGET="_top"
 224 >               <TT
 225 CLASS="FILENAME"
 226 >smb.conf(5)</TT
 227 ></A
 228 > file.</P
 229 ></DD
 230 ><DT
 231 >-l &#60;log directory&#62;</DT
 232 ><DD
 233 ><P
 234 >If specified,
 235                 <TT
 236 CLASS="REPLACEABLE"
 237 ><I
 238 >log directory</I
 239 ></TT
 240 >
 241                 specifies a log directory into which the "log.smbd" log
 242                 file will be created for informational and debug
 243                 messages from the running server. The log
 244                 file generated is never removed by the server although
 245                 its size may be controlled by the <A
 246 HREF="smb.conf.5.html#maxlogsize"
 247 TARGET="_top"
 248 >max log size</A
 249 >
 250                 option in the <A
 251 HREF="smb.conf.5.html"
 252 TARGET="_top"
 253 ><TT
 254 CLASS="FILENAME"
 255 >               smb.conf(5)</TT
 256 ></A
 257 > file.
 258                 </P
 259 ><P
 260 >The default log directory is specified at
 261                 compile time.</P
 262 ></DD
 263 ><DT
 264 >-O &#60;socket options&#62;</DT
 265 ><DD
 266 ><P
 267 >See the <A
 268 HREF="smb.conf.5.html#socketoptions"
 269 TARGET="_top"
 270 >socket options</A
 271 >
 272                 parameter in the <A
 273 HREF="smb.conf.5.html"
 274 TARGET="_top"
 275 ><TT
 276 CLASS="FILENAME"
 277 >smb.conf(5)
 278                 </TT
 279 ></A
 280 > file for details.</P
 281 ></DD
 282 ><DT
 283 >-p &#60;port number&#62;</DT
 284 ><DD
 285 ><P
 286 ><TT
 287 CLASS="REPLACEABLE"
 288 ><I
 289 >port number</I
 290 ></TT
 291 > is a positive integer
 292                 value.  The default value if this parameter is not
 293                 specified is 139.</P
 294 ><P
 295 >This number is the port number that will be
 296                 used when making connections to the server from client
 297                 software. The standard (well-known) port number for the
 298                 SMB over TCP is 139, hence the default. If you wish to
 299                 run the server as an ordinary user rather than
 300                 as root, most systems will require you to use a port
 301                 number greater than 1024 - ask your system administrator
 302                 for help if you are in this situation.</P
 303 ><P
 304 >In order for the server to be useful by most
 305                 clients, should you configure it on a port other
 306                 than 139, you will require port redirection services
 307                 on port 139, details of which are outlined in rfc1002.txt
 308                 section 4.3.5.</P
 309 ><P
 310 >This parameter is not normally specified except
 311                 in the above situation.</P
 312 ></DD
 313 ><DT
 314 >-s &#60;configuration file&#62;</DT
 315 ><DD
 316 ><P
 317 >The file specified contains the
 318                 configuration details required by the server.  The
 319                 information in this file includes server-specific
 320                 information such as what printcap file to use, as well
 321                 as descriptions of all the services that the server is
 322                 to provide. See <A
 323 HREF="smb.conf.5.html"
 324 TARGET="_top"
 325 ><TT
 326 CLASS="FILENAME"
 327 >               smb.conf(5)</TT
 328 ></A
 329 > for more information.
 330                 The default configuration file name is determined at
 331                 compile time.</P
 332 ></DD
 333 ></DL
 334 ></DIV
 335 ></DIV
 336 ><DIV
 337 CLASS="REFSECT1"
 338 ><A
 339 NAME="AEN110"
 340 ></A
 341 ><H2
 342 >FILES</H2
 343 ><P
 344 ></P
 345 ><DIV
 346 CLASS="VARIABLELIST"
 347 ><DL
 348 ><DT
 349 ><TT
 350 CLASS="FILENAME"
 351 >/etc/inetd.conf</TT
 352 ></DT
 353 ><DD
 354 ><P
 355 >If the server is to be run by the
 356                 <B
 357 CLASS="COMMAND"
 358 >inetd</B
 359 > meta-daemon, this file
 360                 must contain suitable startup information for the
 361                 meta-daemon. See the section INSTALLATION below.
 362                 </P
 363 ></DD
 364 ><DT
 365 ><TT
 366 CLASS="FILENAME"
 367 >/etc/rc</TT
 368 ></DT
 369 ><DD
 370 ><P
 371 >or whatever initialization script your
 372                 system uses).</P
 373 ><P
 374 >If running the server as a daemon at startup,
 375                 this file will need to contain an appropriate startup
 376                 sequence for the server. See the section INSTALLATION
 377                 below.</P
 378 ></DD
 379 ><DT
 380 ><TT
 381 CLASS="FILENAME"
 382 >/etc/services</TT
 383 ></DT
 384 ><DD
 385 ><P
 386 >If running the server via the
 387                 meta-daemon <B
 388 CLASS="COMMAND"
 389 >inetd</B
 390 >, this file
 391                 must contain a mapping of service name (e.g., netbios-ssn)
 392                 to service port (e.g., 139) and protocol type (e.g., tcp).
 393                 See the section INSTALLATION below.</P
 394 ></DD
 395 ><DT
 396 ><TT
 397 CLASS="FILENAME"
 398 >/usr/local/samba/lib/smb.conf</TT
 399 ></DT
 400 ><DD
 401 ><P
 402 >This is the default location of the
 403                 <A
 404 HREF="smb.conf.5.html"
 405 TARGET="_top"
 406 ><TT
 407 CLASS="FILENAME"
 408 >smb.conf</TT
 409 ></A
 410 >
 411                 server configuration file. Other common places that systems
 412                 install this file are <TT
 413 CLASS="FILENAME"
 414 >/usr/samba/lib/smb.conf</TT
 415 >
 416                 and <TT
 417 CLASS="FILENAME"
 418 >/etc/smb.conf</TT
 419 >.</P
 420 ><P
 421 >This file describes all the services the server
 422                 is to make available to clients. See <A
 423 HREF="smb.conf.5.html"
 424 TARGET="_top"
 425 >               <TT
 426 CLASS="FILENAME"
 427 >smb.conf(5)</TT
 428 ></A
 429 >  for more information.</P
 430 ></DD
 431 ></DL
 432 ></DIV
 433 ></DIV
 434 ><DIV
 435 CLASS="REFSECT1"
 436 ><A
 437 NAME="AEN143"
 438 ></A
 439 ><H2
 440 >LIMITATIONS</H2
 441 ><P
 442 >On some systems <B
 443 CLASS="COMMAND"
 444 >smbd</B
 445 > cannot change uid back
 446         to root after a setuid() call.  Such systems are called
 447         trapdoor uid systems. If you have such a system,
 448         you will be unable to connect from a client (such as a PC) as
 449         two different users at once. Attempts to connect the
 450         second user will result in access denied or
 451         similar.</P
 452 ></DIV
 453 ><DIV
 454 CLASS="REFSECT1"
 455 ><A
 456 NAME="AEN147"
 457 ></A
 458 ><H2
 459 >ENVIRONMENTVARIABLES</H2
 460 ><P
 461 ></P
 462 ><DIV
 463 CLASS="VARIABLELIST"
 464 ><DL
 465 ><DT
 466 ><TT
 467 CLASS="ENVAR"
 468 >PRINTER</TT
 469 ></DT
 470 ><DD
 471 ><P
 472 >If no printer name is specified to
 473                 printable services, most systems will use the value of
 474                 this variable (or <TT
 475 CLASS="CONSTANT"
 476 >lp</TT
 477 > if this variable is
 478                 not defined) as the name of the printer to use. This
 479                 is not specific to the server, however.</P
 480 ></DD
 481 ></DL
 482 ></DIV
 483 ></DIV
 484 ><DIV
 485 CLASS="REFSECT1"
 486 ><A
 487 NAME="AEN156"
 488 ></A
 489 ><H2
 490 >INSTALLATION</H2
 491 ><P
 492 >The location of the server and its support files
 493         is a matter for individual system administrators. The following
 494         are thus suggestions only.</P
 495 ><P
 496 >It is recommended that the server software be installed
 497         under the <TT
 498 CLASS="FILENAME"
 499 >/usr/local/samba/</TT
 500 > hierarchy,
 501         in a directory readable by all, writeable only by root. The server
 502         program itself should be executable by all, as users may wish to
 503         run the server themselves (in which case it will of course run
 504         with their privileges).  The server should NOT be setuid. On some
 505         systems it may be worthwhile to make <B
 506 CLASS="COMMAND"
 507 >smbd</B
 508 > setgid to an empty group.
 509         This is because some systems may have a security hole where daemon
 510         processes that become a user can be attached to with a debugger.
 511         Making the <B
 512 CLASS="COMMAND"
 513 >smbd</B
 514 > file setgid to an empty group may prevent
 515         this hole from being exploited. This security hole and the suggested
 516         fix has only been confirmed on old versions (pre-kernel 2.0) of Linux
 517         at the time this was written. It is possible that this hole only
 518         exists in Linux, as testing on other systems has thus far shown them
 519         to be immune.</P
 520 ><P
 521 >The server log files should be put in a directory readable and
 522         writeable only by root, as the log files may contain sensitive
 523         information.</P
 524 ><P
 525 >The configuration file should be placed in a directory
 526         readable and writeable only by root, as the configuration file
 527         controls security for the services offered by the server. The
 528         configuration file can be made readable by all if desired, but
 529         this is not necessary for correct operation of the server and is
 530         not recommended. A sample configuration file <TT
 531 CLASS="FILENAME"
 532 >smb.conf.sample
 533         </TT
 534 > is supplied with the source to the server - this may
 535         be renamed to <TT
 536 CLASS="FILENAME"
 537 >smb.conf</TT
 538 > and modified to suit
 539         your needs.</P
 540 ><P
 541 >The remaining notes will assume the following:</P
 542 ><P
 543 ></P
 544 ><UL
 545 ><LI
 546 ><P
 547 ><B
 548 CLASS="COMMAND"
 549 >smbd</B
 550 > (the server program)
 551                 installed in <TT
 552 CLASS="FILENAME"
 553 >/usr/local/samba/bin</TT
 554 ></P
 555 ></LI
 556 ><LI
 557 ><P
 558 ><TT
 559 CLASS="FILENAME"
 560 >smb.conf</TT
 561 > (the configuration
 562                 file) installed in <TT
 563 CLASS="FILENAME"
 564 >/usr/local/samba/lib</TT
 565 ></P
 566 ></LI
 567 ><LI
 568 ><P
 569 >log files stored in <TT
 570 CLASS="FILENAME"
 571 >/var/adm/smblogs
 572                 </TT
 573 ></P
 574 ></LI
 575 ></UL
 576 ><P
 577 >The server may be run either as a daemon by users
 578         or at startup, or it may be run from a meta-daemon such as
 579         <B
 580 CLASS="COMMAND"
 581 >inetd</B
 582 > upon request. If run as a daemon,
 583         the server will always be ready, so starting sessions will be
 584         faster. If run from a meta-daemon some memory will be saved and
 585         utilities such as the tcpd TCP-wrapper may be used for extra
 586         security.  For serious use as file server it is recommended
 587         that <B
 588 CLASS="COMMAND"
 589 >smbd</B
 590 > be run as a daemon.</P
 591 ><P
 592 >When you've decided, continue with either</P
 593 ><P
 594 ></P
 595 ><UL
 596 ><LI
 597 ><P
 598 >RUNNING THE SERVER AS A DAEMON or</P
 599 ></LI
 600 ><LI
 601 ><P
 602 >RUNNING THE SERVER ON REQUEST.</P
 603 ></LI
 604 ></UL
 605 ></DIV
 606 ><DIV
 607 CLASS="REFSECT1"
 608 ><A
 609 NAME="AEN189"
 610 ></A
 611 ><H2
 612 >RUNNING THE SERVER AS A DAEMON</H2
 613 ><P
 614 >To run the server as a daemon from the command
 615         line, simply put the <EM
 616 >-D</EM
 617 > option on the
 618         command line. There is no need to place an ampersand at
 619         the end of the command line - the <EM
 620 >-D</EM
 621 >
 622         option causes the server to detach itself from the tty
 623         anyway.</P
 624 ><P
 625 >Any user can run the server as a daemon (execute
 626         permissions permitting, of course). This is useful for
 627         testing purposes, and may even be useful as a temporary
 628         substitute for something like ftp. When run this way, however,
 629         the server will only have the privileges of the user who ran
 630         it.</P
 631 ><P
 632 >To ensure that the server is run as a daemon whenever
 633         the machine is started, and to ensure that it runs as root
 634         so that it can serve multiple clients, you will need to modify
 635         the system startup files. Wherever appropriate (for example, in
 636         <TT
 637 CLASS="FILENAME"
 638 >/etc/rc</TT
 639 >), insert the following line,
 640         substituting port number, log file location, configuration file
 641         location and debug level as desired:</P
 642 ><P
 643 ><B
 644 CLASS="COMMAND"
 645 >/usr/local/samba/bin/smbd -D -l /var/adm/smblogs/log
 646         -s /usr/local/samba/lib/smb.conf</B
 647 ></P
 648 ><P
 649 >(The above should appear in your initialization script
 650         as a single line.  Depending on your terminal characteristics,
 651         it may not appear that way in this man page. If the above appears
 652         as more than one line, please treat any newlines or indentation
 653         as a single space or TAB character.)</P
 654 ><P
 655 >If the options used at compile time are appropriate for
 656         your system, all parameters except <EM
 657 >-D</EM
 658 > may
 659         be omitted. See the section OPTIONS above.</P
 660 ></DIV
 661 ><DIV
 662 CLASS="REFSECT1"
 663 ><A
 664 NAME="AEN202"
 665 ></A
 666 ><H2
 667 >RUNNING THE SERVER ON REQUEST</H2
 668 ><P
 669 >If your system uses a meta-daemon such as <B
 670 CLASS="COMMAND"
 671 >inetd
 672         </B
 673 >, you can arrange to have the <B
 674 CLASS="COMMAND"
 675 >smbd</B
 676 > server started
 677         whenever a process attempts to connect to it. This requires several
 678         changes to the startup files on the host machine. If you are
 679         experimenting as an ordinary user rather than as root, you will
 680         need the assistance of your system administrator to modify the
 681         system files.</P
 682 ><P
 683 >You will probably want to set up the NetBIOS name server
 684         <A
 685 HREF="nmbd.8.html"
 686 TARGET="_top"
 687 ><B
 688 CLASS="COMMAND"
 689 >nmbd</B
 690 ></A
 691 > at
 692         the same time as <B
 693 CLASS="COMMAND"
 694 >smbd</B
 695 >. To do this refer to the
 696         man page for <A
 697 HREF="nmbd.8.html"
 698 TARGET="_top"
 699 ><B
 700 CLASS="COMMAND"
 701 >nmbd(8)</B
 702 >
 703         </A
 704 >.</P
 705 ><P
 706 >First, ensure that a port is configured in the file
 707         <TT
 708 CLASS="FILENAME"
 709 >/etc/services</TT
 710 >. The well-known port 139
 711         should be used if possible, though any port may be used.</P
 712 ><P
 713 >Ensure that a line similar to the following is in
 714         <TT
 715 CLASS="FILENAME"
 716 >/etc/services</TT
 717 >:</P
 718 ><P
 719 ><B
 720 CLASS="COMMAND"
 721 >netbios-ssn    139/tcp</B
 722 ></P
 723 ><P
 724 >Note for NIS/YP users - you may need to rebuild the
 725         NIS service maps rather than alter your local <TT
 726 CLASS="FILENAME"
 727 >/etc/services
 728         </TT
 729 > file.</P
 730 ><P
 731 >Next, put a suitable line in the file <TT
 732 CLASS="FILENAME"
 733 >/etc/inetd.conf
 734         </TT
 735 > (in the unlikely event that you are using a meta-daemon
 736         other than inetd, you are on your own). Note that the first item
 737         in this line matches the service name in <TT
 738 CLASS="FILENAME"
 739 >/etc/services
 740         </TT
 741 >.  Substitute appropriate values for your system
 742         in this line (see <B
 743 CLASS="COMMAND"
 744 >inetd(8)</B
 745 >):</P
 746 ><P
 747 ><B
 748 CLASS="COMMAND"
 749 >netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd
 750         -d1 -l/var/adm/smblogs/log -s/usr/local/samba/lib/smb.conf</B
 751 ></P
 752 ><P
 753 >(The above should appear in <TT
 754 CLASS="FILENAME"
 755 >/etc/inetd.conf</TT
 756 >
 757         as a single line. Depending on your terminal characteristics, it may
 758         not appear that way in this man page.  If the above appears as more
 759         than one line, please treat any newlines or indentation as a single
 760         space or TAB character.)</P
 761 ><P
 762 >Note that there is no need to specify a port number here,
 763         even if you are using a non-standard port number.</P
 764 ><P
 765 >Lastly, edit the configuration file to provide suitable
 766         services. To start with, the following two services should be
 767         all you need:</P
 768 ><TABLE
 769 BORDER="0"
 770 BGCOLOR="#E0E0E0"
 771 WIDTH="100%"
 772 ><TR
 773 ><TD
 774 ><PRE
 775 CLASS="SCREEN"
 776 >       <TT
 777 CLASS="COMPUTEROUTPUT"
 778 >       [homes]
 779                 writeable = yes
 780
 781         [printers]
 782                 writeable = no
 783                 printable = yes
 784                 path = /tmp
 785                 public = yes
 786         </TT
 787 >
 788         </PRE
 789 ></TD
 790 ></TR
 791 ></TABLE
 792 ><P
 793 >This will allow you to connect to your home directory
 794         and print to any printer supported by the host (user privileges
 795         permitting).</P
 796 ></DIV
 797 ><DIV
 798 CLASS="REFSECT1"
 799 ><A
 800 NAME="AEN234"
 801 ></A
 802 ><H2
 803 >PAM INTERACTION</H2
 804 ><P
 805 >Samba uses PAM for authentication (when presented with a plaintext
 806         password), for account checking (is this account disabled?) and for
 807         session management.  The degree too which samba supports PAM is restricted
 808         by the limitations of the SMB protocol and the
 809         <A
 810 HREF="smb.conf.5.html#OBEYPAMRESRICTIONS"
 811 TARGET="_top"
 812 >obey pam restricions</A
 813 >
 814         smb.conf paramater.  When this is set, the following restrictions apply:
 815         </P
 816 ><P
 817 ></P
 818 ><UL
 819 ><LI
 820 ><P
 821 ><EM
 822 >Account Validation</EM
 823 >:  All acccesses to a
 824         samba server are checked
 825         against PAM to see if the account is vaild, not disabled and is permitted to
 826         login at this time.  This also applies to encrypted logins.
 827         </P
 828 ></LI
 829 ><LI
 830 ><P
 831 ><EM
 832 >Session Management</EM
 833 >:  When not using share
 834         level secuirty, users must pass PAM's session checks before access
 835         is granted.  Note however, that this is bypassed in share level secuirty.
 836         Note also that some older pam configuration files may need a line
 837         added for session support.
 838         </P
 839 ></LI
 840 ></UL
 841 ></DIV
 842 ><DIV
 843 CLASS="REFSECT1"
 844 ><A
 845 NAME="AEN245"
 846 ></A
 847 ><H2
 848 >TESTING THE INSTALLATION</H2
 849 ><P
 850 >If running the server as a daemon, execute it before
 851         proceeding. If using a meta-daemon, either restart the system
 852         or kill and restart the meta-daemon. Some versions of
 853         <B
 854 CLASS="COMMAND"
 855 >inetd</B
 856 > will reread their configuration
 857         tables if they receive a HUP signal.</P
 858 ><P
 859 >If your machine's name is <TT
 860 CLASS="REPLACEABLE"
 861 ><I
 862 >fred</I
 863 ></TT
 864 > and your
 865         name is <TT
 866 CLASS="REPLACEABLE"
 867 ><I
 868 >mary</I
 869 ></TT
 870 >, you should now be able to connect
 871         to the service <TT
 872 CLASS="FILENAME"
 873 >\\fred\mary</TT
 874 >.
 875         </P
 876 ><P
 877 >To properly test and experiment with the server, we
 878         recommend using the <B
 879 CLASS="COMMAND"
 880 >smbclient</B
 881 > program (see
 882         <A
 883 HREF="smbclient.1.html"
 884 TARGET="_top"
 885 ><B
 886 CLASS="COMMAND"
 887 >smbclient(1)</B
 888 ></A
 889 >)
 890         and also going through the steps outlined in the file
 891         <TT
 892 CLASS="FILENAME"
 893 >DIAGNOSIS.txt</TT
 894 > in the <TT
 895 CLASS="FILENAME"
 896 >docs/</TT
 897 >
 898         directory of your Samba installation.</P
 899 ></DIV
 900 ><DIV
 901 CLASS="REFSECT1"
 902 ><A
 903 NAME="AEN259"
 904 ></A
 905 ><H2
 906 >VERSION</H2
 907 ><P
 908 >This man page is correct for version 2.2 of
 909         the Samba suite.</P
 910 ></DIV
 911 ><DIV
 912 CLASS="REFSECT1"
 913 ><A
 914 NAME="AEN262"
 915 ></A
 916 ><H2
 917 >DIAGNOSTICS</H2
 918 ><P
 919 >Most diagnostics issued by the server are logged
 920         in a specified log file. The log file name is specified
 921         at compile time, but may be overridden on the command line.</P
 922 ><P
 923 >The number and nature of diagnostics available depends
 924         on the debug level used by the server. If you have problems, set
 925         the debug level to 3 and peruse the log files.</P
 926 ><P
 927 >Most messages are reasonably self-explanatory. Unfortunately,
 928         at the time this man page was created, there are too many diagnostics
 929         available in the source code to warrant describing each and every
 930         diagnostic. At this stage your best bet is still to grep the
 931         source code and inspect the conditions that gave rise to the
 932         diagnostics you are seeing.</P
 933 ></DIV
 934 ><DIV
 935 CLASS="REFSECT1"
 936 ><A
 937 NAME="AEN267"
 938 ></A
 939 ><H2
 940 >SIGNALS</H2
 941 ><P
 942 >Sending the <B
 943 CLASS="COMMAND"
 944 >smbd</B
 945 > a SIGHUP will cause it to
 946         reload its <TT
 947 CLASS="FILENAME"
 948 >smb.conf</TT
 949 > configuration
 950         file within a short period of time.</P
 951 ><P
 952 >To shut down a user's <B
 953 CLASS="COMMAND"
 954 >smbd</B
 955 > process it is recommended
 956         that <B
 957 CLASS="COMMAND"
 958 >SIGKILL (-9)</B
 959 > <EM
 960 >NOT</EM
 961 >
 962         be used, except as a last resort, as this may leave the shared
 963         memory area in an inconsistent state. The safe way to terminate
 964         an <B
 965 CLASS="COMMAND"
 966 >smbd</B
 967 > is to send it a SIGTERM (-15) signal and wait for
 968         it to die on its own.</P
 969 ><P
 970 >The debug log level of <B
 971 CLASS="COMMAND"
 972 >smbd</B
 973 > may be raised
 974         or lowered using <A
 975 HREF="smbcontrol.1.html"
 976 TARGET="_top"
 977 ><B
 978 CLASS="COMMAND"
 979 >smbcontrol(1)
 980         </B
 981 ></A
 982 > program (SIGUSR[1|2] signals are no longer used in
 983         Samba 2.2). This is to allow transient problems to be diagnosed,
 984         whilst still running at a normally low log level.</P
 985 ><P
 986 >Note that as the signal handlers send a debug write,
 987         they are not re-entrant in <B
 988 CLASS="COMMAND"
 989 >smbd</B
 990 >. This you should wait until
 991         <B
 992 CLASS="COMMAND"
 993 >smbd</B
 994 > is in a state of waiting for an incoming SMB before
 995         issuing them. It is possible to make the signal handlers safe
 996         by un-blocking the signals before the select call and re-blocking
 997         them after, however this would affect performance.</P
 998 ></DIV
 999 ><DIV
1000 CLASS="REFSECT1"
1001 ><A
1002 NAME="AEN284"
1003 ></A
1004 ><H2
1005 >SEE ALSO</H2
1006 ><P
1007 >hosts_access(5), <B
1008 CLASS="COMMAND"
1009 >inetd(8)</B
1010 >,
1011         <A
1012 HREF="nmbd.8.html"
1013 TARGET="_top"
1014 ><B
1015 CLASS="COMMAND"
1016 >nmbd(8)</B
1017 ></A
1018 >,
1019         <A
1020 HREF="smb.conf.5.html"
1021 TARGET="_top"
1022 ><TT
1023 CLASS="FILENAME"
1024 >smb.conf(5)</TT
1025 >
1026         </A
1027 >, <A
1028 HREF="smbclient.1.html"
1029 TARGET="_top"
1030 ><B
1031 CLASS="COMMAND"
1032 >smbclient(1)
1033         </B
1034 ></A
1035 >, <A
1036 HREF="testparm.1.html"
1037 TARGET="_top"
1038 ><B
1039 CLASS="COMMAND"
1040 >       testparm(1)</B
1041 ></A
1042 >, <A
1043 HREF="testprns.1.html"
1044 TARGET="_top"
1045 >       <B
1046 CLASS="COMMAND"
1047 >testprns(1)</B
1048 ></A
1049 >, and the Internet RFC's
1050         <TT
1051 CLASS="FILENAME"
1052 >rfc1001.txt</TT
1053 >, <TT
1054 CLASS="FILENAME"
1055 >rfc1002.txt</TT
1056 >.
1057         In addition the CIFS (formerly SMB) specification is available
1058         as a link from the Web page <A
1059 HREF="http://samba.org/cifs/"
1060 TARGET="_top"
1061 >
1062         http://samba.org/cifs/</A
1063 >.</P
1064 ></DIV
1065 ><DIV
1066 CLASS="REFSECT1"
1067 ><A
1068 NAME="AEN301"
1069 ></A
1070 ><H2
1071 >AUTHOR</H2
1072 ><P
1073 >The original Samba software and related utilities
1074         were created by Andrew Tridgell. Samba is now developed
1075         by the Samba Team as an Open Source project similar
1076         to the way the Linux kernel is developed.</P
1077 ><P
1078 >The original Samba man pages were written by Karl Auer.
1079         The man page sources were converted to YODL format (another
1080         excellent piece of Open Source software, available at
1081         <A
1082 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
1083 TARGET="_top"
1084 >       ftp://ftp.icce.rug.nl/pub/unix/</A
1085 >) and updated for the Samba 2.0
1086         release by Jeremy Allison.  The conversion to DocBook for
1087         Samba 2.2 was done by Gerald Carter</P
1088 ></DIV
1089 ></BODY
1090 ></HTML
1091 >