RE: CVS list files in repository which are currently in checked out status

[Rupa Bholanath Lahiri]

Thank you for your valuable inputs.

Regards,
Rupa

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Mark D. Baushke
Sent: Monday, August 31, 2009 1:18 PM
To: Rupa Bholanath Lahiri
Cc: Arthur Barrett; Mark Risman; Todd Denniston; address@hidden
Subject: Re: CVS list files in repository which are currently in checked out 
status 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rupa Bholanath Lahiri <address@hidden> wrote:

> On a Unix box, through any command can we identify which are all the
> folders being used as working copy?

Assuming edit commands have been done, checking out your own tree and
doing a 'cvs editors' should give you a hint about the path of such a
checkout on a given machine. Of course, if you are using some kind of
NetApp or clustered file system, it is possible that you will find many
of the repositories that have been checked out into the working copy at
one time or other and not been deleted.

If you are able to afford the time to run a 'find' command across all of
your diskspace, then something which looks for the CVS/Root file in the
filesystems you hae avaialable would let you try running 'cvs editors'
commands on each filesystem.

The things to consider is that files and directories on checkout might
be movied or copied or cloned. There is no easy way to determine if a
mount point is consistent across reboots... all of which makes it
problematic to be absolutely certain you will be able to identify the
set of all working copies which have been created for a given set of
checked out modules.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFKm4AWCg7APGsDnFERArUOAJ9kDvc/HHCcCZe9Aijzx+bD+mTUWwCg86sC
TTKr4egg6Defj2Tq7gbNrV0=
=gDbg
-----END PGP SIGNATURE-----