From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git-daemon messing up permissions for gitweb
Date: Fri, 09 Jun 2006 20:58:09 +0200 [thread overview]
Message-ID: <e6cgbo$2rm$1@sea.gmane.org> (raw)
In-Reply-To: 5A14AF34CFF8AD44A44891F7C9FF41050795782F@usahm236.amer.corp.eds.com
Post, Mark K wrote:
> I'm trying to set up a git repository for mainframe Linux developers to
> use at git390.osdl.marist.edu. Everything _seemed_ to go well, until
> Martin Schwidefsky started actually pushing changes back to the
> repository. When he does that, the projects disappear from the web page
> that gitweb.cgi is generating.
>
> As far as I can tell, the problem is happening because these files are
> being written out with file permissions of 640, and since Apache is
> running as user wwwrun, it can't read them:
> -rw-r----- 1 sky git 5490 Jun 9 03:35 ./linux-2.6.git/info/refs
One of the possible soultion would be to add sky to Apache group,
make directory sticky-group, and make files readable by group (perhaps by
marking repository as shared, or something).
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-06-09 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 18:41 Git-daemon messing up permissions for gitweb Post, Mark K
2006-06-09 18:58 ` Jakub Narebski [this message]
2006-06-09 19:05 ` Linus Torvalds
2006-06-09 20:01 ` Junio C Hamano
2006-06-09 19:51 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-06-09 19:11 Post, Mark K
2006-06-09 19:27 ` Jakub Narebski
2006-06-09 20:08 Post, Mark K
2006-06-09 20:18 ` Junio C Hamano
2006-06-09 20:22 ` Linus Torvalds
2006-06-09 20:34 ` Junio C Hamano
2006-06-09 20:44 ` Linus Torvalds
2006-06-09 21:02 ` Jakub Narebski
2006-06-09 20:29 Post, Mark K
2006-06-09 20:45 Post, Mark K
2006-06-09 20:52 Post, Mark K
2006-06-09 21:06 ` Junio C Hamano
2006-06-10 21:30 ` Alex Riesen
2006-06-10 21:41 ` Linus Torvalds
2006-06-10 22:30 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e6cgbo$2rm$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.