On Fri 18 Jun 2010 at 06:52PM, Cynthia McGuire wrote:
>
> Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI
> This information is Copyright (c) 2010, Oracle and/or its affiliates. All
> rights reserved.
> 1. Introduction
> 1.1. Project/Component Working Name:
> Solaris Instance UUID
> 1.2. Name of Document Author/Supplier:
> Author: Gavin Maltby
> 1.3 Date of This Document:
> 18 June, 2010
> 4. Technical Description
> See the case directory for more detail
This case might be easier to grok if it was called "crash dump UUID"
or "boot UUID" or some such-- "image UUID" seems vague, and this case
doesn't appear to be generating anything which is scoped beyond the use
case of crash dumps and live dumps (which seems perfectly reasonable).
I presume when you say "UUID" you are stating that the UUID will comply
with some particular standard? RFC 4122?
My big question, thought, is "Why log it to syslog?" The case provides
no rationale for this and seems to tempt customers to consume it--
especially as it marks the log message itself as "committed", which
seemed surprising to me. There may be other committed syslog messages
but I don't know of them, and it seems like this would be something
to avoid (i.e. log messages are not an interface).
-dp
--
Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp
_______________________________________________
opensolaris-arc mailing list
[email protected]
