From owner-freebsd-stable Thu Jun 8 8:40:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 08FBC37B58B for ; Thu, 8 Jun 2000 08:40:27 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e58FeKI29771; Thu, 8 Jun 2000 08:40:21 -0700 (PDT) Date: Thu, 8 Jun 2000 08:40:20 -0700 (PDT) From: Doug White To: Andrew Tulloch Cc: stable@FreeBSD.ORG Subject: Re: APC Back-UPS Pro In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, Andrew Tulloch wrote: > I'm having a bit of trouble with getting an APC Back-UPS Pro running on > freebsd. It seems to be working with upsd from the ports collection. But > every while I get a whole load of lines looking like this: > upsd[355]: apc_tune: negative repsonse: N > upsd[355]: apc_tune: negative repsonse: ^M > upsd[355]: apc_tune: negative repsonse: ^M > upsd[355]: apc_tune: negative repsonse: N > upsd[355]: apc_tune: negative repsonse: NO > upsd[355]: apc_tune: negative repsonse: NO That looks like either the UPS or upsd getting confused as to where to expect responses. Check your config and make sure you aren't adding extra spaces. I woudn't discount that the APC is doing wierd serial things -- it always seemed flakey to me when I was working on upsd. upsd hasn't been touched in years so it's possible it still has bugs :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message