Re: sysctl: unknown oid 'kern.random.sys.harvest.interrupt

On 2013-09-21 Sat 12:46:56 +0100, RW wrote:
> 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

This seems to have worked.  4 successful reboots into multiuser mode.