-
CONFIG_LOG_BACKEND_NET_AUTOSTART
¶
Automatically start networking backend
Type: bool
Help¶
When enabled automatically start the networking backend on application start. If no routes to the logging server are available on application startup, this must be set to n and the backend must be started by the application later on. Otherwise the logging thread might block.
Direct dependencies¶
LOG_BACKEND_NET
&& !LOG_MINIMAL
&& LOG
(Includes any dependencies from ifs and menus.)
Default¶
Kconfig definition¶
At <Zephyr>/subsys/logging/Kconfig:522
Included via <Zephyr>/Kconfig:8
→ <Zephyr>/Kconfig.zephyr:34
→ <Zephyr>/subsys/Kconfig:31
Menu path: (Top) → Sub Systems and OS Services → Logging → Enable networking backend
config LOG_BACKEND_NET_AUTOSTART bool "Automatically start networking backend" default y ifNET_CONFIG_NEED_IPV4
||NET_CONFIG_NEED_IPV6
depends onLOG_BACKEND_NET
&& !LOG_MINIMAL
&&LOG
help When enabled automatically start the networking backend on application start. If no routes to the logging server are available on application startup, this must be set to n and the backend must be started by the application later on. Otherwise the logging thread might block.
(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)