similar to: Re: [nut-Patches][303751] Checking UPS Temperature

Hi Eric, Can you send again your patches, to the nut list this time. It has been ripped off the mail, since it's violating Eaton Policy. Le dimanche 16 mars 2008 ? 15:38 -0400, Eric Wilde a ?crit : > I am enclosing several modules from NUT 2.2.1 that I have enhanced to > provide additional features. I sent these to Russell Kroll a while > back but I think it was right about the

I've made all the suggested changes - however, I'm having a bit of problem running the tests. I started "make check" and several hours later it had only made it through about 1/3 of the tests. I'm not sure what the deal is. On Mon, Jan 18, 2010 at 1:40 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 16, 2010, at 11:15 AM, Talin wrote: > > OK

OK here's a new version of the patch - and the unions.ll test actually passes :) On Mon, Jan 18, 2010 at 1:40 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 16, 2010, at 11:15 AM, Talin wrote: > > OK here's the patch for real this time :) >> >> On Fri, Jan 15, 2010 at 4:36 PM, Talin <viridia at gmail.com> wrote: >> Here's a work

Hello, The UPS I am developing a driver to is able to report several flags for critical hardware conditions, like overheat, overload, inverter failure, output short etc. What should be the correct policy of operation when such a condition occurs? I think that the an UPS in such a condition is not reliable and therefore a system shutdown should be called. However, the developer's manual and

On Jan 16, 2010, at 11:15 AM, Talin wrote: > OK here's the patch for real this time :) > > On Fri, Jan 15, 2010 at 4:36 PM, Talin <viridia at gmail.com> wrote: > Here's a work in progress of the union patch. Note that the test > "union.ll" does not work, so you probably don't want to check this > in as is. However, I'd be interested in any

Hello I am running Asterisk on SUSE Linux Professional 9.3 on a VIA Epia M Series motherboard - CPU runs at 1GHz. There is no fan - just a large heatsink. Currently system is running off standard IDE hard drive - because I couldn't get astlinux to run with my Digium TDM04B card (only PCI card in system). Strangely I also have the same system also running SUSE Linux running as a file

ping... On Thu, Jan 28, 2010 at 12:25 PM, Talin <viridia at gmail.com> wrote: > OK here's a new version of the patch - and the unions.ll test actually > passes :) > > On Mon, Jan 18, 2010 at 1:40 PM, Chris Lattner <clattner at apple.com> wrote: > >> >> On Jan 16, 2010, at 11:15 AM, Talin wrote: >> >> OK here's the patch for real this

Friends Briefly... In the documentation for lda in MASS it describes the value 'scaling' as 'a matrix which transforms observations into discriminint functions...'. How? Verbosely... I have a matrix of data. 9 independent variables and describing 3-classes. About 100 observations in total. A 10x100 matrix of data. I am trying to generate two discriminant functions and i

Full_Name: cajo ter Braak Version: 2.1.1 OS: Windows Submission from: (NULL) (137.224.10.105) # I would like to attach the matrix C in the Rdata file; it is 50x50 and comes from a geostatistical problem (spherical covariogram) > rm(list=ls(all=TRUE)) > load(file= "test.eigen.Rdata") > ls() [1] "C" "eW" > > sym.check = max(abs(C - t(C))) # should

Upgrading an ancient customer installation... was running 1.4.23.1 (Trixbox) with Zaptel 1.4.12.9 and a Sangoma A102D, which has been running fine for 5+ years. Customer getting anxious about hardware failure, so we built a new box and installed 1.8.24.0, Dahdi 2.7.0.1, and a new Sangoma A104D. The single active span is an RBS T1 B8ZS/ESF/E&M Wink. I tried to move one span over one

I would presume this is another manifestation of what I reported (reproduced below) on 2003-12-01. cajo.terbraak at wur.nl wrote: >Full_Name: cajo ter Braak >Version: 2.1.1 >OS: Windows >Submission from: (NULL) (137.224.10.105) > > ># I would like to attach the matrix C in the Rdata file; it is 50x50 and comes >from a geostatistical problem (spherical covariogram) >

https://bugs.freedesktop.org/show_bug.cgi?id=92959 Bug ID: 92959 Summary: [NV1F celcius GeForce4 MX] Rendering artifacts, screen corruption, system reset. Product: Mesa Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major Priority: medium

The list of status bits we're seeing has increased over the years. Currently for instance, the usbhid-ups driver has defined no less than 20 status bits (and I intend to add two more in the next couple of days, FRANGE and FANFAIL): #define STATUS_ONLINE 0x00001 /* on line */ #define STATUS_DISCHRG 0x00002 /* discharging */ #define STATUS_CHRG 0x00004 /*

Hello Daniel! On Tue, Sep 29, 2020 at 6:23 PM Daniel F. Dickinson <cshore at thecshore.com> wrote: > > Hello joão, > > To get more responses you should plaintext email (standard for open source development mailing lists) instead of HTML mail. I just can't believe that I was sending HTML e-mail. Thank you very very much for bringing this to my attention. I hope it is ok now.

As per https://github.com/networkupstools/nut/pull/1982 I'm looking to add a few more variables from the CyberPower SNMP MIB. At question in particular are the values added to the ups.status variable coming from the CPS-MIB::upsStatus.0 OID. These values are, from the MIB: upsStatus OBJECT-TYPE SYNTAX INTEGER { normal (1),

Simple Q but I can't find the answer in the archives (and am too lazy to look in the source, but then its 32 Celcius here... Do all digium cards provide the zapata timing? e.g. also the analogs (including the X100P) or only the E1/T1 -ones or do I need to use ztdummy on the analog cards? Thanks, Michiel Betel Consultancy Abelenlaan 19 T: +31 20 640 3018 1185 RT Amstelveen

On Tue, 29 Sep 2020, João Luis Meloni Assirati wrote: > The UPS I am developing a driver to is able to report several flags for > critical hardware conditions, like overheat, overload, inverter failure, > output short etc. What should be the correct policy of operation when such a > condition occurs? I think that the an UPS in such a condition is not reliable > and therefore a

Hi, I'm not sure if this is some throttling/DoS protection or a bug. I didn't see notice anything like it mentioned looking at the NEWS file from hg, this is on 2.1.7 on Debian stable. I have a client doing IDLE on INBOX.vomiteer. When individual messages arrive with some time interval in between them, I get EXISTS events for each message as expected. However, when I store a bunch of

Am 04.04.19 um 21:09 schrieb John McMonagle via samba: > It did not migrate a lot of attributes that are in active directory. > The most important one to us is "mail" > Others by ldap account manager names: > User name > First Name > Last Name > I'm sure there are others. Yes as Rowland said only a minimum of attributes are transferred. We wrote a script for

Dear Rhelpers I have the problem with initial values, could you please tell me how to solve it? Thank you June > p = summary(maxLik(fr,start=c(0,0,0,1,0,-25,-0.2))) Error in maxRoutine(fn = logLik, grad = grad, hess = hess, start = start, : NA in the initial gradient > p = summary(maxLik(fr,start=c(0,0,0,1,0,-25,-0.2),method="BFGS")) Error in optim(start, func, gr =