- Xymon - Xymon mailman web

Ubuntu 26.04 sudo-rs incompatibility
by xymon＠mepost.org 13 Jul '26

13 Jul '26

Hello there, on Ubuntu 26.04 with the rust rewrite of sudo, wildcards don’t seem to be supported: sudo -l /etc/sudoers.d/xymon:7:30: wildcards are not allowed in command arguments xymon ALL=("root") NOPASSWD: /usr/bin/cciss_vol_status -u -s /dev/cciss/c*d0 /dev/sg* Any tips how to fix this? Best greetings

3 2

Thoughts on the new Xymon organization - feedback appreciated
by Bruno Manzoni 30 Jun '26

30 Jun '26

Hi all, First of all, many thanks to everyone involved in the new Xymon organization and the recent work around the project. A lot of effort has clearly gone into modernizing and stabilizing the codebase while still preserving the spirit and simplicity of Xymon. * 1. The new governance model is a very positive step for the project:* The fact that *at least two people are now involved in validating and merging changes* *gives much more legitimacy and long-term stability to the project. *It certainly *slows things down a bit*, but for infrastructure software this is probably the correct tradeoff.*It reduces the risk of unilateral decisions and helps keep the technical direction coherent.* *2. The modernization effort* is also going *in the right direction*. One major goal of the new organization is bringing Xymon back to a stable and maintainable upstream state, while progressively *reintegrating improvements that historically existed only in downstream FreeBSD and Debian repositories *(and some in the 4.4 alpha branch).* * *The work achieved so far in this direction is very encouraging. Several important steps have already been achieved:* - GitHub Actions now automatically builds and validates Xymon across multiple platforms, - many Linux, FreeBSD, NetBSD, and pkgsrc portability and build issues were fixed upstream, - parser cleanup and hardening improved robustness, - several memory leaks and stability issues were corrected. As many changes have already been completed, the project is progressively moving toward a new “ready to release” phase, with a growing number of downstream fixes already consolidated upstream, even if the work is not fully completed yet.*It may be better to iterate additional fixes in future releases *instead of trying to consolidate everything at once. This first release will also impact Roland and Mark as Debian and FreeBSD maintainers, so*it should happen when they feel ready,* as they will also need to prepare and publish updated versions on their side. *Keeping the current focus on reducing historical technical debt and reintegrating long-standing downstream work upstream still appears to be the correct priority for now.* *3. That said, there are still some weak points:* - *documentation is still fragmented* between SourceForge, mailing lists, distro patches, wiki pages, and GitHub discussions, - *the maintainer pool is still relatively small,* which can slow reviews and create some continuity risk, - and the project still lacks a clearly centralized long-term roadmap defining modernization priorities and release direction. Overall though, the direction feels healthy, pragmatic, and technically credible. * 4. It would be very interesting to hear what you think as well: *- What could still be improved? - What is currently missing? - How could more people become involved? - And what should the priorities be for the next phases of the project? Bruno

6 9

List archive up and running - with the old archive included - and an anniversary
by Henrik Juul Størner 25 Jun '26

25 Jun '26

4 3

Modernized HTML5 Xymon in my fork
by spiderr 23 Jun '26

23 Jun '26

Thanks to all the great work being done to get Xymon on Github lately, I created a fork where I refactored Xymon HTML output to be HTML 5 compliant. I had to do this in my own projects years ago, so I "put the band back together”. This is not a theme, this is a complete purge of Web 1.0 table based layouts embedded in the .c to a modern HTML5 compliant, responsive (aka mobile) interface. (I did however implement proper CSS themeing for easy customization). Release Details: https://github.com/spiderr/xymon/releases Code: https://github.com/spiderr/xymon/tree/html5-bootstrap EL9 rpm build: https://github.com/spiderr/xymon/releases/download/v5.0.1/xymon-5.0.1-0.el9… Snippet from the release notes: 100% UI changes, 0% everything else. My hard rule was every daemon, protocol, data format, CGI API, URL, and query string is identical to 4.3.30. Scripts, bookmarks, and integrations will not notice the difference. The only thing that changed is the HTML that comes out of the CGIs and page generator. This is a large refactor so I presumptuously dubbed it 5.0, because... HTML5 + Bootstrap 5 = Xymon 5... I could say a lot more, but the release page has almost all changes well documented. Here are some screenshots:

4 8

test mail
by Roland Rosenfeld 22 Jun '26

22 Jun '26

please ignore. No need to respond to this, I can see the result myself. But I need to write through the list server to see, whether the list software now correctly rewrites the From headers or still breaks SPF/DKIM/DMARC... Greetings Roland

2 1

Mailing list test
by Famille Manzoni 17 Jun '26

17 Jun '26

test

2 1

The Next Release Is Within Reach
by Bruno Manzoni 17 Jun '26

17 Jun '26

Hi guys, We currently have 35 PRs that appear ready but are not being merged because nobody is reviewing them. To make code review lighter, I propose modifying our governance as follows: * Typos, comments, and documentation: no review required. * Build/CI fixes: review optional. * Test framework changes: review optional. * Refactoring without behavior changes: review optional. * Bug fixes: one review required before merge. * New features: one review required before merge, with review encouraged at the start and during development when practical. * Architectural changes: one review required before merge, with review encouraged at the start and during development when practical. Let me know what you think. Also, if someone could review PR #158 (normally the last remaining patch before all Debian and FreeBSD patches are integrated), I would appreciate it. For a new feature like this, I am particularly interested in feedback on: * Whether the tests cover the expected use cases and edge cases. * Whether the implementation is understandable and maintainable. * Whether the user interface and behavior are intuitive. * Any obvious issues, limitations, or potential improvements. If everything goes well, a release could be expected fairly soon afterwards. Thanks, Bruno

3 4

New release for Windows Powershell client!
by Stef Coene 15 Jun '26

15 Jun '26

Hi all, I have just released version 2.43 of the Windows PowerShell client! https://github.com/xymon-monitoring/xymon-client-windows-powershell/ This release consolidates various improvements and fixes developed over the last few years. It has been thoroughly tested across 784 Windows servers to ensure stability. Please check out the release notes for the full changelog. Best regards, Stef

2 2

Hello Xymon world!
by Xymon mailinglist 09 Jun '26

09 Jun '26

Just testing the email list. Had a little trouble getting subscribed. I have a few updates to share if this is working.

2 2

Still here, just AFK
by Mark Felder 26 May '26

26 May '26

I know I helped kick off the renewed interest in Xymon, but I've just been a bit too busy with other things to dig in deeper at the moment. I'm watching and reading everything going on, though. Keep up the good work everyone :) Mark

2 4