Displaying 11 results from an estimated 11 matches for "0.000153".
Did you mean:
0.000053
2011 Apr 28
1
Problem with blazer_ser/megatec when upgrading to 2.6.0 from 2.4
Hello
First things first, thanks for great work with NUT.
For years I used Informer compact 3kVA UPS
http://www.informups.com/informer_compact.html with nut/megatec serial
driver, but it stopped working when I switched to blazer_ser with
2.6.0 upgrade.
I'm using 2.6.0 on gentoo.
Blazer_ser seems to connect with UPS, but upsmon reports driver not connected.
uname -a
Linux localhost
2007 Dec 19
0
leaps
Thank you very much for the example. I think interactively I could get
something.
But my obstacle is to write an R script that processes my set of data
automatically.
My difficulty is to extract the information that appears on the screen, when
R is operated interactively, from a scripts.
Let me go over some steps to make sure I am doing things right.
Assume my data have been read into the matrix
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.
2006 Mar 15
2
swap at beginning of slice - danger?
Hello freebsd-stable,
I have 5.5-PRERELEASE server in production, booting from ad0s1:
# BLOCKSIZE=512 swapinfo
Device 512-blocks Used Avail Capacity
/dev/ad0s1b 2097152 52872 2044280 3%
/dev/ad1s1b 2097152 51952 2045200 2%
Total 4194304 104824 4089480 2%
# bsdlabel ad0s1 | fgrep b:
b: 2097152 0 swap
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