Re: strange reaction from post-commit hook

On Jun 5, 2009, at 04:03, J. Bakshi wrote:

> Based on your previous discussion I have just change /sbin/
> nologin to
> /bin/bash of apache entry in /etc/password and assigned it a password.
> then I login as apache user and did a "svn list" to accept the
> certificate. After that the commit and hooks are working perfectly
> Ok :-)
> Thanks for your help. It really made me fixing the problem. I find it
> little bit easier than the file:/// protocol you have mentioned above.
> Specially the users on linux/wimdows client uses their GUI tool and
> there it would not be possible to fire up the script as apache user.

Your users don't need to do anything. All that you, in your role as
server administrator, need to do, is relocate the POSTCOMMIT working
copy to the file:// protocol, one single time. That's all. Your users
will continue to use the https:// protocol.

Giving your apache user a login shell is a security vulnerability and
thus not recommended. Instead of this, if you insist on keeping the
working copy checked out from http or https, you can use the --config-
dir option to the "svn" command to tell it where to look for its
config directory.

> Though there is some permission problem if I use samba. In post-commit
> if I use a samba mount point like

I have also seen issues when trying to use svn commands on an smb
mount point. I cannot help you resolve them.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2359641

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-05 11:49:57 CEST