From ef2fed4bc93a777baa50aeff27b23227d37da7a3 Mon Sep 17 00:00:00 2001 From: 1kastner Date: Tue, 25 Aug 2020 16:47:34 +0200 Subject: [PATCH] Explain culler settings better --- docs/topic/idle-culler.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/topic/idle-culler.rst b/docs/topic/idle-culler.rst index b5af331..86d53ed 100644 --- a/docs/topic/idle-culler.rst +++ b/docs/topic/idle-culler.rst @@ -8,15 +8,15 @@ The idle culler automatically shuts down user notebook servers when they have not been used for a certain time period, in order to reduce the total resource usage on your JupyterHub. - JupyterHub pings the user's notebook server at certain time intervals. If no response is received from the server during this checks and the timeout expires, the server is considered to be *inactive (idle)* and will be culled. -The idle culler is maintained as -`a separate project `_. -For advanced users, the code leaves the option for direct adjustment, e.g. to add -features such as purging old user data. +The idle culler is a JupyterHub service that is installed and enabled by default in TLJH. +It can be configured using tljh-config. For advanced use-cases, like purging old user data, +the idle culler configuration can be extended beyond tljh-config options, using custom +`jupyterhub_config.py snippets `__. + Default settings ================