1 |
There is a very small web server called "thttpd" which is very |
2 |
lightweight and lets start serving files very quickly. |
3 |
It runs on my home router machine with an old Pentium CPU and several |
4 |
megabytes of RAM and seems to consume about 500 kb of it. |
5 |
|
6 |
Regards, |
7 |
Vladimir |
8 |
|
9 |
On Mon, 14 Nov 2011 09:36:22 -0500 |
10 |
Michael Mol <mikemol@×××××.com> wrote: |
11 |
|
12 |
> Isn't there a kernelland HTTP server? ISTR seeing the option. I don't |
13 |
> know anything about it, though. |
14 |
> |
15 |
> On Mon, Nov 14, 2011 at 5:10 AM, microcai |
16 |
> <microcai@×××××××××××××.org> wrote: |
17 |
> > |
18 |
> > http://code.google.com/p/bashttpd/ |
19 |
> > |
20 |
> > run with systemd or xinetd |
21 |
> > |
22 |
> > |
23 |
> > |
24 |
> > 于 2011年11月14日 18:05, J. Roeleveld 写道: |
25 |
> >> On Sat, November 12, 2011 2:11 pm, YoYo Siska wrote: |
26 |
> >>> On Sat, Nov 12, 2011 at 07:40:08PM +0700, Pandu Poluan wrote: |
27 |
> >>>> During my drive home, something hit my brain: why not have the |
28 |
> >>>> 'master' server share the distfiles dir via NFS? |
29 |
> >>>> |
30 |
> >>>> So, the question now becomes: what's the drawback/benefit of |
31 |
> >>>> NFS-sharing vs |
32 |
> >>>> HTTP-sharing? The scenario is back-end LAN at the office, thus, a |
33 |
> >>>> trusted |
34 |
> >>>> network by definition. |
35 |
> >>> |
36 |
> >>> NFS doesn't like when it looses connection to the server. The only |
37 |
> >>> problems I had ever with NFS were because I forgot to unmout it |
38 |
> >>> before a server restart or when I took a computer (laptop) off |
39 |
> >>> to another network... |
40 |
> >> |
41 |
> >> NFS-shares can work, but these need to be umounted before network |
42 |
> >> goes. If server goes, problems can occur there as well. |
43 |
> >> But that is true with any server/client filesharing. (CIFS/Samba, |
44 |
> >> for instance) |
45 |
> >> |
46 |
> >>> Otherwise it works well, esp. when mounted ro on the clients, |
47 |
> >>> however for distfiles it might make sense to allow the clients |
48 |
> >>> download and save tarballs that are not there yet ;), though I |
49 |
> >>> never used it with many computer emerging/downloading same same |
50 |
> >>> stuff, so can't say if locking etc works correctly... |
51 |
> >> |
52 |
> >> Locking works correctly, have had 5 machines share the same |
53 |
> >> NFS-shared distfiles and all downloading the source-files. |
54 |
> >> |
55 |
> >>> And with NFS the clients won't duplicate the files in their own |
56 |
> >>> distfiles directories ;) |
57 |
> >> |
58 |
> >> Big plus, for me :) |
59 |
> >> |
60 |
> >> -- |
61 |
> >> Joost |
62 |
> >> |
63 |
> >> |
64 |
> > |
65 |
> > |
66 |
> > |
67 |
> |
68 |
> |
69 |
> |
70 |
> -- |
71 |
> :wq |
72 |
> |
73 |
> |
74 |
|
75 |
|
76 |
----- |
77 |
<v_2e@×××.net> |