Hi Duy, On 2015-09-19 04:21, Duy Nguyen wrote: > On Thu, Sep 17, 2015 at 11:54 PM, Joakim Tjernlund > <joakim.tjernlund@xxxxxxxxxxxx> wrote: >> 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@xxxxxxxxxxxx> 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@xxxxxxxxxxxx> wrote: >>> > > > I cannot push: >>> > > > # > git push origin >>> > > > Login for jocke@xxxxxxxxxxxxxxxx >>> > > > 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? IMO it makes little sense to remove write access from users who you want to push. They need to write objects to the directory, after all, and update refs. This problem sounds more like the doing of an overzealous sysadmin to me than a careful one who researched diligently what locations require write access for the intended operations. Personally, I see little sense in bending over to try to support such an intentionally tampered setup. Ciao, Dscho -- 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