When wpmd is started from the console, a Ctrl-C will cleanly stop all services before shutting down.
When wpmd is managed by Windows Task Scheduler and stopped, it is sent some kind of termination signal that is not a Ctrl-C, and ultimately the process is killed without a proper cleanup/shutdown, so all of the wpm-managed services remain running.
I feel that the Ctrl-C behavior is the most intuitive/expected behavior.
Maybe there is a valid argument for the option to leave services running when wpmd terminates, but someone can create another issue if/when that becomes true. :)
When wpmd is started from the console, a Ctrl-C will cleanly stop all services before shutting down.
When wpmd is managed by Windows Task Scheduler and stopped, it is sent some kind of termination signal that is not a Ctrl-C, and ultimately the process is killed without a proper cleanup/shutdown, so all of the wpm-managed services remain running.
I feel that the Ctrl-C behavior is the most intuitive/expected behavior.
Maybe there is a valid argument for the option to leave services running when wpmd terminates, but someone can create another issue if/when that becomes true. :)