From: Pascal Bourguignon <spam@mouse-potato.com>
Subject: Re: how to work with unreliable filesystems?
Date: Thu, 12 Jan 2006 18:55:37 +0100 [thread overview]
Message-ID: <87slrt5o12.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: mailman.819.1137074824.26925.help-gnu-emacs@gnu.org
Joakim Verona <joakim@verona.se> writes:
> I have a smb filesystem mounted over a shaky vpn connection.
> Much of the time this works, but if the share hangs for some reason,
> emacs also stops responding, waiting for the share to come back.
>
> I currently solve this by unmounting/remounting the filesystem, but
> its all very inconvenient.
>
> It would be neat if a directory hierarchy could be marked "unstable"
> and using copying instead of direct writes, much as Tramp works.
>
> I guess this would ideally be handled at the os level, but I have
> twiddled mount paramters back and forth to no avail.
>
> Any hints are apreciated.
Perhaps you should use the coda file system. It's a distributed
shared file system that is able to continue to work in disconnected
mode, and when the servers recover their connectivity, they
synchronize the changes.
http://www.coda.cs.cmu.edu/
--
__Pascal Bourguignon__ http://www.informatimago.com/
The world will now reboot. don't bother saving your artefacts.
next parent reply other threads:[~2006-01-12 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.819.1137074824.26925.help-gnu-emacs@gnu.org>
2006-01-12 17:55 ` Pascal Bourguignon [this message]
2006-01-12 10:58 how to work with unreliable filesystems? Joakim Verona
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87slrt5o12.fsf@thalassa.informatimago.com \
--to=spam@mouse-potato.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).