upscmd doesn't
actually wait for the command to be executed.
--
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
haven't personally tried their recent hardware, but at the moment, this seems
like the most promising avenue for vendor support.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
:
battery.charge: 0.00
battery.current: 0.00
battery.runtime: 0.00
battery.voltage: 2.10
input.current: 0.00
Is this just due to low load? (9%, later in the output)
The battery voltage looks very low.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev
.
--
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
for some time, this might still work:
http://trac.networkupstools.org/projects/nut/wiki/NutOnMacOSX
Let us know if you have any questions.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
, and
observe the voltage while under load. This unit might not be capable of doing
that.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut
to see what IRQs it assigns to each
port. I don't know whether OpenBSD requires interrupts, but I know that a lot
of modern OSes tend not to poll the serial port registers.
A Linux live CD might help if you don't want to permanently install it.
--
Charles Lepple
clepple@gmail
:
http://article.gmane.org/gmane.comp.monitoring.nut.devel/6679
We're going to need some help either way.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
running in a desktop session?
--
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
specialized tools - for instance, valgrind deals with
memory allocation errors, and gdb can be useful when tracking down crashes. But
for protocol-level debugging, upsdebugx() is the way to go.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing
On May 2, 2014, at 3:26 AM, Kastus Shchuka wrote:
Hi,
I am trying to set up NUT on a mini-ITX system running OpenBSD 5.5.
I have an APC Smart-UPS SC620 which runs perfectly well on Ubuntu,
with nut-2.2.1. Ubuntu system uses ASUS motherboard.
On mini-ITX system, I have Intel d2500cc
or send a command, the user/password you are using needs to
have permissions to do so. In the upsd.users man page, the first example,
[admin], shows how to allow pretty much everything.
If that doesn't work, please post upsd.users with the passwords removed.
--
Charles Lepple
clepple@gmail
/gmane.comp.monitoring.nut.devel/6558
--
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 ioctls are crucial to set or clear serial control lines.
On 04/04/2014 14:39, Charles Lepple wrote:
Thanks for submitting this - it seems useful. However, the blazer
driver will eventually be replaced by nutdrv_qx. Rather than add this
code to individual drivers, what if it went
specific advice will probably depend on the version of NUT, and the
version of the firmware on the SNMP card. Also, are you using upssched or
something similar to shut down the file server first?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing
.) If not, there is a chance that the mappings from NUT
variable names to HID identifiers are incorrect.
--
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 Apr 5, 2014, at 8:52 AM, Mick michaelkintz...@gmail.com wrote:
The upsrw command was designed for changing variables that are typically
stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't
seem to do that.
Well, if it doesn't do that, how come upsc reports the
On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote:
On Apr 5, 2014, at 8:52 AM, Mick michaelkintz...@gmail.com wrote:
The upsrw command was designed for changing variables that are typically
stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't
seem to do that.
Well
On Apr 4, 2014, at 8:56 AM, Bill S kenwood0...@gmail.com wrote:
It would appear that there is nothing that can be done to correct the
output voltage reading.
Nothing easy, but the AC output voltage is reported by the UPS. It requires
more than just a five-minute fix, though.
The DC battery
to completely power down the UPS, and pull it from the wall long enough to
let some of the power supply capacitors drain.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org
notifier: /usr/local/etc/rc.d/nut: WARNING: failed
precmd routine for nut
Apr 3 09:05:36 archivio notifier: nut_upsmon not running? (check
/var/db/nut/upsmon.pid).
2014-04-03 2:15 GMT+02:00 Charles Lepple clep...@gmail.com:
On Apr 2, 2014, at 9:52 AM, Daniele Borghesi wrote:
Hello, I
.
--
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
: you're using an APC9630 card with which
version of NUT, which firmware version on the card, and which version of
net-snmp?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
can install the sysutils/usbutils port, and run lsusb (also as root) to
be able to directly compare the output to a Linux system.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
to be reloaded, or if the images need a no-cache header in their HTTP
headers.
I tend to use collectd to monitor NUT statistics over time:
https://collectd.org/wiki/index.php/Plugin:NUT
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
or the UPS HID descriptor.
--
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
-standard, so maybe this
would tell us something about this case, too.)
It might be helpful to test with a variac, and ramp the voltage up and down to
see which bits change as the UPS goes from battery to boost to passthrough.
--
Charles Lepple
clepple@gmail
the affected models.
I was hoping we'd get a reply or two from other CyberPower users.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
--
Charles Lepple
clepple@gmail
. If you are computing values in a microcontroller anyway, I agree, it just
adds confusion.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
in the
latter case, I would recommend firewall rules as an additional line of defense.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut
for the NAS to monitor).
--
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 Mar 17, 2014, at 7:16 PM, Andreas Perhab wrote:
finally tested the shutdown and it worked beautifully
Committed, thanks!
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http
).
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
lsusb outputs from UPSes are not HID PDC.)
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
, but I think NUT will still poll the interrupt
pipe if present. The requests over EP0 are probably only made if there are HID
usage paths mapped to NUT variable names.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev
if the USB cable is pulled.
--
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 Mar 8, 2014, at 9:07 AM, Josu Lazkano wrote:
Which is the frequency of the poll?
Once every 2 seconds, typically. See pollinterval in man ups.conf.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
to be
worried about?
Ideally the UPS wouldn't do that, but if it reconnects...
--
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
Elio, please see below as well.
On Feb 22, 2014, at 5:11 PM, Roberto Resoli wrote:
On 22 febbraio 2014 17:28:16 CET, Roberto Resoli robe...@resolutions.it
wrote:
Hello,
after some days running without problems, my riello idialog 800 ups
get disconnected, and usbfs started flooding syslog
, it can do so
simply with a Report ID and the described data.
That's it.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
0x1c at the beginning of the
buffer) is 48/8 = 6 bytes in, for a value of 77 00 (0x0077 since USB is
little-endian), or 119.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http
in?
--
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
.)
--
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
is left over from another 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
not work
as expected, without fixing the above discrepancies first? Right?
I wasn't very clear there: .1.3.6.1.4.1.318.1.1.1.6.2.1.0 *does* currently map
to shutdown.stayoff.
(We should probably fix the other OID to map to shutdown.return, if that is
indeed what it does.)
--
Charles Lepple
clepple
if you unplug and re-plug the USB cable?
--
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 Feb 27, 2014, at 8:16 AM, Josu Lazkano wrote:
I will ask in the OpenWRT forum.
Please let us know what you find out.
Regards,
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
with .1.3.6.1.4.1.318.1.1.1.6.1.1.0
(upsBasicControlConserveBattery), which is currently mapped to shutdown.return
# turn off UP gracefully (APC) (stays off even if power is restored)
#UPS_OID=.1.3.6.1.4.1.318.1.1.1.6.2.1.0 integer 3
This should map to the shutdown.stayoff instant command.
--
Charles Lepple
clepple
recommend trippups1, as that seems to be one
of the more common names for that MIB.
--
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 Feb 20, 2014, at 12:54 PM, Ted Mittelstaedt wrote:
On 2/20/2014 6:55 AM, Charles Lepple wrote:
On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote:
Worse, however, is if there's a power failure right near the end of
the 2-days-off cycle. That happened to me last week - it was a
short
chip). You can give that driver a try as well.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
):
http://www.networkupstools.org/stable-hcl.html
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
On Feb 18, 2014, at 10:15 PM, Charles Lepple wrote:
On Feb 18, 2014, at 5:55 PM, Thiago Tiedtke dos Reis wrote:
Hi,
Recently I got three units of this nobreak [0]:
...
[0] http://www.sms.com.br/produtos/Nobreak-SMS/Manager-III-Senoidal
According to the HCL, for the Manager III, you
./configure make to build it:
You shouldn't need to run autoreconf when building from a .tar.gz file.
What if you re-extract it, and just run ./configure make?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
:-)
update: I see you're working on that:
https://github.com/networkupstools/nut/issues/93
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut
UPS is the size of the battery
string and maybe the power electronics module.
--
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
values with
snmpget, all others returned correct values as listed above.)
The upsSmartControl* OIDs are probably write-only (although the MIB indicates
you should be able to read them back).
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing
On Feb 14, 2014, at 9:26 AM, Charles Lepple wrote:
On Feb 13, 2014, at 10:49 PM, Иши Кылса wrote:
Slightly changed the list, took from running snmptranslate for all
parameters:
snmptranslate -IR -On upsBaseIdentModel upsBaseBatteryStatus
upsSmartBatteryCapacity
-- Forwarded message --
From: Tim Dawson tadaw...@tpcsvc.com
Date: Thu, Feb 13, 2014 at 12:07 AM
Subject: Re: [Nut-upsuser] Powerware (Eaton) Prestige 9 UPS
To: Charles Lepple clep...@gmail.com
Charles -
As a quick followup, the Prestige (both FW 2.13 and 3.09 - 2.x is
pre-Eaton
of the material in this e-mail is
strictly forbidden.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
--
Charles Lepple
clepple@gmail
', but it can muffle the sound...
^ Love 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
* copy netcard.mib-mib.c and netcard.mib-mib.h to ../drivers/
* autoreconf configure make from the top level directory
Does it mean it is ok?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
-Original Message-
From: Charles Lepple clep...@gmail.com
To: Muley mu...@mtida.net
Subject: Re: [Nut-upsuser] compatable driver
Date: Fri, 7 Feb 2014 21:25:52 -0500
On Feb 7, 2014, at 12:57 PM, Muley wrote:
This TrippLite device (09ae:3016) is not (or perhaps not yet) supported
.
I did see a report of someone successfully using blazer_usb (with the cypress
subdriver, but a different UPS vendor) on FreeNAS, so that is some hope.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
: offline / line interactive
ups.vendorid: 0665
Gabor,
which version of FreeBSD is this running on? (Or which version of FreeNAS, and
we can look up the FreeBSD version.) We're seeing a failure of this same
driver/subdriver on different hardware, but on FreeBSD 9.1.
Thanks,
--
Charles Lepple
is to ask the FreeNAS folks if they can delay the start of NUT
until the network is completely configured. If you go that route, let us know
what bug or ticket number gets assigned to that.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing
to something post-2.7.1 from Git.
Please run this:
/usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D
and send the output back to the list.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http
this has been seen before, with no apparent resolution at the time:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2012-December/008164.html
Can you try it with - to see if the error is on the send side?
Also, any output from dmesg related to ugen?
--
Charles Lepple
clepple
will see numbers there,
corresponding to the default format string:
http://www.networkupstools.org/docs/man/upslog.html
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org
there who can test this for me?
Thanks,
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
It looks like some of the TS Shara code has been integrated on Dan's branch:
https://github.com/zykh/nut/compare/networkupstools:master...ts-shara-fix
After you get a chance to test the updated nutdrv_qx driver, the other thing we
should add is a Hardware Compatibility List (HCL) entry. This
?
and they are using a USB cable/port.
see below.
Thx for any leads.
Chris
On 1/31/14, 6:17 PM, Charles Lepple wrote:
On Jan 31, 2014, at 3:14 PM, Chris Duffy wrote:
The current one I am looking is support for:
Upsonic Commercial UPS CXR 2000 - 2000VA/1200W - Rack/Tower
What
sosabra...@gmail.com
2014/1/29 rodo...@tsshara.com.br:
De: Charles Lepple clep...@gmail.com
Em: Quarta 29 de Janeiro de 2014 11:46,
Para: rodo...@tsshara.com.br
Assunto: Re: NUT and UPS TS Shara
Hi Rodolfo,
[please reply to nut-upsdev@lists.alioth.debian.org, not nut-upsdev-owner
to make a change to devd.conf.
What does 'usbconfig list' return when run as root?
Or, if the UPS connects over a serial port, what options are being used, and
what is the resulting message when starting the driver (e.g. with 'upsdrvctl
start')?
--
Charles Lepple
clepple@gmail
to the modified source code
http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic
--
Charles Lepple
clepple@gmail
/*
* blazer_usb.c: support for Megatec/Q1 USB protocol based UPSes
*
* A document describing the protocol implemented by this driver can be
* found online at http
to decide when to shut down.
--
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 Jan 16, 2014, at 11:20 PM, Charles Lepple wrote:
On Jan 16, 2014, at 12:36 PM, Daniel Macks wrote:
On Thu, 16 Jan 2014 07:04:56 -0800, Alexander Hansen
alexanderk.han...@gmail.com wrote:
Another option would be to recompress it and have the new tarball uploaded
to Fink's repository
On Jan 19, 2014, at 11:39 AM, Daniel Macks wrote:
On Sun, 19 Jan 2014 10:39:56 -0500, Charles Lepple clep...@gmail.com wrote:
The cgi-formbuilder-pm.info file passes validation, but if any Perl experts
want to glance at it (I'm used to packaging Python and C stuff), it's in a
temporary
On Jan 19, 2014, at 3:27 PM, Daniel Macks wrote:
Also, just noticed, missing a dependency on perl itself.
Should that be perl%type_pkg[perl]-core, since it is varianted?
--
Charles Lepple
clepple@gmail
: selfupdate-cvs Thu Jan 16 08:54:42 2014, 10.7, x86_64
Trees: local/main stable/main
--
Charles Lepple
clepple@gmail
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses
the tar header keyword extensions inside the gzip payload that are
tripping up the integrated tar+gz auto-detector in GNU tar.
--
Charles Lepple
clepple@gmail
--
CenturyLink Cloud: The Leader in Enterprise Cloud
On Jan 15, 2014, at 10:18 AM, Emilien KIA wrote:
2014/1/15 Charles Lepple clep...@gmail.com:
Emilien,
just saw your commit in Buildbot for testing some Windows changes. That's
great that someone is working on this again!
We have had a few users ask for updates to the 2.6.5+ version of NUT
On Jan 2, 2014, at 7:06 PM, Daniel Johnson wrote:
On Jan 2, 2014, at 8:37 AM, Charles Lepple clep...@gmail.com wrote:
Hi all,
I am looking at packaging ikiwiki, which depends on a bunch of Perl modules.
I am generally familiar with the Fink variants capabilities, but I am
curious
On Jan 10, 2014, at 4:46 PM, Ariel Wainer wrote:
On 10/01/14 01:53, Charles Lepple wrote:
I am curious about why the Interrupt Out packet is sent by the Windows
software if it isn't to turn off the UPS. Is it possible to do some more
testing with shorter timeouts so that the battery doesn't
in ups.conf?
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
On Jan 1, 2014, at 3:50 PM, Ariel Wainer wrote:
On 01/01/14 17:33, Charles Lepple wrote:
Disappointing. I will add a note in the man page for that, too. (Maybe
it is only after the UPS is in the low battery state? You mentioned
that it did shut down when you did the capture with the Windows
request versus control request.
[*] well, someone else confirmed:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2013-January/008195.html
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
?
Lovely. We must have introduced an error somewhere in autoconf. What does the
./configure... line say in the beginning of config.log? (If you don't have
config.log handy, what parameters is your packaging system using?)
--
Charles Lepple
clepple@gmail
On Dec 16, 2013, at 5:52 PM, David C. Rankin wrote:
On 12/16/2013 09:06 AM, Charles Lepple wrote:
If you want, we can take a look at the output of the aforementioned udevd
command from your system. Please compress the output, and if the list bounces
it, I'll extract the relevant portion from
know there is a bit of CPAN magic for installing Perl packages outside
of Fink. Is there any way to leverage that dependency information for building
a Fink package description?
Thanks, and Happy New Year,
--
Charles Lepple
clepple@gmail
between when the
command is sent, and when the UPS actually turns off the load.
--
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 Jan 1, 2014, at 2:58 PM, Ariel Wainer wrote:
On 01/01/14 16:12, Charles Lepple wrote:
In your testing, do you have suggestions on better debug levels? We should
probably log the status changes at level 2 or less, since the hex dump is
only useful for those who know the protocol. Also
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
discuss these subjects.
BR, and Happy New Year!
*Leon Vak*
Control Management Manager
http://www.gamatronic.com/
Thanks again to Leon for reaching out, and Ted for explaining how things work
here.
--
Charles Lepple
clepple@gmail
another thing we need to
add to the list of areas that need better debug messages.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
. 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
On Dec 15, 2013, at 2:03 PM, David C. Rankin wrote:
On 12/14/2013 09:04 PM, Charles Lepple wrote:
Is there someway nut can be modified to probe the 0664 permission usb
devices
and then connect as root before dropping permissions back to the nut
gid?
Given that the udev method should still
USB device, but simpler hand-written rules often suffice.
If anyone has suggestions on udev debugging techniques (besides sprinkling the
source code with log statements, which I would rather not do on a production
system), I'm listening.
--
Charles Lepple
clepple@gmail
1001 - 1100 of 3311 matches
Mail list logo
