On Jul 9, 2006, at 10:57, o.nash@cs.ucc.ie wrote:
[snip]
> svn-cron.sh:-
> cd /etc
> /usr/bin/svn cleanup .
> /usr/bin/svn update
> /usr/bin/svn commit -m"weekly cron commit .."
> exit 0
>
> This fails and logs:-
> Authentication realm: <http://hostname:8080> Subversion Repository
> CSSG Group
> Password for 'root': Authentication realm: <http://hostname:8080>
> Subversion Repository CSSG Group
> Username: /system/bin/hostname/svn-cron.sh: line 11: 14311 Aborted
> /usr/bin/svn update
> svn: Working copy '/etc' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> details)
>
> Line 11 is the update line.
>
> However when the above commands are run manually they work fine.
> and no prompt for password is required.
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 9 16:22:01 2006