Nut upsuser - Nov 2025 - Debian 13 (NUT 2.8.1) fixes upssched bug, but floods systemctl log

>  I was looking at a technique which allows systemd to "Run any
Executable
as Systemd Service in Linux"...

Well, as a sort of hot-fix, you could  edit
`/usr/lib/systemd/system/nut-monitor.service` to replace ExecStart from a
direct command call to a shell snippet, something like:

-ExecStart=/usr/local/ups/sbin/upsmon -F
+ExecStart=/bin/sh -c '/usr/local/ups/sbin/upsmon -F | grep -v "Network
UPS
Tools upsmon 2.8.1"'

NOTE: If here you would be editing the file directly, it would be likely
overwritten by eventual package upgrade - but then it would hopefully be
with a more recent NUT.

Hm, or a minor packaging patch.

Then maybe a site-local "drop-in" override would be better:

:; mkdir -p /etc/systemd/system/nut-monitor.service.d
:; cat > /etc/systemd/system/nut-monitor.service.d/filter.conf <<
'EOF'
[Service]
ExecStartExecStart=/bin/sh -c '/usr/local/ups/sbin/upsmon -F | grep -vE
"Network UPS
Tools .* 2\.8\.[012]"'
EOF
:; systemctl daemon-reload
:; systemctl restart nut-monitor

BEWARE: This is based on my local build that went into under
/usr/local/ups/ - the packaged path to upsmon in your case would likely
differ.

Hope this helps,
Jim Klimov


On Sat, Nov 29, 2025 at 3:04?PM Roger Price <roger at rogerprice.org>
wrote:
> On Sat, 29 Nov 2025, Greg Troxel wrote:
>
> > Debian not having the latest release is a Debian bug
>
> Hello Greg, Agreed !
>
> > I suggest installing the latest.  Surely there's some reasonable
away to
> > do that by taking the control files and moving them forward and
> > building, or taking a package from unstable, or ?
>
> My UPS's are Eaton ECO 1600 which are well supported by NUT 2.8.1 so I
> have less
> motivation to move to the latest release.
>
> I was looking at a technique which allows systemd to "Run any
Executable
> as
> Systemd Service in Linux".  I'm thinking of a very simple
executable which
> would
> run grep -v <banner> on messages before they get to the journal and
> journalctl.
> It's based on a suggestion by Abhinand [1].
>
> Roger
>
> [1]
>
https://abhinand05.medium.com/run-any-executable-as-systemd-service-in-linux-21298674f66f
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20251129/e0e79c4c/attachment.htm>

On Sat, 29 Nov 2025, Jim Klimov wrote:
> Well, as a sort of hot-fix, you could? edit
`/usr/lib/systemd/system/nut-monitor.service` to replace ExecStart
> from a direct command call to a shell snippet, something like:
> 
> -ExecStart=/usr/local/ups/sbin/upsmon -F
> +ExecStart=/bin/sh -c '/usr/local/ups/sbin/upsmon -F | grep -v
"Network UPS Tools upsmon 2.8.1"'
> 
> NOTE: If here you would be editing the file directly, it would be likely
overwritten by eventual package upgrade -
> but then it would hopefully be with a more recent NUT.
This is a neat idea.  I made the change to ExecStart and ran 
systemctl?daemon-reload. I then ran systemctl?status?nut-monitor and got the 
following error message:

Nov 30 12:54:27 titan systemd[1]:
/usr/lib/systemd/system/nut-monitor.service:38:
 Ignoring unknown escape sequences: "/usr/sbin/upsmon -F | grep -vE
"Network UPS Tools .* 2\.8\.[012]""

It looks as if systemd is making a mess of the single and double quotes.

I've been reading 
https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#Command%20lines
but I'm not any clearer about single/double quoting.

Roger