Skip to content
This repository has been archived by the owner on May 17, 2018. It is now read-only.

cNssm Key based solely on ExeFolder #1

Open
Shwaunk opened this issue Apr 8, 2016 · 0 comments
Open

cNssm Key based solely on ExeFolder #1

Shwaunk opened this issue Apr 8, 2016 · 0 comments

Comments

@Shwaunk
Copy link

Shwaunk commented Apr 8, 2016

Currently the key for the cNssm resource is based solely on the ExeFolder. I feel like a better logic for this is to have ExeFolder, ServiceName and ExeOrBatName all have the key qualifier -- otherwise executables in the same folder cannot be added with two resources or the same executable cannot be added twice as services with different names as two resources.

I have a fix for this but do not have permissions to push my branch and cut a PR.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant