You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had multiple versions of hyperdrive as I was debugging install, and after hyperdrive fs unmount; hyperdrive stop there were still a bunch of processes runnng. I saw they had pm2 as a common ancestor, which google told me I could:
npm i -g pm2
pm2 kill
Node people probably know the correct procedure but maybe there should be something in the docs about it? Or just make the existing stop subcommand clean up more thoroughly?
The text was updated successfully, but these errors were encountered:
Thanks @edrex. hyperdrive stop should do a full cleanup (it calls pm2.delete internally, which to my understanding should remove all traces of the process). I've noticed that this can bug out unfortunately, so I'll dig in and try to figure out where it's going wrong.
I'd rather make sure hyperdrive stop doesn't leave behind any stragglers rather than document the pm2-based cleanup. Not sure why that's happening, but it's happening to both you and Tod so definitely keeping this open.
I had multiple versions of hyperdrive as I was debugging install, and after
hyperdrive fs unmount; hyperdrive stop
there were still a bunch of processes runnng. I saw they had pm2 as a common ancestor, which google told me I could:Node people probably know the correct procedure but maybe there should be something in the docs about it? Or just make the existing
stop
subcommand clean up more thoroughly?The text was updated successfully, but these errors were encountered: