_exec_afterstart start to 1 but all other counter start at 0 Fix: See the attached patch How-To-Repeat: _exec_afterstart0 isn't executed
Responsible Changed From-To: freebsd-bugs->freebsd-rc Over to maintainer(s).
The example in /etc/defaults/rc.conf is related to afterstart0. # grep afterstart /etc/defaults/rc.conf #jail_example_exec_afterstart0="/bin/sh command" -- David BERARD --------------------------------------- NFrance Conseil david(at)nfrance.com GPG|PGP KeyId 0x7FC68EB8 GPG|PGP Key http://tinyurl.com/gpgdavid --------------------------------------- * No electrons were harmed in * * the transmission of this email *
State Changed From-To: open->analyzed This is a pickle indeed. Moany people will have used it starting from 1, since the original code was intended to count from 1; see r159072. However, the prestart code added in r191620 counts from 0. The patch at http://www.bayofrum.net/~crees/patches/142973.diff makes it count from 0, but still work with a warning if the user has started at 1. I will talk to the developers concerned.
I am committing a different patch, since the underlying rc file has changed. I've dispensed with the warning since there's already a warning against using rc-conf-based jail parameters.
A commit references this bug: Author: jamie Date: Mon Jan 25 22:14:31 UTC 2016 New revision: 294749 URL: https://svnweb.freebsd.org/changeset/base/294749 Log: Allow the (old rc-style) exec_afterstart jail parameters to start numbering at 0, like exec_prestart and the others do. Make param0 optional, i.e. still look for param1. PR: 142973 MFC after: 3 days Changes: head/etc/rc.d/jail
A commit references this bug: Author: jamie Date: Thu Jan 28 00:41:07 UTC 2016 New revision: 294964 URL: https://svnweb.freebsd.org/changeset/base/294964 Log: MFC r294749: Allow the (old rc-style) exec_afterstart jail parameters to start numbering at 0, like exec_prestart and the others do. Make param0 optional, i.e. still look for param1. PR: 142973 Changes: _U stable/10/ stable/10/etc/rc.d/jail