Notes from meeting: 1) Having log messages that we can track down to individual error messages is a requirement as that end users may want to track what to do on a per message basis. 2) Having log messages that can be tracked uniquely to a error message as it evolves over time is a requirement as that users will not want to keep track of this information from release to release. We've also come up with a starting document on when to use what type of log message: https://github.com/FRRouting/frr/pull/2891 thanks! donald On Tue, Aug 21, 2018 at 12:58 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
All -
In today's technical meeting we spent quite a bit of time discussing David's error code PR:
https://github.com/FRRouting/frr/pull/2841
Discussion centered around understanding out what it was and how we want FRR to work with error codes. Due to time constraints we decided to continue the discussion in a new meeting. This meeting will be held on Aug 22, 9:30 am EDT tomorrow. If you are interested please let me know and I'll add you to the meeting.
donald