Hi Stef,
Yes, I think it is quite hard to follow the mailing list across multiple subjects. Many times we end up with the same information repeated, or even contradictory information.
I’m not using the GitHub wiki because I was told that a repository wiki is not indexed by search engines (e.g., Google). In case someone wants to build a wiki, I created a dedicated repository called *xymon-wiki*, which can be indexed by search engines and is published as a website.
Also, we can pin three issues so they stay at the top of the Issues list. We should also reconsider issue titles and scope (more precise vs. more general), and ensure each issue includes enough context to remain clear over time. Potentially, we could maintain a single “index” issue that tracks and links to the key topics.
For problem that are not "Code Problem", I did create some years ago a demo "xymon-problem" repo. I need to clean it up.
In the "private" repository, I have also reserved several channel names as placeholders for potential future use on Telegram (easy API/bots) and Signal (high security).
I don’t have any problem keeping things as they are now. I see this as an iterative process: if a step makes things better, that is already a good outcome. It doesn’t have to be perfect.
Thanks for trying to make things better.
Bruno
Le 09.02.2026 à 09:28, Stef Coene a écrit :
Hi,
I added the 2 current issues to the wiki: https://github.com/xymon-monitoring/xymon-wiki/wiki
I think it's better to point users to the wiki so we don't have to repeat / repost this on the mailinglist everything this question pops up.
Stef
On 2026-02-06 00:24, Bruno Manzoni via Xymon wrote:
Hi all,
- PCRE on RHEL10-based systems
Anything based on RHEL10 (Oracle Linux 10, CentOS Stream 10, Rocky/Alma 10, etc.) does not ship the legacy "pcre" (PCRE1 / pcre.h) package in the standard repositories.
- Xymon 4.3.x still depends on legacy PCRE (PCRE 8.x).
- As a result, ./configure fails by default on EL10 due to missing pcre- devel.
What works today:
- Install legacy PCRE from a compat / third-party repository (e.g. pcre-8.45-1.el10.8 and pcre-devel-8.45-1.el10.8).
- Rerun ./configure; the PCRE check passes.
Where this is going:
- EL10 natively provides PCRE2.
- PCRE2 support is under active upstream review: https://github.com/xymon-monitoring/xymon/pull/5
- RRDtool 1.9.0 compatibility
RRDtool 1.9.0 (released 2024-07-29) introduced incompatible header changes in rrd.h. This requires changing affected call sites from char ** to const char **.
What is known to work:
- Debian ships an initial compatibility patch here: https://salsa.debian.org/debian/xymon/-/blob/master/debian/ patches/101_rrdtool1.9.patch
What is upstream now:
- The updated fix merged via https://github.com/xymon-monitoring/xymon/ pull/57 includes a build-time switch (based on pkg-config) to support both RRDtool 1.9.0 and older versions.
Note:
- This version-based switch is a tactical solution and should later be replaced by a cleaner build system approach (see build system work / #35).
- Build and packaging tooling
Work is ongoing to move from configure / make / make install to CMake. The goal is to modernize dependency handling and simplify packaging, while keeping existing installs working during the transition.
- Initial focus is on Debian and FreeBSD.
- The existing build system remains available in parallel.
Help welcome: Anyone with hands-on experience in packaging on EL/Fedora or other BSD variants is welcome to help validate the build and packaging work on those platforms.
Thanks again to everyone testing on newer platforms and sharing results. This feedback is exactly what we need to keep Xymon building cleanly on modern toolchains.
Bruno
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