From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] The LIGHTEST web server (just for serving files)?
Date: Mon, 14 Nov 2011 11:05:35 +0100 [thread overview]
Message-ID: <b0719679f494144dbd80e2585a34373b.squirrel@www.antarean.org> (raw)
In-Reply-To: <20111112131152.GA18475@ksp.sk>
On Sat, November 12, 2011 2:11 pm, YoYo Siska wrote:
> On Sat, Nov 12, 2011 at 07:40:08PM +0700, Pandu Poluan wrote:
>> During my drive home, something hit my brain: why not have the 'master'
>> server share the distfiles dir via NFS?
>>
>> So, the question now becomes: what's the drawback/benefit of NFS-sharing
>> vs
>> HTTP-sharing? The scenario is back-end LAN at the office, thus, a
>> trusted
>> network by definition.
>
> NFS doesn't like when it looses connection to the server. The only
> problems I had ever with NFS were because I forgot to unmout it before a
> server restart or when I took a computer (laptop) off to another
> network...
NFS-shares can work, but these need to be umounted before network goes.
If server goes, problems can occur there as well.
But that is true with any server/client filesharing. (CIFS/Samba, for
instance)
> Otherwise it works well, esp. when mounted ro on the clients, however
> for distfiles it might make sense to allow the clients download and save
> tarballs that are not there yet ;), though I never used it with many
> computer emerging/downloading same same stuff, so can't say if locking
> etc works correctly...
Locking works correctly, have had 5 machines share the same NFS-shared
distfiles and all downloading the source-files.
> And with NFS the clients won't duplicate the files in their own
> distfiles directories ;)
Big plus, for me :)
--
Joost
next prev parent reply other threads:[~2011-11-14 10:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 8:24 [gentoo-user] The LIGHTEST web server (just for serving files) ? Pandu Poluan
2011-11-12 8:46 ` Nilesh Govindarajan
2011-11-12 9:01 ` Pandu Poluan
2011-11-12 9:14 ` Florian Philipp
2011-11-12 11:55 ` [gentoo-user] The LIGHTEST web server (just for serving files)? Mick
2011-11-12 12:40 ` Pandu Poluan
2011-11-12 13:01 ` Mick
2011-11-12 13:13 ` Stéphane Guedon
2011-11-12 13:22 ` Pandu Poluan
2011-11-12 13:11 ` YoYo Siska
2011-11-12 13:23 ` Pandu Poluan
2011-11-14 10:05 ` J. Roeleveld [this message]
2011-11-14 10:10 ` microcai
2011-11-14 14:36 ` Michael Mol
2011-11-14 22:01 ` v_2e
2011-11-15 18:40 ` [gentoo-user] " Steven J Long
2011-11-12 13:14 ` [gentoo-user] " Florian Philipp
2011-11-12 13:33 ` Pandu Poluan
2011-11-12 17:05 ` [gentoo-user] " Holger Hoffstaette
2011-11-12 22:01 ` [gentoo-user] " Neil Bothwick
2011-11-13 0:18 ` William Kenworthy
2011-11-12 13:39 ` [gentoo-user] The LIGHTEST web server (just for serving files) ? Ciprian Dorin Craciun
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=b0719679f494144dbd80e2585a34373b.squirrel@www.antarean.org \
--to=joost@antarean.org \
--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