[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: symbolically linked module root

From: Derek Robert Price
Subject: Re: symbolically linked module root
Date: Fri, 31 Oct 2003 08:00:58 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1

Hash: SHA1

Kevin Layer wrote:

|Mark D. Baushke <address@hidden> wrote:
|>>Kevin Layer <address@hidden> writes:
|>>Because I have a large number of checkouts of `modc', I can't just
|>>move it to a new repository.  I'm thinking of creating a new
|>>repository directory like this:
|>>  CVSROOT -> ../cvsroot/CVSROOT
|>>  modc -> ../cvsroot/modc
|>>and having them use cvsroot2 as their repository.
|>>Is this safe?
|>>Not really... cvs does not really understand symbolic links and is
|>>potentially going to give you problems with locking the directories
|>>in that manner.
|We use cvs in server mode, and if all the symlinks are links to files
|on the same filesystem, I don't see why that wouldn't work.  If
|course, if NFS was involved, I'd completely agree with you.

Your diagram above may coincidentally work, even with LockDir specified,
because you have two cvsroots with the "same" directory structure, the
same CVSROOT (which thus must specify the same LockDir) and the
"equivalent" modules are in the parallel locations with the same names.

When "all the symlinks are links to file on the same system" as you say,
things can still go wrong because CVS uses directory locks to change
files and does not acknowledge symlinks.  Thus, if you have a link like

~    /cvsroot2/modc/file1,v -> ../../cvsroot/modc/file1,v

Then a user accessing file1,v via cvsroot2 will leave locks in
/cvsroot2/modc and a user accessing file1,v via cvsroot will leave locks
in /cvsroot/modc and both could then try to write the same file1,v at
the same time, both thinking they have a write lock, and one or the
other set of changes could be overwritten.


- --
~                *8^)

Email: address@hidden

Get CVS support at <>!
- --
Hamlet:  To be or not to be - that is the question;
Whether 'tis nobler in the mind to suffer
The slings and arrows of outrageous fortune
Or to take arms against a sea of troubles
And by opposing end them.  To die, to sleep -
No more - and by a sleep to say we end
The heartache and the thousand natural shocks
That flesh is heir to.  'Tis a consummation
Devoutly to be wished.  To die, to sleep -
To sleep - perchance to dream.  Ay, there's the rub.
For in that sleep of death what dreams may come
When we have shuffled off this mortal coil
Must give us pause.  There's the respect
That makes calamity of so long life.
For who would bear the whips and scorns of time,
Th' oppressor's wrong, the proud man's contumely,
The pangs of despised love, the law's delay,
The insolence of office, and the spurns
That patient merit of the unworthy takes,
When he himself might his quietus make
With a bare bodkin?  Who would fardels bear,
To grunt and sweat under a weary life,
But that the dread of something after death,
The undiscovered country, from whose bourn
No traveller returns, puzzles the will,
And makes us rather bear those ills we have
Than fly to others we know not of?
Thus conscience does make cowards of us all;
And thus the native hue of resolution
Is sicklied o'er with the pale cast of thought,
And enterprises of great pitch and moment
With this regard their currents turn awry
And lose the name of action.  Soft you now,
The fair Ophelia! - Nymph, in thy orisons
Be all my sins remembered.

~     - Hamlet, Act III, Scene 1, Lines 56-89
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape -


reply via email to

[Prev in Thread] Current Thread [Next in Thread]