search for: psa

...mostly static content, I don't have any issues. Below are my options: #!/bin/sh TERM="VT100" RSYNC_RSH="ssh -c blowfish -2 -i /usr/username/.ssh/id_dsa" export RSYNC_RSH echo ' ' /bin/date /bin/rsync -lrtv --stats --timeout=300 --delete-after \ /home/backup/psa username@hostname.net:/home/username/backup source ssh version: OpenSSH_3.9p1 destination ssh version: OpenSSH_3.6.1p2 Output of rsync log: Sat Sep 24 03:01:01 EDT 2005 building file list ... done psa/ psa/psa.dump.full.monthly.aa psa/psa.dump.full.monthly.ab psa/psa.dump.full.monthly.ac psa/psa...

...: Brick1: ylal3020:/soft/venus Brick2: ylal3030:/soft/venus Brick3: yval1000:/soft/venus Brick4: yval1010:/soft/venus Options Reconfigured: nfs.port: 2049 performance.cache-refresh-timeout: 60 performance.cache-size: 1GB network.ping-timeout: 10 features.quota: on features.limit-usage: /test:100MB,/psa:200MB,/:7GB,/soft:5GB features.quota-timeout: 120 Size of each folder from the mount point : /test : 4.1MB /psa : 160MB /soft : 1.2GB Total size 1.4GB (If you want the complete output of du, don't hesitate) gluster volume quota venus list path limit_set size -------...

Hi, Back in 2011, it was reported that Liebert PSA devices persist in reporting OB (On Battery) when using usbhid-ups regardless of the actual state. Pier Paolo did some work (2011) which reportedly solved the issue. However, that doesn't seem to have reached mainstream and I now face the same problem. I'm using NUT 2.6.3 with a new Li...

...3?) is rhe current version, and it makes little sense to backport changes. Nut is a trivial compile . . . 'Use the source, Luke . . .' - Tim On October 17, 2014 6:05:35 PM CDT, Derek Harding <derek at lagham.org.uk> wrote: >Hi, > >Back in 2011, it was reported that Liebert PSA devices persist in >reporting OB (On Battery) when using usbhid-ups regardless of the >actual >state. Pier Paolo did some work (2011) which reportedly solved the >issue. However, that doesn't seem to have reached mainstream and I now >face the same problem. > >I'm u...

...use 2.6.3 is not a current release. 2.7.2 (or 3?) is rhe current version, and it makes little sense to backport changes. Tim, It's possible that these changes didn't make it in. I admit that would be my knee-jerk reaction to seeing an older version number, but the last occurrence of "PSA" in the drivers/ Git log is 2009. > Nut is a trivial compile . . . 'Use the source, Luke . . .' > > - Tim > On October 17, 2014 6:05:35 PM CDT, Derek Harding <derek at lagham.org.uk> wrote: > Hi, > > Back in 2011, it was reported that Liebert PSA devices...

...elease. 2.7.2 (or 3?) is rhe >current version, and it makes little sense to backport changes. > >Tim, > >It's possible that these changes didn't make it in. I admit that would >be my knee-jerk reaction to seeing an older version number, but the >last occurrence of "PSA" in the drivers/ Git log is 2009. > >> Nut is a trivial compile . . . 'Use the source, Luke . . .' >> >> - Tim >> >On October 17, 2014 6:05:35 PM CDT, Derek Harding <derek at lagham.org.uk> >wrote: >> Hi, >> >> Back in 2011, i...

Hello The page https://networkupstools.org/ddl/Liebert/PSA_1500.html don't contain all information about UPS series PSA. First, the variable "*device.serial*" is dummy, it is always empty , and "*ups.serial*" also always empty. Second, configuration file for the all UPS "PSA" contain these lines: [PSA] ??? driver = &...

