-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting script passing arguments on CentOS 7 returns an error #906
Comments
@abernardobr What kind of system are you running on? |
I am using CentOS Linux release 7.0.1406 (Core) |
Sorry, I am not having read the content carefully, never mind. |
@Tjatse there is also another error that I am running into on doing an "npm test"
|
okay. |
@Tjatse any news? We are about to go to production with CentOS 7 and anything that will give more stability would be great. Tks. |
@abernardobr sorry, it took me too much time to get the ISO. if (process.argv.indexOf('-s') > -1) {
for(var key in console){
var code = key.charCodeAt(0);
if(code >= 97 && code <= 122){
console[key] = function(){};
}
}
} The test failed because PM2 test suite ignoring the |
OK great @Tjatse tks The one that worries me the most is the first problem! For now I am using a grunt script to change my files instead of detecting via the script arguments. But since we are using CentOS 7 it would be great to run all the tests to see that it is working fine. So I am going to run the tests and let you know. |
Got the fix. Tks @Tjatse. |
@Tjatse I have downloaded the latest version of pm2 and tried to run npm test again. Now in a directory that does not have in the path node_modules. Intalled in /test/pm2
|
OS: CentOS Linux release 7.0.1406 (Core)
node version: v0.11.14
pm2 version: 0.12.2
start script: start.js
pm2 command: pm2 start start.js --name server –i max --error logs/server.err.log --output logs/server.out.log -- -s prod
Returns the following error:
The text was updated successfully, but these errors were encountered: