similar to: HOWTO video from +superlinux

i am assigned a network to replace its "Windows server with ISA caching proxy" with another "debian linux with squid proxy" with both "linux" and "ISA" are completely differnet boxes. i am using linux 2.6 kernel since the linux server has SATA hard disks . the network has downlink with a penta@net DVB card for down-link ; then it''s connected

On Oct 2, 2014, at 1:53 AM, Tarvo Tiits <Tarvo.Tiits at automaatika.ee> wrote: > On 02.10.2014 03:42, Charles Lepple wrote: >> On Oct 1, 2014, at 5:07 AM, Tarvo.Tiits at automaatika.ee wrote: >> >>> Why is ups.status empty? >> If I understand the commit log for SVN r3590, then that revision was supposed to set the status to OL if the numeric state was 9 for

> To be honest, I haven't experimented much with this, but I saw a normal shutdown/reboot when I just tried this from the command line (10.12): > > reboot ~ Mon Jun 12 08:36 > shutdown ~ Mon Jun 12 08:35 > clepple ttys007 Sun Jun 4 21:52 - shutdown (7+10:43) > However, the "-u" flag did not

I think the high CPU usage was caused by the native OS X driver crashing and not working properly. The native driver was not sensing the UPS going on battery or any change in battery percentage. Unplugging the USB and then plugging it back again made the native driver come back up again properly. Restarting the macosx-ups driver seems to get back to normal CPU usage. I will monitor and see how it

Hi, There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some work on it. The bug manifests itself as a stop of monitoring with no alarm when the clock is moved backwards in time. Please consider adding this to the

Hello all, With a really fast lookup, I think it is probably a problem of NSS initialization (key loading...) . As the problem occurs only when upsd is forked and as nss is initialized ( https://github.com/networkupstools/nut/blob/master/server/upsd.c#L1008)before upsd deamonify ( https://github.com/networkupstools/nut/blob/master/server/upsd.c#L1035), I suspect NSS to not be fork-safe. I will

Attached is the first 32 seconds of the driver output after applying the patch which fixes the battery scaling problem for this UPS. Matthew Stapleton Email: matthew4196 at gmail.com On 10/08/14 01:27, Charles Lepple wrote: > On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com>

hi. i am rani ahmed, a palestinian (superlinux if u recall). i use redhat 9.0 and samba-2.2.7a-7.9.0. i know that i should update my samba but i dont think my problem has to do with updating. the file given is my samba config file. btw: i think ur software is better than microsoft's file sharing. i mean that scientifically. i am using DNS server (named). my unix domain is superlinux.com

Success !! at least in the compile and build of the Cygwin *.exe's git clone git://github.com/networkupstools/nut.git ./autogen.sh cd nut ./autogen.sh ./configure --with-all=auto --with-doc=auto make install problem was in : /* genericups.c - support for generic contact-closure UPS models Copyright (C) 1999 Russell Kroll <rkroll at exploits.org> This program is free

[Please keep the list CC'd - thanks!] > On Jun 3, 2016, at 11:58 AM, Marcos Martinez <marcosdmm at gmail.com> wrote: > > But I have to use my ups MIB file?? > Megatec gives a MIB file from his webpage, I think is NetAgent mini MIB. > I have to use that?? I am not familiar with all of the MIBs, but the NUT driver incorporates information from the supported MIBs - it

Let's try the dev list. Anyone have a spare USB UPS they can test against? The fix is for Tripp Lite and OS X, but I'm looking for other data points because the code is common to nearly *all* of the USB drivers, and could break them. Thanks! On Aug 16, 2014, at 5:25 PM, Charles Lepple <clepple at gmail.com> wrote: > If you have a USB UPS, and can rebuild NUT from source

[please keep the list CC'd, thanks] > On Aug 14, 2015, at 10:27 AM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Would it put NA in the log files if maxage was too short? I think so. I haven't tried it, but if snmp-ups polls every 30 seconds, and MAXAGE is 15, then with a random polling interval, 50% of the time the data would be more than 15 seconds old. In

On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: >> >>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage

Hi Charles, while finishing the Testing release, I faced an autoreconf issue on Testing, linked to the below change (to its non application on Testing in fact): include/Makefile.am:9: shell unset LANG && svnversion -n $(top_srcdir: non-POSIX variable name include/Makefile.am:9: (probably a GNU make extension) include/Makefile.am:10: shell if test "$(SVNREV: non-POSIX variable name

It's arbitrary to me what version I start from, I had just grabbed the latest 2.7.2 tar. How do I get the version that you suggest I start from? git clone? Or do I just change the .tar file I have with what you linked (changes the 52-* file to 62-*) Sincerely, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Monday, March 09,

I wasn't clear. battery.runtime.low is not a counter, but a value estimated in seconds that is decreasing conforming the battery is discharging. It's mean: How much time (in seconds) will be necessary until the battery achieve the depleted status ( http://www.networkupstools.org/protocols/sec.html#Estimated_Minutes ) . If the UPS don't have a load, this value will be higher than the

Greg, I think I fixed it. Thanks for your patience. https://github.com/networkupstools/nut/pull/213 Diffs: https://github.com/networkupstools/nut/compare/usbhid_ups_input_vs_feature If anyone else can test usbhid-ups against their hardware before I merge this to master, I would appreciate it. I tried my MGE UPS on a Linux box as well, and it does not get interrupt events there, either. -

On Jul 29, 2013, at 7:56 AM, Charles Lepple wrote: > On Jul 29, 2013, at 6:43 AM, Pavel Potcheptsov (EKTOS) wrote: > >> Hello list, >> I have explored https://github.com/networkupstools/nut repository >> and found that Riello UPS added into list of supported UPS. >> But current package for most distribution it's nut-2.6.5 which >> doesn't have

Hi Charles, The NAS is a QNAP 659-II It appears that NUT is installed: http://www.qnap.com/en/index.php?sn=4059 http://www.qnap.com/en/?lang=en&sn=940 http://docs.qnap.com/nas/en/index.html?ups_settings.htm -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: Saturday, 22 June, 2013 00:47 To: Massimo Savazzi Cc: nut-upsuser at lists.alioth.debian.org

Hi David and Charles Le 3 mars 2017 2:35 PM, "Charles Lepple" <clepple at gmail.com> a ?crit : > On Mar 3, 2017, at 8:21 AM, Charles Lepple <clepple at gmail.com> wrote: > > > > On Mar 2, 2017, at 3:38 PM, David Baker <david at baker.im> wrote: > >> > >> I?ve read the documentation, and it would appear that this can be set > by the