similar to: Thank you - newhidups (2.03-pre2) works with my APC BackUPS ES 500

Almost worked first time (Solaris 2.7, gcc-2.95.2). Well done. perl -i -p -e 's/-m644/-m 644/' Makefile.in Also, it would be nice to be able to set up LFLAGS somehow, to provide the following: LFLAGS=-R/usr/local/lib YMMV with the path. That way the executables will run without setting LD_LIBRARY_PATH. I can't see where to tweak this in the configure setup at the moment - I'll

Hi there, [ http://www.contribs.org/bugzilla/show_bug.cgi?id=654 ] I just received this: Broadcast message from nut (Sat Feb 4 04:02:45 2006): UPS UPS@localhost battery is low and Feb 4 04:02:45 bigted upsmon[11532]: UPS UPS@localhost battery is low Feb 4 04:02:45 bigted wall[4032]: wall: user nut broadcasted 1 lines (34 chars) but I believe this looks o.k., except for the input voltage

As I read the manpage, you need to enable Subsystems to have the server support them. [...] Subsystem Configures an external subsystem (e.g., file transfer daemon). Arguments should be a subsystem name and a command to execute up? on subsystem request. The command sftp-server(8) implements the ``sftp'' file transfer

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

Well, after our first real extended power outage, I found out that even though the UPS 1000 RM is recognized okay, it does not work properly. It never seems to see any change in UPS status. It looks very similar to the other issue I reported with the APC CyberFort 350. I never was able to get to the bottom of the CyberFort issue, but I'll bet it's the same issue as we have with the

Does anyone on this list have a CyberFort 350? It's a European model, and should be equivalent to the US BackUPS ES 350 model. What I'm seeing is upsd reporting stale data. While the battery is running down, upsc doesn't see the battery % changing, so I'm assuming the driver isn't collecting data at that point. Unfortunately, the system/UPS is not here (I'm in the

PasswordAuthentication seems to be accepted regardless when DSA authentication is not available. Client and server are Linux - openssh-2.5.2p2-1.7.2 Server config is: Port 22 ListenAddress 0.0.0.0 HostKey /etc/ssh/ssh_host_key HostKey /etc/ssh/ssh_host_dsa_key KeyRegenerationInterval 3600 LoginGraceTime 600 ServerKeyBits 768 IgnoreRhosts yes PasswordAuthentication no

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre18. This is mainly merges from the OpenBSD tree, bugfixes for Solaris and libc5 Linux systems. It should fix all reported bugs except the snprintf problems on some older Solaris versions. Please test thoroughly, my hope is to have a stable version released before Jan 1. At this point the main holdup is Solaris. I have

Hi there, I'm trying to track down a problem with said combination. Broadcast message from nut (Thu Jan 26 13:22:06 2006): Communications with UPS UPS@localhost lost Broadcast message from nut (Thu Jan 26 13:22:11 2006): UPS UPS@localhost is unavailable "newhidups -DDD hiddev0" seems happy enough, as does "upsd -DDD -f" - at least until I start upsmon. Then I

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

I am a complete linux noob and I've downloaded and extracted wine and winetools... but when I got to the install application on wine and try to open it, nothing happens. Could someone help me install wine?

Hey all, I have recorded my steps towards getting puppet functional through one of the four different methods that I can think of, which are: 1.Source(copying and insatlling to the recommended unix FSH directory, /usr/local/src) 2.pkg hosted at explanatorygap 3.MacPorts 4.RubyGems I haven''t cleanly tested the last two, but here''s where I am with the first two: 1. I

Installed a 30 day trial of Adobe Acrobat 7.0 and I'm now trying to "properly" uninstall. I run "uninstaller" and the program shows up in the list of installed programs. In Uninstaller: click on the program description to highlight it and then clicking the Uninstall tab causes the hard drive to wobble about a bit, the program becomes un-highlighted and the uninstaller

In the light of the rather serious MEMDISK bug in 2.03, I would like to promote 2.04-pre2 to 2.04 some time this evening, California time. Please try it out -- especially PXELINUX and MEMDISK -- if you have the opportunity. Thanks! -hpa

Hi everybody, If we let the feature running, it appears that the driver gets unbound after a while ( variable from quarter of hour to 6 hours ) and cannot reconnect. This behavior appear with both MGE Ellipse ASR and non-ASR models with connection to an UHCI and OHCI controllers. The USB core is from 2.4.28 kernel. We use nut-2.0.3. Start, powerfail and recovery detections, UPS shutdown work

I decided to upgrade from openSuse 10.2 to openSuse 10.3. I installed xen things, but when I boot using xen option the system is blocked. It appears the green window, with little suse logo in the middle, and mouse cursor, but the system crashes. My computer is a Pentium 4 1,5 GHz, 512 MB of RAM. I attached "diff boot.msg boot.omsg" (as diff opensuse-normal-kernel opensuse-xen-kernel)

Help or suggestions please: When using smbclient to handle printing from a AIX system to a windows print queue somethings work and others do not. I have been able to print without issues to the windows print queue. But I cannot get a listing of the print jobs in a print queue. This is important so the UNIX users can take action on thier print jobs. I'm not sure which why to turn at this

It seems that 2.03-pre1 resolves PXELINUX problem on a reasonable number of hosts. Perhaps somewhat importantly this seems to include the RBFG PXE boot floppy, which did not work with 2.02. This was somewhat of a surprise, since it didn't exhibit the failure mode that I would have thought would have been the trigger of the bug. Instead, it was one of those stacks that would transmit packets

Hi all, I have just released SYSLINUX 2.03-pre4; this is the same as SYSLINUX 2.03-pre3, except: a) I have -- I hope -- finally fixed the Perl scripts so they work in UTF-8 locales; b) MEMDISK now supports gzip compressed images. For those who have requested it... you should really thank me for the last one. It took quite a bit of work, mostly because I had to move the installer to be a

Hi all, Since it seems 2.03-pre3 solves some significant problems for people, I'm going to release it as 2.03 some time later in the week. I would *greatly* appreciate people testing it before then. Thanks, -hpa