similar to: Printing fails above a certain size

Okay, now that I've got NUT up and running with the newhidups driver, I can give it a quick shakedown. Most of the values look good, but are few are off. Here's what I get: elrond@foxstar:~$ upsc foxstarups@localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 3150/08/01 battery.mfr.date: 2005/03/22 battery.runtime: 1935 battery.runtime.low: 120

Hello, I am having trouble getting upsd to start. I am using the Debian NUT packages version 2.0.3 (current in Debian/sid). I am using the newhidups driver with an APC Back-UPS BR 800. The init.d script wasn't functioning, so I backtracked to running upsd manually and I get: foxstar:/etc/nut# upsd -u root Network UPS Tools upsd 2.0.3 Can't connect to UPS [foxstarups] (newhidups-auto):

Hello, Upon upgrading to the Debian package of NUT 2.2.0 my APC Back-UPS Pro is no longer recognized. Here is the output if I try to run the driver manually: ----------- # /lib/nut/usbhid-ups -DDD -x vendorid=051d -x productid=0002 -a foxstarups Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) debug level is '3' No appropriate HID device found No matching HID

Hello all, I am trying to leave a video voicemail but am unable to do so. I am using Ekiga (formerly Gnomemeeting) to make a SIP connection to Asterisk 1.2.4. Ekiga supports h261 for video. The call connects and negotiation seems okay. When I leave a message, however, only the audio is recorded. Looking in the log file afterwards I see many messages like this: Mar 21 22:02:34 WARNING[2418]

There is a problem in MacOS X with multiple definitions of the same symbol in different files that will be put into the same bundle or dynamic library by the dynamic linker. It occurs, for example, in the rpart package, which includes rpart.h in all its source files, and rpart.h has definitions of a structure rp and functions rp_init and so on. I think the same problem occurs in the grid package

I have Samba 3.0.9 on SuSE 9.2 on a P-III-500 with only 352mb of RAM. The share I'm copying to is on a SCSI RAID array handled by a Compaq Smart-2/P RAID Controller (rev 04) as identified by lspci. The RAID is all LVM and the share is ReiserFS-- maybe not the best choice for something which is so slow to write to. Anyhow, the problem is that when I copy to the share "movies" it

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, sorry to bother you with this. I'm trying to set up an experimental system (which may become production if it ever gets off the ground) and it's not working. The short version: I'm trying to get Dovecot 1.2.4 to authenticate against a customised PAM module. In short, we're using a specialised OTP radius backend. One of my

Hi, Now that --enable-experimental-targets build flags have been added to the build systems. What needs to be done in order to get the R600 backend added as an experimental target? I've posted an updated version of the backend to llvm-commits[1], that addresses many of the criticisms of the backend, but I haven't received any feedback, and I feel like the submission process has stalled.

Hi, I would like to try to keep the staging area discussion going. There seems to be a general consensus that a staging area for backends and also new features would be acceptable for the LLVM project. What actions are required to make the staging area a reality? Is more discussion needed? Is anyone willing to volunteer to be the "Code Owner" for the staging area, to help move the

On Fri, Jul 27, 2012 at 01:30:49PM -0400, Justin Holewinski wrote: > On 07/27/2012 01:01 PM, Tom Stellard wrote: > >Hi, > > > >I would like to try to keep the staging area discussion going. There > >seems to be a general consensus that a staging area for backends and also > >new features would be acceptable for the LLVM project. What actions > >are required

FYI >Mailing-List: contact vulnwatch-help@vulnwatch.org; run by ezmlm >List-Post: <mailto:vulnwatch@vulnwatch.org> >List-Help: <mailto:vulnwatch-help@vulnwatch.org> >List-Unsubscribe: <mailto:vulnwatch-unsubscribe@vulnwatch.org> >List-Subscribe: <mailto:vulnwatch-subscribe@vulnwatch.org> >Delivered-To: mailing list vulnwatch@vulnwatch.org

Greetings, I am running samba 2.2.5 win RedHat 8.0 Linux machine Windows 2000 machine has fixed IP 192.168.0.40 Windows XP machine has fixed IP 192.168.0.30 Linux machine has fixed IP 192.168.0.1 on eth0 (local network NIC) and dynamic IP on eth1 (NIC connected to ADSL modem). I can ping 192.168.0.1 ( linux machine) from all machines I can ping 192.168.0.40 ( windows 2000 machine) from all

Dear Tom, Looks like setting LCOMMDirectiveType in AMDGPUMCAsmInfo.cpp is not needed anymore? I commented it out, and then LLVM got compiled fine. - D. 2012/9/6 Tom Stellard <tstellar at gmail.com>: > Hi, > > Now that --enable-experimental-targets build flags have been added to > the build systems. What needs to be done in order to get the R600 > backend added as an

JohnG <mcsjgs@cox.net> wrote: > I run OS X 10.3.7 on a PowerMac MDD G4 on a cable broadband connection. > I have reason to think my system has been tampered with. Security > features in Mac OS X have been left unlocked (Preference Pane - Users) OSX is substantially different from FreeBSD (even without netinfo) despite having some of the same source code. I doubt you'll find

On 07/27/2012 01:01 PM, Tom Stellard wrote: > Hi, > > I would like to try to keep the staging area discussion going. There > seems to be a general consensus that a staging area for backends and also > new features would be acceptable for the LLVM project. What actions > are required to make the staging area a reality? Is more discussion > needed? Is anyone willing to

Hi there, I made up a very simple and generic rpm .spec.in. It's .in, so autoconf can replace the VERSION in it, so there's only one place to maintain the version number. This .spec.in is independent of any distribution and does not include any "advanced" features. It just packages the installed files up. There are two things that it does do extra: 1) create

Hi, I would like to follow up on the recent discussion on the mailing list about requirements for new backends[1] by submitting the following proposal for a staging area for new LLVM backends. This proposal incorporates ideas from Owen, Chandler, and others who chimed in on the original thread, and I hope the LLVM developers will be able to come to a consensus on this proposal or a modified

On Jul 20, 2012, at 8:51 AM, Tom Stellard wrote: > The goals of the staging area will be: > 1. Facilitate communication between the LLVM project and backend > developers > 2. Ensure that new backends meet LLVM standards > 3. Give the backend more exposure to users and prospective developers FWIW, I really like this idea or concept, but we have to be careful for it to be done

On Fri, 20 Oct 2017, David Newall wrote: > WHAT CAN I DO TO HELP STEWARD THIS CHANGE INTO THE MASTER SOURCE? > What do I need to do? Stop yelling and go file a bug at https://bugzilla.mindrot.org/ As I mentioned previously, your suggested change is wrong and we'd (at least) need to replace fd 1 with /dev/null prior to assigning it to the channel. -d