, but the software
in question will only work in one place (don't ask).
The problem is that each time I check something in, CVS changes the
file's permissions to 755, so that my teammates can't change it.
How do you control this behavior?
I believe this behavior is also responsible for occasional up-to-date
time I check something in, CVS changes the
file's permissions to 755, so that my teammates can't change it.
How do you control this behavior?
I believe this behavior is also responsible for occasional up-to-date
check failed messages. Since there is only one developer tree, there
are no other
[EMAIL PROTECTED] wrote:
The problem is that each time I check something in, CVS changes the
file's permissions to 755, so that my teammates can't change it.
How do you control this behavior?
use directories setgid bit to ensure files checked in will stay
group-writable.
--
All warranty
Folks,
I'm COMPLETELY new to CVS, and am assisting the CVS
administrator configure the tool on a Linux server. I've got a cursory
understanding of the CVSROOT directory structure; my question is one of
permissions. I realize that this has probably been addressed in the past, but
reading
Michaelis, Daniel writes:
This is a multi-part message in MIME format.Please do not send MIME and/or
HTML encrypted messages to the list.
Plain text only, PLEASE!
SNIP
there doesn't seem to be anything that prevents User1
from going into the ProjectDir1/bin directory and
removing file2
that someone had mucked with
permissions on the cvs executable, because I mistakenly assumed that it
would take advantage of the setuid capability in a Unix environment, and
manage reading/writing on its own.
The errors that I was getting were undoubtedly due to the setuid that I
used; when I
Michaelis, Daniel wrote:
Todd,
Thanks for the answers.
Regarding your comments, my intent is less to provide a secure environment
(we don't expose cvs outside the internal network), and I'm not terribly
worried about malicious destruction of data; I'm much more concerned with
the
I had suggested one group per project, but that has its own set of
difficulties:
- Each user has a default group that is used to set permissions on new
files
(I know there's supposed to be a way to configure the O/S to inherit
permissions from the parent, but our sysadmin either hasn't
you VERY little.
I had suggested one group per project, but that has its own set of
difficulties:
- Each user has a default group that is used to set permissions on new files
(I know there's supposed to be a way to configure the O/S to inherit
permissions from the parent, but our sysadmin either
Title: Remote repository permissions best practices
Ive hacked my way through setting up a few CVS repositories in the past, but Ive always struggled with getting the user/group ownership and file permissions correct. I always seem to end up with a setup where the users cant access
Howard, Les wrote:
I've hacked my way through setting up a few CVS repositories in the past,
but I've always struggled with getting the user/group ownership and file
permissions correct. I always seem to end up with a setup where the users
can't access the files that other users have
Todd Denniston wrote:
Howard, Les wrote:
I've hacked my way through setting up a few CVS repositories in the past,
but I've always struggled with getting the user/group ownership and file
permissions correct. I always seem to end up with a setup where the users
can't access the files
[top posting as a courtesy for Doug]
-R Recursively change permissions of directories and
their contents.
Its the their contents part that is the problem, you only need and want to
change the ownership and permissions on the directories.
The files should be read only, and we
Todd Denniston wrote:
1) all the users who need write access to the repository
should be in the
same UNIX group.
Doesn't this effectively negate any benefit of using groups? For example, in
our setup we want full-time staff to have general access to most of the
repository, and co-op students
Jim.Hyslop wrote:
Todd Denniston wrote:
1) all the users who need write access to the repository
should be in the
same UNIX group.
Doesn't this effectively negate any benefit of using groups? For example, in
our setup we want full-time staff to have general access to most of the
I'm getting files from checkout and update commands that have no file
permissions at all... The directories show the directory bit set, but
files have NO bits set for permissions.
What could cause this? We're using CVS 1.11.19, on a window platform,
and using cygwin for the command line
Dave Bartmess wrote:
I'm getting files from checkout and update commands that have no file
permissions at all... The directories show the directory bit set, but
files have NO bits set for permissions.
What could cause this? We're using CVS 1.11.19, on a window platform,
and using cygwin
, Todd Denniston wrote:
Dave Bartmess wrote:
I'm getting files from checkout and update commands that have no file
permissions at all... The directories show the directory bit set, but
files have NO bits set for permissions.
What could cause this? We're using CVS 1.11.19, on a window
How do you do to restrict the level of access to the
modules of the project?
For exemple all users have permission to access the
module templates, but only Jon have permission to
access the module system´s test.
Yahoo! Mail - Com 250MB de espaço. Abra sua
=?iso-8859-1?q?Gleidson=20S=E1=20Barreto?= writes:
How do you do to restrict the level of access to the
modules of the project?
https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_2.html#SEC13
-Larry Jones
I'm not a vegetarian! I'm a dessertarian. -- Calvin
simple restrictions based on
directories, the easiest way is to use operating system permissions and
ACLs.
For more complex permissions, have a look at the cvs_acls script in the
contrib directory (part of the source code distribution, available at
www.cvshome.org). Note that this approach only
Hey folks,
I was unsuccessfully checking several CVS documentation for user
permissions in CVS.
What we want to do is give explicit read permissions to users for
files/directories. By default a user should have no read or write access
to files/directories unless we specify that they do. I
Matthias Friebe wrote:
Hey folks,
I was unsuccessfully checking several CVS documentation for user
permissions in CVS.
What we want to do is give explicit read permissions to users for
files/directories. By default a user should have no read or write access
to files/directories unless
Matthias Friebe writes:
I was unsuccessfully checking several CVS documentation for user
permissions in CVS.
https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_2.html#SEC13
-Larry Jones
How am I supposed to learn surgery if I can't dissect anything? -- Calvin
Matthias Friebe [EMAIL PROTECTED] wrote:
I was unsuccessfully checking several CVS documentation for user
permissions in CVS.
Larry already pointed you to the docs on cvshome.org, so start there.
Note the bit about LockDir in CVSROOT/config, which is necessary
if you plan to give read-only
physical permisions to proyects,
so I have one proyect proyect_1 that
belongs to user admincvs and group cvs with file permissions (r
w x r - x - - -), but when I try to get the
proyect from the repository to the websphere studio, I get the
following mistake:
El
Martinez Pla,Jose Antonio writes:
Other chance I´ve try is to give physical permisions to proyects,
so I have one proyect proyect_1 that
belongs to user admincvs and group cvs with file permissions (r
w x r - x - - -), but when I try to get the
proyect from the repository
Rogier wrote at 15 Dec 2004 01:40:55 and again at 15 Dec 2004 02:03:07:
Rogier, please note RFC 1855[1] , section 2.1.1, item 12 (if I counted
correctly)
Remember that people with whom you communicate are located across the
globe. If you send a message to which you want an immediate response,
SEE a dir or file at all? So when he checks out or updates, he
only gets the stuff I want him to get, and no errors about dirs that he
can't access?
Thanks a lot,
Rogier
(*) this is because I don't want to mess with system-dependant user
rights or NTFS file permissions. I want to control file
SEE a dir or file at all? So when he checks out or updates, he
only gets the stuff I want him to get, and no errors about dirs that he
can't access?
Thanks a lot,
Rogier
(*) this is because I don't want to mess with system-dependant user
rights or NTFS file permissions. I want to control file
Todd Denniston wrote:
Rogier wrote at 15 Dec 2004 01:40:55 and again at 15 Dec 2004
02:03:07:
Rogier, please note
(...)
[1] http://www.dtcc.edu/cs/rfc1855.html
[2] http://www.catb.org/~esr/faqs/smart-questions.html#id3002966
--
Todd Denniston
Uhm, have I been double-posting, or what is
Rogier wrote:
Todd Denniston wrote:
Rogier wrote at 15 Dec 2004 01:40:55 and again at 15 Dec 2004
02:03:07:
Rogier, please note
(...)
[1] http://www.dtcc.edu/cs/rfc1855.html
[2] http://www.catb.org/~esr/faqs/smart-questions.html#id3002966
--
Todd Denniston
Uhm, have I been
Somehow, one file in my project emerges from CVS with write access OFF.
When I look in the repository, this file and several others have these
permissions:
-r--r--r--1 mhusby sequence13990 Nov 2 00:49 mavenant.xml,v
-r--r--r--1 mhusby sequence38109 Nov 2 00:49 maven.xml
Hello, maybe this already has been discussed. What I'm looking for is
how to set permissions on specific branch names, I mean, make some
branches read-only. This is necessery because it happens that WinCvs
users perform commits where they should not. I'm using RedHat Linux as
repository server
PROTECTED]
Subject: Permissions on Branchs
Hello, maybe this already has been discussed. What I'm looking for is
how to set permissions on specific branch names, I mean, make some
branches read-only. This is necessery because it happens that WinCvs
users perform commits where they should not. I'm
Paola Attadio wrote:
Hello, maybe this already has been discussed. What I'm looking for is
how to set permissions on specific branch names, I mean, make some
branches read-only. This is necessery because it happens that WinCvs
users perform commits where they should not. I'm using RedHat
looking for is
how to set permissions on specific branch names, I mean, make some
branches read-only. This is necessery because it happens that WinCvs
users perform commits where they should not. I'm using RedHat Linux as
repository server with WinCVS clients.
I believe this can be scripted
Hi,
I tried to change the permissions of one directory in my checkout and coomit
it to cvs.
The answer was, that I can't add the directory because the directory already
exist.
In the cederquist cvs manual is pointed out that I need to clear the whole
directory
before it could be deleted. Ok, I do
Hi all,
I do have a question regarding file permissions. After I commit a file
or make an update the file permissions is read-only for all
owner/group/others in the local working directory. Is there a way to
control this permissions? I want CVS to keep permission 644 after I
commit the file
I believe CVSUMASK will do what you want. It works
just like the Unix umask.
-chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of marius trestioreanu
Sent: Friday, September 03, 2004 4:28 AM
To: [EMAIL PROTECTED]
Subject: project files permissions
, September 03, 2004 4:28 AM
To: [EMAIL PROTECTED]
Subject: project files permissions
Hi all,
I do have a question regarding file permissions. After I commit a file
or make an update the file permissions is read-only for all
owner/group/others in the local working directory
the
error - Unable to create #cvs.lock, Permission denied.
The reason is that a module or a subdirectory thereof will be
created by the permission set of the permission who created it. Though
the directory permissions are 775 and all the users are in the group
cvs, but still the problem
Gaurav Vaish wrote:
No, all are with 775. But still, cvs (client) reports the error about
permission denied.
If subdirectories are being created with more restrictive permissions,
it means that you forgot to turn on the setgid bit in their
parent's permissions.
I think you will find
/cvspro
Regards,
Arthur Barrett
-Original Message-
From: [EMAIL PROTECTED] on behalf of Gaurav Vaish
Sent: Tue 8/17/2004 3:46 PM
To: [EMAIL PROTECTED]
Cc:
Subject:CVS Permissions
Hi,
I setup CVS on a Linux machine and I'm facing problem
.
Regards,
Arthur Barrett
-Original Message-
From: Gaurav Vaish [mailto:[EMAIL PROTECTED]
Sent: Wed 8/18/2004 4:25 PM
To: Arthur Barrett
Cc: [EMAIL PROTECTED]
Subject:Re: CVS Permissions
So, does that mean the permission issue is a standard problem?
I would be surprised
PROTECTED]
Subject:Re: CVS Permissions
So, does that mean the permission issue is a standard problem?
I would be surprised then! There must be someway to overcome this in
the default CVS server itself, rather than going for 3rd party
implementation of the CVS, like CVSNT you mentioned
it. Though
the directory permissions are 775 and all the users are in the group
cvs, but still the problem persists.
I'm lost. 775 is the correct permission. Are you saying all the
directories have that permission and you still have problems ?
If subdirectories are being created with more restrictive
Vaish
Sent: Tue 8/17/2004 3:46 PM
To: [EMAIL PROTECTED]
Cc:
Subject:CVS Permissions
Hi,
I setup CVS on a Linux machine and I'm facing problem with permissions.
I am using pserver to connect and more often than not, I get the
error - Unable to create #cvs.lock, Permission
Hi,
I setup CVS on a Linux machine and I'm facing problem with permissions.
I am using pserver to connect and more often than not, I get the
error - Unable to create #cvs.lock, Permission denied.
The reason is that a module or a subdirectory thereof will be
created by the permission set
At 12:34 AM 8/5/2004, Mark D. Baushke wrote:
Failing that, have a crontab job run thru the tree
every so often and change the group for you.
I suppose another way around it would be to run
the cvs executable on your server as a set-gid
process. I don't recommend it unless you know what
you are
Todd Denniston wrote:
directories should be drwxrwsr-x or drwxr-sr-x and should be owned by the
correct user and group.
That fixed my problem, thank you.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Joseph Shraibman writes [quoting me]:
https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_2.html#SEC13
Setting LockDir helps, but that url is wrong.
No, it's not. The entire section is relevant to what you're trying to
do and the third paragraph explicitly talks about the need for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joseph Shraibman [EMAIL PROTECTED] writes:
Joseph Shraibman [EMAIL PROTECTED] writes:
... Now the problem is that checkouts of
certain files are failing because Permission
denied. These files are owned by a group that
the user is a member
and/or world?
the files should either be -r--r--r-- or -r--r-.
directories should be drwxrwsr-x or drwxr-sr-x and should be owned by the
correct user and group.
see 2.2.2 File permissions [1], and I would suggest reading all of 2.2
How data is stored in the repository [2]
the default group
Joseph Shraibman writes:
I attempted to limit access to parts of my module by using group
permissions. The problem is than when the checkout reaches a directory
it can't read, it fails right away and doesn't go on to other directories.
You need to use LockDir= in your CVSROOT/config file
Larry Jones wrote:
You need to use LockDir= in your CVSROOT/config file to put the lock
files somewhere other than in the repository:
https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_2.html#SEC13
Setting LockDir helps, but that url is wrong.
Larry Jones wrote:
Joseph Shraibman writes:
I attempted to limit access to parts of my module by using group
permissions. The problem is than when the checkout reaches a directory
it can't read, it fails right away and doesn't go on to other directories.
You need to use LockDir= in your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joseph Shraibman [EMAIL PROTECTED] writes:
... Now the problem is that checkouts of certain
files are failing because Permission denied.
These files are owned by a group that the user
is a member of, but not the default group. Is
there any way
I attempted to limit access to parts of my module by using group
permissions. The problem is than when the checkout reaches a directory
it can't read, it fails right away and doesn't go on to other directories.
cvs server: failed to create lock directory for `dir'
(dir/#cvs.lock): Permission
Hi there,
i got some problems with my cvs. I m trying to set a a cvs with ssh
access, but i have a few problems when adding new files.
When i add new files, the permissions are set to readonly for owner,
group and all. I ve tryed to set the CVSUMASK variable, but there is no
difference
Markus Bott writes:
When i add new files, the permissions are set to readonly for owner,
group and all. I ve tryed to set the CVSUMASK variable, but there is no
difference.
If you mean the repository files, they're supposed to be read-only. CVS
never modifies an existing file, it replaces
Hi
I have got following structure of my existing
system
Linux Server(Acting as a CVS and Samba File
Server)--- XP Clients
I am having three groups ADMIN, BSSEG, BSSIG with
following scenario to be taken care of
BSSEGcan check out any file from the
repository, do the changes and
Is it possible to limit (write) access to a specific branch for specific
users?
Thanks
Euan
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
I have a sample project with r-s permissions for g and o.
I have dir1/file1 directory/file in the project, which user
cvsadmin in the cvs group, created. so now file1 has
r--r--r-- permissions.
I have a separate lock direcotry, called /cvsroot/lockDir
with rwxrwsrwx permissions.
Now user1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fouts Christopher (6452) [EMAIL PROTECTED] writes:
I have a sample project with r-s permissions for g and o.
I have dir1/file1 directory/file in the project, which user
cvsadmin in the cvs group, created. so now file1 has
r--r--r-- permissions
Fouts Christopher (6452) wrote:
I have a sample project with r-s permissions for g and o.
I have dir1/file1 directory/file in the project, which user
cvsadmin in the cvs group, created. so now file1 has
r--r--r-- permissions.
I have a separate lock direcotry, called /cvsroot/lockDir
Thanks to all!
-chris
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 08, 2004 12:43 PM
To: Fouts Christopher (6452)
Cc: [EMAIL PROTECTED]
Subject: Re: Question on repository file permissions
References:
[EMAIL PROTECTED]
From: Mark D
to the repository.
How do I set up my rwx permissions so ALL members of group users
can checkout/checkin from/to the repository, but ONLY cvsadmin can
directly access the repository, that is, through a regular unix
session and not via cvs.
If I do chmod g+rwxs sample, anyone in group users can
, and changed group ownership to users.
I have a user1 in group users who wants to read from and commit
to the repository.
How do I set up my rwx permissions so ALL members of group users
can checkout/checkin from/to the repository, but ONLY cvsadmin can
directly access the repository
Hello,
I have been digging into the manual for security and directory permissions. So far I
have not found what I am looking to implement and that is to cut off others outside
specific groups from seeing the cvs repository. Currently I must maintain 755 on all
the dirs inorder for cvs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Croswhite [EMAIL PROTECTED] writes:
I have been digging into the manual for security and directory
permissions. So far I have not found what I am looking to implement
and that is to cut off others outside specific groups from seeing the
cvs
I am trying to set up file permissions for my CVS repository that will be accessed from a remote client. The CVSNT server is v2.0.9 and is intalled on win2k server and the client is WinCVS 1.3.13 running on windowXP there are essentially 3 things i would like to do:1. i would like to limit access
,
Zandall.
-Original Message-
From: rog amos [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 3:27 PM
To: [EMAIL PROTECTED]
Subject: CVSNT File/Directory Permissions
I am trying to set up file permissions for my CVS repository that will
be accessed from a remote client
Hey all,
I am trying to understand the various intracacies with
users, permissions, groups and control of a
repository.
I have done the usual in initing a repository, setting
a cvs group as the owner of the initial repository
directory. I read that a cvsadmin group should be
the only accessible
Let's say I have in my repository, two modules: client1_module,
client2_module.
I only want my internal folks to view, commit, update, etc from
client1_module. However, I want to be able to give an employee of my
client2 access to and abilitity to commit, update, etc anything in
client2_module.
[ On Wednesday, August 6, 2003 at 22:27:24 (-0400), [EMAIL PROTECTED] wrote: ]
Subject: permissions on modules
I only want my internal folks to view, commit, update, etc from
client1_module. However, I want to be able to give an employee of my
client2 access to and abilitity to commit
I will be out of the office until August 11. Thank you, Heather
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Hi guys! I need perform a CVS with very configurable permissions.
I'm trying cvscop (http://cvscop.sourceforge.net). Cvscop seems very
friendly and easy to use. But I found some bug into the code.
What's the best way to limit or grant access at directory/sub-directory
level and user/group
Federico Edelman wrote:
I'm trying cvscop (http://cvscop.sourceforge.net). Cvscop seems very
friendly and easy to use. But I found some bug into the code.
What's the best way to limit or grant access at directory/sub-directory
level and user/group for each project (or module) of CVS repository.
I
permissions for different group of users. I have read the cvs manualfrom
|
| http://www.cvshome.org/docs/manual/cvs_2.html#SEC13
|
| and I have used the command chmod to specify a read only access
rights to the repository for the user named cvsuser, but I found that
when I log in as cvsuser
Hi Lu,
Please check cvspermissions
http://www.magic-cauldron.com/cm/cvspermissions/cvspermissions.html
if it doesn't meet your requirements.
It's a bunch of shell scripts intented to work on *NIX systems but
hopefully it could work on cygwin.
Regards,
Dusan
Hi, all
I have installed CVS with cygwin under windows2k operation system. It is
working properly. Further more,I want to specify the files permissions for
different group of users. I have read the cvs manualfrom
http://www.cvshome.org/docs/manual/cvs_2.html#SEC13
and I have used the command
Hi,
I have a strange problem. I want to synchronize 2 CVS databases but
want to preserve the permissions at Slave Server So that whatever
permissions I set on Slave it would not be replicated. I am running cvsup
from root account. Would you please help me how to acheive the same.
Regards
Preserve permissions is not working properly in my supfile
Here is the sample supfile
*default host=10.91.208.245
*default base=.
*default release=cvs
*default preserve
*default delete use-rel-suffix compress
kdeall
And mentioned below is the version number of CVSUP
CVSup client, non-GUI
-suffix
world-all
%
To mirror the sources from the 10.1.20.36 host.
This is good enough for our site.
Good luck,
-- Mark
Amit Sharma (SCM) [EMAIL PROTECTED] writes:
Preserve permissions is not working properly in my supfile
Here is the sample supfile
*default host
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a patch to CVS that does this (and a lot of other things). It's
at http://home.attbi.com/~minyard/.
- -Corey
Gaganinder Singh wrote:
|Hi,
|
|After creating a Brach from a Tag, I would like to set permissions on the
|branch. There are 50
Hi,
After creating a Brach from a Tag, I would like to set permissions on the
branch. There are 50 Users who have read write access on the main branch
however we need to set permission so that 25 of the 50 users have Read Write
Access and the rest of the 25 only Read Access newly created branch
Gaganinder Singh [EMAIL PROTECTED] writes:
After creating a Brach from a Tag, I would like to set permissions on the
branch. There are 50 Users who have read write access on the main branch
however we need to set permission so that 25 of the 50 users have Read Write
Access and the rest
On Fri, Feb 21, 2003, Mark D. Baushke wrote:
After creating a Brach from a Tag, I would like to set permissions on the
branch. There are 50 Users who have read write access on the main branch
however we need to set permission so that 25 of the 50 users have Read Write
Access and the rest
Isaac Claymore [EMAIL PROTECTED] writes:
I guess my question is somewhat more about filesystems than CVS, but I
think you guys may have had similar problems.
There're 10 members of my team, and they're in the group devp. $CVSROOT
is thus owned by group devp, so that every team member gets
Hi, CVS folks.
I guess my question is somewhat more about filesystems than CVS, but I
think you guys may have had similar problems.
There're 10 members of my team, and they're in the group devp. $CVSROOT
is thus owned by group devp, so that every team member gets read/write
access to the
On Thu, Feb 06, 2003, Prem Prakash Pathak wrote:
Can anybody suggest, how to restrict specific users from tagging.
We are using CVS Server 1.11 under linux accessing thru both Mac CVSClient
WinCVS using pserver. Upto now, any user who got permission to access
repository, can use
Hi All,
Can anybody suggest, how to restrict specific users from tagging.
We are using CVS Server 1.11 under linux accessing thru both Mac CVSClient
WinCVS using pserver. Upto now, any user who got permission to access
repository, can use tagging utility. Now we want to restrict some
I have updated the permissions patch to version 1.11.5. Because the
security problems in 1.11.4, you should update immediately.
In case you don't know, this patch adds the following:
* directory/file/branch permissions done internally to CVS. Each CVS
user can have permissions on a file
permissions, which have been
a high-demand feature.
The readme for this patch is attached. You can get the patch at
http://home.attbi.com/~minyard/.
Note that this hasn't seen much testing, so use it with care until you
have fully verified it.
-Corey
This directory contains a large number
Mullican, Catherine wrote:
Some files were checked in with the permissions set to 644. They need to be
755. I tried changing the permissions, making some whitespace changes, and
checking the files back in, but they're still 644 on checkout. Other files
in the project have the correct
Jericho writes:
I have a problem with permissions in directories under in my
repository. I noticed today that some files were marked with 'write'
permission for both the file owner and group. According to the cvs
docs, these should only be 'read-only' and not be changed.
That's correct
Hi all,
I have a problem with permissions in directories under in my
repository. I noticed today that some files were marked with 'write'
permission for both the file owner and group. According to the cvs
docs, these should only be 'read-only' and not be changed.
I'm wondering
I have added a perl script to checkoutlist in CVSROOT. When its extracted,
it does not have the execute permission. Is there a way to get ot to extract
with the execute permission, or would I have to have a script triggered off
of somewhere to modify the permissions after its extracted?
Thanks
the permissions after its extracted?
chmod +x $CVSROOT/CVSROOT/maillog.pl,v
Then delete the file in your sandbox and cvs update. It should now be
executable.
Fred
___
Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com
1 - 100 of 313 matches
Mail list logo
