On Sun, 9 Jul 2006, 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?
>
> -- brian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Brian, Ryan,
Thanks for this points
I was as sudo user when manually running so the passwords were sure enough
only cached in my own home dir .subversion
I am about to test with cron [ which since it is a root cron run's as
root] again having first done a true svn connection to repo with root
user.
About the file:// url would that be a wise choice?
in this case I need to tell svn about the new URL ? I think.
This repos is never going to be checked out, it is only for recording etc
dir changes.
regards
-- Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 10 15:27:19 2006