Also show the status of the hardware random number generator ("RNGD") at the services.cgi page in the WebUI. Before, this was only shown at the entropy.cgi page, which was a bit inconsistent. Already submitted a patch for this, but it contained some errors, so I have to go through it again. This bug is just a reminder. :-)
Send in second patch a few days ago.
Link to the patch: https://patchwork.ipfire.org/patch/1575/ @Michael: In case anything is wrong with it, let me know. :-) No rush.
@Michael: Please have a look at that patch when it suits.
Done. Please see my feedback on the mailing list.
For the records, the mailing list post is here: https://lists.ipfire.org/pipermail/development/2018-March/004202.html And yes, 700 PID files are quite stange. Will try to develop a patch here and send it upstream (might take a while)...
Waiting for C121 since rng has been updated there.
I think this fell through the cracks... ping?
I will copy Arne so that he can merge this into c161.
Resetting back to ASSIGNED as the patch did not made it into C161. I will take care of it for C162 - sorry for the delay.
Created attachment 1076 [details] working diff for Core 169, as installed (line numbers may be inaccurate) I've modified my existing services.cgi on Core 169, per attachment. Line numbers may differ from the git source.
As of Core 170, services.cgi is radically different from Core 169, and I haven't determined the needed mods.
Created attachment 1107 [details] working (modified) services.cgi for Core171
Created attachment 1126 [details] patch for services.cgi based on next 1e8334707
rng-tools has been converted from a core program to an addon as per bug 12900 This means that when rng-tools is installed as an addon it will now be shown in the addon services status table.
https://blog.ipfire.org/post/ipfire-2-27-core-update-174-is-available-for-testing
Tested this on my vm testbed with CU174 Testing and I can confirm that when rng-tools is installed as an addon it now shows up in the addon services status table. This confirms that this bug has been fixed.
https://blog.ipfire.org/post/ipfire-2-27-core-update-174-released