similar to: FossCamp / UDS feedback and 2.4 roadmap update

Dear NUT users and developers, A bit later than usual, here is the traditional end of the year mail to sum up the past year, think about the future and make some announcements. Those of you who have followed closely the project already know: 2008 has been a harder year than ever. And the UPS world has somehow finished a full revamp cycle, started 2 years ago! * A new sponsor: Last year,

On Sun, Nov 16, 2008 at 11:08 AM, Arnaud Quette <aquette.dev at gmail.com> wrote: >>> The remainder, until the -pre stage, will be: >>> - the Powerman support (through the powerman driver) for more PDUs >>> - the possible RRD integration into upslog >> >> It would be nice to have native RRD support in upslog, but we may also >> want to point

fellows, You can now commit to the trunk everything that is scheduled for 2.4 For my part, the november month will be mostly dedicated to the following: - commit the USB "improved maintenance" code. I'm about to finish that one, which allows to extract USB info and generate the various USB related files (hotplug, udev and hal). so the end of that bothering era ^_^ - complete &

Hi all, I just wanted to let you know that Jon Ludlam and I will be hosting a workshop on Project Kronos [1] tomorrow at the Ubuntu Developer Summit (UDS) for Ubuntu 12.04. We''ll be discussing the status of the project, and the work remaining for us to get Kronos included in Ubuntu. You can join in the workshop remotely. There will be a live audio stream [2], an IRC channel on

Hi all, I just wanted to let you know that Jon Ludlam and I will be hosting a workshop on Project Kronos [1] tomorrow at the Ubuntu Developer Summit (UDS) for Ubuntu 12.04. We''ll be discussing the status of the project, and the work remaining for us to get Kronos included in Ubuntu. You can join in the workshop remotely. There will be a live audio stream [2], an IRC channel on

I've noticed that some systems don't have redhat-lsb or even redhat-lsb-core installed and as a side effect, the ocsinventory agent reports them as 'linux' instead of Centos with the release version. Also, where it is installed and ocsinventory does pick up the name, it doesn't include Centos (pre-7.x) in the 'all Linux' grouping because the name is just CentOS and

Hi Ocsinventory http://www.ocsinventory-ng.org/ might be considered if not then I could also recommend Spacewalk http://www.redhat.com/spacewalk/? for something like this both runs well on Centos Per E-mail: per at norhex.com [1] http://www.linkedin.com/in/perqvindesland [2] --- Original message follows --- SUBJECT:?[CentOS] Tracking updates FROM: ?Martin Spinassi TO:?"CentOS mailing

Hi Attila, first of all, you should prefer posting support request on the NUT user mailing list (cc'ed) after having subscribed here: http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser 2010/6/23 Attila wrote: > *Dear Arnaud Quette,* > > * > * > > I'm currently working with an IBM UPS should be connected to my Linux Debian system. > > I've read that

Hi Powermen ;-) I recently came across the Powerman project (http://sourceforge.net/projects/powerman/), pointed by Tony Merenda, from Opengear (thanks Tony). Congrats for your work in this area! I've thought a bit about Powerman and NUT since then... NUT currently supports hosts of UPSs and few PDUs (RPCs), and provides tons of features: http://test.networkupstools.org

Hello, I have bought Powerman Optima 500 Plus UPS. While this product might be unknown outside Russia, it is shipped with megatec software and obviously works with megatec driver in NUT. besides the following problems (I think they are caused by one reason): 1) megatac driver is able to load and detect UPS only on second or third run. On the first run it typically fails. Later if daemon is

Hi Alexander, > I've UPS named PowerMan RealSmart 1000, it is not listed in > compatibility list. I found that it works with "fentonups" driver and > have ups.model "Unknown S163-1000". Ithink "1000" is from capacity - > I've seen in Internet someone have RealSmart 800 identified "S163-800". > Also PowerMan have

Hi, I get a trouble using nut with PowerMan Back Pro N 1400 Plus ~# /lib/nut/megatec -DDDDD -a pman Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) send_to_all: SETINFO driver.parameter.port "/dev/ttyS0" debug level is '5' DTR=1, RTS=0 Starting UPS detection process... Asking for UPS information [I]... I => OK [# PCSTAR-PRO V1.02-2411] I VALUES => [

Hi, folks! Which driver should be used for PowerMan 2000 Real Smart? Backpro 1000 Plus is successfully monitored by genericups/upstype=4, but this's not working for RealSmart2000. Somebody wrote in blogs at http://k001.livejournal.com/270848.html that RealSmart can be monitored using "fentonups" driver but this is false on my box. WBR, Ilya

Greetings, I have helped host a few applications such as GLPI, OCSInventory, etc etc. using the tarball method and untarring them in /var/www/htom directory. I have never done them though using yum. I was trying to install Trac, Bugzilla etc using yum install method on a Centos 6.2 box. Somehow I am not able to see the respective pages say even using http://localhost/trac or

I've recently been working a bit on adding PDU (http://en.wikipedia.org/wiki/Power_distribution_unit) support in NUT. Some of you might have seen the Powerman thread, which also deals with adding more PDUs support: http://powerman.sourceforge.net/supported.html The result is that we now have support for 2 Eaton | Powerware ePDUs (Managed and Monitored iirc, check http://www.epdu.com). I plan

Hi, I need help because I can't install Nut in RedHat EL 6.6 The version of Nut in repository ot RHEL is 2.6.5-2, but doesn't suppor my UPS, Liebert GXT3-200RT. I read that it is supported using Nut version 2.7.2, but I looking all around the web how to install it in my RedHat but I didn't find answers. Follow the guide, I can downlad lasted version stable on web: 2.7.2 Here the

2008/12/19 Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Fri Dec 19 09:34:11 2008 > New Revision: 1656 > > Log: > Some more header file changes > > Removed: > trunk/drivers/powerman-pdu.h the same can be applied to many driver's headers since this goes back to pre autoconf/automake full support. so I created quite a

Built for years every version using: ./configure --with-usb Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes build Powerman PDU client driver: no build IPMI driver: no enable SSL development code: yes enable libwrap (tcp-wrappers) support: yes build CGI programs: no enable HAL support: no

Rainer, Arjen I was wandering around the code, and found that few things are missing around the IVT code: - no manpage, - no entry in driver.list - no device{mfr,model,type} in the code. I was about to submit a patch to address the above (ready to commit), but wanted first to get an update on the status. looking at the last thread, it's a bit unclear... I'm also interested an upsc

Dear NUT developers and contributors, time has come to shed more light on 2.8.0 roadmap! Ubuntu Developer Summit attendance has helped to clarify things. several of 2.8.0 tasks are detailed here: https://wiki.ubuntu.com/ServerOneiricInfraPower I'm conscious that our development infrastructure (Alioth) is not that suitable to track roadmaps, "Agile" specs and developments, as we do