On Mon, Jul 21, 2003 at 10:11:38AM -0300, The Hermit Hacker wrote:
>
> check it now, should be fine ...
Works now, thanks.
Kurt
---(end of broadcast)---
TIP 8: explain analyze is your friend
Teodor Sigaev <[EMAIL PROTECTED]> writes:
> Mark, you don't set right umask for me, IMHO.
There seems to be more to it than that: I can do "cvs update" just fine
from the master server. So I'd guess that the issue is not with your
own permissions, but with what happens when a new directory is
pro
check it now, should be fine ...
On Mon, 21 Jul 2003, Kurt Roeckx wrote:
> When doing cvs update I get:
>
> cvs server: Updating contrib/tsearch2
> cvs server: failed to create lock directory for
> `/projects/cvsroot/pgsql-server/contrib/tsearch2'
> (/projects/cvsroot/pgsql-server/contrib/tsearc
Mark, you don't set right umask for me, IMHO.
Kurt Roeckx wrote:
When doing cvs update I get:
cvs server: Updating contrib/tsearch2
cvs server: failed to create lock directory for
`/projects/cvsroot/pgsql-server/contrib/tsearch2'
(/projects/cvsroot/pgsql-server/contrib/tsearch2/#cvs.lock):
Permis
When doing cvs update I get:
cvs server: Updating contrib/tsearch2
cvs server: failed to create lock directory for
`/projects/cvsroot/pgsql-server/contrib/tsearch2'
(/projects/cvsroot/pgsql-server/contrib/tsearch2/#cvs.lock):
Permission denied
cvs server: failed to obtain dir lock in repository
`/
