search for: node7

http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz.sig So, this is it. Unless you can find a new and important bug within a week, this release is the same as v1.0. I'll only update the version number and NEWS file. Changes since rc29: * PAM: Lowercase the PAM service name when calling with "args = *". Linux PAM did this

http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz.sig So, this is it. Unless you can find a new and important bug within a week, this release is the same as v1.0. I'll only update the version number and NEWS file. Changes since rc29: * PAM: Lowercase the PAM service name when calling with "args = *". Linux PAM did this

I'm finally picking my dovecot project back up now, and after upgrading rc19 to rc27, I sent a test message to an existing account which resulted in log entries like these: Mar 16 08:45:37 node7 deliver(user at example.com): Corrupted transaction log file /var/indexes/example/com/u/us/user/.INBOX/dovecot.index.log: Append with UID 3, but next_uid = 15368 Mar 16 08:45:37 node7 deliver(user at example.com): msgid=<20070316124031.8F089D39A5 at node7.neonova.net>: save failed to INBO...

...t; ] node2 [ label="2: [ inf, 0.000000e+00 ]" ] node3 [ label="3: [ inf, 0.000000e+00 ]" ] node4 [ label="4: [ 5.357143e-02, 0.000000e+00 ]" ] node5 [ label="5: [ inf, 0.000000e+00 ]" ] node6 [ label="6: [ 6.250000e-02, 0.000000e+00 ]" ] node7 [ label="7: [ 7.500000e-02, 0.000000e+00 ]" ] node8 [ label="8: [ inf, 0.000000e+00 ]" ] node9 [ label="9: [ inf, 0.000000e+00 ]" ] node10 [ label="10: [ inf, 0.000000e+00 ]" ] node11 [ label="11: [ inf, 0.000000e+00 ]" ] node12 [ label=&q...

hello all, we are developing and porting vorbis1decoder on a 24 bit platform. in the process we came across somedoubts about node bytes and leaf words. from the specification we got that we are arranging the huffman codeword tree into an array. the nodebytes are the number of bytes that are required to represent a node and leafwords are the no. of bytes required to represent the leaf i.e the

...<f2> 1"]; node3 [shape = ellipse, label = "1"]; node2:f0 -> node3; node4[label = "<f0> 0 | <f1> | <f2> 1"]; node5 [shape = ellipse, label = "2"]; node4:f0 -> node5; node6[label = "<f0> 0 | <f1> | <f2> 1"]; node7[label = "<f0> 0 | <f1> | <f2> 1"]; node8[label = "<f0> 0 | <f1> | <f2> 1"]; node9 [shape = ellipse, label = "3"]; node8:f0 -> node9; node10[label = "<f0> 0 | <f1> | <f2> 1"]; node11 [shape = ellipse, la...

...t;2: [ inf, 0.000000e+00 ]" ] > node3 [ label="3: [ inf, 0.000000e+00 ]" ] > node4 [ label="4: [ 5.357143e-02, 0.000000e+00 ]" ] > node5 [ label="5: [ inf, 0.000000e+00 ]" ] > node6 [ label="6: [ 6.250000e-02, 0.000000e+00 ]" ] > node7 [ label="7: [ 7.500000e-02, 0.000000e+00 ]" ] > node8 [ label="8: [ inf, 0.000000e+00 ]" ] > node9 [ label="9: [ inf, 0.000000e+00 ]" ] > node10 [ label="10: [ inf, 0.000000e+00 ]" ] > node11 [ label="11: [ inf, 0.000000e+00 ]" ]...

Hi Lang, I'm surprised about the fact that you omit R1/R2 reductions in some cases. Can you give a more detailed description of the bug (e.g. a PBQP dump)? Best regards, Sebastian Lang Hames wrote: > Hi Sachin, llvm-dev, > > I've just committed a new PBQP solver which, among other things, > should take care of this bug. > > Please let me know how it works out for you.

...yi.domain:/mnt/xfsd/test_replica2_dis4 Brick4: bjzw.miaoyan.cluster1.node4.qiyi.domain:/mnt/xfsd/test_replica2_dis4 Brick5: bjzw.miaoyan.cluster1.node5.qiyi.domain:/mnt/xfsd/test_replica2_dis4 Brick6: bjzw.miaoyan.cluster1.node6.qiyi.domain:/mnt/xfsd/test_replica2_dis4 Brick7: bjzw.miaoyan.cluster1.node7.qiyi.domain:/mnt/xfsd/test_replica2_dis4 Brick8: bjzw.miaoyan.cluster1.node8.qiyi.domain:/mnt/xfsd/test_replica2_dis4 Options Reconfigured: features.limit-usage: /:5TB features.quota: enable -sh-4.1$ sudo dd if=/dev/zero of=iotest/testfff2 bs=1M count=1000 1000+0 records in 1000+0 records out 10485...

Hi, I've been trying to understand the documentation on the Speex echo canceller, and unless I'm confused, I think there's a mistake somewhere. The documentation on http://speex.org/docs/manual/speex-manual/node7.html#SECTION00740000000000000000 says, " The recommended tail length is approximately the third of the room reverberation time". However, the Octave script echo_diagnostic.m has the code: if (b > .3*tail_length) printf ('This is too much delay, try delaying the far-e...

I've got a question about the granulepos in speex packets. >From the speex manual (http://www.speex.org/manual2/node7.html#SECTION00073000000000000000): >The third and subsequent packets each contain one or more (number found in header) Speex frames. These are identified with packetno starting from 2 and the granulepos is the number of the last sample encoded in that packet. In experimenting however, it seems...

I have my login log format set like so: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c When I log in using a full email address, though, I only get the username part of the address: Jan 24 13:28:29 node7 dovecot: pop3-login: Login: user=<justin>, method=PLAIN, rip=137.118.2.60, lip=137.118.7.247 Jan 24 13:28:30 node7 dovecot: POP3(justin): Disconnected: Logged out top=0/0, retr=0/0, del=0/717, size=15797460 Is that behavior intentional? If so, can it log the full username as given by the...

Hi Sachin, llvm-dev, I've just committed a new PBQP solver which, among other things, should take care of this bug. Please let me know how it works out for you. Cheers, Lang. On Tue, Dec 15, 2009 at 5:54 PM, Lang Hames <lhames at gmail.com> wrote: > Hi Sachin, > > Yes. Bernhard Scholz and I have just discussed a fix for this. I hope to > commit it in the next few days. I

Hi, I am a bit confused on how code-words are derived from the codeword lengths. I will appreciate if someone can point me in the correct direction. I will take the example of an actual codebook that i found in a valid vorbis encoded file as shown below. [SK] +------Codebook [0] -------- [SK] Codebook Dimensions = 1 [SK] Codebook Entries = 8 [SK] Unordered [SK] 1, 6, 3, 7, 2, 5, 4, 7, [SK] NO

Hi guys, I'm writing an application that will sniff audio streams going across the network and allow a seperate client application to listen into one of these streams. I was looking into ways to distribute the captured stream media to a client for listening, and icecast came to mind. Icecast, as I understand it, is usually used for streaming a few data sources to MANY clients. As I want

...th that. Here's my rsyncd.conf: use chroot = false strict modes = false hosts allow = * log file = rsyncd.log pid file = rsyncd.pid [crystal_windows] path=/stuff/windows read only=false comment=some stuff When I run the following command from my laptop: rsync -vzrLpogtu /stuff/windows/ user@node7::crystal_windows It sets *ALL* the files in the /stuff/windows folder on the remote machine to read-only. This is a big problem because it means that when an operator goes to edit a file in the windows folder with a program, he has to first make the file not read only. Is it possible to change t...

...-Sep-2007 11:42 .fonts.conf 28545958 -rw------- 1 2522 2004 31 4-Sep-2007 12:07 .mcoprc 28545959 drwxr-xr-x 2 2522 2004 4096 4-Sep-2007 12:17 .wp 28545962 drwxr-xr-x 2 2522 2004 4096 4-Sep-2007 15:04 .seqlab-node7 28545967 -rw-r--r-- 1 2522 2004 707 4-Sep-2007 16:16 .seqlab-history 28545968 drwxr-xr-x 5 2522 2004 4096 4-Sep-2007 15:05 GCGSeqmergeTests etc stat gives [root@jic55124 databases]# echo "stat /users/cbu/vigourom" | debugfs...

...-Sep-2007 11:42 .fonts.conf 28545958 -rw------- 1 2522 2004 31 4-Sep-2007 12:07 .mcoprc 28545959 drwxr-xr-x 2 2522 2004 4096 4-Sep-2007 12:17 .wp 28545962 drwxr-xr-x 2 2522 2004 4096 4-Sep-2007 15:04 .seqlab-node7 28545967 -rw-r--r-- 1 2522 2004 707 4-Sep-2007 16:16 .seqlab-history 28545968 drwxr-xr-x 5 2522 2004 4096 4-Sep-2007 15:05 GCGSeqmergeTests etc stat gives [root@jic55124 databases]# echo "stat /users/cbu/vigourom" | debugfs...

...cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-3,32-35 NUMA node1 CPU(s): 4-7,36-39 NUMA node2 CPU(s): 8-11,40-43 NUMA node3 CPU(s): 12-15,44-47 NUMA node4 CPU(s): 16-19,48-51 NUMA node5 CPU(s): 20-23,52-55 NUMA node6 CPU(s): 24-27,56-59 NUMA node7 CPU(s): 28-31,60-63 I'm running one big virtual on this hypervizor - almost whole memory + all physical CPUs. This is what I'm seeing inside: root@zenon10:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s):...

...6 credit y 0 Pool-node2 6 credit y 0 Pool-node3 6 credit y 0 Pool-node4 6 credit y 0 Pool-node5 6 credit y 0 Pool-node6 6 credit y 0 Pool-node7 6 credit y 0 root@dosorca:/data/images# xl cpupool-list -c Name CPU list Pool-node0 0,1,2,3,4,5 Pool-node1 6,7,8,9,10,11 Pool-node2 12,13,14,15,16,17 Pool-node3 18,19,20,21,22,23 Pool-node4 24,25,26,27,28,29 Pool-node...