On Wed, Mar 05, 2008 at 03:22:30PM -0000, Lewis, Rob wrote:
>
> I am using OpenBSD as both client and server. We are running rpc.lockd
> on both client and server sides.
But did you read the manual page? It seems you did not.
OpenBSD NFS clients do not support locking.
-Otto
> Regards
> Robert
>
> Petro-Canada UK Limited,
> 1 London Bridge,
> London,
> SE1 9BG
> Tel: +44 (0) 20 7105 6200
> Fax: +44 (0) 20 7105 6202
> Direct Line: +44 (0) 20 7105 6724
> mobile: +44 (0) 7802 651986
> email: [EMAIL PROTECTED]
>
>
> -----Original Message-----
> From: Otto Moerbeek [mailto:[EMAIL PROTECTED]
> Sent: 05 March 2008 15:20
> To: Lewis, Rob
> Cc: [EMAIL PROTECTED]; [email protected]; Buckley, Nadine; Hughes,
> Adrian; Le Monde, Paul
> Subject: Re: Sendbug
>
> On Wed, Mar 05, 2008 at 01:44:07PM -0000, Lewis, Rob wrote:
>
> > Description:
> >
> > We are having problems getting NFS file locking working
> > correctly. We have tried both NFS version 2 and 3 using both UDP and
> TCP
> > transport mechanisms. Whentwo users access the same file; both have
> the
> > ability to write to that file. Open Office also exhibits this
> behaviour.
> >
> >
> >
> > How-To-Repeat:
> >
> > Mount a shared file system to two different machines. Login as
> > two different users and access a single file from both machines. We
> are
> > using NIS for the user database. This can be replicated on all of our
> > installations.
>
> You do not say if you are using OpenBSD as a client or a server, but
> start with reading man rpc.lockd, especially the BUGS section.
>
> -Otto
>
>
>
> ***********************
>
> This email communication is intended as a private communication for the sole
> use of the primary addressee and those individuals listed for copies in the
> original message. The information contained in this email is private and
> confidential and if you are not an intended recipient you are hereby notified
> that copying, forwarding or other dissemination or distribution of this
> communication by any means is prohibited. If you are not specifically
> authorized to receive this email and if you believe that you received it in
> error please notify the original sender immediately. We honour similar
> requests relating to the privacy of email communications.
