anchor.diff:  If you have the Java Development Kit (JDK) installed, you can view live Daemons with the `jps` command.
   Live Daemons appear under the name `GradleDaemon`. Because this command uses the JDK, you can view Daemons
   running any version of Gradle.
  +
  +== Enable
  +
  +Gradle enables the Daemon by default since Gradle 3.0. If your project doesn't use the
  +Daemon, you can enable it for a single build with the `--daemon` flag when you run a build:
  +
  +====
  +[listing.terminal]
  +----
  +$ gradle <task> --daemon
  +----
  +====
  +
  +This flag overrides any settings that disable the Daemon in your project or user `gradle.properties` files.
  +
  +To enable the Daemon by default in older Gradle versions, add the following setting to the
  +`gradle.properties` file in the project root or your Gradle user home:
  +
  +====
  +.gradle.properties
  +[source,properties]
  +----
  +org.gradle.daemon=true
  +----
  +====
  +
  +[[sec:disabling_the_daemon]]
  +== Disable
  +
  +You can disable the Daemon in multiple ways.
  +
  +=== Disable for a Build
  +
  +To disable the Daemon for a single build, pass the `--no-daemon` flag when you run a build:
  +
  +====
  +[listing.terminal]
  +----
  +$ gradle <task> --nodaemon
  +----
  +====
  +
  +This flag overrides any settings that enable the Daemon in your project or user `gradle.properties` files.
  +
  +=== Disable for a Project
  +
  +To disable the Daemon for all builds of a project, add `org.gradle.daemon=false` to
  +the `gradle.properties` file in the project root.
  +
  +=== Disable for a User
  +
  +On Windows, this command disables the Daemon for the current user:
  +
  +[source]
  +----
  +(if not exist "%USERPROFILE%/.gradle" mkdir "%USERPROFILE%/.gradle") && (echo. >> "%USERPROFILE%/.gradle/gradle.properties" && echo org.gradle.daemon=false >> "%USERPROFILE%/.gradle/gradle.properties")
  +----
  +
  +On UNIX-like operating systems, the following Bash shell command disables the Daemon for the current user:
  +
  +[source,bash]
  +----
  +mkdir -p ~/.gradle && echo "org.gradle.daemon=false" >> ~/.gradle/gradle.properties
  +----
  +
  +=== Disable Globally
  +
  +There are two recommended ways to disable the Daemon globally across an environment:
  +
  +* add `org.gradle.daemon=false` to the `<GRADLE_USER_HOME>/gradle.properties` file
  +* add the flag `-Dorg.gradle.daemon=false` to the `GRADLE_OPTS` environment variable
  +
  +[[sec:stopping_an_existing_daemon]]
  +== Stop
  +
  +It can be helpful to stop the Daemon when troubleshooting or debugging a failure.
  +Daemons automatically stop given any of the following conditions:
  +
  +* available system memory is low
  +* the Daemon has been idle for 3 hours
  +
  +To stop running Daemon processes, use the following command:
  +
  +====
  +[listing.terminal]
  +----
  +$ gradle --stop
  +----
  +====
  +
  +This terminates all Daemon processes started with the same version of Gradle used to execute the command.
  +
  +You can also kill Daemons manually with your operating system. To find the PIDs for all Daemons regardless of Gradle version,
  +see <<gradle_daemon.adoc#find_all_daemons,Find all Daemons>>.
   
   [[sec:tools_and_ides]]
   == Tools & IDEs
  
positive.code: Please see <<build_environment.adoc#build_environment,the build environment documentation>> for details.
  
  [[sec:what_can_go_wrong_with_daemon]]
  === What can go wrong with Daemon?
  
  User build scripts and third party plugins can destabilize the Daemon through memory leaks, poor resource management,
  and global state corruption. Failing to close files after reading and writing is a common cause.
  
negative.code: The Daemon enables in-memory caching across builds. This includes classes for plugins and build scripts.
  Similarly, the Daemon maintains in-memory caches of build data such as the hashes of task inputs and outputs for incremental builds.
  
  == Performance Monitoring
  
  Gradle actively monitors heap usage to detect memory leaks in the Daemon.
  