Message267695
| Author |
dstufft |
| Recipients |
Colm Buckley, Lukasa, alex, christian.heimes, doko, dstufft, larry, lemburg, martin.panter, matejcik, ned.deily, python-dev, rhettinger, skrah, thomas-petazzoni, vstinner, ztane |
| Date |
2016年06月07日.15:35:49 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1465313749.54.0.281951571849.issue26839@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Please note: this is *not* just a VM/cloud issue. This is observed on physical standalone systems.
But it should only occur on initial boot I believe? AFAIK all of the major linux vendors have stored a seed file once the machine has been booted and the pool has been initialized to use to seed the pool on subsequent boots. I suppose it's possible that /lib/systemd/system-generators/systemd-crontab-generator is running prior to Debian reseeding the pool from that seed file, but it seems like it should be doing the reseeding as early as possible? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年06月07日 15:35:49 | dstufft | set | recipients:
+ dstufft, lemburg, rhettinger, doko, vstinner, larry, christian.heimes, matejcik, ned.deily, alex, skrah, python-dev, martin.panter, ztane, Lukasa, thomas-petazzoni, Colm Buckley |
| 2016年06月07日 15:35:49 | dstufft | set | messageid: <1465313749.54.0.281951571849.issue26839@psf.upfronthosting.co.za> |
| 2016年06月07日 15:35:49 | dstufft | link | issue26839 messages |
| 2016年06月07日 15:35:49 | dstufft | create |
|