Open cyberalex4life opened 9 years ago
Seems like the pid killer isn't working. do you still have ~node~ pids running after?
I checked if there is any node* proccess after and it isn't.
Ok, two node processes are usually started by nodejuice. I saved their pids from gnome-system-monitor, and, after killing nodejuice, I ran ps -p !pid!
This command doesn't show anything after killing nodejuice.
I mention that I use nodejs v0.10.25 from ubuntu repositories, and it is linked in symlinks folder to node
Ah, so this sounds like it IS working indeed, but there's a side effect output somewhere that's not captured.
I don't know if this is a bug or not, but this is what I get on ubuntu 14.04 amd64 after stopping nodejuice:
Sidekick Server(14854)
Seeker Server(14855) { host: null , port: 8010 , fetch: { host: "localhost" , port: 80 } } { host: null , port: 8002 , delay: 90 , wait: 500 , browser: { navigate: false , scroll: { lkp: "yes" , sync: "yes" , speed: 200 } } , add: true , remove: true , touch: true , access: false , bits: true , save: true , dir: true , ignore: [{ } , { } , { } , { } , { } , { } ] } ^C
nodejuice shuting down... goodbye
Usage: kill [options] [...]
Options: