Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 62 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       smbd  [ -D ]  [ -a ]  [ -i ]  [ -o ]  [ -P ]  [ -h ]  [ -V
       ]  [ -d <debug level> ]  [ -l  <log  directory>  ]   [  -p
       <port  number> ]  [ -O <socket option> ]  [ -s <configura­
       tion file> ]


       This program is part of the Samba suite.

       smbd 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, Win­
       dows 95/98/ME, Windows NT, Windows 2000,  OS/2,  DAVE  for
       Macintosh, and smbfs for Linux.

       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
        This man page will not describe the  services,  but  will
       concentrate  on  the administrative aspects of running the

       Please note that there are significant  security  implica­
       tions  to running this server, and the smb.conf(5) manpage
       should be regarded as mandatory reading before  proceeding
       with installation.

       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 dur­
       ing that session. When all connections from its client are
       closed, the copy of the server for that client terminates.

       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 connec­
       tions to any service that is already  established.  Either
       the user will have to disconnect from the service, or smbd
       killed and restarted.


       -D     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  smbd  for
              servers  that provide more than casual use file and
              be overwritten when opened. By default,  smbd  will
              append entries to the log files.

       -P     Passive option. Causes smbd not to send any network
              traffic out. Used for debugging by  the  developers

       -h     Prints the help information (usage) for smbd.

       -v     Prints the version number for smbd.

       -d <debug level>
              debuglevel  is an integer from 0 to 10. The default
              value if this parameter is not specified is zero.

              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  seri­
              ous  warnings  will be logged. Level 1 is a reason­
              able level for day to day running - it generates  a
              small  amount  of information about operations car­
              ried out.

              Levels above 1 will generate  considerable  amounts
              of  log data, and should only be used when investi­
              gating 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.

              Note that specifying this parameter here will over­
              ride the log level file.

       -l <log directory>
              If  specified, log directory specifies a log direc­
              tory 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 con­
              trolled  by  the  max  log  size  option   in   the
              smb.conf(5)  file.  Beware: If the directory speci­
              fied does not exist, smbd will log to  the  default
              debug log location defined at compile time.

              The  default  log directory is specified at compile

       -O <socket options>
              See the socket options parameter in the smb.conf(5)
               file for details.

       -p <port number>
              port  number  is  a  positive  integer  value.  The
              clients, should you configure it on  a  port  other
              than  139,  you  will require port redirection ser­
              vices on port 139, details of which are outlined in
              rfc1002.txt section 4.3.5.

              This  parameter is not normally specified except in
              the above situation.

       -s <configuration file>
              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 descrip­
              tions of all the services that  the  server  is  to
              provide.  See   smb.conf(5)  for  more information.
              The default configuration file name  is  determined
              at compile time.


              If  the  server is to be run by the inetd meta-dae­
              mon, this file must contain suitable startup infor­
              mation     for    the    meta-daemon.    See    the
              UNIX_INSTALL.html document for details.

              or  whatever  initialization  script  your   system

              If  running the server as a daemon at startup, this
              file will need to contain  an  appropriate  startup
              sequence  for the server. See the UNIX_INSTALL.html
              document for details.

              If running the server via  the  meta-daemon  inetd,
              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
              UNIX_INSTALL.html document for details.

              This is the default location of the smb.conf server
              configuration  file.  Other common places that sys­
              tems install this file are  /usr/samba/lib/smb.conf
              and /etc/smb.conf.

              This  file describes all the services the server is
              to make available to clients. See  smb.conf(5)  for
              more information.



       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 obey pam restricions  smb.conf
       paramater.  When  this  is set, the following restrictions

       · Account Validation: 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.

       · Session Management: 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  configu­
         ration  files may need a line added for session support.


       This man page is correct for  version  2.2  of  the  Samba


       One  of  the  common  causes of difficulty when installing
       Samba and SWAT is the existsnece of some type of  firewall
       or  port filtering software on the Samba server. Make sure
       that the appropriate ports outlined in this man  page  are
       available  on  the  server  and  are  not  currently being
       blocked by some type of security software such as iptables
       or  "port  sentry".  For more troubleshooting information,
       refer to the  additional  documentation  included  in  the
       Samba distribution.

       Most  diagnostics  issued  by  the  server are logged in a
       specified log file. The log file name is specified at com­
       pile time, but may be overridden on the command line.

       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.

       Most  messages  are  reasonably self-explanatory. Unfortu­
       nately, at the time this man page was created,  there  are
       too  many diagnostics available in the source code to war­
       rant 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

       whilst still running at a normally low log level.

       Note that as the signal handlers send a debug write,  they
       are  not  re-entrant  in  smbd. This you should wait until
       smbd 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 perfor­


       hosts_access(5), inetd(8), nmbd(8) smb.conf(5)
        and the  Internet  RFC's  rfc1001.txt,  rfc1002.txt.   In
       addition  the  CIFS (formerly SMB) specification is avail­
       able as a link from the  Web  page  http://samba.org/cifs/


       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.

       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,  avail­
       able           at          ftp://ftp.icce.rug.nl/pub/unix/
       <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the
       Samba  2.0  release  by  Jeremy Allison. The conversion to
       DocBook for Samba 2.2 was done by Gerald Carter

                         19 November 2002                 SMBD(8)

Looking for a "printer friendly" version?



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can help in many different ways.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds