linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rahul Nabar <rpnabar@gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS and file locking for use with sqllite
Date: Fri, 13 Aug 2010 16:33:15 -0500	[thread overview]
Message-ID: <AANLkTimqTvgyvvjP2R12wsdpZRs10T+YAtUGw7u6pxWZ@mail.gmail.com> (raw)
In-Reply-To: <0C88B758-1DE8-4CFB-9546-A30104009A12@oracle.com>

On Fri, Aug 13, 2010 at 4:15 PM, Chuck Lever <chuck.lever@oracle.com> wrote:
>
> It's really not clear what is meant by this vague warning.  Maybe you should ask for details from the sqlite development community.

Thanks Chuck! The warning seemed pretty vague to me as well. Just
thought I'd doublecheck if there was something obvious I was missing.
Thanks for your comments.

>
> You have two choices on Linux clients:  "lock" and "nolock".  They control whether file locks appear to other clients or not.  I assume >your applications cares about serialization with processes only on the same client where it is running.  Mount options almost certainly >do not matter in this case.
>

I do have locking enabled. I'm not using "nolock" as a option and I
have lockd daemon running.

-- 
Rahul

  reply	other threads:[~2010-08-13 21:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 20:54 NFS and file locking for use with sqllite Rahul Nabar
2010-08-13 21:15 ` Chuck Lever
2010-08-13 21:33   ` Rahul Nabar [this message]
     [not found]     ` <AANLkTimqTvgyvvjP2R12wsdpZRs10T+YAtUGw7u6pxWZ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-13 22:09       ` Risto Bell
2010-08-13 22:34         ` Vasily Tarasov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimqTvgyvvjP2R12wsdpZRs10T+YAtUGw7u6pxWZ@mail.gmail.com \
    --to=rpnabar@gmail.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).