From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 5509 invoked from network); 8 Jun 2021 09:13:25 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 8 Jun 2021 09:13:25 -0000 Received: (qmail 24220 invoked by uid 89); 8 Jun 2021 09:13:46 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 24213 invoked from network); 8 Jun 2021 09:13:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=knTg8ujlhBCs7lOVUgjbavslQnsMC7SoGZirZDkaiZw=; b=oC81S5fAkUaOSIzJaSqWdHV0oxdS3euy7dZBG80wBU5PHgG0UmI4/K/zRy+vp5XDm/ GUuSmusTlZLIuz7AWEO1hCDg6sb4FBKDWgZ30Plr3CygzzB8JcYb3nvuLt+62d7GHx6f aCe2pONnQGTZprHZpAUpoKc5nDDzeQOz9DtoT8IG5asLSjtmRdHpe0Oq2cxE9U75LRb1 eFfk71yt4MFUc9KKTgXA/SA2Ba991NrEGP8nEOWQPkS/6tEnVRXfmODCEECMACOMM7Qa QjDJFPGGuRW59FZxLquZgGmBH8JkNf58+x8w37BhGS+gaEASBuEfmd/xy9uGUyhuISvD KhBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=knTg8ujlhBCs7lOVUgjbavslQnsMC7SoGZirZDkaiZw=; b=qFa25asKzcRlq1zc2zZtXuyxCpvMlSMdu7h+rn9bsTa1aPwRE3XI6dHeXWFArhW1wA irDawPOUqyNJCMZ2Ky7o07TuNNfQ6Ak/5fhzDaVZ1z0CrXuGRrji9cF8xTZRbxQR392W XbgeT2x0Qwj+BWiZ2WLcgDT1TqufEp2g+6YLRb73gTp4VgfofiX80sT1+QhtZzY7ol+t 3Rz0kff2o5VKEBR38B4AwEHeWz5Bke8MY3zSy3SFTvmRBlDc74I9SbsTUBhhXtwo4dYh K7WM3Wq6/jB493TFs/3HDeJ/8I79y1u4OzPsRWigtGYeTZdV53mozedOfrM3X0fpnJVe ziBA== X-Gm-Message-State: AOAM531mb2fIqEeVTwuRJSHUukRLN06Rl06rh5UsyafmW31YpJpOkcgW /WAwNLNKJsQbLAGn3N885sZX/9IW3No8/eeqEWA4CZq5DT9mbg== X-Google-Smtp-Source: ABdhPJzLTDjlEmfRAf/Oi9cQ6glthiuvEbOGBwjLUokmQbkG4he4Q0ROc4YWe2j7JEzm12JErRWQCFyc37tK3IU6+8A= X-Received: by 2002:a1c:4d0d:: with SMTP id o13mr3147996wmh.59.1623143599129; Tue, 08 Jun 2021 02:13:19 -0700 (PDT) MIME-Version: 1.0 From: Arjun D R Date: Tue, 8 Jun 2021 14:43:08 +0530 Message-ID: Subject: Query on s6-log and s6-supervise To: supervision@list.skarnet.org Content-Type: multipart/alternative; boundary="000000000000a546b905c43d9136" --000000000000a546b905c43d9136 Content-Type: text/plain; charset="UTF-8" Hi Team, I would like to hear from you for a few queries. Please help. 1. Why do we need to have separate supervisors for producer and consumer long run services? Is it possible to have one supervisor for both producer and consumer, because anyhow the consumer service need not to run when the producer is down. I can understand that s6 supervisor is meant to monitor only one service, but why not monitor a couple of services when it is logically valid if I am not wrong. 2. Is it possible to have a single supervisor for a bundle of services? Like, one supervisor for a bundle (consisting of few services)? 3. Generally how many instances of s6-supervise can run? We are running into a problem where we have 129 instances of s6-supervise that leads to higher memory consumption. We are migrating from systemd to s6 init system considering the light weight, but we have a lot of s6-log and s6-supervise instances that results in higher memory usage compared to systemd. Is it fine to have this many number of s6-supervise instances? ps_mem data - 5.5 MiB s6-log (46) , 14.3 MiB s6-supervise (129) Thanks, Arjun --000000000000a546b905c43d9136--