CLI: shorter, plainer output
Tables name a journal source by its first two units or identifiers; guard test shows 20 matching lines and addresses (--all for all), no /32; Housecarl connection errors without Go's request URL, said once by guard check; status tells "not running" from "no permission"; bans says when there are none; "1 ban lifted". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
96f551be80
commit
b87cc6fb62
5 files changed
+169
-37
No files matched your search
@@ -36,3 +36,15 @@ All notable changes to Guard are documented here. The format follows
|
||||
`SupplementaryGroups`. `sudo -u guard guard test` and `guard check`
|
||||
could read neither `/var/log`'s files (`permission denied`) nor the
|
||||
journal. Upgrading adds the groups.
|
||||
- Shorter, plainer command output. Tables name a journal source by its
|
||||
first two units or identifiers (`journal postfix/smtpd,
|
||||
postfix/submission/smtpd +1`), so `presets`, `check` and `status`
|
||||
fit a normal terminal. `guard test` prints the first 20 matching
|
||||
lines (not 200) and the first 20 addresses it would ban (`--all` for
|
||||
every one), single addresses without `/32`, and counts the matches
|
||||
from `never_ban` addresses. When Housecarl doesn't answer, `guard check`
|
||||
says so once ("Housecarl at URL doesn't answer: connection refused")
|
||||
instead of once per ban list with the request's URL, and only asks for
|
||||
`log:read` when Housecarl refused the log. `guard status` tells "not
|
||||
running" from "no permission". `guard bans` says when there are none;
|
||||
`guard unban` says "1 ban lifted".
|
||||
Reference in new issue
Block a user