ginuerzh 2306f45bf9 service: a closed listener is not a failure to warn about ...

A remote listener (rtcp/runix/rudp) wraps an accept failure in core's
AcceptError — which always answers Temporary() — to say "rebuild the transport
and try again", and a closed pipe under it is one of the failures that recovers
that way, so the retry stays exactly as it was. What was wrong is what it said: a
stop arrives down the same path, and a warning that promises a retry reads like a
hiccup in the log of a service that is simply being stopped. The retry is logged
at debug when the error means a closed listener, pipe or socket; every other
failure still warns, and the tail still logs real failures at error.

No behaviour change: the retry, its backoff and the state transitions are
untouched — the classification decides only the log level.

2026-10-01 14:28:33 +08:00

..

service_test.go

service: a closed listener is not a failure to warn about

2026-10-01 14:28:33 +08:00

service.go

service: a closed listener is not a failure to warn about

2026-10-01 14:28:33 +08:00

status_test.go

fix(service): default nil logger, fix Events() allocation, collect Close errors

2026-05-25 23:47:47 +08:00

status.go

fix(handler/sshd): unwrap limiter wrappers to fix wrong connection type (issue #867)

2026-06-13 14:29:51 +08:00