Disable process cleanup
See original GitHub issueDescribe the bug Our build process starts a bazel server on each run but the runner kills the process on cleanup. I want the server to stay around.
To Reproduce Steps to reproduce the behavior:
- Start a background process in a job
Complete job
steps kills the process
Expected behavior
I expect some kind of ability to disable this behavior. I see process.clean
but have no idea how to modify that variable.
Runner Version and Platform
linux-x64-2.267.1
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
How to Fix Too Many Background Processes Running on a ...
Right-click on any process you want to disable and select the Disable option in the context menu. Disabling Startup Processes on Task Manager....
Read more >How to Remove Unwanted Computer Processes
1. Press "Ctrl-Shift-Esc" to open the Task Manager. · 2. Click the "Processes" tab. · 3. Right-click any active process and select "End...
Read more >Fix: Too Many Background Processes on Your Windows PC
1. Clean up the Windows Startup · 2. Terminate background processes using Task Manager · 3. Remove third-party software services from the Windows ......
Read more >4 Solutions to Fix Too Many Background Processes in ...
Reduce Background Processes Using Task Manager ... You can press Ctrl + Shift + Esc keyboard shortcut to open Task Manager in Windows...
Read more >How to Close Unneccessary Processes in Windows 10
Method 1: Adjusting the Power Settings · Method 2: Disabling Windows Tips and Tricks · Method 3: Uninstalling Bloatware · Method 4: Lower...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
RUNNER_TRACKING_ID="" && ./yourtool
before starting your process, then the process you start should not get killed by the runner.Adding this in front the command solved the problem. RUNNER_TRACKING_ID=“” &&
Changed this
forever start app.js
toRUNNER_TRACKING_ID="" && forever start app.js
@TingluoHuang you saved my day.