←back to thread

CPU-X: CPU-Z for Linux

(thetumultuousunicornofdarkness.github.io)
170 points nateb2022 | 9 comments | 07 Jul 25 13:52 UTC | HN request time: 1.289s | source | bottom
1. DrillShopper ◴[07 Jul 25 16:33 UTC] No.44492043[source]▶
It would really be nice to not have to require a daemon to make this program useful
replies(5): >>44492205 #>>44492304 #>>44492481 #>>44493217 #>>44493449 #
2. DeepYogurt ◴[07 Jul 25 16:50 UTC] No.44492205[source]▶
Ya. The joy of cpu-z is that its a single small binary.
replies(1): >>44494563 #
3. dmitrygr ◴[07 Jul 25 16:58 UTC] No.44492304[source]▶

   $ man dmidecode
4. preisschild ◴[07 Jul 25 17:14 UTC] No.44492481[source]▶
At least in the Flatpak, it can be started by just clicking the "Start daemon" button.
5. nateb2022 ◴[07 Jul 25 18:20 UTC] No.44493217[source]▶
c.f. https://github.com/TheTumultuousUnicornOfDarkness/CPU-X/wiki...

the daemon separates userspace from root domain, and ensures that the code running with root privileges is very small and easily auditable

replies(1): >>44495172 #
6. whalesalad ◴[07 Jul 25 18:45 UTC] No.44493449[source]▶
I use it without the daemon. I don't even know what the daemon does.
7. lmz ◴[07 Jul 25 20:51 UTC] No.44494563[source]▶
I wouldn't read too deeply into that. I'm pretty sure cpu-z bundles a driver that is unpacked and installed at runtime (search for 'cpuz sys')
8. __turbobrew__ ◴[07 Jul 25 22:14 UTC] No.44495172[source]▶
Maybe I am dumb, but why does it have to be a daemon? Why not have the user process fork off the privileged binary to collect data and return the results through stdout?
replies(1): >>44495409 #
9. unaindz ◴[07 Jul 25 22:54 UTC] No.44495409{3}[source]▶
Forking a process is not free and starting one every hundred of a millisecond* seems very expensive. *I'm do not know which frequency it updates the data but it's usually 1 sec to 0.1 sec.