Displaying 12 results from an estimated 12 matches for "0.000159".
Did you mean:
0.000151
2009 Sep 19
1
Powercom 600AP USB support
Hi,
I know it's been a topic many times here, but I've searched the
archives, googled for days, and I simply don't believe, that there is
still no solution to this.
I'm using a PowerCom BNT-600AP ups with usb port.
I've downloaded the latest version from svn, compiled it, and tried to
use it:
* megatec(_usb) - no luck, it did not find the UPS (I?ve read in this
list, that
2020 Oct 11
1
[Bug 14529] New: Please add option to save metadata to single file to speed up backups
https://bugzilla.samba.org/show_bug.cgi?id=14529
Bug ID: 14529
Summary: Please add option to save metadata to single file to
speed up backups
Product: rsync
Version: 3.2.0
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: core
2023 Jun 13
3
Upssched 100% CPU after updating Debian 12
After launching the command several times, with debug (posted by new code
in a new branch for the investigation) confirming that the same daemon
handles operations from the new client instances, its strace now has
numerous FDs to report after select() - so I guess it is a problem of
detecting an exit of the counterpart.
0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT
2023 Jun 13
3
Upssched 100% CPU after updating Debian 12
After launching the command several times, with debug (posted by new code
in a new branch for the investigation) confirming that the same daemon
handles operations from the new client instances, its strace now has
numerous FDs to report after select() - so I guess it is a problem of
detecting an exit of the counterpart.
0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Hi,
Great work Jim! I?m glad you could reproduce the problem and found a potential culprit.
Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Hi,
Great work Jim! I?m glad you could reproduce the problem and found a potential culprit.
Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)
2023 Jun 13
0
Upssched 100% CPU after updating Debian 12
So... determining that FD is to be reaped proved hard. Internet lore
suggests fcntl() and poll() on the FD, but it just seems valid to them. The
errno is also usually not raised (once I saw a "111: Connection refused"
though).
So the best dumb idea so far is to bail out if we spent the whole loop (128
attempts) and only got zero-sized read replies and no errors.
2023 Jun 13
0
Upssched 100% CPU after updating Debian 12
So... determining that FD is to be reaped proved hard. Internet lore
suggests fcntl() and poll() on the FD, but it just seems valid to them. The
errno is also usually not raised (once I saw a "111: Connection refused"
though).
So the best dumb idea so far is to bail out if we spent the whole loop (128
attempts) and only got zero-sized read replies and no errors.
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
So, got some good news: I hear(*) I managed to reproduce the problem with
current NUT master and an adapted copy of your posted configs and script :D
Experimental debugging now sounds possible.
(*) PC under the desk wails with all its cooling fans as soon as I started
the client which spawned a daemon and itself had exited:
$ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
So, got some good news: I hear(*) I managed to reproduce the problem with
current NUT master and an adapted copy of your posted configs and script :D
Experimental debugging now sounds possible.
(*) PC under the desk wails with all its cooling fans as soon as I started
the client which spawned a daemon and itself had exited:
$ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT
2006 Apr 20
12
memcache, sessions, fragments, oh my!
Hi all -
I am trying to get rails to use memcache for sessions and fragment
caching. I''d also like to use the same connection for general caching of
this and that.
I''m following the instructions here:
http://wiki.rubyonrails.com/rails/pages/HowtoChangeSessionStore
and hitting a brick wall.
I''m using the new memcache-client since from what I''ve read
2015 Feb 14
2
freenas USB connection error
Hi all,
I'm a new user trying to get a Proline UPS I1000 UPS to work with freenas 9.3
over USB. When running upsdrvctl I get a permission denied error.
Required debug info:
OS name and version,
# uname -a
FreeBSD freenas.local 9.3-RELEASE-p5 FreeBSD 9.3-RELEASE-p5 #2
r275790+f84e770: Tue Dec 23 23:35:33 PST 2014
root at