info-cvs
[Top][All Lists]
Advanced

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

suggestions to figure out why permissions are not working on new repo. w


From: Todd Denniston
Subject: suggestions to figure out why permissions are not working on new repo. was:Re: CVS help needed urgently
Date: Tue, 11 Mar 2008 21:40:32 -0400
User-agent: Thunderbird 2.0.0.9 (X11/20071031)

Sadia Tahseen wrote, On 03/11/2008 06:21 PM:
Hi ,

<todd said>
something is highly amiss at this point.

You probably have leftovers from several attempts of getting setup at this 
point, some of which probably have permission/ownership problems. (probably 
something owned by root that should be owned by sadia.)
There are two ways out that I can think of.
1) remove the repository and sandboxes that you have created so far and start 
following the email with the description again fresh, if this fails go to 
method 2, while indicating this one failed and how.
2) we have to look at the permission/ownership of everything in $CVSROOT and 
the sandboxes, and then determine what changes have to be made.

The second method is significantly more pain in my book, but it is you who gets 
to pick the method.
</todd said>
<Sadia said>
How are we supposed to do the second method>
<Sadia said>



<todd said>
To begin second method:
take attached files,
as sadia, copy wereareweserver.txt to the server
export CVSROOT and CVS_RSH as appropriate
chmod +x wereareweserver.txt
execute wereareweserver.txt

as sadia, copy wereareweworksta.txt to the workstation
export CVSROOT and CVS_RSH as appropriate
chmod +x wereareweworksta.txt
execute wereareweworksta.txt

get server:/tmp/serverlog.txt and workstation:/tmp/workstationlog.txt into one directory. review serverlog.txt and workstationlog.txt make sure that anything sensitive, like passwords, either are not present or sanitize them.
attach serverlog.txt and workstationlog.txt to an email to info-cvs with the
subject line: "Re: suggestions to figure out why permissions are not working on new repo."
</todd said>

<todd said>
you are executing the attached scripts at your own risk.
you should probably review them and understand them before executing them.
</todd said>
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
#purpose: to figure out what permissions are on cvs things in the server.
#it should be ran as the normal user...sadia

LOGFILE=/tmp/serverlog.txt

echo "CVSROOT ($CVSROOT)" > $LOGFILE
echo "CVS_RSH ($CVS_RSH)" >> $LOGFILE
echo " " >> $LOGFILE
echo " checking perms on Repo dirs" >> $LOGFILE
ls -ld /appl/src/cvs/JavaAppl \
    /appl/src/cvs/JavaAppl/CVSROOT \
    /appl/src/cvs/JavaAppl/projectdir >> $LOGFILE
echo " " >> $LOGFILE
echo " who am i" >> $LOGFILE
whoami >> $LOGFILE
echo " " >> $LOGFILE
echo " checking sadia perms" >> $LOGFILE
groups  >> $LOGFILE
echo " " >> $LOGFILE
echo " find out what kind of device we are on " >> $LOGFILE
CVSMNTPT=`df /appl/src/cvs/JavaAppl|tail -1 |awk '{print $6}'`
mount |grep $CVSMNTPT >> $LOGFILE
echo " " >> $LOGFILE
echo " " >> $LOGFILE
echo " " >> $LOGFILE
echo " " 
echo " " 
echo " " 
echo " " 
cat $LOGFILE
echo "send $LOGFILE to info-cvs"
#purpose: to figure out what permissions are on cvs things in the workstation.
#it should be ran as the normal user...sadia

LOGFILE=/tmp/workstationlog.txt

echo "CVSROOT ($CVSROOT)" > $LOGFILE
echo "CVS_RSH ($CVS_RSH)" >> $LOGFILE
echo " " >> $LOGFILE
echo " checking perms on sandbox dirs" >> $LOGFILE
ls -ld ~/projectdir/ >> $LOGFILE
 ls -l ~/projectdir/ >> $LOGFILE
echo " " >> $LOGFILE
echo " who am i" >> $LOGFILE
whoami >> $LOGFILE
echo " " >> $LOGFILE
echo " checking sadia perms" >> $LOGFILE
groups  >> $LOGFILE
echo " " >> $LOGFILE
echo " test checkout" >> $LOGFILE
cd
mv projectdir projectdir.old
echo "going to need your ssh password"
cvs checkout projectdir 2>&1 | tee -a $LOGFILE
echo " " >> $LOGFILE
echo " checking perms on sandbox dirs again" >> $LOGFILE
ls -ld ~/projectdir/ >> $LOGFILE
 ls -l ~/projectdir/ >> $LOGFILE
echo " " >> $LOGFILE
echo " " >> $LOGFILE
echo " " >> $LOGFILE
echo " " 
echo " " 
echo " " 
echo " " 
cat $LOGFILE
echo "send $LOGFILE to info-cvs"
Even when this disclaimer is not here, 
the opinions expressed by me are not necessarily sanctioned by and 
do not necessarily represent those of my employer. 
Also even when this disclaimer is not here, I DO NOT have authority to 
direct you in any way to alter your contractual obligation 
and my email can NOT be used as direction to modify a contract.

reply via email to

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