Re: [Samba] error whit more than one user.

2005-11-29 Thread jorge santiago
Hi, I'm experiencing a very similar problem: any user except the first
one, opens the database at a very very slow transfer rate.  The .mdb
file size is 75 MB. I've tweaked oplocks with no success If you
find any solution please let me know. Thanks in advance,

santiago.

On 11/28/05, Guilherme Pretto Nunes <[EMAIL PROTECTED]> wrote:
> Hi.
>
> I having a problem when more then one user open the same file. It's a
> MS-Access database file (yeah, ugh.).
> In my samba share, for the fist user who open the file works fine, but
> when the second try to open the file (when the first user still using
> the database file) doesn't work. If the first user "disconnect" from the
> file, the second one can open-it just fine. And if i make this share in
> a windows box, works fine. Don't know if it's in my samba configuration
> or a file system problem. Tried whit ext3 and ntfs.
>
> If anyone can help me to make more than one connection open the same
> file, thanks.
>
> here's my samba conf.:
>
> [global]
> locking = no
> workgroup = (asd)
> netbios name = (asdasd)
> server string =
> announce as = NT Server
> security = share
> log file = /var/log/samba/samba.%m
> max log size = 100
> debug level = 3
> local master = no
> os level = 100
> domain master = no
> preferred master = no
> domain logons = no
> wins support = no
> dns proxy = no
> keep alive = 20
> load printers = no
> hosts deny = all
> hosts allow = 192.168.1.
>
> [the share]
>path = (path)
>public = yes
>writable = yes
>printable = no
>browsable = yes
>create mask = 0777
>directory mask = 0777
>read only = no
>force create mode = 777
>force security mode = 770
>force directory mode = 770
>force directory security mode = 777
>guest ok = yes
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Slow Access Database on Samba

2005-11-16 Thread jorge santiago
Sure, I pasted it below,  dbsystem is the share where the Access
database is located. I'm using debian sarge (samba 3.0.14a-3, openldap
2.2.23-8).

santiago.

/etc/samba/smb.conf:

#=== Global Settings ===

[global]
   workgroup = myworkgroup
   netbios name = mysmbserver
   server string = %h server
   wins support = yes
   name resolve order = lmhosts host wins bcast

   log file = /var/log/samba/log.%m
   log level = 1
   max log size = 1000
   syslog = 0
   panic action = /usr/share/samba/panic-action %d

   security = user
   encrypt passwords = true
   passdb backend = ldapsam:ldap://127.0.0.1

   ldap ssl = Off

   obey pam restrictions = no

   ldap admin dn = cn=admin,dc=mydomain,dc=com
   ldap suffix = dc=mydomain,dc=com
   ldap group suffix = ou=Groups
   ldap user suffix = ou=People
   ldap machine suffix = ou=Computers
   ldap idmap suffix = ou=People

   ldap passwd sync = Yes
   passwd program = /usr/sbin/smbldap-passwd %u
   passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*all*authentication*tokens*updated*

   guest account = nobody
   invalid users = root
   admin users = Administrator

   add user script = /usr/sbin/smbldap-useradd -m "%u"
   ldap delete dn = Yes
   delete user script = /usr/sbin/smbldap-userdel "%u"
   add machine script = /usr/sbin/smbldap-useradd -w "%u"
   add group script = /usr/sbin/smbldap-groupadd -p "%g"
   delete group script = /usr/sbin/smbldap-groupdel "%g"
   add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
   delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g"
   set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"

  logon script = netlogon.bat
  socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192

   domain logons = yes
   domain master = yes
   preferred master = yes
   local master = yes

   os level = 100

   time server = yes

   getwd cache = yes
   use sendfile = no
   lock spin time = 15
   lock spin count = 30
   hosts allow = 172.25.0.0/16 172.30.0.0/16 127.0.0.1
   interfaces = eth1 eth1:0 lo
   bind interfaces only = yes
  ;dns proxy = no
   oplocks = no
   level2 oplocks = no
   change notify timeout = 300
   dos filetimes = yes
   strict locking = no

#=== Share Definitions ===

