Dear Maintainer,

I see these logs on my machine:

2026-10-04T23:19:51.166438+02:00 myhost nut-server[2378]: fopen /run/nut/upsd.pid: No such file or directory
2026-10-04T23:19:51.167112+02:00 myhost nut-server[2378]: Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
2026-10-04T23:19:51.176560+02:00 myhost nut-server[2378]: Running as foreground process, not saving a PID file

And then I also see:

2026-10-04T23:19:51.177052+02:00 myhost nut-server[2378]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
2026-10-04T23:19:51.177400+02:00 myhost nut-server[2378]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
2026-10-04T23:19:51.177723+02:00 myhost nut-server[2378]: upsnotify: logged the systemd watchdog situation once, will not spam more about it

As far as I can tell, both are kind of related since the configure scripts determines whether Type=notify + the -FF option or Type=simple + the -F option are used in the service file. And we end up with Type=simple + the -F option, for some reason. Looking at the build log, I never see "if your systemd version supports Type=notify". I suspect systemd-analyze is not installed during the build, that would explain the issue (if my reading of configure.ac is correct).

Can we add the package that contains systemd-analyze as a build dep? Or patch the configure script to not depend on this check?

Thanks