On Sat, 01 Nov 2014 01:33:09 +0100
Dag-Erling Sm〓rgrav <d...@des.no> wrote:
> Manfred Antar <n...@pozo.com> writes:
> > Then for some reason /var started to being mounted mfs.
> > so for me i think it has something to do with the new rc.d startup files.
> > If I have varmfs="NO" and cleanvar_enable="NO" everything works fine.
> Not really. The default for varmfs is AUTO, which mounts a memory file
> system on /var if, after mounting all "early" file systems, /var is not
For me, Manfred's workaround actually helped.
VirtualBox VM [head, r273922, amd64] on stable/10 host [r273847,
In my case, /var is NOT a mount point (root only partition, mounted
rw), but empty mfsvar is forcibly used without Manfred's workaround in
multi user mode.
In single user mode, actual /var (in root partition) appears as before.
So there can be some mis-ordering within rc scripts.
(Remounting of / is delayed? Check for /var too early?)
> > Writing entropy file:random: unblocking device.
> > takes a little longer
> > I changed to entropy_save_sz="4096" in /etc/rc.conf, maybe thats why.
> That shouldn't make any difference. Our /dev/random never blocks once
> it's seeded, and reading 4096 bytes won't take noticeably longer than
> reading 2048 bytes. But it should already be unblocked by then - this
> is on shutdown, right?
For me, it takes nearly 2 minutes each boot after r273872.
No specific rc.conf setting for it.
> Dag-Erling Sm〓rgrav - d...@des.no
> firstname.lastname@example.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
青木 知明 [Tomoaki AOKI]
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"