search for: deinitialize

I'm trying to understand autoexpunge, but the documentation is just not clear. Hopefully, someone can clear up a few questions. http://wiki.dovecot.org/MailboxSettings says the following: autoexpunge=<time>: (v2.2.20+) Automatically at user deinitialization expunge all mails in this mailbox whose saved-timestamp is older than <time> (e.g. autoexpunge=30d). This removes the

...), since python 2.3 doesnt support this method. - allow user to press ''q'' to quit pygrub - corretly handle timeout feature - fix bug on fill_entries (incorrect check & display menu items) - incorrect check on boot entry (idx variable) - remove abundant checking on disk image - deinitialize curses before quitting. - fix few typos Signed-off-by: Nguyen Anh Quynh <aquynh@gmail.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Thanks Philon, I did read the extra bullets, as indicated in my email below. But your "When the user quits and thus closes his mailbox/connection" is more clear than "after the client is already disconnected", since the latter is really anytime, rather than at the time they quit. I can guess that the bulletin about LMTP similarly means at the end of each time LMTP delivers

...ing of all symbols / resources to the // containing JITDylib's tracker. void detach(); }; I'm hoping that usage will look like: LLJIT J = LLJITBuilder().create(); // No tracker specified. Resources tracked by the containing // JITDylib's tracker, and freed when the JITDylib is // deinitialized. ExitOnErr(J.addIRModule(sdt::move(UntrackedModule))); // Explicitly specify tracker. Module symbols can be // - materialized by calling T->emit(); // - removed by calling T->remove(); // - transfered to the JITDylib by calling T->release(); auto T = std::make_unique<ResourceTracke...

Hello *, I'm running dovecot 1.0.10 on a Fedora 6 with this configuration # 1.0.10: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/dovecot/etc/mailbox.pem ssl_key_file: /usr/local/dovecot/etc/mailbox.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default):

...0 at 3:29 AM Lang Hames <lhames at gmail.com> wrote: > > Hi Hans, > > Apologies if I got here too late, but just in case I didn't here are some JIT release notes for 11.0.0: > > - LLJIT now supports execution of static inits / deinits via the LLJIT::initialize and LLJIT::deinitialize methods > - Static libraries can now be added to a JITDylib using the StaticLibraryDefinitionGenerator class > - A C API has been added for OrcV2 (llvm-project/llvm/include/llvm-c/Orc.h) > - Several OrcV2 example projects have been added to llvm-project/llvm/examples/OrcV2Examples > - M...

Thanks! Committed in 158581772fc8f3d6c601ceba14a08285e46cb7e9 On Tue, Sep 15, 2020 at 4:23 PM Ahsan Saghir <saghir.ibm at gmail.com> wrote: > > Hi Hans, > Here are the PowerPC release notes for 11.0.0: > > Optimization: > > Improved Loop Unroll-and-Jam legality checks, allowing it to handle more than two level loop nests > Improved Loop Unroll to be able

Greetings, recently I've been writing a database driver module for Dovecot to use SQLite. It's mostly for my own use, but I do recall other people have asked for this. Firstly - Timo, I grow to love your work more and more every day. :) I have not had any trouble figuring out what is needed of the driver, even without any API documentation. However, the one part of the driver

mail1 dovecot: imap(smith at willcapmanagement.com): Timeout leak: 0x807fad0 Can anyone give me a heads up on what might cause the above message? I am working on polishing a plugin and it continues to throw this error with no seeming consequences. -David

Full_Name: R Embedder Version: 2.7.2 OS: win XP SP 2 Submission from: (NULL) (83.25.35.249) I'm having problems using embedded R. I try to adapt examples from "tests/Embedding/". Everything works fine except when I try to reinitialize R for the second time in the same program. I need to reinitialize correctly because my code is some kind of .dll plugin to an external application.

Hello Dovecot users, The new Dovecot v2.0.8 release has a few changes that prompted changes in Pigeonhole as well. This means that a new release of Pigeonhole is also necessary, because otherwise things will not compile anymore. Apart from a few rather minor bugfixes, some of which originate in Dovecot, one TODO item has finally been resolved: the reject action uses the LDA mail reject API,

Hello Dovecot users, The new Dovecot v2.0.8 release has a few changes that prompted changes in Pigeonhole as well. This means that a new release of Pigeonhole is also necessary, because otherwise things will not compile anymore. Apart from a few rather minor bugfixes, some of which originate in Dovecot, one TODO item has finally been resolved: the reject action uses the LDA mail reject API,

...dir instead of readdir_r to avoid build warnings libdrm: gralloc_handle.h: Fix build issue with Android Marek Olšák (1): Revert "amdgpu:support 16 ibs per submit for PAL/SRIOV" Matt Atwood (1): Intel: Add a Kaby Lake PCI ID Michel Dänzer (1): amdgpu: Deinitialize vamgr_high{,_32} Paulo Zanoni (1): intel: add support for ICL 11 Qiang Yu (1): amdgpu:support 16 ibs per submit for PAL/SRIOV Rex Zhu (1): headers: sync up amdgpu_drm.h with drm-next Rob Clark (2): freedreno: add fd_pipe refcounting bump version for...

On 04/20/2015 05:12 PM, Laine Stump wrote: > On 04/20/2015 08:45 PM, Matthew Schumacher wrote: >> List, >> >> I was under the impression that I could restart libvirtd without it >> destroying my VMs, but am not finding that to be true. > If not, then something is wrong. > Here are the logs from the vm: 2015-04-20 23:50:20.387+0000: shutting down qemu:

Hello Dovecot users, Now that Dovecot v2.2.6 is released, I can release a new Pigeonhole. Due to the SO_REUSEPORT changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. I also made a new release for Dovecot v2.1.17 that includes most of these fixes and some older ones. A word of warning for people using doveadm

Hello Dovecot users, Now that Dovecot v2.2.6 is released, I can release a new Pigeonhole. Due to the SO_REUSEPORT changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. I also made a new release for Dovecot v2.1.17 that includes most of these fixes and some older ones. A word of warning for people using doveadm

I'm a new dovecot user, just began using it last week. I switched from courier because my research showed that Dovecot did indexes, and allows me to store them anywhere I chose. I did this, and it fixed some severe disk IO issues that my server had. (25k horde only webmail install using imap proxy). I'm using quotas, and by default had it set to 'dirsize'. my postfix is already

On 04/20/2015 09:28 PM, Matthew Schumacher wrote: > > On 04/20/2015 05:12 PM, Laine Stump wrote: >> On 04/20/2015 08:45 PM, Matthew Schumacher wrote: >>> List, >>> >>> I was under the impression that I could restart libvirtd without it >>> destroying my VMs, but am not finding that to be true. >> If not, then something is wrong. >> >

List, I was under the impression that I could restart libvirtd without it destroying my VMs, but am not finding that to be true. When I killall libvirtd then my VM's keep running, but then when I start libvirtd it calls qemuDomainObjEndJob:1542 : Stopping job: modify (async=none vm=0x7fb8cc0d8510 name=test) and my domain gets whacked. Any way to disable this behavior? Also, while I'm

...es, + client->deleted_count, + client->expunged_count); +} + +void client_destroy(struct client *client, const char *reason) { int ret; + if (reason != NULL) + i_info("%s %s", reason, client_stats(client)); + if (client->command_pending) { /* try to deinitialize the command */ i_stream_close(client->input); @@ -88,8 +100,11 @@ io_loop_stop(ioloop); } -void client_disconnect(struct client *client) +void client_disconnect(struct client *client, const char *reason) { + if (reason != NULL) + i_info("%s %s", reason, client_stats(client...