weird save-entropy behaviour

[Ed Jobs]

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20091115/631fd0c6/attachment.pgp