Add the ability to run executable jail.conf and read its stdout.
AbandonedPublic
Actions

Authored by crest_freebsd_rlwinm.de on Tue, Apr 28, 5:49 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Fri, May 8, 2:30 AM

	Unknown Object (File)
	Thu, May 7, 9:57 PM

	Unknown Object (File)
	Wed, May 6, 12:17 PM

	Unknown Object (File)
	Tue, May 5, 7:57 PM

	Unknown Object (File)
	Sun, May 3, 9:12 PM

	Unknown Object (File)
	Fri, May 1, 5:43 PM

	Unknown Object (File)
	Fri, May 1, 2:10 PM

	Unknown Object (File)
	Thu, Apr 30, 3:24 PM

View All 9 Files

Subscribers

imp

Details

Reviewers: None

Summary

The redundancy between similar jails and some dynamic behavior can't
be captured by .include "<pattern>"; alone and still allow
jail -c <name> to start jails without a wrapper.

Take the same way out as automountd(8) and run executable configuration
files. These scripts are expected to write a valid configuration
(snippet) to standard output and return exit status 0.