search for: wilcock

...reach the person managing the list at nut-upsdev-owner@lists.alioth.debian.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Nut-upsdev digest..." Today's Topics: 1. Re: questions re. patching bcmxcp.c and choosing variable names (Oliver Wilcock) 2. Buildbot up and running (Charles Lepple) ---------------------------------------------------------------------- Message: 1 Date: Sat, 7 Apr 2007 15:20:16 -0400 (EDT) From: "Oliver Wilcock" Subject: Re: [Nut-upsdev] questions re. patching bcmxcp.c and choosing variable names To: nu...

I certainly saw the issue with the non-APIC HAL, but I don''t see any performance or CPU issues with the APIC MP HAL. -Nick -----Original Message----- From: Venefax <venefax@gmail.com> To: ''James Harper'' <james.harper@bendigoit.com.au>, ''Oliver Wilcock'' <oliver@owch.ca>, xen-users@lists.xensource.com Subject: RE: [Xen-users] Xen GPL PV and undesirable requirement for APIC (irq >15) Date: Tue, 25 Nov 2008 10:03:48 -0500 I concur on seeing the issue. I changed the HAL to Standard PC (Non-apic) and the Xennet driver strangely got...

I've patched bcmxcp.c such that it can power cycle the outlet load segments independently on a Powerware PW5125 UPS. I presume that it will work for any XCP protocol UPS with 2 load segments. Should these instant commands be called outlet.1.shutdown.return outlet.2.shutdown.return ? Where do the descriptions displayed by upscmd -l come from? Presently it shows outlet.1.shutdown.return -

Also works if you want to shutdown one segment/outlet early in the power failure. It should stay off until utility power returns and then apply the configured delay - although I haven't tested this aspect. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bcmxcp.c.diff Url:

...k at what is available in the outlet.* collection. I still need to complete the docs/powersave.txt file... 2007/7/9, Kjell Claesson <keyson-guest at alioth.debian.org>: > Author: keyson-guest > Date: Mon Jul 9 19:48:51 2007 > New Revision: 1019 > > Log: > Patch from Oliver Wilcock - bcmxcp.c modified to control individual load segments (outlet.2.shutdown.return) on Powerware PW5125. > > Modified: > trunk/ChangeLog > trunk/drivers/bcmxcp.c > ... thanks, Arnaud -- Free Software Developer - http://arnaud.quette.free.fr/ Debian Developer - http://people.de...

Caller*ID used to work as some point, but I can't seem to get it going these days. The card is a x101p. I've tried going up and down the rxgain scale. Can the txgain effect it at all? When I plug in a phone into the line with a splitter it can decode caller id with no problems. Reading through the mailing list archives hasn't given me any move clues. Any ideas?

Hi, folks, I''m attempting to run an e-mail server on Xen. The e-mail system is Novell GroupWise, and it serves about 250 users. The disk volume for the e-mail is on my SAN, and I''ve attached the FC LUN to my Xen host, then used the "phy:/dev..." method to forward the disk through to the domU. I''m running into an issue with high I/O wait on the box (~250%)

I''ve found that if a vncviewer is already connected to a DomU (ie vncveiwer dom0server:5901) then another connection attempt hangs (it seems to go into a queue). Is it possible to change this behaviour in any of the following ways? - simultaneous connections mean that users fight over mouse and keyboard - the new connection breaks the old - the length of the connection is limited Are

> Date: Tue, 6 Jan 2009 13:58:55 +1100 > From: "James Harper" <james.harper@bendigoit.com.au> > Subject: RE: [Xen-users] GPLPV drivers problem > To: "Nick Couchman" <Nick.Couchman@seakr.com>, "Venefax" > <venefax@gmail.com>, <xen-users@lists.xensource.com>, > <lfernandes@lojav.pt> > Message-ID: