search for: level2oplocks

Hello for all ! We use a samba server 2.2.1a with conectiva 7 [ kernel 2.4.18] and have the most important system of enterprise in clipper. In begin we have many problems with index corruption and clipper system freezes Then we turned off oplocks and level2oplocks and found peace. But sometimes the system until freeze in one station and this freeze others stations too. When clipper system is closed in the first freezed station, the others return to normality. The softhouse that was developer clipper system say: * linux and samba is the problem > he don&...

...grant Modify for Windows... As of smb.conf, here is snippet [pripomienkovanie]    path = /mnt/data_disk/www/pripomienkovanie/     dos filetime resolution = yes     writable = yes     read only = no     preserve case = yes     create mask = 775     directory mask = 2775     oplocks = false     level2oplocks = false Dňa 16. 11. 2018 o 11:28 Rowland Penny via samba napísal(a): > On Fri, 16 Nov 2018 10:03:08 +0100 > "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org> wrote: > >> Hi, >> >> I'm searching the web for a while but cannot find an answer t...

...the error is. I'm running Samba 3.0.2 with OpenLDAP 2.0.27. It might be related to Kerberos or to SSL. I've looked through my NMBD and SMBD logs and found very little as to what the problem could be. I've tried various things in my smb.conf like turing off file locking (oplock) and level2oplocks as some of the groups mentioned that this might be the cause. Any thoughts? I can forward more info if needed. Apr 20 13:27:22 bd4 smbd[30280]: [2004/04/20 13:27:22, 0] lib/util_sock.c:write_socket_data(388) Apr 20 13:27:22 bd4 smbd[30280]: write_socket_data: write failure. Error = Connection r...

...te mounted share and I don't know what this slow performance can be due to. I'm not running with oplocks cause the share is accessed only by the other linux machine (no windows clients) and oplocks produced a few problems with my database indexes (dataflex) in the past. Thus oplocks and level2oplocks are disabled. The following is a part of my configuration file: [DATA] comment = database path = /vol1/sys/ writable = yes browsable = no available = yes public = yes printable = no guest ok = yes copy = lock_template...

...ectory mask = 0775 force create mode = 0664 force directory mode = 0775 force user = expl force group = expl # The following to avoid file system lockings locking = Yes strictlocking = No posixlocking = Yes oplocks = No level2oplocks = No fakeoplocks = No blockinglocks = Yes $ df /opt/srv007/app/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/asm/vpdona07-390 68157440 13112864 55044576 20% /opt/srv007/app /dev/asm/vpdona07-390 /opt/srv007/app acfs rw,relatime,...

...t I need essentially the following in my smb.conf file: [lab] path = /usr2/lab available = yes public = yes guest only = no writeable = yes browseable = yes valid users = foonly, hart only user = no oplocks = No level2oplocks = No create mask = 770 directory mask = 770 force group = lab with the important lines being "create mask", "directory mask" and "force group". The problem is that while the "create mask" and "directory mask" lines work,...

...oplocks = no default case = lower case sensitive = no preserve case = no fstype = vfat [homes] comment = Home-Verzeichnis locking = yes strict locking = yes blocking locks = yes veto oplock files = /*.dbf/*.DBF/*.cdx/*.CDX/*.fpt/*.FPT oplocks = no level2oplocks = no fake oplocks = no browseable = no read only = no create mode = 0750 hide unreadable = yes ---------------------------------- I tried several different oplocks configurations, but nothing works. Can you help me? Claudia

...ll also intermittently get red crosses over the icon indicating loss of connection. All clients are involved in a render network and are accessing the server constantly so this can't be a inactivity timeout, could it? Some smd.conf parameters I've been playing with: oplocks = False level2oplocks = False debug level = 2 keepalive = 300

...p = WORKGROUP server string = Linux Server netbios name = SRVNAME log level = 1 security = ads dedicated keytab file = /etc/krb5.keytab kerberos method = system keytab realm = WORKGROUP.COM passdb backend = tdbsam socket options = TCP_NODELAY IPTOS_LOWDELAY client NTLMv2 auth = yes oplocks = False level2oplocks = False posix locking = no log file = /var/log/samba/log.%m max log size = 5000 include = /etc/samba/rhs-samba.conf [test] path = /home/test inherit permissions = yes inherit acls = yes public = yes only guest = no writable = yes printable = no browseable = yes strict locking = no >...

...ed fiddling with the following parameters without any noticeable difference no matter what I do except in the case of the socket options. The setting you see below, commented out, causes file copying to/from the samba server to run much faster than if I put the setting back in. ;oplocks = false ;level2oplocks = false ;socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 Anyone else running into similar issues? Any thoughts or suggestions welcome! Thanks, ~Eric My SMB.CONF (Note some lines are commented out) -------------------------------------------------------------------------- [global]...

...nt acl support = no time server = yes enable privileges = yes passdb backend = tdbsam username map = /etc/samba/smbusers hide dot files = yes guest ok = no name cache timeout = 60 [geo$] comment = Mapa # oplock = yes # level2oplocks = yes # locking = yes invalid users = @geodeta, at ewidencja, write list = +geo path = /home/samba/geo force group = geo force create mode = 0777 vfs object = recycle full_audit recycle:repository = .recycle/%U recycle:touch = tr...

...ectory mask = 0775 force create mode = 0664 force directory mode = 0775 force user = expl force group = expl # The following to avoid file system lockings locking = Yes strictlocking = No posixlocking = Yes oplocks = No level2oplocks = No fakeoplocks = No blockinglocks = Yes $ df /opt/srv007/app/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/asm/vpdona07-390 68157440 13112864 55044576 20% /opt/srv007/app /dev/asm/vpdona07-390 /opt/srv007/app acfs rw,relatime,...

...bove two lines are interesting, if something is writable, this means it isn't just readable, or to put it another way, they both mean the same so why have both ? > >     preserve case = yes >     create mask = 775 >     directory mask = 2775 > >     oplocks = false >     level2oplocks = false Why don't you want oplocks ? To be honest, I would replace all of the above with this: [pripomienkovanie]    path = /mnt/data_disk/www/pripomienkovanie/     read only = no Then follow the wikipage I point you to earlier. Rowland

...les running Samba with Office XP (specifically Access XP) from Win2k boxes? BTW, for those interested, here is appropriate sections from smb.conf for the share in the first question: [acsup] path = /export/acsup read only = No browseable = No oplocks = No level2oplocks = No writable = yes browsable = yes only user = no and everything else seems to work fine. -- Sam Hart University/Work addr. <hart@physics.arizona.edu> Personal addr. <criswell@geekcomix.com> end

hi, why is it i cannot open a ms access database (residing in my samba server) while being used/open by another user? is there an implementation of antivirus in a samba server? Thanks in advance for your suggestion! eric __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

...s are being connected to the root directory "/" of my server as nobody. The only way you can discover the user is to troll the log file. Here is my config file as pertains to users: [global] - encrypt passwords=yes ; wins support=yes ; security=user ; domain logons=yes ; oplocks=no ; level2oplocks=no ; logon path=\\%L\profiles\%u\%m ; logon script=logon.bat ; logon drive=S: ; logon home=\\%L\%u\.win_profile\%m ; invalid users = nobody root bin daemon adm sync shutdown ; add user script=/usr/sbin/useradd -d /dev/nu.. -g 100 -s /bin/false -M %u ; log file = /etc/samba/smblog-%m.txt ; log level...

...s are being connected to the root directory "/" of my server as nobody. The only way you can discover the user is to troll the log file. Here is my config file as pertains to users: [global] - encrypt passwords=yes ; wins support=yes ; security=user ; domain logons=yes ; oplocks=no ; level2oplocks=no ; logon path=\\%L\profiles\%u\%m ; logon script=logon.bat ; logon drive=S: ; logon home=\\%L\%u\.win_profile\%m ; invalid users = nobody root bin daemon adm sync shutdown ; add user script=/usr/sbin/useradd -d /dev/nu.. -g 100 -s /bin/false -M %u ; log file = /etc/samba/smblog-%m.txt ; log level...

...s security = user wins support = yes create mask = 0600 directory mask = 0700 log file = /var/samba/log.%m log level = 1 max log size = 0 interfaces = 10.52.1.1 10.42.1.1 domain master = Yes security mask = 0777 level2oplocks = no encrypt passwords = Yes dont descend = /proc,/dev,/etc,/usr printing = SYSV server string = Samba Server workgroup = #### hosts allow = 127. 10. 172.16. netbios name = ####### socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALI...

...= yes printable = no writable = yes delete readonly = yes hide dot files = no case sensitive = yes force group = users valid users = mark directory mode = 0775 force directory mode = 0775 create mode = 0664 force create mode = 0664 oplocks = False level2oplocks = False Any help would be greatly appreciated. Mark -- A fool lies awake at nights, worrying of this and that; weary is he when morning breaks, and all remains as before.

...1:45:07, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) ***** --------------------------------------- I have: [global] workgroup = PEOPLESQUEST hosts allow = 172.16. socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8576 SO_SNDBUF=8576 oplocks = True level2oplocks = True # Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. ; interfaces = 192.168.12.2/24 192.168.13.2/24 Bind Interfaces Only = True Interfaces = eth0:99 172.16.0.1 remote announce = 172.1...