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
I created a new windows service using CreateService. You can pass a service configuration which includes the filed ErrorControl. It supports the following values:
I tried to create a windows service with ErrorIgnore, which has the underlying uint32-value 0 - which is also go's zero-value.
CreateService sees that value, assumes that it's not populated, and replaces it with ErrorNormal (1).
There is no workaround (that I can see) to configure ErrorIgnore with the go API.
The only option is to install the service and then edit the registry-key at r\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<service> with the name ErrorControl.
What did you expect to see?
I expect the service to have the correct ErrorControl type.
If this can't be fixed due to backwards compatibility reasons, at least the goDoc should mention the issue and provide an alternative way of configuring this.
The text was updated successfully, but these errors were encountered:
go1.15
What did you do?
I created a new windows service using CreateService. You can pass a service configuration which includes the filed
ErrorControl
. It supports the following values:I tried to create a windows service with
ErrorIgnore
, which has the underlying uint32-value0
- which is also go's zero-value.CreateService sees that value, assumes that it's not populated, and replaces it with ErrorNormal (1).
There is no workaround (that I can see) to configure
ErrorIgnore
with the go API.The only option is to install the service and then edit the registry-key at
r\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<service>
with the nameErrorControl
.What did you expect to see?
I expect the service to have the correct ErrorControl type.
If this can't be fixed due to backwards compatibility reasons, at least the goDoc should mention the issue and provide an alternative way of configuring this.
The text was updated successfully, but these errors were encountered: