Martin Kessler wrote:
Have to correct my last email, I just wasn't patient enough, it took
20min between starting service apcupsd and "NIS server startup
succeeded" message. Could also be that the communication came up because
we had a few voltage fluctuations right before the message. Its
definitely weird that it takes that long.

Oh boy. That is due to a very embarassing bug in the apcupsd patch. It doesn't initialize the inter-urb timer properly so it could end up waiting very, very long the first time thru.

Attached is the corrected patch.

Someone please pass the brown paper bag...
--Adam

Attachment: apcupsd-enforce-urb-delay2.patch
Description: Binary data

Reply via email to