On Sun, 10 Mar 2002, Patrick Nelson wrote: > Nope that doesn't work. The commits seem to work but then there is an error > of the nature of: > > cvs commit: Examining . > Checking in il.txt; > /usr/local/cvsroot/bon/il/il.txt,v <-- il.txt > new revision: 1.3; previous revision: 1.2 > done > cvs commit: cannot open CVS/Entries.Log: Permission denied
You need to "own" the local working copy too, as cvs updates files in the CVS/ directory when it's run. > Further commits give worse results: > > cvs commit: Examinig. > cvs commit: Up-to-date check failed for 'il.txt' > cvs [commit aborted]: correct above errors first! That last one means that you have a checked-out file, and there is a newer version checked into the repository. You have to update the local repository before you can commit the changes. > OK so I added the checkout to the list thinking that maybe I need to be > checking it out as the same user... > > su pnelson -c 'cvs -d $cvslocal checkout bon/il' > > That has errors too: > > cvs [checkout aborted]: cannot make directory bon: No such file or > directory > > Make sense seeing I'm in a root permission dir... Arg... > > So me thinks that maybe a better description of what I'm doing might shed > some light on someone being able to help me with my solution. > > I have a root run admin script that I want to use to track the changes to > documentation. The program is meant to be run as a "su -" call I have many > scripts that utilize the root user (and only the root user) in this way and > this script incorporates many off these other scripts. This "no root > commits" is idiotic to me, but I never get into those root flame wars. > However, I need to be able to commit as some damn user so that I can > implement this darn script. Anyone have any other ideas? I'm a little puzzled by the requirement to run as root. Is there any way to run the rest of this process with user permissions rather than running as root? I'm guessing that you're trying to keep some record of changes to certain files or directories in the CVS tree? If so there is a way to do that by configuring cvs to run a script when those files are checked in, which would perhaps ease your pain a little. If that won't do, it's just a question of changing permissions on the files so that a non-root cvs operation will succeed, which you can do with chown/chmod within the part of your script that runs as root. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
