service

package

v0.1.0 Latest Latest Go to latest Published: Oct 11, 2022 License: Apache-2.0 Imports: 12 Imported by: 0

Details

Valid go.mod file

The Go module system was introduced in Go 1.11 and is the official dependency management solution for Go.
Redistributable license

Redistributable licenses place minimal restrictions on how software can be used, modified, and redistributed.
Tagged version

Modules with tagged versions give importers more predictable builds.
Stable version

When a project reaches major version v1 it is considered stable.
Learn more about best practices

Repository

github.com/newrelic/infrastructure-agent

Links

Open Source Insights

Documentation ¶

Rendered for

Overview ¶

Index ¶

Variables
func GetCommandPath(svcCmd string) string
func New(arg ...string) (service.Service, error)
func WaitForExitOrTimeout(exitCode <-chan int) error
type Service

Constants ¶

This section is empty.

Variables ¶

View Source

var (
	GracefulExitTimeout    = 10 * time.Second
	GracefulExitTimeoutErr = errors.New("graceful stop time exceeded... forcing stop")
)

Functions ¶

func GetCommandPath ¶

func GetCommandPath(svcCmd string) string

GetCommandPath returns the absolute path of the agent binary that should be run.

func New ¶

func New(arg ...string) (service.Service, error)

func WaitForExitOrTimeout ¶

func WaitForExitOrTimeout(exitCode <-chan int) error

Types ¶

type Service ¶

type Service struct {
	// contains filtered or unexported fields
}

Service is a wrapper object which provides the necessary hooks to start/stop the agent as a service

func (*Service) Shutdown ¶

func (svc *Service) Shutdown(_ service.Service) (err error)

Shutdown is called in Windows only, when the machine is shutting down

func (*Service) Start ¶

func (svc *Service) Start(s service.Service) (err error)

Start is called when the service manager tells us to start

func (*Service) Stop ¶

func (svc *Service) Stop(_ service.Service) (err error)

Stop is called when the service manager commands us to stop By default systemD sends the SIGTERM signal to all the subprocesses, so the agent (child) process will have to handle it in order to property stop (otherwise it just gets killed 'immediately')

Source Files ¶

View all Source files

?	: This menu
/	: Search site
f or F	: Jump to
y or Y	: Canonical URL