Displaying 20 results from an estimated 1000 matches similar to: "Apple patch 9"
2009 Jan 06
3
Apple patches 11-14
These are the last patches for now, and they're small. The base for
each of them is dovecot-1.1.7 + Apple patches 9 and 10, again not
because of a logical dependency but just because these patches change
parts of the earlier patches.
Patch #11 adds a few dtrace providers to key points in the code. We
are still validating the correct placement and usefulness of these.
One cool
2008 Dec 17
6
Apple patches 6-8
Here are a few more patches. Still keeping it easy for now. Again
the basis for these patches is dovecot-1.1.7.
Patch #6. Solve a cross-compilation endianness issue. Currently,
Dovecot assumes that the endianness of the build system is the same as
the endianness of the runtime system. This is not necessarily true.
We ran into this while compiling for i386 on a ppc machine. The
2018 Sep 10
0
make check (pigeonhole)
I did so as non-root user and got the same error.
On 9/10/2018 9:10 AM, Aki Tuomi wrote:
> Have you attempted this as non-root user?
>
>
>
> ---
> Aki Tuomi
> Dovecot oy
>
> -------- Original message --------
> From: Eric Broch <ebroch at whitehorsetc.com>
> Date: 10/09/2018 18:03 (GMT+02:00)
> To: dovecot at dovecot.org
> Subject: Re: make check
2018 Sep 10
1
make check (pigeonhole)
Dovecot list,
1) I downloaded latest dovecot and pigeonhole tar balls and extracted on
latest updated CentOS 7 : dovecot-2.3.2.1.tar.gz and
dovecot-2.3-pigeonhole-0.5.2.tar.gz
2) I moved pigeonhole (dovecot-2.3-pigeonhole-0.5.2) directory into
dovecot (dovecot-2.3.2.1) directory
3) built dovecot with following config and paramerters:
patch -p1 <
2009 Jan 06
2
Apple patch 10
Patch #10 allows the pop3 and imap mail processes to handle multiple
clients. We know this weakens the security model but it greatly
increases scalability especially when clients are idle.
Here's how it works. When there are no mail processes, or none
serving fewer than mail_max_connections clients, the master creates a
new mail process pretty much like it does now, but with some
2016 Mar 11
0
[PATCH v1 19/19] zram: use __GFP_MOVABLE for memory allocation
Zsmalloc is ready for page migration so zram can use __GFP_MOVABLE
from now on.
I did test to see how it helps to make higher order pages.
Test scenario is as follows.
KVM guest, 1G memory, ext4 formated zram block device,
for i in `seq 1 8`;
do
dd if=/dev/vda1 of=mnt/test$i.txt bs=128M count=1 &
done
wait `pidof dd`
for i in `seq 1 2 8`;
do
rm -rf mnt/test$i.txt
done
2006 Apr 28
1
imaptest, with options!
I hacked some command line options into imaptest.
I dont think I broke it..
Place into dovecot-source root as usual and compile with:
gcc imaptest.c -o imaptest -Wall -W -I. -Isrc/lib -DHAVE_CONFIG_H
src/lib/liblib.a
As per Timo's instructions.
# imaptest -h imaptest [USER at IP:PORTNO] [pass=PASSWORD] [mbox=MBOX]
[clients=CC] [msgs=NMSG] [use_authenticate] [PORTNO]
USER = template for
2018 Sep 09
3
make check (pigeonhole)
Hello list,
During the 'make check' (pigeonhole) portion of a building (rpmbuild) a
dovecot.spec file I'm getting the following error:
testsuite(root): Fatal: Couldn't drop privileges: User is missing UID
(see mail_uid setting)
I'm not sure how to resolve this, and any help would be appreciated to
help me finish the creating the rpm
--
Eric Broch
White Horse Technical
2016 Jun 22
3
Re: [libvirt-users] virt-sparsify changing the apparent-size of files
On Wed, Jun 22, 2016 at 12:40:40AM -0500, libvirt_users@skagitattic.com wrote:
> So you are saying when I do the virt-sparsify its converting the image
> from raw to [qcow2]?
No. virt-sparsify will use the same input and output formats, unless
you use the --convert option.
> I studied the man page for virt-sparsify and tried again with
> the flag "--format raw"
2008 Dec 22
1
Web-driven SIP call thru Asterisk IPBX
Hi,
I think that the web-driven SIP Phone (free) doddle (beta version) can be useful with your Asterisk applications.
You can pre-fill it with your sip settings (Asterisk host name or IP /?realm / sip user), you just need to setup the HTML link as that: (Attached is the HTML page example)
?
/**************************/
simple HTML code example:
/*************************/
<html>
<head>
2023 Mar 29
1
[PATCH] mm: Take a page reference when removing device exclusive entries
On 3/28/23 20:16, Matthew Wilcox wrote:
...
>> + if (!get_page_unless_zero(vmf->page))
>> + return 0;
>
> From a folio point of view: what the hell are you doing here? Tail
> pages don't have individual refcounts; all the refcounts are actually
ohh, and I really should have caught that too. I plead spending too much
time recently in a somewhat more driver-centric
2023 Mar 29
1
[PATCH] mm: Take a page reference when removing device exclusive entries
On Tue, Mar 28, 2023 at 01:14:34PM +1100, Alistair Popple wrote:
> +++ b/mm/memory.c
> @@ -3623,8 +3623,19 @@ static vm_fault_t remove_device_exclusive_entry(struct vm_fault *vmf)
> struct vm_area_struct *vma = vmf->vma;
> struct mmu_notifier_range range;
>
> - if (!folio_lock_or_retry(folio, vma->vm_mm, vmf->flags))
> + /*
> + * We need a page reference to
2023 Mar 30
1
[PATCH] mm: Take a page reference when removing device exclusive entries
John Hubbard <jhubbard at nvidia.com> writes:
> On 3/28/23 20:16, Matthew Wilcox wrote:
> ...
>>> + if (!get_page_unless_zero(vmf->page))
>>> + return 0;
>> From a folio point of view: what the hell are you doing here? Tail
>> pages don't have individual refcounts; all the refcounts are actually
I had stuck with using the page because none of
2018 May 01
1
Re: Create qcow2 v3 volumes via libvirt
On Tue, May 1, 2018 at 10:45 AM, Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Tue, Jan 30, 2018 at 01:17:21PM +0100, Gionatan Danti wrote:
> > Hi all,
> > on a fully patched CentOS 7.4 x86-64, I see the following behavior:
> >
> > - when creating a new volumes using vol-create-as, the resulting file is
> a
> > qcow2 version 2 (compat=0.10) file.
2014 Mar 12
0
Finding memory leaks
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I try to find a memory leak in a dovecot plugin that I develop. In
order to find it, it would be helpful to print the total amount of
memory that is currently allocated. This print could than spread over
the source code and the memory consumption can be tracked.
I've tried
i_debug("pool size %u",
(unsigned
2016 Jun 15
2
virt-sparsify changing the apparent-size of files
Hello,
I am curious why when using virt-sparsify the apparent-size of the file
gets reduced to the actual file size? Is there a way to get the
apparent-size left as the full size?
In the man page for virt-sparsify it has a section on
"IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to
indicate what I would expect where "ls -lh" shows the full apparent size
2016 Jun 15
2
virt-sparsify changing the apparent-size of files
Hello,
I am curious why when using virt-sparsify the apparent-size of the file
gets reduced to the actual file size? Is there a way to get the
apparent-size left as the full size?
In the man page for virt-sparsify it has a section on
"IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to
indicate what I would expect where "ls -lh" shows the full apparent size
2008 Dec 22
2
Download lustre 1.6.6
i am unable to download lustre 1.6.6 , links does seems to be broken but its
not working
--
Regards--
Rishi Pathak
Pune-Maharastra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20081222/e72e8bc2/attachment-0001.html
2006 Jun 22
1
Patch for rawlog.c
hello
The homedirectories are stored as a relative path in my userdb
One problem ocoures with rawlog:
rawloging occures only if a directory $HOME/dovecot.rawlog exist.
this is checked with lstat
for me $HOME is always "username/". This is relative to /var/mail and works.
in rawlog.c lstat should now check "username//dovecot.rawlog" which fails.
lstat can check
2016 Jun 23
2
Re: [libvirt-users] virt-sparsify changing the apparent-size of files
On Wed, Jun 22, 2016 at 05:56:09PM -0500, libvirt_users@skagitattic.com wrote:
> > Delete what you've done and start from the beginning. Describe
> > exactly how you created the guest. Use 'qemu-img info' to show the
> > format of the input file. Show precisely the virt-sparsify command
> > you are running. And use 'qemu-img info' on the output file