> here i disagree.
>
> 1. if we copy a file as its downloading - we want to get the rest of the file
> that was appended to after the copy began, if we can.
> 2. try this with cp. cp behaves like efm. if you're telling me this is a
> security issue.. then it's a security issue in cp too.. and been
On Mon, 23 Jul 2012 10:15:35 +0200 rustyBSD said:
> Hi,
> I was told that I have to explain race conditions I found.
>
> I. Copy file bytes
> It concerns 'e_fm_op.c.diff1'. When copying a file, the dest
> file is written with bytes read from source file. It only stops
> when we are at the end of
Hi,
I was told that I have to explain race conditions I found.
I. Copy file bytes
It concerns 'e_fm_op.c.diff1'. When copying a file, the dest
file is written with bytes read from source file. It only stops
when we are at the end of the source file. The problem
is that you just have to launch a pr
