[Nut-upsdev] Threads

Kiss Gabor (Bitman) kissg at ssg.ki.iif.hu
Mon Jun 28 15:35:32 UTC 2010

> The upsd server can do the same, yet only uses a single thread. I still don't
> see the benefit of multi threading.

Shorter code that could be maintained more easy.
But no problem, I already forgot multithreading. :)

> I'm interested in how you intend to consolidate the different values from the
> four UPSes you have without losing information. If one UPS loses input power,
> what would the value for 'input.voltage' of your meta-UPS be?

Actually my clients are interested in ups.status only.
And maybe battery.runtime.
They don't care with luxury things like input.voltage. :)

> If you want to help your system administrators setting up NUT easily, why not
> provide them with a centralized 'upsmon.conf' file? If you're using parallel
> redundant UPSes, it should be trivial to let upsmon monitor all of them and
> start shutting down when the POWERVALUE is too low. There is an undocumented

Eeeeer.... the situation is much more complex.
We have three machine rooms and two of them will be de-energized
artifically after a few minutes in order to preserve all
of remaining battery charge to the third server room.
This is where our supercomputer resides that needs quite long
time for a proper shutdown.
So hosts in the other two server rooms require several virtual UPSs
that set LB flag in status 1/3/5/7 minutes earlier than
a shunt trip breaker disconnect mains from physical UPSs.

Wenn ist das Nunstück git und Slotermeyer?
Ja! ... Beiherhund das Oder die Flipperwaldt gersput.

More information about the Nut-upsdev mailing list