-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Pfeiffer <[EMAIL PROTECTED]> writes:
> Great info from everyone! Thank you - > Have one quick question right now, more comments later - and Mark, I'll > get the problem with the current version of Eclipse and any cvs version of > 1.11.7 and higher out as soon as I can. Thanks. Note that it might have to go to the Eclipse folks too. > As far as setting this LockDir to something like /tmp/CVSLockDir: > > I know the manual references LockDir to point to an in-file memory system. > In our case, as a refresher, our repository is prod. level NFS mounted on > a dedicated NetApp disk and we have proven that in our case, this is much > faster. So: > 1) Would it still be advisable to try writing lock files to the local > /tmp? Be careful that you do not have any symbolic links anywhere in your repository and that you do not have any processes tha 'clean up' files and/or directories out of /tmp and you may indeed find it helps. > 2) Could switching LockDir so that lock files are written to the local > /tmp increase load on the local machine and increase our problem, since > that's where our problems lie? It will increase the space used out of /tmp, but should not increase the load on the machine. > 3) Or, would it be feasble to have LockDir point to a file across NFS, but > outside of the repository? Of course then, we'd be are increasing NFS > traffic. Feasable? Yes. However, I don't see the point in this change unless you want to alter the permissions of the LockDir or something. Using LockDir is runs thru a slightly more complicated code path than not using it, so all other things being equal using it will slow you down. -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/oAsU3x41pRYZE/gRAuVzAJ9/OsfcXHQQ7fHcU4iwbW6W4zrM7gCguqJA C9OnbHiEylh86iNzYIbZ1QQ= =P1l2 -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs