Re: Cron process to schedule CVS check in as another user ???

[Pierre Asselin]

address@hidden wrote:

> We would like to version PLSQL code, but we don't want the repository
> to be updated until code has successfully been compiled and deployed to
> the DB.

Would branching do ?  Develop and test on a branch and merge
to the trunk when the tests are declared passed.

> [ snip ]
> Granted, as I write this code - I realize it's backwards, but here are
> my questions:

> 1. is it possible to check in code as common user telling it to use
> another for CVS history and logs?

I don't think so, but I may be wrong.  There is always sudo(8), where
you *authorize* user X to run some class of commands as user Y.

> 2. Can a common user cd to the developers working CVS directories and
> even do a check in?

I think so, if he has write permission to the working directory tree
and if he uses the "-d" option to override the access method stored
in the CVS/Root files.  For the permissions, use set up the groups
appropriately and set the umask to something like 002 so the cvs
operations don't clobber group flags.


> 3. I'm not really a Unix expert, what's the best way to run a script as
> another Unix user ? we are an HPUX 11 shop. 

I'd say sudo, as configured in the file /etc/sudoers .


-- 
pa at panix dot com