Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Dec 2003 16:20:50 -0600
From:      "John Brooks" <john@day-light.com>
To:        "'Lewis Watson'" <lists@visionsix.com>, <apcupsd-users@lists.sourceforge.net>
Cc:        freebsd-isp@FreeBSD.ORG
Subject:   RE: FreeBSD and APCUPSD 3.10.6
Message-ID:  <003601c3bdd9$89c444c0$c905010a@daylight.net>
In-Reply-To: <012c01c3bdba$7e9497e0$df0a0a0a@visionsix.net>

next in thread | previous in thread | raw e-mail | index | archive | help
many scripts in /usr/local/etc/rc.d will require the full path to
manually start or stop. just doing "./<scriptname.sh> start" will 
produce the error you are experiencing. try using:

  /usr/local/etc/rc.d/apcupsd.sh start
     or
  /usr/local/etc/rc.d/apcupsd.sh stop

--
John Brooks
john@stlbsd.org 

-----Original Message-----
From: owner-freebsd-isp@freebsd.org
[mailto:owner-freebsd-isp@freebsd.org]On Behalf Of Lewis Watson
Sent: Monday, December 08, 2003 12:39 PM
To: apcupsd-users@lists.sourceforge.net
Cc: freebsd-isp@FreeBSD.ORG
Subject: FreeBSD and APCUPSD 3.10.6


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

_______________________________________________
freebsd-isp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003601c3bdd9$89c444c0$c905010a>