is in the vendor-specific range, and the two Usage fields are just 8-byte
unstructured buffers (also with vendor-specific IDs).
It might be possible to tell usbhid-ups to match on the 0xFFA0 usage page, and
ignore all of the other HID PDC definitions. I'll poke around the code.
--
Charles
running as a nut server and have each of the VMs running a nut client
so they can shut themselves down gracefully in the event of a longer
power outage.
Makes sense. Depending on how long a shutdown/startup cycle takes, it could be
useful to suspend the VMs.
--
Charles Lepple
clepple@gmail
initiated
Is that expected?
Not sure. The quick test might be just verifying that the battery capacity
hasn't changed much. (I only have a small Back-UPS, which I don't think has two
test modes.)
Best,
Christian
Am 17.12.2013 03:55, schrieb Charles Lepple:
On Dec 8, 2013, at 10:41 PM
. You can probably do
the test.battery.start.quick test with the server still plugged into the UPS,
though.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
calibration command would be the best to try.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
of the status
flags.
Actually, splitting ups.status into an array of strings should probably be done
in UPS::Nut, but that module doesn't look like it has been updated in a while.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
/networkupstools/nut/issues/79
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
the various debug levels off the top of my head, but if you
want to manually start the driver with a few -D flags and log the resulting
output, we can see whether or not your UPS is sending the notifications the way
that the driver is expecting them.
--
Charles Lepple
clepple@gmail
information, but I don't think we need to break the existing
syntax to do that.
If anything, I would want finer-grained control over the syslog level for some
of these events.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
? (There are
a number of devices out there which use Cypress chips - maybe another package
changed the permissions as well.)
On Tue, Dec 3, 2013 at 1:54 PM, Charles Lepple clep...@gmail.com wrote:
On Dec 3, 2013, at 1:10 AM, Danijel Šili wrote:
On Tue, Dec 3, 2013 at 2:52 AM, Charles Lepple clep
udev file, those should
be equivalent.
What version of udev and the Linux kernel do you have on your system?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
reporting. I added an issue on
GitHub, but if you built from source, you can extend the upslogx() command line
to see why system() is failing.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
On Dec 1, 2013, at 8:19 AM, Roberto Martelli wrote:
My nut version is 2.7.1 (autocompiled)
Is it safe to assume you are using Linux (given the pm-hibernate command)? Are
there any access control systems such as SELinux or AppArmor that might be
interfering with the system() call?
--
Charles
seems like it should either fail due to more
restrictive default permissions, or it would work due to less-restrictive and
possibly less secure permissions.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
from the UPS, and that is probably what Gnome is using. But I
haven't really looked at Gnome power management in a while.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org
be a nut-usb
package or similar. You will probably have to remove nut-hal to install
nut-usb. The nut+upsd+upsmon solution is mutually exclusive with nut-hal, but
they use the same device-specific code, and it sounds like your device is
compatible.
--
Charles Lepple
clepple@gmail
on Debian, I would try 'sudo /lib/nut/blazer_usb -a salicru -DDD'
If that works, you can ^C that and run 'sudo /etc/init.d/nut-server start'.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
you be interested in helping out with this?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
. The
instructions I read said to set up that port in NUT configuration, but I
would rather not set that.
I forgot to mention: by default, NUT listens on localhost. If you are using
Linux, you could add a -m owner --uid-owner rule to iptables to only match
the UID for the NUT system user.
--
Charles
functionality.
What are you trying to optimize?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
component.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
, the developers of
NUT would not know if a new Eaton model would not work with NUT until someone
reports it to the mailing list, but that has not been an issue to date.)
Alf has already commented on the bcmxcp side.
--
Charles Lepple
clepple@gmail
___
Nut
:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-May/00.html
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
On Sep 12, 2013, at 7:47 PM, Derek Rachul drac...@gmail.com wrote:
I tried reversing the order of the definitions in the config file, and it
does seem to change the order in which they're loaded (at least according to
the system logs) however the error remains.
I don't have any experience
://www.networkupstools.org/docs/man/upsmon.html#_forced_shutdowns
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
minutes of power (plus a safety factor) are available.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
defined once a process daemonizes.
The wall output is optional, especially if you have your own NOTIFYCMD defined
in upsmon.conf.
http://www.networkupstools.org/docs/man/upsmon.conf.html
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing
processes is creating more problems that it solves. Right
now, we have four modes to cover three daemons, and this use case introduces a
fifth mode. I can't help but wonder if there is a better way to represent these
configurations.
--
Charles Lepple
clepple@gmail
a lot of
commonality in the protocols - so feel free to post updates as you go along.
There is a good chance that the protocol is similar to another driver, but that
driver may have failed to detect that protocol variant.
--
Charles Lepple
clepple@gmail
upsmon -c fsd, which triggers the entire shutdown sequence.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[forgot to include the list]
Begin forwarded message:
From: Charles Lepple clep...@gmail.com
Subject: Re: [Nut-upsuser] NUT under NAS4Free config issue
Date: August 26, 2013 9:03:35 AM EDT
To: Incze Andras andrisga...@gmail.com
On Aug 26, 2013, at 8:08 AM, Incze Andras wrote:
Here
files if needed.
On Thu, Aug 22, 2013 at 3:32 PM, Charles Lepple clep...@gmail.com wrote:
On Aug 22, 2013, at 5:15 AM, Incze Andras wrote:
Thanks, the strange is that I could set in this way the master user.
That is odd. The development version of NAS4Free seems to be regenerating the
entire
be read from the XML configuration file.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
have two or more SSH simultaneous sessions using
the same login and password.
Not sure about the second question.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
configuration databases that are outside the scope of NUT. (I assume this is to
make it easier to modify permissions from the web GUI.)
Let us know what you find out.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
disable CONFIG_USB_DEVICE_CLASS option and rebuild kernel.
Now i rebuilding kernel, and try again.
20.08.2013, в 6:21, Charles Lepple clep...@gmail.com написал(а):
On Aug 19, 2013, at 9:10 PM, Charles Lepple wrote:
On Aug 19, 2013, at 12:58 PM, Korviakov Andrey wrote:
I have Liebert GXT3
On Aug 18, 2013, at 8:59 AM, Charles Lepple wrote:
On Aug 18, 2013, at 12:14 AM, Lyndon Drake wrote:
I'm happy to test an updated build, but have no idea about how to go about
doing a build in the first place. Could someone help me in the process of
creating a snapshot build for FreeNAS
Checking device (09AE/3016) (/dev/usb//dev/ugen1.3)
Randy,
were you ever able to get this working?
One thing I didn't think of at the time is checking the permissions on
/dev/ugen*. The dev nodes should be writable by the uucp user (which is the
default system user for NUT on *BSD).
--
Charles
:
[liebert]
driver = liebert
port = /dev/ttyS0
I am confused. Are you using a serial cable with the liebert driver, or a USB
cable with the usbhid-ups driver?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
On Aug 19, 2013, at 9:10 PM, Charles Lepple wrote:
On Aug 19, 2013, at 12:58 PM, Korviakov Andrey wrote:
I have Liebert GXT3 UPS connected to CentOS Linux with kernel
2.6.32-131.0.15.el6.x86_64 and nut version 2.6.5-2.
lsusb: Bus 002 Device 003: ID 10af: Liebert Corp. UPS
times to test out similar in-place upgrades in Linux.)
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
to a non-volatile directory? We have the NUT tarball
generation part of our Buildbot setup working, so I suspect you will only need
a compiler and libusb devel files.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
is not available to see how it handles this.
Also, I am not at all familiar with the runtime calibration config variables.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org
, the UPS powers
off. When wall power returns the server restarts correctly.
I still haven't messed with systemd yet, so I am in over my head here. Is this
similar to what Kjell posted about? Or is it in addition to that?
http://www.kepstin.ca/blog/networkupstoolsnutandsystemd/
--
Charles
/gmane.comp.monitoring.nut.user/7420/focus=7422
A modified version of this patch has been incorporated into the
development version of NUT, which will become 2.7.1.
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
a package of the whole nut (binary, conf
etc...)
This is not guaranteed to work, but when the version numbers are close enough
(2.6.4, 2.6.5, 2.7.1/master), it usually does work. The network protocol is
more stable than the upsd/driver interface.
--
Charles Lepple
clepple@gmail
On Aug 1, 2013, at 8:15 AM, Charles Lepple wrote:
On Jul 29, 2013, at 7:12 AM, James HORLEY wrote:
There’s a software advised by the constructor that work on linux
(http://www.power-software-download.com/viewpower.html), unfortunately it’s
heavy (tomcat and java) and I don’t find
the distribution package.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
to see if this is going to work first?
Agreed, the first kill(pid, 0) is redundant in that case.
https://github.com/networkupstools/nut/blob/master/clients/upsmon.c#L1930
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
whether the kill() function call is expected to fail or not.
Patches welcome :-)
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
): No such file or directory
We need to determine whether upsd and the driver are using the same path for
the socket.
Is the driver still running when you get the no such file or directory
message? The socket should be in /var/state/ups.
--
Charles Lepple
clepple@gmail
On Jul 29, 2013, at 7:56 AM, Charles Lepple wrote:
On Jul 29, 2013, at 6:43 AM, Pavel Potcheptsov (EKTOS) wrote:
Hello list,
I have explored https://github.com/networkupstools/nut repository
and found that Riello UPS added into list of supported UPS.
But current package for most
need to re-run ./configure in the source tree with the driver,
using the arguments above. Then 'cd drivers; make clean; make riello_ser' and
install the new copy of the driver.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
check the generated man pages into the Git repository, so the easiest
way to get around this is probably to just install asciidoc.
At some point I will fix the Buildbot step which generates snapshot tarballs
with the generated man pages included.
--
Charles Lepple
clepple@gmail
might need some additional dependencies. I think it's
actually the a2x script in the asciidoc package:
http://www.methods.co.nz/asciidoc/a2x.1.html#X1
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
Nice, that MIB fills in a few details.
.1.3.6.1.4.1.232.165 is cpqPower.
.1.3.6.1.4.1.232.165.3 is cpqPower.ups.
On Jul 16, 2013, at 10:25 PM, Charles Lepple wrote:
Here's the first update of ups.status:
0.102449getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0)
0.102546
most of the units that Eaton's
selector would recommend.
You could also go with a Tripplite rack-mount UPS, but a lot of the low-end
ones use a proprietary protocol that seems to change between model years.
--
Charles Lepple
clepple@gmail
___
Nut
Here's the first update of ups.status:
0.102449 getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0)
0.102546 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.4.5.0
0.102646 nut_snmp_get(.1.3.6.1.4.1.232.165.3.4.5.0)
0.104539 SNMP UPS driver : entering su_status_set()
desktops or small servers? A whole machine room?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
source release out the door.)
Feel free to take this idea and run with it.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Windows branch maintainer has
been MIA for a bit. Maybe someone else with a similar system can offer some
more debugging suggestions.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
for
long-term monitoring.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Follow-up from Massimo:
Additional info:
I followed this and NUT should be configured:
http://forum.qnap.com/viewtopic.php?f=151t=47493#p213186
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
On Jun 21, 2013, at 9:39 AM, Reed Hedges wrote:
OK, I'll try none and see what happens.
Also, depending on what other tools are accessing the serial port, you may need
to add the nolock option to ups.conf.
--
Charles Lepple
clepple@gmail
#_monitoring_client
http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#UPS_shutdown
Please subscribe to continue this discussion:
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
--
Charles Lepple
OL = -RNG
LB = RNG
(The upstype setting is arbitrary in this case, as all of the settings get
overridden.)
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi
that they call upsdrvctl shutdown after the rest of the system processes have
shut down (including the NUT driver). That should avoid the device or resource
busy error - only one process can open the UPS USB device node at a time.
--
Charles Lepple
A: Because it messes up the order in which
with other ARM/Linux boards, and none of the
symptoms are the same as on x86 PCs.
Do you have a desktop or laptop Linux system where you can test this?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
, it might expect it to be in the same format.
On the other hand, there has been discussion in the past that it is not
possible to change this through the NUT interfaces, e.g.:
http://thread.gmane.org/gmane.comp.monitoring.nut.user/7786
--
Charles Lepple
clepple@gmail
:
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s09.html#_revision_history
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut
on the list might be able to help.
The separation between clients and server is to allow processes like upsmon and
the drivers to run as different users. There are also passwords in some of the
configuration files. Aside from that, what do you suggest that we combine?
--
Charles Lepple
clepple
with the inner workings of the SNMP driver.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
to follow along in the code. I
recommend saving the log to a file (via 'script' or 'tee') and compressing it
to keep the list post to a reasonable size.
I suspect that the type is coming from the SNMP MIB definition. Could you also
send the ups.conf file contents?
--
Charles Lepple
clepple@gmail
to compile NUT from source with the same options that
Debian uses, and just swap in the snmp-ups driver for testing.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
On May 15, 2013, at 10:15 AM, lutz.niede...@gmx.net wrote:
I will post the changed apc-mib.c here. Ok? Or shall I send it to someone
else?
This list is fine. Would you please post a unified diff (diff -u) instead of
the whole file?
Thanks,
--
Charles Lepple
clepple@gmail
the files up the same way between sub-packages. If you continue with
Debian packages, you probably need to grab both nut-client and nut-server:
http://packages.debian.org/wheezy/nut
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
or libusb-1.0 + libusb-0.1-compat)
We have a workaround committed in Git, but I would like to get to the root of
the problem.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
and feeding on the software side as the USB UPSes do. If
we ever inadvertently break support for one of the serial models, please let us
know.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
an up-to-date version of NUT. If
this does not fix the problem, try running the driver with the
'-x productid=2010' option.
This was fixed in the version just after 2.4.3 (2.6.0).
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
/ecaee22189ca4add854c7fc0d5aca1e4ee4bfe2d#drivers/powercom.c
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
are getting with blazer_usb don't follow the same pattern as
some of the other USB issues seen on older versions of FreeBSD, so debugging
that could take a while.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
[original message was too long; forwarding.]
From: Pladi Computers Ltd. pl...@lovechnet.com
Subject: Not receiving real data from a Eaton E series DX 1000H UPS
Date: April 23, 2013 8:46:06 AM EDT
To: Arnaud Quette aquette@gmail.com, nut-upsuser@lists.alioth.debian.org
It works with
a tool that was like a miniature lsusb: it would print some descriptor
information, but not much else. I don't know if many distributions packaged
that. If there is such a tool for 1.0, that would make a great test case to
confirm that the problem is in libusb-1.0.
--
Charles Lepple
clepple
On Apr 14, 2013, at 2:02 PM, Matus UHLAR - fantomas wrote:
here it is: http://test.fantomas.sk/nas_lsusb-vvv-d_0463
BTW, looks like that URL got truncated:
http://test.fantomas.sk/nas_lsusb-vvv-d_0463:
--
Charles Lepple
clepple@gmail
On Apr 6, 2013, at 10:08 AM, Matus UHLAR - fantomas wrote:
On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote:
libusb: 0.00 error [get_config_descriptor] short output read 0/8
On 05.04.13 20:39, Charles Lepple wrote:
Reading the config descriptor is a pretty basic operation
HID subdrivers use UPS.Output.Voltage as well. Assuming NUT
is parsing this value correctly, it should show up in the vendor software. Can
you try loading the software in a VM?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote:
libusb: 0.00 error [get_config_descriptor] short output read 0/8
Reading the config descriptor is a pretty basic operation. What does lsusb
-vvv -d 0463: return?
--
Charles Lepple
clepple@gmail
.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
-routing the USB cable
should help.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
}
ST_FLAG_IMMUTABLE means that the variable can't be changed later by the driver
or upsrw.
Unfortunately, I am not familiar with the rest of the driver - perhaps
someone else can comment on recommended values.
I also hope so :)
Remember to keep the list CC'd :-)
--
Charles Lepple
clepple@gmail
it sees
the LB signal. Do you have any documentation or manufacturer's software for the
UPS?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut
:
$ cd drivers; make snmp-ups
I need to finish the Buildbot code to upload the auto-generated tarball which
includes the output of asciidoc.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
at the
moment, but if you follow those directions and post results to the list (either
this one, or nut-upsdev), I'll see what I can do.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
experimentation was needed.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
-based rather than percentage-based,
but it should get the job done.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
, but
timing might be interesting.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
of the NUT source
code, which you can get from Github:
https://github.com/networkupstools/nut
Feel free to post any questions you encounter. Even if you just have a sysOID
for your UPS, we can compare it to the others in the tree, and see if it is
similar.
--
Charles Lepple
clepple@gmail
match this device.
What does 'ls -l /dev/bus/005/003' return? (adjust the 005/003 to match the
last part of the Checking device line for the UPS)
You can also see if '/lib/nut/blazer_usb -DDD -u root -a powerwalker1' works
temporarily.
--
Charles Lepple
clepple@gmail
that page, or clone via git. Let us know if you
need a snapshot which does not require autoconf and automake.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
reads normal when idle, but it dips
too low during a test.
ups.test.interval : 1209600
1209600 seconds = 14 days, so if it does it again in two weeks...
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
601 - 700 of 1342 matches
Mail list logo
