sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-24 21:34:56 +03:00
Code

Regenerate docs

Browse Source
This commit is contained in:
Jelmer Vernooij 0001-01-01 00:00:00 +00:00
parent c442e52488
commit b78c6ee1d1
18 changed files with 2434 additions and 2410 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/Samba-HOWTO-Collection.pdf
View File

Binary file not shown.

17
docs/faq/FAQ-ClientApp.html
View File

@ -1,5 +1,4 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter 2. Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-errors.html" title="Chapter 4. Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter 3. Specific client application problems</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2816576">MS Office Setup reports &quot;Cannot change properties of '\\MSOFFICE\\SETUP.INI'&quot;</a></dt><dt><a href="FAQ-ClientApp.html#id2815108">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2816253">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816576"></a>MS Office Setup reports &quot;Cannot change properties of '\\MSOFFICE\\SETUP.INI'&quot;</h2></div></div><div></div></div><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter 2. Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-errors.html" title="Chapter 4. Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter 3. Specific client application problems</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2868727">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2815168">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2874026">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868727"></a>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</h2></div></div><div></div></div><p>
When installing MS Office on a Samba drive for which you have admin
user permissions, ie. admin users = username, you will find the
setup program unable to complete the installation.
@ -9,9 +8,9 @@ permissions The problem is that MS Office Setup checks that a file is
rdonly by trying to open it for writing.
</p><p>
Admin users can always open a file for writing, as they run as root.
You just have to install as a non-admin user and then use &quot;chown -R&quot;
You just have to install as a non-admin user and then use "chown -R"
to fix the owner.
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815108"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><div></div></div><p>
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815168"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><div></div></div><p>
Microsoft Office products can be installed as an administrative installation
from which the application can either be run off the administratively installed
product that resides on a shared resource, or from which that product can be
@ -37,7 +36,7 @@ set the following parameters on the share containing it:
[MSOP95]
path = /where_you_put_it
comment = Your comment
volume = &quot;The_CD_ROM_Label&quot;
volume = "The_CD_ROM_Label"
read only = yes
available = yes
share modes = no
@ -45,8 +44,8 @@ set the following parameters on the share containing it:
browseable = yes
public = yes
</pre></li><li><p>Now you are ready to run the setup program from the Microsoft Windows
workstation as follows: <b class="command">\\&quot;Server_Name&quot;\MSOP95\msoffice\setup</b>
</p></li></ul></div></div><div xmlns:ns3="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816253"></a>Microsoft Access database opening errors</h2></div></div><div></div></div><p>
workstation as follows: <b class="command">\\"Server_Name"\MSOP95\msoffice\setup</b>
</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874026"></a>Microsoft Access database opening errors</h2></div></div><div></div></div><p>
Here are some notes on running MS-Access on a Samba drive from <a href="stefank@esi.com.au" target="_top">Stefan Kjellberg</a>
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</td></tr><tr><td>Make sure that you open the database as 'shared' and to 'lock modified records'</td></tr><tr><td>Of course locking must be enabled for the particular share (smb.conf)</td></tr></table><ns3:p>
</ns3:p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Compiling and installing Samba on a Unix host </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Common errors</td></tr></table></div></body></html>
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</td></tr><tr><td>Make sure that you open the database as 'shared' and to 'lock modified records'</td></tr><tr><td>Of course locking must be enabled for the particular share (smb.conf)</td></tr></table><p>
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Compiling and installing Samba on a Unix host </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Common errors</td></tr></table></div></body></html>

23
docs/faq/FAQ-Install.html
View File

@ -1,5 +1,4 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2. Compiling and installing Samba on a Unix host</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-general.html" title="Chapter 1. General Information"><link rel="next" href="FAQ-ClientApp.html" title="Chapter 3. Specific client application problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Compiling and installing Samba on a Unix host</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-Install"></a>Chapter 2. Compiling and installing Samba on a Unix host</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Install.html#id2816194">My client reports &quot;cannot locate specified share name&quot; or similar</a></dt><dt><a href="FAQ-Install.html#id2816881">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816194"></a>My client reports &quot;cannot locate specified share name&quot; or similar</h2></div></div><div></div></div><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2. Compiling and installing Samba on a Unix host</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-general.html" title="Chapter 1. General Information"><link rel="next" href="FAQ-ClientApp.html" title="Chapter 3. Specific client application problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Compiling and installing Samba on a Unix host</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-Install"></a>Chapter 2. Compiling and installing Samba on a Unix host</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Install.html#id2868750">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2818341">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868750"></a>My client reports "cannot locate specified share name" or similar</h2></div></div><div></div></div><p>
This message indicates that your client CAN locate the specified
server, which is a good start, but that it cannot find a service of
the name you gave.
@ -8,7 +7,7 @@ The first step is to check the exact name of the service you are
trying to connect to (consult your system administrator). Assuming it
exists and you specified it correctly (read your client's docs on how
to specify a service name correctly), read on:
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Many clients cannot accept or use service names longer than eight characters.</td></tr><tr><td>Many clients cannot accept or use service names containing spaces.</td></tr><tr><td>Some servers (not Samba though) are case sensitive with service names.</td></tr><tr><td>Some clients force service names into upper case.</td></tr></table></div><div xmlns:ns2="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816881"></a>Why are my file's timestamps off by an hour, or by a few hours?</h2></div></div><div></div></div><p>
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Many clients cannot accept or use service names longer than eight characters.</td></tr><tr><td>Many clients cannot accept or use service names containing spaces.</td></tr><tr><td>Some servers (not Samba though) are case sensitive with service names.</td></tr><tr><td>Some clients force service names into upper case.</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818341"></a>Why are my file's timestamps off by an hour, or by a few hours?</h2></div></div><div></div></div><p>
This is from Paul Eggert eggert@twinsun.com.
</p><p>
Most likely it's a problem with your time zone settings.
@ -16,12 +15,12 @@ Most likely it's a problem with your time zone settings.
Internally, Samba maintains time in traditional Unix format,
namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
(or ``GMT''), not counting leap seconds.
</p><ns2:p>
</p><p>
On the server side, Samba uses the Unix TZ variable to convert
internal timestamps to and from local time. So on the server side, there are
two things to get right.
</ns2:p><table class="simplelist" border="0" summary="Simple list"><tr><td>The Unix system clock must have the correct Universal time. Use the shell command &quot;sh -c 'TZ=UTC0 date'&quot; to check this.</td></tr><tr><td>The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.</td></tr></table><ns2:p>
</ns2:p><p>TZ must have the correct value.</p><p>
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</td></tr><tr><td>The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.</td></tr></table><p>
</p><p>TZ must have the correct value.</p><p>
If possible, use geographical time zone settings
(e.g. TZ='America/Los_Angeles' or perhaps
TZ=':US/Pacific'). These are supported by most
@ -30,16 +29,16 @@ more accurate for historical timestamps. If your
operating system has out-of-date tables, you should be
able to update them from the public domain time zone
tables at <a href="ftp://elsie.nci.nih.gov/pub/" target="_top">ftp://elsie.nci.nih.gov/pub/</a>.
</p><ns2:p>If your system does not support geographical timezone
</p><p>If your system does not support geographical timezone
settings, you must use a Posix-style TZ strings, e.g.
TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
Posix TZ strings can take the following form (with optional
items in brackets):
</ns2:p><pre class="programlisting">
</p><pre class="programlisting">
StdOffset[Dst[Offset],Date/Time,Date/Time]
</pre><ns2:p>
</pre><p>
where:
</ns2:p><table class="simplelist" border="0" summary="Simple list"><tr><td>`Std' is the standard time designation (e.g. `PST').</td></tr><tr><td>`Offset' is the number of hours behind UTC (e.g. `8').
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>`Std' is the standard time designation (e.g. `PST').</td></tr><tr><td>`Offset' is the number of hours behind UTC (e.g. `8').
Prepend a `-' if you are ahead of UTC, and
append `:30' if you are at a half-hour offset.
Omit all the remaining items if you do not use
@ -53,8 +52,8 @@ time starts and ends. The format for a date is
of the nth week of the mth month, where week 5 means
the last such day in the month. The format for a
time is [h]h[:mm[:ss]], using a 24-hour clock.
</td></tr></table><ns2:p>
</ns2:p><p>
</td></tr></table><p>
</p><p>
Other Posix string formats are allowed but you don't want
to know about them.</p><p>
On the client side, you must make sure that your client's clock and

29
docs/faq/FAQ-errors.html
View File

@ -1,35 +1,34 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Common errors</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-ClientApp.html" title="Chapter 3. Specific client application problems"><link rel="next" href="FAQ-features.html" title="Chapter 5. Features"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Common errors</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-ClientApp.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-features.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-errors"></a>Chapter 4. Common errors</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-errors.html#id2815002">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2816347">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2816385">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2816438">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></div><div xmlns:ns4="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815002"></a>Not listening for calling name</h2></div></div><div></div></div><ns4:p>
</ns4:p><pre class="programlisting">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Common errors</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-ClientApp.html" title="Chapter 3. Specific client application problems"><link rel="next" href="FAQ-features.html" title="Chapter 5. Features"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Common errors</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-ClientApp.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-features.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-errors"></a>Chapter 4. Common errors</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-errors.html#id2815122">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2874876">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2874916">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2874971">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815122"></a>Not listening for calling name</h2></div></div><div></div></div><p>
</p><pre class="programlisting">
Session request failed (131,129) with myname=HOBBES destname=CALVIN
Not listening for calling name
</pre><ns4:p>
</ns4:p><p>
</pre><p>
</p><p>
If you get this when talking to a Samba box then it means that your
global &quot;hosts allow&quot; or &quot;hosts deny&quot; settings are causing the Samba
global "hosts allow" or "hosts deny" settings are causing the Samba
server to refuse the connection.
</p><p>
Look carefully at your &quot;hosts allow&quot; and &quot;hosts deny&quot; lines in the
Look carefully at your "hosts allow" and "hosts deny" lines in the
global section of smb.conf.
</p><p>
It can also be a problem with reverse DNS lookups not functioning
correctly, leading to the remote host identity not being able to
be confirmed, but that is less likely.
</p></div><div xmlns:ns5="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816347"></a>System Error 1240</h2></div></div><div></div></div><p>
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874876"></a>System Error 1240</h2></div></div><div></div></div><p>
System error 1240 means that the client is refusing to talk
to a non-encrypting server. Microsoft changed WinNT in service
pack 3 to refuse to connect to servers that do not support
SMB password encryption.
</p><ns5:p>There are two main solutions:
</ns5:p><table class="simplelist" border="0" summary="Simple list"><tr><td>enable SMB password encryption in Samba. See the encryption part of
</p><p>There are two main solutions:
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>enable SMB password encryption in Samba. See the encryption part of
the samba HOWTO Collection</td></tr><tr><td>disable this behaviour in NT. See the section about
Windows NT in the chapter &quot;Portability&quot; of the samba HOWTO collection
</td></tr></table><ns5:p>
</ns5:p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816385"></a>smbclient ignores -N !</h2></div></div><div></div></div><p>
Windows NT in the chapter "Portability" of the samba HOWTO collection
</td></tr></table><p>
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874916"></a>smbclient ignores -N !</h2></div></div><div></div></div><p>
&#8220;<span class="quote">When getting the list of shares available on a host using the command
<b class="command">smbclient -N -L</b>
the program always prompts for the password if the server is a Samba server.
It also ignores the &quot;-N&quot; argument when querying some (but not all) of our
It also ignores the "-N" argument when querying some (but not all) of our
NT servers.
</span>&#8221;
</p><p>
@ -43,7 +42,7 @@ This will set both the username and password to null, which is
an anonymous login for SMB. Using -N would only set the password
to null, and this is not accepted as an anonymous login for most
SMB servers.
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816438"></a>The data on the CD-Drive I've shared seems to be corrupted!</h2></div></div><div></div></div><p>
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874971"></a>The data on the CD-Drive I've shared seems to be corrupted!</h2></div></div><div></div></div><p>
Some OSes (notably Linux) default to auto detection of file type on
cdroms and do cr/lf translation. This is a very bad idea when use with
Samba. It causes all sorts of stuff ups.

49
docs/faq/FAQ-features.html
View File

