. If you can
get that set up, we could probably help backport the changes, but note that the
blazer* driver is no longer actively maintained (replaced by nutdrv_qx, which I
do not believe was ever ported to Windows).
--
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
: Look in the man page or call this driver
with -h for a list of valid variable names and flags.
Right, I mentioned it is a setting in upsmon.conf, which is separate from
ups.conf that the driver reads.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser
.
It is possible that packet loss is happening on the SNMPwebcard. Those sorts of
cards typically do not have fast CPUs. But the snmpwalk results should shed
some more light on this.
On Mar 30, 2015 8:30 PM, Charles Lepple clep...@gmail.com wrote:
On Mar 30, 2015, at 10:41 AM, Jason Gould jgo
NetSNMP retries, but SNMP is UDP-based.
You could also try running 'snmpwalk' by hand against the SNMPwebcard to see if
it experiences the same packet loss. If that doesn't work, I think you have a
case for Tripp Lite support.
--
Charles Lepple
clepple@gmail
this opportunity to point out in the snmp-ups man page that if there are
no shutdown.* commands listed in the upscmd output, there is a potential for a
race condition if the power comes back early.
Arnaud, as maintainer of snmp-ups, any thoughts here?
Thanks again,
--
Charles Lepple
clepple@gmail
for publishing such
information. All that with an impact on all the NUT driver, and a transition
period to address that cleanly.
I prefer this option, for what it's worth. Let's not make ups.status more
cluttered.
--
Charles Lepple
clepple@gmail
___
Nut
.
--
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 looks
for the ONBATT event (corresponds to OB for ups.status):
http://www.networkupstools.org/docs/man/upsmon.html
http://www.networkupstools.org/docs/man/upsmon.conf.html
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev
dropping root privileges, and it would be
nice if NUT could do something similar.
But it sounds complicated (I briefly looked at the osdir mailing list thread),
and with keys stored in memory either way, you might as well initialize after
forking.
--
Charles Lepple
clepple@gmail
?) might
be the right way to go.
There is a maximum packet size in the lsusb output, but I wouldn't expect an
EPIPE error if that did not match. Still something to try, though - EP0 is a
little different than the other endpoints.
--
- Charles Lepple
http://ghz.cc/charles
that a human could power the UPS back on. Nearly all of the UPSes I
have worked on have momentary power buttons (either toggle on/off, or a pair of
on and off buttons).
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev
.
It's a little closer to what some PC BIOSes default to, where they will stay
off when power comes back, if they were last commanded to turn off.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http
On Mar 23, 2015, at 7:57 PM, Eric Cobb eric_c...@tripplite.com wrote:Number 1 change - 2.7.2 no longer has the HAL scripts that 2.6.5 has. I am working on if HAL is actually required on CentOS6.6 with the 2.7.2 code or if they have another way around it. This is code diving which is taking some
'mc' before, but assuming it has a hex editor, you would just
search for the string 'FSD' (46 53 44) and replace it with 'OFF' (4F 46 46),
write the file, and start the driver. (You might need to stop the driver first.)
--
Charles Lepple
clepple@gmail
On Mar 22, 2015, at 1:48 PM, cinowell cinow...@gmail.com wrote:
ups.status: ALARM OL OFF
Great! This was so easy than I expected.
UPS back to life again.
Thank you.
You're welcome. hyouko's 'ignoresab' fix should also get rid of the ALARM
status.
--
Charles Lepple
clepple@gmail
power it back on.
I suspect a lot of people who want to maximize uptime would want the UPS to
wait a bit for the battery to charge (battery.charge.restart - Minimum
battery level for UPS restart after power-off) before powering the load back
on.
--
Charles Lepple
clepple@gmail
.
You're 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
On Mar 17, 2015, at 10:32 PM, Charles Lepple clep...@gmail.com wrote:
A bit of explanation on the debug output: the Report Descriptor: (739
bytes) hex dump is the HID representation of the individual reports
available. NUT parses that out, and iterates over all of the Usage IDs
(status
I will try anything!
Many thanks for your help.
Philip.
openups_drv_start_lineon.gzopenups_drv_start_onbatt.gz
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi
or wall outlet
3) Turn the UPS on
4) Kill the upsmon process (this will prevent automatic shutdown)
5) Plug the UPS USB cable back in
6) Turn the UPS off, and watch upsc ups.status
If the FSD indication disappears, then the bit is inverted, otherwise it
needs to be ignored.
--
Charles Lepple
On Mar 4, 2015, at 9:04 AM, Charles Lepple wrote:
We only have a few open items that I think should be resolved before
releasing 2.7.3. The list grew a bit in the past week, but we'll cover that
later. Here is the list:
* #93: Devices Dumps Library improvements
https://github.com
[attachments were 100kB; trimmed]
Begin forwarded message:
From: Jakub Scepka (private) jakub.sce...@gmail.com
Subject: Re: [Nut-upsuser] nutdrv_atcl_usb
Date: March 13, 2015 at 4:30:08 PM EDT
To: hyo...@gmail.com hyo...@gmail.com
Cc: nut-upsuser nut-upsuser@lists.alioth.debian.org
what CentOS does. Debian (wheezy; not
sure about jessie yet) and Ubuntu have a poweroff action in
/etc/init.d/nut-client.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
?
--
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 12, 2015, at 11:55 PM, Melkor Lord melkor.l...@gmail.com wrote:
On Mon, Mar 2, 2015 at 2:39 AM, Charles Lepple clep...@gmail.com wrote:
I thought start-stop-daemon was involved because it closes stdin/stdout file
descriptors after exec()'ing the daemon. I tried --no-close option
that the firmware supports, but you may not want to run
those on a production system. Let us know (this list or nut-upsdev) if you
would like more details on that.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
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
, but only
if you build it outside of the Git working directory.
--
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
-installed FreeBSD box, while building a new snapshot from
the git master branch required autoconf, automake, libtool, asciidoc, and its
host of dependencies.
If you do repackage 2.7.2, please add something to the version number (e.g.
2.7.2-RTD) to indicate that it is patched.
--
Charles Lepple
On Mar 9, 2015, at 9:55 AM, Rob Groner rgro...@rtd.com wrote:
Is there a specific file with the version number in it that I would modify,
or do you just mean the file names?
The canonical place is in configure.ac, and everything else gets regenerated if
you rerun autogren.sh
That script,
on the udev
files, means you might be better off starting from the latest Git version of
NUT, or at least including the following patch:
https://github.com/networkupstools/nut/commit/040c800efad46ead9670077c9764360802d7aaf5
Reference:
https://github.com/networkupstools/nut/issues/140
--
Charles
On Mar 9, 2015, at 11:28 AM, hyo...@gmail.com wrote:
2014-11-09 16:29 GMT+01:00 Charles Lepple clep...@gmail.com:
On Nov 8, 2014, at 7:01 PM, hyo...@gmail.com wrote:
Since this UPS seems to be supported by UPSmart2000I, it could use a
serial-over-usb implementation of the megatec protocol
: Charles Lepple [mailto:clep...@gmail.com]
Sent: Friday, March 06, 2015 6:17 PM
To: Eric Cobb
Cc: Nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Problems communicating with Tripp Lite
SMART500RT1U via USB with CentOS 6.6 and NUT 2.6.5
On Mar 6, 2015, at 12:51 PM, Eric Cobb
... approach), but I'm not going to make promises for the project based
on limited free time.
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut
On Tue, Feb 11, 2014 at 10:03 PM, Charles Lepple clep...@gmail.com wrote:
Please see below. I think I know what is going on (it seems to be a
make/gmake incompatibility), but to fix it, I need to rewrite some of the
HP-UX packaging code, and I need a HP-UX user to help test this. Otherwise
be able to publish the specs of
that protocol, would you? ;-) That would help remove the experimental driver
warning.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
if it works or not: quite a lot of testing may be 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
upsd in foreground). Documenting the handling of non-monotonic time as a known
bug (with a simple patch tested on Linux) is perhaps not equivalent, but given
the developer resource constraints we have had over the past year, I think it
is not out of the question.
--
Charles Lepple
clepple
://github.com/networkupstools/nut/issues/188 )
Glad to hear that Arno will have more time to work on NUT again!
--
Charles Lepple
clepple@gmail
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
, and the ./configure script converts Makefile.in
to the Makefile.
--
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
), and rebuild the RPMs themselves for testing. Granted, this may
not work if startup scripts or other internals change, but I think it would be
a step in the right direction. My information on SRPMS is somewhat dated - any
suggestions would be appreciated.
--
Charles Lepple
clepple@gmail
.
Not familiar with usbview. NUT has its own nut-scanner tool (not
included in Debian, AFAIR), but I don't know that we interface with
other driver scanning tools.
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
-FBohe.pdf
although it doesn't specify using debug mode, either.
Also, the Ubuntu test script does not pass -D to upsd:
http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-nut.py
I will try to test this on some other OSes.
- Charles Lepple
packages did not have them.
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
to pull all of the UPS status, but it should
then go into the background.
Maybe check syslog to see if there are any errors?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
mailing list posts, but the information is out there.
--
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 10, 2015, at 5:24 PM, Miroslav Todorov miro0...@yahoo.com wrote:
Hi Artronic art 1000 bl is supported partially by blazer_ser:
When you say partially supported, what is not supported? Are any of the
values incorrect?
--
Charles Lepple
clepple@gmail
On Feb 19, 2015, at 11:23 PM, Gene Heskett ghesk...@wdtv.com wrote:
Almost $800 dollars and worthless
on wheezy. I am asking a few ?? over that on their mailing list as it
worked perfectly on ubuntu-10.04.4 LTS.
If you still have a backup of /etc from the Ubuntu install, there might be some
On Feb 20, 2015, at 8:40 AM, Charles Lepple clep...@gmail.com wrote:
So let's do it the manual way. Brand name? Any vendor-included software that
is currently being used as a beverage coaster? USB or serial? If USB, what
does lsusb say about it? (Might have to run lsusb as root, if the udev
On Feb 20, 2015, at 3:15 PM, Rob Groner rgro...@rtd.com wrote:
Instead, it seems that the usbhid-ups driver will search through its own list
of known devices with vid/pid, and won't match my device unless that device
exists as an entry in its device table. Is that correct?
More or less,
On Feb 19, 2015, at 8:55 AM, Gene Heskett ghesk...@wdtv.com wrote:
On Wednesday, February 18, 2015 08:11:13 PM Charles Lepple wrote:
[...]
On recent Debian and Ubuntu with 2.7.2 and
earlier, there was an issue where the udev rules file needed to be
renamed from 62-nut* to 52-nut* in order
On Feb 19, 2015, at 8:43 AM, Rob Groner rgro...@rtd.com wrote:
I followed the log messages and found where it had created the udev rule...as
Charles said, in /lib/udev/rules.d. It is named 52-nut- and there is
nothing else that starts with 52 in /lib/udev/rules.d or /etc/udev/rules.d.
On Feb 19, 2015, at 8:43 AM, Rob Groner rgro...@rtd.com wrote:
I looked at the file and saw how it was laid out...basically an ATTR for
every known USB UPS. Well, since mine is not a known UPS, I had to add my
own entry.
If you want, once things are working, we can add an entry to that
On Feb 18, 2015, at 10:40 AM, Rob Groner rgro...@rtd.com wrote:
Does this revolve around hotplug and udev?
Yes. (Well, technically hotplug was superseded by udev)
In other words, is the idea that the created USB device will be in the nut
group,
Yes.
and thus I'd be able to tell
On Feb 18, 2015, at 7:56 PM, Gene Heskett ghesk...@wdtv.com wrote:
Even though I installed nut-doc, there are no man pages so I am running in
the dark again.
They seem to be in the file list:
https://packages.debian.org/wheezy/amd64/nut-client/filelist
Is $MANPATH set to something strange?
,
which has the side effect of preventing other non-root processes from meddling
with 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
-specific tweaks
to it, trying it would probably be faster than recompiling the kernel, and
there is little to lose.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
/build process, and gzip and attach
it? You should run 'make clean' first, or build from a new source directory.
This error shouldn't happen either, but it is possible that another -devel
package is missing somewhere. (We don't do much testing on fresh installs of
RHEL, I guess.)
--
Charles Lepple
' (or maybe
'lib64nss-devel'?) to get the NSS headers and development library.
--
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
hardware might need an external High
Speed to Full Speed rate-matching hub.
--
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
a driver which talks to ATCL FOR USB devices, but
with a different protocol:
http://thread.gmane.org/gmane.comp.monitoring.nut.user/8808/focus=8839
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
or directory
Check the messages from the blazer_usb driver when it starts. OpenWRT might not
have the permissions set up on the /dev/bus/usb node.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
submitting URB: Device or
resource busy
Device or resource busy usually means that another kernel driver or userspace
program is accessing the same device. Check for another copy of nutdrv_atcl_usb.
Which Raspberry Pi distribution are you using, and what is the kernel version?
--
Charles Lepple
, we can add the output of 'upsc' and 'upscmd -l' for your
UPS. (Feel free to mask off the serial number from the upsc output.)
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
?
In general, if a startup script isn't doing what I think it should, I run it
with sh -x name-of-script start. That will print a trace log of all of the
commands as they are executed.
In this particular case, do you have the mode in /etc/nut/nut.conf set up?
--
Charles Lepple
clepple@gmail
upsmon removes it at startup in the clear_pdflag() function (if
it was indeed created by upsmon last shutdown).
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
that can be renamed. I thought there was a Debian bug about this, but here's
the equivalent Ubuntu bug database entry:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
On Jan 30, 2015, at 11:12 PM, Charles Lepple clep...@gmail.com wrote:
On Jan 30, 2015, at 4:22 PM, Melvin Call melvincall...@gmail.com wrote:
At this point I unplugged the UPS and plugged it into a different USP port,
but
that did not change the above. Figuring this was likely a udev
the same
error from upsd?
--
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
ProductID of 0002
is one of the less-broken ones) but do you still get the read error if you add
the pollonly option to the UPS-specific part of ups.conf (i.e. after
[xs1500])?
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser
On Jan 22, 2015, at 9:53 AM, Sebastian Hosche sebastian.hos...@web.de wrote:
Hi Charles,
Thanks so much for your quick and detailed reply! I've added my answers and
details inline.
Sorry this reply wasn't as quick.
On 22.1.2015 04:46, Charles Lepple wrote:
On Jan 21, 2015, at 9:15 AM
NOTIFYCMD.
http://www.networkupstools.org/docs/man/upsmon.conf.html
--
- Charles Lepple
http://ghz.cc/charles/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
in.
Thanks,
Sebastian
logs.zip___
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
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
On Sun, Jan 18, 2015 at 1:07 PM, Charles Lepple clep...@gmail.com wrote:
On Fri, Jan 2, 2015 at 7:31 PM, hyo...@gmail.com hyo...@gmail.com wrote:
Before I merge it (well.. provided that it works..), I'd like to know
a couple of things more:
1. does the load.off command ('S00R') work
.5R), as well as 60 seconds (S01R).
I don't think this is a regression for my model, although the docs
suggest sending the command without the R:
http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/protocols/sola.html#_shutdown_command
--
- Charles Lepple
to the USB device, but I am not sure if that is still an
option. At the very least, it probably requires a developer certificate.
You may want to check out the HIDAPI project instead - if I recall correctly,
it uses the native HID interface on OS X (probably on Windows as well).
--
- Charles Lepple
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
do this weekend.
--
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, 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
ways that might make
it easier for others to help add new features in the future.
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
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
for me on OS X 10.9 (Mavericks) as well.
The only thing we need to watch out for is when the parameters to printf have
'%' embedded in them. Probably not a problem for the DDL, since '%' has special
meaning in URLs, but using 'printf %s' should avoid problems down the road.
Thanks,
- Charles
701 - 800 of 3309 matches
Mail list logo
