It actually boiled down to permissions and the restricted execution
enviroment for cron. Specifying the complete path for the svn binary and
the working directory fixed the problem. The SSH issues and other net
related issues were moot points due to the repository being accessed via the
file:// option. The working directory is what we write to since it's
mounted on all but 1 of the servers, then the workhorse server just does the
commit for the entire working area.
-Garrett
-----Original Message-----
From: Thomas Harold [mailto:tgh@tgharold.com]
Sent: Wednesday, December 13, 2006 6:38 PM
To: users@subversion.tigris.org
Subject: Re: svn and cron
Vincent Lefevre wrote:
> On 2006-12-11 20:50:49 -0600, Ryan Schmidt wrote:
>> Curious. What do you need expect for in this scenario? svn is not an
>> interactive program. The only thing I think it can prompt for is the
>> username and password, and you can provide that with the --username
>> and --password options without resorting to something like expect.
>
> The --password option may be a security hole, e.g. if there are
> several users on the machine.
>
You might also look into using a no-password SSH keyfile that has limited
rights to the SVN repository (i.e. it can only read). Plus you can restrict
the SSH key to only executing the "svnserve -t" command on the SVN server.
Which should be fairly secure and low-risk.
(We us something similar to push log files from our web servers to a central
SVN server. Works well, only transmits the changes and we have it set to
transmit hourly.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 14 15:09:47 2006