From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2517 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Casper Ti. Vector" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Update on the progress of slew development Date: Sun, 17 Mar 2019 21:25:32 +0800 Message-ID: <20190317132532.GA22622@CasperVector> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="45142"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.11.3 (2019-02-01) To: supervision@list.skarnet.org Original-X-From: supervision-return-2107-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Mar 17 14:25:41 2019 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1h5VnI-000BfO-UA for gcsg-supervision@m.gmane.org; Sun, 17 Mar 2019 14:25:41 +0100 Original-Received: (qmail 11816 invoked by uid 89); 17 Mar 2019 13:26:05 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 11809 invoked from network); 17 Mar 2019 13:26:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:subject:message-id:mail-followup-to:mime-version :content-disposition:user-agent; bh=T/fk33TXPGs6RkSLQtWdao/ZsBOVTCW3O9MIGomYWmY=; b=TzVnVTgx6pRNK6Bw44F396D9tg7iI2DQncOGQxTzmYxJ9SL8TM7e74U0mndL2VqpaU zUE8oMh9ZfjByUFm253EgUjJ+8VlVEFyh9g0A0tot4x4udxYN68f9J2JgtXF9zDQxH9A C63tyfDHuBbeCOOSk2RysMbzgnH0qAdmPh0pD5/jiARcYUXvFnSyJX3sCoonPDvax7bW 9v+pdlZTc+hPKbN2E98MA6DKkE1S91X9XWxHdG7EVOh6toBX/1H80OIlLEkk6F+c+qrG obqBIaW8uF1D3lf3bAZudM+fl0I8rffUq8nN8URdP6WWWStjNt+0Oh7J/1TSEiXRC0XR yVag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:subject:message-id:mail-followup-to :mime-version:content-disposition:user-agent; bh=T/fk33TXPGs6RkSLQtWdao/ZsBOVTCW3O9MIGomYWmY=; b=XnwypSFrvHCufTRP62imIjwWHrjtm9sHk/JcJIvaZtrZu4PhuPUzc3ibozm5b1Cn2h iIkVbbBdNzY8hsLXKQpcMZ4L2/vxizQthfAM/mNAq4aIyndvtH0NBy/IHXbOHXN0ZC9q T3i21tIp/ikGQUlxmnMGny7QZdmJL+aEMkE9EuV+PerpCi5fGe8H4pSJ/saW3d0WfvXG GxfIBnEa5uiSWBAwSIgQuUHUQFNE//NvtjYNORErJNu0cVmPsYpEnlSph2QzJpv18K+u 6+PpjsJdQytH5Cc/uHDkIxBvIjy2J99Dc8QWP++OY9aRIJaRDK6emv+Vk16tgGfSmL5Z 7XTA== X-Gm-Message-State: APjAAAXgDKWChdgGq8DZAeRa/gXmcfp1xwVxSl/Sn0EJbCIhjzi0G59B pwuVo60BVBcKCG51ZS4r9WIkHymqwfs= X-Google-Smtp-Source: APXvYqxq0Xv1YwRBhDtk+1rzr9YyCUBExUCC8fiVVNvlWLfwygKMXn2j3g5igEI6f42lG3nVkyRyzA== X-Received: by 2002:a5e:8212:: with SMTP id l18mr8333535iom.67.1552829137028; Sun, 17 Mar 2019 06:25:37 -0700 (PDT) X-Google-Original-From: "Casper Ti. Vector" Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2517 Archived-At: Since the first announcement [1] of slew [2], a few people expressed interest in the project, but I have received little feedback regarding its technical contents. Therefore although I have successfully deployed slew on a few real-life systems, it is still quite a slowly moving personal hobby project. However, there are a few changes which I think might be interesting to some people here, which is briefly summarised in this mail, 5 days before the project's one-year anniversary. [1] . [2] . Previously, slew would only save /run/uncaught-logs/current to /var/log/init (so rotated log files would be ignored) on shutdown (so no saved logs if the system crashed). Now the log-saving mechanism is implemented in an s6-log rotation processor (`init/save_log.rc'), which would do the task with best effort (if /var/log/init is unwritable for too long and the catch-all logger is fed with a large stream, the head of the stream might be discarded anyway). The `local' oneshot and `init/rc.halt' would trigger the mechanism by sending the logger SIGALRM; currently, the remaining issue is that s6-log would not run the processor upon SIGALRM if `current' is empty, so a temporary write failure in /var/log/init plus an unfortunate amount of log (no new bytes after the rotated and unsaved log) would result in discarded logs. Other noteworthy changes: * The issue about slew's fault tolerane mentioned in the original announcement has been largely solved. * "Methods" for polymorphic services are supported: see `lib/fn' and `misc/wpa_supplicant/wpa_cli.rc' for an example. * Information can be passed through the kernel command line to slew: see `lib/kcmd.rc', and `init/{load,save}_clock.rc' for an example. Finally, as some people strongly complained [3] about this issue, I would like to ask for your opinions about the naming convention: what do you prefer, more "standardised" names like `wpa_supplicant.wlan0.log' or easier-to-type names like `wpasup.wlan0.log'? I can switch to a new convention if you overwhelmingly support it or if I find a very convincing argument for it, but I need to be really sure that I would *not* need to change the convention *more than once*. [3] . Suggestions and questions are welcome. -- My current OpenPGP key: RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19) 7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C