On Mon, 22 Jan 2007, Martin Langhoff wrote:
> On 1/22/07, Linus Torvalds <torvalds@xxxxxxxx> wrote:
> > Umm. Your git daemon is probably running as "nobody", and simply doesn't
> > have write permissions to the archive, does it?
> >
> > > % cat /etc/xinet.d/git-daemon
> > > service git
> > > {
> > > user = nobody
> >
> > iow, I think you simply need to make sure that git-daemon will have write
> > permission to the thing. Either by making the whole repository writable by
> > nobody, or by running git-daemon as the proper user.
>
> Whereby I personaly run back quickly to cover under my git-over-ssh
> safety blanket.
Sure.
I suspect that git-daemon is possibly easier and faster to set up in the
kind of situation where you set up git instead of CVS inside a company,
though.
In that situation, you could just say: "machine X is the central CVS
repository, and now it also contains a set of git repositories, all owned
by nobody:nobody".
That way, you basically get the exact same situation as you had with CVS,
with minimal setup.
If the alternative is some NFS thing, I'd take that writing git-daemon
over shared NFS-access from everybody any day..
Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html