On Sep 1, 2018, at 2:44 PM, Mick wrote: > > On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote: >> I don’t have the code in front of me at the moment, but my guess is that the >> config parser stopped parsing at the “#” character. > > I suspected a rogue character was being interpreted and used `backticks`, > 'single quotes' and then "double quotes", but all failed. I ended up > removing > the offending # character and it seems to have worked:
I logged an issue to improve the documentation for this: https://github.com/networkupstools/nut/issues/607 > Is there a particular command I could run to make sure upsmon is working as > expected? A recent battery failure caused the server to crash, but > thankfully > it didn't corrupt any data. https://networkupstools.org/docs/man/upsmon.html "upsmon -c fsd" sends the FSD (forced shutdown) signal to upsd, which should verify that the NUT users and permissions are working. _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
