Trying to start the same jail more than once results in the .id file being blown away i.e. /var/run/jail_name.id Causes problems with ezjail-admin list being unable to report the status if a jail is mistakenly started more than once.
Created attachment 169586 [details] Stop removing jail.id files when startup fails The diff is quite simple: rc.d/jail used to create the file when a jail started, but after the change to use config files, that was expanded to also remove the file when startup failed. The fix is simply not to do that.
A commit references this bug: Author: jamie Date: Sat Apr 23 16:23:01 UTC 2016 New revision: 298516 URL: https://svnweb.freebsd.org/changeset/base/298516 Log: Don't remove the /var/run/jail_name.id file if a jail fails to start. This messes up ezjail (and possibly others), when attempting to start a jail that already exists. PR: 208806 Reviewed by: tj MFC after: 5 days Changes: head/etc/rc.d/jail
A commit references this bug: Author: jamie Date: Thu Apr 28 01:31:07 UTC 2016 New revision: 298728 URL: https://svnweb.freebsd.org/changeset/base/298728 Log: MFC r298516: Don't remove the /var/run/jail_name.id file if a jail fails to start. This messes up ezjail (and possibly others), when attempting to start a jail that already exists. PR: 208806 Reviewed by: tj Changes: _U stable/10/ stable/10/etc/rc.d/jail