Skip to content

Local syslog support, networking resilience/hardening and non-zero exit code when terrible things happen - #23

Open
nagisa wants to merge 3 commits into
velbus:masterfrom
nagisa:hardening-and-syslog
Open

nagisa wants to merge 3 commits into
velbus:masterfrom
nagisa:hardening-and-syslog

Conversation

@nagisa

@nagisa nagisa commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Fixes #21 and assorted other issues I discovered over the last year(s) of use.

Best reviewed commit-by-commit which have in-depth descriptions of each issue being fixed. I didn't split this up into separate PRs to reduce administrative burden. Let me know if you'd prefer splits.

@nagisa
nagisa force-pushed the hardening-and-syslog branch 2 times, most recently from caa78c0 to 5b19f07 Compare November 6, 2026 00:42
@nagisa nagisa changed the title Local syslog support, networking resilience/hardening and correct exit code when fan meets volatile organic compounds Local syslog support, networking resilience/hardening and non-zero exit code when terrible things happen Nov 6, 2026
@nagisa
nagisa force-pushed the hardening-and-syslog branch 2 times, most recently from dfa888b to 21dca36 Compare November 10, 2026 19:30
this is a collection of fixes for issues I've seen crop up in my use of
velbustcp. Usually those issues were harmless enough and presented
themselves as "just" an exception in the logs.

However it also contains fixes for genuine issues such as `.gather`
returning out on the first exception when broadcasting the message to
all the connected clients.
The default syslog sends to UDP, but a common case for people running
this on linux systems will be logging into journald or similar, which
expects to deal with local transport, not udp.

I chose to create a new type rather than to modify the remote syslog
output in order to not break any existing users.
@nagisa
nagisa force-pushed the hardening-and-syslog branch from 21dca36 to 6ddd958 Compare November 10, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bind failure will exit with status code 0

1 participant