Linux NFS development
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: how to check if file locking is working?
Date: Thu, 03 May 2007 15:36:55 +0200	[thread overview]
Message-ID: <4639E577.6090201@wpkg.org> (raw)
In-Reply-To: <1178002901.5588.11.camel@heimdal.trondhjem.org>

Trond Myklebust schrieb:

>>>> Kernel option on a client or server, export options on the server, mount 
>>>> options on the client etc.?
>>> nfsroot does not support NFSv4 at this time.
>> Hmm, I didn't say anything about nfsroot, did I?
>>
>> I merely did a chroot over NFSv4, and some apps don't work well then.
> 
> Sorry. I misread your mail. The easiest way to check basic locking would
> be to run the connectathon suite. See
> http://www.connectathon.org/#technologies

It looks like it's not working when I mount an export as NVSv4.
What can be wrong?


-- 
Tomasz Chmielewski
http://wpkg.org

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2007-05-03 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 11:29 how to check if file locking is working? Tomasz Chmielewski
2007-04-26 12:19 ` Tomasz Chmielewski
2007-04-29 21:27   ` Trond Myklebust
2007-05-01  6:24     ` Tomasz Chmielewski
2007-05-01  7:01       ` Trond Myklebust
2007-05-03 13:36         ` Tomasz Chmielewski [this message]

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=4639E577.6090201@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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