[FAQ on USB-connected UPSes] > Remember: this is brand new *experimental* software and is probably > very broken. Do us a favor and report successes or failures to > the mailing lists. No problem ... : UPS: Liebert PowerSure PSA 500 NUT: Version 2.0.2 Kernel: 2.6.11.5, with CONFIG_USB_HID, CONFIG_USB_HIDINPUT, and CONFIG_USB_HIDDEV compiled in (statically) ================================================================ Driver: liebert Conn.: Original RS232 cable Starts OK, but fails to detect any events I tried (pulli...

Begin forwarded message: > From: "Paul Smith" > Subject: Liebert PSA UPS problem. > Date: July 31, 2013 4:42:33 PM EDT > To: <nut-upsuser at lists.alioth.debian.org> > > Hi all, > A brief summary: > > I have a new Liebert PSA UPS which I wanted to help support my FreeNAS box (a FreeBSD 8 variant). Unfortunately the nut-ups implementa...

This patch adds support for the following ups to liebert-hid.c: $ lsusb | grep Liebert Bus 007 Device 005: ID 10af:0001 Liebert Corp. PowerSure PSA UPS Using this patch, I'm able to obtain information about the ups via upsc: $ upsc upsname battery.charge: 100 battery.runtime: 1012 battery.type: PbAc battery.voltage: 1172 battery.voltage.nominal: 12 driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 dri...

Anyone have any advice what I need to do next? Regards, Paul. -----Original Message----- From: Nut-upsuser [mailto:nut-upsuser-bounces+paul=smithp.co.uk at lists.alioth.debian.org] On Behalf Of Charles Lepple Sent: 02 August 2013 11:36 To: nut-upsuser list Subject: [Nut-upsuser] Fwd: Liebert PSA UPS problem. Begin forwarded message: > From: "Paul Smith" > Subject: Liebert PSA UPS problem. > Date: July 31, 2013 4:42:33 PM EDT > To: <nut-upsuser at lists.alioth.debian.org> > > Hi all, > A brief summary: > > I have a new Liebert PSA UPS which...

Hi all, This is just a PSA that as of r302752, 3 parallel algorithms (for_each, for_each_n, and sort) are available in llvm/Support/Parallel.h. Effort was made to match the C++ Parallelism TS N4507 [ http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4507.pdf] as closely as possible, but some aspects were intentionall...

...en the call is answered. ; Standard extension logic [macro-stdexten] ; ${ARG1}=Extension ${ARG2}=Device(s) to ring exten => s,1,NoOp(stdexten ${EXTEN}) exten => s,n,Set(cname=${CALLERID(number)}@asterisk.deskoptional.com) exten => s,n,Set(CALLERID(number)=${cname}) exten => s,n,Macro(psa-predial) exten => s,n,Dial(${ARG2},20,tTwW) exten => s,n,Set(savestatus=${DIALSTATUS}) exten => s,n,Macro(psa-postdial) exten => s,n,Goto(s-${savestatus},1);ANSWER,BUSY,CHANUNAVAIL,CONGESTION,ANSWER exten => s-ANSWER,1,NoOp(call was answered!!!!!) exten => s-CHANUNAVAIL,1,VoiceMa...

...>>current version, and it makes little sense to backport changes. >> >>Tim, >> >>It's possible that these changes didn't make it in. I admit that would >>be my knee-jerk reaction to seeing an older version number, but the >>last occurrence of "PSA" in the drivers/ Git log is 2009. >> >>> Nut is a trivial compile . . . 'Use the source, Luke . . .' >>> >>> - Tim >>> >>On October 17, 2014 6:05:35 PM CDT, Derek Harding ><derek at lagham.org.uk> >>wrote: >>> Hi...

I have a matrix of p-values for for each explanatory variable. Each row is an area of the response variable and each column is an explanatory variable. e.g. PSA pval_DOY pval_PDSIconcurrent pval_PDSIantecedent_annual_average pval_TMAXanomaly pval_FM100anomaly 1 NC06 0.96747495 0.6092668 0.53353019 0.9301115 0.99801334 2 NC04 0.04699659 0.2759152 0.07024752 0.6046828...

...? ? ? ? K [ c g d` a? ?? ?? (? -? ?? ?? ;? ?? G? ?? ?? ?? ?? ? ? ? ?? %? ? ?& ?) ?, .Data .Names ? ???1??1o`k???E??:?????28q|??9V 9`???7?C?%???KI????????Bt0??K#4????\??_????d?}?e?????=6???p PREOP.PSA PREOP.PSA' T.STG=T2A T.STG=T2B T.STG=T2C T.STG=T3 G1=> 3 G2=> 3 BX.POS BX.NEG RP.YEAR G1=> 3 * G2=> 3 .Data .Dim .Dimnames ? ? = E 6??w??a??_?JM g???j???E???rV?>??? T??>WD?Ow:?? ... SA?;_ws6?@?(??Lp@????QEF??VU9X?f??????[????'??T????-?91???F????K???...

...n 19.1 or later, so 19.0 is not > sufficient. > > --paulr > > > > *From:* llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] *On Behalf Of *JF > Bastien via llvm-dev > *Sent:* Friday, February 08, 2019 1:16 PM > *To:* via llvm-dev; cfe-dev > *Subject:* [llvm-dev] [PSA] minimum toolchain update completed > > > > Hello compiler fans! > > > > As discussed in the RFC > <http://lists.llvm.org/pipermail/llvm-dev/2019-January/129452.html>, > LLVM’s cmake configuration now soft-errors if you use an older toolchain to > build. The n...

...t; accurate? > > If so, I'll rely on that behavior in LLDB, and extend the implementation > in LLVM accordingly. > > On Wed, May 10, 2017 at 5:37 PM, Zachary Turner via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi all, >> >> This is just a PSA that as of r302752, 3 parallel algorithms (for_each, >> for_each_n, and sort) are available in llvm/Support/Parallel.h. >> >> Effort was made to match the C++ Parallelism TS N4507 [ >> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4507.pdf] as >> closely as...

This is the last post in the old thread: http://lists.alioth.debian.org/pipermail/nut-upsuser/2011-February/006651.html I'm marginally reluctant to install a non-standard release on a customer server because I may not be the next person to have to work on it, however, I do agree the most recent is usually the first port-of-call. Since it seems the fix didn't get followed through,

http://netsystemsresearch.com/ dovecot.log.1.bz2:Jan 05 17:28:15 pop3-login: Info: Disconnected (no auth attempts in 3 secs): user=<>, rip=169.54.233.124, lip=MYIP, TLS handshaking: Disconnected, session=<z/L0OVxFetOpNul8> Their "research" pokes your email ports. Block if you want or participate in the (cough cough) research. IP addresses and opt-out email address on