search for: spinned

I did some btrfs RTFS over the weeking and I have a hard time understanding what this code is attempting to do: 28 int btrfs_tree_lock(struct extent_buffer *eb) 29 { 30 int i; 31 32 if (mutex_trylock(&eb->mutex)) 33 return 0; 34 for (i = 0; i < 512; i++) { 35 cpu_relax(); 36 if

As we prepare to push ovirt-node ISOs to ovirt.org while also working on getting an ovirt-node spin into Fedora, there is some debate over whether the version hosted on ovirt.org should use the minimizer kickstart or not. Main argument for including the minimizer kickstart: Size. We're currently looking at something around 130MB for the ISO with minimizer and probably around double that

On 01/27/2016 08:11 AM, m.roth at 5-cent.us wrote: > my manager has me using > pmount/pumount to mount the hard drives I'm putting in the eSATA drive bay > for offline backups. Formerly, I used mount/umount, and when I umounted > it, and walked downstairs, mostly, esp the green drives, were spun down. I > pumount... and*nothing* spins down. I think you're seeing a simple

Hi all, I keep getting the following error messages on all my systems that have Vlans configured on it's ethernet interfaces. May 27 02:50:50 spin-gw snmpd[5226]: error on subcontainer 'ia_addr' insert (-1) May 27 02:50:50 spin-gw snmpd[5226]: error on subcontainer 'ia_addr' insert (-1) May 27 02:50:50 spin-gw snmpd[5226]: error on subcontainer '' insert (-1)

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

I have found XLispStat's spinning plots illuminating. I'd like to do the same thing in R. A dozen or so probes with help, help.search, apropos haven't turned up anything, and I've even resorted to grepping through the entire R source distribution looking for 'spin.*plot', to no avail. Either the feature is called something else in R (what?), or it's in some other

I just built a CentOS7 system on a Zotac NANO PC. I used a 320GB 2.5" HD I had sitting around and installed with Standard Partitions on XFS. The drive is spinning, nonstop. How can I monitor if there is actually disk i/o to warrant this constant spinning. So noatime for all partitions work with XFS?? I did some browsing and the claim is XFS uses realtime which is better? than noatime?

Hello people, Is there some simple way of spinning and/or flipping arrays in R? Here's what I mean. Suppose that foo is a 2x3x4 array with the following contents: (I know this is different than typing 'foo' at and R prompt, but I'm so used to row major order from using APL, I have a hard time with R's output) > foo[1,,] [,1] [,2] [,3] [,4] [1,] 1 2 3 4

https://fedoraproject.org/wiki/Ovirt_Node_Spin I noticed that virt-manager-tui is in rawhide finally, but the package name implies that it's not going to be in f16? virt-manager-tui.noarch 0.9.0-4.fc17 rawhide Cole, is this intentional or just smth that we need to follow up on? Also, I've noticed that ovirt-node needs refreshing... iirc apevec did tag/release of 2.0.1 from

I have an old external harddisk, Toshiba 320 Gb, with a USB connector that I wanted to check for contents. It did not start up when connected and I could not hear the motor spinning. After leaving it in the freezer overnight the motor spins but it is not recognized by my computer. I disassembled it and could see that the head assembly rests outside the disk but when it is powered on, the head

I'll file a ticket once fedorahosted is back online. The request is to port the isohybrid script, in the syslinux package, from perl to C (and of course submit it upstream). This would let syslinux drop its dependency on perl, which would save considerable space. $ wc -l git/syslinux/utils/isohybrid.in 258 git/syslinux/utils/isohybrid.in As this is doing some simple structure unpacking

PV-GRUB is really awesome, however I noticed that it spins at 100% cpu, even while just sitting at its prompt. Just a heads-up... Thanks, -Chris _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Is there an R version of the very handy S-PLUS function spin? I've tried the help pages and apropos() without success. Malcolm Quine -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the

On Wed, Jan 27, 2016 at 02:30:15PM +0000, Timothy Murphy wrote: > Jonathan Billings wrote: > > >> > Maybe you're not > >> > aware of it, but there are a LOT of things that systemd fixes that > >> > people are happy about. > > >> Like what ? I don't remember there were as many errors to fix before > >> systemd appeared. >

Hello fellow syslinux/extlinux users! Please forgive the long post, but I believe my problem warrants the background info to understand the issue. I've developed a specialized spin of Fedora that runs off CompactFlash. The spin is actually produced by the livecd-tools package and is then transferred to the CF card -- which has been formatted with ext3 -- using livecd-tools'

I''m having problems launching the spin process via the deploy.rb task. Everything works great when is run the script manually via: % ssh admin@monterey.example.net /Web/Rails/Example/current/script/spin However, when I run ''cap spinner'' or ''rake remote:exec ACTION=spinner'', I get the following errors: % cap spinner loading configuration

Estimados miembros de la lista, Estoy trabajando con la función spin del paquete knitr y no puedo entender por que a pesar de usar #+ para iniciar cada chunk no reconoce el inicio de un nuevo chunk al menos que incluya texto entre cada inicio de chunk. En el ejemplo abajo #+ data(cars) #+ cars No los separa como 2 chunks diferentes Ejemplo de mi archivo en r (prueba.R)

On Zed''s suggestion, I caught two new spinning mongrels and sent a SIGUSR2. The code appears to be stuck in read_multipart for both processes: # kill -USR2 6109 ** USR2 signal received. Thu Sep 21 14:55:39 EDT 2006: Reaping 1 threads for slow workers because of ''shutdown'' Thread #<Thread:0x419d7ce0 run> is too old, killing. Waiting for 1 requests to finish, could

Muchas gracias Carlos. Tengo las mismas versiones pero no logro separar los chunks cuando uso #+, pero si lo logro cuando uso #". Mi script es spin("prueba.R", knit = FALSE) y si me hace un Rmd. #+ a = c(1,2,3) #+ mean(a) Ejecuto, > spin("prueba.R", knit = FALSE) y obtengo un prueba.Rmd ```{r } a = c(1,2,3) ```{r } mean(a) ``` Pero si escribo: #' a =

Hi Dovecot-ers, Immediately on accessing our new dovecot 1.0b3 build, we see processes spinning, much like the old dovecot 0.9x builds did for us. Here is a ktrace of the spinning imap process: topos:tmp# kdump 18248 imap EMUL "native" 18248 imap PSIG SIGALRM caught handler=0x1c03ff88 mask=0x0 18248 imap CALL setitimer(0,0xcfbcb3bc,0xcfbcb3ac) 18248 imap RET