:orphan:

.. title:: CONFIG_LOG_BACKEND_NET_AUTOSTART

.. kconfig:: CONFIG_LOG_BACKEND_NET_AUTOSTART

CONFIG_LOG_BACKEND_NET_AUTOSTART
################################

*Automatically start networking backend*

Type: ``bool``

Help
====

.. code-block:: none

    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
===================

\ :kconfig:`LOG_BACKEND_NET <CONFIG_LOG_BACKEND_NET>` && !\ :kconfig:`LOG_FRONTEND <CONFIG_LOG_FRONTEND>` && !\ :kconfig:`LOG_MINIMAL <CONFIG_LOG_MINIMAL>` && \ :kconfig:`LOG <CONFIG_LOG>`

*(Includes any dependencies from ifs and menus.)*

Default
=======

- y if \ :kconfig:`NET_CONFIG_NEED_IPV4 <CONFIG_NET_CONFIG_NEED_IPV4>` || \ :kconfig:`NET_CONFIG_NEED_IPV6 <CONFIG_NET_CONFIG_NEED_IPV6>`

Kconfig definition
==================



At ``<Zephyr Subsystem>/logging/Kconfig.backends:281``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:31`` → ``<Zephyr Subsystem>/logging/Kconfig:23``

Menu path: (Top) → Sub Systems and OS Services → Logging → Backends → Enable networking backend

.. code-block:: kconfig

    config LOG_BACKEND_NET_AUTOSTART
    	bool "Automatically start networking backend"
    	default y if NET_CONFIG_NEED_IPV4 || NET_CONFIG_NEED_IPV6
    	depends on LOG_BACKEND_NET && !LOG_FRONTEND && !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.)*