JelmerR.VernooijR.
The Samba Team
jelmer@samba.org
'>
&person.jelmer;'>
GeraldCarter(Jerry)
Samba Team
jerry@samba.org
'>
&person.jerry;'>
JeremyAllison
Samba Team
jra@samba.org
'>
JohnTerpstraH.
Samba Team
jht@samba.org
'>
&person.jht;'>
GuentherDeschner
Samba Team
gd@samba.org
'>
&person.gd;'>
KarlAuer
Samba Team
kauer@biplane.com.au
'>
&person.kauer;'>
DanShearer
Samba Team
dan@samba.org
'>
&person.danshearer;'>
TimPotter
Samba Team
tpot@samba.org
'>
&person.tpot;'>
AndrewTridgell
Samba Team
tridge@samba.org
'>
JimMcDonough
IBM
jmcd@us.ibm.com
'>
&person.jmcd;'>
VolkerLendecke
Samba Team
Volker.Lendecke@SerNet.DE
'>
&person.vl;'>
DavidBannon
Samba Team
dbannon@samba.org
'>
RafalSzczesniak
Samba Team
mimir@samba.org
'>
DavidLechnyr
Unofficial HOWTO
david@lechnyr.com
'>
EricRoseme
HP Oplocks Usage Recommendations Whitepaper
eric.roseme@hp.com
'>
GavinHenry
Suretec Systems Limited, UK
ghenry@suretecsystems.com
'>
-d|--debuglevel=level
level is an integer
from 0 to 10. The default value if this parameter is
not specified is 0.
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.
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.
Note that specifying this parameter here will
override the log level parameter
in the &smb.conf; file.
'>
-d|--debuglevel=level
level is an integer
from 0 to 10. The default value if this parameter is
not specified is 1.
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.
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.
Note that specifying this parameter here will
override the log level parameter
in the &smb.conf; file.
'>
-s|--configfile <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 descriptions of all the services that the server is
to provide. See &smb.conf; for more information.
The default configuration file name is determined at
compile time.
'>
-V|--version
Prints the program version number.
'>
-l|--log-basename=logdirectory
Base directory name for log/debug files. The extension
".progname" will be appended (e.g. log.smbclient,
log.smbd, etc...). The log file is never removed by the client.
'>
-R|--name-resolve <name resolve order>
This option is used to determine what naming
services and in what order to resolve
host names to IP addresses. The option takes a space-separated
string of different name resolution options.
The options are: "lmhosts", "host", "wins" and "bcast".
They cause names to be resolved as follows :
lmhosts:
Lookup an IP address in the Samba lmhosts file. If the
line in lmhosts has no name type attached to the
NetBIOS name
(see the lmhosts
5 for details)
then any name type matches for lookup.
host:
Do a standard host name to IP address resolution, using
the system /etc/hosts, NIS, or DNS
lookups. This method of name resolution is operating
system dependent, for instance on IRIX or Solaris this
may be controlled by the /etc/nsswitch.conf
file). Note that this method is only used
if the NetBIOS name type being queried is the 0x20
(server) name type, otherwise it is ignored.
wins:
Query a name with the IP address listed in the
wins server parameter. If no
WINS server has been specified this method will be
ignored.
bcast:
Do a broadcast on each of the known local interfaces
listed in the interfaces
parameter. This is the least reliable of the name
resolution methods as it depends on the target host
being on a locally connected subnet.
If this parameter is not set then the name resolve order
defined in the &smb.conf; file parameter
(name resolve order) will be used.
The default order is lmhosts, host, wins, bcast. Without
this parameter or any entry in the name resolve order parameter of the &smb.conf; file, the name
resolution methods will be attempted in this order.
'>
-n|--netbiosname <primary NetBIOS name>
This option allows you to override
the NetBIOS name that Samba uses for itself. This is identical
to setting the netbios name parameter in the &smb.conf; file.
However, a command
line setting will take precedence over settings in
&smb.conf;.
'>
-i|--scope <scope>
This specifies a NetBIOS scope that
nmblookup will use to communicate with when
generating NetBIOS names. For details on the use of NetBIOS
scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
very rarely used, only set this parameter
if you are the system administrator in charge of all the
NetBIOS systems you communicate with.
'>
-W|--workgroup=domain
Set the SMB domain of the username. This
overrides the default domain which is the domain defined in
smb.conf. If the domain specified is the same as the servers
NetBIOS name, it causes the client to log on using the servers local
SAM (as opposed to the Domain SAM).
'>
-O|--socket-options socket options
TCP socket options to set on the client
socket. See the socket options parameter in
the &smb.conf; manual page for the list of valid
options.
'>
-N|--no-pass
If specified, this parameter suppresses the normal
password prompt from the client to the user. This is useful when
accessing a service that does not require a password.
Unless a password is specified on the command line or
this parameter is specified, the client will request a
password.
If a password is specified on the command line and this
option is also defined the password on the command line will
be silently ingnored and no password will be used.
'>
-U|--user=username[&pct;password]
Sets the SMB username or username and password.
If &pct;password is not specified, the user will be prompted. The
client will first check the USER environment variable, then the
LOGNAME variable and if either exists, the
string is uppercased. If these environmental variables are not
found, the username GUEST is used.
A third option is to use a credentials file which
contains the plaintext of the username and password. This
option is mainly provided for scripts where the admin does not
wish to pass the credentials on the command line or via environment
variables. If this method is used, make certain that the permissions
on the file restrict access from unwanted users. See the
-A for more details.
Be cautious about including passwords in scripts. Also, on
many systems the command line of a running process may be seen
via the ps command. To be safe always allow
rpcclient to prompt for a password and type
it in directly.
'>
-A|--authentication-file=filename
This option allows
you to specify a file from which to read the username and
password used in the connection. The format of the file is
username = <value>
password = <value>
domain = <value>
Make certain that the permissions on the file restrict
access from unwanted users.
'>
-k|--kerberos
Try to authenticate with kerberos. Only useful in
an Active Directory environment.
'>
-C|--use-ccache
Try to use the credentials cached by winbind.
'>
-h|--help
Print a summary of command line options.
'>
OpenLDAP'>
smbd'>
nmbd'>
testparm'>
smb.conf'>
smbclient'>
winbindd'>
net'>
Currently NOT implemented.">
root# ">
$ ">
C:\> ">
">