tg.enumerate(ts);

            for (Thread active : ts) {
                String name = active.getName();
                boolean daemon = active.isDaemon();
                assertTrue(daemon, name + " is no daemon Thread.");
            }
        }

        assertTrue(seen, "Could not find ThreadGroup: " + DefaultArtifactResolver.DaemonThreadCreator.THREADGROUP_NAME);
    }

    @Test

 * plugin that only runs in the daemon would declare the daemon as a target runtime,
 * while a worker action that executes in a worker must declare that it executes in
 * a worker.
 *
 * However, a shared library used by both daemon and worker actions does not necessarily
 * care which runtimes it must execute in. The target runtimes it must support is a function

that can send requests to a Gradle daemon.
Each daemon runs one request at a time. Generally speaking, the daemons only act in response to a request from a client and do not take any action on their own.
There are some background actions that the daemon takes, for example monitoring system memory, watching for file changes or cleaning up caches.
The daemon never runs any user code in the background.

        touch "$pidfile" && chown "$FESS_USER":"$FESS_GROUP" "$pidfile"
    fi

    echo -n $"Starting $prog: "
    # if not running, start it up here, usually something like "daemon $exec"
    daemon --user $FESS_USER --pidfile="$pidfile" $exec -d
    retval=$?
    pid=`ps aux | grep "^${FESS_USER}" | grep "${PROC_NAME}" | sed 's/[\t ]\+/\t/g' | cut -f2`
    if [ -n "$pid" ]; then
        echo $pid > "$pidfile"

fun DistributionTest.distributionReports(): List<FileLocationProvider> = listOf(
    gradleInstallationForTest.gradleUserHomeDir.dir("test-kit-daemon"),
    gradleInstallationForTest.gradleUserHomeDir.dir("kotlin-compiler-daemon"),
    gradleInstallationForTest.daemonRegistry,
)

fun JapicmpTask.japicmpReports(): List<FileLocationProvider> = listOf(richReport.flatMap { it.destinationDir.file(it.reportName) })

  {
    "name": "daemon-messaging",
    "path": "platforms/core-runtime/daemon-messaging",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "daemon-protocol",
    "path": "platforms/core-runtime/daemon-protocol",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "daemon-server",

              ant.include(name: projectDir.toPath().relativize(it.toPath()))
            }
          }
        }

        fileset(dir: "${gradle.gradleUserHomeDir}/daemon/${gradle.gradleVersion}", followsymlinks: false) {
          include(name: "**/daemon-${ProcessHandle.current().pid()}*.log")
        }

        fileset(dir: "${gradle.gradleUserHomeDir}/workers", followsymlinks: false)
      }
    } catch (Exception e) {

    if command -v systemctl >/dev/null; then
        echo "### NOT starting on installation, please execute the following statements to configure fess service to start automatically using systemd"
        echo " sudo systemctl daemon-reload"
        echo " sudo systemctl enable fess.service"
        echo "### You can start fess service by executing"
        echo " sudo systemctl start fess.service"

    elif command -v chkconfig >/dev/null; then

   * This is useful if the given service uses daemon threads, and we want to keep the JVM from
   * exiting immediately on shutdown, instead giving these daemon threads a chance to terminate
   * normally.
   *
   * @param service ExecutorService which uses daemon threads
   * @param terminationTimeout how long to wait for the executor to finish before terminating the
   *     JVM

        // Remove caches that weren't multi-process safe and may be corrupt
        fileSystemOperations.removeDodgyCacheFiles(workerDir.dir("caches"))

        // Remove old daemon log files
        fileSystemOperations.removeDaemonLogFiles(workerDir.dir("daemon"))
    }