Ask Your Question
0

Node command looks for executable specifically at /usr/sbin

asked 2013-08-19 07:06:21 -0500

PanStav gravatar image

Installed Fedora 19 just today, am very pleased at the interface..

yum install npm, 103 files downloaded, installed and cleaned after. 'npm' command works fine, i manage to install my dependencies, but 'node' command doesn't work, it doesn't find the executable at '/usr/sbin/node'.

cd over to /usr/sbin and it really doesn't have any node exec.

but /usr/bin does - /usr/bin/node is there. working just fine..

$PATH includes both /usr/sbin and /usr/bin.. so what am missing?

cp /usr/sbin/node to /usr/sbin/node and 'node' command does work now, but why didn't it find it at /usr/bin?

edit retag flag offensive close merge delete

Comments

Hello,

First, why do you insist on having node in /usr/sbin rather than /usr/bin/? I guess node can be launched by any user of your system.

Second, copying a binary manually from one place to another is really not the right solution, and it's even totally insane (what will happen when there'll be an update of the package). I'd advice you to remove the binary you copied in /usr/sbin/ and trying to understand the problem instead of using "workaround".

baptistemm gravatar imagebaptistemm ( 2013-08-19 07:28:18 -0500 )edit

I guess i got used to /usr/bin, wasn't aware of /usr/sbin at all, still, wonder why node wants it specifically there.. Regarding copying binary, sorry i wasn't clear, i copied the soft link, not the binary itself

PanStav gravatar imagePanStav ( 2013-08-19 09:10:22 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2013-08-19 07:17:45 -0500

baptistemm gravatar image

updated 2013-08-19 07:29:05 -0500

Hello,

Did you try opening a new terminal to see if wasn't just the cache not refreshed in the current terminal. What does return which node in a new terminal?

Regards

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-08-19 07:06:21 -0500

Seen: 830 times

Last updated: Aug 19 '13