@ -1,41 +1,40 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 5. Features</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-errors.html" title="Chapter 4. Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-features"></a>Chapter 5. Features</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-features.html#id2816464">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2814278">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2814327">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2814420">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2814505">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2814704">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2814830">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2814877">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2814906">Does samba have wins replication support?</a></dt></dl></div><div xmlns:ns6="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816464"></a>How can I use samba as a fax server?</h2></div></div><div></div></div><p>Contributor: <a href="mailto:zuber@berlin.snafu.de" target="_top">Gerhard Zuber</a></p><ns6:p>Requirements:
</ns6:p><table class="simplelist" border="0" summary="Simple list"><tr><td>UNIX box (Linux preferred) with SAMBA and a faxmodem</td></tr><tr><td>ghostscript package</td></tr><tr><td>mgetty+sendfax package</td></tr><tr><td>pbm package (portable bitmap tools)</td></tr></table><ns6:p>
</ns6:p><p>First, install and configure the required packages. Be sure to read the mgetty+sendfax
manual carefully.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2814278"></a>Tools for printing faxes</h3></div></div><div></div></div><p>Your incomed faxes are in:
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 5. Features</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-errors.html" title="Chapter 4. Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-features"></a>Chapter 5. Features</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-features.html#id2875179">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874300">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2874353">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2874445">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2874838">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2814744">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2814866">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2883464">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2883493">Does samba have wins replication support?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875179"></a>How can I use samba as a fax server?</h2></div></div><div></div></div><p>Contributor: <a href="mailto:zuber@berlin.snafu.de" target="_top">Gerhard Zuber</a></p><p>Requirements:
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>UNIX box (Linux preferred) with SAMBA and a faxmodem</td></tr><tr><td>ghostscript package</td></tr><tr><td>mgetty+sendfax package</td></tr><tr><td>pbm package (portable bitmap tools)</td></tr></table><p>
</p><p>First, install and configure the required packages. Be sure to read the mgetty+sendfax
manual carefully.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874300"></a>Tools for printing faxes</h3></div></div><div></div></div><p>Your incomed faxes are in:
<tt class="filename">/var/spool/fax/incoming</tt>. Print it with:</p><pre class="programlisting">
for i in *
do
g3cat $i | g3tolj | lpr -P hp
done
</pre><ns6:p>
</ns6:p><p>
</pre><p>
</p><p>
g3cat is in the tools-section, g3tolj is in the contrib-section
for printing to HP lasers.
</p><p>
If you want to produce files for displaying and printing with Windows, use
some tools from the pbm-package like the following command: <b class="command">g3cat $i | g3topbm - | ppmtopcx - &gt;$i.pcx</b>
and view it with your favourite Windows tool (maybe paintbrush)
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2814327"></a>Making the fax-server</h3></div></div><div></div></div><p>fetch the file <tt class="filename">mgetty+sendfax/frontends/winword/faxfilter</tt> and place it in <tt class="filename">/usr/local/etc/mgetty+sendfax/</tt>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</p><p>prepare your faxspool file as mentioned in this file
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874353"></a>Making the fax-server</h3></div></div><div></div></div><p>fetch the file <tt class="filename">mgetty+sendfax/frontends/winword/faxfilter</tt> and place it in <tt class="filename">/usr/local/etc/mgetty+sendfax/</tt>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</p><p>prepare your faxspool file as mentioned in this file
edit fax/faxspool.in and reinstall or change the final
/usr/local/bin/faxspool too.
</p><pre class="programlisting">
if [ &quot;$user&quot; = &quot;root&quot; -o &quot;$user&quot; = &quot;fax&quot; -o \
&quot;$user&quot; = &quot;lp&quot; -o &quot;$user&quot; = &quot;daemon&quot; -o &quot;$user&quot; = &quot;bin&quot; ]
if [ "$user" = "root" -o "$user" = "fax" -o \
"$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
</pre><p>find the first line and change it to the second.</p><p>
make sure you have pbmtext (from the pbm-package). This is
needed for creating the small header line on each page.
</p><p>Prepare your faxheader <tt class="filename">/usr/local/etc/mgetty+sendfax/faxheader</tt></p><ns6:p>
</p><p>Prepare your faxheader <tt class="filename">/usr/local/etc/mgetty+sendfax/faxheader</tt></p><p>
Edit your /etc/printcap file:
</ns6:p><pre class="programlisting">
</p><pre class="programlisting">
# FAX
lp3|fax:\
:lp=/dev/null:\
:sd=/usr/spool/lp3:\
:if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
:lf=/usr/spool/lp3/fax-log:
</pre><p>Now, edit your <tt class="filename">smb.conf</tt> so you have a smb based printer named &quot;fax&quot;</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2814420"></a>Installing the client drivers</h3></div></div><div></div></div><p>
Now you have a printer called &quot;fax&quot; which can be used via
</pre><p>Now, edit your <tt class="filename">smb.conf</tt> so you have a smb based printer named "fax"</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874445"></a>Installing the client drivers</h3></div></div><div></div></div><p>
Now you have a printer called "fax" which can be used via
TCP/IP-printing (lpd-system) or via SAMBA (windows printing).
</p><p>
On every system you are able to produce postscript-files you
@ -45,7 +44,7 @@ On Windows 3.1 95 and NT:
</p><p>
Install a printer wich produces postscript output,
e.g. apple laserwriter
</p><p>Connect the &quot;fax&quot; to your printer.</p><p>
</p><p>Connect the "fax" to your printer.</p><p>
Now write your first fax. Use your favourite wordprocessor,
write, winword, notepad or whatever you want, and start
with the headerpage.
@ -55,17 +54,17 @@ your address, your phone/fax-number.
</p><p>
It carries also the recipient, his address and his *** fax
number ***. Now here is the trick:
</p><ns6:p>
</p><p>
Use the text:
</ns6:p><pre class="programlisting">
</p><pre class="programlisting">
Fax-Nr: 123456789
</pre><ns6:p>
</pre><p>
as the recipients fax-number. Make sure this text does not
occur in regular text ! Make sure this text is not broken
by formatting information, e.g. format it as a single entity.
(Windows Write and Win95 Wordpad are functional, maybe newer
versions of Winword are breaking formatting information).
</ns6:p><p>
</p><p>
The trick is that postscript output is human readable and
the faxfilter program scans the text for this pattern and
uses the found number as the fax-destination-number.
@ -73,7 +72,7 @@ uses the found number as the fax-destination-number.
Now print your fax through the fax-printer and it will be
queued for later transmission. Use faxrunq for sending the
queue out.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2814505"></a>Example smb.conf</h3></div></div><div></div></div><pre class="programlisting">
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874838"></a>Example smb.conf</h3></div></div><div></div></div><pre class="programlisting">
[global]
printcap name = /etc/printcap
print command = /usr/bin/lpr -r -P %p %s
@ -89,7 +88,7 @@ queue out.
create mode = 0700
browseable = yes
guest ok = no
</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814704"></a>Samba doesn't work well together with DHCP!</h2></div></div><div></div></div><p>
</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814744"></a>Samba doesn't work well together with DHCP!</h2></div></div><div></div></div><p>
We wish to help those folks who wish to use the ISC DHCP Server and provide
sample configuration settings. Most operating systems today come ship with
the ISC DHCP Server. ISC DHCP is available from:
@ -142,14 +141,14 @@ applied to the resulting DHCP offered settings UNLESS the DHCP server also sets
a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS
Scope from your DHCP server. The can be done in the dhcpd.conf file with the
parameter:
<b class="command">option netbios-scope &quot;&quot;;</b>
<b class="command">option netbios-scope "";</b>
</p><p>
While it is true that the Microsoft DHCP server that comes with Windows NT
Server provides only a sub-set of rfc1533 functionality this is hardly an issue
in those sites that already have a large investment and commitment to Unix
systems and technologies. The current state of the art of the DHCP Server
specification in covered in rfc2132.
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814830"></a>How can I assign NetBIOS names to clients with DHCP?</h2></div></div><div></div></div><p>
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814866"></a>How can I assign NetBIOS names to clients with DHCP?</h2></div></div><div></div></div><p>
SMB network clients need to be configured so that all standard TCP/IP name to
address resolution works correctly. Once this has been achieved the SMB
environment provides additional tools and services that act as helper agents in
@ -164,13 +163,13 @@ This can be done, but needs a few NT registry hacks and you need to be able to
speak UNICODE, which is of course no problem for a True Wizzard(tm) :)
Instructions on how to do this (including a small util for less capable
Wizzards) can be found at
</p><p><a href="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html" target="_top">http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</a></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814877"></a>How do I convert between unix and dos text formats?</h2></div></div><div></div></div><p>
</p><p><a href="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html" target="_top">http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</a></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883464"></a>How do I convert between unix and dos text formats?</h2></div></div><div></div></div><p>
Jim barry has written an <a href="ftp://samba.org/pub/samba/contributed/fixcrlf.zip" target="_top">
excellent drag-and-drop cr/lf converter for
windows</a>. Just drag your file onto the icon and it converts the file.
</p><p>
The utilities unix2dos and dos2unix(in the mtools package) should do
the job under unix.
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814906"></a>Does samba have wins replication support?</h2></div></div><div></div></div><p>
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883493"></a>Does samba have wins replication support?</h2></div></div><div></div></div><p>
At the time of writing there is currently being worked on a wins replication implementation(wrepld).
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Common errors </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>

27
docs/faq/FAQ-general.html
View File

