Arch Killing long running node/npm processes before finishing

[patrickhwood]

hello all,

when i run certian longer processes in node.js/npm, like an update ($ npm update -g) or to search for an npm package ($ npm search elm), it starts the process on my Pine64 A64+ w/ 2 GB board, but then half- or even three-quarters of the way through, it just kills the process before it completes; particularly, i noticed, when it's waiting for info to come back across the 'net through the ethernet port, with —

Killed

then it just gives me the command prompt again, process never completes. this happens no matter how many times i re-try it.

is there anyway to change a setting, somewhere, that will extend the amount of time before these processes are killed? any help would be much appreciated, please. thank you and advance. 

best,

—  faddah

     portland, oregon, u.s.a.

Linux doesn't normally kill processes that run long. Try "dmesg | tail" after the process is killed to see if something like oom is killing it.