I'm not quite sure if this is a bug report or a feature requet.
One of my customer reported the following problem with texify:
He tried to compile a very large pdf (32MB) with a lot of images. When running texify --pdf the first compilation in the texify cycle worked fine:
Output written on xxx.pdf (234 pages, 32206173 bytes).
But the second failed:
! I can't write on file `xxx.pdf'.
There was no problem if "draft" was used (which makes the pdf much smaller) or if pdflatex was called directly. Imho it is a timing problem. The pdf hasn't been released yet before texify tried to start the second pdflatex compilation.
Would it be possible that texify either checks that the pdf is not locked before starting the second cycle or at least offers an option "wait=xx" to put some time between the compilations?