search for: 34661

...length: 60) dsl001-148-165.sfo1.dsl.speakeasy.net.39250 > mail.server.com.imaps: S [tcp sum ok] 3827175783:3827175783(0) win 5840 <mss 1460,sackOK,timestamp 1555810196 0,nop,wscale 2> LSOF: /var/log 91# lsof -i | grep imap sshd 4475 andrew 11u IPv4 39601 TCP localhost:34661->localhost:imaps (ESTABLISHED) dovecot 6540 root 5u IPv4 38988 TCP *:imaps (LISTEN) imap-logi 6599 dovecot 9u IPv4 39602 TCP localhost:imaps->localhost:34661 (ESTABLISHED) imap-logi 6629 dovecot 1u IPv4 38988 TCP *:imaps (LISTEN) imap-logi 6630 dovec...

Hi, On my x86_64 system I have a SiL311x controller that can do RAID. If I configure my 2 identical disks in a RAID1 setup, I would expect to see only 1 block device on Linux. Still I see 2 block devices. Is this intentional, and if so, isn't that dangerous ? (i.e. writing to both disks at the same time) Anyone with an insight, please explain :) -- dag wieers, dag at wieers.com,

...26 pending requests (max 1 secs, pid=34809, EOF) Jun 05 15:05:23 lmtp(34659): Error: write(auth socket) failed: Broken pipe Jun 05 15:05:24 lmtp(34649): Error: write(auth socket) failed: Broken pipe Jun 05 15:05:24 lmtp(34655): Error: write(auth socket) failed: Broken pipe Jun 05 15:05:24 lmtp(34661): Error: write(auth socket) failed: Broken pipe Jun 05 15:05:25 director: Error: Auth server disconnected unexpectedly Jun 05 15:05:25 director: Error: Auth server disconnected unexpectedly Jun 05 15:05:25 director: Error: Auth server disconnected unexpectedly Jun 05 15:05:25 director: Error: Auth...

https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another less important fix. - quota_warning scripts weren't

https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another less important fix. - quota_warning scripts weren't

...57448, 59759, 61350, 70081, 23412, 24078, 25157, 25813, 26845, 27522, 28035, 29885, 33453, 34823, 36470, 38876, 43025, 45422, 46674, 48547, 49026, 51011, 52661, 55224, 56155, 56881, 58671, 59214, 60475, 61110, 61691, 68951, 70135, 73754, 23349, 24817, 25505, 26846, 29162, 31760, 32979, 33497, 34661, 35836, 40191, 44880, 45457, 46079, 47357, 48374, 49093, 50187, 51892, 54524, 55210, 55810, 56243, 57605, 58565, 59249, 60339, 62345, 65299, 66304, 67782, 71822, 23275, 24132, 24592, 25057, 28456, 32484, 32961, 33442, 34287, 34864, 35334, 37177, 48274, 49067, 50791, 52114, 52728, 54547, 56413,...

Hi Konrad, Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361). It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0." With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between. dmesg and xm dmesg attached -- Sander Dom0 shows: total