no longer implements PPPS. Only the old silver
version does. What is the point of a model# if you can't count on the
functionality?
--
Stuart D. Gathman
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft spons
On Mon, 2 Jun 2014, elliot smith wrote:
Hello,
I want to propose a universal UPS driver that will work with any and all
UPSes out there. That driver is called: PING :-)
It works like this... the user plugs their router into a power source
OTHER than the UPS. Instead of talking to the UPS, N
On Mon, 2 Jun 2014, Ted Mittelstaedt wrote:
Incidentally, there are many other schemes that can be used to get
power state into a PC. Here are some:
So maybe the dummy driver can be configured with a script to poll
power state (or a callback to get power state events). That would be much
sa
On Jan 9, Jim Klimov transmitted in part:
On 2013-01-09 18:53, Kiss Gabor (Bitman) wrote:
For some time I've been meaning to dig into the problem, and found
that I need a tool to emulate poweroffs for a testbed (VM likely).
What better tool would it be than a fake UPS driver that reports
to NUT
I am running nut in Fedora 17 (previously 16). There is a bug in
startup that I think I understand well enough to explain. The symptom
is that upsd refuses to start at boot time, complaining:
Oct 12 22:28:22 melissa upsdrvctl[868]: Network UPS Tools - UPS driver
controller 2.6.5
Oct 12 22:28:
On Jul 3, Arnaud Quette transmitted in part:
I just found a bug in systemd scripts.
nut-driver.service.in and nutshutdown.in contains
@SBINDIR@/upsdrvctl
but it should be
@driverexecdir@/upsdrvctl
thanks for your report, fixed in commit r3668:
http://trac.networ
On Jun 7, Seth Galitzer transmitted in part:
upsrw reports ups.id is a string, which could be useful if I could match
against it, but if I read your statement correctly, I cannot.
Matching on USB bus number would not be optimal, since this changes even when
a device is unplugged and replugged
Applied this to nut-2.6.3 on fedora, and bestfortress seems to still
work. The patch seems reasonable as well. As to why it isn't needed
for me, I suspect it has to do with serial IO buffering. Driver was
depending on upsflushin() to empty the input buffer before triggering
another status update
Long ago, Nostradamus foresaw that on Apr 11, Michal Hlavinka would write:
This is no longer true for Fedora. Since Fedora 17, there is no /bin nor
/sbin now. Everything got moved to /usr/(s)bin. They are symlinks to /usr...
for now.
In the /sbin world, I have been creating custom nut package
r even the developers?
I have the docs at the office somewhere - I'll dig them up. It is
interesting to see the attention given to a model with 2 known users :-)
Old things are inherently interesting.
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-09
r situation.)
While in one sense, your problem is much more serious than mine,
in another sense, it is much better being highly repeatable!
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus ad
no handshake. The record length is 80 bytes. The UPS does not
send the 80 byte record until you ask it to. So you just need a buffer with 81
bytes for the data. The COM/serial driver is returning too soon, and doesn't
have a big enough buffer.
--
Stuart D. Gathman
B
Long ago, Nostradamus foresaw that on 01/27/2012 07:05 PM, Oliver Kluge
would write:
>
> root@FSC:/home/okluge/devel/trunk# ./autogen.sh
> Regenerating Augeas ups.conf lens...
> Regenerating the USB helper files...
> Calling autoreconf...
> ./autogen.sh: 35: autoreconf: not found
You also need to i
the necessary giant log, but it will take a while.
It used to happen more often (several times a day) at the customer site
where this UPS was previously installed (and replaced with a modern
USB based model). So I suspect that the corruption is caused by
interference on the serial cable.
--
Long ago, Nostradamus foresaw that on 01/24/2012 03:25 AM, Arnaud Quette
would write:
Use the following procedure to do so:
$ svn co svn://anonscm.debian.org/nut/trunk
$ cd trunk
$ ./autogen.sh
$ ./configure --sysconfdir=/etc/nut --with-statepath=/var/run/nut
--with-altpidpath=/var/run/nut --wit
and
messages contains:
Jan 21 12:53:30 melissa systemd[1]: Service nut-driver.service is not
needed anymore. Stopping.
this looks exactly as a symptom of the bug I mentioned in last email
I agree, and will report back when the promised systemd update makes it
to the repo.
--
St
Long ago, Nostradamus foresaw that on 01/19/2012 07:35 AM, Michal
Hlavinka would write:
>>> Yes, on Fedora 16, you have to start nut-server before nut-monitor, and
>>> systemd tries to start them at once. Haven't got around to
>>> reporting that.
>>> I don't think this problem is fortress specific
ere
N should likely be 1) without reporting stale.
I've just committed a patch to trunk (r3400) to get more visibility on
the received data, and impact on ignoring checksum.
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
&
uses. I generally adjust upsmon.conf to compensate. If I'm not
the only fortress user left, I'll have to see if I can tweak the driver.
Perhaps it should leave status unchanged after a single corrupt
record from the UPS instead of reporting a problem.
--
Stuart D. Gathm
Long ago, Nostradamus foresaw that on 12/24/2011 01:53 PM, Charles
Lepple would write:
> Before you do that... the scaling that we're talking about is usually
> evident from the voltage readings. Most of the errors are misplaced
> decimal points, but in this case, some UPSes read high by a factor o
cross the battery terminals? (Is
that safe with a cheap voltmeter?)
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do
Long ago, Nostradamus foresaw that on 12/21/2011 10:45 PM, Charles
Lepple would write:
> lsusb -vvv -d 0764:0501
Bus 002 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDevice
Long ago, Nostradamus foresaw that on 12/21/2011 09:08 PM, Charles
Lepple would write:
> On Dec 21, 2011, at 8:40 PM, Cliff Wright wrote:
>
>> A little over a month ago I acquired a CyberPower CP825AVR-G
>> ups. I found the usb was reporting the same vendor id (0x0501)
> (side note: 0x0501 is the p
.
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from he
On 10/14/2011 06:10 PM, Regid Ichira wrote:
> The if() statement always evaluated to true.
>> Detected by "cppcheck", not tested on real hardware.
>>
>> - if( ( BattVoltage > 129 ) || ( BattVoltage < 144 ) )
>> + if( ( BattVoltage > 129 ) && ( BattVoltage < 144 ) )
> I think the curre
f the auton calculation is actually only
valid outside the range).
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Mi
be millisleep.
*/
}
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_
On 10/03/2011 01:02 PM, Regid Ichira wrote:
> - usleep(25);
> + struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
>
Would it be better to define a local version of usleep in terms of
nanosleep? I suspect the library version already does that, but if the
libra
want to send commands to the UPS, however.
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go fr
On Thu, 1 Sep 2011, Charles Lepple wrote:
On Sat, Aug 27, 2011 at 8:19 PM, Stuart D Gathman wrote:
The problem:
We maintain small servers in customer offices. Customers often get
confused when asked to plug the server into the UPS. Sometimes they
have multiple servers from different
The problem:
We maintain small servers in customer offices. Customers often get
confused when asked to plug the server into the UPS. Sometimes they
have multiple servers from different vendors, and multiple UPSs, and
plug our server into the wrong UPS. The end result is that the UPS
being monit
still up to a human).
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do yo
the
upscli_connect call to check if it really is a NUT server.
That is a very good idea. Use some other port scanning code to narrow down
ports to try instead of corrupting upscli_connect with complications not
needed for normal operation.
--
Stuart D. Gathman
Business Ma
On 06/28/2011 02:29 PM, Arjen de Korte wrote:
Citeren Frédéric Bohé :
I am currently working on the nut scanner. For detecting available upsd
on the network, I rely on upscli_connect. The problem with this function
is that it calls a blocking "connect" function.
The upscli_connnect() call sh
brary that handles such details - and pid files
are not necessary with more modern init systems such systemd. (Also,
AIX has its own service manager that uses unix sockets to signal
services. Portability requires an API.)
--
Stuart D. Gathman
Business Management Systems Inc. Phon
copied to a process when it is
created, and can only be changed by the process itself. So getenv()
in effect *is* the global var/struct you want. Is Windows different
in that regard?
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
l, given an authenticated server and secure connection, any security
problems with client password authentication also apply to the private key
needed for client cert authentication.
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
ules. In practice,
I find it simpler to do a chown in rc.local.
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sp
e in the mean time.
In recent desktop linux distros, HAL has its own USB ups driver that needs to
be disabled to use NUT. I wouldn't be surprised if Solaris had
something similar.
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6
bit of work on the upsd server.
If I understand the problem correctly, here is a possible solution: create
another daemon (mged) that connects to the high end UPS and in turn listens on
multiple sockets, one for each outlet. Each socket would simulate a simple
UPS. There would be a NUT driver for
Kiss Gabor (Bitman) wrote:
On Thu, 1 Oct 2009, Stuart D. Gathman wrote:
keep simulation parameters in a separate config file from driver parameters.
Meanwhile file docs/developers.txt writes (watch the third sentence):
| Note: this does not apply to drivers. Driver authors should use
would write the UPS simulator in python (or your favorite
dynamic script language), wrapping common nut code as needed to communicate
with upsd. Then you can easily add complex simulation behaviour in
a high level script language.
--
Stuart D. Gathman
Business Management Systems
h do
not correspond directly to any code, it is not so clear cut. For the special
case of nut drivers, however, I think having the man page info as inline
comments is helpful. The nut drivers are like OO subclasses, and the
driver specific manpage portions included are like the class description.
m in production (they are rugged, reliable, and the batteries
are still made).
--
Stuart D. Gathman
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Micros
Charles Lepple wrote:
On Aug 14, 2009, at 3:13 PM, Stuart D. Gathman wrote:
Best fortress support was understandably dropped, but we still use them,
and someone else may want the driver I ported to nut-2.0.
Thanks for re-submitting the bestfortress driver. What specific
version of NUT were
15. Baud
rate, etc, are configured on the terminal server in this case, and
set_set_speed is ignored. (In theory, it could log on to the terminal
server in admin mode and auto configure, but that would be highly device
dependent. Maybe doable with an expect script and admin port.)
--
46 matches
Mail list logo
