search for: gaffs

I noted some correspondence from several years back about supporting this device with bcmxcp, and the problems therein. Since I have one of these UPS units, still going strong, and the Eaton LanSafe stuff has finally caused me enough grief to abandon it, I figured I'd take a look at this. The issue is not that bad - the bcmxcp driver query of the topology block (2 bytes!) is returning

On Feb 28, 2014, at 7:49 PM, Tim Dawson wrote: > I just noted that I got my outputs reversed in my posting - the git version is the .26, with 2.7.1 being .28, which still seems odd . . . The "-3857M" suffix on the "0.26 (2.6.5-3857M)" version was generated from SVN. Is it possible that the driver is left over from another package? -- Charles Lepple clepple at gmail

Before responding to Jeff's posting, let me reiterate my question: Why does a function using m1*m1 produce an integer overflow, but m1^2 does not? As for Jeff's 'response': > a) Numeric values may be either integers (signed 32 bit) or double precision (53 bit mantissa). > b) Double precision constants are numeric with no decoration (e.g. 61224). Integer constants have an L

For fun, if you want to see where the system thinks it is linking a library from, you can use "ldconfig -p" and it will give you a path to all known libraries that it can find. If you have one loaded, and it can't find it (odd directory, etc.) you can always amend "LD_LIBRARY_PATH" the same way as PKG_CONFIG_PATH I mentioned earlier . . . . PKG . . . is for the build

---------- Forwarded message ---------- From: Tim Dawson <tadawson at tpcsvc.com> Date: Thu, Feb 13, 2014 at 12:07 AM Subject: Re: [Nut-upsuser] Powerware (Eaton) Prestige 9 UPS To: Charles Lepple <clepple at gmail.com> Charles - As a quick followup, the Prestige (both FW 2.13 and 3.09 - 2.x is pre-Eaton, 3.x post) reply to the topology block query thus: 3.064046

Before I make any serious gaffes, is this an acceptable place to post PHPAGI questions as well? I can't seem to find a dedicated mailing list for it. If not, any suggestions? Thanks, Jay

Hello, I'm new to this group so please accept my apologies for any gaffs I might make. My problem is this: I am running Samba 2.23 on RedHat 7.3. Using various unix permissions, users & groups & smbusers / smbpasswords I am able to control who see what shares. The Security in samba is set to users. and passwords are encrypted. What I would like to do is have o...

Looking for Powerware Prestige 9 Series 6000VA. If you know where I can buy one please respond. thanks!

Either it is not loaded, or the usb serial and/or hid drivers are not loaded, which appear to have been used on your Debian box. - Tim On February 24, 2014 1:12:36 AM CST, Josu Lazkano <josu.lazkano at gmail.com> wrote: >Thanks again. > >This is the lsmod output: > ># lsmod >aead 4256 0 >arc4 1312 2 >b43

First off, I have to say I really like the antispam plugin. I am running a (relatively) new freebsd 8.0 server with postfix/dovecot/dspam/squirrelmail and it works great. Create a SPAM folder and tell the dovecot antispam plugin to use INBOX.SPAM as the spam folder and drag messages from INBOX to the spam folder and they are trained as spam. Here is the problem though: after training

a) Numeric values may be either integers (signed 32 bit) or double precision (53 bit mantissa). b) Double precision constants are numeric with no decoration (e.g. 61224). Integer constants have an L (e.g. 61224L). c) 61224*61224 > 2^31-1 so that answer cannot fit into an integer. d) Exponentiation is a floating point operation so the result of 61224L^2L is a floating point answer that CAN

The following code snippet will not compile support for RSAref on NetBSD even if it exists on the system (which breaks OpenSSL): for WANTS_RSAREF in "" 1 ; do if test -z "$WANTS_RSAREF" ; then LIBS="$saved_LIBS -lcrypto" else LIBS="$saved_LIBS -lcrypto -lRSAglue

Just looked at your prior mail, and it was using 'usbhid' based on your output. If 'modprobe' exists on your router, what response do you get to 'modprobe usbhid'? - Tim On February 24, 2014 2:56:16 AM CST, Tim Dawson <tadawson at tpcsvc.com> wrote: >Either it is not loaded, or the usb serial and/or hid drivers are not >loaded, which appear to have been used

I have problem with integer overflow that I cannot understand. I have a character vector curr.lemmas with the following properties: length(curr.lemmas) # 61224 length(unique(curr.lemmas)) # 2652 That vector is the input to the following function: yules.k1 <- function(input) { m1 <- length(input); temp <- table(table(input)) m2 <- sum("*"(temp,

Thanks again. This is the lsmod output: # lsmod aead 4256 0 arc4 1312 2 b43 324014 0 bcma 28621 1 b43, button_hotplug 2800 0 cfg80211 172273 2 b43,mac80211, cifs 190077 0 compat 651 3 b43,mac80211,cfg80211, crc16 1015 1 ext4, crc_ccitt

Rob - Just stepping in from the sidelines . . . with a few tidbits. Nut uses pkgconfig to find and identify stuff as part of it's build . . . So, depending on where your libusb install went, if it wasn't in the default "PKG_CONFIG_PATH" setting, it won't be found. Much like other shell variables, you can adjust that setting to find anything you like . . . IE

Thanks again Tim. I installed openSUSE from scratch, without installing libusb anything. I tried configure, and it failed because it couldn't find libusb. I used ldconfig to see what the system could see. It found 3 entries with "libusb" in them. I then built and installed the last update of libusb-0.1 (not libusb-compat or libusb-1.0). I tried configure, and it ran without

Question: I just uploaded the git development repository, and upon building it, I note that on the bcmxcp driver, it would appear that the git tree is actually older than what is in the 2.7.1 release: Git: Network UPS Tools - BCMXCP UPS driver 0.28 (2.7.1) RS-232 communication subdriver 0.20 2.7.1: Network UPS Tools - BCMXCP UPS driver 0.26 (2.6.5-3857M) RS-232 communication subdriver 0.20

I just noted that I got my outputs reversed in my posting - the git version is the .26, with 2.7.1 being .28, which still seems odd . . . But at least Iam on the correct tree! Since I have seen some other questions regarding the Prestige, I was thinking of formalizing my changes into anactual patch. - Tim On February 28, 2014 5:40:29 PM CST, Charles Lepple <clepple at gmail.com> wrote:

...e: > Well, is ices 0.2.3 still being supported? not that I'm aware of. > Because I still can't get it to compile on the PPC > even with new version of LAME and ogg installed. Thats because your mixing shout versions, your using libshout from CVS and ices 0.2.3. There are some gaffs really, that what's causing this. Someone has tried to be smart by checking if another shout exists and using that instead of using the one in the tree, presumably for the idea of an updated libshout. > Here's the output from make: > make[3]: Entering directory `/usr/ices-0.2.3/src...