* Jim Hyslop ([EMAIL PROTECTED]) wrote: > Dr. David Alan Gilbert wrote: > > 2) I could do with a better under standing of the directory locks; > > pointers? I've read the top of lock.c but it still doesn't tell me > > enough; for example there seem to be multiple lock files used - but > > then surely the creation of them isn't atomic? Or is there one lock > > file used for both reading and writing? > The locking process is explained in the manual, at > https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_2.html#SEC17
Thanks Jim for pointing me at that (I'd had a good search through the FAQ rather than the manual....). (and to Paul - apologies if I misquoted in that last email) OK; this convinces me that I don't need to worry about cvs reading my file while it is being modified. Together with the restriction of me only performing my trick if the write is entirely within a block then I feel reasonably safe. I'm going to have a crack at making this optimisation and will forward a copy here for discussion when I've done it. Dave -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \ \ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
