Eitle J�rgen wrote:
>
> Hi,
> ok here it comes. If I do the same as I described in the last mail, but this
> time I stop WinCVS and restart it, then it works. Which means, that somehow
> (win)CVS is keeping the file open. But how could this be?
> In fact when I do the whole thing from the command line it works out ok. It
> did'nt do it before probably beacause of another problem. So the culprit
> seems to be winCVS keeping the file open.
WinCVS uses a DLL, rather than simply calling CVS.EXE, so until WinCVS is terminated,
and dangling
open files are still considered open by the system.
What appears to be happing is that the locking code is leaving files open. However I
haven't been able
to find out how/why yet.
Tony
--
#define QUESTION ((bb) || !(bb)) - Shakespeare
[EMAIL PROTECTED]
