-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
PM2 Fix (again): add pm2_env.unique_id
checking and cleaning
#3626
Conversation
@bugsounet, I just tested your code changes. All looks good except for this one line.
Since this.PM2 is the pm2 index number and it's zero based, you can get the wrong message that PM2 is not in use if MagicMirror happens to be listed first in your managed PM2 process list. Which mine is (and the only).
|
i didn't notice that, i set mine to -1 before looking |
@@ -1,7 +1,7 @@ | |||
const Exec = require("node:child_process").exec; | |||
const Spawn = require("node:child_process").spawn; | |||
const fs = require("node:fs"); | |||
|
|||
const pm2 = require("pm2"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not happy with moving this to top level.
Problem: With this statement pm2 starts already process(es) in the background so people not using pm2 have this unneeded and unwanted processes running, e.g. in a docker container.
So this should only called after Checking PM2 using
as before.
@khassel : ok, i will reverse it. rejas merges it at lightning speed! (it's my fault I should have drafted it) |
continue from #3626 Is it ok for you ?
#3605 : new purpose code with
pm2_env.unique_id
checking