1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
|
<HTML
><HEAD
><TITLE
>smbd</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="SMBD"
>smbd</A
></H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN5"
></A
><H2
>Name</H2
>smbd -- server to provide SMB/CIFS services to clients</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>smbd</B
> [-D] [-a] [-i] [-o] [-P] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN24"
></A
><H2
>DESCRIPTION</H2
><P
>This program is part of the Samba suite.</P
><P
><B
CLASS="COMMAND"
>smbd</B
> is the server daemon that
provides filesharing and printing services to Windows clients.
The server provides filespace and printer services to
clients using the SMB (or CIFS) protocol. This is compatible
with the LanManager protocol, and can service LanManager
clients. These include MSCLIENT 3.0 for DOS, Windows for
Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
OS/2, DAVE for Macintosh, and smbfs for Linux.</P
><P
>An extensive description of the services that the
server can provide is given in the man page for the
configuration file controlling the attributes of those
services (see <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf(5)
</TT
></A
>. This man page will not describe the
services, but will concentrate on the administrative aspects
of running the server.</P
><P
>Please note that there are significant security
implications to running this server, and the <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf(5)</TT
></A
>
manpage should be regarded as mandatory reading before
proceeding with installation.</P
><P
>A session is created whenever a client requests one.
Each client gets a copy of the server for each session. This
copy then services all connections made by the client during
that session. When all connections from its client are closed,
the copy of the server for that client terminates.</P
><P
>The configuration file, and any files that it includes,
are automatically reloaded every minute, if they change. You
can force a reload by sending a SIGHUP to the server. Reloading
the configuration file will not affect connections to any service
that is already established. Either the user will have to
disconnect from the service, or <B
CLASS="COMMAND"
>smbd</B
> killed and restarted.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN38"
></A
><H2
>OPTIONS</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>-D</DT
><DD
><P
>If specified, this parameter causes
the server to operate as a daemon. That is, it detaches
itself and runs in the background, fielding requests
on the appropriate port. Operating the server as a
daemon is the recommended way of running <B
CLASS="COMMAND"
>smbd</B
> for
servers that provide more than casual use file and
print services. This switch is assumed if <B
CLASS="COMMAND"
>smbd
</B
> is executed on the command line of a shell.
</P
></DD
><DT
>-a</DT
><DD
><P
>If this parameter is specified, each new
connection will append log messages to the log file.
This is the default.</P
></DD
><DT
>-i</DT
><DD
><P
>If this parameter is specified it causes the
server to run "interactively", not as a daemon, even if the
server is executed on the command line of a shell. Setting this
parameter negates the implicit deamon mode when run from the
command line.
</P
></DD
><DT
>-o</DT
><DD
><P
>If this parameter is specified, the
log files will be overwritten when opened. By default,
<B
CLASS="COMMAND"
>smbd</B
> will append entries to the log
files.</P
></DD
><DT
>-P</DT
><DD
><P
>Passive option. Causes <B
CLASS="COMMAND"
>smbd</B
> not to
send any network traffic out. Used for debugging by
the developers only.</P
></DD
><DT
>-h</DT
><DD
><P
>Prints the help information (usage)
for <B
CLASS="COMMAND"
>smbd</B
>.</P
></DD
><DT
>-v</DT
><DD
><P
>Prints the version number for
<B
CLASS="COMMAND"
>smbd</B
>.</P
></DD
><DT
>-b</DT
><DD
><P
>Prints information about how
Samba was built.</P
></DD
><DT
>-d <debug level></DT
><DD
><P
><TT
CLASS="REPLACEABLE"
><I
>debuglevel</I
></TT
> is an integer
from 0 to 10. The default value if this parameter is
not specified is zero.</P
><P
>The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
information about operations carried out.</P
><P
>Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
data, most of which is extremely cryptic.</P
><P
>Note that specifying this parameter here will
override the <A
HREF="smb.conf.5.html#loglevel"
TARGET="_top"
>log
level</A
> parameter in the <A
HREF="smb.conf.5.html"
TARGET="_top"
> <TT
CLASS="FILENAME"
>smb.conf(5)</TT
></A
> file.</P
></DD
><DT
>-l <log directory></DT
><DD
><P
>If specified,
<TT
CLASS="REPLACEABLE"
><I
>log directory</I
></TT
>
specifies a log directory into which the "log.smbd" log
file will be created for informational and debug
messages from the running server. The log
file generated is never removed by the server although
its size may be controlled by the <A
HREF="smb.conf.5.html#maxlogsize"
TARGET="_top"
>max log size</A
>
option in the <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
> smb.conf(5)</TT
></A
> file.
</P
><P
>The default log directory is specified at
compile time.</P
></DD
><DT
>-O <socket options></DT
><DD
><P
>See the <A
HREF="smb.conf.5.html#socketoptions"
TARGET="_top"
>socket options</A
>
parameter in the <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf(5)
</TT
></A
> file for details.</P
></DD
><DT
>-p <port number></DT
><DD
><P
><TT
CLASS="REPLACEABLE"
><I
>port number</I
></TT
> is a positive integer
value. The default value if this parameter is not
specified is 139.</P
><P
>This number is the port number that will be
used when making connections to the server from client
software. The standard (well-known) port number for the
SMB over TCP is 139, hence the default. If you wish to
run the server as an ordinary user rather than
as root, most systems will require you to use a port
number greater than 1024 - ask your system administrator
for help if you are in this situation.</P
><P
>In order for the server to be useful by most
clients, should you configure it on a port other
than 139, you will require port redirection services
on port 139, details of which are outlined in rfc1002.txt
section 4.3.5.</P
><P
>This parameter is not normally specified except
in the above situation.</P
></DD
><DT
>-s <configuration file></DT
><DD
><P
>The file specified contains the
configuration details required by the server. The
information in this file includes server-specific
information such as what printcap file to use, as well
as descriptions of all the services that the server is
to provide. See <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
> smb.conf(5)</TT
></A
> for more information.
The default configuration file name is determined at
compile time.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN120"
></A
><H2
>FILES</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="FILENAME"
>/etc/inetd.conf</TT
></DT
><DD
><P
>If the server is to be run by the
<B
CLASS="COMMAND"
>inetd</B
> meta-daemon, this file
must contain suitable startup information for the
meta-daemon. See the <A
HREF="UNIX_INSTALL.html"
TARGET="_top"
>UNIX_INSTALL.html</A
>
document for details.
</P
></DD
><DT
><TT
CLASS="FILENAME"
>/etc/rc</TT
></DT
><DD
><P
>or whatever initialization script your
system uses).</P
><P
>If running the server as a daemon at startup,
this file will need to contain an appropriate startup
sequence for the server. See the <A
HREF="UNIX_INSTALL.html"
TARGET="_top"
>UNIX_INSTALL.html</A
>
document for details.</P
></DD
><DT
><TT
CLASS="FILENAME"
>/etc/services</TT
></DT
><DD
><P
>If running the server via the
meta-daemon <B
CLASS="COMMAND"
>inetd</B
>, this file
must contain a mapping of service name (e.g., netbios-ssn)
to service port (e.g., 139) and protocol type (e.g., tcp).
See the <A
HREF="UNIX_INSTALL.html"
TARGET="_top"
>UNIX_INSTALL.html</A
>
document for details.</P
></DD
><DT
><TT
CLASS="FILENAME"
>/usr/local/samba/lib/smb.conf</TT
></DT
><DD
><P
>This is the default location of the
<A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf</TT
></A
>
server configuration file. Other common places that systems
install this file are <TT
CLASS="FILENAME"
>/usr/samba/lib/smb.conf</TT
>
and <TT
CLASS="FILENAME"
>/etc/smb.conf</TT
>.</P
><P
>This file describes all the services the server
is to make available to clients. See <A
HREF="smb.conf.5.html"
TARGET="_top"
> <TT
CLASS="FILENAME"
>smb.conf(5)</TT
></A
> for more information.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN156"
></A
><H2
>LIMITATIONS</H2
><P
>On some systems <B
CLASS="COMMAND"
>smbd</B
> cannot change uid back
to root after a setuid() call. Such systems are called
trapdoor uid systems. If you have such a system,
you will be unable to connect from a client (such as a PC) as
two different users at once. Attempts to connect the
second user will result in access denied or
similar.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN160"
></A
><H2
>ENVIRONMENT VARIABLES</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="ENVAR"
>PRINTER</TT
></DT
><DD
><P
>If no printer name is specified to
printable services, most systems will use the value of
this variable (or <TT
CLASS="CONSTANT"
>lp</TT
> if this variable is
not defined) as the name of the printer to use. This
is not specific to the server, however.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN169"
></A
><H2
>PAM INTERACTION</H2
><P
>Samba uses PAM for authentication (when presented with a plaintext
password), for account checking (is this account disabled?) and for
session management. The degree too which samba supports PAM is restricted
by the limitations of the SMB protocol and the
<A
HREF="smb.conf.5.html#OBEYPAMRESRICTIONS"
TARGET="_top"
>obey pam restricions</A
>
smb.conf paramater. When this is set, the following restrictions apply:
</P
><P
></P
><UL
><LI
><P
><EM
>Account Validation</EM
>: All acccesses to a
samba server are checked
against PAM to see if the account is vaild, not disabled and is permitted to
login at this time. This also applies to encrypted logins.
</P
></LI
><LI
><P
><EM
>Session Management</EM
>: When not using share
level secuirty, users must pass PAM's session checks before access
is granted. Note however, that this is bypassed in share level secuirty.
Note also that some older pam configuration files may need a line
added for session support.
</P
></LI
></UL
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN180"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN183"
></A
><H2
>DIAGNOSTICS</H2
><P
>Most diagnostics issued by the server are logged
in a specified log file. The log file name is specified
at compile time, but may be overridden on the command line.</P
><P
>The number and nature of diagnostics available depends
on the debug level used by the server. If you have problems, set
the debug level to 3 and peruse the log files.</P
><P
>Most messages are reasonably self-explanatory. Unfortunately,
at the time this man page was created, there are too many diagnostics
available in the source code to warrant describing each and every
diagnostic. At this stage your best bet is still to grep the
source code and inspect the conditions that gave rise to the
diagnostics you are seeing.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN188"
></A
><H2
>SIGNALS</H2
><P
>Sending the <B
CLASS="COMMAND"
>smbd</B
> a SIGHUP will cause it to
reload its <TT
CLASS="FILENAME"
>smb.conf</TT
> configuration
file within a short period of time.</P
><P
>To shut down a user's <B
CLASS="COMMAND"
>smbd</B
> process it is recommended
that <B
CLASS="COMMAND"
>SIGKILL (-9)</B
> <EM
>NOT</EM
>
be used, except as a last resort, as this may leave the shared
memory area in an inconsistent state. The safe way to terminate
an <B
CLASS="COMMAND"
>smbd</B
> is to send it a SIGTERM (-15) signal and wait for
it to die on its own.</P
><P
>The debug log level of <B
CLASS="COMMAND"
>smbd</B
> may be raised
or lowered using <A
HREF="smbcontrol.1.html"
TARGET="_top"
><B
CLASS="COMMAND"
>smbcontrol(1)
</B
></A
> program (SIGUSR[1|2] signals are no longer used in
Samba 2.2). This is to allow transient problems to be diagnosed,
whilst still running at a normally low log level.</P
><P
>Note that as the signal handlers send a debug write,
they are not re-entrant in <B
CLASS="COMMAND"
>smbd</B
>. This you should wait until
<B
CLASS="COMMAND"
>smbd</B
> is in a state of waiting for an incoming SMB before
issuing them. It is possible to make the signal handlers safe
by un-blocking the signals before the select call and re-blocking
them after, however this would affect performance.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN205"
></A
><H2
>SEE ALSO</H2
><P
>hosts_access(5), <B
CLASS="COMMAND"
>inetd(8)</B
>,
<A
HREF="nmbd.8.html"
TARGET="_top"
><B
CLASS="COMMAND"
>nmbd(8)</B
></A
>,
<A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf(5)</TT
>
</A
>, <A
HREF="smbclient.1.html"
TARGET="_top"
><B
CLASS="COMMAND"
>smbclient(1)
</B
></A
>, <A
HREF="testparm.1.html"
TARGET="_top"
><B
CLASS="COMMAND"
> testparm(1)</B
></A
>, <A
HREF="testprns.1.html"
TARGET="_top"
> <B
CLASS="COMMAND"
>testprns(1)</B
></A
>, and the Internet RFC's
<TT
CLASS="FILENAME"
>rfc1001.txt</TT
>, <TT
CLASS="FILENAME"
>rfc1002.txt</TT
>.
In addition the CIFS (formerly SMB) specification is available
as a link from the Web page <A
HREF="http://samba.org/cifs/"
TARGET="_top"
>
http://samba.org/cifs/</A
>.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN222"
></A
><H2
>AUTHOR</H2
><P
>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</P
><P
>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
<A
HREF="ftp://ftp.icce.rug.nl/pub/unix/"
TARGET="_top"
> ftp://ftp.icce.rug.nl/pub/unix/</A
>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter</P
></DIV
></BODY
></HTML
>
|
