From: Clint Adams <clint@zsh.org>
To: martin f krafft <madduck@debian.org>,
482525@bugs.debian.org, zsh-workers@sunsite.dk
Subject: Re: Bug#482525: failure to fcntl-lock history file, takes ages to create interactive session
Date: Sat, 24 May 2008 02:56:58 +0000 [thread overview]
Message-ID: <20080524025658.GB30511@scru.org> (raw)
In-Reply-To: <20080523223034.GM7056@prunille.vinc17.org>
On Sat, May 24, 2008 at 12:30:34AM +0200, Vincent Lefevre wrote:
> Don't you mean -o nohistfcntllock?
No, I meant mount -o nolock on the client to see if the behavior was
consistent with a lock-disabled NFS mount.
next prev parent reply other threads:[~2008-05-24 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080523094636.GA3814@piper.oerlikon.madduck.net>
2008-05-23 13:24 ` Clint Adams
2008-05-23 22:30 ` Vincent Lefevre
2008-05-24 2:56 ` Clint Adams [this message]
2008-05-27 8:32 ` martin f krafft
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=20080524025658.GB30511@scru.org \
--to=clint@zsh.org \
--cc=482525@bugs.debian.org \
--cc=madduck@debian.org \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).