search for: lengthening

Good day, I am the only user of the laptop at home. Please, How/where can I change to keep to screen longer open. Thanks Johan

On Thursday 29 October 2020 22:12:00 Charles Lepple wrote: > On Oct 28, 2020, at 9:56 PM, Gene Heskett <gheskett at shentel.net> wrote: > > Which looks very incomplete to me. OTOH, its not a very big UPS but > > neither is the pi. I have tested that, and it shuts off long before > > it outouts a LB signal. > > Which part looks incomplete, the variables or the

Dear all, I wonder what's special about spinograms {vcd} that prevents me from using it the way I do with other plots. I do: > spine(f.speaker.identity ~ x.log.lengthening, > data=ms,breaks=45,gp=gpar(fill=c("red","green")),xlab="length difference > (log ms)",ylab="speaker") > curve(0*x,add=T) Error in plot.xy(xy.coords(x, y), type = type, col = col, lty = lty, ...) : plot.new has not been called yet OK, if I do...

A server at work today appeared unresponsive to all network traffic. The machine in question doesn't have a k/v/m terminal; it's configured to use a serial console. So I connected to the serial console and got /etc/issue (with all the \char sequences properly expanded). At the login: prompt I typed root and pressed Enter. Several seconds went by before the Password: prompt was

...te from the list of instant commands. (There is another "shutdown delay" - the time between when NUT signals the UPS to turn off, and when the relay actually goes "clunk". That would be "ups.delay.shutdown", but from the context, it sounds like you are concerned about lengthening the time between when the power fails and when the UPS says "the battery is low". A USB HID UPS typically measures it the other way: the battery is low (LB flag is set) when either: * the charge is below a certain percentage (battery.charge.low) * or the runtime is below a certain numbe...

After doing a lot of automated seek testing on files, it looks like the length of the sync code (currently 9 bits) is not long enough to enable a really robust AND efficient seek algorithm. Lengthening the sync code will require a format change (i.e. FLAC <0.8 streams won't play back on FLAC >0.9 decoders), so I'm sending this message out to see if there is any "NO DON'T DO IT!" kind of feedback from users. While I'm at it I will probably add a frame-level CRC as...

Hi list, Recently I was debugging L2 guest slow booting issue in nested virtualization environment (both L0 and L1 hypervisors are all Xen). To boot a L2 Linux guest (RHEL6u2), it will need to wait more than 3 minutes after grub loaded, I did some profile, and see guest is doing disk operations by int13 BIOS procedure. Even not consider the nested case, I saw there is a bug reporting normal VM

I am working on a streaming download (CSV) from Rails 3.2 and am coming up against an issue of the initial page request taking a long time. The following controller code illustrates my issue: self.response_body = Enumerator.new do |y| 10_000_000.times do y << "Hello World" end end With the above, the response does seem like its streaming

Belkin F6C1200-UNV on Ubuntu 7.04, megatec_usb driver, Every few minutes I get a beep and a "UPS not available" message that seems to be bogus; upsc reports real data, not at complaint that it's stale. Is there some timeout I need to lengthen? Also, shouldn't upsc report the poll time associated with the data it displays? -- >>esr>>

I have several data input functions that include a construct like the following: indat <- function(stuff) { [...] awkp <- paste("awk ...yada yada...", stuff, etc.) scan(pipe(awkp),quiet=TRUE) } I use these functions a lot, and as I do, a lengthening list of closed, but undestroyed, connections accumulates. Ultimately this appears to stuff things up and cause error messages, such as "cannot close output sink connection". I seem to remember a related query some time ago on this list, but I can't locate it. So my question is: Sho...

Hello there, I have a fairly simple request (I hope!) I have produced a filled contour plot like this: library(grDevices) library(gplots) library(plotrix) filled.contour(contour, axes=F, frame.plot=TRUE, color=terrain.colors, ylab= "Length Along Flume (m)", key.title = title(main="Velocity\n(m/s)"), key.axes = axis(4, seq(0, 0.6, by = 0.1)), asp=2, plot.axes = {

On 02/02/2014 01:48, David Chisnall wrote: > In most calling conventions, this is a callee-save register. After its last use, the register allocator may reuse that register. On x86 and ARM, the register that contains this is also (usually) the register used for But the rule "after the last use, the register allocator may reuse it" is also introduced by llvm, since register

I second this proposal, and I make a motion to lengthen 3/1.5 to 6/5. On Fri, May 11, 2018 at 9:37 AM, Keane, Erich via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi All- > As we all know, the C++14 discussion is flaring up again. Chandler > brought up that he would like a concrete plan to switch. In my opinion, > this is insufficient, as it will result in us simply

Ping From: Mandeep Singh Grang [mailto:mgrang at codeaurora.org] Sent: Tuesday, February 03, 2015 4:34 PM To: 'llvmdev at cs.uiuc.edu' Cc: 'ghoflehner at apple.com'; 'apazos at codeaurora.org'; mgrang at codeaurora.org Subject: Question on Machine Combiner Pass Hi, In the file lib/CodeGen/MachineCombiner.cpp I see that in the function

Hi, I've dug a bit through the wiki and the mailing lists, and haven't really seen anything like this, but there must be someone out there doing this. Basically, there is a fax line that I don't want to answer inbound, but I want it available to do dial out from. Right now, we are using a busy wait around the ringing line, but I was hoping for something that might be a little more

Based on my reading of the release pages (https://gcc.gnu.org/releases.html and http://releases.llvm.org/) 6/5 would make GCC 4.7 and Clang 3.1 required, and GCC 4.8 and Clang 3.3 the first to not warn. 6/5 is surprisingly close to making the policy conform to exactly our current time-lag, where we are GCC4.8 (instead of 4.7) and Clang 3.1 (also 3.1). -Erich From: Andrew Kelley

We''ve been noticing a lot of these errors when booting VMs since we moved to 3.0.3 - I''ve traced this to the hotplug scripts in Dom0 taking >10s to run to completion and specifically the vif-bridge script taking >=9s to plug the vif into the s/w bridge on occasion - was wondering if anyone has any insight into why it might take this long. I added some instrumentation to

Dear R-SIG-Debian, > > a) You still haven't explained why you need to rebuild it when > ? ? ? sudo apt-get install r-cran-rgl > ? gets you a binary I do not want to answer for the OP, but for myself, two things: 1) I maintain a personal library in my HOME folder - for a few reasons - and one of the benefits is that I can install/update R packages without needing to run R as

The test relies on the timeout program. Also, since the nbdkit_nanosleep code relies on the Linux extension POLLRDHUP to detect early client closure, we may have to relax that part of the test when porting to platforms that lack ppoll/POLLRDHUP. (That is, while we should still be able to let a signal to the server shut down nbdkit quickly, it's harder to let a client close()ing its end cause

Hi All- As we all know, the C++14 discussion is flaring up again. Chandler brought up that he would like a concrete plan to switch. In my opinion, this is insufficient, as it will result in us simply having this discussion AGAIN next release. Instead, I would prefer us to have a concrete Policy on our host compilers. That way, changes like this are unsurprising to our users, and advance our