similar to: imap processing spinning on the CPU

An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20080423/af167fa3/attachment.txt

An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20080423/af167fa3/attachment.txt

I got WoW to work, no problem. On Ubuntu 9.04 But when I log in, if I click my mouse the screen spins. and the camera is centered above my character. I checked my keybindings but didn't find anything that would cause that ..any idead?

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

Hello, The attached patch should fix Debian bug #128632 (http://bugs.debian.org/128632). This bug happened because if an error occurred in writefd_unbuffered (such as the remote end closing the socket), it would call rprintf, which would call io_multiplexing_write, which would in turn call writefd_unbuffered, which would then just sit in a loop trying to write to the broken socket. Also, we

R 3.0.2 OS X, Windows 7 Colleagues This is my first submission to this bulletin board so forgive me if I miss some etiquette issue. I am running some C code in Rgui in both OS X and Windows. It takes ~ 10 seconds for the code to execute. In OS X, the GUI is silent during this period. In Windows, a spinning wheel appears and the GUi grays out, then recovers. Is it possible to suppress the

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

> On April 7, 2017 at 6:48 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: > > > On Apr 7, 2017, at 11:17 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: > >> On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >

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

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

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

I was flipping through the code recently and noticed that we still have the double whammy of allocating dir entry positions with parent_dir->counter++ and that weird setting of f_pos to 2^31-1. So after enough creates (and deletes :)) in a directory we end up with an entry item whose key is past that value. f_pos gets rewound instead of being set to that magical EOF. readdir() gets stuck

I've been wanting to try out Squat for full-text indexing for a while now, so I finally gave it a whirl. I did a fresh pull from hg. I have it enabled, but it's taking *forever* to do a query. (Using alpine, I issued a Select command for all messages with some word anywhere, which presumably caused the Squat indexer to run.) I think Dovecot is infinite looping. I thought something

> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: > > > On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote: > >> On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote: > >>> >

Hi, dovecot's message parser enters an endless loop when fed with certain multipart messages with stray CR characters. parse_next_body_to_boundary() assumes the '\r' might be the beginning of a boundary line, reducing the block size by one: src/lib-mail/message-parser.c: 404 /* no linefeeds in this block. we can just skip it. */ 405 ret = 0; 406

Hello, I recently upgraded to dovecot 2.0.2 (on gentoo ~amd64) and now fts_squat's index building seems to hang for some of my mailboxes. The imap process gets stuck at 100% cpu usage and dovecot.index.search is never touched. I traced the problem to a message (attached) for one of the problematic mailboxes. Also attached are a full backtrace and the output of dovecot -n. The problem

Hi, I compressed a folder with the following script: ... for i in *.*.*; do file $i | grep bzip2 >/dev/null 2>&1 if [ $? -ne 0 ]; then echo "Compress: $i" cat "$i" | bzip2 -9 > ../tmp/$i if [ $? -eq 0 ]; then mv ../tmp/$i $i fi else

On Apr 7, 2017, at 11:17 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: >> On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>>> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote: >>>> On 7 Apr 2017, at 2.25, Daniel

I did Dovecot profiling on huge e-mail system, and p_strdup was very high on list. I do minor change: p_strdup: /* for (len = 0; (str)[len] != '\0'; ) len++; len++; */ len = strlen(str) + 1; p_strndup: /* len = 0; while (len < max_chars && ((const char *) str)[len] != '\0') len++; */ len = strnlen(str, max_chars); And after changes strdup drop down on the

> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote: > > > On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote: > > > > On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote: > >> Planning to release v2.2.29 on Monday. Please find and report any bugs before that. > > > > I'm seeing still