Graeme Geldenhuys wrote:
On 2013-02-27 16:49, Michael Van Canneyt wrote:
It is better to simply parse
/proc/cpuinfo
and
/proc/PID/*
.... and hope all distros behave the same. My experience with OnGuard
work is that your mileage will vary.
For this sort of thing /proc/pid is the way to go, since- I'm pretty
sure- it's what's used by ps so there are certain things that can't be
changed.
The non-pid stuff, specifically things like /proc/cpuinfo, is far more
of a problem.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
