On Mon, Nov 19, 2012 at 03:03:47PM -0500, Dave Abrahams wrote:
> on Mon Nov 19 2012, Oswald Buddenhagen wrote:
> > will wait for them forever until the connection is reset for some
> > reason.
>
> I don't understand what "reset for some reason" actually means. The
> computer does re-connect to
On Mon, Nov 19, 2012 at 03:03:47PM -0500, Dave Abrahams wrote:
>
> on Mon Nov 19 2012, Oswald Buddenhagen wrote:
>
> > On Mon, Nov 19, 2012 at 09:35:26AM -0500, Dave Abrahams wrote:
> >> One thing I notice sometimes is that after I've suspended and woken my
> >> computer an mbsync job will get "
on Mon Nov 19 2012, Oswald Buddenhagen wrote:
> On Mon, Nov 19, 2012 at 09:35:26AM -0500, Dave Abrahams wrote:
>> One thing I notice sometimes is that after I've suspended and woken my
>> computer an mbsync job will get "stuck," neither exiting or seeming to
>> make any forward progress. Is the
On Mon, Nov 19, 2012 at 09:35:26AM -0500, Dave Abrahams wrote:
> One thing I notice sometimes is that after I've suspended and woken my
> computer an mbsync job will get "stuck," neither exiting or seeming to
> make any forward progress. Is there a cure for this other than
> monitoring and explici
on Thu Nov 15 2012, Dave Abrahams wrote:
> In case anyone cares, I wrote a Python script to monitor a remote
> mailbox with IDLE, issue periodic synchronizations with mbsync, and
> notify the user of incoming messages:
>
>
> https://github.com/dabrahams/local-dovecot-starter-kit/blob/master/s
One thing I notice sometimes is that after I've suspended and woken my
computer an mbsync job will get "stuck," neither exiting or seeming to
make any forward progress. Is there a cure for this other than
monitoring and explicitly killing the job?
Thanks,
--
Dave Abrahams
BoostPro Computing
