Re: continue w/ password and network failures
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
I do that as well, unfortunately some accounts would never be serviced.
What I've done for now is wrap some exception handling around the account
checking loop in accounts.AccountSynchronizationMixin.syncrunner, and caused
those threads to exit upon failure (I think...).
I'd prefer to have them retry later, but I haven't figured out how the
connection pooling works. The connections seem to be left in a bad state if the
previous iteration did not successfully connect.
On Wed, 10 Dec 2008, Patrick Morris wrote:
> On Wed, 10 Dec 2008, Simon P. Ditner wrote:
>> Is there an existing config option to prevent offlineimap from exiting
>> upon hitting one account with a bad password, or network connection
>> failure in non-interactive mode?
>> I'm synchronizing a number of accounts with the same process. Sometimes
>> bad account data is submitted, resulting in the program terminating
>> without visiting the other accounts.
> I just run offlineimap inside an infinite loop to restart it if
> something makes it die:
> pmorris@bakgwai ~ $ while true; do offlineimap; done