Releases: fraxflax/nw-watchdog
v1.1.6 - Update Release, 2025-02-17
-
Waiting for arp statuses STALE, NONE, INCOMPLETE, DELAY & PROBE to change before deciding if NEXTHOP is reachable or not.
-
DOWN and UNREACHABLE alerts now tells if the interface is being reset or not
-
Corrected documentation.
v1.1.5 - Update Release, 2024-05-15
-
Optimized check of logsize argument
-
Fixed escaping of local address check
-
Minor optimizations
v1.1.4 - Update and Bugfix Release, 2024-04-28
-
Optimised resolving TARGET
-
Optimized initial device existance and link up check
-
Fixed bug "Not alerting on STATE change."
v1.1.3 - Update and Bugfix Release, 2024-04-25
-
Typos / spelling corrected in help.
-
Code optimizations
-
Create directories for verified pidfile and logfile if required (fixes "No systemd service startup at reboot" bug).
v1.1.2 - Update Release, 2024-04-23
-
Code improvments and optimizations, rewritten tests, replaced deprecated syntax, replaced dynamic strings with constants where possible, and more.
Large thanks to Joakim Roupert for his input both in the form of disussions and pull requests. -
POSIX reference
Please, see documentation/changelog.md for full changelog, including older releases.
v1.1.1 - Update Release, 2024-04-18
Release notes
- Corrected and updated documentation.
Please, see documentation/changelog.md for full changelog, including older releases.
v1.1.0 - Feature Release, 2024-04-17
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.
v1.0.0 - First Stable Release, 2024-04-03
Release notes
Stability tested thoroughly.
POSIX and dependency checks are in place.
All functionality is documented.
Documentation is up to date with sufficient number of EXAMPLES to show the functionality.