ldpd, lib: integrate lde/ldpe into standard logging infrastructure #15515
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The lde/ldpe subprocesses previously used ldp-only
IMSG_LOG
messages between lde/ldpe and the main ldpd process, which then threw the messages intozlog_*
. This has the unfortunate side effect of losing the unique ID information, but also thatassert()
s don't get consistent backtraces, and debug messages are not batched for efficiency.⇒ rework by using the
zlog_live
log target that is already used fordaemon⇒vtysh
log messages by adding a receiver in ldpd so we can dodaemon⇒daemon
ldpd/log.c
is now no longer necessary & entirely removed. UIDs work, asserts get backtraces, and debug messages are batched.Note
ldpd
uses its original BSD coding style, any style warnings inldpd/*
are bogus.