Skip to content

v1.1.0 - Feature Release, 2024-04-17
Compare
Choose a tag to compare
@fraxflax fraxflax released this 17 Apr 10:27
v1.1.0
b93a08d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release notes

  • New alert states: LINKDOWN and LINKUP
    In version 1.0.0, if there is no link on the interface a WARNING alert is sent causing alerts to be sent repeatedly under certain circumstances (e.g. every max-nolink * ifup-grace second if the link is physically lost (switch port down, cable damaged / out, etc) and --force-interface with a --max-nolink greater than 0 is used.

    With these new alert states there will be only one alert when the link is lost and we can't get it up again within max-nolink_ tries.

    Once the link comes up there will be one LINKUP (or REAHCABLE / UP depending on what is detected firstly) alert.

  • Information level (--verbosity-level=4) logging (instead of WARNING alerts when conflicting topology detected using --force-interface.

  • LIST ALL ERRORS
    Instead of dying with an error message upon first found error whilst parsing the options, now all options and arguments are parsed and checked firstly, then if there are error(s), all error messages and USAGE instruction is shown.

  • New option: --no-pager | --no-less | --no-more | -M
    No longer recommending using PAGER=cat not to use pager.

    --install-systemd will enforce --no-pager when installing systemd-services

  • New option: --remove-systemd=SERVICENAME.

    (Manual removal proces is also described in --help.)

  • New option: --list-systemd

  • Changed logfile and pidfile filename for systemd services:
    --pidfile=/run/nw-watchdog/SERVICENAME.pid (instead of /run/nw-watchdog-SERVICENAME.pid)

    and --logfile=/var/log/nw-watchdog/SERVICENAME.log (instead of /var/log/nw-watchdog-SERVICENAME.log)

  • Initial device check (addresses the "False --force-interface UP bug")
    If an interface is specified with --interface or --force-interface and the corresponding device is non-existing or has no link, attempts to bring it up or reset it is performed unless --no-interface-reset is specified. Using --force-interface will now require the interface to come up with link before proceeding. This addresses the bug of when a non-existing device was specified as --force-interface the TARGET could be considered UP if reachable via another interface.

  • New alert state: INITIAL
    For alerting of initial problems preventing or delaying the start of the monitoring:

    --force-interface non-existing device, cannot be brought up or ha no link, non-existing --interface device in combination with --no-interface-reset

    and also if initial topology is immediately changed due to specified non-existing / no-link --interface could not be brought up with link from the start.

  • Options and Arguments Parsing
    All options and arguments are now parsed in a more general approach making it easier and more fool proof to introduce or change options and argument verification, allowing for quicker development less likely to introduce bugs.

Please, see documentation/changelog.md for full changelog, including older releases.

Assets 2
Loading