From owner-freebsd-isp@FreeBSD.ORG Mon Dec 8 10:38:40 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E34DA16A4CE for ; Mon, 8 Dec 2003 10:38:40 -0800 (PST) Received: from mordrede.visionsix.com (mordrede.visionsix.com [65.202.119.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8001043F93 for ; Mon, 8 Dec 2003 10:38:34 -0800 (PST) (envelope-from lists@visionsix.com) Received: from vsis169 (unverified [65.202.119.169]) by mordrede.visionsix.com (Vircom SMTPRS 3.0.273) with SMTP id ; Mon, 8 Dec 2003 12:38:33 -0600 Message-ID: <012c01c3bdba$7e9497e0$df0a0a0a@visionsix.net> From: "Lewis Watson" To: Date: Mon, 8 Dec 2003 12:38:38 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-isp@FreeBSD.ORG Subject: FreeBSD and APCUPSD 3.10.6 X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 18:38:41 -0000 I have successfully used apcupsd 3.8.x and FreeBSD for several months. I recently upgraded to 3.10.6 and now am having much trouble. It starts with the new .sh init script in /usr/local/etc/rc.d. I get a prefix not found error. I had a copy of the old .sh file and it starts apcupsd successfully; which gets logged to syslog and the apcupsd.events file. To test the program I unplug the ups from the serial port and syslog shows that communication with the unit has been lost; yet it no longer is wall'd to the terminals and any attempt to plug the unit back in goes unnoticed. The funny thing is once I run a ./apcupsd.sh stop it then walls that communication were lost with UPS_BERT as it also does a signal 11 core dump. Please bear in mind that this was working fine until I upgraded. I would appreciate any help that could be provided. I did email the port maintainer who suggested I read the FreeBSD doc's ( I have read the handbook and Absolute FreeBSD and many wonderful articles but there is no mention of this problem nor even apcupsd). If anyone could please point me in a good direction I would greatly appreciate it. I am going to try and rebuild apcupsd with my own ./configure parameters. Thanks, Lewis