From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2712 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Laurent Bercot" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit patches to fix compiler warnings on RHEL 7 Date: Thu, 28 Nov 2019 19:04:37 +0000 Message-ID: References: <20191125214342.y7lx5mixrljr6s27@gromit.local> <20191127203307.ohaameqfgncm52h5@gromit.local> Reply-To: "Laurent Bercot" Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MB57F07698-3182-4F31-A07E-A14C833EE7DA" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="126513"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: eM_Client/7.2.36908.0 To: supervision@list.skarnet.org Original-X-From: supervision-return-2301-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Nov 28 20:04: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 1iaP5k-000Wn0-L9 for gcsg-supervision@m.gmane.org; Thu, 28 Nov 2019 20:04:40 +0100 Original-Received: (qmail 30333 invoked by uid 89); 28 Nov 2019 19:05: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: List-Id: Original-Received: (qmail 30326 invoked from network); 28 Nov 2019 19:05:05 -0000 In-Reply-To: X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrudeijedgudduiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfpfgfogfftkfevteeunffgpdfqfgfvnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhhrfgggtgesrgdtreertderjeenucfhrhhomhepfdfnrghurhgvnhhtuceuvghrtghothdfuceoshhkrgdqshhuphgvrhhvihhsihhonhesshhkrghrnhgvthdrohhrgheqnecurfgrrhgrmhepmhhouggvpehsmhhtphhouhhtnecuvehluhhsthgvrhfuihiivgeptd Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2712 Archived-At: --------=_MB57F07698-3182-4F31-A07E-A14C833EE7DA Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable I am reluctant to bring this up because I am not a neutral third party, but this is frankly a conversation that needs to be had. - This mailing-list accepts all discussions about process supervision software. It also accepts patches to such software (but rather than cold sending patches, please engage in a tech discussion first - it doesn't have to be long.) - The original author or runit is still subscribed to this list, and comes from time to time. However, I'm not aware of an official repo for runit, and runit's latest official version has been 2.1.2 for many a=20 year now. It looks like several distributions have their own version of runit; they are maintained by the distros themselves. - We on the list will gladly help with any question with runit, but to be honest, I'm not exactly sure what to do with patch upstream requests for runit. Is anyone processing them and integrating them into a new release? - I host this list. I'm also the author of s6, a supervision software suite that is very similar to runit in many ways. s6 is actively maintained and has a public git repo, and we generally have a quick response time with requests. - My opinion is that the most sustainable path forward, for runit users who need a centrally maintained supervision software suite, is to just switch to s6 - and it comes with several other benefits as well. - But again, I'm not impartial, and alternatives are a good thing. So no matter what individual decisions are made, it would definitely be a net positive if the exact state and workflow of runit could be clarified, and if a real development/maintenance structure was in place. -- Laurent --------=_MB57F07698-3182-4F31-A07E-A14C833EE7DA--