13 Jan
2026
13 Jan
'26
3:37 p.m.
Thanks Tom.
Your experience with Xymon and C/Linux can be very useful. Any help with code, patches, or testing is very valuable and very much appreciated. Bruno
Le 13.01.2026 à 16:01, Tom Schmidt via Xymon a écrit :
I have contributed to and used Xymon for decades since the Big Brother days. My team used it to monitor hundreds of systems at my former workplace. I have now been retired for 6 years and use Xymon at home to monitor my local network. I have been running the 4.4.0 alpha1 release on Rocky Linux 8 and 9 platforms and have submitted many patches for it. I have created several external monitors for my local home devices, such as ASUS routers, HP and Epson printers, SolarEdge inverter, and Foscam IP cameras.
I am willing to help in any way I can, but I have no experience running repositories. I do have a good background in C and Linux. I agree that it would be best if a single source for the repository would be best.
Tom Schmidt
On Tue, Jan 13, 2026 at 7:36 AM Josh Luthman <josh@imaginenetworksllc.com> wrote:
Thanks Copilot. Let's refrain from AI slop in this mailing list, please. On Tue, Jan 13, 2026 at 9:24 AM Bruno Manzoni via Xymon <xymon@xymon.com> wrote: HI all *Instruction / call for feedback* This summary was prepared from mailing list discussions and user input to give a clear overview of the current Xymon situation. Feedback from users, maintainers, and operators is strongly requested to confirm this view *and to indicate their willingness to help by briefly listing their relevant skills, availability, and areas of interest (e.g. maintenance, releases, packaging, testing, or specific technical domains).* *Resume* - Xymon development is largely inactive upstream. - Version 4.3 is the only production-ready release. - Version 4.4 is unfinished and experimental. - Most maintenance work is done downstream, causing duplicated effort. *Main problem* *- There is no active upstream maintainer group and no modern collaboration workflow.* - This is the root cause of fragmented patches, stalled releases, and unfinished work (notably IPv6 in 4.4). *Minimal requirements / immediate next steps* *- One public Git repository accepted *as the upstream reference. - *One or two interim maintainers* with merge and release responsibility. - One maintained production branch: 4.3. - A basic issue list to track bugs and patches. - A first consolidated 4.3.x maintenance release. *Who can help* - Distribution maintainers (Debian, FreeBSD). - The original author (Henrik) for CVS migration support. - Production users for testing and validation. - Community members willing to help maintain releases. Bruno Le 13.01.2026 à 10:13, Henrik Størner via Xymon a écrit :Hi, speaking for myself, I must admit that I haven't worked on Xymon for several years. Just lurking on the mailing list occasionally. J.C.Cleaver was maintaining the 4.3.30 version and I was working on the 4.4 branch, but both efforts have stalled - mine certainly has. A Git repo would undoubtedly make it easier for people to contribute than the current Sourceforge CVS repository, so if the is an interest in maintaining or even developing Xymon further, then that would be a very good first step. About the state of the various branches, 4.3 is certainly the production version - this should be priority #1 when moving to Git. The 4.4 branch is - as Roland mentions - very unfinished and alpha-like. It was an attempt on my part to move all of the networking code into a library with support for both IPv4 and IPv6 - quite a bit of it was working, but it was not completed or even stress-tested. It is certainly not bug-free. I cannot offer to restart Xymon development by myself, but I will be happy to assist anyone with getting the code moved from Sourceforge to a Git repo - if you need any special access to Sourceforge. Regards, Henrik Roland Rosenfeld skrev den 13-01-2026 08:47:On Mon, 12 Jan 2026, Mark Felder via Xymon wrote:Is Henrik or JC Cleaver still working on Xymon? I am still the maintainer of the packages on FreeBSD and have been crawling through the mailing list archives, Debian packages, etc and have accumulated a lot of patches that have never made it into a Xymon release. I'm aware there's an Alpha of 4.4 with IPv6 support and a lot of changes too, but it's very much unfinished last I saw (IPv6 for client-server but Xymonnet not refactored to be able to execute IPv6 tests IIRC...)Similar here, as one of the Debian maintainers of the package. We maintain several patches for 4.3.30 in https://salsa.debian.org/debian/xymon/-/tree/master/debian/patches and even more for 4.4alpha1 in https://salsa.debian.org/debian/xymon/-/tree/experimental/debian/patches but the latter are not enough to use 4.4 in a production environment, since there are still some open issues. It would be great to have some shared GIT repo where all the patches from different sources can be consolidated and where we can track open issues, instead of doing duplicated work on different distributions...I'd like to light the fire again. Xymon is something special and I keep coming back to it. It's just the perfect amount of simplicity and power to make monitoring things easy.Same here. My employer uses this with over thousand hosts, several custom addons (for server and client) and with devmon for SNMP polling. And we didn't find a better alternative for our needs yet. I'd be very happy to see activity in xymon development again. Greetings Roland _______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com_______________________________________________ Xymon mailing list --xymon@xymon.com To unsubscribe send an email toxymon-leave@xymon.com_______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com _______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list --xymon@xymon.com To unsubscribe send an email toxymon-leave@xymon.com