On 2013/08/22 12:01, Landry Breuil wrote: > On Thu, Aug 22, 2013 at 10:39:54AM +0200, Renaud Allard wrote: > > Hello, > > > > I upgraded one of my machines to OpenBSD 5.4-current containing the > > 64bits time_t change. And I noticed that exim was giving a 4XX error > > to every mail because it was too busy. So I commented > > smtp_load_reserve in the configuration file and it now works just > > fine. So it seems this parameter is not interpreted correctly after > > the time_t change. > > LOTS of ports will have runtime issues after the time_t bump, and will > require manual fiddling to remove/purge caches, reset indexes, reindex > databases, etc... > > - mutt header caches > - dovecot indexes > - etc....
Mutt is OK as of the current port (mutt-1.5.21p4v0). I have not had any problems with Dovecot using mdbox on amd64 over the 64-bit time_t bump - do not zap your indexes/caches blindly especially for the dbox formats. If anyone does run into problems with Dovecot please give full information, I think it highly likely that upstream would treat it as a bug if this did happen. Also not had problems with MySQL. I would be interested to hear if anyone takes an openldap box over the bump to find whether or not that works OK :)
