RE: [Nut-upsuser] make errors on solaris express dev 02/07

2007-03-06 Thread Zoltan Farkas
See attached the configure.out file for the configure output. Thanks --zoly -Original Message- From: Charles Lepple [mailto:[EMAIL PROTECTED] Sent: Monday, March 05, 2007 11:19 PM To: Zoltan Farkas Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] make errors on

[Nut-upsuser] nut upset after Oops

2007-03-06 Thread Udo van den Heuvel
Hello, When my kernel oopses (not ups/nut related) nut is somewhat upset and keeps complaining that power is gone, and restored, etc, etc, etc. How can I fix this? Kind regards, Udo ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Arjen de Korte
When my kernel oopses (not ups/nut related) nut is somewhat upset and keeps complaining that power is gone, and restored, etc, etc, etc. How can I fix this? Which NUT version? UPS connected through serial or USB? Operating system? What is the reason the kernel oopes? Is this a one time

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Peter Selinger
Udo van den Heuvel wrote: Hello, When my kernel oopses (not ups/nut related) nut is somewhat upset and keeps complaining that power is gone, and restored, etc, etc, etc. How can I fix this? Please start by providing some information. What NUT version are you using, what driver? What

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Udo van den Heuvel
Arjen de Korte wrote: When my kernel oopses (not ups/nut related) nut is somewhat upset and keeps complaining that power is gone, and restored, etc, etc, etc. How can I fix this? Which NUT version? UPS connected through serial or USB? Operating system? What is the reason the kernel oopes?

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Arjen de Korte
When my kernel oopses (not ups/nut related) nut is somewhat upset and keeps complaining that power is gone, and restored, etc, etc, etc. How can I fix this? Which NUT version? UPS connected through serial or USB? Operating system? What is the reason the kernel oopes? Is this a one time

Re: [Nut-upsuser] make errors on solaris express dev 02/07

2007-03-06 Thread Peter Selinger
How I love svn blame! 571 selinger-guest if ( test ${ac_cv_func_connect} = no ); then 2aquette AC_CHECK_LIB(nsl, printf, [ 2aquette NETLIBS=-lnsl 2aquette ], [], []) 2aquette 2aquette AC_CHECK_LIB(socket, printf, [

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Udo van den Heuvel
Peter Selinger wrote: Udo van den Heuvel wrote: How can I fix this? Please start by providing some information. What NUT version are you using, what driver? The FC6 binary for 2.0.3-2.1. I use the Mustek PowerMust driver with a Sweex UPS. What messages do you see? How frequently? Mar 6

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Arjen de Korte
Please start by providing some information. What NUT version are you using, what driver? The FC6 binary for 2.0.3-2.1. I use the Mustek PowerMust driver with a Sweex UPS. Before trying anything else, upgrade to nut-2.0.5. There have been many bugfixes since nut-2.0.3, including problems with

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Charles Lepple
On 3/6/07, Udo van den Heuvel [EMAIL PROTECTED] wrote: Hello, When my kernel oopses (not ups/nut related) nut is somewhat upset and keeps complaining that power is gone, and restored, etc, etc, etc. How can I fix this? It depends on what you want to get from NUT when the kernel oopses. You

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Udo van den Heuvel
Arjen de Korte wrote: Sometimes even after the restart nut keeps complaining even though the UPS is OK. You failed to mention the version of NUT you're using and it's also not quite clear to me if you're using a USB driver or a serial driver (posting the output of the driver startup

Re: [Nut-upsuser] make errors on solaris express dev 02/07

2007-03-06 Thread Charles Lepple
Peter, I will look at this more later, but do you know why configure.in is checking for printf in -lnsl? checking for printf in -lnsl... yes checking for printf in -lsocket... yes It seems like it should be checking for a socket function instead. Zoltan, can you send the config.out generated

Re: [Nut-upsuser] make errors on solaris express dev 02/07

2007-03-06 Thread Charles Lepple
On 3/6/07, Zoltan Farkas [EMAIL PROTECTED] wrote: /bin/bash ../libtool --tag=CC --mode=link gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/sfw/include -g -Dsolaris2 -I. -I/usr/sfw/include -O -Wall -Wsign-compare

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Udo van den Heuvel
Udo van den Heuvel wrote: Arjen de Korte wrote: Please start by providing some information. What NUT version are you using, what driver? The FC6 binary for 2.0.3-2.1. I use the Mustek PowerMust driver with a Sweex UPS. Before trying anything else, upgrade to nut-2.0.5. OK, done. (did my

RE: [Nut-upsuser] make errors on solaris express dev 02/07

2007-03-06 Thread Zoltan Farkas
This is the configure I have executed: ./configure --with-user=ups --with-group=ups Here are the versions of the tools: $ libtool --version ltmain.sh (GNU libtool) 1.5.22 (1.1220.2.365 2005/12/18 22:14:06) $ autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Udo van den Heuvel
Udo van den Heuvel wrote: (cut) Looked over the configs which were (mostly) unchanged from the previous version. What's the cause for this vague message? The Megatec starts OK, then the upsd cannot connect to the ups (megatec...). If I start the daemons manually, following the info at

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Charles Lepple
On 3/6/07, Udo van den Heuvel [EMAIL PROTECTED] wrote: Udo van den Heuvel wrote: (cut) Looked over the configs which were (mostly) unchanged from the previous version. What's the cause for this vague message? The Megatec starts OK, then the upsd cannot connect to the ups (megatec...). If

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Arjen de Korte
Udo van den Heuvel wrote: If I start the daemons manually, following the info at http://www.networkupstools.org/doc/2.0.1/INSTALL.html The programs start OK, no error there. How can I automate this? Why don't the scripts work OK? Which script did you use? I can only guess that the script is

[Nut-upsuser] cannot connect to usb ups on solaris express 02/07

2007-03-06 Thread Zoltan Farkas
I cannot connect to my ups (USB tripplite 1000omniLCD): # ./usbhid-ups -DD -u root -a z2ups Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) debug level is '2' Checking device (0424/2228) (/dev/usb/424.2228/0) - VendorID: 0424 - ProductID: 2228 - Manufacturer: Generic -

Re: [Nut-upsuser] cannot connect to usb ups on solaris express 02/07

2007-03-06 Thread Charles Lepple
On 3/6/07, Zoltan Farkas [EMAIL PROTECTED] wrote: I cannot connect to my ups (USB tripplite 1000omniLCD): [...] lrwxrwxrwx 1 root root 58 Mar 5 21:17 hid1 - ../../devices/[EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED],1/[EMAIL PROTECTED]:hid_-124_4 NUT depends on libusb to

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Udo van den Heuvel
Arjen de Korte wrote: Udo van den Heuvel wrote: If I start the daemons manually, following the info at http://www.networkupstools.org/doc/2.0.1/INSTALL.html The programs start OK, no error there. How can I automate this? Why don't the scripts work OK? Which script did you use? The

Re: [Nut-upsuser] nut upset after Oops

2007-03-06 Thread Arjen de Korte
If I start the daemons manually, following the info at http://www.networkupstools.org/doc/2.0.1/INSTALL.html The programs start OK, no error there. How can I automate this? Why don't the scripts work OK? Which script did you use? The standard scripts that come with the rpm. We, the NUT