Thank you Oswald,
Is this enough detail to show only one mbsync in the background on the
fcntl call that is stuck ???
eismej@eismej-u14:~$ mbsync -a
C: 0/1 B: 0/44 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0 C-c C-z
[1]+ Stopped mbsync -a
eismej@eismej-u14:~$ bg
eismej@eismej-u14:~$ ps -fux |grep mbsync
eismej 28132 0.0 0.0 23544 4648 pts/1 S 08:57 0:00 | \_ mbsync
-a
eismej@eismej-u14:~$ sudo strace -p 28132
Process 28132 attached
fcntl(4, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0} C-c
C-cProcess 28132 detached
-- John
Oswald Buddenhagen writes:
> On Thu, Sep 17, 2015 at 02:55:46PM -0400, John Eismeier wrote:
>> Thanks for your quick response Oswald. I did not find any additional
>> mbsync in the background. How would I be able to demonstrate that ?
>>
> ps fux
>
>> Does the config (.mbsyncrc) look OK? The connection does list the MS
>> exchange boxes/folders without issue ???
>>
> it looks just fine.
> and i don't even know how a bad config could cause a deadlock.
>
>> Oswald Buddenhagen writes:
>> > On Thu, Sep 17, 2015 at 09:13:53AM -0400, John Eismeier wrote:
>> >> fcntl(4, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}
>> >>
>> > that isn't helpful without context (knowing what fd 4 belongs to).
>>
> i.e. send me more of the strace log.
------------------------------------------------------------------------------
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
