zfs/init.d at master - zfs - Trustie: Git with trustie

History

Benda Xu 162cc80b81 etc/init.d: decide which variant to use at build time. Let Debian use the sysv-rc variant of the script, even when OpenRC is installed. Unlike on Gentoo, OpenRC on Debian consumes both the sysv-rc scripts and OpenRC ones. ZFS initscripts on Debian should be the sysv-rc version to provide most compatibility and to integrate with the rest of initscripts for dependency tracking. Restrict the substitution in the Makefile to the dedicated list. This construct is inspired by Mo Zhou's detection of the execution shell and follows the strategy of Peter in `6ef28c526b`. As of 2024, the initscripts are mostly relevant on Debian, Gentoo and their derivatives. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Benda Xu <orv@debian.org> Issue #8063 Issue #8204 Issue #8359 Closes #15977		2024-04-08 16:52:24 -07:00
..
.gitignore	Add init script to load keys	2021-12-12 11:17:14 -08:00
README.md	etc/init.d: decide which variant to use at build time.	2024-04-08 16:52:24 -07:00
zfs-import.in	etc/init.d: decide which variant to use at build time.	2024-04-08 16:52:24 -07:00
zfs-load-key.in	etc/init.d: decide which variant to use at build time.	2024-04-08 16:52:24 -07:00
zfs-mount.in	etc/init.d: decide which variant to use at build time.	2024-04-08 16:52:24 -07:00
zfs-share.in	etc/init.d: decide which variant to use at build time.	2024-04-08 16:52:24 -07:00
zfs-zed.in	etc/init.d: decide which variant to use at build time.	2024-04-08 16:52:24 -07:00

README.md

DESCRIPTION These script were written with the primary intention of being portable and usable on as many systems as possible.

This is, in practice, usually not possible. But the intention is there. And it is a good one.

They have been tested successfully on:

* Debian GNU/Linux Bookworm
* Gentoo

SUPPORT If you find that they don't work for your platform, please report this at the OpenZFS issue tracker at https://github.com/openzfs/zfs/issues.

Please include:

* Distribution name
* Distribution version
* Where to find an install CD image
* Architecture

If you have code to share that fixes the problem, that is much better. But please remember to try your best keep portability in mind. If you suspect that what you're writing/modifying won't work on anything else than your distribution, please make sure to put that code in appropriate if/else/fi code.

It currently MUST be bash (or fully compatible) for this to work.

If you're making your own distribution and you want the scripts to work on that, the biggest problem you'll (probably) have is the part at the beginning of the "zfs-functions" file which sets up the logging output.

INSTALLING INIT SCRIPT LINKS To setup the init script links in /etc/rc?.d manually on a Debian GNU/Linux (or derived) system, run the following commands (the order is important!):

update-rc.d zfs-import   start 07 S .       stop 07 0 1 6 .
update-rc.d zfs-load-key start 02 2 3 4 5 . stop 06 0 1 6 .
update-rc.d zfs-mount    start 02 S       . stop 06 0 1 6 .
update-rc.d zfs-zed      start 07 2 3 4 5 . stop 08 0 1 6 .
update-rc.d zfs-share    start 27 2 3 4 5 . stop 05 0 1 6 .

To do the same on RedHat, Fedora and/or CentOS:

chkconfig zfs-import
chkconfig zfs-load-key
chkconfig zfs-mount
chkconfig zfs-zed
chkconfig zfs-share

On Gentoo:

rc-update add zfs-import boot
rc-update add zfs-load-key boot
rc-update add zfs-mount boot
rc-update add zfs-zed default
rc-update add zfs-share default

The idea here is to make sure all of the ZFS filesystems, including possibly separate datasets like /var, are mounted before anything else is started.

Then, ZED, which depends on /var, can be started. It will consume and act on events that occurred before it started. ZED may also play a role in sharing filesystems in the future, so it is important to start before the 'share' service.

Finally, we share filesystems configured with the share* property.