similar to: Seagate announces enterprise SSD

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hello! We have two upses: MGE Pulsar M 3000 and MGE Pulsar EXtreme 3200C. They connect to server by USB. EXtreme works good with usbhid-ups (nut 2.2.1) and newhidups (nut 2.0.5). But Pulsar M doesn't want to work with usbhid-ups. - my ups.conf: [extreme] driver = usbhid-ups port = auto product = "EXtreme" [pulsar] driver = usbhid-ups port =

On 26/04/16 10:07 PM, John R Pierce wrote: > On 4/26/2016 6:45 PM, Jack Bailey wrote: >> >> Today someone in a meeting claimed the Bourne shell is deprecated, one >> of the reasons being it supposedly has security issues. Well that's >> all news to me, and I cannot find anything online to corroborate the >> claim. Is this true, is it a bash vs. Bourne FUD, or

Hi all, Not sure if this is on topic or not. I'm trying to query an SNMP value from centos 6 and I get a bad response if I don't specify the MIB to use: 0 digimer at pulsar:~/anvil/striker$ snmpget -v2c -c public -m /home/digimer/Downloads/APC/AP7900/MIB/powernet421.mib 10.255.2.1 .1.3.6.1.2.1.2.2.1.6.2 RFC1213-MIB::ifPhysAddress.2 = Hex-STRING: 00 C0 B7 5F 8A 85 0 digimer at

Hi everybody, I installed and configured Nut 2.4.3 on Debian Squeeze, using package. It monitors an MGE Pulsar 1500 UPS in standalone mode. Here are parts of upsmon.conf : SHUTDOWNCMD "/bin/bash /root/extinction.sh >> /var/log/ups/ups.log 2>>&1" NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh" [...] NOTIFYFLAG ONBATT SYSLOG+EXEC At startup, driver, upsd and upsmon

Dear Sirs, I have an old but very well-working UPS MGE Pulsar ESV8+ Rack. I'd like to use it to power FreeBSD 9.0-Rel server. Of fortunately I have problem with recommended driver - mge-utalk, nut 2.6.4 (installed from FreeBSD Ports). I get messages: Could not get multiplier table: using raw readings. and updateinfo: Cannot update system status I saw similar thread on mailing list with no

With the Dell OpenManage question on my mind (and having seen it answered very well), I was reminded of an interesting and a little surprising thing I saw yesterday. I upgraded a PowerEdge 2850 from CentOS4 to Fedora Core 5 (keeping everything updated for GNUradio to run on CentOS 4 became more of a job that it should have) for our pulsar data processing machine (it has a GNUradio Universal

Hello, I'm trying to communicate with a MGE Pulsar STS 16 using nut under Linux, but I've had no luck so far. I haven't saw it supported in the doc, so if there's anything I can try... Thanks, Arnaud. -- Perso: http://launay.org/blog/ H?bergement: http://www.nocworld.com/

(Sorry, I accidentally discarded the wrong message in the moderation queue - please subscribe to the list to avoid this in the future.) > From: <onyx at netfusion.fr> > Subject: [HCL] MGE Pulsar Evolution 1100 - not recognized by USB driver > Date: December 22, 2011 12:15:16 AM EST > To: <nut-upsuser at lists.alioth.debian.org> > > > Hi everybody, > > It

I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working with an MGE Pulsar Evolution 500, but I cannot get the USB interface to work. When I plug in the USB cable I get the following message in my system log: kernel: usbhid: probe of 2-1:1.0 failed with error -5 Any ideas? Thanks Mike

Buenas, Estoy creando un paquete y me gustaría crear un acceso directo en el escritorio que al pulsar sobre el, abra R, cargue el paquete [ library(mipaquete) ] y ejecute la funcion inicio() ¿Es posible hacerlo? Gracias [[alternative HTML version deleted]]

Hi, I've been using NUT for many years to look after the UPS on my home servers. Originally I was using a Compaq R3000 but that was replaced with an MGE Pulsar Evolution 3000 about a couple of years ago because the Compaq one was just too noisy! I'm just setting up a replacement server and would like to connect it using a serial cable as I've found that the USB connection

Hello, My MGE Pulsar Evolution 800 had some hardware troubles (it may be the batteries according to the manual). The fault was not detected so the power was cut to the load and nothing appears in the log files. Arnaud: do you know if the UPS have some way to report this kind of troubles to the PC so that NUT can handle it with a shutdown sequence ? Philippe

Hi all ! I have communication issues between my station and my old Pulsar EX10 UPS, (U-Talk) connected by RS232, when using v2.4.1 of nut-server. I tried to come back to version 2.2.2 and then, communication start and is operational. Maybe it's linked to bug 498655, but i haven't seen any answer ? http://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg566711.html Here are

Using hccm() I got a heteroscedasticity correction factor on the diagonal of the return matrix, but I don't know how to incorporate this into my linear model: METHOD 1: > OLS1 <- lm(formula=uer92~uer+low2+mlo+spec+degree+hit) Coefficients: Estimate Std. Error t value Pr(>|t|) (Intercept) -0.0623377 0.0323461 -1.927 0.057217 . uer 0.2274742 0.0758720

I suspect that the battery is failing on my Pulsar Evolution 500 (it is several years old now) but I can't seem to get a valid battery voltage from the UPS. The following tests were done using NUT 2.2.1, but I first noticed this with the trunk, and reproduced it with the current branches/Testing as well. The only two values I have seen for battery.voltage are 120.0 and 119.0, e.g.: $ upsc

hello, I installed with NUT UPS MGE Pulsar Evolution 2200 all orders of arrest, interrogation etc etc ... UPS work well However, I have a problem with the order in NOTIFYCMD upsmon.conf that not run ... I created a script that generates a simply log I indicated in upsmon.conf NOTIFYCMD / home / nut / alert_ups.sh below my upsmon.conf RUN_AS_USER nut MONITOR pulsar at localhost 1 admin1

Hello, I forgot nut since more than a year because a lot of job with other application My server nut failed since severals months We had 3 electric failure so I must install a new server nut I work with ubuntu 10.04.4 (64bits) / I installed nut 2.4.3 with deposits I have a MGE Pulsar evolution 2200 connected on usb last week when I began my tests all was ok (communication etc etc ..)

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with nut-2.0.1 (the standard "sarge" packages). I have it connected through USB, and I'm using newhidups. However, about once a day the driver looses contact with the UPS and I have to restart NUT to get it to drop the "data stale" nonsense (it happens more often than this, but most times it recovers without