On Monday, April 13, 2015 at 1:33:49 AM UTC+2, Aria Stewart wrote:
>
> On Sunday, April 12, 2015 at 7:22:15 PM UTC-4, Guy Dillen wrote:
>>
>> Hi,
>>
>> Until know i have worked with nodejs on Mac and Windows so
>> straightforward installing nodejs from the binaries.
>> Now i need nodejs on Deb
On Sunday, April 12, 2015 at 7:22:15 PM UTC-4, Guy Dillen wrote:
>
> Hi,
>
> Until know i have worked with nodejs on Mac and Windows so straightforward
> installing nodejs from the binaries.
> Now i need nodejs on Debian 32-bit. I'm confused as how to install it on
> Debian:
> - can i just ins
Hi,
Until know i have worked with nodejs on Mac and Windows so straightforward
installing nodejs from the binaries.
Now i need nodejs on Debian 32-bit. I'm confused as how to install it on Debian:
- can i just install the Linux 32 bit binaries?
- or compile nodejs from source?
- or by using a pac
So I'm doing my cluster exactly like this gist:
https://gist.github.com/dickeyxxx/0f535be1ada0ea964cae but whenever the
service is stopped, the worker doesn't receive any message, inside its
file, I'm using process.on("message"), but nothing is coming from the master
--
Job board: http://jobs.nod
On Saturday, April 11, 2015 at 10:46:12 PM UTC-4, Ingwie Phoenix wrote:
> When we now use cluster.isMaster and cluster.isChild… what behaviour could
> be expected from the above structure? I saw C programs doing a fork-in-fork
> mechanism, but not in NodeJS, especially since in this case, a sc
Thanks Daniel
I think that i will put nodes user in the sudo list, restrict commands list
allowed with the sudo file and create some scripts on the server to not
allow users to send custom commands
I will have a look how to sanitize commands
Chris
Le dimanche 12 avril 2015 00:15:42 UTC+2, Dani
