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