Date: Mon, 16 Nov 2009 01:37:52 +0200 From: Ed Jobs <oloringr@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: weird save-entropy behaviour Message-ID: <200911160137.52555.oloringr@gmail.com> In-Reply-To: <200911152358.57050.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> References: <200911151830.02578.oloringr@gmail.com> <200911160038.10993.oloringr@gmail.com> <200911152358.57050.mel.flynn%2Bfbsd.questions@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Monday 16 November 2009 00:58, Mel Flynn wrote: > Does the cron log (/var/log/cron) show that it was run as operator around > the time it started? > /usr/sbin/cron[47350]: (operator) CMD (/usr/libexec/save-entropy) > > Even if it wasn't, I don't see a reason for such a buildup. Unless....since > stdin isn't sending anything, it could be the scripts wait indefinitely for > user confirmation, then finally get killed off by some limit. There should > be some hint at that in /var/log/messages around 5:50. > The script should probably do mv -f in line 76. > you were right. there was something at the messages. Nov 15 05:50:49 hostname sshd[1126]: error: accept: Software caused connection abort Nov 15 05:50:49 hostname last message repeated 6 times weird. the only thing in auth.log about sshd[1126] is: Nov 13 12:31:51 hostname sshd[1126]: Server listening on :: port 22. Nov 13 12:31:51 hostname sshd[1126]: Server listening on 0.0.0.0 port 22. and the message that was in the messages log too. -- Real programmers don't document. If it was hard to write, it should be hard to understand. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAksAkNAACgkQBPpdVEWKA31i9wCg0kxB/oD/o8BDW/1zrfMExFcY hLkAnj9RPszwUXyenlMQswSp/z/xrGCL =68cC -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200911160137.52555.oloringr>