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=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17236 invoked from network); 8 Jun 2021 20:02:54 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 8 Jun 2021 20:02:54 -0000 Received: (qmail 5275 invoked by uid 89); 8 Jun 2021 20:03:18 -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 5268 invoked from network); 8 Jun 2021 20:03:18 -0000 From: "Laurent Bercot" To: "Thiyagarajan, Deva" , "supervision@list.skarnet.org" Subject: Re: Suspend s6-log writing to log file and resume it back after sometime Date: Tue, 08 Jun 2021 20:02:51 +0000 Message-Id: In-Reply-To: References: Reply-To: "Laurent Bercot" User-Agent: eM_Client/8.2.1473.0 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduledrfedtledguddviecutefuodetggdotffvucfrrhhofhhilhgvmecupfgfoffgtffkveetuefngfdpqfgfvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfhhrfgggtgfgsehtqhertddtreejnecuhfhrohhmpedfnfgruhhrvghnthcuuegvrhgtohhtfdcuoehskhgrqdhsuhhpvghrvhhishhiohhnsehskhgrrhhnvghtrdhorhhgqeenucggtffrrghtthgvrhhnpedvgfevffeuleegvdektdffteegvdeiieefkeetgfeuheffheelheejhfevueeijeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphhouhht >Any pointers on how I can go about this? Is there any hack or tricks that= could be done in s6-log to achieve this? Sorry, but no, nothing comes to mind - s6-log was not designed for=20 this. I don't think expecting services to keep running while not logging to disk, whether or not in standby/sleep mode, is reasonable: if logs keep coming up, memory fills up. What do you do if the machine doesn't wake up before the memory is full? The logger will die and you will lose all your carefully accumulated logs. Ideally, you would have dynamic verbosity in the service, and switch it to zero when going into standby/sleep mode, so it would stop producing logs, so you'd never wake up the disk. Of course, unless it's the wakeup event listener, the concept of still having a service running when in standby mode is weird: it defeats the very purpose of standby mode, which is saving energy. The best way to not have your disk spin is to have nothing to make it spin in the first place. :P s6-svc -p all your services when entering standby mode! (Except the wakeup event listener.) :D Sorry for being unhelpful, and good luck, -- Laurent