similar to: Re: nut 2.0.4 and APC Back-UPS Pro 1500

I've read that the sm.conf configuration option "ldap filter" is removed after 3.0.14. Why is that? For one of the networks we maintain it is a very crucial option. I could not found an explanation or work around. Met vriendelijke groet/Regards Prompt R.J. Baart Kerkstraat 173 5261CW Vught tel: +31 73 6567041 mailto:R.J.Baart@Prompt.NL

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB

Configuration: Samba 2.2.8a with openLDAP 2.1.30 on a SeSE 8.2. server When adding a user using a ldif file we give the user a given name, say Ruud Baart. The cn and uid are the same, say 21cs12345 (a studentnumber). After adding the user to LDAP the displayname is as expected: "Ruud Baart". However after smbpasswd -a 21cs12345 -s secret the displayname is "21cs12345".

Paolo, Try sudo /lib/nut/newhidups -DDD -u root -a SmartUps1500 newhidups would only run on my computer if I ran it using sudo and as root user. I know this indicates a problem with the USB permissions, but I could not, for the life of me, get the permissions to change when I plugged the UPS in. I know this isn't a true fix, but it worked for me. -- ~Brian Foster

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

Hi, Can't get newhidups (2.0.5) or usbhid-ups (SVN trunk) to work 2.0.5 hidups seems to work, but I was hoping for more information... like temperature, etc. Tried newhidups and usbhid-ups, but they don't seem to detect my UPS... should I switch back to serial? Will I get more information? (trying not to move back to apcupsd, since i have a mixed environment) Here is some debug

We upgraded from 2.2.3a to 2.2.4 on a SuSE 7.2 server. We compiled Samba just default. The new version seems to work ok with the exception of printer administration. Printer admins are not able to see the properties of the printers (right click on printer gives on error). Our workstations are W2k SP2. But users that are not printer admin are able to see the properties of a printer, but they

Our server is a SuSE Linux 7.2 with CVS samba 2.2 branche. Version number is 2.2.pre-4. We updated today. We have a problem with the default devmode in Windows 2000 (SP2) clients. We have uploaded the printerdrivers to the share print$. The Samba printeradministrator is able to change the printer capabilities as memory, trays, papersize. etc. Changes are global: when a user logs in, he sees

Hello Mr Baart, 2006/3/11, R.J. Baart <R.J.Baart@prompt.nl>: > We are a reseller of MGE. Just sold 2 MGE Evolution 1100 UPS and 4 MGW powerswitches. > thanks for your choice and support. > But I have a problem with a new MGE Evolution 1100 UPS. After adding user=root I was able > to start nut. But the monitor won't work. I guess a problem with autorization. However I

I have a new APC Back-UPS XS 1200. It is detected properly by the Linux kernel (2.6.16): # dmesg usb 5-3.4: new low speed USB device using ehci_hcd and address 9 usb 5-3.4: new device found, idVendor=051d, idProduct=0002 usb 5-3.4: new device strings: Mfr=3, Product=1, SerialNumber=2 usb 5-3.4: Product: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 usb 5-3.4: Manufacturer: American Power Conversion usb

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

'lo, UPS model: APC Back-UPS BR 800 (supplied by Dell) My USB connection: Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 # upsc desk@localhost|grep load ups.load: 0.0 This UPS has 2 pc's and some minor other gear connected, yet the load stays at 0.0 when checking with nut. driver.version: 2.0.5 driver.version.data: APC/CyberPower HID 0.9

I was testing out newhidups with an APC UPS, and I noticed that I needed '-x vendor=American.Power.*' instead of '-x vendor=APC.*' as indicated in the man page. Do other APC USB UPSes use 'APC' in the vendor string? Should we sidestep any such problems and just go with the hex vendor ID for APC examples? This was tested with a snapshot from the development branch, but the

Hi, I'm new to nut, just installed it. I configured it using the hidups driver to work with my APC BackUPS: # upsc apc350@localhost battery.charge: 100 battery.runtime: 885 battery.voltage: 13.5 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.delay.shutdown: -1 ups.delay.start: 0 ups.load: 660 ups.mfr: American Power Conversion ups.model: Back-UPS CS 350

I'm converting my NT 4.0 Print Servers to Samba Print Servers. Which printing system should I be using? LPR, LPRng or CUPS. I would love to have some feedback on the advantages and disadvantages or what the Samba Team recommends as a standard for working wih Samba. In case you need it, my system is SuSE 7 kernel 2.2.16 running under VM on s/390. Thanks, Josh Konkol, CNE MCSE Senior

Hi. I had a problem recently with %subj, and I've solved it. Sent a letter with solution to maintainers, but it seems like I've lost it somewhere. May be just simply forgot to write it.. But anyway. I've noticed that I'm not the only one who had it. So I post the workaround. The problem is similar to the one mentioned in letter with alike subject at Oct. 5. When the UPS

Folks, while I've got the above combination to compile and run under Solaris 10, it seems that there are still problems in the libusb/ugen driver stack from Sun and or the APC Smart UPS 1500, so things aren't actually working. It seems that the APC Smart UPS 1500RM doesn't return the HID descriptor length information in 0x21 as noted in a previous thread, but in my case, it also

Greetings: I've been following through the instructions on how to connect an APC BackUPS 650 ES to USB, and have it monitored with NUT... I know my system can SEE the UPS, as DMESG shows this: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-1 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver I can see

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

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT