aboutsummaryrefslogtreecommitdiff
path: root/scripts/testing/archsetup-test.conf
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-17 14:32:38 -0500
committerCraig Jennings <c@cjennings.net>2026-05-17 14:32:38 -0500
commit19cd3ffad4874a812fb5ecbff636e15b0d0a7fc7 (patch)
treee9a62b1ebcdce73b25147289a3af0accdaea3965 /scripts/testing/archsetup-test.conf
parentdae765970268dcbea96060de63cae06c3e63bea6 (diff)
downloadarchsetup-19cd3ffad4874a812fb5ecbff636e15b0d0a7fc7.tar.gz
archsetup-19cd3ffad4874a812fb5ecbff636e15b0d0a7fc7.zip
fix(cmail-setup-finish): verify both Bridge ports and dump status on failure
The "verifying Bridge is listening" check used a regex `127\.0\.0\.1:(1143|1025)` against `ss -ltn` output. That matches if *either* port is listening, but the success message claims both are. So a half-broken Bridge (IMAP up, SMTP down or vice versa) would pass the check. I split the check into two greps and report which port is missing. When the check fails, the script now also prints the last 10 lines of `systemctl --user status protonmail-bridge` to stderr so the operator sees the service state immediately instead of being told to go run the command themselves.
Diffstat (limited to 'scripts/testing/archsetup-test.conf')
0 files changed, 0 insertions, 0 deletions