Date: Thu, 02 Oct 2014 22:56:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 194105] New: sysutils/ezjail with zfs_datasets does not work with /etc/rc.d/zfs Message-ID: <bug-194105-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194105 Bug ID: 194105 Summary: sysutils/ezjail with zfs_datasets does not work with /etc/rc.d/zfs Product: Ports Tree Version: Latest Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: bdrewery@FreeBSD.org CC: erdgeist@erdgeist.org CC: erdgeist@erdgeist.org 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. --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Maintainers CC'd -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194105-13>