This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Max gerrit-no-reply at lists.osmocom.orgReview at https://gerrit.osmocom.org/4155 logging: document alarms target Add subsection describing "log alarms" target. Change-Id: I95ce5f3db38616608590e02ee79eb3a7e6e4ea14 Fixes: OS#1913 --- M common/chapters/logging.adoc 1 file changed, 17 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/55/4155/1 diff --git a/common/chapters/logging.adoc b/common/chapters/logging.adoc index 94fa898..da304b5 100644 --- a/common/chapters/logging.adoc +++ b/common/chapters/logging.adoc @@ -127,6 +127,23 @@ one only for logging, while the other is used for interacting with the system. Another option would be to use different log target. +==== Logging to the ring buffer + +To avoid having separate VTY session just for logging output while still having immediate access to them, +one can use `alarms` target. It lets you store the log messages inside the ring buffer of a given size which +is available with `show alarms` command. + +It's configured as follows: +---- +OsmoBSC> enable +OsmoBSC# configure terminal +OsmoBSC(config)# log alarms 10000 +OsmoBSC(config-log)# +---- + +In the example above 10000 is the desired size of the ring buffer (number of messages). Once it's filled, +the incoming log messages will push out the oldest messages available in the buffer. + ==== Logging to a file As opposed to Logging to the VTY, logging to files is persistent and -- To view, visit https://gerrit.osmocom.org/4155 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I95ce5f3db38616608590e02ee79eb3a7e6e4ea14 Gerrit-PatchSet: 1 Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Owner: Max <msuraev at sysmocom.de>