Oswald,
Oh, this is very interesting! I didn't know that mbsync locked against
other processes. I have just been using lockrun all this time.
Nice to know that I don't have to disable my cronjob when I debug. =)
Regards,
Ram Raghunathan
On Wed, May 13, 2015 at 3:19 AM, Oswald Buddenhagen
wrote
* Oswald Buddenhagen [2015-05-13 03:19]:
> On Tue, May 12, 2015 at 05:22:31PM -0400, Peter P. wrote:
> > Is there an inherent danger in having two mbsyncs do their work at the
> > same time, could they somehow conflict?
> >
> no. you'll just get messages about locked mailboxes.
Thank you Oswald,
Oswald Buddenhagen writes:
> On Tue, May 12, 2015 at 03:51:06PM -0400, Eric Abrahamsen wrote:
>> I have migrated (yet again) to another computer, and since I had
>> pretty good luck last time I did this, I just rsync'd the message
>> directories and ~/.mbsync over onto the new machine directly.
>
On Tue, May 12, 2015 at 05:22:31PM -0400, Peter P. wrote:
> Is there an inherent danger in having two mbsyncs do their work at the
> same time, could they somehow conflict?
>
no. you'll just get messages about locked mailboxes.
On Tue, May 12, 2015 at 09:11:22PM +0100, [email protected] wrote:
> I have a (possibly silly) idea for my set-up that basically involves mbsync
> running continuously as a daemon, [...]
>
> a) are there existing tools available to do this? (I do not have shell
> access
> to the remote se
