Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config-rewrite: Rename service_idle_kill to service_idle_kill_interval #1026

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion data/settings.js
Original file line number Diff line number Diff line change
Expand Up @@ -9761,7 +9761,7 @@ the process should get restarted eventually. For example \`100\` or \`1000\`
can be good values.`
},

service_idle_kill: {
service_idle_kill_interval: {
tags: [ 'service' ],
changed: {
settings_service_idle_kill_changed: `
Expand Down
6 changes: 3 additions & 3 deletions docs/core/config/service.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,8 +120,8 @@ The anvil process tracks state of users and their connections.
auth and login services, because each of them has a persistent connection
to anvil.

* **idle_kill=infinite**, because it should never die or all of its tracked
state would be lost.
* **idle_kill_interval=infinite**, because it should never die or all of its
tracked state would be lost.

* [[doveadm,who]] and some other doveadm commands connect to anvil's UNIX
listener and request its state.
Expand Down Expand Up @@ -221,7 +221,7 @@ be used.

This can be used to cycle the process after the specified number of auth
requests (default is unlimited). The worker processes also stop after
being idle for `idle_kill` seconds.
being idle for [[setting,service_idle_kill_interval]].

### config

Expand Down
Loading