alfred: Start up alfred without valid interfaces 643/head
authorSven Eckelmann <sven@narfation.org>
Mon, 15 Feb 2021 20:17:53 +0000 (21:17 +0100)
committerSven Eckelmann <sven@narfation.org>
Mon, 15 Feb 2021 20:17:53 +0000 (21:17 +0100)
commitad85bc8142626b6644ef3365bc5cfb37d541092a
treed83b2908064fcf49de55fb3aa983ad524ff95c24
parent993f03cecb2db3e845bfa6ba4326bc352f853e3c
alfred: Start up alfred without valid interfaces

The alfred server always needs interfaces to operate on. But these
interfaces might not exist at the moment when the daemon process is
started. This situation stopped the startup process after the init scripts
waited for a longer period of polling the system state.

But alfred is able to deal with interfaces which disappeared at runtime but
existed at startup. To force a similar behavior for the alfred startup, the
parameter "--force" or "-f" is used. The extra polling code is therefore no
longer needed in the init scripts.

Signed-off-by: Sven Eckelmann <sven@narfation.org>
alfred/Makefile
alfred/files/alfred.init
alfred/patches/0001-alfred-Show-error-message-for-invalid-batadv-interfa.patch [new file with mode: 0644]
alfred/patches/0002-alfred-Allow-exactly-one-interface-for-secondary-mod.patch [new file with mode: 0644]
alfred/patches/0003-alfred-Save-global-mode-flags-in-bitfield.patch [new file with mode: 0644]
alfred/patches/0004-alfred-Allow-start-of-server-without-valid-interface.patch [new file with mode: 0644]