similar to: i'm confused

Summary ======= I have encountered problems with the nut shutdown sequence using the directory structure in the packages for Fedora Core 4. These problems occur when the /var file system is mounted as a separate volume. I have done some investigation and think that I have an answer, but I need verification from someone who has more experience from nut on a wider variety of systems. I want to

On mar., 2011-01-18 at 19:52 +0000, Arjen de Korte wrote: > Author: adkorte-guest > Date: Tue Jan 18 19:52:02 2011 > New Revision: 2845 > URL: http://trac.networkupstools.org/projects/nut/changeset/2845 > > Log: > Prefer to use static variables locally over global variables (to prevent namespace conflicts) > > Modified: > branches/windows_port/common/common.c

Listmates, After wrangling with the voltage value on the CyberPower 1000AVRLCD and now having 2 of them working, I though it would be a simple matter to move my APC BP650 from apcupsd to nut so that all 3 servers would be monitored on the same web interface. The APC is attached to an older box running openSuSE 11.0 with nut-2.2.2-66.1. (nut-classic). The APC BP650 uses a serial connection

Denny, The first three commands had outputs but the "clog /var/log/system.log | grep -i ups” didn't output any. Did I do anything wrong? This is the output without the grep: can't allocate llinfo for <Public IP> on igb0 Aug 14 18:14:59 pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug 14 18:15:00 pfSense kernel: arpresolve: can't

Hello, I am working on getting NUT working with my Smart-UPS 900 UPS (with the C c= able) For several years, I have used the apcupsd product, but because of the nagios support for nut, I am working on switching over. Under apcupsd, I get tons of information from my UPS: # /usr/local/sbin/apcaccess status DATE : Sat Jul 09 12:56:41 CDT 2005 HOSTNAME : homer RELEASE : 3.8.6 UPSNAME :

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

Hi,   We've deployed Xen 3.0.2-2 successfully on a CentOS 4.3 installation running on a Dell PE 2950 servers. On a HVM/VMX guest also running CentOS 4.3 with the configuration below, we see occasional DMA messages in the guests dmesg output, they don't occur often and for no obvious reason - it seems they normally occur when the load on the host system is low.   hda: dma_timer_expiry: dma

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

> On Aug 13, 2018, at 06:17, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong <kevindd992002 at yahoo.com> wrote: >> >> Hi, >> >> I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date

I need a little help on this problem, please? I include my /etc/apcupsd/apcupsd.conf file is attached. port 3551 udp/tcp has been added to the (running) firewall. My APC is recognized as: APC Back-UPS 450 FW:844.Kld.D USB FW:Kld This from the hardware browser. PS says: root 2419 0.0 0.0 4196 584 ? Ss Mar23 0:09 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf Is group 2419 the

Hi, I've found that upsdrvctl crashes when there is not ports= specified ups.conf #0 __strrchr_sse2 () at ../sysdeps/x86_64/strrchr.S:33 #1 xbasename (file=0x0) at common.c:266 #2 stop_driver (ups=0x1e163e0) at upsdrvctl.c:135 #3 send_all_drivers (command=0x4020f0 <stop_driver>) at upsdrvctl.c:446 #4 main (argc=1, argv=0x7ffff30be9c0) at upsdrvctl.c:565 stop_driver

Hello, the appended patch converts the reason of transfer to be human readable. How about adding this variable to the usbmon message when it detects being on battery? Michael ---------------------------------------------------------------------- --- ./drivers/apcsmart.h.orig 2009-12-09 16:52:56.000000000 +0100 +++ ./drivers/apcsmart.h 2009-12-09 16:54:34.000000000 +0100 @@ -98,6 +98,7 @@

I'm not sure I understand your question. The UPS was running for more than 15 minutes before it went below the battery.charge.low: of 70. Below is my /etc/nut/nut.conf. My goal is that when the UPS report a battery.charge.low of < 70 (or, if possible has been running for 5 minutes) it starts the shutdown process. The shutdown process should take 15 minutes so that proxmox can shutdown

I've documented a desire to do this for a while, time to actually follow through and support connecting as a client to a TCP server. Note that it is desirable to support the plugin connecting to an encrypted server over TCP, then exposing the raw data over a local Unix socket; that aspect requires yet more work, left for another day. But even allowing an old-style client to connect to an

Hi. rsync 3.0.8 FreeBSD RELENG_4 i386. rsync -Haxi --delete /.../ /.../ The first pathspec above (residing on zz, a full filesystem) is: /vvvv/wwww/xxxx/zz/ The second pathspec above (residing on yyy, an empty filesystem) is: /vvvv/wwww/xxxx/yyy/zz/ It's obviously a 'copy everything over' operation. I've had to obfuscate the pathnames, however the exact pathlength throughout

gcc 8 gripes (when using './configure --enable-gcc-warnings'): nbd.c: In function 'nbd_open': nbd.c:470:3: error: 'strncpy' specified bound 108 equals destination size [-Werror=stringop-truncation] strncpy (sock.sun_path, sockname, sizeof (sock.sun_path)); The warning is a false positive, given that we currently reject names >= sizeof(sock.sun_path), and thus we are

This is a minimal implementation of an NBD forwarder; it lets us convert between old and newstyle connections (great if a client expects one style but the real server only provides the other), or add TLS safety on top of a server without having to rewrite that server. Right now, the real server is expected to live on a named Unix socket with no encryption, and the transactions are serialized

I hate to be a pest, but are there any revelations on file descriptor "overusage" by dovecot-auth? ----- Forwarded message from Steven F Siirila <sfs at tc.umn.edu> ----- Date: Sat, 20 Jan 2007 12:42:50 -0600 From: Steven F Siirila <sfs at tc.umn.edu> To: Dovecot Mailing List <dovecot at dovecot.org> User-Agent: Mutt/1.4.2.1i Subject: Re: [Dovecot] dovecot-auth file

With new enough libnbd, we already support vsock by virtue of uri=; however, it's also nice to allow direct exposure of the nbd_connect_vsock() api. Signed-off-by: Eric Blake <eblake@redhat.com> --- As with commit 7ce9feef, there is no easy way to add testsuite coverage for this. plugins/nbd/nbdkit-nbd-plugin.pod | 30 +++++++++----- plugins/nbd/nbd.c | 65