zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: History corruption (over NFS)
Date: Thu, 10 Feb 2005 18:41:11 +0000	[thread overview]
Message-ID: <1050210184111.ZM22490@candle.brasslantern.com> (raw)
In-Reply-To: <20050210165417.GG30487@ay.vinc17.org>

On Feb 10,  5:54pm, Vincent Lefevre wrote:
}
} I've noticed history corruption (several times) when using screen,
} with the following .screenrc file: the end of the .zhistory file
} gets many null characters. I thought that zsh was using a lock
} mechanism.

My experience has been that this sort of thing occurs when a file is
shortened with e.g. ftruncate(), and is a problem with NFS and not
with whether a locking mechanism is in use.

One thing to check is whether the file on the NFS server actually does
contain those nul bytes, or if it's only the NFS client that sees them.
I vaguely recall that you may need to explicitly specify "noac" in the
NFS mount options, but it's been quite some time since I encountered
this particular problem.


  reply	other threads:[~2005-02-10 18:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 16:54 Vincent Lefevre
2005-02-10 18:41 ` Bart Schaefer [this message]
2005-02-10 23:54   ` Vincent Lefevre
2005-02-14 15:56   ` Vincent Lefevre
2005-02-14 16:24     ` Bart Schaefer
2005-02-15  9:50       ` Vincent Lefevre
2005-02-15 16:15         ` Bart Schaefer
2005-02-14 18:57     ` Wayne Davison
2005-02-14 21:06       ` Seth Kurtzberg
2005-02-14 22:33         ` Wayne Davison
2005-02-15  9:58       ` Vincent Lefevre

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=1050210184111.ZM22490@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).