[Nut-upsuser] ownership of pid directory

2006-12-27 Thread David Benfell
Hello all, Some time ago, you all were very helpful in getting nut running on an OpenBSD system, using--for what it's worth--a CyberPower 1500AVR. So I finally got my FreeBSD system's UPS, also a CyberPower 1500AVR, within reach of its serial cable and I'm trying to get nut running here. I'm goi

Re: [Nut-upsuser] right problem with ups belkin (model who work with

2006-12-27 Thread Marc Collin
> > Good! This will work fine, if you don't mind running the driver as > "root". > > If you would like to run the driver without "-u root" (as I assumed > you wanted to do from your previous message), then the above > instructions might still help. > > If you have any further questions, please fee

Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2006-12-27 Thread Peter Selinger
Miwa Forever wrote: > > Hello. > So as my english is not so good, i'll try to write my story in bash commands > :o) > > [EMAIL PROTECTED] uname -mrs > FreeBSD 5.5-STABLE i386 > [EMAIL PROTECTED] su > [EMAIL PROTECTED] cd /usr/ports/sysutils/nat > [EMAIL PROTECTED] make && make install > [EMAIL PR

[Nut-upsuser] Re: Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2006-12-27 Thread Miwa Forever
2006/12/27, Miwa Forever <[EMAIL PROTECTED]>: [EMAIL PROTECTED] uname -mrs FreeBSD 5.5-STABLE i386 [EMAIL PROTECTED] su [EMAIL PROTECTED] cd /usr/ports/sysutils/nat [EMAIL PROTECTED] # make && make install [EMAIL PROTECTED] cd ../nut-usb [EMAIL PROTECTED] make && make install [EMAIL PROTECTED]

Re: [Nut-upsuser] right problem with ups belkin (model who work with

2006-12-27 Thread Peter Selinger
Marc Collin wrote: > > Le mercredi 27 d=E9cembre 2006 00:29, vous avez =E9crit=A0: > > Hi Marc, > > > > the answer to your question is contained in the file INSTALL, > > distributed with NUT, section 6 "Set ownership data and permissions on > > your serial or USB ports that go to your UPS hardware

[Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2006-12-27 Thread Miwa Forever
Hello. So as my english is not so good, i'll try to write my story in bash commands :o) [EMAIL PROTECTED] uname -mrs FreeBSD 5.5-STABLE i386 [EMAIL PROTECTED] su [EMAIL PROTECTED] cd /usr/ports/sysutils/nat [EMAIL PROTECTED] make && make install [EMAIL PROTECTED] cd ../nut-usb [EMAIL PROTECTED] m

Re: [Nut-upsuser] MGE 800, ttyS0, frequent timeout

2006-12-27 Thread Bruno Wolff III
On Wed, Dec 27, 2006 at 08:19:06 +0100, Arjen de Korte <[EMAIL PROTECTED]> wrote: > > If the problems only occur for the MGE UPS, chances are this is driver > related. In that case, first upgrade to the latest version from SVN or > wait a couple of days for the release of nut-2.0.5 which should

Re: [Nut-upsuser] ups poweroff with cyberpower text protocol

2006-12-27 Thread Arjen de Korte
Anton Piatek wrote: > shutting down my CyberPower OP500TE doesn't seem to work. > Does anyone know if it is possible? (if not I will just change the > shutdown script as suggested in the faq, but it would be nice to do the > proper way). The cpsups driver badly needs maintenance. The driver has s

[Nut-upsuser] ups poweroff with cyberpower text protocol

2006-12-27 Thread Anton Piatek
Hi, shutting down my CyberPower OP500TE doesn't seem to work. Does anyone know if it is possible? (if not I will just change the shutdown script as suggested in the faq, but it would be nice to do the proper way). Thanks, Anton %/etc/init.d/ups-monitor poweroff Shutting down the UPS ... Network

Re: [Nut-upsuser] Unitek iZi UPS 525

2006-12-27 Thread Arjen de Korte
Ciprian Vizitiu wrote: > Another thing: am I supposed to be able to see some activity in the > PIPEFN/LOCKFN folder during the declared "AT" timings? 'coz there is none! > :-o And upssched.conf has the same perms like all other files in /etc/ups/ You should see some activity there (the PIPEFN is

Re: [Nut-upsuser] Unitek iZi UPS 525

2006-12-27 Thread Arjen de Korte
Ciprian Vizitiu wrote: > Ok, most likely it's me but I'm out of ideas right now; last night my very > first attempt was to use "NOTIFYCMD" with > > NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC > NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC > NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC > > ... and the very simple script fo