Thanks for the suggestion, but dmidecode is not portable and is super
unreliable since it depends on upstream hardware vendors setting
reasonable values. Even running on a sample of 8-10 models of
motherboards all from the same vendor I get vastly different results
from dmidecode. I'd strongly
Adrian,
The Host sFlow agent exports UUIDs (and is compatible with Ganglia 3.2+).
http://blog.sflow.com/2011/07/ganglia-32-released.html
The daemon relies on command utilities invoked at startup to find the UUID (for
reasons of portability that Dave mentioned). You could take a look at the
I think the more general point here (and has come up in other contexts
such as mobile phones) is that sometimes neither IP nor reverse DNS make
sense and people would like sending something else to be 'smoother' (as
opposed to hacky/spoofy).
My experience with vendor data hasn't given me warm
I 100% agree that we should be able to use some sort of unique and
persistent way to identify hosts, but I don't think that dmidecode is
the way to do it. Generating a UUID once and then persisting it in a
file would be my preference, but I think that more generally if we were
to allow a user
On 08/01/2013 10:23 AM, Peter Phaal wrote:
Adrian,
The Host sFlow agent exports UUIDs (and is compatible with Ganglia 3.2+).
http://blog.sflow.com/2011/07/ganglia-32-released.html
The daemon relies on command utilities invoked at startup to find the
UUID (for reasons of portability that
