Displaying 4 results from an estimated 4 matches for "to_instance".
Did you mean:
if_instance
2019 Feb 07
2
system wakeup caused by write operations to /var/lib/dovecot/instances
...; 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?
>
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/a...
2019 Feb 02
2
system wakeup caused by write operations to /var/lib/dovecot/instances
Hi, I hope someone can help me with this.
Problem
Dovecot writes to _/var/lib/dovecot/instances_ 1 up to 3 times a day,
causing the system to wake up and disks to spin up.
Details
content of /var/lib/dovecot/instances :
1549073010 dovecot /var/run/dovecot /etc/dovecot/dovecot.conf
--> only the timestamp is changed (to current time) when dovecot writes
to this file
--> during write the
2019 Feb 07
0
system wakeup caused by write operations to /var/lib/dovecot/instances
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?
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments...
2019 Feb 07
0
system wakeup caused by write operations to /var/lib/dovecot/instances
...; 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...