2006/3/3, Nevil Thatcher [EMAIL PROTECTED]:
Hi Arnaud,
Have attached the debug log to this message.
...
the interrupt pipe problem is confirmed:
...
Waiting for notifications...
USB error: error reading from interrupt endpoint /dev/ugen1.01:
Interrupted system call
...
But I don't know why.
The reason for Success is that the code calls
fatal(getpwnam(%s), user);
and not
fatalx(getpwnam(%s), user);
While this fact is not widely documented, the only difference between
the (badly named) procedures fatal() and fatalx() is that fatal()
prints an error message based on errno,
I propose to rename the function fatal() as fatal_with_errno(), and
similarly upslog() as upslog_with_errno(). Reason: this is
self-documenting, and will help to avoid accidentally calling fatal()
in a situation where errno is not set. fatalx() and upslogx() would
remain as before.
Any
Hello,I have a Tripplite SMART1500 UPS, and I'm having a little luck with the tripplite_usb driver. Only a LITTLE though. It's working better than any of the other drivers I've tried, but I'm not getting a status from it. Here's the output of upsc:
battery.voltage: 0.00battery.voltage.nominal:
4 matches
Mail list logo
