search

oetiker / znapzend

zfs backup with remote capabilities and mbuffer integration.
www.znapzend.org
GNU General Public License v3.0
608 stars 137 forks source link

on macOS znapzend does not startup correct at system startup #356

Closed rwilkey closed 6 years ago

rwilkey commented 6 years ago

Because of how Open ZFS on OSX mounts pools, znapzend starts up before any pools are mounted. This condition causes znapzend to go inactive and will only become active after a HUP signal is sent. This defeats the purpose of running with startup. Also, launchd (macOS startup or init replacement) does not have a mechanism for resolving service dependencies so I haven't figured out how to resolve this).

I did find a solution by patching ZnapZend.pm to die on initialization if there is nothing to do (which is the case if no pools are mounted). Then I can have launchd restart znapzend at some time interval, until the pools become available. This was tested by exporting all the pools then starting up znapzend to observe the effects.

So should I make a pull request and show you my work?

oetiker commented 6 years ago

yes, I think that is a good behavior, please provide a PR

JMoVS commented 6 years ago

this wouldn'T solve my problem s some of my pools are only available at home so if I reboot my macbook, it won't see the pool until possibly a couple of days