Beiträge von hermeti-k

Thanks for your reply!

I checked out, and they are enabled. But testing with in the clients pc, i can see that, there are versions of libre/openoffice, that dont create any .-lock file!

I think it is a Openoffice change.

In versions from 2.0 to 2.4 of openoffice the file locking works great. When i try to open a file that its already in use, a message saying "the file is locked for editing" appears.

When i use newer versions of Openoffice, the behaviour changes. I can open an already in use file and i can change whatever i want, causing data loss in the files.

Nop, i saw that link before, and it is still not working!

Hi guys!

Im trying to set up my smb.conf, and cannot find the solution of the problem

When user1 (ubunutu machine) opens a xls placed in a share, then user2 opens the same file, it opens whithout any warning that user1 is editing the file.

i tried to disable oplocks, kernel oplocks, without any success. I want that when user1 opens an xls file in that share, the srver locks the until the useres closes it.

is it posible???

here is my smb.conf file

oplcoks, kernel oplocks, and other parameters....seems to have no effect on what im trying to do.

#======================= Global Settings =======================
[global]
workgroup = WORKGROUP
server string = %h server
dns proxy = no
log level = 0
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
syslog only = yes
panic action = /usr/share/samba/panic-action %d
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
use sendfile = no
null passwords = no
local master = yes
time server = no
wins support = no
kernel oplocks = yes


#======================= Share Definitions =======================
[share]
path = /media/3dcb9e47-f9a2-41fa-9e6a-b20a44674a6a/share/
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = yes
store dos attributes = yes
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
valid users = "esteban"
invalid users =
read list =
write list = "esteban"

Hi all,

i have a OMV 0.43b with shared folders int it, an its working fine!
Last week i needed to install a new OMV box, and got the last dated package in the site and installed it. After configuring all shares in it (they work fine, permissions etc.), I noticed that samba isn't locking files when an user opens it.

For example:

user 1: opens .xls in a share
user 2: opens same .xls and samba is not showing that a user has already open the file.

I tried to use oplocks, locking, strict locking feautures without success!
With the old OMV box, i dont have any issues of this kind, and files are blocking right!
Has anyone have an idea whats is going wrong with mi conf.? Or instead there is a samba update that doesnt work like it used to be?