Note: If MS Outlook has been configured to use an IMAP account configuration there may be problems
following these instructions. Feedback from users suggests that where IMAP is used the PST
file is used to store rules and filters. When the PST store is relocated it appears to break
- MS Outlook's Send/Receive button. If anyone has sucessfully relocated PST files where IMAP is
+ MS Outlook's Send/Receive button. If anyone has successfully relocated PST files where IMAP is
used please email <literal>jht@samba.org</literal> with useful tips and suggestions so that
this warning can be removed or modified.
</para></step>
Samba currently supports up to the "NT LM 0.12" protocol, which is the
one preferred by Win95 and WinNT3.5. Luckily this protocol level has a
"capabilities" field which specifies which super-duper new-fangled
-options the server suports. This helps to make the implementation of
+options the server supports. This helps to make the implementation of
this protocol level much easier.
</para>
<para>
<indexterm><primary>tdb</primary></indexterm>
-<indexterm><primary>currupted</primary></indexterm>
+<indexterm><primary>corrupted</primary></indexterm>
<indexterm><primary>backup</primary></indexterm>
<indexterm><primary>restore</primary></indexterm>
Those who package Samba for commercial distribution with operating systems and appliances would do well to take
lru file entry lifetime = 5
; exclude files from being scanned based on the MIME-type! Semi-colon
-; seperated list (default: empty list). Use this with care!
+; separated list (default: empty list). Use this with care!
exclude file types =
; socket name of clamd (default: /var/run/clamd). Setting will be ignored if
<title>DESCRIPTION</title>
<para>The idmap_nss plugin provides a means to map Unix users and groups
- to Windows accounts and obseletes the "winbind trusted domains only"
+ to Windows accounts and obsoletes the "winbind trusted domains only"
smb.conf option. This provides a simple means of ensuring that the SID
for a Unix user named jsmith is reported as the one assigned to
DOMAIN\jsmith which is necessary for reporting ACLs on files and printers
responsibility of the application that calls this library to set this to a sensible value. This
is a compile-time option. This value determines the maximum number of local master browsers to
query for the list of workgroups. In order to ensure that the list is complete for those present
- on the network, all master browsers must be querried. If there are a large number of workgroups
+ on the network, all master browsers must be queried. If there are a large number of workgroups
on the network, the time spent querying will be significant. For small networks (just a few
workgroups), it is suggested to set this value to 0, instructing libsmbclient to query all local
master browsers. In an environment that has many workgroups a more reasonable setting may be around 3.
<listitem><para><replaceable>DOMAIN</replaceable> can be a NetBIOS domain name (also known as short domain name) or a DNS domain name for Active Directory Domains. As in Windows, it is also possible to control which Domain Controller to use. This can be achieved by appending the DC name using the \ separator character. Example: MYDOM\MYDC. The <replaceable>DOMAIN</replaceable> parameter cannot be NULL.</para></listitem>
-<listitem><para><replaceable>OU</replaceable> can be set to a RFC 1779 LDAP DN, like <emphasis>ou=mymachines,cn=Users,dc=example,dc=com</emphasis> in order to create the machine account in a non-default LDAP containter. This optional parameter is only supported when joining Active Directory Domains.</para></listitem>
+<listitem><para><replaceable>OU</replaceable> can be set to a RFC 1779 LDAP DN, like <emphasis>ou=mymachines,cn=Users,dc=example,dc=com</emphasis> in order to create the machine account in a non-default LDAP container. This optional parameter is only supported when joining Active Directory Domains.</para></listitem>
<listitem><para><replaceable>ACCOUNT</replaceable> defines a domain account that will be used to join the machine to the domain. This domain account needs to have sufficient privileges to join machines.</para></listitem>
MSCHAPv2) generated in some way by both the server and
the client.
</para>
- <para><example>LANMAN-Challege: 0102030405060708</example></para>
+ <para><example>LANMAN-Challenge: 0102030405060708</example></para>
</listitem></varlistentry>
<varlistentry>
<varlistentry>
<term>Request-User-Session-Key</term>
- <listitem><para>Apon sucessful authenticaiton, return
+ <listitem><para>Upon successful authenticaiton, return
the user session key associated with the login.
</para>
<para><example>Request-User-Session-Key: Yes</example></para>
<varlistentry>
<term>Request-LanMan-Session-Key</term>
- <listitem><para>Apon sucessful authenticaiton, return
+ <listitem><para>Upon successful authenticaiton, return
the LANMAN session key associated with the login.
</para>
<para><example>Request-LanMan-Session-Key: Yes</example></para>
</listitem></varlistentry>
- <para><warning>Implementors should take care to base64 encode
+ <para><warning>Implementers should take care to base64 encode
any data (such as usernames/passwords) that may contain malicous user data, such as
a newline. They may also need to decode strings from
the helper, which likewise may have been base64 encoded.</warning></para>
<varlistentry>
<term>--request-lm-key</term>
- <listitem><para>Retreive LM session key</para></listitem>
+ <listitem><para>Retrieve LM session key</para></listitem>
</varlistentry>
<varlistentry>
<title>TROUBLESHOOTING</title>
<para>If you're experiencing problems with authenticating Internet Explorer running
- under MS Windows 9X or Millenium Edition against ntlm_auth's NTLMSSP authentication
+ under MS Windows 9X or Millennium Edition against ntlm_auth's NTLMSSP authentication
helper (--helper-protocol=squid-2.5-ntlmssp), then please read
<ulink url="http://support.microsoft.com/support/kb/articles/Q239/8/69.ASP">
the Microsoft Knowledge Base article #239869 and follow instructions described there</ulink>.
without changing the tool).</para>
<para>There are five main ways to use pdbedit: adding a user account,
- removing a user account, modifing a user account, listing user
+ removing a user account, modifying a user account, listing user
accounts, importing users accounts.</para>
</refsect1>
<varlistentry>
<term>-f|--fullname fullname</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will specify the user's full
+ modifying a user account. It will specify the user's full
name. </para>
<para>Example: <command>-f "Simo Sorce"</command></para>
<varlistentry>
<term>-h|--homedir homedir</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will specify the user's home
+ modifying a user account. It will specify the user's home
directory network path.</para>
<para>Example: <command>-h "\\\\BERSERKER\\sorce"</command>
<varlistentry>
<term>-D|--drive drive</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will specify the windows drive
+ modifying a user account. It will specify the windows drive
letter to be used to map the home directory.</para>
<para>Example: <command>-D "H:"</command>
<varlistentry>
<term>-S|--script script</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will specify the user's logon
+ modifying a user account. It will specify the user's logon
script path.</para>
<para>Example: <command>-S "\\\\BERSERKER\\netlogon\\sorce.bat"</command>
<varlistentry>
<term>-p|--profile profile</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will specify the user's profile
+ modifying a user account. It will specify the user's profile
directory.</para>
<para>Example: <command>-p "\\\\BERSERKER\\netlogon"</command>
<varlistentry>
<term>-N|--account-desc description</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will specify the user's description
+ modifying a user account. It will specify the user's description
field.</para>
<para>Example: <command>-N "test description"</command>
<varlistentry>
<term>-Z|--logon-hours-reset</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will reset the user's allowed logon
+ modifying a user account. It will reset the user's allowed logon
hours. A user may login at any time afterwards.</para>
<para>Example: <command>-Z</command>
<varlistentry>
<term>-z|--bad-password-count-reset</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will reset the stored bad login
+ modifying a user account. It will reset the stored bad login
counter from a specified user.</para>
<para>Example: <command>-z</command>
<varlistentry>
<term>-I|--domain</term>
<listitem><para>This option can be used while adding or
- modifing a user account. It will specify the user's domain field.</para>
+ modifying a user account. It will specify the user's domain field.</para>
<para>Example: <command>-I "MYDOMAIN"</command>
</para>
server support the UNIX extensions. Request that the connection be
encrypted. This is new for Samba 3.2 and will only work with Samba
3.2 or above servers. Negotiates SMB encryption using GSSAPI. Uses
- the given credentials for the encryption negotiaion (either kerberos
+ the given credentials for the encryption negotiation (either kerberos
or NTLMv1/v2 if given domain/username/password triple. Fails the
connection if encryption cannot be negotiated.
</para></listitem>
<para>Restore from tar file <filename>backup.tar</filename> into myshare on mypc
(no password on share). </para>
- <para><command>smbclient //mypc/yshare "" -N -Tx backup.tar
+ <para><command>smbclient //mypc/myshare "" -N -Tx backup.tar
</command></para>
<para>Restore everything except <filename>users/docs</filename>
<varlistentry>
<term>du <filename></term>
- <listitem><para>Does a directory listing and then prints out the current disk useage and free space on a share.
+ <listitem><para>Does a directory listing and then prints out the current disk usage and free space on a share.
</para></listitem>
</varlistentry>
<para>
Note that this message only sends notification that an
- event has occured. It doesn't actually cause the
+ event has occurred. It doesn't actually cause the
event to happen.
</para>
<refsect1>
- <title>QUOTA_SET_COMAND</title>
+ <title>QUOTA_SET_COMMAND</title>
<para>The format of an the QUOTA_SET_COMMAND is an operation
name followed by a set of parameters specific to that operation.
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 <smbconfoption name="obey pam restrictions"/> <citerefentry><refentrytitle>smb.conf</refentrytitle>
- <manvolnum>5</manvolnum></citerefentry> paramater. When this is set, the following restrictions apply:
+ <manvolnum>5</manvolnum></citerefentry> parameter. When this is set, the following restrictions apply:
</para>
<itemizedlist>
<listitem><para><emphasis>Account Validation</emphasis>: All accesses to a
samba server are checked
- against PAM to see if the account is vaild, not disabled and is permitted to
+ against PAM to see if the account is valid, not disabled and is permitted to
login at this time. This also applies to encrypted logins.
</para></listitem>
<listitem><para><emphasis>Session Management</emphasis>: 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.
+ level security, users must pass PAM's session checks before access
+ is granted. Note however, that this is bypassed in share level security.
Note also that some older pam configuration files may need a line
added for session support.
</para></listitem>
<varlistentry>
<term>-s suffix</term>
<listitem><para>
- The <command>-s</command> option allows the adminisistrator to specify a file
+ The <command>-s</command> option allows the administrator to specify a file
backup extension. This way it is possible to keep a history of tdb backup
files by using a new suffix for each backup.
</para> </listitem>
<varlistentry>
<term>-v</term>
<listitem><para>
- The <command>-v</command> will check the database for damages (currupt data)
+ The <command>-v</command> will check the database for damages (corrupt data)
which if detected causes the backup to be restored.
</para></listitem>
</varlistentry>
Dumps the named parameter. If no section-name is set the view
is limited by default to the global section.
- It is also possible to dump a parametrical option. Therfore
+ It is also possible to dump a parametrical option. Therefore
the option has to be separated by a colon from the
parametername.
</para></listitem>
<para>The <command>vfs_readonly</command> VFS module marks a share
as read only for all clients connecting within the configured
time period. Clients connecting during this time will be denied
- write access to all files in the share, irrespective of ther
+ write access to all files in the share, irrespective of their
actual access privileges.</para>
<para>This module is stackable.</para>
<programlisting>
<smbconfsection name="[homes]"/>
<smbconfoption name="vfs objects">shadow_copy2</smbconfoption>
- <smbconfoption name="shadow:snapdir">/data/snaphots</smbconfoption>
+ <smbconfoption name="shadow:snapdir">/data/snapshots</smbconfoption>
<smbconfoption name="shadow:basedir">/data/home</smbconfoption>
<smbconfoption name="shadow:sort">desc</smbconfoption>
</programlisting>
</simplelist>
<para><command>vfs_smb_traffic_analyzer</command> sends the following data
- in a fixed format seperated by a comma through either an internet or a
+ in a fixed format separated by a comma through either an internet or a
unix domain socket:</para>
<programlisting>
BYTES|USER|DOMAIN|READ/WRITE|SHARE|FILENAME|TIMESTAMP
<listitem><para><command>USER</command> - the user who initiated the operation</para></listitem>
<listitem><para><command>DOMAIN</command> - the domain of the user</para></listitem>
<listitem><para><command>READ/WRITE</command> - either "W" for a write operation or "R" for read</para></listitem>
- <listitem><para><command>SHARE</command> - the name of the share on which the VFS operation occured</para></listitem>
+ <listitem><para><command>SHARE</command> - the name of the share on which the VFS operation occurred</para></listitem>
<listitem><para><command>FILENAME</command> - the name of the file that was used by the VFS operation</para></listitem>
- <listitem><para><command>TIMESTAMP</command> - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occured</para></listitem>
+ <listitem><para><command>TIMESTAMP</command> - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occurred</para></listitem>
<listitem><para><command>IP</command> - The IP Address (v4 or v6) of the client machine that initiated the VFS operation.</para></listitem>
</itemizedlist>
to speed up case insensitive name mappings. It represents
the number of kilobyte (1024) units the stat cache can use.
A value of zero, meaning unlimited, is not advisable due to
- increased memory useage. You should not need to change this
+ increased memory usage. You should not need to change this
parameter.
</para>
</description>
<para>A common problem with Samba printer configuration is forgetting to use the full <indexterm id="ch07-idx-956511-0"><primary>pathnames</primary><secondary>printer configuration and</secondary></indexterm>
-<indexterm id="ch07-idx-956511-1"><primary>printing</primary><secondary>pathnames used in comands for</secondary></indexterm>pathnames for commands; simple commands often don't work because the guest account's PATH doesn't include them. Another frequent problem is not having the correct <indexterm id="ch07-idx-956512-0"><primary>permissions</primary><secondary sortas="printing">for printing</secondary></indexterm>
+<indexterm id="ch07-idx-956511-1"><primary>printing</primary><secondary>pathnames used in com
mands for</secondary></indexterm>pathnames for commands; simple commands often don't work because the guest account's PATH doesn't include them. Another frequent problem is not having the correct <indexterm id="ch07-idx-956512-0"><primary>permissions</primary><secondary sortas="printing">for printing</secondary></indexterm>
<indexterm id="ch07-idx-956512-1"><primary>printing</primary><secondary>permissions for</secondary></indexterm>permissions on the spooling directory.<indexterm id="ch07-idx-956494-0" class="endofrange" startref="ch07-idx-956450-0"/></para>
git.samba.org / ddiss / samba.git / commitdiff