similar to: [Fwd: Re: [Nut-packaging] Nut-packaging post from richard@aardvark.com.au requires approval]

FWIW the tcpdump will be a few days at http://rosa.stappers.nl/ff/tcp_w.pcap md5sum a8090ca85202d62ddd5a3d5684b2e8fd tcp_w.pcap ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Thu, 06 Jun 2013 12:49:11 -0700 From: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from upendra.gandhi at gmail.com requires approval Message-ID:

Op 2014-01-13 om 10:29 schreef syslinux-owner at zytor.com: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: Syslinux at zytor.com > From: zmau1962 at gmail.com > Subject: Re: [syslinux] (no subject) > Reason: Post by non-member to a members-only list > > At your convenience, visit: >

Hi Elio, once more, your email was blocked due to the 40 Kb limits... note that here, NUT Monitor screenshots were not needed. upsc output is sufficient. From: Elio Parisi <E.Parisi at riello-ups.com> > To: "nut-upsdev at lists.alioth.debian.org" < > nut-upsdev at lists.alioth.debian.org> > Cc: > Date: Fri, 23 Nov 2012 15:05:49 +0100 > Subject: Riello patch

> Here is more informations. I hope this can help. Tell me if you need other > information. > > Version : Network UPS Tools upsd 2.2.0- > Driver : usbhid-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core > 0.30 (2.2.0-) Many improvements have been made to usbhid-ups since 2.2.0. You may want to upgrade, or at least check the

>> Over the last couple months, we have had a couple incidents (luckily a= ll >> on weekends) where all 15 UPSs will mysteriously shut off, and we had = to >> manually power them back up. To top it off, there was nothing in syslo= g >> about any UPS going onto battery power and staying there - just a coup= le >> curious low-battery warnings from one of the UPSs. You

Since reports received over the interrupt pipeline are a recurring problem for various types of UPS'es, I propose to simply ignore the data we receive there and only flush the respective report buffer. By doing so, at the time the interrupt reports are processed the first variable that is retreived will trigger a poll for the corresponding feature report and we should be fine. The impact on

Dear Moderator, Please post the following on your job board. Thanks!! *************************************************************************************************************** My client in Bay Area, CA is looking for 5 FreeBSD kernel developers for contract only/ contract to Hire / Fulltime positions. Here are the details: Title: SOFTWARE ENGINEER (FREE BSD KERNEL) - 5 positions Job

I recently installed NUT 2.2.1 and set it up with a Belkin F6C100-UNV. I can monitor it via serial (belkinunv) or USB (usbhid-ups) cable, and both do seem to work fine, but I would prefer USB to avoid having to add a PCI serial card to the machine. I had to unplug something else to try it with a serial cable. Using 'belkinunv', there's a "-x wait" option: [ from

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

Hello, Usually is it easy to identify a valid non-subscriber-posting. Example given: the four postings about "bugzilla is back" in last day. Today there is a posting from the data plane development kit project, http://dpdk.org/ DPDK is a set of libraries and drivers for fast packet processing. Packets being network packets. That posting is not spam, but it should not go to this

I'm forwarding Marco's msg to the list, since it's really too big, and embeds upsc/upsrw/upscmd binaries! cheers, Arnaud -- Engineering Linux/Unix Expert - Opensource Solutions Lead - Eaton - http://opensource.eaton.com NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr

Alex: Any idea why the list is still bouncing these? "noreply at rubyforge.org" is in the list of addresses that are supposed to be allowed to post even though not subscribed. What is that about "Message has implicit destination"??? Kevin -------- Original Message -------- Subject: Wxruby-development post from noreply at rubyforge.org requires approval Date: Sat, 21 Oct

Hi Peter Now I can get subdrivers to have ups.conf/command-line options, I've started looking at making the newhidups belkin-hid subdriver have the wait and wait-on-shutdown behaviour in the same was as belkinunv, and having just gone back and gone "yuck!" at my huge comments in my revised belkinunv source, I decided to clear out all the extraneous commentary in my

Hi all! The following files emits warnings when compiled with gcc 4.0: al175.c bcmxcp_ser.c belkinunv.c cyberpower.c everups.c powercom.c solis.c All warnings seem to be of this variety: everups.c:38: warning: pointer targets in passing argument 2 of 'ser_get_char' differ in signedness I suggest that those who fiddles with those drivers fixes the warnings and verifies that it works

Hi Arjen My apologies fro drifting off topic in the other mailing list...:-) On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV The "au" is for Australia I think. "man belkinunv" states that F6C120-UNV is supported - and I assumed that the "au" would not prevent this. I plugged in the USB to gather the information you requested. My intention

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

Dear fellow NUT developers, after almost exactly two years as a NUT developer, I have concluded that this would be a good time to retire from active development. The project is in good shape, and the driver I was most involved with (usbhid-ups) is in better condition than ever, due to the excellent recent work of Arjen de Korte. Having already scaled back my activity for the last 6 months, I

charge, but instead will be raised a few seconds before the power will be cut by the UPS, either because of a low battery event or a user initiated shutdown (with delay) command. The thing I don't like about that, is that by that time the shutdown sequence has apparently already started by the UPS, which means that we have no control over when the power will be cut. Also, if it indeed only

Hello, I installed NUT and configured it for 2 MGE UPS's connected via USB. Debian etch NUT package: # dpkg -l nut*|grep ^ii ii nut 2.0.4-3 The core system of the nut - Network UPS Tools ii nut-usb 2.0.4-4 USB Drivers subsystem for the nut - Network UP Separately, with only one UPS defined in ups.conf, each one works fine (I specified specific serial numbers for either, with