@kulak Many thanks for the feedback.

I don't close the issue to keep future feedbacks about working platforms in one place.

❗️ Please, report bugs into a separate issue.

When I try to use in windows 10 I get ".\daemon.go:50:14: undefined: syscall.Credential".

go-daemon is not supported on Windows. Windows has "Windows Services" API infrastructure that's completely different from Unix daemon model. I think there was a separate issue about windows were I made a similar comment.

I would not expect go-daemon to work on Windows. The best you can expect is to be able to compile go-daemon on Windows due to API stubs, but it will not run. So, in the end Windows target is kind of pointless. I higher level abstraction library may incorporate go-daemon and Windows. I am quite sure that this abstraction will loose a lot of capabilities of go-daemon and some of Windows service. For example, go-daemon standard streams can be captured. I don't recall ever working with standard output on windows services. Windows sends service a request to shutdown. The service can request for extension of shutdown time. Linux daemons don't have that.

In the end, it is the best to structure your application to be able to run on Linux and Windows platforms via 2 different top level entry files. That's what I would do.