weird save-entropy behaviour

2009-11-15 Thread Ed Jobs
Greetings. Yesterday, i noticed a very weird behaviour on my computer (which is running 8.0-RC3 btw. The shells were not responding and the load was insane, and constantly going up. At the time i managed to lock myself out, the load was 84 and growing (i have a screenshot if anyone is

Re: weird save-entropy behaviour

2009-11-15 Thread Mel Flynn
On Sunday 15 November 2009 17:30:02 Ed Jobs wrote: Yesterday, i noticed a very weird behaviour on my computer (which is running 8.0-RC3 btw. The shells were not responding and the load was insane, and constantly going up. At the time i managed to lock myself out, the load was 84 and growing

Re: weird save-entropy behaviour

2009-11-15 Thread Ed Jobs
On Monday 16 November 2009 00:12, Mel Flynn wrote: Did the operator uid change or perhaps shared with another uid? Check both `id operator` and `id 2`. Secondly, why did this stop? Seems like a weird question to ask, but since this script is supposed to run every 11 minutes, there should

Re: weird save-entropy behaviour

2009-11-15 Thread Mel Flynn
On Sunday 15 November 2009 23:38:10 Ed Jobs wrote: On Monday 16 November 2009 00:12, Mel Flynn wrote: Did the operator uid change or perhaps shared with another uid? Check both `id operator` and `id 2`. Secondly, why did this stop? Seems like a weird question to ask, but since this

Re: weird save-entropy behaviour

2009-11-15 Thread 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. Unlesssince