Re: Unable to create temporary file '/var/git/tmv3-target-overlay.git/shallow_Un8ZOR': Permission denied
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Sep 19, 2015, 02:21 UTC
- Message-ID
- <CACsJy8DFpLLtc7+Mix1d=Hy8h-duUqt4Y8WYsRL1nEryizoeww@mail.gmail.com>
- In-Reply-To
- <1442508864.21964.26.camel@transmode.se>
On Thu, Sep 17, 2015 at 11:54 PM, Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
Show 17 quoted lines
> On Thu, 2015-09-17 at 20:18 +0700, Duy Nguyen wrote: >> On Mon, Sep 14, 2015 at 10:37 PM, Joakim Tjernlund >> <joakim.tjernlund@transmode.se> wrote: >> > On Mon, 2015-08-31 at 16:56 +0700, Duy Nguyen wrote: >> > > On Fri, Aug 21, 2015 at 6:36 PM, Joakim Tjernlund >> > > <joakim.tjernlund@transmode.se> wrote: >> > > > I cannot push: >> > > > # > git push origin >> > > > Login for jocke@git.transmode.se >> > > > Password: >> > > > Counting objects: 7, done. >> > > > Delta compression using up to 4 threads. >> > > > Compressing objects: 100% (7/7), done. >> > > > Writing objects: 100% (7/7), 13.73 KiB | 0 bytes/s, done. >> > > > Total 7 (delta 4), reused 0 (delta 0) >> > > > fatal: Unable to create temporary file '/var/git/tmv3-target-overlay.git/shallow_Un8ZOR': Permission >> > > > denied
I'm about to do it, but now I'm not sure if I should move shallow_XXXXXX out of $GIT_DIR. It will not be the only command that may write to $GIT_DIR. "git gc --auto" (which can be triggered at the server side at push time) can write $GIT_DIR/gc.pid (and soon, gc.log). Even if you disable gc --auto and run it periodically (with cron or something), it will write gc.pid.
Is it really necessary to remove write access in $GIT_DIR? Do we (git devs) have some guidelines about things in $GIT_DIR?
-- Duy