On 19/11/24 10:29, Sebastien Marie wrote: > Omar Polo <o...@omarpolo.com> writes: >> [...] >> >> I've actually stopped using pounce (I found a bit annoying to loose the >> connection and queued messages when I got disconnected), so if you're using >> it feel free to also take the maintainance :-) > I took the maintainership :)
Thank you! off-list I just got the request to enable the pounce-notify and palaver extensions. I've tested pounce-notify back when I added -t upstream and it works fine, but I didn't enable it for the 3.1 version since I wanted to backport it on -stable. Then I probably forgot to enable them. Just in case you want to consider enabling them as well. > Regarding disconnecting, I am seeing it as a feature, as it permits to > properly pledge the program. Reconnection is moved to another level : I > wrote a simple wrapper for that, but upstream made a dedicated tool for > that (kitd, see https://git.causal.agency/kitd/about/ and > https://marc.info/?l=openbsd-ports&m=173073487330785&w=2 for import) we seem to have different opinions regarding 'features' I used a simple wrapper for it too, but in general I don't like the idea of automatically restart a network-facing daemon, and that's why I never proposed to add kitd to the ports tree. I'd score as a 'feature' not needing a process supervisor to automatically restart a service. They could keep "inet dns" and just reconnect instead, and/or optionally moving to a slightly different privsep design. I thought they didn't had reconnect due to capsicum(4). >> p.s. regarding icbirc I've "forked" it and changed/fixed a few things. I >> still have to check whether my version has this issue as well. >> >> https://git.omarpolo.com/?action=summary&path=icbirc.git > thanks for the link. I intented to see with dhartmei to properly > upstream the patches we are carrying. oh, that's great! :)
