git: 77e1ccbee3ed - main - rc: implement parallel boot

[Alastair Hogge]

On 2021-03-08 15:16, Cy Schubert wrote:
> In message <74fde23ead6719ac4e56dacb51bca6ed at bayofrum.net>, Chris Rees 
> writes:
>> Forgot to CC the actual author!
>>
>> On 2021-02-23 17:03, Chris Rees wrote:
>> > Hi,
>> >
>> > On 23 February 2021 10:27:34 GMT, Baptiste Daroussin <bapt at FreeBSD.org>
>> > wrote:
>> >> The branch main has been updated by bapt:
>> >>
>> >> URL:
>> >> https://cgit.FreeBSD.org/src/commit/?id=77e1ccbee3ed6c837929e4e232fd07f95b
>> fc8294
>> >>
>> >> commit 77e1ccbee3ed6c837929e4e232fd07f95bfc8294
>> >> Author:     Rick Parrish <unitrunker at gmail.com>
>> >> AuthorDate: 2021-02-07 06:15:21 +0000
>> >> Commit:     Baptiste Daroussin <bapt at FreeBSD.org>
>> >> CommitDate: 2021-02-23 10:16:53 +0000
>> >>
>> >>    rc: implement parallel boot
>> >>
>> >>    take advantage of the rcorder -p argument to implement parallel
>> >>    booting in rc.
>> >>
>> >>    According to the author non scientific tests:
>> >>    on a Core 2 Duo with spinning disk:
>> >>
>> >>    | Services enabled | before | after | saving |
>> >>    | 0                | 8s     | 8s    | 0      |
>> >>    | 1                | 13s    | 13s   | 0      |
>> >>    | 2                | 17s    | 13s   | 5      |
>> >>    | 3                | 23s    | 13s   | 10     |
>> >>    | 4                | 28s    | 13s   | 15     |
>> >>    | 5                | 33s    | 13s   | 20     |
>> >>
>> >>    PR:             249192
>> >>    MFC after:      3 weeks
>> >> ---
>> >> libexec/rc/rc | 49 ++++++++++++++++++++++++++++++++++---------------
>> >> 1 file changed, 34 insertions(+), 15 deletions(-)
>> >>
>> >> diff --git a/libexec/rc/rc b/libexec/rc/rc
>> >> index 35db4a850516..722d7fe35884 100644
>> >> --- a/libexec/rc/rc
>> >> +++ b/libexec/rc/rc
>> >> @@ -91,19 +91,31 @@ if ! [ -e ${firstboot_sentinel} ]; then
>> >> 	skip_firstboot="-s firstboot"
>> >> fi
>> >>
>> >> +# rc_parallel_start default is "NO"
>> >> +rc_parallel_start=${rc_parallel_start:-NO}
>> >
>> > Should this go in defaults/rc.conf?
>>
>> I think this should be in defaults/rc.conf-- the load_rc_config line is
>> above it.
>>
>> Incidentally, is the plan for this to go into 13 *and* 12, or just 13?
>> It's an exciting step!
> 
> If this does go into 13 or 12, it should be tested in -CURRENT for longer 
> than three weeks. Probably six weeks.

mountd on my NAS fails to load because unbound (via ports) is not yet
responding to any name queries:

[...]
Starting mountd.
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
direwolf.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host direwolf.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
nova.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host nova.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
deimos.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host deimos.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
koto.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host koto.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: bad exports list line '/exports
-maproot': no valid entries
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
direwolf.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host direwolf.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
nova.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host nova.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
deimos.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host deimos.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: can't get address info for host
koto.local.
Mar  8 02:35:13 fafnir mountd[67654]: bad host koto.local., skipping
Mar  8 02:35:13 fafnir mountd[67654]: bad exports list line 'V4:
/exports direwolf.local. nova.local. deimos.local. koto.local.': no
valid entries
Starting nfsd.
Mounting late filesystems:.
Starting cron.
Configuring vt: blanktime.
Performing sanity check on sshd configuration.
Starting sshd.
[...]