Closed abmusse closed 6 years ago
Original comment by christophe LALEVEE (Bitbucket: lalevee, GitHub: Unknown).
Works fine ! Thank you.
Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt).
Hello @lalevee ,
You can work around the issue by changing the default user id to 0 --
File:
/QOpenSys/QIBM/ProdData/OPS/Node6/lib/node_modules/npm/lib/config/defaults.js
Line 213:
user: process.platform === 'win32' ? 0 : 'nobody',
-->
user: 0,
Root cause:
setuid() on PASE can not accept a 'nobody' parameter.
Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).
Unless I am missing something this isn't related to this project (Node.js db connector) and is instead a general Node.js issue.
Would probably be best to log a PMR.
Note IBM has updated the RFE for open sourcing the Node.js port to have a status of "under consideration" so one might conclude that in the future we will have a repo to log these issues vs doing a PMR.
Original report by christophe LALEVEE (Bitbucket: lalevee, GitHub: Unknown).
Trying to use npm (node.js 6.9.1, npm 3.10.8) with QSECOFR user profile (remote ssh), I get following error
Doing the same with another user profile (*SECOFR class) works fine: