This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Colm Buckley, Lukasa, Theodore Tso, alex, christian.heimes, doko, dstufft, larry, lemburg, martin.panter, matejcik, ned.deily, python-dev, rhettinger, skrah, thomas-petazzoni, vstinner, ztane
Date 2016-06-08.08:44:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
To see how long it takes to initialize urandom pool, you can grep your kernel logs. On my physical PC with real hardware, interruptions etc. it's quite fast: 5 seconds.

-- Logs begin at mar. 2016-01-26 07:54:37 CET, ...
juin 06 18:34:47 smithers kernel: random: systemd urandom read with 2 bits of entropy available
juin 06 18:34:52 smithers kernel: random: nonblocking pool is initialized

I get that the "kernel: random: systemd urandom read with 2 bits of entropy available" message comes from the kernel when systemd reads from /dev/urandom whereas the pool is not initialized yet.
Date User Action Args
2016-06-08 08:44:56vstinnersetrecipients: + vstinner, lemburg, rhettinger, doko, larry, christian.heimes, matejcik, ned.deily, alex, skrah, python-dev, martin.panter, ztane, dstufft, Lukasa, thomas-petazzoni, Colm Buckley, Theodore Tso
2016-06-08 08:44:56vstinnersetmessageid: <>
2016-06-08 08:44:56vstinnerlinkissue26839 messages
2016-06-08 08:44:56vstinnercreate