[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible bug -- how to trace the dead-lock?
From: |
Ole Tange |
Subject: |
Re: Possible bug -- how to trace the dead-lock? |
Date: |
Mon, 20 Dec 2010 11:17:28 +0100 |
On Mon, Dec 20, 2010 at 8:34 AM, Maciej Pilichowski
<pilichowski.maciej@gmail.com> wrote:
>> -vv -D will give you some debugging information.
>
> Hmm, they are printing info to STDOUT and it interferes with the output of
> the processing (small wish: could you add optional parameter, like
> -vv=filename and/or -D=filename meaning the output would be directed to a
> file?).
You can redirect your program's output:
seq 1 10 | parallel -vv -D '(echo {};echo bar{}) >/tmp/output{}'
> However, I spotted dead lock again -- one of the files was not transferred
> to the remote computer, and parallel was stuck at such point (transferring
> it).
:
> Does it mean it is rsync fault?
It would explain the randomness of the lockups.
/Ole