search for: 50s

My email workflow with Dovecot is that mail gets delivered to INBOX, where I handle it and then move it into a folder called archive. I have alpine set to use the Default sort of "THREAD" of a folder. After moving a (few) mail(s) from INBOX to archive, archive takes a long time (10-50s) to load while alpine tells me: [Sorting "archive" ... ] (I can do the IMAP traces, but I figure alpine's terminology is going to be so similar to IMAP terminology that it should be straightforward enough for Timo to know what I'm talking about.) I...

...wasn't due to my changes. One of the tests that fail is basically: ssh -2 -F $build/regress/ssh_proxy 999.999.999.999 true The server reports: sshd[20529]: Disconnecting: Command terminated on signal 11. The culprit seems to be session.c line 1019 or so: snprintf(buf, sizeof buf, "%.50s %d %.50s %d", get_remote_ipaddr(), get_remote_port(), get_local_ipaddr(packet_get_connection_in()), get_local_port()); After poking around, it seems that: 1) get_local_ipaddr returns NULL 2) this NULL is passed to snprintf 3) which dereferences the NULL causing a SEGV (get_local_ipad...

...ENCODER=opusenc from opus-tools 0.2-3-gf5f571b ENCODER_OPTIONS=--bitrate 56 --vbr --comp 5 ALBUM=Test-Sweeps ARTIST=Audacity COMMENT=60s logarithmic sweep (0-20kHz): 5s=10Hz, 10s=20Hz, 15s=39Hz, 20 s=78Hz, 25s=156Hz, 30s=312Hz, 35s=625Hz, 40s=1.25kHz, 45s=2.5kHz, 50s=5kHz, 55s= 10kHz, 60s=20kHz COMMENTS=60s logarithmisch DATE=2016 TITLE=Sweep (0-20kHz at 96kHz) log TRACKNUMBER=2 Opus stream 1: Pre-skip: 312 Playback gain: 0 dB Channels: 1 Original sample rate: 96000 Hz Packet duration: 20...

...to load the data from a file: I tried the read.table(), the scan() and the matrix(scan()) options, but I have problems to allocate the single columns. The list() option could be a solution, but it is very unconvenient: list(0,0,0......). And how do I plot a single time series, let's say the 50s? And how to plot all of them? The last problem is maybe more advanced: I would like to plot all 100 time series, but with a confidence interval, where the density of data is indicated by the density of the colour of the confidence interval. A colleague gave me the tip that this is possible in...

...ens, cyan a 50-50 Blue/Green split with no Red votes and so on, with grey, black or white at a 1/3,1/3,1/3 split vote. I've spent a couple of half hours knocking out a function to do various versions of that, including using Red/Yellow/Blue for the primaries with Orange/Green/Purple for the 50/50s. I'm wondering if a) There's existing functionality in one of the packages on CRAN (I've had a look and googled) b) Anyone can point me to information about colour perception of this kind of three-way colour scheme. Thanks muchly. Barry

...ddr2(void); const char *get_remote_name_or_ip(u_int, int); char *get_peer_ipaddr(int); *** openssh-2.9.9p2/session.c.bak Sun Sep 16 15:17:15 2001 --- openssh-2.9.9p2/session.c Fri Oct 12 16:52:09 2001 *************** *** 1255,1260 **** --- 1255,1263 ---- snprintf(buf, sizeof buf, "%.50s %d %d", get_remote_ipaddr(), get_remote_port(), get_local_port()); child_set_env(&env, &envsize, "SSH_CLIENT", buf); + snprintf(buf, sizeof buf, "%.50s", + get_local_ipaddr2()); + child_set_env(&env, &envsize, "SSH_LOCAL", buf);...

...Node device not found I try to find the reason with gdb, and found that the 'nodedev-create' command will call virNetClientIOEventLoop() function of the remote driver, in this function, code will wait on: repoll: ret = poll(fds, ARRAY_CARDINALITY(fds), timeout); after about 50s, poll() returns, but the replied msg->header.status=VIR_NET_ERROR. I am not familiar with the rpc call in the remote driver, does anybody here can give some clues? BRs, Dennis

...acity means by a logarithmisch sweep. Is that a fixed number of Hertz per second (SoX calls that linear)? Or a fixed number of semitones per second (SoX calls that exponantional)? (The ogg comment says 5s=10Hz, 10s=20Hz, 15s=39Hz, 20s=78Hz, 25s=156Hz, 30s=312Hz, 35s=625Hz, 40s=1.25kHz, 45s=2.5kHz, 50s=5kHz, 55s=10kHz, 60s=20kHz so it seems the frequency rises logarithmically.) $ sox -c 1 -r 96k -b 16 -n /tmp/sweep.wav synth 60 sin create 1-20 gain -3 > With Opus I noticed that the file size for 48kHz and 48 kbps > compared to 96kHz Vorbis at 31kbps is about double the size Your opusenc...

