CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!
Dag-Erling Smørgrav
des at des.no
Sat Nov 1 00:33:10 UTC 2014
Manfred Antar <null at 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
writeable.
> 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?
DES
--
Dag-Erling Smørgrav - des at des.no
More information about the freebsd-current
mailing list