Hi Jeremy
Thanks for testing 4.3.31, and for the report.
1 You're right about ypmatch: on a system without NIS tools, configure printed "ypmatch: command not found" whenever getent did not find the user, and configure.client has the same line. Both now discard ypmatch's errors as they do getent's, and quote the user name for getent like the other two lookups. That's pull request #645, for 4.3.31: https://github.com/xymon-monitoring/xymon/pull/645
The FAILURE itself was correct: configure needs the xymon user to exist before it runs, so creating it first was the right fix on your side.
*->If that works for you, you can review and approve this PR*, and it will be on the rpm package automatically.
2 On SELinux: the spec in the source tarball (rpm/xymon.spec) does no SELinux labelling or policy. That's packaging, handled in the xymon-monitoring/xymon-rpm repository, so i started to work on your findings there: will be pushed without a review as possible normally in a few minutes (I did not enforce double human review for now): *Nothing to do in your side. *
- Also I did update the docs with specific RPM/Rhel info...: *Nothing to do in your side. (so shop other feature!)*
Cheers Bruno
Le 12.10.2026 à 08:35, Jeremy Laidman a écrit :
Hi Bruno
I'm testing "4.3.31-root" on RHELv9.8. When I run ./configure I get an error due to ypmatch not being installed:
What userid will be running Xymon [xymon] ?
~/xymon-4.3.31-root/configure.server: line 223: ypmatch: command not found FAILURE: The user xymon does not exist. Create user and try again.
I would guess the ypmatch command STDERR could simply be discarded with "2>/dev/null", as it is already done with getent.
This is probably only cosmetic, and I don't think this is actually going to cause a problem, except that the compilation fails because the xymon user doesn't exist, but that's something I probably should have already done. If I use the configure command line from the spec file, which sets a bunch of variables, I don't see the error message.
I also noticed that the same line in configure.server appears to have an inconsistency in the use of XYMONUSER:
USERDATA=
getent passwd $XYMONUSER 2>/dev/null || ypmatch "${XYMONUSER}" passwd || grep "^${XYMONUSER}:" /etc/passwdI believe best practice would be to quote "$XYMONUSER" in all three instances, so I'm not sure why it wasn't quoted in the first command.
Ongoing...
I used the spec file to build a package and installed it onto another RHEL9 host. After installation, the only issue I have noticed is that SELinux was preventing CGI scripts from working correctly. I believe the Terabithia RPM package installs a "xymon.pp" file for SELinux to appropriately label the CGI scripts with "httpd_sys_script_exec_t", and also to allow CGI scripts to initiate network connections (required for connecting to localhost:1984).
Apart from that, it all appears to be running correctly, and I'll continue to play with it for a while.
Cheers Jeremy
On Mon, 12 Oct 2026 at 00:03, Bruno Manzoni via Xymon <xymon@xymon.com> wrote:
Hi Mario, Thanks! Reproduced: if the tree loses its execute bits, configure restores them on its own scripts but not on build/convert-bbservices. That script only converts a 2005 format, so we're removing it. The PR needs a review before it can merge, and it's a two-line diff, so if you have five minutes, I'd love it to be yours: https://github.com/xymon-monitoring/xymon/pull/626 And please report back on SNMP, it's still experimental. Cheers, Bruno Le 11.10.2026 à 11:09, hopbyhop.net <http://hopbyhop.net> via Xymon a écrit :Hi Bruno, hi all. I cloned main tree yesterday and compiled from source as I always used to do with xymon. The box is a Slackware64-current, fping 5.5 and rrd 1.11.0 also compiled from source just before xymon. The only issue I faced was running make install: make[1]: ../build/convert-bbservices: Permission denied That was due to convert-bbservices not being executable. I chmod-ed it an re-run make install and all was fine. So far now xymon runs smoothly just as it did before. Then I recompiled with SNMP=1 env and got xymon-snmpcollect executable. I'm planning to start basic SNMP monitoring without devmon on my home network with a few devices: openwrt switches and access points, pfsense firewall, slackware server (it runs xymon and file and media server). I will let you know how xymon's snmp works in my environment. I'm not sure if I could soon upgrade also the production server at work, running the 4.3.30 release. It would require a pretty big OS refresh first (also Slackware there) and I don't have so much time, since sysadmin is not my role anymore. We started playing with Grafana, but xymon still rocks! See you soon !!! Mario De Chenno Il giorno gio, 08/10/2026 alle 06.46 +0200, Bruno Manzoni via Xymon ha scritto:Hi all, Seven years after 4.3.30, a new Xymon is nearly ready, and it's a big one: code tests docs 241 merged PRs +5,342 -1,546 +13,266 -2,092 6,497 9 still open +267 -104 +981 -5 157 Roughly five years of Xymon development, packed into less than one: the biggest Xymon update since 4.3.0. Help us get it over the line: - Got time for just one review? Take #349 or #428: they're the ones holding the release back. https://github.com/xymon-monitoring/xymon/pull/349 https://github.com/xymon-monitoring/xymon/pull/428 - Review a 4.3.31 PR. Most of them just wait for a second look: https://github.com/xymon-monitoring/xymon/issues?q=is%3Apr+state%3Aopen+milestone%3A4.3.31 - Or go shopping in the other open PRs. Something for every taste, and reviewing is free: https://github.com/xymon-monitoring/xymon/pulls - Build it on your system. - Run it next to your setup and tell us what changes. Reply here or open an issue: https://github.com/xymon-monitoring/xymon Thanks! 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 toxymon-leave@xymon.com_______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com