:orphan: .. title:: LOG_BACKEND_NET_AUTOSTART .. option:: 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 =================== \ :option:`LOG_BACKEND_NET ` && !\ :option:`LOG_FRONTEND ` && !\ :option:`LOG_MINIMAL ` && \ :option:`LOG ` *(Includes any dependencies from ifs and menus.)* Default ======= - y if \ :option:`NET_CONFIG_NEED_IPV4 ` || \ :option:`NET_CONFIG_NEED_IPV6 ` Kconfig definition ================== .. highlight:: kconfig At ``subsys/logging/Kconfig.backends:244`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:31`` → ``subsys/logging/Kconfig:25`` Menu path: (Top) → Sub Systems and OS Services → Logging → Backends → Enable networking backend .. parsed-literal:: config LOG_BACKEND_NET_AUTOSTART bool "Automatically start networking backend" default y if \ :option:`NET_CONFIG_NEED_IPV4 ` || \ :option:`NET_CONFIG_NEED_IPV6 ` depends on \ :option:`LOG_BACKEND_NET ` && !\ :option:`LOG_FRONTEND ` && !\ :option:`LOG_MINIMAL ` && \ :option:`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.)*