Re: BUG?: Dsync over piped process (DSYNC_RUN_TYPE_CMD): EPIPE if X (done) is received in another write after F (finish)

Hi Timo, The below solved the problem for me as far as I can tell I was getting a EPIPE about 1:30 dsync runs over the socket. I have received 0 in 1 runs with this change. https://github.com/dovecot/core/pull/10 You know the code much better then

Re: BUG?: Dsync over piped process (DSYNC_RUN_TYPE_CMD): EPIPE if X (done) is received in another write after F (finish)

On 19 May 2016, at 03:54, J. Nick Koston wrote: > > Hi, > > It appears that dsync closes the file handle once it gets the F (finish) > response even if it hasn’t received the X (done) response. > If the X (done) response gets delivered in another write this will generate > EPIPE in the connec

BUG?: Dsync over piped process (DSYNC_RUN_TYPE_CMD): EPIPE if X (done) is received in another write after F (finish)

Hi, It appears that dsync closes the file handle once it gets the F (finish) response even if it hasn’t received the X (done) response. If the X (done) response gets delivered in another write this will generate EPIPE in the connected process. This is much easier to replicate over SSL, however