alfred: Start up alfred without valid interfaces 644/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:33:27 +0000 (21:33 +0100)
commit369908cb0a0e34fccc5e0e4ff7098133a3813308
tree26a4796852133a2e4ba6bff0efcda1ba0feea9ff
parent97e760095578a8a1491f59423c712c7dc7b75a1f
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/0004-alfred-Show-error-message-for-invalid-batadv-interfa.patch [new file with mode: 0644]
alfred/patches/0005-alfred-Allow-exactly-one-interface-for-secondary-mod.patch [new file with mode: 0644]
alfred/patches/0006-alfred-Save-global-mode-flags-in-bitfield.patch [new file with mode: 0644]
alfred/patches/0007-alfred-Allow-start-of-server-without-valid-interface.patch [new file with mode: 0644]