Date: Mon, 8 Dec 2003 17:08:05 -0600 From: "Lewis Watson" <lists@visionsix.com> To: <john@day-light.com> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: [Apcupsd-users] RE: FreeBSD and APCUPSD 3.10.6 Message-ID: <00f001c3bde0$22d4ef10$df0a0a0a@visionsix.net> References: <003601c3bdd9$89c444c0$c905010a@daylight.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 This was exactly correct for the prefix error that was generated. More information on the problem where apcupsd appeared to be failing to communicate with the ups. - I looked at the commfailure and commok files. Each file tries to run apcaccess and place the output of it in the email notifying the admin of the change. I removed these lines and now apcupsd is notifiying with wall, email, and logging each communication status change. Apparantly, apcaccess was just hanging which in turn made the rest of the program nonresponsive. So far so good at this time with those lines that called apcaccess commented out! Thanks, Lewis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00f001c3bde0$22d4ef10$df0a0a0a>