Adam Stokes wrote:
So I am trying to figure out the best way to create identifiers on a
per-machine basis.
Identifier for use in the file name? I think your right, RHN ID if
it's there, perhaps FQDN if it's there and not
"localhost.localdomain",
and then some MD5 hash if nothing else. For RHN ID, tack something
like "RHNID" to the front of the ID so that we can distinguish it
from
an MD5 hash or whatever new scheme we come up with in the
future.
Yea I think I'll add the checks for at least RHNID and if hostname is
not localhost we'll use that. Good idea.
Additionally, I've been thinking that it would be good if we
attach
this kind of information to core dumps (like RHN ID, and hostname, and
ticket #, etc), into a file (or files) in the tarball that contains
the
core dump so that we aren't limited to just the information we can fit
in a file name. Thoughts?
Yea I was thinking about this too, perhaps some kind of metadeta that
has that type of information in it. So far I only have one plugin
written for fastback but netdump is next and I believe just one file
that has the above information in it is necessary.
I'll know more about what I'm saying when I get some more code
written :)
--
__ __
.-----.| |_.-----.| |--.-----.-----.
|__ --|| _| _ || <| -__|__ --|
|_____||____|_____||__|__|_____|_____|
.----------------------------------.
( ajs(a)redhat.com || 919.754.4187 )
`----------------------------------'