Quote from: BTC Turkiye on November 04, 2014, 09:04:44 PM

Nevermind. I solved the issue and thought I should let others know.

If you use Ubuntu, the command to start the script is not node gekko but It`s
sudo nodejs gekko

gekko with a standard node.js installation has never required sudo.

ubuntu is doing something wrong to break your node.js if it disabled the node command and changed the command to nodejs

perhaps you should check and confirm that ubuntu isn't adding "node" to your environment / path...

I don't use ubuntu, nor do I know how they like to do things otherwise I'd file a bug with your distro.

commands to check and make sure it's in your path:

Code:

kuzetsa@yurizoku ~ $ which node
/usr/bin/node
kuzetsa@yurizoku ~ $ which nodejs
which: no nodejs in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.9.1)
kuzetsa@yurizoku ~ $

^ I have no idea what that "nodejs" even is, but if it requires sudo to use I'd recommend fixing your path
(and/or possibly uninstalling the ubuntu nodejs all together, since it's naughty and demands more privileges than it needs)

you SHOULD NOT need to use sudo.

If you chose to use gekko via the the ubuntu-provided "nodejs" command, you're doing so at your own risk.