systemd: add Conflicts=zfs-import.service

[ggzengel]

For systems with systemd in sysv init compatibility mode you have to prevent that services in /etc/init.d will be executed if there is a equivalent in systemd.
There is zfs-import without a corresponding systemd service. You have to add 'Conflicts=zfs-import.service' to zfs-import-cache.service and zfs-import-scan.service.

[Unit]
Description=Import ZFS pools by cache file
DefaultDependencies=no
Requires=systemd-udev-settle.service
After=systemd-udev-settle.service
After=cryptsetup.target
ConditionPathExists=/etc/zfs/zpool.cache
Conflicts=zfs-import.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=/sbin/modprobe zfs
ExecStart=/sbin/zpool import -c /etc/zfs/zpool.cache -aN
ExecStop=/sbin/zpool export -a

[behlendorf]

@ggzengel could you please open a pull request with the proposed fix. It makes is easier for me to merge, get it reviewed, and properly credit the author.

[ggzengel]

First time I made this with github. Now we have #3838.

[FransUrbo]

I'm slowly starting to understand what you're been on about for the last couple of days :).

So you're saying that that zfs-import.service is auto generated from the /etc/init.d/zfs-import file. And when you install both the SYSV scripts and the systemd services files on the same system and systemd is in charge of starting services (not init), this auto generated service file conflicts with the two existing ones, the zfs-import-cache.service and zfs-import-scan.service??

[ggzengel]

@FransUrbo Exactly. You got it. That's the way systemd will make smooth migration.

I googled about jessie and systemd: Jessie will always use systemd on normal install and will use systemd on upgrade from Wheezy to Jessie.

[ggzengel]

I hope I don't spam too much.
Is this now useful?

[FransUrbo]

Very much so, thanx!

[ggzengel]

better solution in #3839