TLS Certificate reloading about chasquid HOT 5 CLOSED

chasquid currently does not support reloading certificates while running, it needs to be restarted to pick up the new ones. This was a conscious decision since implementing cert reloading would introduce significant complexity, for very little gain given how tolerant SMTP is, and how fast chasquid restarts.

chasquid launching a new instance of itself also gets complicated (due to privileged descriptor passing, etc.), that's why nowadays many daemons delegate these things to the launcher (like systemd), instead of trying to handle all this logic themselves (as was more common in the past).

I would, then, focus on ways to restart chasquid in your particular environment. If it had a /quit endpoint in the monitoring server, for example, would that help you? Do you run chasquid with something that would start it again if it dies, like systemd?

Thanks!

from chasquid.

You're right, even restarting would be complex. /quit would be great as I do use an init in Docker that will restart it automatically.

from chasquid.

ThinkChaos implemented the /exit handler in #13, commit 99ec58b in next, so I think that should fix this issue.

ThunkChaos, can you confirm the change in next works for you? It's not too late to adjust and amend, so please let me know how it goes.

Thanks!

from chasquid.

I'm now using next and it works great!
Looking forward to the next release with this minor change. Thanks!

I'll let you close this issue when you want.

from chasquid.

Thanks a lot for the patch and the confirmation!

I think we can now close this, the change will be moved to master in a few days (just to give it more exposure in next in case something comes up), and will be included in the 1.6 release.

Thanks again!

from chasquid.