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

[Jim Klimov]

Maybe then use double-quotes around the command, and escape the inner ones
for grep args. Or make a wrapper script in a separate file with equivalent
content, and call it as ExecStart.

Jim

On Sun, Nov 30, 2025, 14:08 Roger Price <roger at rogerprice.org> wrote:

> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20251130/294a3e70/attachment.htm>