system wakeup caused by write operations to /var/lib/dovecot/instances
ruben at mrbrklyn.com
Thu Feb 7 20:26:49 EET 2019
On Thu, Feb 07, 2019 at 05:10:04PM +0100, Tijl via dovecot wrote:
> Hi Timo,
> Thank you very much for replying with an instant solution!
> Suggestion for future release: a setting in the configuration to
> enable/disable the automatic instance_update_now action and/or set the
> timeout by the user.
> In the meanwhile I can use the recompiled version with this code change.
> Problem solved for me.
> Timo Sirainen schreef op 2019-02-07 15:59:
> > On 2 Feb 2019, at 6.44, Tijl <dovecot at odie.be> wrote:
> >> How can dovecot be run without writing to /var/lib/dovecot/instances everyday? Is there a configuration setting for this?
Postfix can do this without that added infrastructure.
> > You'd need to patch src/master/main.c instance_update_now() to remove:
> > to_instance = timeout_add((3600 * 12 + i_rand_limit(60 * 30)) * 1000,
> > instance_update_now, list);
> > I'm not quite sure why I wrote such code to update it continuously.
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive
http://www.coinhangout.com - coins!
Being so tracked is for FARM ANIMALS and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013
More information about the dovecot