Skip to content

Latest commit

 

History

History
107 lines (78 loc) · 3.11 KB

README.md

File metadata and controls

107 lines (78 loc) · 3.11 KB

Init scripts

This directory includes integration for different service management frameworks, so that znapzend works for you automatically (as long as you have set up the dataset retention policies with the znapzendzetup utility).

Since the service manifests contain the absolute path to the znapzend install directory, they are not contained in the prebuilt version. But you can get a copy from github and roll your own by building the project properly or by just manually replacing the tags in the corresponding .in template file to match your existing system layout (replace @BINDIR@ usually with /usr/local/bin to match other setup documentation).

macOS/launchd

For macOS launchd, you can copy the generated org.znapzend.plist file to /Library/LaunchDaemons and then start the daemon with:

launchctl load /Library/LaunchDaemons/org.znapzend.plist

Note: It is recommended to not set the --daemonize flag of znapzend as launchd will lose control of the process. Check out init/org.znapzend.plist.in for an example plist.

To reload the daemon by sending a HUP signal, use this command:

sudo launchctl kill -HUP system/org.znapzend

Solaris/Illumos

For solaris/illumos OSes you can tell configure to install a znapzend service manifest into a particular location (no default imposed) by calling configure with the option like --enable-svcinstall=/var/svc/manifest/site. You can also define the service name (defaults to oep/znapzend) by calling configure with the option like --with-svcname-smf=system/filesystem/zfs/znapzend.

After you have installed the manifest file, verify and import it:

svccfg validate /var/svc/manifest/site/znapzend.xml
svccfg import /var/svc/manifest/site/znapzend.xml

and then enable the service

svcadm enable oep/znapzend

Systemd

For systemd based systems, you can copy the generated znapzend.service file to /etc/systemd/system/ and then enable and start the daemon.

systemctl enable znapzend.service
systemctl start znapzend.service

If you want to set parameters for the znapzend daemon separately from the unit file, copy znapzend.default to /etc/default/znapzend and edit it.

Upstart

For upstart based systems, you can copy the generated znapzend.upstart file to /etc/init/znapzend.conf and start the daemon.

service znapzend start

If you want to set parameters for the znapzend daemon separately from the upstart file, copy znapzend.default to /etc/default/znapzend and edit it.

System V

For systems with SysV-based initscripts, you can copy the generated znapzend.sysv file to /etc/init.d/znapzend and then enable and start the daemon.

For Red Hat systems (RHEL, RHEL derivatives, and Fedora):

chkconfig znapzend on
service znapzend start

For Debian systems:

update-rc.d znapzend defaults
service znapzend start

If you want to set parameters for the znapzend daemon separately from the init script, copy znapzend.default to /etc/default/znapzend and edit it.