Xymon development inquiry
Hi all,
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...)
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.
I have privately converted the Xymon source repo to Git much like has been done at https://github.com/xymon-monitoring/ but I've preserved all the tags and backdated them properly. My own list of changes is growing:
Fixed buffer overflow in trends which causes it to stop showing graphs if you have too many
Fix FreeBSD graphing of vmstat/CPU utilization (has been broken for many years)
Custom graphs docs do not match reality -- you can't submit NCV or trends data to be processed into RRD files and then display them on any status page you want. I've fixed this; you can put custom graphs on any status page now, not just ones that already have graphs
added ALPN support to xymmonnet so you can create custom protocols to do things like test IMAP through Nginx HTTPS/443 port
WIP -- debugging DS rule processing in analysis.cfg which doesn't obey "first match" like everything else, hope to have this nailed down soon
Please reach out...
Mark
Add one of the people using Xymon on FreeBSD for quite a while now, I want to thank you for all your work! In fact, I might have even been using it for over 15 years, now that I think about it. It has benefited me, my current employer, and my previous employer.
Jaime Kikpole
Director of Technology Ichabod Crane Central School District (518) 758-7575, x5425
On Mon, Jan 12, 2026, 8:58 PM Mark Felder via Xymon <xymon@xymon.com> wrote:
Hi all,
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...)
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.
I have privately converted the Xymon source repo to Git much like has been done at https://github.com/xymon-monitoring/ but I've preserved all the tags and backdated them properly. My own list of changes is growing:
Fixed buffer overflow in trends which causes it to stop showing graphs if you have too many
Fix FreeBSD graphing of vmstat/CPU utilization (has been broken for many years)
Custom graphs docs do not match reality -- you can't submit NCV or trends data to be processed into RRD files and then display them on any status page you want. I've fixed this; you can put custom graphs on any status page now, not just ones that already have graphs
added ALPN support to xymmonnet so you can create custom protocols to do things like test IMAP through Nginx HTTPS/443 port
WIP -- debugging DS rule processing in analysis.cfg which doesn't obey "first match" like everything else, hope to have this nailed down soon
Please reach out...
Mark
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Hi all,
I created the https://github.com/xymon-monitoring/<https://github.com/xymon-monitoring/> repository, which is intended to serve as a potential Git repository home for Xymon. It contains a curated mirror of the SourceForge repository, as well as other related repositories.
This effort is currently incomplete and faces several challenges. The original goal was to produce a clean and understandable representation of the SourceForge history while preserving it accurately. However, I am not yet sure how to properly handle the 4.4 branching from SourceForge, which makes the repository difficult to follow and messy from that point onward. My inability to tackle this problem led me to stop work at that stage. As a result, no further work has been done to improve the repository’s structure or visibility beyond that point.
More fundamentally, I realize that several high-level questions need to be answered before any technical progress can reasonably continue:
*What concrete problem does this initiative actually solve?*
What issue does this repository aim to address for the Xymon project
or community (visibility, fragmentation, contribution workflow,
long-term continuity, etc.)?2.
*Does the Xymon community want this repository to become the new
development home?*
In other words, is there interest in moving active development here,
or should this repository remain a mirror or coordination space only?3.
*Who is willing to help make this a reality?*
Who can contribute time and expertise to resolve the history and
branching issues, help define a clear direction, and participate in
maintaining the repository?Until these questions are clarified, I currently lack a clear vision for how to turn this repository into something valuable for both present and future use.
I would appreciate any help, guidance, or feedback from the community.
Bruno
Le 13.01.2026 à 03:18, Jaime Kikpole via Xymon a écrit :
Add one of the people using Xymon on FreeBSD for quite a while now, I want to thank you for all your work! In fact, I might have even been using it for over 15 years, now that I think about it. It has benefited me, my current employer, and my previous employer.
Jaime Kikpole
Director of Technology Ichabod Crane Central School District (518) 758-7575, x5425
On Mon, Jan 12, 2026, 8:58 PM Mark Felder via Xymon <xymon@xymon.com> wrote:
Hi all, 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...) 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. I have privately converted the Xymon source repo to Git much like has been done at https://github.com/xymon-monitoring/ but I've preserved all the tags and backdated them properly. My own list of changes is growing: - Fixed buffer overflow in trends which causes it to stop showing graphs if you have too many - Fix FreeBSD graphing of vmstat/CPU utilization (has been broken for many years) - Custom graphs docs do not match reality -- you can't submit NCV or trends data to be processed into RRD files and then display them on any status page you want. I've fixed this; you can put custom graphs on any status page now, not just ones that already have graphs - added ALPN support to xymmonnet so you can create custom protocols to do things like test IMAP through Nginx HTTPS/443 port - WIP -- debugging DS rule processing in analysis.cfg which doesn't obey "first match" like everything else, hope to have this nailed down soon Please reach out... Mark _______________________________________________ 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
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
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
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
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 to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
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 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 to xymon-leave@xymon.com
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
Hi Tom, I did Invite you to xymon-monitoing repo! 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
Hi All,
I redid a test of an initial import of the Xymon SVN repository into Git:
https://github.com/xymon-monitoring/xymon-svn-mirror
The goal was a faithful copy, not a cleanup:
- full SVN history imported
- no commits rewritten or dropped
- no branches renamed
- no tags modified
Two helper scripts used for the migration (SVN mirroring and SVN-to-Git conversion) are included in the repository for transparency and reproducibility. A short document (GIT-MIGRATION.md) explains the methodology and the current status.
Current state:
- 4.x-master is still the default branch, matching the historical SVN layout
- a main branch was added to document the migration and related scripts; it will probably be removed later
- no decisions have been made yet (branch naming, cleanup, or future governance)
I would really appreciate if experienced contributors could take a look at this work, as I don’t feel qualified to fully assess it myself. Henrik, if you’re available to validate it, you’ve been invited to the repository with full access, as have JC, TOM, and others. Please let me know if access doesn’t work.
In particular:
- check the repository structure
- verify that the history, branches, and tags look correct
- confirm that the import is technically sound
- review the migration methodology and scripts (on the main branch)
Once the migration is validated, we’ll need to decide:
- whether this repository (github.com/xymon-monitoring/) makes sense to keep, or if someone has a better proposal
- if and how to deprecate the SVN repository
Any feedback is welcome.
Best regards, Bruno
Le 13.01.2026 à 17:10, Bruno Manzoni via Xymon a écrit :
Hi Tom, I did Invite you to xymon-monitoing repo! 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
Xymon mailing list --xymon@xymon.com To unsubscribe send an email toxymon-leave@xymon.com
On 1/13/26 14:12, Bruno Manzoni via Xymon wrote:
Hi All,
I redid a test of an initial import of the Xymon SVN repository into Git:
https://github.com/xymon-monitoring/xymon-svn-mirror
The goal was a faithful copy, not a cleanup:
- full SVN history imported
- no commits rewritten or dropped
- no branches renamed
- no tags modified
Two helper scripts used for the migration (SVN mirroring and SVN-to-Git conversion) are included in the repository for transparency and reproducibility. A short document (GIT-MIGRATION.md) explains the methodology and the current status.
Current state:
- 4.x-master is still the default branch, matching the historical SVN layout
- a main branch was added to document the migration and related scripts; it will probably be removed later
- no decisions have been made yet (branch naming, cleanup, or future governance)
I would really appreciate if experienced contributors could take a look at this work, as I don’t feel qualified to fully assess it myself. Henrik, if you’re available to validate it, you’ve been invited to the repository with full access, as have JC, TOM, and others. Please let me know if access doesn’t work.
This looks similar to what my own effort produced. The tags are correctly backdated, all looks well. I think the only change that needs to happen is to alter the default branch to "main".
If we can find consensus on moving development to this or another git forge hosted somewhere/anywhere, I'd love to begin creating issues and MRs with the patches I've collected and created so we can get the ball rolling on a 4.3.31 release.
Mark
Thanks Mark for checking and for the feedback.
Good to know everything looks fine on your side and that the tags and history came through correctly.
About switching the default branch to main: that’s a future step. For
now, I’m avoiding making decisions on my own.
I fully agree that reaching consensus on the git forge is the next step. Once that’s clear, starting to collect issues and get things moving again would be awesome.
By the way, I’ve invited you to collaborate on the repo. Thanks very much for your feedback.
Bruno
Le 14.01.2026 à 00:10, Mark Felder via Xymon a écrit :
On 1/13/26 14:12, Bruno Manzoni via Xymon wrote:
Hi All,
I redid a test of an initial import of the Xymon SVN repository into Git:
https://github.com/xymon-monitoring/xymon-svn-mirror
The goal was a faithful copy, not a cleanup:
- full SVN history imported
- no commits rewritten or dropped
- no branches renamed
- no tags modified
Two helper scripts used for the migration (SVN mirroring and SVN-to-Git conversion) are included in the repository for transparency and reproducibility. A short document (GIT-MIGRATION.md) explains the methodology and the current status.
Current state:
- 4.x-master is still the default branch, matching the historical SVN layout
- a main branch was added to document the migration and related scripts; it will probably be removed later
- no decisions have been made yet (branch naming, cleanup, or future governance)
I would really appreciate if experienced contributors could take a look at this work, as I don’t feel qualified to fully assess it myself. Henrik, if you’re available to validate it, you’ve been invited to the repository with full access, as have JC, TOM, and others. Please let me know if access doesn’t work.
This looks similar to what my own effort produced. The tags are correctly backdated, all looks well. I think the only change that needs to happen is to alter the default branch to "main".
If we can find consensus on moving development to this or another git forge hosted somewhere/anywhere, I'd love to begin creating issues and MRs with the patches I've collected and created so we can get the ball rolling on a 4.3.31 release.
Mark
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
On 1/13/26 01:13, Henrik Størner via Xymon wrote:
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.
On 1/12/26 23:47, Roland Rosenfeld wrote:
I'd be very happy to see activity in xymon development again.
I think that settles it then. There is a xymon-monitoring org on Github that bonomani created and we have several members. It appears there is an invitation for Henrik and another person which has not been responded to yet. I do not see an invitation sent to Roland yet, so I will look into that.
If we can get agreement that the "xymon-svn-mirror" repository looks correct I think the first step will be to rename the repository to "xymon" and begin Tracking issues and Pull Requests. I have a fairly large list of patches I've harvested from mailing list archives and distro packaging which I can migrate to this repo and we can begin crafting the 4.3.31 release.
Mark
participants (7)
-
Bruno Manzoni
-
Henrik Størner
-
Jaime Kikpole
-
Josh Luthman
-
Mark Felder
-
Roland Rosenfeld
-
Tom Schmidt