On 6/25/2017 8:33 AM, Manuel Wolfshant wrote:
On 06/25/2017 05:52 PM, Philip Rhoades wrote:
Larry,
On 2017-06-25 23:26, Larry Fahnoe wrote:
Hi Phil,
I don't have an answer to your question about the lack of LAN ports,
I think it is weird - with everything else being connected to LANs
On Tue, Sep 16, 2008 at 03:12:22PM -0400, tarbeite wrote:
Hi all
.
.
stuff
.
.
case $(1) in
onbattwarn)
WALL UPS is down fix me please
echo TIM_UPS is on Battery for more then 10 seconds \
| mailx -r [EMAIL
On Tue, Apr 22, 2008 at 11:15:27AM +0200, Arjen de Korte wrote:
Attached is approx 30 sec of output from the following command:
[...]
/* Get HID notifications on Interrupt pipe first */
/* TODO: cap number of times we check for events? */
while ((evtCount =
On Mon, Apr 21, 2008 at 09:36:07AM +0200, Arjen de Korte wrote:
John Darrah wrote:
I have determined that the the socket is never created because the program
never reaches dstate_init().
It *must* reach this, otherwise it would never reach the part where it
continuously loops through
On Mon, Mar 31, 2008 at 09:16:03AM +0200, Arjen de Korte wrote:
John Darrah wrote:
I have determined that the socket is not being created. Even with -
the following is never executed:
upsdebugx(2, dstate_init: sock %s open on fd %d, sockname, sockfd)
With the driver running if did
On Sat, Mar 29, 2008 at 06:28:38PM +0100, Arjen de Korte wrote:
You may also want to checkout that you didn't do something
weird to the STATEPATH (the directory where this socket is
created). After starting up the driver, you should be able
to see a listening socket being created there.
On Thu, Feb 07, 2008 at 08:24:13AM +0100, Arjen de Korte wrote:
The previous driver would stop by typing a CTRL-C when
running interactively in debug mode. The new driver will not
respond to a CTRL-C. It does not respond to a kill -1,
kill -2 or a kill -15 either (Which may or may not be
Does the following error message have a specific meaning:
usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret
-75
I get two of these messages every time I run the following:
/lib/nut/usbhid-ups -u root -DDD -a trippy
The following is the output from the above
8 matches
Mail list logo
