[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9C22AC43-6E0E-4CEE-ACA6-9CE07B4DACC7@gmail.com>
Date: Wed, 27 Aug 2014 18:36:44 -0500
From: Brent Cook <busterb@...il.com>
To: musl@...ts.openwall.com
Subject: Re: static build and dlopen
On Aug 27, 2014, at 6:24 PM, Laurent Bercot <ska-dietlibc@...rnet.org> wrote:
>> Node.js spends a lot of time throwing uncaught exceptions; I suspect
>> transitioning to S5 will be less common than node just dying.
>
> Then it's all the more reason to *not* run it as process 1.
> If Node.js dies unexpectedly, you want to restart it automatically,
> or at least to reboot; you do not want a kernel panic and a
> maintenance call.
>
>
>> Perhaps this would be ok with a stateless netbooted ramdisk as a
>> root fs.
>
> Kernel + libc + Node + all the needed node modules, netbooted ?
> Now I know why the terminals at my train station are so slow. :P
>
> --
> Laurent
>
IIRC the pfsense ands m0n0wall firewalls run PHP as process 1, so I
guess something like this is not unheard of. But, they do run from a
ramdisk as well.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
