On Mon, Jan 5, 2015 at 2:43 PM, Aria Stewart <[email protected]> wrote: > >> On Jan 5, 2015, at 5:22 PM, Sam Roberts <[email protected]> wrote: >> >> On Mon, Jan 5, 2015 at 12:54 PM, Aria Stewart <[email protected]> wrote: >>>> If you are setting up a production machine, probably best to install >>>> node as root, and if absolutely necessary to do any npm global >>>> installs (should be rare), run the global installs as root, or with >>>> sudo, and use --unsafe-perm so that scripts run with sufficient privs >>>> to succeed, and so that the ~/.npm/ cache is writeable. >>> >>> As a heads up: --unsafe-perm is the default when run as root. You don't >>> need to specify it. >> >> Good to know. I guess I can understand the rationale... and now I >> know why I occaisonally get reports that running as root and running >> using sudo fail differently. :-( > Nope! sudo's as root too. Should all be the same. If you're not using npm@2, > though, that's where I'd put my blame.
Sorry, Aria, I'm not following you anymore. You just wrote that --unsafe-perm is is the default when running as root. It is NOT the default when running "sudo npm" (sudoing to root). Therefore, running as root and running "sudo root" can behave differently. Am I missing something? -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CACmrRmSwBiGgDn%3D10GE3z%3DEApv8JrXmh856--GxnYhAoPw1WAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
