diff --git a/contrib/Makefile.OpenBSD b/contrib/Makefile.OpenBSD
new file mode 100644
index 0000000..ac2d32e
--- /dev/null
+++ b/contrib/Makefile.OpenBSD
@@ -0,0 +1,7 @@
+build:
+	sh tools/bin/td
+
+install:
+	install build/telodendria $(PREFIX)/bin/telodendria
+	install -D contrib/production.conf $(PREFIX)/share/examples/telodendria/telodendria.conf
+	find man -name 'telodendria*\.[1-8]' -exec install {} $(PREFIX)/{} \;
diff --git a/contrib/telodendria.rc b/contrib/telodendria.rc
deleted file mode 100755
index bd85315..0000000
--- a/contrib/telodendria.rc
+++ /dev/null
@@ -1,11 +0,0 @@
-#!/bin/ksh
-
-daemon="/usr/local/bin/telodendria"
-daemon_timeout=5
-
-. /etc/rc.d/rc.subr
-
-rc_bg=YES
-rc_stop_signal=INT
-
-rc_cmd $1
diff --git a/man/man7/package.7 b/man/man7/package.7
index 3b5a064..a41ace0 100644
--- a/man/man7/package.7
+++ b/man/man7/package.7
@@ -43,14 +43,10 @@ for developers, and so do not need to be installed to the system.
 An init script. People that wish to install Telodendria to their system
 expect it to be integrated enough that Telodendria can be easily started at
 boot, and otherwise managed by the system's daemon tools, be it systemd, or
-another init system. An init script suitable for your platform might be
-available in
-.Pa contrib/ ,
-but if not, it should be trivial to write your own. If you do end up making
-an official package for your system, feel free to submit your init script
-to be added to the
-.Pa contrib/
-directory.
+another init system. Consult your system's documentation for writing an
+init script. Do note that Telodendria does not fork itself to the background;
+the init script should do that. Also note that Telodendria responds to SIGINT,
+so a SIGINT should be sent to stop Telodendria instead of a SIGTERM or SIGKILL.
 .It
 A sample
 .Pa telodendria.conf