<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 16, 2020, at 9:39 PM, David Moylan <<a href="mailto:djm@wiz.net.au" class="">djm@wiz.net.au</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div id="divtagdefaultwrapper" dir="ltr" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12pt; font-family: Calibri, Helvetica, sans-serif;" class=""><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class="">><span lang="en-US" class=""><font size="3" face="Times New Roman,serif" style="font-family: "Times New Roman", serif, serif, EmojiFont;" class=""><span style="font-size: 12pt;" class=""><font size="2" face="Calibri,sans-serif" color="#1F497D" style="font-family: Calibri, sans-serif, serif, EmojiFont;" class=""><span style="font-size: 11pt;" class=""> I have a whole yaml file for logging, which is mostly taken verbatim from Paul’s example. I get tons of logged events – starting circuits, starting datalinks, nodes up, areas up, routers >discovered, etc. It doesn’t seem like it’s changed with this release. You might try that.</span></font></span></font></span></div><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="en-US" class=""><font size="3" face="Times New Roman,serif" style="font-family: "Times New Roman", serif, serif, EmojiFont;" class=""><span style="font-size: 12pt;" class=""><font size="2" face="Calibri,sans-serif" color="#1F497D" style="font-family: Calibri, sans-serif, serif, EmojiFont;" class=""><span style="font-size: 11pt;" class=""><br class=""></span></font></span></font></span></div><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class="">ok so you got me curious about this and i worked it out. i'm not using any of the yaml/json config files for logging, so the default logging goes to the console.</div><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class="">by adding "logging console" to the config i get all the events as expected into my log file as specified on the startup command line.</div></div></div></blockquote><blockquote type="cite" class=""><div class=""><div id="divtagdefaultwrapper" dir="ltr" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12pt; font-family: Calibri, Helvetica, sans-serif;" class=""><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><br class=""></div><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class="">but i have one query for paul:</div><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><br class=""></div><div style="margin: 0px 0in; font-size: 12pt; font-family: "Times New Roman", serif;" class="">is it valid to have both "logging monitor" and the "logging console" enabled together in the configuration file?</div></div></div></blockquote><div><br class=""></div>Absolutely. </div><div><br class=""></div><div>The old code was logging events to the Python log -- which is meant to be the "logging console" even if they were going to other sinks and not to console. I fixed that.</div><div><br class=""></div><div>PyDECnet implements the DECnet logging model, which has three sink types, console, file, and monitor, and both local and remote sinks for each. Any sink type and sink destination has its own event filters. All this was enabled in the current rev (or actually in 521).</div><div><br class=""></div><div>For example, on my core router (PYTHON), I have this config setting:</div><div><br class=""></div><div><div style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Monaco;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">logging console</span></div><div style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Monaco;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">logging monitor --sink-node 28nh --events 4.7-10,14-15,18-19</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class="">For local logging console, the default --events is all events; for all others the default event filter is no events. So for example the following is valid. Perhaps not terribly sensible, but valid:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Monaco;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">logging console</span></div><div style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Monaco;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">logging file --sink-file events.dat --events *.*</span></div><div style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Monaco;" class="">logging console --sink-node ni1d --events 4.*</div></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><div style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Monaco;" class=""><span style="font-variant-ligatures: no-common-ligatures;" class="">logging monitor --sink-node 28nh --events 4.7-10,14-15,18-19</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures;" class=""><br class=""></span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures;" class="">This means: all events go to the local console, i.e., the Python log. All events also go to event file events.dat (in RMS VAR format records containing the binary encoded events). All events in class 4 go to the console of node ni1d, and the mapping events go to the mapper.</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures;" class=""><br class=""></span></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>paul</div><div class=""><br class=""></div></span></div></div></body></html>