From 355d6a83810e1b7bb3bc2ccd3102141dbea63821 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 21 Aug 2022 02:37:46 +0000 Subject: Add upper limit to -c in s6-svscan Also document it, and document changes to s6-supervise Signed-off-by: Laurent Bercot --- doc/s6-svscan.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc/s6-svscan.html') diff --git a/doc/s6-svscan.html b/doc/s6-svscan.html index 5c031c6..8b94cf4 100644 --- a/doc/s6-svscan.html +++ b/doc/s6-svscan.html @@ -76,10 +76,11 @@ where all error messages go to the s6-svscan-log catch-all logger servi default, except messages from this service itself, which fall back to consoleholder. If you're not sure what to use this option for, or how, you don't need it.
  • -c max : maintain services for up to max -service directories. Default is 500. Lower limit is 2. There is no upper limit, but: +service directories. Default is 500. Lower limit is 2. Upper limit is 90000. If +you're increasing this value from the default, please note that:
    • The higher max is, the more stack memory s6-svscan will use, -approximately 50 bytes per service.
      • +up to 100 bytes per service.
    • s6-svscan uses 2 file descriptors per logged service.
    It is the admin's responsibility to make sure that s6-svscan has enough available -- cgit v1.2.3