@ -1,30 +1,29 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1. General Information</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-Install.html" title="Chapter 2. Compiling and installing Samba on a Unix host"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. General Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-Install.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-general"></a>Chapter 1. General Information</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-general.html#id2815526">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2815894">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2816167">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></div><div xmlns:ns1="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815526"></a>What do the version numbers mean?</h2></div></div><div></div></div><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1. General Information</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-Install.html" title="Chapter 2. Compiling and installing Samba on a Unix host"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. General Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-Install.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-general"></a>Chapter 1. General Information</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-general.html#id2882842">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2883252">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2868767">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882842"></a>What do the version numbers mean?</h2></div></div><div></div></div><p>
It is not recommended that you run a version of Samba with the word
&quot;alpha&quot; in its name unless you know what you are doing and are willing
"alpha" in its name unless you know what you are doing and are willing
to do some debugging. Many, many people just get the latest
recommended stable release version and are happy. If you are brave, by
all means take the plunge and help with the testing and development -
but don't install it on your departmental server. Samba is typically
very stable and safe, and this is mostly due to the policy of many
public releases.
</p><ns1:p>
</p><p>
How the scheme works:
</ns1:p><table class="simplelist" border="0" summary="Simple list"><tr><td>When major changes are made the version number is increased. For
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>When major changes are made the version number is increased. For
example, the transition from 1.9.15 to 1.9.16. However, this version
number will not appear immediately and people should continue to use
1.9.15 for production systems (see next point.)</td></tr><tr><td>Just after major changes are made the software is considered
unstable, and a series of alpha releases are distributed, for example
1.9.16alpha1. These are for testing by those who know what they are
doing. The &quot;alpha&quot; in the filename will hopefully scare off those who
doing. The "alpha" in the filename will hopefully scare off those who
are just looking for the latest version to install.</td></tr><tr><td>When the release manager, currently Jerry, thinks that the alphas have stabilised to the point
where he would recommend new users install it, he renames it to the
same version number without the alpha, for example 1.9.16.</td></tr><tr><td>Inevitably bugs are found in the &quot;stable&quot; releases and minor patch
levels are released which give us the pXX series, for example 1.9.16p2.</td></tr></table><ns1:p>
</ns1:p><ns1:p>
same version number without the alpha, for example 1.9.16.</td></tr><tr><td>Inevitably bugs are found in the "stable" releases and minor patch
levels are released which give us the pXX series, for example 1.9.16p2.</td></tr></table><p>
</p><p>
So the progression goes:
</ns1:p><pre class="programlisting">
</p><pre class="programlisting">
1.9.15p7 (production)
1.9.15p8 (production)
1.9.16alpha1 (test sites only)
@ -32,17 +31,17 @@ So the progression goes:
1.9.16alpha20 (test sites only)
1.9.16 (production)
1.9.16p1 (production)
</pre><ns1:p>
</ns1:p><p>
</pre><p>
</p><p>
The above system means that whenever someone looks at the samba ftp
site they will be able to grab the highest numbered release without an
alpha in the name and be sure of getting the current recommended
version.
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815894"></a>What platforms are supported?</h2></div></div><div></div></div><p>
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883252"></a>What platforms are supported?</h2></div></div><div></div></div><p>
Many different platforms have run Samba successfully. The platforms
most widely used and thus best tested are Linux and SunOS.</p><p>
At time of writing, there is support (or has been support for in earlier
versions):
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A/UX 3.0</td></tr><tr><td>AIX</td></tr><tr><td>Altos Series 386/1000</td></tr><tr><td>Amiga</td></tr><tr><td>Apollo Domain/OS sr10.3</td></tr><tr><td>BSDI </td></tr><tr><td>B.O.S. (Bull Operating System)</td></tr><tr><td>Cray, Unicos 8.0</td></tr><tr><td>Convex</td></tr><tr><td>DGUX. </td></tr><tr><td>DNIX.</td></tr><tr><td>FreeBSD</td></tr><tr><td>HP-UX</td></tr><tr><td>Intergraph. </td></tr><tr><td>Linux with/without shadow passwords and quota</td></tr><tr><td>LYNX 2.3.0</td></tr><tr><td>MachTen (a unix like system for Macintoshes)</td></tr><tr><td>Motorola 88xxx/9xx range of machines</td></tr><tr><td>NetBSD</td></tr><tr><td>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</td></tr><tr><td>OS/2 using EMX 0.9b</td></tr><tr><td>OSF1</td></tr><tr><td>QNX 4.22</td></tr><tr><td>RiscIX. </td></tr><tr><td>RISCOs 5.0B</td></tr><tr><td>SEQUENT. </td></tr><tr><td>SCO (including: 3.2v2, European dist., OpenServer 5)</td></tr><tr><td>SGI.</td></tr><tr><td>SMP_DC.OSx v1.1-94c079 on Pyramid S series</td></tr><tr><td>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</td></tr><tr><td>SUNOS 4</td></tr><tr><td>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</td></tr><tr><td>Sunsoft ISC SVR3V4</td></tr><tr><td>SVR4</td></tr><tr><td>System V with some berkely extensions (Motorola 88k R32V3.2).</td></tr><tr><td>ULTRIX.</td></tr><tr><td>UNIXWARE</td></tr><tr><td>UXP/DS</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816167"></a>How do I subscribe to the Samba Mailing Lists?</h2></div></div><div></div></div><p>
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A/UX 3.0</td></tr><tr><td>AIX</td></tr><tr><td>Altos Series 386/1000</td></tr><tr><td>Amiga</td></tr><tr><td>Apollo Domain/OS sr10.3</td></tr><tr><td>BSDI </td></tr><tr><td>B.O.S. (Bull Operating System)</td></tr><tr><td>Cray, Unicos 8.0</td></tr><tr><td>Convex</td></tr><tr><td>DGUX. </td></tr><tr><td>DNIX.</td></tr><tr><td>FreeBSD</td></tr><tr><td>HP-UX</td></tr><tr><td>Intergraph. </td></tr><tr><td>Linux with/without shadow passwords and quota</td></tr><tr><td>LYNX 2.3.0</td></tr><tr><td>MachTen (a unix like system for Macintoshes)</td></tr><tr><td>Motorola 88xxx/9xx range of machines</td></tr><tr><td>NetBSD</td></tr><tr><td>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</td></tr><tr><td>OS/2 using EMX 0.9b</td></tr><tr><td>OSF1</td></tr><tr><td>QNX 4.22</td></tr><tr><td>RiscIX. </td></tr><tr><td>RISCOs 5.0B</td></tr><tr><td>SEQUENT. </td></tr><tr><td>SCO (including: 3.2v2, European dist., OpenServer 5)</td></tr><tr><td>SGI.</td></tr><tr><td>SMP_DC.OSx v1.1-94c079 on Pyramid S series</td></tr><tr><td>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</td></tr><tr><td>SUNOS 4</td></tr><tr><td>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</td></tr><tr><td>Sunsoft ISC SVR3V4</td></tr><tr><td>SVR4</td></tr><tr><td>System V with some berkely extensions (Motorola 88k R32V3.2).</td></tr><tr><td>ULTRIX.</td></tr><tr><td>UNIXWARE</td></tr><tr><td>UXP/DS</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868767"></a>How do I subscribe to the Samba Mailing Lists?</h2></div></div><div></div></div><p>
Look at <a href="http://samba.org/samba/archives.html" target="_top">the samba mailing list page</a>
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-Install.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Samba FAQ </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Compiling and installing Samba on a Unix host</td></tr></table></div></body></html>

4
docs/faq/samba-faq.html
View File