...; ... #if !defined(_PATH_MAILDIR) && defined(MAILDIR) # define _PATH_MAILDIR MAILDIR #endif /* !defined(_PATH_MAILDIR) && defined(MAILDIR) */ In session.c, this definition gets used to set the MAIL environment variable: snprintf(buf, sizeof buf, "%.200s/%.50s", _PATH_MAILDIR, pw->pw_name); child_set_env(&env, &envsize, "MAIL", buf); This results in the doubled slash. I can recommend two alternatives to correct the problem. One trivial workaround for the bug is simply to test whether the last character of MAILDIR...

The waiting time is about 50s on my CentOS box now. "yum remove openssh* "and "yum install openssh*" can't make it right. "mv ~/.ssh{,.bak}" not works either. Here comes my tcpdump log, I am not an expert on SSH, Can anyone here get me out of this? Thanks Ryan [root at centos5u2 ~]# tcpdump...

...=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 2) [ 270...

...=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 2) [ 270...

...24 > kHz. And it was 50 seconds long. > > > How did you obtain it, > > I used Angelo Farina's "Aurora" modules. One of them is called "Generate > sine sweep". Can you please make that sound file available? It is hard to tell without having anything. (50s of sines shouldn't be large.) > > and how exactly did you encode and decode it? > > 1) Opusenc --bitrate 12 --downmix-mono Sweep50.wav Sweep50.opus > 2) Opusdec --float Sweep50.opus Sweep50out.wav

...bserved a considerable loss in performance. I would be interested to learn if others have similar experiences, and what the general opinion is concerning what version (and flags) to use for R! 1) gcc 3.2.0 -O3 can be much slower than gcc 3.2.0 -O2, causing a collection of simple tests to take over 50s instead of under 20s. This is due to -finline-functions!! 2) I have my own graphing/analysis programme that contains an expression language with a byte compiler (i.e. the parser constructs a call graph with the callback function pointers, memory for arguments and other relevant information). Again...

...acity means by a logarithmisch sweep. Is that a fixed number of Hertz per second (SoX calls that linear)? Or a fixed number of semitones per second (SoX calls that exponantional)? (The ogg comment says 5s=10Hz, 10s=20Hz, 15s=39Hz, 20s=78Hz, 25s=156Hz, 30s=312Hz, 35s=625Hz, 40s=1.25kHz, 45s=2.5kHz, 50s=5kHz, 55s=10kHz, 60s=20kHz so it seems the frequency rises logarithmically.) $ sox -c 1 -r 96k -b 16 -n /tmp/sweep.wav synth 60 sin create 1-20 gain -3 > With Opus I noticed that the file size for 48kHz and 48 kbps > compared to 96kHz Vorbis at 31kbps is about double the size Your opusenc...

> (PS, if you do use threads, protect speex_jitter_put/get with a mutex > (CRITICAL_SECTION I believe they're called in Win32Speak) -- calling put > and get at the exact same time from different threads leads to "features") I've never tested this, but I designed the jitter buffer to work from two threads even without using a mutex. This would work as long as there is

...est on redhat5.2 virtualization platform. But the startup process hung with messages: xen-vbd: registered block device major 202 xvda:<6>netfront: Initialising virtual ethernet driver. XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...<6>Uniform Multi-Platform E-IDE driver SCSI subsystem initialized st: Version 20080504, fixed bufsize 32768,...

I have been doing some profiling using the profile provider. I have a command that runs more slowly on the T1000 than it does on prior systems and I am trying to find out why. Using the profile provider at 1000 hz, and aggregating on the ustack output, I find that the same function appears at the top of the stack on both platforms, but on each there are specific instruction locations within

...ild_set_env(&env, &envsize, "USER", pw->pw_name); child_set_env(&env, &envsize, "LOGNAME", pw->pw_name); @@ -1245,10 +1323,22 @@ # endif /* HAVE_CYGWIN */ #endif /* HAVE_LOGIN_CAP */ +#ifndef MAILDIR_FORMAT snprintf(buf, sizeof buf, "%.200s/%.50s", _PATH_MAILDIR, pw->pw_name); +#else + snprintf(buf, sizeof buf, "%.240s/Maildir", + pw->pw_dir); + /* + * Check if $HOME/Maildir exists, otherwise set $MAIL to + * _PATH_MAILDIR/$USER + */ + if (stat(buf, &mailstat) != 0) { + snprintf(buf, sizeof buf, &...

...rocessed: 820 Uptime: 8h 51m 1s PID: 5624 Sessions: 1 Processed: 126 Uptime: 8h 20m 24s PID: 7328 Sessions: 1 Processed: 811 Uptime: 7h 49m 17s PID: 7274 Sessions: 1 Processed: 984 Uptime: 7h 49m 20s PID: 8761 Sessions: 1 Processed: 85 Uptime: 7h 18m 50s PID: 9135 Sessions: 1 Processed: 907 Uptime: 7h 16m 27s PID: 8777 Sessions: 1 Processed: 342 Uptime: 7h 18m 49s PID: 10508 Sessions: 1 Processed: 51 Uptime: 6h 47m 6s PID: 10853 Sessions: 1 Processed: 603 Uptime: 6h 43m 9s PID: 10620 Sessions: 1 Proc...