Re: anoncvs troubles (was Re: CVS vs anoncvs)

Christof Petig <christof@petig-baender.de>

From: Christof Petig <christof@petig-baender.de>
To: "Marc G. Fournier" <scrappy@hub.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2001-09-20T14:38:09Z
Lists: pgsql-hackers, pgsql-general
"Marc G. Fournier" wrote:

> Okay, its updated effective a few minutes ago ... and the upate should
> work as well ...

Should ...

~/pgsql-cvs/pgsql/src/interfaces/ecpg/preproc > cvs status preproc.y
cvs server: failed to create lock directory for
`/projects/cvsroot/pgsql/src/interfaces/ecpg/preproc'
(/projects/cvsroot/pgsql/src/interfaces/ecpg/preproc/#cvs.lock): Permission denied

cvs server: failed to obtain dir lock in repository
`/projects/cvsroot/pgsql/src/interfaces/ecpg/preproc'
cvs [server aborted]: read lock failed - giving up

~/pgsql-cvs/pgsql > cvs update
cannot create_adm_p /tmp/cvs-serv48812/ChangeLogs
Permission denied

~/pgsql-cvs/pgsql > cvs update -l
cvs server: Updating .
cvs server: failed to create lock directory for `/projects/cvsroot/pgsql'
(/projects/cvsroot/pgsql/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository `/projects/cvsroot/pgsql'
cvs [server aborted]: read lock failed - giving up

... but it does not, yet.

Christof