[homes]
   comment = Home Directories
   browseable = no
   writable = yes
   create mask = 0700
   directory mask = 0700
   oplocks = yes
   level2 oplocks = yes
   root preexec = /usr/local/sbin/sambalogger.sh start %u %m %I
   root postexec = /usr/local/sbin/sambalogger.sh stop %u %m %I

[netlogon]
   comment = Network Logon Service
   path = /home/SambaPot/netlogon
   guest ok = yes
   writable = no
   share modes = no

[printers]
   comment = All Printers
   browseable = no
   path = /tmp
   printable = yes
   public = no
   writable = no
   create mode = 0700

[dbsystem]
path = /home/SambaPot/dbsystem
read only = Yes
browseable = Yes
create mask = 0666
directory mask = 0777
write list = @dbsystem


On 11/16/05, Gerald Drouillard <[EMAIL PROTECTED]> wrote:
> Jorge Santiago wrote:
>
> >I've applied all the optimizations you mention in that URL in my own
> >smb.conf but my problem persists.  The first user of the database
> >opens it very fast, but the next users that try to open it, do it very
> >slowly.  Do you know what option (locking option?) might cause this
> >behaviour? I've also tried 'strict locking = no' with no success.
> >
> >
> Can we see what you smb.conf looks like now?
>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Samba/LDAP-Backend stability on Debian Sarge

2005-11-12 Thread Jorge Santiago
Hi,

First, excuse me if this post is a bit offtopic, maybe this should be
posted in the debian-users maillist, but I just wanted to read your
experiences with this kind of setup, since I've  migrated the server
to Debian Sarge using LDAP Backend to serve clients using WinXP and
Win98, and I've got this serious problems:

- Samba segfaults [1]
- slapd process crashes very often, almost once per day (i had to
create a cron job to restart it periodically).
- Slow MS Access database access [2] (I'm still trying to figure this
one, maybe is a change of default in some samba option).

Any of you is running a setup like this and having similar problems? 
Any Idea on how I could solve any of this?

Thanks,

santiago.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314461
[2] http://rubyurl.com/9Dz
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Slow Access Database on Samba

2005-11-12 Thread Jorge Santiago
I've applied all the optimizations you mention in that URL in my own
smb.conf but my problem persists.  The first user of the database
opens it very fast, but the next users that try to open it, do it very
slowly.  Do you know what option (locking option?) might cause this
behaviour? I've also tried 'strict locking = no' with no success.

Thanks for your help,

santiago.

On 11/11/05, Gerald Drouillard <[EMAIL PROTECTED]> wrote:
> Dave Williams wrote:
> > Dear  All,
> >
> > We have an access database running on a Samba share (Samba version
> > 3.0.10-1.4E) with a gigabit connection to the network. The front end of the
> > databases are on the client machines with linked tables stored in a separate
> > mdb file on the linux server.
> >
> > For some reason the database runs very slowly when it is set up in this way.
> > I tested copying a 10 MB file onto the samba share and it was instant which
> > leads me to believe that this is not a networking issue but tweak needed to
> > the smb.conf file. I have also run the database with the back end stored on
> > a Windows Peer in the network - it runs much faster than on  the linux
> > setup. Here is the current Global setting in smb.conf. I would be very
> > grateful if anyone can help;
> >
> >
> > [global]
> > workgroup = ACE
> > server string = Ace New Server
> > passdb backend = tdbsam
> > username map = /etc/samba/smbusers
> > wins support = Yes
> > local master = yes
> > preferred master = yes
> > wins support = yes
> > socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096
> > SO_RCVBUF=4096
> > oplocks = no
> >
> >
> > Dave Williams
> >
> >
> >
>
> Have a look at:
> http://drouillard.ca/Tips&Tricks/Samba/Oplocks.htm
>
> --
> Regards
> --
> Gerald Drouillard
> Technology Architect
> Drouillard & Associates, Inc.
> http://www.Drouillard.ca
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Slow MS Access database after upgrade to Samba3

2005-11-08 Thread Jorge Santiago
Thanks for your suggestion,

I tried "strict locking = no" with the same results.   Any other idea?

Thanks,

santiago.

