Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 08 Jan 2022 16:26:59 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 261036] [patch] rc.d/jail: Support multiple _startN and _stopN variables
Message-ID:  <bug-261036-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261036

            Bug ID: 261036
           Summary: [patch] rc.d/jail: Support multiple _startN and _stopN
                    variables
           Product: Base System
           Version: 13.0-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: conf
          Assignee: bugs@FreeBSD.org
          Reporter: thomas@gibfest.dk

Created attachment 230822
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D230822&action=
=3Dedit
A patch to support having multiple jail _startN and _stopN commands

Hello,

I've been running with the attached patch for /etc/rc.d/jail for a few years
now.=20

It enables having multiple "jail_jailname_start0" "jail_jailname_start1"
"jail_jailname_start2" etc (and the same for stop) variables when using leg=
acy
variables to configure jails. This is already supported for _prestart,
_poststart, _prestop, and _poststop, but for some reason _start and _stop w=
ere
left out.

In case I missed something and the patch isn't as trivial as I thought then
please let me know or just close this as wontfix and I will keep running wi=
th
the patch locally :)

Thanks! :)

ps. I care about this because I use /etc/rc.conf.d/jail files written by
ansible to configure jails. I prefer it to jail.conf because they can be
written by sysrc and they are easier to maintain from configuration managem=
ent
compared to jail.conf(.d).

--=20
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-261036-227>