@ -1,4 +1,4 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Samba FAQ</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-general.html" title="Chapter 1. General Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Samba FAQ</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-general.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-FAQ"></a>Samba FAQ</h1></div><div><div class="author"><h3 class="author"><span class="surname">Samba Team</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div><hr></div><div class="dedication" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2882410"></a>Dedication</h2></div></div><div></div></div><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Samba FAQ</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-general.html" title="Chapter 1. General Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Samba FAQ</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-general.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-FAQ"></a>Samba FAQ</h1></div><div><div class="author"><h3 class="author"><span class="surname">Samba Team</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div><hr></div><div class="dedication" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2882190"></a>Dedication</h2></div></div><div></div></div><p>
This is the Frequently Asked Questions (FAQ) document for
Samba, the free and very popular SMB server product. An SMB server
allows file and printer connections from clients such as Windows,
@ -7,4 +7,4 @@ corrections to the samba documentation mailinglist at
<a href="mailto:samba-doc@samba.org" target="_top">samba-doc@samba.org</a>.
This FAQ was based on the old Samba FAQ by Dan Shearer and Paul Blackman,
and the old samba text documents which were mostly written by John Terpstra.
</p></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="FAQ-general.html">General Information</a></dt><dd><dl><dt><a href="FAQ-general.html#id2868480">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2814037">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2814530">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></dd><dt>2. <a href="FAQ-Install.html">Compiling and installing Samba on a Unix host</a></dt><dd><dl><dt><a href="FAQ-Install.html#id2815348">My client reports &quot;cannot locate specified share name&quot; or similar</a></dt><dt><a href="FAQ-Install.html#id2815254">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></dd><dt>3. <a href="FAQ-ClientApp.html">Specific client application problems</a></dt><dd><dl><dt><a href="FAQ-ClientApp.html#id2817040">MS Office Setup reports &quot;Cannot change properties of '\\MSOFFICE\\SETUP.INI'&quot;</a></dt><dt><a href="FAQ-ClientApp.html#id2817072">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2882489">Microsoft Access database opening errors</a></dt></dl></dd><dt>4. <a href="FAQ-errors.html">Common errors</a></dt><dd><dl><dt><a href="FAQ-errors.html#id2817005">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2816337">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2816376">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2816431">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></dd><dt>5. <a href="FAQ-features.html">Features</a></dt><dd><dl><dt><a href="FAQ-features.html#id2816716">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2816664">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2883185">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2883278">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2883362">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2883387">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2883513">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2883561">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2883589">Does samba have wins replication support?</a></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="FAQ-general.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. General Information</td></tr></table></div></body></html>
</p></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="FAQ-general.html">General Information</a></dt><dd><dl><dt><a href="FAQ-general.html#id2882842">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2883252">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2868767">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></dd><dt>2. <a href="FAQ-Install.html">Compiling and installing Samba on a Unix host</a></dt><dd><dl><dt><a href="FAQ-Install.html#id2868750">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2818341">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></dd><dt>3. <a href="FAQ-ClientApp.html">Specific client application problems</a></dt><dd><dl><dt><a href="FAQ-ClientApp.html#id2868727">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2815168">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2874026">Microsoft Access database opening errors</a></dt></dl></dd><dt>4. <a href="FAQ-errors.html">Common errors</a></dt><dd><dl><dt><a href="FAQ-errors.html#id2815122">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2874876">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2874916">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2874971">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></dd><dt>5. <a href="FAQ-features.html">Features</a></dt><dd><dl><dt><a href="FAQ-features.html#id2875179">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874300">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2874353">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2874445">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2874838">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2814744">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2814866">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2883464">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2883493">Does samba have wins replication support?</a></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="FAQ-general.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. General Information</td></tr></table></div></body></html>

4329
docs/htmldocs/Samba-HOWTO-Collection.html
View File

File diff suppressed because one or more lines are too long

8
docs/htmldocs/lmhosts.5.html
View File

@ -18,10 +18,10 @@
192.9.200.20 NTSERVER#20
192.9.200.21 SAMBASERVER
</pre><p>Contains three IP to NetBIOS name mappings. The first
and third will be returned for any queries for the names &quot;TESTPC&quot;
and &quot;SAMBASERVER&quot; respectively, whatever the type component of
the NetBIOS name requested.</p><p>The second mapping will be returned only when the &quot;0x20&quot; name
type for a name &quot;NTSERVER&quot; is queried. Any other name type will not
and third will be returned for any queries for the names "TESTPC"
and "SAMBASERVER" respectively, whatever the type component of
the NetBIOS name requested.</p><p>The second mapping will be returned only when the "0x20" name
type for a name "NTSERVER" is queried. Any other name type will not
be resolved.</p><p>The default location of the <tt class="filename">lmhosts</tt> file
is in the same directory as the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, and <a href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>
</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities

4
docs/htmldocs/samba.7.html
View File

@ -57,7 +57,9 @@
</p></dd><dt><span class="term"><a href="profiles.1.html"><span class="citerefentry"><span class="refentrytitle">profiles</span>(1)</span></a></span></dt><dd><p><b class="command">profiles</b> is a command-line
utility that can be used to replace all occurences of
a certain SID with another SID.
</p></dd><dt><span class="term"><a href="vfstest.1.html"><span class="citerefentry"><span class="refentrytitle">vfstest</span>(1)</span></a></span></dt><dd><p><b class="command">vfstest</b> is a utility
</p></dd><dt><span class="term"><a href="log2pcap.1.html"><span class="citerefentry"><span class="refentrytitle">log2pcap</span>(1)</span></a></span></dt><dd><p><b class="command">log2pcap</b> is a utility
for generating pcap trace files from Samba log
files.</p></dd><dt><span class="term"><a href="vfstest.1.html"><span class="citerefentry"><span class="refentrytitle">vfstest</span>(1)</span></a></span></dt><dd><p><b class="command">vfstest</b> is a utility
that can be used to test vfs modules.</p></dd><dt><span class="term"><a href="ntlm_auth.1.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(1)</span></a></span></dt><dd><p><b class="command">ntlm_auth</b> is a helper-utility
for external programs wanting to do NTLM-authentication.
</p></dd><dt><span class="term"><a href="smbmount.8.html"><span class="citerefentry"><span class="refentrytitle">smbmount</span>(8)</span></a>, <a href="smbumount.8.html"><span class="citerefentry"><span class="refentrytitle">smbumount</span>(8)</span></a>, <a href="smbmount.8.html"><span class="citerefentry"><span class="refentrytitle">smbmount</span>(8)</span></a></span></dt><dd><p><b class="command">smbmount</b>,<b class="command">smbmnt</b> and <b class="command">smbmnt</b> are commands that can be used to

12
docs/htmldocs/smbsh.1.html
View File

@ -1,4 +1,4 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbsh</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbsh.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbsh &#8212; Allows access to Windows NT filesystem
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbsh</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbsh.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbsh &#8212; Allows access to remote SMB shares
using UNIX commands</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbsh</tt> [-W workgroup] [-U username] [-P prefix] [-R &lt;name resolve order&gt;] [-d &lt;debug level&gt;] [-l logfile] [-L libdir]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a> suite.</p><p><b class="command">smbsh</b> allows you to access an NT filesystem
using UNIX commands such as <b class="command">ls</b>, <b class="command">
egrep</b>, and <b class="command">rcp</b>. You must use a
@ -33,11 +33,11 @@ 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 class="indexterm" name="id2796723"></a><i class="parameter"><tt>log level</tt></i> parameter
override the <a class="indexterm" name="id2802215"></a><i class="parameter"><tt>log level</tt></i> parameter
in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-R &lt;name resolve order&gt;</span></dt><dd><p>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.</p><p>The options are: &quot;lmhosts&quot;, &quot;host&quot;, &quot;wins&quot; and &quot;bcast&quot;.
string of different name resolution options.</p><p>The options are: "lmhosts", "host", "wins" and "bcast".
They cause names to be resolved as follows :</p><div class="itemizedlist"><ul type="disc"><li><p><tt class="constant">lmhosts</tt>:
Lookup an IP address in the Samba lmhosts file. If the
line in lmhosts has no name type attached to the
@ -66,9 +66,9 @@ resolution methods as it depends on the target host
being on a locally connected subnet.
</p></li></ul></div><p>If this parameter is not set then the name resolve order
defined in the <tt class="filename">smb.conf</tt> file parameter
(<a class="indexterm" name="id2796877"></a><i class="parameter"><tt>name resolve order</tt></i>) will be used.
(<a class="indexterm" name="id2796281"></a><i class="parameter"><tt>name resolve order</tt></i>) will be used.
</p><p>The default order is lmhosts, host, wins, bcast. Without
this parameter or any entry in the <a class="indexterm" name="id2796896"></a><i class="parameter"><tt>name resolve order</tt></i> parameter of the <tt class="filename">smb.conf</tt> file, the name
this parameter or any entry in the <a class="indexterm" name="id2796300"></a><i class="parameter"><tt>name resolve order</tt></i> parameter of the <tt class="filename">smb.conf</tt> file, the name
resolution methods will be attempted in this order. </p></dd><dt><span class="term">-L libdir</span></dt><dd><p>This parameter specifies the location of the
shared libraries used by <b class="command">smbsh</b>. The default
value is specified at compile time.
@ -91,7 +91,7 @@ resolution methods will be attempted in this order. </p></dd><dt><span class="te
cd</b> command to change directories, <b class="command">vi</b> to
edit files, and <b class="command">rcp</b> to copy files.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p><b class="command">smbsh</b> works by intercepting the standard
libc calls with the dynamically loaded versions in <tt class="filename">
smbwrapper.o</tt>. Not all calls have been &quot;wrapped&quot;, so
smbwrapper.o</tt>. Not all calls have been "wrapped", so
some programs may not function correctly under <b class="command">smbsh
</b>.</p><p>Programs which are not dynamically linked cannot make
use of <b class="command">smbsh</b>'s functionality. Most versions

2
docs/htmldocs/smbspool.8.html
View File

@ -3,7 +3,7 @@
are position-dependent for compatibility with the Common UNIX
Printing System, but you can use smbspool with any printing system
or from a program or script.</p><p><span class="emphasis"><em>DEVICE URI</em></span></p><p>smbspool specifies the destination using a Uniform Resource
Identifier (&quot;URI&quot;) with a method of &quot;smb&quot;. This string can take
Identifier ("URI") with a method of "smb". This string can take
a number of forms:</p><div class="itemizedlist"><ul type="disc"><li><p>smb://server/printer</p></li><li><p>smb://workgroup/server/printer</p></li><li><p>smb://username:password@server/printer</p></li><li><p>smb://username:password@workgroup/server/printer</p></li></ul></div><p>smbspool tries to get the URI from argv[0]. If argv[0]
contains the name of the program then it looks in the <tt class="envar">
DEVICE_URI</tt> environment variable.</p><p>Programs using the <b class="command">exec(2)</b> functions can

10
docs/htmldocs/testprns.1.html
View File

@ -1,11 +1,11 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>testprns</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="testprns.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>testprns &#8212; check printer name for validity with smbd</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">testprns</tt> {printername} [printcapname]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a> suite.</p><p><b class="command">testprns</b> is a very simple test program
to determine whether a given printer name is valid for use in
a service to be provided by <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>.</p><p>&quot;Valid&quot; in this context means &quot;can be found in the
printcap specified&quot;. This program is very stupid - so stupid in
a service to be provided by <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>.</p><p>"Valid" in this context means "can be found in the
printcap specified". This program is very stupid - so stupid in
fact that it would be wisest to always specify the printcap file
to use. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">printername</span></dt><dd><p>The printer name to validate.</p><p>Printer names are taken from the first field in each
record in the printcap file, single printer names and sets
of aliases separated by vertical bars (&quot;|&quot;) are recognized.
of aliases separated by vertical bars ("|") are recognized.
Note that no validation or checking of the printcap syntax is
done beyond that required to extract the printer name. It may
be that the print spooling system is more forgiving or less
@ -16,9 +16,9 @@
specified at compile time. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt class="filename">/etc/printcap</tt></span></dt><dd><p>This is usually the default printcap
file to scan. See <tt class="filename">printcap (5)</tt>.
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>If a printer is found to be valid, the message
&quot;Printer name &lt;printername&gt; is valid&quot; will be
"Printer name &lt;printername&gt; is valid" will be
displayed. </p><p>If a printer is found to be invalid, the message
&quot;Printer name &lt;printername&gt; is not valid&quot; will be
"Printer name &lt;printername&gt; is not valid" will be
displayed. </p><p>All messages that would normally be logged during
operation of the Samba daemons are logged by this program to the
file <tt class="filename">test.log</tt> in the current directory. The

26
docs/htmldocs/winbindd.8.html
View File

@ -69,9 +69,9 @@ 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 class="indexterm" name="id2796919"></a><i class="parameter"><tt>log level</tt></i> parameter
override the <a class="indexterm" name="id2796344"></a><i class="parameter"><tt>log level</tt></i> parameter
in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
<tt class="constant">".client"</tt> will be appended. The log file is
never removed by the client.
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
</p></dd><dt><span class="term">-i</span></dt><dd><p>Tells <b class="command">winbindd</b> to not
@ -108,15 +108,15 @@ never removed by the client.
and group rids. </p></div><div class="refsect1" lang="en"><h2>CONFIGURATION</h2><p>Configuration of the <b class="command">winbindd</b> daemon
is done through configuration parameters in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file. All parameters should be specified in the
[global] section of smb.conf. </p><div class="itemizedlist"><ul type="disc"><li><p>
<a class="indexterm" name="id2797151"></a><i class="parameter"><tt>winbind separator</tt></i></p></li><li><p>
<a class="indexterm" name="id2797169"></a><i class="parameter"><tt>idmap uid</tt></i></p></li><li><p>
<a class="indexterm" name="id2797187"></a><i class="parameter"><tt>idmap gid</tt></i></p></li><li><p>
<a class="indexterm" name="id2797205"></a><i class="parameter"><tt>winbind cache time</tt></i></p></li><li><p>
<a class="indexterm" name="id2797223"></a><i class="parameter"><tt>winbind enum users</tt></i></p></li><li><p>
<a class="indexterm" name="id2797241"></a><i class="parameter"><tt>winbind enum groups</tt></i></p></li><li><p>
<a class="indexterm" name="id2797259"></a><i class="parameter"><tt>template homedir</tt></i></p></li><li><p>
<a class="indexterm" name="id2797277"></a><i class="parameter"><tt>template shell</tt></i></p></li><li><p>
<a class="indexterm" name="id2797296"></a><i class="parameter"><tt>winbind use default domain</tt></i></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXAMPLE SETUP</h2><p>To setup winbindd for user and group lookups plus
<a class="indexterm" name="id2798898"></a><i class="parameter"><tt>winbind separator</tt></i></p></li><li><p>
<a class="indexterm" name="id2798916"></a><i class="parameter"><tt>idmap uid</tt></i></p></li><li><p>
<a class="indexterm" name="id2798934"></a><i class="parameter"><tt>idmap gid</tt></i></p></li><li><p>
<a class="indexterm" name="id2798952"></a><i class="parameter"><tt>winbind cache time</tt></i></p></li><li><p>
<a class="indexterm" name="id2798970"></a><i class="parameter"><tt>winbind enum users</tt></i></p></li><li><p>
<a class="indexterm" name="id2798988"></a><i class="parameter"><tt>winbind enum groups</tt></i></p></li><li><p>
<a class="indexterm" name="id2799006"></a><i class="parameter"><tt>template homedir</tt></i></p></li><li><p>
<a class="indexterm" name="id2799025"></a><i class="parameter"><tt>template shell</tt></i></p></li><li><p>
<a class="indexterm" name="id2799043"></a><i class="parameter"><tt>winbind use default domain</tt></i></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXAMPLE SETUP</h2><p>To setup winbindd for user and group lookups plus
authentication from a domain controller use something like the
following setup. This was tested on a RedHat 6.2 Linux box. </p><p>In <tt class="filename">/etc/nsswitch.conf</tt> put the
following:
@ -135,7 +135,7 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
</b></p><p>The next step is to join the domain. To do that use the
<b class="command">net</b> program like this: </p><p><b class="command">net join -S PDC -U Administrator</b></p><p>The username after the <i class="parameter"><tt>-U</tt></i> can be any
Domain user that has administrator privileges on the machine.
Substitute the name or IP of your PDC for &quot;PDC&quot;.</p><p>Next copy <tt class="filename">libnss_winbind.so</tt> to
Substitute the name or IP of your PDC for "PDC".</p><p>Next copy <tt class="filename">libnss_winbind.so</tt> to
<tt class="filename">/lib</tt> and <tt class="filename">pam_winbind.so
</tt> to <tt class="filename">/lib/security</tt>. A symbolic link needs to be
made from <tt class="filename">/lib/libnss_winbind.so</tt> to
@ -176,7 +176,7 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
apply any parameter changes to the running
version of winbindd. This signal also clears any cached
user and group information. The list of other domains trusted
by winbindd is also reloaded. </p></dd><dt><span class="term">SIGUSR1</span></dt><dd><p>The SIGUSR1 signal will cause <b class="command">
by winbindd is also reloaded. </p></dd><dt><span class="term">SIGUSR2</span></dt><dd><p>The SIGUSR2 signal will cause <b class="command">
winbindd</b> to write status information to the winbind
log file including information about the number of user and
group ids allocated by <b class="command">winbindd</b>.</p><p>Log files are stored in the filename specified by the

21
docs/manpages/log2pcap.1
View File

@ -21,12 +21,10 @@
.SH NAME
log2pcap \- Extract network traces from Samba log files
.SH "SYNOPSIS"
.ad l
.hy 0
.HP 9
\fBlog2pcap\fR [\-h] [logfile] [pcap_file]
.ad
.hy
.nf
\fBlog2pcap\fR [-h] [-q] [logfile] [pcap_file]
.fi
.SH "DESCRIPTION"
@ -42,10 +40,15 @@ The log file must have a \fIlog level\fR of at least \fB5\fR to get the SMB head
.SH "OPTIONS"
.TP
\-h
-h
If this parameter is specified the output file will be a hex dump, in a format that is readable by the text2pcap utility\&.
.TP
-q
Be quiet\&. No warning messages about missing or incomplete data will be given\&.
.TP
logfile
Samba log file\&. log2pcap will try to read the log from stdin if the log file is not specified\&.
@ -57,7 +60,7 @@ Name of the output file to write the pcap (or hexdump) data to\&. If this argume
.TP
\-h|\-\-help
-h|--help
Print a summary of command line options\&.
@ -81,7 +84,7 @@ Convert to pcap using text2pcap:
.nf
$ log2pcap \-h samba\&.log | text2pcap \-T 139,139 \- trace\&.pcap
$ log2pcap -h samba\&.log | text2pcap -T 139,139 - trace\&.pcap
.fi

274
docs/manpages/mount.cifs.8
View File

@ -1,170 +1,186 @@
.\" This manpage has been automatically generated by docbook2man
.\" from a DocBook document. This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "MOUNT.CIFS" "8" "03 August 2002" "" ""
.\"Generated by db2man.xsl. Don't modify this, modify the source.
.de Sh \" Subsection
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Ip \" List item
.br
.ie \\n(.$>=3 .ne \\$3
.el .ne 3
.IP "\\$1" \\$2
..
.TH "MOUNT.CIFS" 8 "" "" ""
.SH NAME
mount.cifs \- mount using the Common Internet File System (CIFS)
.SH SYNOPSIS
.SH "SYNOPSIS"
\fBmount.cifs\fR \fBservice\fR \fBmount-point\fR [ \fB-o options\fR]
.nf
\fBmount.cifs\fR {service} {mount-point} [-o options]
.fi
.SH "DESCRIPTION"
.PP
\fBmount.cifs\fR mounts a Linux CIFS filesystem. It
is usually invoked indirectly by
the \fBmount(8)\fR command when using the
"-t cifs" option. This command only works in Linux, and the kernel must
support the cifs filesystem. The CIFS protocol is the successor to the
SMB protocol and is supported by most Windows servers and many other
commercial servers and Network Attached Storage appliances as well as
by the popular Open Source server Samba.
.PP
The mount.cifs utility attaches the UNC name (exported network resource) to
the local directory \fBmount-point\fR. It is possible to set the mode for mount.cifs to
setuid root to allow non-root users to mount shares to directories for which they
have write permission.
.PP
Options to \fBmount.cifs\fR are specified as a comma-separated
list of key=value pairs. It is possible to send options other
than those listed here, assuming that cifs supports them. If
you get mount failures, check your kernel log for errors on
unknown options.
.PP
\fBmount.cifs\fR is a daemon. After mounting it keeps running until
the mounted resource is unmounted (usually via the umount utility)
.SH "OPTIONS"
\fBusername=<arg>\fR
specifies the username to connect as. If
this is not given, then the environment variable \fB USER\fR is used. This option can also take the
form "user%password" or "user/workgroup" or
"user/workgroup%password" to allow the password and workgroup
to be specified as part of the username.
.TP
\fBpassword=<arg>\fR
specifies the CIFS password. If this
option is not given then the environment variable
\fBPASSWD\fR is used. If it can find
no password \fBmount.cifs\fR will prompt
for a passeword, unless the guest option is
given.
Note that password which contain the arguement delimiter
character (i.e. a comma ',') will failed to be parsed correctly
on the command line. However, the same password defined
in the PASSWD environment variable or a credentials file (see
below) will be read correctly.
.PP
This tool is part of the \fBSamba\fR(7) suite\&.
.PP
mount\&.cifs mounts a Linux CIFS filesystem\&. It is usually invoked indirectly by the \fBmount\fR(8) command when using the "-t cifs" option\&. This command only works in Linux, and the kernel must support the cifs filesystem\&. The CIFS protocol is the successor to the SMB protocol and is supported by most Windows servers and many other commercial servers and Network Attached Storage appliances as well as by the popular Open Source server Samba\&.
.PP
The mount\&.cifs utility attaches the UNC name (exported network resource) to the local directory \fBmount-point\fR\&. It is possible to set the mode for mount\&.cifs to setuid root to allow non-root users to mount shares to directories for which they have write permission\&.
.PP
Options to \fBmount\&.cifs\fR are specified as a comma-separated list of key=value pairs\&. It is possible to send options other than those listed here, assuming that cifs supports them\&. If you get mount failures, check your kernel log for errors on unknown options\&.
.PP
\fBmount\&.cifs\fR is a daemon\&. After mounting it keeps running until the mounted resource is unmounted (usually via the umount utility)
.SH "OPTIONS"
.TP
\fBcredentials=<filename>\fR
specifies a file that contains a username
and/or password. The format of the file is:
username=\fIarg\fR
specifies the username to connect as\&. If this is not given, then the environment variable \fBUSER\fR is used\&. This option can also take the form "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup to be specified as part of the username\&.
.TP
password=\fIarg\fR
specifies the CIFS password\&. If this option is not given then the environment variable \fBPASSWD\fR is used\&. If it can find no password \fBmount\&.cifs\fR will prompt for a passeword, unless the guest option is given\&.
Note that password which contain the arguement delimiter character (i\&.e\&. a comma ',') will failed to be parsed correctly on the command line\&. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly\&.
.TP
credentials=\fIfilename\fR
specifies a file that contains a username and/or password\&. The format of the file is:
.nf
username = <value>
password = <value>
username = value
password = value
.fi
This is preferred over having passwords in plaintext in a shared file, such as \fI/etc/fstab\fR\&. Be sure to protect any credentials file properly\&.
This is preferred over having passwords in plaintext in a
shared file, such as \fI/etc/fstab\fR. Be sure to protect any
credentials file properly.
.TP
\fBuid=<arg>\fR
sets the uid that will own all files on
the mounted filesystem.
It may be specified as either a username or a numeric uid.
This parameter is ignored when the target server supports
the CIFS Unix extensions.
uid=\fIarg\fR
sets the uid that will own all files on the mounted filesystem\&. It may be specified as either a username or a numeric uid\&. This parameter is ignored when the target server supports the CIFS Unix extensions\&.
.TP
\fBgid=<arg>\fR
sets the gid that will own all files on
the mounted filesystem.
It may be specified as either a groupname or a numeric
gid. This parameter is ignored when the target server supports
the CIFS Unix extensions.
gid=\fIarg\fR
sets the gid that will own all files on the mounted filesystem\&. It may be specified as either a groupname or a numeric gid\&. This parameter is ignored when the target server supports the CIFS Unix extensions\&.
.TP
\fBport=<arg>\fR
sets the port number on the server to attempt to contact to negotiate
CIFS support. If the CIFS server is not listening on this port or
if it is not specified, the default ports will be tried i.e.
port 445 is tried and if no response then port 139 is tried.
port=\fIarg\fR
sets the port number on the server to attempt to contact to negotiate CIFS support\&. If the CIFS server is not listening on this port or if it is not specified, the default ports will be tried i\&.e\&. port 445 is tried and if no response then port 139 is tried\&.
.TP
\fBfile_mode=<arg>\fR
If the server does not support the CIFS Unix extensions this
overrides default file mode which will be used locally.
file_mode=\fIarg\fR
If the server does not support the CIFS Unix extensions this overrides default file mode which will be used locally\&.
.TP
\fBdir_mode=<arg>\fR
If the server does not support the CIFS Unix extensions this
overrides the default mode for directories.
dir_mode=\fIarg\fR
If the server does not support the CIFS Unix extensions this overrides the default mode for directories\&.
.TP
\fBip=<arg>\fR
sets the destination host or IP address.
ip=\fIarg\fR
sets the destination host or IP address\&.
.TP
\fBdomain=<arg>\fR
sets the domain (workgroup) of the user
domain=\fIarg\fR
sets the domain (workgroup) of the user
.TP
\fBguest\fR
don't prompt for a password
guest
don't prompt for a password
.TP
\fBro\fR
mount read-only
ro
mount read-only
.TP
\fBrw\fR
mount read-write
rw
mount read-write
.TP
\fBrsize\fR
rsize
default network read size
.TP
\fBwsize\fR
wsize
default network write size
.SH "ENVIRONMENT VARIABLES"
.PP
The variable \fBUSER\fR may contain the username of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords. The variable can be used to set both username and
password by using the format username%password.
The variable \fBUSER\fR may contain the username of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&. The variable can be used to set both username and password by using the format username%password\&.
.PP
The variable \fBPASSWD\fR may contain the password of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords.
The variable \fBPASSWD\fR may contain the password of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&.
.PP
The variable \fBPASSWD_FILE\fR may contain the pathname
of a file to read the password from. A single line of input is
read and used as the password.
The variable \fBPASSWD_FILE\fR may contain the pathname of a file to read the password from\&. A single line of input is read and used as the password\&.
.SH "NOTES"
.PP
This command may be used only by root\&.
.SH "CONFIGURATION"
The primary mechanism for making configuration changes and for reading
debug information for the cifs vfs is via the Linux /proc filesystem.
In the directory /proc/fs/cifs are various configuration files and
pseudo files which can display debug information. For more
information see the kernel file fs/cifs/README
.PP
The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem\&. In the directory /proc/fs/cifs are various configuration files and pseudo files which can display debug information\&. For more information see the kernel file fs/cifs/README
.SH "BUGS"
.PP
Passwords and other options containing , can not be handled.
For passwords an alternative way of passing them is in a credentials
file or in the PASSWD environment.
Passwords and other options containing , can not be handled\&. For passwords an alternative way of passing them is in a credentials file or in the PASSWD environment\&.
.PP
The credentials file does not handle usernames or passwords with
leading space.
The credentials file does not handle usernames or passwords with leading space\&.
.PP
Note that the typical response to a bug report is suggestion
to try the latest version first. So please try doing that first,
and always include which versions you use of relevant software
when reporting bugs (minimum: samba, kernel, distribution)
Note that the typical response to a bug report is suggestion to try the latest version first\&. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)
.SH "VERSION"
.PP
This man page is correct for version 3\&.0 of the Samba suite\&.
.SH "SEE ALSO"
.PP
Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel
source tree may contain additional options and information.
Documentation/filesystems/cifs\&.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information\&.
.SH "AUTHOR"
.PP
Steve French
Steve French
.PP
The syntax and manpage were loosely based on that of smbmount.
The syntax and manpage were loosely based on that of smbmount\&. It was converted to Docbook/XML by Jelmer Vernooij\&.
.PP
The current maintainer of the Linux cifs vfs and the userspace
tool \fBmount.cifs\fR is Steve French <URL:mailto:sfrench@samba.org>.
The SAMBA Mailing list <URL:mailto:samba@samba.org>
is the preferred place to ask questions regarding these programs.
The current maintainer of the Linux cifs vfs and the userspace tool \fBmount\&.cifs\fR is Steve French\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&.

5
docs/manpages/samba.7
View File

@ -151,6 +151,11 @@ The \fBnet\fR command is supposed to work similar to the DOS/Windows NET\&.EXE c
\fBprofiles\fR is a command-line utility that can be used to replace all occurences of a certain SID with another SID\&.
.TP
\fBlog2pcap\fR(1)
\fBlog2pcap\fR is a utility for generating pcap trace files from Samba log files\&.
.TP
\fBvfstest\fR(1)
\fBvfstest\fR is a utility that can be used to test vfs modules\&.

4
docs/manpages/winbindd.8
View File

@ -279,8 +279,8 @@ Reload the \fBsmb.conf\fR(5) file and apply any parameter changes to the running
.TP
SIGUSR1
The SIGUSR1 signal will cause \fB winbindd\fR to write status information to the winbind log file including information about the number of user and group ids allocated by \fBwinbindd\fR\&.
SIGUSR2
The SIGUSR2 signal will cause \fB winbindd\fR to write status information to the winbind log file including information about the number of user and group ids allocated by \fBwinbindd\fR\&.
Log files are stored in the filename specified by the log file parameter\&.