1. 16 2月, 2021 2 次提交
    • S
      alfred: Start up alfred without valid interfaces · ad85bc81
      Sven Eckelmann 提交于
      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: NSven Eckelmann <sven@narfation.org>
      ad85bc81
    • S
      alfred: Fix procd process handling for disable state · 993f03ce
      Sven Eckelmann 提交于
      Alfred can be stopped during a (re)start or reload when:
      
      * disabled = 1
      * batman-adv interface is missing
      * MAC based EUI64 IPv6 link-local address not set
      
      It is assumed that procd detects that the procd instance definition
      disappeared and the currently running instance must be stopped. But all
      these checks were triggering an "exit" which then stopped the alfred init
      script and the wrapper from /lib/functions/procd.sh. And thus procd was
      never informed about the instances which should be changed.
      
      The correct handling is to return the result of the function instead of
      directly killing the init scripts.
      
      Fixes: 45db0e60 ("alfred: use procd")
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      993f03ce
  2. 29 1月, 2021 1 次提交
  3. 27 10月, 2020 1 次提交
  4. 26 8月, 2020 1 次提交
  5. 07 7月, 2020 1 次提交
  6. 25 4月, 2020 1 次提交
  7. 08 3月, 2020 2 次提交
  8. 14 12月, 2019 1 次提交
  9. 11 11月, 2019 1 次提交
    • A
      alfred: improve version string · c5004988
      Adrian Schmutzler 提交于
      This changes the package version string so it does not start
      with "openwrt", but with the base version we are modifying:
      
      So far: openwrt-2019.4-1
      Now:    2019.4-openwrt-1
      
      Since it's us modifying version 2019.4 (in this case), this order
      is more convenient (and also closer to what the kernel version
      string does).
      Signed-off-by: NAdrian Schmutzler <freifunk@adrianschmutzler.de>
      c5004988
  10. 26 10月, 2019 2 次提交
  11. 02 8月, 2019 2 次提交
  12. 01 8月, 2019 1 次提交
  13. 28 7月, 2019 2 次提交
  14. 24 5月, 2019 1 次提交
  15. 29 3月, 2019 1 次提交
  16. 02 2月, 2019 1 次提交
  17. 15 11月, 2018 1 次提交
  18. 07 10月, 2018 1 次提交
    • S
      alfred: Add openwrt revision to internal version · 37366306
      Sven Eckelmann 提交于
      OpenWrt is using a modified version of the software and these modifications
      may introduce extra bugs (or behavior changes). It is also patched for
      stable releases instead of switching to new releases. The revision should
      therefore be added to the version number to make it easier understandable
      which modified version the user may have installed.
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      37366306
  19. 15 9月, 2018 1 次提交
  20. 21 7月, 2018 1 次提交
  21. 20 7月, 2018 1 次提交
  22. 18 7月, 2018 1 次提交
  23. 26 4月, 2018 1 次提交
  24. 09 4月, 2018 1 次提交
  25. 27 2月, 2018 1 次提交
  26. 06 12月, 2017 1 次提交
  27. 29 9月, 2017 1 次提交
  28. 29 7月, 2017 2 次提交
  29. 25 5月, 2017 1 次提交
  30. 29 3月, 2017 1 次提交
  31. 01 3月, 2017 1 次提交
  32. 30 1月, 2017 1 次提交
  33. 16 12月, 2016 1 次提交
  34. 29 10月, 2016 1 次提交