Re: Error found searching for command node.

Hi Justin,

Not /usr/bin, instead put it in /QOpenSys/usr/bin. The latter is in a case
sensitive file system and, imho, is where the majority of everything should
go.

With that said, and as a side note, I've been pondering why a user's home
directory is in /home/aaron vs. /QOpenSys/home/aaron.

Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces


On Fri, Dec 2, 2016 at 12:13 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

Well, Kevin's solution didn't work. What you're suggesting is manually
creating symlinks in /usr/bin/. I can do that.

I assume that v6 would be the same path as v4, but Node6? I have the v4
path but nothing for v6.




-----Original Message-----
From: Aaron Bartell [mailto:aaronbartell@xxxxxxxxx]
Sent: Friday, December 02, 2016 11:56 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Error found searching for command node.

I just saw Kevin's answer come in after I had typed mine, so the following
will be for scenarios where you'd need to manually set things up (which has
been my case in situations where I have perzl+PowerRuby+5733OPS all
conflicting).

Need to create two symbolic links, one for 'node' and another for 'npm'.
I am fairly certain v0.12.13 had symlinks a little wonky and I'd highly
recommend you get to v4 or v6 (both are now available in 5733OPS). Here's
how you'd set the symlinks for v4.

ln -s /QOpenSys/QIBM/ProdData/OPS/Node4/bin/node /QOpenSys/usr/bin ln -s
/QOpenSys/QIBM/ProdData/OPS/Node4/bin/npm /QOpenSys/usr/bin

Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.