tree: 66635c4e2b393fe09d269244d291cad30dc31c56 [path history] [tgz]
  1. activation/
  2. daemon/
  3. dbus/
  4. journal/


Build Status godoc

Go bindings to systemd. The project has several packages:

  • activation - for writing and using socket activation from Go
  • 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
  • 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:


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. 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.


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


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

<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
    <policy user="root">
        <allow eavesdrop="true"/>
        <allow eavesdrop="true" send_destination="*"/>


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


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