rclone/lib/atexit/atexit_other.go

//go:build windows || plan9

package atexit

import (
	"os"

	"github.com/rclone/rclone/lib/exitcode"
)

var exitSignals = []os.Signal{os.Interrupt}

func exitCode(_ os.Signal) int {
	return exitcode.UncategorizedError
}
build: apply gofmt from golang 1.17 2021-09-09 20:25:25 +08:00			`//go:build windows \|\| plan9`
lib/atexit: add SIGTERM to signals which run the exit handlers on unix 2019-02-28 06:49:22 +08:00
			`package atexit`

			`import (`
			`"os"`
atexit: Terminate with non-zero status after receiving signal When rclone received a SIGINT (Ctrl+C) or SIGTERM signal while an atexit function is registered it always terminated with status code 0. Unix convention is to exit with a non-zero status code. Often it's `128 + int(signum), but at least not zero. With this change fatal signals handled by the `atexit` package cause a non-zero exit code. On Unix systems it's `128 + int(signum)` while on other systems, such as Windows, it's always 2 ("error not otherwise categorised"). Resolves #5437. Signed-off-by: Michael Hanselmann <public@hansmi.ch> 2021-07-06 05:51:12 +08:00
			`"github.com/rclone/rclone/lib/exitcode"`
lib/atexit: add SIGTERM to signals which run the exit handlers on unix 2019-02-28 06:49:22 +08:00			`)`

			`var exitSignals = []os.Signal{os.Interrupt}`
atexit: Terminate with non-zero status after receiving signal When rclone received a SIGINT (Ctrl+C) or SIGTERM signal while an atexit function is registered it always terminated with status code 0. Unix convention is to exit with a non-zero status code. Often it's `128 + int(signum), but at least not zero. With this change fatal signals handled by the `atexit` package cause a non-zero exit code. On Unix systems it's `128 + int(signum)` while on other systems, such as Windows, it's always 2 ("error not otherwise categorised"). Resolves #5437. Signed-off-by: Michael Hanselmann <public@hansmi.ch> 2021-07-06 05:51:12 +08:00
			`func exitCode(_ os.Signal) int {`
			`return exitcode.UncategorizedError`
			`}`