something like upsd (or
something similar, like apcupsd's NIS master mode), or the NVR has to send the
shutdown signal to the Raspberry Pi.
http://www.networkupstools.org/docs/user-manual.chunked/ar01s03.html#_advanced_configuration
--
Charles Lepple
clepple@gmail
would be a lot
simpler, IMHO.
--
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
, since you
want the RPi to talk to the UPS). There are many USB adapter cables out there
that will only work for supplying power, or only with point-to-point USB OTG.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
, but it might work for supplying 5VDC.
Thanks a lot for advice.
Da: Charles Lepple [mailto:clep...@gmail.com]
Inviato: martedì 20 gennaio 2015 14:23
A: Maurizio Iacaruso
Cc: NUT List
Oggetto: Re: [Nut-upsuser] R: NUT and relay on USB
On Jan 20, 2015, at 7:43 AM, Maurizio Iacaruso
often the UPS
updates the runtime estimate - it might be dropping below 90 (or whatever the
internal threshold is for RemainingTimeLimit) for short intervals.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
powering a critical
system). I need to do some testing with another UPS, so maybe after that, I can
swap this one in and see what happens.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
On Jan 10, 2015, at 11:07 AM, Steve Ballantyne steve.ballant...@gmail.com
wrote:
On Thu, Jan 8, 2015 at 11:37 PM, Charles Lepple clep...@gmail.com wrote:
Although this tends to happen more with x86 systems and/or USB3, you might
want to see if the disconnects are less frequent with a shorter
log. STATUS(TIMELIMITEXP) maps to ...RemainingTimeLimitExpired, which I don't
see, and STATUS(SHUTDOWNIMM) would cause an ups.alarm message to show up in
upsc.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
can do to fix that other than to just ignore it.
Although this tends to happen more with x86 systems and/or USB3, you might want
to see if the disconnects are less frequent with a shorter or higher-quality
USB cable.
--
Charles Lepple
clepple@gmail
in advance
DGC
--
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
disconnect signal, so
there is no getting around this plus accompanying the data stale message.
However, for the notifications, you could use upssched to only notify you if
the UPS is disconnected for longer than the usual reconnection time.
--
Charles Lepple
clepple@gmail
, Mike Raath raa...@gmail.com wrote:
Ok - before stale data:
After stale data:
$ lsusb -d 0665:
Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
After stale data:
And the gzipped log attached:
On 2 January 2015 at 21:56, Charles Lepple clep...@gmail.com wrote
in the USB cable (or run udevadm trigger --
subsystem-match=usb), subsequent driver runs should find the USB device.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi
/nutdrv_qx.log'
(Please gzip nutdrv_qx.log before sending it, thanks.)
--
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
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-upsuser
from Dan (hyouko@gmail) regarding the start
character.
--
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, 2015, at 8:23 PM, Charles Lepple clep...@gmail.com wrote:
On Jan 1, 2015, at 4:57 PM, Jonathan Gammell jon.gamm...@utoronto.ca wrote:
[ups]
driver = dummy-ups
port = eaton1
desc = Dummy UPS
There is a typo in the specification of port = in the dummy-ups man
for a simulation file named
'eaton1'. The presence of an @ character enables repeater mode. If you change
this to 'port = eaton1@localhost', things should work as you described.
The lack of syslog messages is indeed a bug.
--
Charles Lepple
clepple@gmail
On Dec 29, 2014, at 6:38 PM, Janez Kremzer janez...@gmail.com wrote:
Charels get me e hint about comment out root user and add $ sudo adduser nut
dialout.
In Ярослав's case (FreeBSD), the group would be uucp (and I don't think the
adduser command supports this syntax).
--
Charles Lepple
to be RemainingCapacity. You
can verify this by forcing the UPS onto battery power until the front panel
displays a charge lower than 100%.
I do not see any items which are likely to be runtime.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
[please use the nut-upsuser@ address rather than nut-upsuser-owner@ and be sure
to use Reply-All - thanks!]
On Dec 23, 2014, at 1:52 PM, Janez Kremzer janez...@gmail.com wrote:
Hi!
I woud like to use Raspberry Pi with NUT installed whic coud shut down NAS in
the office.
NAS doesn't have
._USB-Serial_Controller-if00-port0 - ../../ttyUSB0
Although it is unwieldy, the pathnames under /dev/serial/by-id should always
point to the correct /dev/ttyUSB? node.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
by the debug output (case-insensitive) rather than a numerical match,
so it should be -x vendorid=0463.
I did not see a potential match for battery.charge in the non-explore output,
but can you try again with the fixed vendorid and -DDD?
--
Charles Lepple
clepple@gmail
discharge until the low battery threshold is
reached (or the test is stopped).
In practice, the difference is determined by the UPS firmware.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
60 seconds, then please gzip the log before sending it to
the list.
Thanks,
--
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
send a copy of the output of 'upsc',
'upscmd -l' and 'upsrw' for your UPS. (If you prefer to mask out part or all of
the serial number, that is fine.) Let us know if any of the returned values are
known to be incorrect for your setup.
--
Charles Lepple
clepple@gmail
://apcupsd.cvs.sourceforge.net/viewvc/apcupsd/apcupsd/ReleaseNotes?pathrev=Release-3_14_11
and if you need connectivity with an existing NUT setup:
http://www.networkupstools.org/docs/man/apcupsd-ups.html
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing
-root.php?message_id=E4AF6D2D%2d44B0%2d4371%2d988B%2d72A1A3CE49EC%40gmail.com
--
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
conditions.
--
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
On Dec 4, 2014, at 7:01 AM, j...@telefonica.net wrote:
I have got this output with driver usbhid-ups
ups.conf
[Phoenixtec]
driver = usbhid-ups
vendorid = 06da
productid = 0002
port = auto
#~ langid_fix=0x0409
Oh, sorry - I meant for you to try that with blazer_usb.
--
Charles
:
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#hid-subdrivers
The driver keeps looping and reading the values, and you can see whether they
correspond to various power states (on battery vs on AC, low battery, etc.)
--
Charles Lepple
clepple@gmail
On Dec 3, 2014, at 2:02 PM, j...@telefonica.net wrote:
USB error: error sending control message: Invalid or incomplete
multibyte or wide character
This is a wild guess, but what about using the option langid_fix=0x0409?
--
Charles Lepple
clepple@gmail
to
those values, the UPS will shut off its output 30 seconds after the shutdown
signal (so you need to make sure that your OS shutdown takes less time than
that).
Does upsrw -l advice show anything?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser
-to-serial
adapters.
The most likely driver is blazer_usb (or nutdrv_qx, which is newer). You may
need to shut down the UPS completely (turn power off, and unplug) if the other
drivers have sent commands that put the UPS into a bad state.
--
Charles Lepple
clepple@gmail
On Dec 1, 2014, at 9:19 AM, Victor Porton por...@narod.ru wrote:
01.12.2014, 14:50, Charles Lepple clep...@gmail.com:
Does upsrw -l advice show anything?
$ upsrw -l advice
upsrw: invalid option -- 'l'
I suppose I should read the documentation every once in a while :-)
upsrw advice
I
is included in the startup shell script, which is
case-sensitive.)
Here is the original nut.conf with its comments:
https://github.com/networkupstools/nut/blob/587d5f828c03d961f0cbeb11c6a19a7944ec6ccd/conf/nut.conf.sample
--
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
:
https://dl.fedoraproject.org/pub/epel/7/SRPMS/n/
install to /usr/src (or something) and rebuild with a NUT snapshot:
http://buildbot.networkupstools.org/snapshots
If you have questions, let us know - I'm sure there are other users of
RPM-based distributions on the list.
--
Charles Lepple
clepple
=3016' option.
The suggestion in the error message applies, although you may need to either
run the driver as root, or add an entry for this UPS in the udev files (exact
details will depend on your Linux variant).
--
Charles Lepple
clepple@gmail
://bugs.debian.org .
--
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
/mailing.html
The bottom line is that we are happy to try and work with you to debug this,
but so far there are more questions than answers in this particular problem
space.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
driver does recommend a higher value of
pollinterval, but that is a special case (it is essentially USB over a serial
cable, and the baud rate is not high enough for the defaults) and wouldn't
apply to your UPS.
--
Charles Lepple
clepple@gmail
problem.
2) I would recommend changing back to a pollinterval of 2, and if that is
causing other problems, we should take a closer look at that.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
else can offer help
if needed. If nothing else, we do have source code :-)
The soft shutdown/WOL part seems possible.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi
On Nov 12, 2014, at 6:32 PM, Klint Gore kgo...@une.edu.au wrote:
-Original Message-
From: Charles Lepple [mailto:clep...@gmail.com]
Sent: Thursday, 13 November 2014 12:12 AM
I am surprised that the blazer_usb configuration didn't work. If you leave
off
the matching options
the LIBUSB_DEBUG environment variable.
libusb 1.0.19, lubusb-compat 0.1.5, nut 2.7.2
At the moment, we don't have a lot of experience with libusb1 and
libusb-compat. When it works, it's just like libusb-0.1, but if not...
For the permissions issue, is your nut user a member of the nut group?
--
Charles
of the
protocol between the vendor software and 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-upsuser
(to avoid running down the batteries too much). Note
that this will shut down the master system, too. Details are in the upsmon man
page.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
/drivers/mge-hid.c#L201
Arnaud or Emilien,
Is there any way we could get the HID dump from a few of the other Powerware
models to extend the following table?
https://github.com/networkupstools/nut/blob/master/drivers/mge-hid.c#L82
--
Charles Lepple
clepple@gmail
this the right way:
https://github.com/networkupstools/nut/issues/170
--
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 Nov 9, 2014, at 8:13 AM, Marcelo Fernandez
marcelo.fidel.fernan...@gmail.com wrote:
2014-11-09 9:59 GMT-03:00 Charles Lepple clep...@gmail.com:
Strange, I would have thought that the Value: 0 would show the actual
number. Does it look like drivers/libhid.o got rebuilt?
Yes, at first
). Please gzip
the log before attaching it and sending back to the list.
--
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 netstat output I mentioned in a previous
email?
--
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
[Please use reply-all to keep the discussion on the list, thanks]
On Nov 6, 2014, at 10:19 PM, Charles Lepple clep...@gmail.com wrote:
On Nov 6, 2014, at 12:48 PM, Steve Read sd_r...@hotmail.com wrote:
I am presently upgrading my servers. The old ones are running Suse 10.1 and
I am
as the slave.
--
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 Nov 7, 2014, at 7:30 AM, Marcelo Fernandez
marcelo.fidel.fernan...@gmail.com wrote:
2014-11-07 0:16 GMT-03:00 Charles Lepple clep...@gmail.com:
On Nov 6, 2014, at 5:56 PM, Marcelo Fernandez
marcelo.fidel.fernan...@gmail.com wrote:
battery.voltage: 1000.
battery.voltage.nominal
, let it run for a minute, then gzip and attach the resulting
log?
--
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 author of the driver - maybe the manufacturer can
provide more information?
Same thing with the configuration variables. There are a few non-standard HID
usage IDs at the end of the log, but it is not clear how to make use of them.
--
Charles Lepple
clepple@gmail
, maybe those aren't the /dev node names that it is using. Can please you
send the output of:
strace -o nutdrv_atcl_usb.strace /lib/nut/nutdrv_atcl_usb -a name -DD
Also, if you run 'ldd /lib/nut/nutdrv_atcl_usb', is it linking against
'libusb-0.1.so.4' or libusb-compat?
--
Charles Lepple
ioctl(4, USBDEVFS_SUBMITURB, 0xbff9a580) = 0
ioctl(4, USBDEVFS_REAPURBNDELAY, 0xbff9a564) = -1 EAGAIN (Resource temporarily
unavailable)
select(5, NULL, [4], NULL, {0, 1000}) = 0 (Timeout)
On 6 November 2014 00:22, Charles Lepple clep...@gmail.com wrote:
On Nov 5, 2014, at 1:36 AM, jani
be able to run
lsof -n as root, and grep for usb or hid.
--
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 reference, here's the thread discussing the development of that driver:
http://news.gmane.org/find-root.php?message_id=52B4C54E.1050106%40ariwainer.com.ar
It seems to have worked under Kubuntu 13.10.___
Nut-upsuser mailing list
security mechanisms like SELinux or
AppArmor, etc.)
Also, what happens if you add -u root to the driver command line? (The 'chmod
777' should have been sufficient...)
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
On Nov 1, 2014, at 1:30 AM, jani wrote:
Hi Charles,
I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId of
0001. It seems to be a re-badged unit manufactured by Guangdong East Power
company, and besides the little brand stamp it looks identical to:
at a higher priority.
___
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
soon for the next NUT release. It will
look like this:
http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/
Out of curiosity, what tools do you use to build the VIB file?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
On Oct 10, 2014, at 6:44 AM, paul.chav...@fnac.net wrote:
Please find attached the patches i have applied to the current master.
Merged to master, as of commit f5462ebb. Thanks again!
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
=0008
If you configure using --with-user=nut, it will match the Ubuntu package, and
you can simplify the configuration:
[liebert]
driver=usbhid-ups
port = auto # (can be any string; driver matches based on USB VID:PID)
No productid is needed with the merged code.
--
Charles
, it's not 100% clear
if they are using DTE or DCE terms, but that's a simple swap). I'm also curious
as to whether the modem control lines are wired up in the stock cable.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
/Directory
I'm still looking at the other asciidoc email.
--
Charles Lepple
clepple@gmail
for something specific with grep.
I'm not saying don't bother to rebuild the documentation, but it is one of
the dependencies that is unintentionally optimized for developers who need to
make changes to the documentation, and see how the changes render.
--
Charles Lepple
clepple@gmail
, and trying to kill that
process. The default PID file locations for Ubuntu and the NUT source install
don't match.
I should probably add a FAQ entry about using killall or pkill if there are
multiple drivers running.
--
Charles Lepple
clepple@gmail
in the collectd version that is in 10.04. Something to consider if
you are looking for more than just an instantaneous readout:
http://packages.ubuntu.com/lucid/collectd
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
?
,;;:;,
;
,:;;:;,'=.
;:;:;' .= ,'_\
':;:;,/ ,__:=@
';;:; =./)_
`=\_ )_`
``'`
Excellent idea :-)
--
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
___
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
and NUT version, but if you have a valid battery charge level, you can
use the ignorelb setting to synthesize a low battery notification.
--
Charles Lepple
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most
errors in configurations such as this.
If you had subnets that segregate the A and B groups, you might be able to do
something with mDNS to find the nearest NUT master, but I don't know if I would
depend on that unless servers move around frequently.
--
Charles Lepple
clepple@gmail
8.04 LTS
version.
A quick check shows that your UPS's ID was added in 2006 (NUT v2.0.3 and later)
so your version should be new enough.
--
Charles Lepple
http://ghz.cc/charles/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
On Oct 14, 2014, at 9:07 AM, Gene Heskett ghesk...@wdtv.com wrote:
On Tuesday 14 October 2014 08:19:02 Charles Lepple did opine
And Gene did reply:
usbhid-ups
I apologize, I should have just mentioned the whole ups.conf:
[myups]
driver = usbhid-ups
port = auto
The usbhid-ups
, but with modern servers, the stack of
driver/upsd/upsmon is fairly lightweight compared to the rest of what is
usually running on each server.
Does this help? I feel like I am missing a critical detail about how you want
to integrate the two server groups.
--
Charles Lepple
clepple@gmail
the portion after
lib and before the first dot:
./configure --with-snmp --with-wrap --with-snmp-libs=-L/opt/csw/lib -lnetsnmp
If that doesn't work, can you gzip and send config.log?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
=pentium_pro not recognized
gcc: error: language chip=pentium_pro not recognized
--
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
.
If you get a similar error with the SPARC machine, you may want to see if you
can get NUT to use the Sun compiler instead. (This is probably faster than
rebuilding Net-SNMP with GCC.)
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut
documentation:
http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/
--
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 Oct 2, 2014, at 1:53 AM, Tarvo Tiits tarvo.ti...@automaatika.ee wrote:
On 02.10.2014 03:42, Charles Lepple wrote:
On Oct 1, 2014, at 5:07 AM, tarvo.ti...@automaatika.ee wrote:
Why is ups.status empty?
If I understand the commit log for SVN r3590, then that revision was
supposed to set
.
Regards.
Paul.
--
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
/networkupstools/nut/commit/9cb2de3d9568aa382cc118b4385d97d5664c457b
Is your UPS set to ECO mode? Can you do a snmpget on
.1.3.6.1.4.1.4555.1.1.1.1.4.1.0?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
Source for that page is:
https://github.com/networkupstools/nut/blob/master/data/driver.list.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
at the same code as what is built on your system. Do
you have the exact version for the RPM files, or better yet, the corresponding
SRPMs?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
-get build-dep nut should work, then you can
skip to the git clone step.
--
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 26, 2014, at 8:31 AM, Dave Williams d...@opensourcesolutions.co.uk
wrote:
On 08:09, Fri 26 Sep 14, Charles Lepple wrote:
Well, I ended up linking to the latest version of those files, so this shows
the change better:
https://github.com/networkupstools/nut/commit
to rebuild the driver, let me know - even though yours seems to be
from NUT 2.6.4, I doubt there will be any issues with building the 2.7.2+ Git
version and dropping it in.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
for users to apply,
or is there another patch needed to deconflict ugen and upd?
--
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
) as
well as the corresponding /var/log/messages output.
--
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
.
http://news.gmane.org/find-root.php?message_id=B8D50FAB7FEF06479924547835C34D448412AEF6%40CHI%2dVS%2dEXMBX11.tripplite.com
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org
On Sep 22, 2014, at 12:37 PM, Adam Pribyl pri...@lowlevel.cz wrote:
I am experiencing the same kind of disconnects, stale data on Eaton brand UPS
(Nova AVR). It keeps doing it probably due to Windows to detect it as a new
hardware, until Eaton software is installed. With Eaton Linux IPP
. But
it only shows up in the Fedora output, and its messages seem closer to when the
device is attached, rather than when it disconnects. I'm not sure if Fedora or
CentOS have server builds, but I would recommend starting from the minimum
software necessary and building up.
--
Charles Lepple
clepple
On Sep 18, 2014, at 10:09 PM, Stan Gammons sg063...@gmail.com wrote:
On 09/17/14 22:31, Charles Lepple wrote:
Can you rebuild the libusb1 pkg as a port, with the DEBUG flag turned on?
Is --enable-debug the way one turns it on? I modified the Makefile as shown
below, then did a make
401 - 500 of 1342 matches
Mail list logo
