Windows - Investigate Torus as a Service

Windows, like many operating systems, offer a robust service model for starting, stopping, and restarting long running back ground processes such as the Torus Daemon.

It would be awesome if Torus could be registered as a service during install (#212). However, one thing for us to sort out is how this would work on a per-user basis (to copy the security model that we use in *nix of tying the socket to the current user/group).

Another thing to consider is how this would work in a Windows Server environment where you'd most likely want to run Torus as a machine wide service similar to the default setup we have on Debian/Ubuntu and RHEL/CentOS with our yum/apt packages via systemd.

Begin by reviewing the installation work in issue #212 and the existing systemd-based setup used by the Debian/Ubuntu and RHEL/CentOS packages. Define how Windows service registration should support both per-user security and machine-wide Windows Server operation; the issue is done when those service models and their installation behavior are specified.

Written by the indexing model from the issue text.