binctr/vendor/github.com/coreos/go-systemd
Jess Frazelle 94d1cfbfbf
update vendor
Signed-off-by: Jess Frazelle <acidburn@microsoft.com>
2018-09-25 12:27:46 -04:00
..
activation update vendor 2018-09-25 12:27:46 -04:00
daemon update vendor 2018-09-25 12:27:46 -04:00
dbus fix chown and seccomp 2018-03-22 09:22:44 -04:00
examples/activation update vendor 2018-09-25 12:27:46 -04:00
fixtures update vendor 2018-09-25 12:27:46 -04:00
journal update vendor 2018-09-25 12:27:46 -04:00
login1 update vendor 2018-09-25 12:27:46 -04:00
machine1 update vendor 2018-09-25 12:27:46 -04:00
scripts update vendor 2018-09-25 12:27:46 -04:00
sdjournal update vendor 2018-09-25 12:27:46 -04:00
unit update vendor 2018-09-25 12:27:46 -04:00
util update vendor 2018-09-25 12:27:46 -04:00
.travis.yml update vendor 2018-09-25 12:27:46 -04:00
code-of-conduct.md update vendor 2018-03-19 21:36:34 -04:00
CONTRIBUTING.md update vendor 2018-03-19 21:36:34 -04:00
DCO update vendor 2018-03-19 21:36:34 -04:00
Gopkg.toml update vendor 2018-09-25 12:27:46 -04:00
Jenkinsfile update vendor 2018-03-19 21:36:34 -04:00
LICENSE update vendor 2018-03-19 21:36:34 -04:00
NOTICE update vendor 2018-03-19 21:36:34 -04:00
README.md update vendor 2018-09-25 12:27:46 -04:00
test update vendor 2018-03-19 21:36:34 -04:00

go-systemd

Build Status godoc minimum golang 1.5

Go bindings to systemd. The project has several packages:

  • activation - for writing and using socket activation from Go
  • daemon - for notifying systemd of service status changes
  • dbus - for starting/stopping/inspecting running services and units
  • journal - for writing to systemd's logging service, journald
  • sdjournal - for reading from journald by wrapping its C API
  • login1 - for integration with the systemd logind API
  • machine1 - for registering machines/containers with systemd
  • unit - for (de)serialization and comparison of unit files

Socket Activation

An example HTTP server using socket activation can be quickly set up by following this README on a Linux machine running systemd:

https://github.com/coreos/go-systemd/tree/master/examples/activation/httpserver

systemd Service Notification

The daemon package is an implementation of the sd_notify protocol. It can be used to inform systemd of service start-up completion, watchdog events, and other status changes.

D-Bus

The dbus package connects to the systemd D-Bus API and lets you start, stop and introspect systemd units. The API docs are here:

http://godoc.org/github.com/coreos/go-systemd/dbus

Debugging

Create /etc/dbus-1/system-local.conf that looks like this:

<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
    <policy user="root">
        <allow eavesdrop="true"/>
        <allow eavesdrop="true" send_destination="*"/>
    </policy>
</busconfig>

Journal

Writing to the Journal

Using the pure-Go journal package you can submit journal entries directly to systemd's journal, taking advantage of features like indexed key/value pairs for each log entry.

Reading from the Journal

The sdjournal package provides read access to the journal by wrapping around journald's native C API; consequently it requires cgo and the journal headers to be available.

logind

The login1 package provides functions to integrate with the systemd logind API.

machined

The machine1 package allows interaction with the systemd machined D-Bus API.

Units

The unit package provides various functions for working with systemd unit files.