due to being "bound" to my laptop for more work than in the past weeks, I noticed my zsysctl.conf settings (limiting RAM usage etc) not being active. After some finding I noticed that zconfigd gets started at boot time, but throws several "top level name kstat in <sysctl var> is invalid" errors (log below). I've booted the machine several times, it's always the same. Killing the zconfigd process gets launchd to restart it and then it's setting the sysctls just fine.
org.openzfsonosx.zconfigd.err:
Looking for service matching net_lundman_zfs_zvol
Found match
Running /usr/local/bin/zsysctl -f /etc/zfs/zsysctl.conf
top level name kstat in kstat.zfs.darwin.tunable.zfs_dirty_data_max is invalid
top level name kstat in kstat.zfs.darwin.tunable.zfs_arc_meta_limit is invalid
top level name kstat in kstat.zfs.darwin.tunable.zfs_arc_max is invalid
Starting the run loop
Looking for service matching net_lundman_zfs_zvol
Starting the run loop
Found match
Running /usr/local/bin/zsysctl -f /etc/zfs/zsysctl.conf
top level name kstat in kstat.zfs.darwin.tunable.zfs_dirty_data_max is invalid
top level name kstat in kstat.zfs.darwin.tunable.zfs_arc_meta_limit is invalid
top level name kstat in kstat.zfs.darwin.tunable.zfs_arc_max is invalid
Looking for service matching net_lundman_zfs_zvol
Found match
Running /usr/local/bin/zsysctl -f /etc/zfs/zsysctl.conf
Starting the run loop
Looking for service matching net_lundman_zfs_zvol
Starting the run loop
Found match
Running /usr/local/bin/zsysctl -f /etc/zfs/zsysctl.conf
top level name kstat in kstat.zfs.darwin.tunable.zfs_dirty_data_max is invalid
top level name kstat in kstat.zfs.darwin.tunable.zfs_arc_meta_limit is invalid
top level name kstat in kstat.zfs.darwin.tunable.zfs_arc_max is invalid
Looking for service matching net_lundman_zfs_zvol
Found match
Running /usr/local/bin/zsysctl -f /etc/zfs/zsysctl.conf
Starting the run loop
org.openzfsonosx.zconfigd.log is empty - until I kill the initial zconfigd process and the new one does it's job.
Machine is a 2019 MacBook Pro 16 running the current OS X 10.15.5 and the latest 1.9.4 package
Couldn't find anything on the forum or on the projects GitHub repo that indicates that this is a known problem?