See bug 1240031 for a discussion of the technical challenges specifically for Windows.

Comment on attachment 8787210 [details] Daemonize taskcluster-worker Looks okay... but we probably should implement SIGTERM properly.

Commits pushed to master at https://github.com/taskcluster/taskcluster-worker https://github.com/taskcluster/taskcluster-worker/commit/cfccf8da8946aecc605e413fa8707ed69f65d22c Bug 1298801: Includes the daemon command. r=jonasfj This commits introduces the ability for taskcluster-worker to run as a daemon. Before running it, you need to install it as a daemon, with the "install" command: $ taskcluster-worker daemon install --engine macosx --logging-level info The --engine argument is mandatory for the install command. To start the daemon, run: $ taskcluster-worker daemon start To stop it: $ taskcluster-worker daemon stop And to uninstall it: $ taskcluster-worker daemon remove Remember taskcluster-worker reads taskcluster credentials from environment variables. You need to make sure taskcluster-worker daemon has these environment variables set. https://github.com/taskcluster/taskcluster-worker/commit/fe30c7b9290a4625338c6360fb798af0ee3ec7e5 Merge pull request #100 from walac/daemonize Bug 1298801: Includes the daemon command. r=jonasfj