close 466946 # housekeeping while here anyway; cf. #911043 reassign 776597 rng-tools-debian thanks
On Tue, 10 Nov 2020, Trek wrote: > as far as I know, if the daemon does not have files opened for writing, > the system should be able to unmount the filesystem correctly lrwx------ 1 root root 64 Nov 10 20:37 0 -> /dev/null lrwx------ 1 root root 64 Nov 10 20:37 1 -> /dev/null lrwx------ 1 root root 64 Nov 10 20:37 2 -> /dev/null lr-x------ 1 root root 64 Nov 10 20:37 3 -> /dev/hwrng lrwx------ 1 root root 64 Nov 10 20:37 4 -> /dev/random lrwx------ 1 root root 64 Nov 10 20:37 5 -> /run/rngd.pid lrwx------ 1 root root 64 Nov 10 20:37 6 -> 'socket:[954404]' Hmm. Although starting/stopping this is tricky enough already, so I’ll not bother investigating this further. > what I don't know is how the system reacts to a non-responding rngd or > how rngd reacts to a non-responding hwrng device Eh, ouch. This, coupled with needing to detect which device to use, can be tricky… thankfully timeout(1) exists. Thanks, //mirabilos -- 15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
