On Dec 28, 2006 16:46 -0500, Jody McIntyre wrote: > These message IDs will be assigned using a page on the Lustre wiki > listing the engineer allocating the message and the source file in > which it will be used. This will become obsolete quickly but that's > OK - we only need to know that a message ID has been "claimed", by > whom, and for what purpose.
Other companies uses messages of the form MMMM-NNNN (component-msgnum) so that messages can be allocated separately between different pieces of software or components (e.g. MGS, LMV, or other parts of the code that are being worked on independently). > Once code that prints a message using a particular message ID has been > committed to any branch of CVS, the format of the message may no > longer be changed. Details of what the message means and how to > interpret any variables in the message must be sent to an email > address (to be determined.) This will go to the team(s) responsible > for updating the troubleshooting documentation and the web-based > analysis tool. One issue with this is if a message is unclear or otherwise lacking information and it needs to be fixed then it presumably needs to have a new message ID. That in turn means that the message database will have duplicate information, or there needs to be a facility to link different messages together like "XXXX: (previously YYYY, ZZZZ)"... There are already 2224 CWARN and CERROR messages in the current code base, so I'm not sure a use-once 4-digit number is large enough. Another alternative is to allow the format to "grow" by adding on elements to the end and allowing the "non-format" parts of the message to change (improved wording, etc) so long as there are no changes in the order of existing format elements. As for "committed to any branch of CVS", that imposes a burden on in-development code which might have numerous changes before the code is first released... Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. _______________________________________________ Lustre-devel mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-devel
