You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: