The ezjail rc script:
1. starts the jail first
2. -> calls /etc/rc in the jail
3. -> runs /etc/rc.d/zfs (and any other rc scripts which might depend on a /zfs path being mounted)
4. Finally after the jail is started the ezjail rc script runs 'zfs jail' to attach the datasets.
This ordering makes the use of startup scripts impossible in the jail which depend on the ZFS dataset being jailed.
I'm not sure how to fix this without using a post_start script to restart rc services or to rework /etc/rc.d/jail to:
1. start the jail
2. zfs jail datasets
3. jexec run the startcmd
I think the only sane thing is to fix /etc/rc.d/jail. I'm logging this as a tracking/discussion issue though.
Moving this to "open" since maintainer was notified and there's no patch to apply with the timeout.
This this problem still relevant for the current systems?
Same question: Is this still relevant?