[GH-ISSUE #158] remember and tell last result msg #149

New issue

Closed

opened 2026-02-26 09:36:06 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 09:36:06 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Aug 28, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/158

currently, if some client/server fault happens, we call register_*_fault to increment a fault counter.
this leads to some clients getting flagged as abusers if they produce too many faults.

this could be changed to something like register_*_result to register the last result msg (success msg or failure msg) and optionally increment the fault counter (for failures which are considered abusive).

the last result msg could then be displayed on the web UI for the host (or domain).

Originally created by @ThomasWaldmann on GitHub (Aug 28, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/158 currently, if some client/server fault happens, we call register_*_fault to increment a fault counter. this leads to some clients getting flagged as abusers if they produce too many faults. this could be changed to something like register_*_result to register the last result msg (success msg or failure msg) and optionally increment the fault counter (for failures which are considered abusive). the last result msg could then be displayed on the web UI for the host (or domain).

kerem

2026-02-26 09:36:06 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 09:36:07 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Sep 3, 2014):

fixed by 556194ca3f and following changesets

@ThomasWaldmann commented on GitHub (Sep 3, 2014): fixed by 556194ca3f785e43b7d6412275f0af5c43604c90 and following changesets

kerem referenced this issue

2026-02-26 10:31:19 +03:00

[PR #149] [MERGED] Pu translations #396