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.1 required=5.0 tests=DATE_IN_PAST_96_XX, MAILING_LIST_MULTI,NICE_REPLY_A autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 2566 invoked from network); 17 Feb 2021 19:30:07 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 17 Feb 2021 19:30:07 -0000 Received: (qmail 8858 invoked by uid 89); 17 Feb 2021 19:30:30 -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 8851 invoked from network); 17 Feb 2021 19:30:30 -0000 X-Injected-Via-Gmane: http://gmane.org/ To: supervision@list.skarnet.org From: Benjamin Franksen Subject: Re: runit patches to fix compiler warnings on RHEL 7 Date: Tue, 3 Dec 2019 11:57:06 +0100 Message-ID: References: <20191125214342.y7lx5mixrljr6s27@gromit.local> <20191127203307.ohaameqfgncm52h5@gromit.local> <20191202175710.pl475v2li5xnhrho@gromit.local> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 Autocrypt: addr=ben.franksen@online.de; keydata= xsFNBE9WAmEBEADTYcaP7CH9imjcTAT0/G+bli6IYnIkPsWqQ2kJ6Q12reFkmXECOPTFcSqs C1uRL0fLUg4gE6RLQacxku13lQC+xAvKYL2mUdIzcJVrXzbgjFQ4YIGaUnuEqXIPnjb1M6X/ 9CtTlSO9P8XzFb2Rs6gSxI9DbIGucdmsj2QoT2yIWYBoaugfQ1xRHmqu8xrEXQlBfTtJXz2X qCyQXW95HzUrGR+XclvAoKL6LKpGA1apsSVfMD8mVOQHu3GlBxryNBTaTNZW4N/Q8kHLwaNe JZ8GO/8BlJzGUq1rQihR3/DdZw+eAnabaihFn3aW4DJDQDXRX2OuaI4VjN4kYAxikGYfidt0 BNvF6kGMVUEWQwd9NXEzFGgcjb8LA1MfzjXrr0ytJUvQm/sV2VoGUyt5pMFbt/AQZ9pEgDk1 Du1w2QHF5Q2V0K7jBidBLzOqQM7gx0jkwdE8tgB+BM//u8gb5wlw7OQfhD71ADRvp/cI/9pm QoD09r91FZZnDF8Rb3aMmfIhaTavDFlyoy36AF1NYY+ly5R4FepfPFzx2WNPiFTAJKQLXPoq cCPkKRXkmvtbhD3l8JbOtpL143uXVXupk1F4K/6S/f1ZK9vVucqMszBqtf8rJia5pCk1D788 V3MVaDPbE5aIcAmpkax4FgjRJ7aIweO7pbHWpTF7FEZJZrVdYwARAQABzSVCZW4gRnJhbmtz ZW4gPGJlbi5mcmFua3NlbkBvbmxpbmUuZGU+wsF5BBMBAgAjBQJW6XZAAhsvBwsJCAcDAgEG FQgCCQoLBBYCAwECHgECF4AACgkQnnTm9+eykAXxVA/+MAcC0GjdvZ6L7zPce7p8ttbwxhAn nzA4XgnpAJPiBHgCIG7CBJW8oc6PJDEziwHpWRIisvG7rr7xP4d9X4+hYJ5dSV4hNZiy+aA+ Z6AskJIUP+x7iwUDp6BGq72fIGjlAbZJTglfY92bpnQGJM+tnzrzFwUZvLHxZkoZvUS/9DIs 5W5iVbgkeX3SXXV9md7rLv3wlBurHIjh4ehwoLDp7izVqOqk8ADB47SzY/82Y1JTVQq/UzFY v3fqYQvfNCk70bcOnm4IPeEvQalJqZBLn7K1xEVBOMed6TAKEcrtWq6U55kH+Kv1Ih33J/DP 6qJ569K5eYRzzDRYqulCeBdexs5CrpFJyM1jqJ+6ztxjvii3WI6hSAI/mcSg76PAumxV14KX HPYnGTNp1uMdMJlW1NRU3pVlfxNa2QaYy1PQ1hfuQIfZesp2ZtyQcbLkHGABLeB7/J6F0cBn kEliQjE6O99X+KX1amImvFRPRGYhpqqU+salqih2wUSCyb8JncXfp0l4cSRXikC97TnY5Bjt RkNhZAdSdahYdeqr8AIMnNknpjhwEfDKSVuHPidli33q0jSp+sd2RztkpJr4e5TIP9i23cQk 1TQDV4pIB0OrC7+8RpMuW3mMANJz5e2clwHWfeqZEFkQkoGPc0VZqJJpIFVybG+aoSzoTolE /oicLoI= In-Reply-To: Content-Language: en-US Am 02.12.19 um 22:58 schrieb Laurent Bercot: >> I see something called sdnotify-wrapper, so maybe I should have a look >> at that?  (It was mentioned to me off-list.) > > sdnotify-wrapper will only be useful if your daemon is using the > NOTIFY_SOCKET mechanism (aka sd_notify()) to tell systemd when it is > ready. If it's the case, then yes, you can use sdnotify-wrapper in your > s6 run script and it should automatically do the right thing. Hi, I was the one who told Lewis about sdnotify-wrapper and it seems I got it completely wrong: I had thought it was a wrapper for daemons that use the s6 notification mechanism to make them compatible with the systemd convention. Your description above suggests it does the exact opposite. Cheers Ben