[Samba] Re: What affects file locking?

2008-08-14 Thread Doug Germann
Jeremy Allison  samba.org> writes:

> > Jeremy--
> > 
> > Many thanks.
> > 
> > You are right--between Ubuntu and WinXP, the files are locked appropriately.
> > 
> > But how do I get these byte-range locks between the Ubuntu clients? I have
> > searched in Google and on Ubuntuforums without luck.
> 
> The application should ask for them via the fcntl API. I'm pretty sure
> OpenOffice does do this. How are you mounting the Samba server from
> the Ubuntu boxes ? CIFSFS does pass along byte range locks.
> 
> Jeremy.


> The application should ask for them via the fcntl API. I'm pretty sure
> OpenOffice does do this. How are you mounting the Samba server from
> the Ubuntu boxes ? CIFSFS does pass along byte range locks.
> 
> Jeremy.
> 
Jeremy--

Thanks for helping me.

>From /etc/fstab:
//samba1/vol22/sam/vol22  cifs
rw,user,credentials=/[hidden],uid=doug,gid=data  0   0

Doing some poking in man files I found a reference to -o mand for fcntl.
 Would it help to add that to fstab? Where? Or should it go in 
the server's fstab? Or both?

Thanks so much, Jeremy!

:- Doug.



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Re: What affects file locking?

2008-08-13 Thread Doug Germann
Doug Germann <76066.515  CompuServe.com> writes:


> Jeremy writes:
> Ok, deny_none should conflict with deny_write, so you should
> see "someone else has this file open" between WinXP and
> the Ubuntu clients.
> 
> However, for UNIX clients they need to provide mutual exclusion
> using byte range locks (the traditional UNIX way) not deny
> modes. I'm not sure if OpenOffice on Ubuntu does this (it
> should).
> 
> Jeremy.
> 
Jeremy--

Many thanks.

You are right--between Ubuntu and WinXP, the files are locked appropriately.

But how do I get these byte-range locks between the Ubuntu clients? I have
searched in Google and on Ubuntuforums without luck.

Thanks, Jeremy!

:- Doug.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Re: What affects file locking?

2008-08-12 Thread Doug Germann
Doug Germann <76066.515  CompuServe.com> writes:

On Tue, 2008-08-12 at 17:27 -0700, Jeremy Allison wrote:
> Normally what you call "file locking" in this case is really access 
exclusion
> ie. share modes. Use smbstatus on the server to see what open modes 
the
> clients are currently using.
> 
> Jeremy.

Jeremy--

Thanks! Had not thought of using smbstatus. 

What is happening is that the Ubuntu clients are establishing a lock of

deny_none, and the WinXP client is establishing deny_write. 

I have tried changing oplocks and kernel oplocks to yes, and all else to

the defaults shown here, but there is no change in this behavior:
http://www.physiol.ox.ac.uk/Computing/Online_Documentation/
using_samba/ch05_05.htmll

What else should I try, please?

:- Doug.



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Re: What affects file locking?

2008-08-07 Thread Doug Germann
John Drescher  gmail.com> writes:

> 
> On Thu, Aug 7, 2008 at 9:16 PM, Doug Germann <76066.515  compuserve.com>
wrote:
> > Hi--
> >
> > We are in a production environment with one WinXP box and several linux
boxes.
> >
> > We have discovered that the WinXP and linux boxes seem to respect each 
other's
> > file locks, but that the linux boxes do not respect each other's locks. In 
other
> > words, box 1 can have a file open, and at the same time box 2 can open it 
and
> > edit and save the file.
> >
> > We have smb.conf set with level2 oplocks yes, kernel oplocks no, and 
oplocks no.
> > When we first noticed the problem the last two were set to yes. The change 
has
> > made the locks work sometimes, but not reliably.
> >
> > Are there other things besides the oplocks and the smb.conf file which can
> > affect file locking? How would you trouble shoot this?
> >
> 
> Are the linux machines sharing the file using samba and mounting the

> share using cifs?
> 
> John

Yes. From fstab:
//samba1/doug2/sam/doug2  cifs 
  
rw,user,credentials=/[blanked],
uid=doug,gid=doug   0   0

:- Doug.


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] What affects file locking?

2008-08-07 Thread Doug Germann
Hi--

We are in a production environment with one WinXP box and several linux boxes.

We have discovered that the WinXP and linux boxes seem to respect each other's
file locks, but that the linux boxes do not respect each other's locks. In other
words, box 1 can have a file open, and at the same time box 2 can open it and
edit and save the file.

We have smb.conf set with level2 oplocks yes, kernel oplocks no, and oplocks no.
When we first noticed the problem the last two were set to yes. The change has
made the locks work sometimes, but not reliably.

Are there other things besides the oplocks and the smb.conf file which can
affect file locking? How would you trouble shoot this?

Thanks!

:- Doug.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Ubuntu 8.04 breaks samba file locking

2008-08-04 Thread Doug Germann
Just upgraded Saturday from Ubuntu 7.10 to 8.04.01. File locking in Samba is now
broken, meaning two different users can have the same file open at the same time
and edit it.

Server is RedHat 9.0 running Samba 2.2.7a-security-rollup-fix. This has been
working well for us for several years. Have one WinXP box accessing the server
using OOo 2.0. Have another couple of Win95 boxes.

In addition, have one Ubunutu 6.06 box, and three other 8.04 boxes.

It appears the XP and the 6.06 box lock files so the other cannot edit them
while one has them open, but the 8.04 boxes, running OOo 2.4 can access and edit
and save these files, thus causing havoc.

The linux clients mount via cifs, such as this line from /etc/fstab:
//samba1/vol22/sam/vol22  cifs   
rw,user,credentials=/[blanked],uid=doug,gid=data  0   0


This is a production environment.

Could it be a mis-match between the version of samba on the server and the one
on the clients?

Can anybody suggest a solution or at least a trouble-shooting procedure?

Thanks!


:- Doug. 

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba