From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] autofs
Date: Fri, 3 Jun 2011 17:06:49 +0200 [thread overview]
Message-ID: <201106031706.49544.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4DE8DA34.7060205@binarywings.net>
Apparently, though unproven, at 14:57 on Friday 03 June 2011, Florian Philipp
did opine thusly:
> Am 03.06.2011 14:25, schrieb Alan McKinnon:
> > Apparently, though unproven, at 14:18 on Friday 03 June 2011, Volker
> > Armin
> >
> > Hemmann did opine thusly:
> >> On Friday 03 June 2011 13:37:54 Stéphane Guedon wrote:
> >>> On Friday 03 June 2011 12:55:58 Alan McKinnon wrote:
> >>>> Apparently, though unproven, at 12:44 on Friday 03 June 2011, Stéphane
> >>>> Guedon
>
> >>>> did opine thusly:
> [...]
>
> >>>> The point is that NFS was not designed with laptops and other devices
> >>>> that can be disconnected in mind. It was designed for secure LANs that
> >>>> do not change much, and laptops present issues that are not easy to
> >>>> solve.
>
> [...]
>
> >>> Nfs hasn't been designed for laptop, it's ok. But, appart from coda
> >>> (which has a file size limit of 1 giga, so, useless in home
> >>> networking), I know nothing that is fit for network file-sharing for
> >>> laptop (the laptop isn't the server of course).
> >>>
> >>> I search a solution for that since years !
> >>
> >> samba?
> >
> > +1
> >
> > Samba works nicely for ad-hoc connections, the kind of thing Windows
> > clients would do. And it's a lot more tolerant of connections going away
> > than NFS.
>
> I always was under the impression that NFS is more fault-tolerant on the
> network because of its usage of stateless UDP connections whereas CIFS
> usually freezes when the connection is lost. In the end, both issue an
> IO error, usually crashing an unprepared application. So, in which
> regard performs CIFS better with interrupted connections?
I find that when an NFS server disappears from the client's view, the only
thing that brings it back is making the server visible again. True, there are
options that modify this behaviour (hard, soft) but they come with their own
risks as described in the man page.
Trying to unmount an NFS mount with no server is painful, and all too easy to
do if you carry your laptop to a meeting room in another building.
CIFS can usually at least be killed (depending on how it's mounted) - a
kioslave in konqueror for example is easy to kill.
Neither option is well suited for laptops IMO but on balance CIFS tends to be
easier for the user to deal with.
> That being said, I always use NFS over TCP because of performance issues
> with UDP and wireless LAN.
Smart move. I genuinely feel that the use-case for NFS over UDP has largely
gone away in these modern times and TCP is the better choice for normal use.
OT, but the same applies to auth systems i.e. tacacs vs radius
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-06-03 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 10:44 [gentoo-user] autofs Stéphane Guedon
2011-06-03 10:55 ` Alan McKinnon
2011-06-03 11:37 ` Stéphane Guedon
2011-06-03 12:18 ` Volker Armin Hemmann
2011-06-03 12:25 ` Alan McKinnon
2011-06-03 12:57 ` Florian Philipp
2011-06-03 15:06 ` Alan McKinnon [this message]
2011-06-04 0:40 ` William Kenworthy
2011-06-04 15:10 ` Stéphane Guedon
2011-06-04 21:11 ` Stroller
2011-06-05 9:13 ` Alan McKinnon
2011-06-03 12:18 ` pk
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=201106031706.49544.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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