I am able to work around this by calling windows.ChangeServiceConfig2() directly:

import (
	"github.com/winlabs/gowin32/wrappers"
	"golang.org/x/sys/windows"
	"golang.org/x/sys/windows/svc"
	"golang.org/x/sys/windows/svc/mgr"
)

...

	flag := wrappers.SERVICE_FAILURE_ACTIONS_FLAG{
		FailureActionsOnNonCrashFailures: 1,
	}
	err := windows.ChangeServiceConfig2(s.Handle, windows.SERVICE_CONFIG_FAILURE_ACTIONS_FLAG, (*byte)(unsafe.Pointer(&flag)))
	...

However, it seems like this should also be in the mgr package.

Does this require changing the signature of SetRecoveryActions, or adding a new method?

cc @golang/windows

You could do either of those.SetRecoveryActions currently only takes a list of failure actions (passing SERVICE_CONFIG_FAILURE_ACTIONS to ChangeServiceConfig2), and there's no provision to support any of the other options provided by ChangeServiceConfig2 which are mainly single values and not lists. So, either it would need to change, or a new function could be added.

Hello @craig65535

If you want to have access to the failure actions flag, we can add 2 new methods similar to, for example:

a@spot:~/src/golang.org/x/sys/windows/svc/mgr$ GOOS=windows go doc Service.SetRebootMessage                           
package mgr // import "."

func (s *Service) SetRebootMessage(msg string) error
    SetRebootMessage sets service s reboot message. If msg is "", the reboot
    message is deleted and no message is broadcast.

a@spot:~/src/golang.org/x/sys/windows/svc/mgr$ GOOS=windows go doc Service.RebootMessage
package mgr // import "."

func (s *Service) RebootMessage() (string, error)
    RebootMessage is broadcast to server users before rebooting in response to
    the ComputerReboot service controller action.

a@spot:~/src/golang.org/x/sys/windows/svc/mgr$

Would that work for you?

I did not need this functionality ever. But others contributed code for whatever service parameters they required. I doubt we could support all combinations that are supported by ChangeServiceConfig2 in a general and simple way. So I expect some users to call windows.ChangeServiceConfig2 directly. But it would be nice to have most common parameters supported.

Alex

@alexbrainman Yes, that sounds perfect.

@alexbrainman Yes, that sounds perfect.

Would you like to try to add that code yourself?

Alex

Sure, I can give this one a shot as well.

golang/sys#157

Change https://go.dev/cl/484896 mentions this issue: windows/svc/mgr: add Service.RecoveryActionsOnNonCrashFailures

I propose to add these two methods

// SetRecoveryActionsOnNonCrashFailures sets the failure actions flag. If the
// flag is set to false, recovery actions will only be performed if the service
// terminates without reporting a status of SERVICE_STOPPED. If the flag is set
// to true, recovery actions are also perfomed if the service stops with a
// nonzero exit code.
func (s *Service) SetRecoveryActionsOnNonCrashFailures(flag bool) error


// RecoveryActionsOnNonCrashFailures returns the current value of the failure
// actions flag. If the flag is set to false, recovery actions will only be
// performed if the service terminates without reporting a status of
// SERVICE_STOPPED. If the flag is set to true, recovery actions are also
// perfomed if the service stops with a nonzero exit code.
func (s *Service) RecoveryActionsOnNonCrashFailures() (bool, error)

to the golang.org/x/sys/windows/svc/mgr.Service struct. New methods will allow users set and read SERVICE_FAILURE_ACTIONS_FLAG for the service.

We already have similar Service.RebootMessage / Service.SetRebootMessage, Service.RecoveryActions / Service.SetRecoveryActions and few others.

It is possible to achieve this functionality by calling Windows API directly. See #59016 (comment) for an example. But we decided since we already have similar attributes handled, maybe we can add RecoveryActionsOnNonCrashFailures flag to that list.

Thank you for consideration.

Alex

@bcmills

Just want to make sure that this proposal is not forgotten. I labelled the issue as proposal about month ago. I hope I did not make mistake somewhere.

Thank you for your help.

Alex

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group