Good morning, On Wed, 2023-09-13 at 23:12:34 +0200, Jim Klimov wrote: > Hello, > > I think this should be possible, probably with dummy-ups or clone* > drivers and respective override.* definitions in the "secondary drivers"
Indeed I had used "dummy-ups" before - it turned out that had been more than 7 years ago, with version 2.7.4. I had completely forgotten about the "override.*" trick though, and a search over all obvious documentation didn't return anything useful - it seems that the "override" feature is a bit, say, underdocumented... Fortunately, while digging into my archives I found that old setup that somehow was obsoleted by a reinstall not done by me, and forgotten afterwards. So basically I'm now adding "dummy-ups" entries for various battery levels, and monitor them all. 2.8.0 doesn't seem to behave much differently than the previous release in ths respect. I think that I can consider the new systemd integration as a black box. The machine in question is the management server for a whole cluster, so it gets some "manual love" anyway the two times per 5 years it gets restarted, I can easily check for presence of the required services, no need for sophisticated systemd unit dependencies. So all seems to be fine (I got to find out about how fine-grained the corresponding timers and scheduler actions need to be, but perhaps I'll set up individual timers per dummy UPS to keep stuff readable), with the exception of that big black hole in the docs. Thanks so far, Steffen -- Steffen Grunewald, Cluster Administrator Max Planck Institute for Gravitational Physics (Albert Einstein Institute) Am Mühlenberg 1 * D-14476 Potsdam-Golm * Germany ~~~ Fon: +49-331-567 7274 Mail: steffen.grunewald(at)aei.mpg.de ~~~ _______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
