Citeren Michal Soltys <[email protected]>:
Those two commands happen only once before the actual loop is in
effect, during the initialization stage - in upsdrv_initinfo(). It's
the only place where such large delay is used. Note this is only the
max possible delay, the read will return as quickly as possible
(each command ends with LF) - in case of one of my models it takes
roughly 3 seconds ("capability set" command, "command set" is
faster) - so I wanted to be on the safe side.
I persume the upper limit it's not a problem when upsdrv_initinfo()
is considered ?
In that case, it's fine. But be aware if for whatever reason you need
to call these functions from within in upsdrv_updateinfo, you'll need
to make sure not to hang around waiting for the answer.
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
