similar to: Error in FAQ

Hi Arjen, in server/upsd.c r731, you moved the call conf_load() from after check_perms() (~ l.1020) to before setupsignals() (~ l.989). The problem is that conf_load() needs to open the ups driver socket, and it assumes that STATEPATH is the current working directory. The directory is only set in l.1016. Therefore, the first attempt to open a socket will always fail. From the user's point of

> Feature Requests item #310492, was opened at 07/01/2008 09:57 > Status: Open > Priority: 3 > Submitted By: Arnaud Quette (aquette) > Assigned to: Nobody (None) > Summary: Allow to specify hostnames in ACL (upsd.conf) > Category: None > Group: None > > > Initial Comment: > allow a new ACL form: > ACL hostname/mask > > example: > ACL localhost

I'm trying to see if we can make upsd autodetect the driver sockets from the STATEPATH. This works quite well and uses surprisingly little code (much less than parsing the 'ups.conf' file). However, since I can no longer read the name from the 'ups.conf' file, I need to extract this from the name of the socket. We might simply strip the drivername from the socket name again,

I'll be back one more time perhaps I found the reason of these errors Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale it happens when daemon upsd et upsmon are started after the boot obviously, there isn't any errors when upsd and upsmon are started at boot following later ... -----Message d'origine----- De : goudard sabine Envoy? : mardi

2006/11/16, Arjen de Korte <adkorte-guest@alioth.debian.org>: > Author: adkorte-guest > Date: Thu Nov 16 21:16:40 2006 > New Revision: 585 > > Modified: > trunk/ChangeLog > trunk/conf/upsd.conf.sample > trunk/server/conf.c > trunk/server/upsd.c > trunk/server/upsd.h > Log: > upsd: add MAXINIT parameter to upsd.conf to make the time upsd

I think I have found a way to deal with the issue of the spurious message on startup of NUT. Before implementing it, I would like to see what the other developers think of this idea. My proposal is not to wait for DUMPDONE in the startup of upsd for a duration of MAXINIT seconds, but rather to send the fake "INIT" status in response to a ups.status request. As soon as DUMPDONE hits, or

While browsing the sources of the nss-ssl-port sources I noticed that client certificates were added. What is the reason behind this? As far as I can see, using a server certificate and validating it in the upsmon client should provide us with a secure channel. Authorizations for the server will then be handled by the settings in upsd.users by logging into the server with user and

In my latest patch, I hardcoded the port NUT uses for TCP communication (3493). The reason is, that I can't figure out a way how to change the numeric value of the #define'd PORT into a character string. Using snprintf() and a temporary buffer just seems wrong, since this should be handled by the preprocessor, rather than at runtime. The following files are affected: - server/conf.c (line

(Arjen - I apologize if you get two copies, I sent the first one to the old de-korte.org address) Arjen, all, I've run into a usbhid-ups problem with nut on Arch Linux with the new 2.6.35 kernels. (latest is 2.6.35.4-1) For some reason when you get to the udev events on boot and it tries to load the usbhid-ups driver, it hangs until the 120 sec timeout occurs and then boot continues but

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

Arjen, I just installed openSuSE 11.1. I though it would be simple to setup the same CyberPower CP1000AVRLCD on the same machine that we worked through the 20+ voltage issue with, but usbhis-ups driver is failing for some reason. I have gotten the output I remember you needing from the last issue for you. What do you think the problem might be? Here is the information: First the logs from the

Can anyone give me insight into upsrw? I have a cyberpower PR2200 UPS (running an experimental version of the powerpanel driver hot off the presses by Arjen (thanks Arjen!!)). When I try to run "upsrw -s xyz=abc" to set any available variable, I get "Set variable failed: Access denied". What user name and password is it looking for here? My upsd.users file has 2 users

Currently, the 'upsd' server uses 'ups.conf' to find out which drivers should be running and uses this information to construct the socketname it needs. This means that drivers that have not been configured in 'ups.conf' can never be seen by the server. If we ever want to autodetect (by whatever means) what drivers are started (udev?) and we start them automatically, this

Hi, I've been trying to get my new Tripplite OmniVS100 UPS (USB Connection) to work on my system. What I have is: Ubuntu 10.04 Server Nut 2.4.3 /etc/nut/ups.conf [omni] Driver = usbhid-ups Port = auto Desc = "My Server" /etc/nut/nut.conf MODE=standalone I followed the instructions at this link:

Citeren Emilien Kia <emilienkia-guest op alioth.debian.org>: > Author: emilienkia-guest > Date: Fri Jan 7 14:44:25 2011 > New Revision: 2809 > URL: http://trac.networkupstools.org/projects/nut/changeset/2809 > > Log: > Deprecate CERTFILE conf var to the benefit of CERTPATH : homogenize > conf directive names. > > Modified: >

---> On 15/03/2009 8:00 AM, nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 1 > Date: Sat, 14 Mar 2009 21:47:08 +0100 > From: Arjen de Korte <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Weird Load and Battery Temp Readings > To: nut-upsuser at lists.alioth.debian.org > Message-ID: <20090314214708.37122w00w79l6u9s at mail.de-korte.org>

On Tue, 31 Jan 2006, Arjen de Korte wrote: > > But I'd like to know what I'm testing. Could you please post a bug tracker > > URL? I'm having trouble finding #302338. > > That may be because I closed the bug (maybe a little overenthousiastic). See > > http://alioth.debian.org/tracker/index.php?func=detail&aid=302338&group_id=30602&atid=411542 >

Great, thanks Arjen! Now we need an autoconf test to set HAVE_IPV6 automatically. I will look into what functionality needs to be tested; the test can be refined as problems arise later. -- Peter Arjen de Korte wrote: > > Author: adkorte-guest > Date: Sat Jan 6 19:39:08 2007 > New Revision: 710 > > Modified: > trunk/ChangeLog > trunk/clients/upsc.c >

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

With the Ipv6 patch (r708), I get: upsclient.c: In function `upscli_connect': upsclient.c:469: `AI_ADDRCONFIG' undeclared (first use in this function) upsclient.c:469: (Each undeclared identifier is reported only once upsclient.c:469: for each function it appears in.) Even if it doesn't break IPv4 support, it may break portability, as IPv6 seems to require specific functions that are