From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RPtW3-00069f-Nw for garchives@archives.gentoo.org; Mon, 14 Nov 2011 10:11:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AAFD421C0EA; Mon, 14 Nov 2011 10:11:32 +0000 (UTC) Received: from cai.gentoo (unknown [61.135.152.218]) by pigeon.gentoo.org (Postfix) with ESMTP id E48D821C0D2 for ; Mon, 14 Nov 2011 10:10:23 +0000 (UTC) Received: from [127.0.0.1] (cai.gentoo [127.0.0.1]) by cai.gentoo (8.14.5/8.14.5) with ESMTP id pAEAADwg010246 for ; Mon, 14 Nov 2011 18:10:14 +0800 Message-ID: <4EC0E905.9050200@fedoraproject.org> Date: Mon, 14 Nov 2011 18:10:13 +0800 From: microcai User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111111 Thunderbird/8.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] The LIGHTEST web server (just for serving files)? References: <4EBE38F3.2000005@binarywings.net> <201111121155.41045.michaelkintzios@gmail.com> <20111112131152.GA18475@ksp.sk> In-Reply-To: X-Enigmail-Version: 1.3.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5F1D91A13E1E5F025D6DACEA" X-Archives-Salt: 38492db3-ccf9-4264-b138-f064b943a247 X-Archives-Hash: a38e9543312cce58e366c769f8d5b882 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5F1D91A13E1E5F025D6DACEA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable http://code.google.com/p/bashttpd/ run with systemd or xinetd =E4=BA=8E 2011=E5=B9=B411=E6=9C=8814=E6=97=A5 18:05, J. Roeleveld =E5=86=99= =E9=81=93: > 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 'maste= r' >>> server share the distfiles dir via NFS? >>> >>> So, the question now becomes: what's the drawback/benefit of NFS-shar= ing >>> 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... >=20 > 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) >=20 >> Otherwise it works well, esp. when mounted ro on the clients, however >> for distfiles it might make sense to allow the clients download and sa= ve >> 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... >=20 > Locking works correctly, have had 5 machines share the same NFS-shared > distfiles and all downloading the source-files. >=20 >> And with NFS the clients won't duplicate the files in their own >> distfiles directories ;) >=20 > Big plus, for me :) >=20 > -- > Joost >=20 >=20 --------------enig5F1D91A13E1E5F025D6DACEA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iQEcBAEBAgAGBQJOwOkFAAoJEKT4Uz7oTANZBtcH/RCDzV6SrXrTg6+ZDMcyveNX oTOJvsgpkSXgxXg7xZqiiyenMsA/LIzNQRbkd4r56Xmh2Ntu9nsIrvcL6GXV/Ldu QupZ9MG+HXHMLVvqWHzL5oAODsia4YWd5JhpLIVvXYWfHHxApn7I0Tk7nC8rXmRG b8sYf2XZvWdGMknJDjZUDGId3QYYS4anC1TakYfKupgUmNoS9kHUmAD9+wEt2YCR njx0bNY/xqJ9hr6BoWcELA7upteIouwCU9Png45vlOISb3oClSBlLmJDj6jJlswt FfyQws+o5zcJDoRXOHVU3+TSXto7GKipdKvgcTjrG5WTAN/LMH3bLsatGIruYDE= =KxVH -----END PGP SIGNATURE----- --------------enig5F1D91A13E1E5F025D6DACEA--