Displaying 20 results from an estimated 3000 matches similar to: "Links on MainConfig wiki page not working"
2010 Aug 28
1
MainConfig for dovecot 2.0
Hey,
for dovecot 1.2 there is a very good reference page for all options.
http://wiki.dovecot.org/MainConfig
is there a reference for dovecot 2.0 in the new wiki? If not, when will
be this page online? Thanks a lot.
--
Gru?
Sascha
2009 Apr 27
2
[PATCH] Clarify rawlog example
# HG changeset patch
# User matthijs at stdin.nl
# Date 1240845142 -7200
# Branch HEAD
# Node ID 19f4b6167b426c36b7b3b38db4397f2723dc75c2
# Parent c8de2237478fc01ee46e6ec8cda41e8d3cecb68c
Clarify rawlog example.
diff -r c8de2237478f -r 19f4b6167b42 dovecot-example.conf
--- a/dovecot-example.conf Thu Apr 23 12:01:40 2009 -0400
+++ b/dovecot-example.conf Mon Apr 27 17:12:22 2009 +0200
@@ -543,6
2006 Mar 17
3
Open .ssc .S ... files in R (PR#8690)
----- Quick summary:
In the File:Open dialog, please change
"S files (*.q)"
to
"S files (*.q, *.ssc, *.S)"
and show the corresponding files (including .SSC and .s files).
----- Background
This is motivated by the following query to R-help:
>Date: Thu, 16 Mar 2006 22:44:11 -0600
>From: "xpRt.wannabe" <xprt.wannabe at gmail.com>
>Subject: [R] Is
2008 Jul 30
3
[LLVMdev] llvm-gcc builds on 32 bit linux broken
Hi all,
I'm having some trouble building llvm-gcc as of today, with and without
bootstrap.
The error I get is:
/home/kooijman/src/llvm-gcc/obj/./gcc/xgcc
-B/home/kooijman/src/llvm-gcc/obj/./gcc/
-B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/bin/
-B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/lib/ -isystem
2016 Oct 04
8
[Bug 2621] New: ControlMaster started by scp (non-ssh?) doesn't forward agent
https://bugzilla.mindrot.org/show_bug.cgi?id=2621
Bug ID: 2621
Summary: ControlMaster started by scp (non-ssh?) doesn't
forward agent
Product: Portable OpenSSH
Version: 7.3p1
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Miscellaneous
2011 Dec 12
1
Documentation clarifiction on mmap_disable
Greetings,
On http://wiki.dovecot.org/MainConfig I read:
"mmap_disable = no
Don't use mmap() at all. This is required if you store indexes to
shared filesystems (NFS or clustered filesystem). "
Does that mean:
1. mmap is required when using NFS or
2. it is required to don't use mmap at all when using NFS?
Sorry if this is obvious. Best regards.
--
*Marcio Merlone*
2012 Sep 04
1
Custom auth process in dovecot 2
Hi,
I'm trying to upgrade from dovecot-1.1.x to 2.1.7.
We have our own custom auth server process (because we want to do our own password validation and for other reasons) that listens on a UNIX domain socket and speaks the dovecot auth protocol.
In dovecot 1.1 we could configure this with
auth external {
socket connect {
master {
path = /var/run/dovecot/auth.sock
}
}
2006 Jun 12
0
Wiki's MainConfig page
Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20060612/2dcf5e53/attachment.pgp
2020 Apr 26
1
Hierarchy separator recommendation?
On 26.4.2020. 12:17, Markus Winkler wrote:
>
>> Doesn't it, in the end, all come to translation from IMAP names
>> (user,folder) to OS filesystem names within dovecot (at some
>> benchmark tests expense) ? :-)
>
> No, as there's a difference between "namespace / hierarchy" (mailbox
> name) and "layout" separators (OS filesystem).
Hi
2008 Jun 05
4
[LLVMdev] Adding DenseMap::FindAndConstruct with a default value
Hi All,
I've been fiddling around with a DenseMap to store cached copies of some
result. In short, I'm doing the following:
It = Map.find(Key)
if (It != Map.end() && It->second != Unknown)
Return It->second;
// do_stuff
return Map[Key] = Result;
However, I this requires two lookups in the hash table, which is not so nice.
Currently, there is no way to write this down so
2008 May 07
4
[LLVMdev] Missing passes
Hi,
I was evaluating all transformation passes and noticed a few things. In
particular, I found three passes in the documentation that I can't seem to
find any code for. Where these removed?
Lower GC intrinsics, for GCless code generators (-lowergc)
Correlated Expression Elimination (-cee)
Lower select instructions to branches (-lowerselect)
Additionally, I found the following passes for
2009 Jan 22
3
[LLVMdev] Leaving LLVM
Hi all,
about a month ago, I've started working on my master's thesis. Since I want to
focus on just that work, I've stopped my LLVM work for now. It is unclear
whether I will continue my work after graduation, but it seems unlikely.
I'll still keep track of LLVM from a personal interest (mostly watching the
IRC channel), but I won't have the time to track any mailing lists.
2008 May 13
2
[LLVMdev] [PATCH] Split LoopUnroll pass into mechanism and policy
Hi Dan,
please find an updated patch attached (don't forget to run the svn cp command
I posted earlier, before applying this patch).
I've incorporated all the changes we've discussed.
Gr.
Matthijs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL:
2008 Jul 10
2
[LLVMdev] Including svn version number in --version output
> I suppose to be annoyingly pedantic about it you could require a
> network connection for the build, check svn info and svn status and
> then set the version string based on whether or not there are local
> patches applied to the checkout - but that would probably fall under
> neurotic :)
Using svnversion (as the original patch does) does exactly this. It outputs
the rev
2008 Jul 21
0
[LLVMdev] Structs as first class values.
Hi Rich,
> I was thinking about my problem and thought that there might be a good
> interim solution. I would like not to clutter my front end with stuff
> that will go away. How about a pass that runs before code generation
> that changes functions returning structs to void functions with the
> return pointer first parameter?
On this topic, you should look at the
2008 Aug 23
0
[LLVMdev] Proposal : Function Notes
Hi Devang,
> All supported notes must be documented in LLVM language reference.
Does this also mean that undocumented / unsupported notes are invalid? In
particular, when I have a custom frontend and backend, using custom notes
could be a great way to communicate between those, if the LLVM IR would allow
unknown notes.
Other than that, this seems like a decent approach. As Andrew pointed out,
2008 May 21
4
[LLVMdev] MultiSource/Applications/lemon slow in JIT
Hi,
I've been toying around with the testsuite for a bit, and after recompiling
llvm-gcc a bunch of times and fixing a nasty bashism bug, I actually got it to
run and pass most tests.
When running, I noticed a very long runtime on the lemon test. At first I
suspected an infinite loop, but it turned out the test simply needed around
1000 seconds to run. Some investigation turned out that the
2008 Jul 10
3
[LLVMdev] (GEP) Index validity
Hi Evan,
> I don't think this is right. According to llvm documentation:
>
> The index types specified for the 'getelementptr' instruction depend on the
> pointer type that is being indexed into. Pointer and array types can use a
> 32-bit or 64-bit integer type but the value will always be sign extended to
> 64-bits. Structure and packed structure types require
2008 May 30
2
[LLVMdev] Troubling promotion of return value to Integer ...
Hi,
> 4) There will be 4 new function attributes:
> sign_ext_from_i8, sign_ext_from_i16
> zero_ext_from_i8, zero_ext_from_i16
> These attributes will be placed on the function CALL node by front-end to
> inform the backend about such promotions and enable optimization of
> return value. This should be sufficient for direct and indirect call.
> (syntax of
2008 Jul 08
4
[LLVMdev] Optimization passes and debug info
Hi all,
I've been fiddling around with debug info generated by clang, with the goal of
propagating line number info to our custom backend (which is not an llvm
backend, but does use llvm IR as its input).
I've created a small pass which strips all debug info except for stop points,
which are currently the only things we're interested in. Leaving only stop
points in actually works