David Lamparter a4af82ee2b lib, vtysh: report lost messages on live log ... The vtysh live logs don't try to buffer messages when vtysh isn't reading them fast enough. Either the kernel has space and can accept messages without delay, or it doesn't and we continue on. While this is intentional (otherwise slow vtysh could block a routing daemon), at least give the user an indication if messages were dropped. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>		2022-03-07 18:03:16 +01:00
..
.gitignore	vtysh: ignore generated file vtysh_daemons.h	2020-10-06 17:32:09 -04:00
daemons.pl	vtysh: dynamically generate the list of daemons for commands	2020-10-02 15:06:27 +03:00
extract.pl.in	Merge pull request #10376 from patrasar/master_pimv6_vtysh	2022-02-28 10:26:22 +01:00
Makefile	build: non-recursive vtysh	2018-09-08 21:26:54 +02:00
subdir.am	vtysh: show live log messages	2022-02-28 13:33:27 +01:00
vtysh_config.c	vtysh: fix duplicated output of key chain configuration	2021-12-03 18:52:42 +03:00
vtysh_main.c	vtysh: use poll/callback-driven readline interface	2022-02-28 13:28:43 +01:00
vtysh_user.c	*: sprintf -> snprintf	2020-04-20 19:14:33 -04:00
vtysh_user.h	*: reindent	2017-07-17 14:04:07 +02:00
vtysh.c	lib, vtysh: report lost messages on live log	2022-03-07 18:03:16 +01:00
vtysh.h	vtysh: show live log messages	2022-02-28 13:33:27 +01:00