similar to: Incorrect battery.runtime.low being reported?

All, I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT version of SDS5-2-2015Q1branch-5579-15061. I then attempted to connect my desktop via SNMP. My desktop is running Arch Linux, with a

[please use reply-all to include the list.] > On Oct 12, 2015, at 4:52 PM, Daniel Green <ddgreen at gmail.com> wrote: > > I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT

On Mon, Mar 7, 2016 at 9:00 PM, Charles Lepple <clepple at gmail.com> wrote: > If you stop and start the driver, it should refresh. Hi Charles, thanks for the reply! Pardon the dead horse beating, but I just want to clarify/confirm two things: 1) I did my full power down test (including powering down UPS and NAS, and restarting them) after the change to 600s on the UPS. Shouldn't

I found their source code for what appears to be the previous version of DSM (their OS), the most recent entry in the NUT Changelog is: 2012-05-31 Arnaud Quette <arnaud.quette at free.fr> * [r3643] NEWS, UPGRADING, configure.in, docs/website/news.txt: Final update for 2.6.4 release Ah ha. Nevermind the above, I tried just running upsmon and that worked (with settings

On Mar 6, 2016, at 1:40 AM, Mike Lee <curby+forums at cur.by> wrote: > > As part of the desired second configuration, I reset the UPS to report > low battery when it had 10 minutes (600s) of estimated battery left. > However, battery.runtime.low as reported to NUT is still the default > of 120. "There are 2 hard problems in computer science: cache invalidation, naming

On Mar 8, 2016, at 12:54 PM, Mike Lee <curby+forums at cur.by> wrote: > > On Mon, Mar 7, 2016 at 9:00 PM, Charles Lepple <clepple at gmail.com> wrote: >> If you stop and start the driver, it should refresh. > > Hi Charles, thanks for the reply! Pardon the dead horse beating, but > I just want to clarify/confirm two things: > > 1) I did my full power down

I've grabbed a snapshot of NUT from just a couple days ago. Glad to see APC's new 5G UPSes added to the list (though you probably want to add it to the UDEV 52-nut-usbups.rules file as well...). My issues with new APC Smart-UPS units (SMT1000) : Powering-down the unit, whether with upsdrvctl or upscmd will not obey the specified delay in offdelay, or ups.delay.shutdown. Instead, a

On 06/01/16 17:36, Andreas Maier wrote: > Hi, > I have started using symbolic links on an SMB share and find that > symbolic links whose target no longer exists cannot be removed on the > client side. > > Example, on the SMB client side in an SMB-mounted directory: > > 1. Create a file and a relative symlink to it: > > $ touch a > $ ln -s a b > $

Hi, I have started using symbolic links on an SMB share and find that symbolic links whose target no longer exists cannot be removed on the client side. Example, on the SMB client side in an SMB-mounted directory: 1. Create a file and a relative symlink to it: $ touch a $ ln -s a b $ ls -l total 0 -rw-rw-r--. 1 andi andi 0 Jan 6 14:42 a lrwxrwxrwx. 1 andi andi 1

Has anybody tried to use a Polycom phone (I have 500s and 600s) with a netmask shorter than /24? (A network bigger than 255.255.255.0). We've run out of IPs in our initial /24 network, and I'd like to expand it to 255.255.248.0. When I set it to 255.255.248.0 I can ping the phone while the bootloader has control. As soon as the SIP application starts, I stop getting ping responses. Phone

As shown below, adding a message to TRASH doesn't increase virtual/test's MESSAGES count. However SELECTing virtual/test triggers the increase; so does running `doveadm mailbox status vsize virtual/test` in another shell. $ mkdir -m0700 ~/mail/virtual/test $ echo -e "TRASH\n\tall" > ~/mail/virtual/test/dovecot-virtual $ /usr/lib/dovecot/imap S: * PREAUTH [CAPABILITY

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 28 March 2019 21:31 Robert Kudyba <rkudyba@fordham.edu> wrote: </div> <div> <br> </div> <div> <br>

Since "PCI: Add runtime PM support for PCIe ports", the parent PCIe port can be runtime-suspended which disables power resources via ACPI. This is incompatible with DSM, resulting in a GPU device which is still in D3 and locks up the kernel on resume (on a Clevo P651RA, GTX965M). Mirror the behavior of Windows 8 and newer[1] (as observed via an AMLi debugger trace) and stop using the

Hi, Yufei: Thanks for your kind action. Let me centralize all the harm-hearted guys and involved alias in one email. Below is the answer of your question (Can you reply with more details on what failed? Does websphere use an IBM or Sun developed SDK? ) 1. Seems IBM bundled JDK can not detect agent options, like below: If use Sun JDK 1.5, no problem: /usr/jdk/jdk1.5.0_06/bin/java

Since "PCI: Add runtime PM support for PCIe ports", the parent PCIe port can be runtime-suspended which disables power resources via ACPI. This is incompatible with DSM, resulting in a GPU device which is still in D3 and locks up the kernel on resume. Mirror the behavior of Windows 8 and newer[1] (as observed via an AMLi debugger trace) and stop using the DSM functions for D3cold when

Hi all, I'm plotting to get the intersection value of three curves. Defining the x-axis as dsm, the following code works; dsm = c(800,600,NA,525,NA,450,400,NA,NA,NA,0) s3 = seq(0.05,1.05,0.1) plot(dsm,s3,col="blue",las=1,ylab="fraction",xlab="distance (km)") fc <- function(x,a,b){a*exp(-b*x)} fm <- nls(s3~fc(dsm,a,b),start=c(a=1,b=0)) co <- coef(fm)

On Tue, May 31, 2016 at 11:43:56AM +0300, Mika Westerberg wrote: > On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote: > > Do you have any suggestions for the case where the pcieport driver > > refuses to put the bridge in D3 (because the BIOS is too old)? In that > > case the nouveau driver needs to fallback to the DSM method (but not > > when runtime PM is

> On Mar 28, 2019, at 10:29 AM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> On 28 March 2019 16:08 Robert Kudyba via dovecot <dovecot at dovecot.org> wrote: >> >> >> dovecot-2.3.3-1.fc29.x86_64 >> >> Mar 28 10:04:47 auth: Panic: file http-client-request.c: line 283 (http_client_request_unref): assertion failed:

On a test shutdown of an APC Back-UPS RS1500 upsc was run periodically to follow the UPS discharge, it showed these values: battery.low 120 battery.charge.low 10 As it turned out, the battery.charge.low was encountered first and the system shut down there. However, considering the rate at which the charge was falling at the end I would much rather have had it shutdown sooner than it did. Is

Hi, I'm running this command: # upsrw -s "battery.date=2013Jun7" -u ups-mon-IT "IT-APC-BOTTOMRIGHT at 127.0.0.1" Password: OK but I'm getting this listing: # upsc IT-APC-BOTTOMRIGHT at 127.0.0.1 battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 15 battery.date: 01/10/06 battery.packs: 000 battery.runtime: 1440 battery.runtime.low: 120