Date: Sat, 21 Sep 2013 12:46:56 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-current@freebsd.org Subject: Re: sysctl: unknown oid 'kern.random.sys.harvest.interrupt Message-ID: <20130921124656.795536d0@gumby.homeunix.com> In-Reply-To: <20130921031424.GA3069@direwolf.aux.io> References: <20130916172139.GA1297@devbox.vnode.local> <20130921031424.GA3069@direwolf.aux.io>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 21 Sep 2013 11:14:29 +0800
Alastair Hogge wrote:
> On 2013-09-16 Mon 19:21:39 +0200, Joel Dahl wrote:
> > Hi,
>
> Hi,
>
> > I noticed the following during boot on a machine running HEAD from
> > today:
>
> I have noticed this since the recent work to /sys/dev/random
>
> > Entropy harvesting:sysctl: unknown oid
> > 'kern.random.sys.harvest.interrupt': No such file or directory
> > interruptssysctl: unknown oid 'kern.random.sys.harvest.ethernet':
> > No such file or directory ethernetsysctl: unknown oid
> > 'kern.random.sys.harvest.point_to_point': No such file or directory
> > point_to_point kickstart.
> >
> > Known problem?
It looks like /etc/rc.d/initrandom is no longer correctly checking for
whether the software generator is in use, so it tries to set sysctls
that don't exist. Those partiticular warnings look harmless.
It might be that writing to /dev/random which occurs immediatly after is
causing the problem. Try commenting out the following:
# First pass at reseeding /dev/random.
#
case ${entropy_file} in
[Nn][Oo] | '')
;;
*)
if [ -w /dev/random ]; then
feed_dev_random "${entropy_file}"
fi
;;
esac
better_than_nothing
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130921124656.795536d0>