Linux NFS development
 help / color / mirror / Atom feed
From: "Ingmar" <i2a@gmx.net>
To: nfs@lists.sourceforge.net
Subject: NFS file .lock problem?
Date: Thu, 4 Jan 2007 19:25:01 +0100	[thread overview]
Message-ID: <20070104181136.M28899@quicknet.nl> (raw)

Hi All,

I am having a problem with the Openoffice.org suite and am guessing it has something to do
with NFS.

I am using NFS to mount my home dir, and Writer it will hang as soon as you (for example)
remove the ruler check from the document interface.

When using another account with an local/"on disk" home dir there is no problem.

Something similar occurs with aMule, it is unable to write a lock file.

Are there any special options needed by NFS to export or mount the directory.

My current export and mount lines are:

/* /etc/exports */
/home/i2a          192.168.0.21(rw,sync)

/* /etc/fstab */
192.168.0.254:/home/i2a  /home/i2a  nfs  rw,retrans=3,intr,noac


Thanks and regards,
  Ingmar

-------------------------------------------------------------------------------
unfair competition, n.:
	Selling cheaper than we do.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-01-04 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 18:25 Ingmar [this message]
2007-01-05 12:10 ` NFS file .lock problem? Trond Myklebust

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=20070104181136.M28899@quicknet.nl \
    --to=i2a@gmx.net \
    --cc=nfs@lists.sourceforge.net \
    /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