On 11/6/05, Andrew Bartlett <[EMAIL PROTECTED]> wrote:
> On Sat, 2005-11-05 at 20:54 -0500, Jorge Santiago wrote:
> > Hi,
> >
> > I had a Debian woody server with samba as PDC with LDAP backend in the
> > same box, and mixed windows clients (98, XP, etc).  The clients
> > accessed a 75MB MS Access database (.mdb)  that was put in a Samba
> > share.  Everything was fast... everything was good...
> >
> > But, last week I decided to upgrade to debian Sarge, so as you know
> > Samba was upgraded to Samba3 too (3.0.14a), and now if a user tries to open 
> > the
> > database and is the first user accessing it, it opens really fast
> > (100Mps network), but any other user after the first who tries to open
> > it gets the database to open very slow (seems like 10Mbps transfers, as
> > shown in windows network monitor).
> >
> > I've enabled and disabled oplocks with no success at all, but I'm
> > almost sure is some kind of problem with locking, since any other samba
> > transfer between the server and the clients are fast.
> >
> > Have anyone spotted this kind of problem that could give me any advice?
>
> My guess would that a change in the default of 'strict locking'.  Try
> 'strict locking = no' on the share.
>
> (You are unlikely to be sharing this with server-side posix or NFS
> apps :-)
>
> Andrew Bartlett
>
> --
> Andrew Bartletthttp://samba.org/~abartlet/
> Authentication Developer, Samba Team   http://samba.org
> Student Network Administrator, Hawker College  http://hawkerc.net
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQBDbarQz4A8Wyi0NrsRArYCAJ9gxrU49gs/zrz5nUqLEYoBG2RcNwCfUJyh
> HT39w1h8lnjPpdaGn3VgPx8=
> =H5oT
> -END PGP SIGNATURE-
>
>
>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Slow MS Access database after upgrade to Samba3

2005-11-05 Thread Jorge Santiago
Hi,

I had a Debian woody server with samba as PDC with LDAP backend in the
same box, and mixed windows clients (98, XP, etc).  The clients
accessed a 75MB MS Access database (.mdb)  that was put in a Samba
share.  Everything was fast... everything was good...

But, last week I decided to upgrade to debian Sarge, so as you know
Samba was upgraded to Samba3 too (3.0.14a), and now if a user tries to open the
database and is the first user accessing it, it opens really fast
(100Mps network), but any other user after the first who tries to open
it gets the database to open very slow (seems like 10Mbps transfers, as
shown in windows network monitor).

I've enabled and disabled oplocks with no success at all, but I'm
almost sure is some kind of problem with locking, since any other samba
transfer between the server and the clients are fast.

Have anyone spotted this kind of problem that could give me any advice?

Your help is greatly appreciated.  I attach most relevant parts of my
current smb.conf, dbsystem is the share where the MS Access database is
located.

Thanks a lot,

santiago.


/etc/samba/smb.conf:

[global]

## Browsing/Identification ###

   workgroup = myworkgroup
   netbios name = sambaserver
   server string = %h server
   wins support = yes
   name resolve order = lmhosts host wins bcast

### Authentication ###

   security = user
   encrypt passwords = true
   passdb backend = ldapsam:ldap://127.0.0.1

   ldap ssl = Off

   obey pam restrictions = no

 Misc 

  logon script = netlogon.bat

  socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192
SO_SNDBUF=8192

   domain logons = yes
   domain master = yes
   preferred master = yes
   local master = yes

   os level = 100

   time server = yes

   getwd cache = yes
   use sendfile = no
   lock spin time = 15
   lock spin count = 30
   hosts allow = 172.25.0.0/16 172.30.0.0/16 127.0.0.1
   interfaces = eth1 eth1:0 lo
   interfaces = eth1 eth1:0 lo
   bind interfaces only = yes
   oplocks = no
   level2 oplocks = no
   change notify timeout = 300
   dos filetimes = yes

# Share Definitions =

[homes]
   comment = Home Directories
   browseable = no
   writable = yes
   create mask = 0700
   directory mask = 0700
   oplocks = yes
   level2 oplocks = yes
   root preexec = /usr/local/sbin/sambalogger.sh start %u %m %I
   root postexec = /usr/local/sbin/sambalogger.sh stop %u %m %I

[dbsystem]
path = /home/samba/dbsystem
read only = Yes
browseable = Yes
create mask = 0666
directory mask = 0777
write list = @dbsystem
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba