similar to: Debian package init scripts

Hello list, I have a replicated dovecot with two servers. People seem to get vacation responses more often then it is specified in "days: XX", depending on which dovecot instance they receive the incoming mail. Is ".dovecot.lda-dupes" replicated? The other problem is that the vacation response is coming from the wrong address depending on which field the recipient was

Dearest list, just now I migrated a pine user to dovecot. Nothing special so far, but then I saw this in my syslog and the user reported, that he got this error message: MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR Obviously this problem is related to his local filter rules: If commented out everything works like a charm. The corresponding filter rule looks for a

Hi list, I get these warnings quite frequently. Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync Is this something to worry about? Otherwise the replication works perfectly. Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum ---------------------------------------- Auf dem Huegel 69, D-53121 Bonn

I''ve been experiencing some odd behavior with puppet and checking the status of running processes. Let me see if I can explain it: I have a very simple node.js socket server I''m attempting to puppetize. It is managed through an init.d script with start, stop, status, and restart. The init.d script runs perfectly fine as any other user in the system. However, when puppet

From: Rodrigo Barbosa <rodrigob at suespammers.org> > There is nothing wrong with using X11 at runlevel 3. The only thing > that can't be present is a display manager (KDM, XDM, GDM etc). That's _exactly_ what I'm talking about. Run-level 3 starts xdm. Several Linux distros use 2 for multi-user, 3 for multi-user w/X. Run-level 2 as multi-user w/o networking or w/o NFS was

In lib/gcc_personality_v0.c, I believe the type of the exception_cleanup member of the struct _Unwind_Exception is incorrect. It has a return type of _Unwind_Reason_Code versus a return type of void as specified in http://refspecs.freestandards.org/abi-eh-1.21.html, and as can be seen in unwind.h on Linux, and OS X 10.6.x (the latter's unwind.h is under the Developer directory tree). The

Hi Jim, I didn't use any documents, but intensively looked at gcc's output. I think this document: http://refspecs.freestandards.org/elf/elfspec_ppc.pdf is the last specification of the ABI. Cheers, Nicolas Jim Laskey wrote: > Nicolas, > > Would you point me to the Linux/PPC ABI documents you are using so I > can better judge what your restrictions are? These changes

Here are the items removed when removing postfix: Nov 1 09:56:59 localhost yum[22042]: Erased: google-chrome-stable Nov 1 09:57:00 localhost yum[22042]: Erased: redhat-lsb-compat Nov 1 09:57:00 localhost yum[22042]: Erased: redhat-lsb Nov 1 09:57:01 localhost yum[22042]: Erased: redhat-lsb-graphics Nov 1 09:57:01 localhost yum[22042]: Erased: redhat-lsb-printing Nov 1 09:57:02 localhost

Hi everyone, Currently, when declaring a va_list in llvm, one only needs to do: %ap = alloca i8 * (Reference : llvm/docs/LangRef.html#int_varargs) This is OK for x86 and PPC/Darwin ABI because a va_list in these architectures is just a pointer to the stack. The va_start intrinsic just initializes where the pointer points at in the stack. I do not know how the other backends operate, but I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I have been in discussion with several other accessibility projects to work on a common API for speech synthesis and speech recognition drivers. I suggested to discuss this on a mailing list and to found a new list at freedesktop.org for this purpose. Since there are also a number of other accessibility related areas where cooperation is

On Sat, Jan 9, 2010 at 5:54 AM, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote: > If the powers at be want this, I could easily transform the source to the LLVM coding standards, and add > the necessary portable UNIX support--someone else would have to add non-UNIX support although the > System library probably helps with this. However I'm guessing the LLVM release flux of the

If the powers at be want this, I could easily transform the source to the LLVM coding standards, and add the necessary portable UNIX support--someone else would have to add non-UNIX support although the System library probably helps with this. However I'm guessing the LLVM release flux of the exception system, along with a lack of universal platform, dwarf JIT support might be a hinderance in

Hi Timo, please find attached a patch for the init script in the doc directory. * Added LSB-compliant info block (for insserv and friends) * Updated base_dir detection (for v2.0 config output) Regards, Pascal -- The trapper recommends today: decade.0932307 at localdomain.org -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot-initd_LSB_header.patch

Hi, I've recently significantly improved the automated Dovecot Debian package builder. At the beginning it only produced i386 binaries for Debian testing. A few weeks back I added a slave builder that builds packages for Debian stable. Today I have extended the slave builder with support for multiple architectures and I've added amd64 binaries to the repository. The master builder

Nicolas, Would you point me to the Linux/PPC ABI documents you are using so I can better judge what your restrictions are? These changes also have an effect on debugging and exception handling. Cheers, -- Jim On 2-Feb-07, at 08:58 AM, Nicolas Geoffray wrote: > Hi everyone, > > I have almost completed the implementation of a linux/ppc backend > in llvm. There were a few

Hello, after I have done a dist-upgrade to Squeeze, I got some nasty problem with my dovecot. When I try to establish a connection via IMAP, it doesn't react and writes the following into my logfile: 2011-02-16 15:23:49 imap-login: Info: Login: user=<thomas at XXX>, method=PLAIN, rip=84.130.16.134, lip=XX.XXX.XX.XXX, TLS 2011-02-16 14:23:49 dovecot: Fatal:

Hi there, I'm using Dovecot together with Postfix; as I understand it, there are two ways to transfer the mail from Postfix to Dovecot. 1.) by using LDA with mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" 2.) by using LMTP with mailbox_transport = lmtp:unix:private/dovecot-lmtp (currently using number 1) I'm interessted in the

I can ssh into a remote machine. I can start X on that machine with startx How do I then start firefox on that machine (from the ssh prompt) and have it display on my machine in my office. So I want to be using firefox on the remote machine but displaying the screen output from firefox in my office. Both boxes are running centos 5. how is that done? Jerry

On 5 September 2013 19:27, Bill Wendling <wendling at apple.com> wrote: > Hi Rafael, > > I've been staring at the CFI directives and have a question. Some background: I want to generate the compact unwind information using just the CFI directives. I *think* that this should be doable. The issue I'm facing right now is that I need to know how much the stack pointer was

Hi Rafael, I've been staring at the CFI directives and have a question. Some background: I want to generate the compact unwind information using just the CFI directives. I *think* that this should be doable. The issue I'm facing right now is that I need to know how much the stack pointer was adjusted. So when I have something like this: .cfi_startproc Lfunc_begin175: