Brian Munroe wrote:
> On 7/9/06, Ryan Schmidt <subversion-2006c@ryandesign.com> wrote:
>
>>
>> Sounds like when you run the command manually, your password is
>> cached (in the directory ~/.subversion/auth) and when you run it from
>> cron, it's running under a different user who doesn't have the
>> password cached. If you can figure out which user cron runs as, you
>> could become that user on the shell and manually do a Subversion
>> command so it caches your username and password. Or you may need to
>> pass the username and password to the svn update and svn commit
>> commands with the --username and --password switches.
>>
>
> Additionally, since the /etc dir is on the same server as the SVN
> repo, could Oliver change the URL format from http:// to file:// and
> make sure the crontab user as write permission to the repository?
Doing file:// based access is a bit of an adventure to maintain access
control parallel with the HTTP/HTTPS access control with, unless you start
using svnperms.py or something like it.
But ignore that: for many users, they log in as themselves and "su" or
"sudo" to do root operations or run things as root. The result is that they
wind up inheriting a lot of their environment from their login account, and
this can confuse things like cron scripts run as that bare user in seriously
odd ways.
Ryan? Try actually logging in as root and running the cron scripts by hand,
making sure not to do it as su or sudo, as a test. I actually ran into a
very similar problem with a web repository this year that I solved by doing
the checkout as the root login user, not the "sudo" root user.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 9 19:08:15 2006