Displaying 3 results from an estimated 3 matches for "upsstart".
Did you mean:
upstart
2014 Jul 26
0
Documenting the NUT driver-qualification process
...bad news, however, is that (a) this is not a NUT-supported device,
>
I've logged an entry for the APC Modbus:
https://github.com/networkupstools/nut/issues/139
> and (b) the (poorly documented) NUT process for discovering and
> customizing a driver failed at the first step. Running upsstart
> gave a driver fail message containing no clues as to how to recover.
>
yup, definitely room for enhancement!
I've got some ideas, beside from the obvious need to improve the
documentation, that I'll like to discuss.
> This is definitely USB and probably a fairly generic hidups...
2014 Jul 09
5
Documenting the NUT driver-qualification process
...easing.
Based on the experience, I have updated the UPS HOWTO:
http://www.catb.org/esr/ldp/UPS-HOWTO.html
The bad news, however, is that (a) this is not a NUT-supported device,
and (b) the (poorly documented) NUT process for discovering and
customizing a driver failed at the first step. Running upsstart
gave a driver fail message containing no clues as to how to recover.
This is definitely USB and probably a fairly generic hidups device.
There is no good reason for customizing a driver profile to be
so difficult.
What I'd like to do is this: confer in real-time, perhaps via IRC,
with someon...
2014 Jul 29
1
APC protocols and drivers (was: Documenting the NUT driver-qualification process)
...orted device,
>>
>>
>> I've logged an entry for the APC Modbus:
>> https://github.com/networkupstools/nut/issues/139
>>
>> and (b) the (poorly documented) NUT process for discovering and
>> customizing a driver failed at the first step. Running upsstart
>> gave a driver fail message containing no clues as to how to recover.
>>
>>
>> yup, definitely room for enhancement!
>> I've got some ideas, beside from the obvious need to improve the
>> documentation, that I'll like to discuss.
>>
>>...