1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-25 23:21:54 +03:00

Added a few example case thingies - called Common Errors.

(This used to be commit 58ed149471)
This commit is contained in:
John Terpstra 2003-05-27 16:10:53 +00:00
parent 6d4b58f622
commit 5a4a8305cc
4 changed files with 119 additions and 0 deletions

View File

@ -448,4 +448,20 @@ example of what you would not want to see would be:
script to make Samba fit into that system.</para></note>
</sect2>
</sect1>
<sect1>
<title>Common Errors</title>
<para>
I've compiled Samba-3 from the CVS and the two binaries (smbd and nmbd)
are very large files (40 Mg and 20 Mg). I've the same result with
--enable-shared ?
</para>
<para>
Answer: Strip the binaries (or dond't compile with -g).
</para>
</sect1>
</chapter>

View File

@ -255,6 +255,39 @@ or that suffer regular outages. Network stability and integrity are key concerns
distributed trusted domains.
</para>
<sect2>
<title>Tell me about Trust Relationships using Samba</title>
<para>
Like many, I administer multiple LANs connected together using NT trust
relationships. This was implemented about 4 years ago. I now have the
occasion to consider performing this same task again, but this time, I
would like to implement it solely through samba - no Microsoft PDCs
anywhere.
</para>
<para>
I have read documentation on samba.org regarding NT-style trust
relationships and am now wondering, can I do what I want to? I already
have successfully implemented 2 samba servers, but they are not PDCs.
They merely act as file servers. I seem to remember, and it appears to
be true (according to samba.org) that trust relationships are a
challenge.
</para>
<para>
Please provide any helpful feedback that you may have.
</para>
<para>
These are almost complete in Samba 3.0 snapshots. The main catch
is getting winbindd to be able to allocate uid/gid's for trusted
users/groups. See the updated Samba HOWTO collection for more
details.
</para>
</sect2>
</sect1>
</chapter>

View File

@ -219,4 +219,54 @@ performance. Check the sections on the various clients in
</para>
</sect1>
<sect1>
<title>Samba performance problem due changing kernel (2.4.20 Linux kernel)</title>
<para>
Hi everyone. I am running Gentoo on my server and samba 2.2.8a. Recently
I changed kernel version from linux-2.4.19-gentoo-r10 to
linux-2.4.20-wolk4.0s. And now I have performance issue with samba. Ok
many of you will probably say that move to vanilla sources...well I ried
it too and it didn't work. I have 100mb LAN and two computers (linux +
Windows2000). Linux server shares directory with DivX files, client
(windows2000) plays them via LAN. Before when I was running 2.4.19 kernel
everything was fine, but now movies freezes and stops...I tried moving
files between server and Windows and it's trerribly slow.
</para>
<para>
Grab mii-tool and check the duplex settings on the NIC.
My guess is that it is a link layer issue, not an application
layer problem. Also run ifconfig and verify that the framing
error, collisions, etc... look normal for ethernet.
</para>
</sect1>
<sect1>
<title>Corrupt tdb Files</title>
<para>
<screen>
Well today it happend.... our first major troubles using samba. This is
no complaints but just some questions :-)
Our samba PDC server has been hosting 3 TB of data to our 500+ users
[Windows NT/XP] for the last 3 years using samba, no problem.
But today all shares went SLOW; very slow. Also the main smbd kept
spawning new processes so we had 1600+ running smbd's.... ( while
normally we avg. 250 ).
It crashed the SUN E3500 cluster twice. After alot of searching I
decided to rm ./var/locks/*.tbl and YES I was happy again.
Q1) Is there any method of keeping the *.tbl files in top condition or
how to early detect corruption?
Q2) What I also would like to mention is that the service latency seems
alot lower then before the locks cleanup, any ideas on keeping it top notch?
</screen>
</para>
</sect1>
</chapter>

View File

@ -980,6 +980,26 @@ so far:
</para></listitem>
</itemizedlist>
<scet2>
<title>locking.trb error messages</title>
<para>
<screen>
> We are seeing lots of errors in the samba logs like:
>
> tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
> 0x4d6f4b61 at offset=36116
>
> What do these mean?
</screen>
</para>
<para>
Corrupted tdb. Stop all instancesd of smbd, delete locking.tdb, restart smbd.
</para>
</sect2>
</sect1>
<sect1>