Re: save-entropy race in 10-STABLE (was: -CURRENT)?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01.05.2015 01:21, Dimitry Andric wrote:

 First of all, I should not write messages after 12 hours working day
in the end of the week. Of course, I have 10-STABLE on this server.
So, mailing list is not appropriate, sorry. But problem is true one.

>> % sudo grep -R save-entropy /etc /var/cron/tabs /etc/crontab:*/11
>> *       *       *       *       operator 
>> /usr/libexec/save-entropy %
>> 
>> Nothing wrong!
> 
> Ok, and what does /var/log/cron say about it?  Any chance there
> might be two instances of the cron daemon running?
% sudo ps -ax | grep cron
 1457  -  Ss        0:02.46 /usr/sbin/cron -s
 9980  0  S+        0:00.00 grep cron
%

But in logs command is mentioned twice sometimes (note 03:03)!

May  1 02:00:00 onlyone /usr/sbin/cron[93867]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 02:11:00 onlyone /usr/sbin/cron[94254]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 02:22:00 onlyone /usr/sbin/cron[94289]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 02:33:00 onlyone /usr/sbin/cron[94400]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 02:44:00 onlyone /usr/sbin/cron[94512]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 03:03:25 onlyone /usr/sbin/cron[94636]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 03:03:25 onlyone /usr/sbin/cron[94632]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 03:11:00 onlyone /usr/sbin/cron[95113]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 03:22:00 onlyone /usr/sbin/cron[95146]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 03:33:00 onlyone /usr/sbin/cron[95252]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 03:44:00 onlyone /usr/sbin/cron[96168]: (operator) CMD
(/usr/libexec/save-entropy)
May  1 03:55:00 onlyone /usr/sbin/cron[96279]: (operator) CMD
(/usr/libexec/save-entropy)


 And with "cut | uniq -c" magic I found second command with same
problem: /usr/libexec/atrun

 Again, about every second day it is executed twice at same time.

 Logs show, that it is NOT happen with every "save-entropy" or "atrun"
execution, only as often as I get these "save-entropy" complains.

- -- 
// Lev Serebryakov AKA Black Lion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQJ8BAEBCgBmBQJVQ0mqXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF
QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EeP6bcP/jEwzFw2nTdCdjnZELSsv+g3
FCB9XSk8jnfYemO4NGIQb5CF0Yc0wt3RFTHS3r9j+qSCKW01IEukPM5nPP1s8hwy
4HP0xO997UtgyzIdIVNFVd2ynAECK+dRYEAIHH3k9RZmaHM+ele3JHZXRyedz0n1
A/uDyR2uiV6+qOqVm3wjhNPKUjauqpbcifDjgFeFiICLubMYzce8KfxrOByiV/Sq
1SilpL0L/V4Bw93s2whV6zCW/1ZmGH8vzYWkjC0IVIDpMFaj2Mmj3H4DqerJ3XeN
GLuesziKEH6T83EwrfR9P5rmapanKmvL9qHB/tPeuG1Ozm0yfw9T8xEj59irPalv
Qiuh4BCNQ1NkOqGM5NndrWhxMvlQmTVQIKBv3ByrYeQHXr877XwNdEqkjFwS5C8o
HigFgHV/PZLiAuh+/xbCUIAcOTAwK0bJxA1Veb3Egxrhqs30NDqQc4kFJWRB6x47
9Wk/5aK8YJKIzbbmEsP1QFqNEDRuB4e97hVzs8RjUy/r5Amq+TynnSApklhKbkft
HiLI8ZIU2C7KtFlLhW6OxEB3AYNuZhsjmscWOqKnQDGQCP+PCVIf+Tl7R/gWgJ1L
x6xsLJ0m+pLbHOG3lSijl3tJc5xMNTeBjwvkUqxRhPPqC/NUuO6pWes/W8YEifsi
ikZ2YxUIPagHOnThhlDU
=AVMj
-----END PGP SIGNATURE-----