Date: Sun, 11 Oct 2020 15:09:40 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: errors happening with /usr/libexec/save-entropy on 12.1-p10 Message-ID: <20201011150940.6d0f5547@gumby.homeunix.com> In-Reply-To: <20201011030537.GA30207@rpi4.gilescoppice.lan> References: <20201011030537.GA30207@rpi4.gilescoppice.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 11 Oct 2020 04:05:37 +0100 tech-lists wrote: > Hi, > > I've noticed recently in the daily security email that *sometimes* > when this is run out of /etc/crontab on a 12.1-p10 system: > > # Save some entropy so that /dev/random can re-seed on boot. > */11 * * * * operator > /usr/libexec/save-entropy > > that it'll generate an error visible in the security email like this: > > [redacted] kernel log messages: +pid 12995 (dd), uid 2 inumber 2086730 > on /: filesystem full > > (the filesystem has plenty of inodes spare and plenty of space) > > It's the only one I've seen so far (12.1-p10) with this issue. > 12-stable doesn't have this problem, but the If it fails on 12.1 but not on 12-stable that would imply that it's a long standing problem and something was fixed in stable. There's no sign that anything like that happened. I think it's unlikely that this is caused by save-entropy. All it does is dd the output of /dev/random to a file and rotate the files. When you say that there's plenty of space, are you allowing for the fact that the operator user can't write to space reserved for root.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201011150940.6d0f5547>