Disable daemon autostarting

Open
#4,904 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
cli

Research direction

Start by tracing how PM2 currently auto-spawns its daemon and how the CLI handles a missing daemon. Define the behavior for an explicitly requested start versus other commands: report that the daemon is not running and quit without starting it. Done means production use can globally prohibit automatic daemon spawning while explicit daemon startup still works.

Written by the indexing model from the issue text.

Description

What's going wrong?

It is not possible to globally prohibit daemon auto-spawning.

It is not good to have rogue daemons in production. Pm2 daemon should be started only if explicitly requested to do so, as it is admin's responsablity to start system services. If the daemon is not running, pm2 should just report it and quit.

Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Unitech/pm2

All issues in Unitech/pm2

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.