samba - Jul 1999 - samba and msaccess help please

Hopefully this is a samba question, and not a Microsoft Access question...  


I have a multiuser access database on a samba share...  it worked fine with
multiple users being able to connect to it at the same time no probs.  I just
upgraded the linux box to red hat 6, copied across the same smb.conf from before
and now users are getting a error "Too many active users" when more
than one user tries to connect.

Any help much appreciated...


Paul Thomsen

-------------- next part --------------
HTML attachment scrubbed and removed

> Paul Thomsen wrote:
> 
> Hopefully this is a samba question, and not a Microsoft Access
> question...
> 
> 
> I have a multiuser access database on a samba share...  it worked fine
> with multiple users being able to connect to it at the same time no
> probs.  I just upgraded the linux box to red hat 6, copied across the
> same smb.conf from before and now users are getting a error "Too many
> active users" when more than one user tries to connect.
> 
> Any help much appreciated...
> 
What happens if you delete the .ldb file and start over?

When the world was young, "Paul Thomsen"
<paul@nungalinya.edu.au>
carved some runes like this:  
> I have a multiuser access database on a samba share...  it
> worked fine with multiple users being able to connect to it at
> the same time no probs.  I just upgraded the linux box to red hat
> 6, copied across the same smb.conf from before and now users are
> getting a error "Too many active users" when more than one user
> tries to connect. 
The change from redhat 5 to 6 can cause some interesting side 
effects due to a significant change in the stock kernel version 
(2.0.36 to 2.2.x) and glibc.  IMHO there are still some bugs to be 
worked out in the latest glibc, as well as a few in the new kernel.

Since samba depends heavily on the kernel source for header/include 
files, smbfs, etc, and the compilation of samba requires both the 
full kernel source and header files, as well as a properly 
installed glibc, upgrading a production samba box (as you just did) 
is a non-trivial task.  Which is why my samba box at work is still 
running kernel 2.0.30/libc5/samba 1.9.18p10.  When I finish some 
other stuff, I'll be able to do the whole samba/kernel/libc update 
thing at home before I try it here.

There have been various changes in op-clock behavior due to the 
samba/kernel/libc changes, as well as misbehaved M$ clients not 
responding to op-lock break requests, etc.  I'd bet that's the 
source of your problem.  I'd recommend scanning the samba archives 
and smb newsgroups for related posts, then try compiling the samba 
source.  Start with 2.04b, but you may need to get the latest 
snapshot.

Of course, I could be completely goofy and somebody who really 
knows this stuff (Jerry?) might have a simple fix for you...

Steve

****************************************************************
Stephen L. Arnold                        Senior Systems Engineer
ENSCO Inc.                        email:  arnold.steve@ensco.com
P.O. Box 5488                         www:  http://www.ensco.com
Vandenberg AFB, CA  93437                    voice: 805.606.8838
                                               fax: 805.734.4779
#include <std_disclaimer.h>
****************************************************************