Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Nov 2009 23:58:57 +0100
From:      Mel Flynn <>
Cc:        Ed Jobs <>
Subject:   Re: weird save-entropy behaviour
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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 script is supposed to run every 11 minutes, there should not
> > be a reason for this to stop, if there's a race condition.
> # id operator
> uid=2(operator) gid=5(operator) groups=5(operator)
> # id 2
> uid=2(operator) gid=5(operator) groups=5(operator)
> As for the orer part, why did it stop, i really have no clue. All the
>  messages arrived at root's mailbox at 5:57, tho the date in them said that
>  they were sent at 5:50.
> It's really strange because I was locked out from the computer at 2:29, so
> it's not something I did. and there's nothing that cron runs at that time.

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.

Want to link to this message? Use this URL: <>