search for: bayli

After installing NUT, I've noticed that the belkin driver capabilities are rather basic. We have a Belkin Regulator Pro 1400VA (F6C1400-EUR), so I've updated the driver to support control of the buzzer & tests, as well as adding test result reporting. I've attached the following patches. Hopefully they can be added to any upcoming versions. -- John Bayly Systems Administrator

...e Directory structure in place as well. We will keep away from it as long as we can but may end up having to put it in. I want to gather information before this happens. Can you please direct me to any information you have about Microsoft Active Directory within a Samba environment. -- Mark Baylis Swyddog Cynnal Rhwydwaith Network Support Officer mark.baylis@powys.gov.uk Tel: 0845 0580428 FAX: 01597 826221 Mae'r e bost hwn ac unrhyw atodiad iddo yn gyfrinachol ac fe'i bwriedir ar gyfer y sawl a enwir arno yn unig. Gall gynnwys gwybodaeth freintiedig. Os yw wedi eich cyrraedd trwy...

On Wed, 2 Feb 2000, Harald at iki.fi wrote: > How come I can't get scp to work properly. It just complains like this: > > scp foo host: > bash: scp: command not found > lost connection Maybe you should check for the path on the remote machine: it seems like the remote shell can't find scp in its $PATH. -- Dominik - http://www.saargate.de/~domi/

I've patched the belkin driver to add the test commands & beeper control, as well as reporting the beeper and test status. I've submitted them to the nut-upsdev list, but haven't heard anything back. Is there a place or person I can contact to submit changes to? Thanks, John

I've discovered an issue (which may be unique to my UPS) with this commit. init_communication now returns -1, instead of 0 if it failed to read the manufacturer info, this makes sense after all. With my UPS (Belkin F6C1400-EUR), the response to the Manufacturer command returns only 6 spaces (rather than "BELKIN"), this means that init_communications fails, and the driver fails

On 14/01/2011 20:40, Arnaud Quette wrote: > Author: aquette > Date: Fri Jan 14 20:40:06 2011 > New Revision: 2832 > URL: http://trac.networkupstools.org/projects/nut/changeset/2832 > > +link:http://www.networkupstools.org/source/2.6/nut-2.6.0.tar.gz.sig[signature] May I suggest that you also provide checksums for the tarball? I'm updating the FreeBSD port, and wanted to

I am using Samba 3.0.20 with Sun Directory Server as a PDC. I have been running this setup for a year now, and I haven't had any other issues, except this one... I have four Windows 2003 Servers that are domain members. On one of the 2003 Servers is being used as a Terminal Services Session Directory, and the other three 2003 Servers are Terminal Servers. I am trying to add the three

...g going wrong during driver initialization and device probing. Once again, I need answers to these two specific questions: 1) Is PCIe Advanced Error Reporting (including error injections) known to work in 5.5? 2) What configuration options do I need to select in order to enable it? Thanks, Neil Baylis

Are there any plans to allow us to specify UPS variables in ups.conf, eg: [evo_s_3000] driver = usbhid-ups port = auto desc = "Eaton Evolution S 3000" vendorid = 0463 productid = ffff ups.delay.shutdown = 120 ups.delay.start = 130 The reason I ask is that I'm using FreeBSD & gmirror and need to extend the gracetime

I've a Belkin Regulator Pro (F6C1400-EUR) connected via serial to a FreeBSD machine using NUT v.2.4.3 Sometimes I get a series of logged messages saying that the data is switching between stale and valid, this in itself isn't an issue, however occasionally when the communication is re-established, upsmon gets a "On battery" message followed quickly by "Battery low"

flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop

flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail

flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail

flight 17901 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 4 xen-install fail REGR. vs. 12557 test-amd64-i386-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-pv 4

flight 17916 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl-win7-amd64 4

flight 18150 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18150/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18181 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18181/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

...min.tissoires@gmail.com> Benjamin Tissoires <benjamin.tissoires@redhat.com> Benjamin Vahl <bvahl@net.t-labs.tu-berlin.de> Benjamin Wang <cpwang2009@gmail.com> Benny Halevy <bhalevy@tonian.com> Benoit Cousson <b-cousson@ti.com> Benoit Cousson <bcousson@baylibre.com> Benoit Cousson <benoit.cousson@gmail.com> Benoit Cousson <benoit.cousson@linaro.org> Benoit GAUTHIER <benoit.gauthier-xsig@stericsson.com> Benoit Goby <benoit@android.com> Benoit Gschwind <gschwind@gnu-log.net> Benoit Lecardonnel <Benoit.Lecar...

...min.tissoires@gmail.com> Benjamin Tissoires <benjamin.tissoires@redhat.com> Benjamin Vahl <bvahl@net.t-labs.tu-berlin.de> Benjamin Wang <cpwang2009@gmail.com> Benny Halevy <bhalevy@tonian.com> Benoit Cousson <b-cousson@ti.com> Benoit Cousson <bcousson@baylibre.com> Benoit Cousson <benoit.cousson@gmail.com> Benoit Cousson <benoit.cousson@linaro.org> Benoit GAUTHIER <benoit.gauthier-xsig@stericsson.com> Benoit Goby <benoit@android.com> Benoit Gschwind <gschwind@gnu-log.net> Benoit Lecardonnel <Benoit.Lecar...

We're looking at supplementing our Belkin Regulator Pro 1400 with a 2nd UPS, and were contemplating the APC's 3kVA Smart UPS LCD. We'd still be using either our existing FreeBSD box or a CentOS box to control the UPS. I was just wondering if anyone's got much experience with using these with NUT. From the NUT compatibility guide, it says it uses the usb-hid driver. It also