Julian Foad <julianfoad@btopenworld.com> writes:
> Philip Martin wrote:
> > David Wilson <dw@botanicus.net> writes:
> >
> >> $ svn co https://china.botanicus.net/svn/cdr_mysql < /dev/null
> > If you are running svn from a crontab then using --non-interactive
> > will cause it to fail rather than spin.
>
> Sorry, Philip - not enough words for someone like me to understand.
> (Apologies if it is obvious from some previous message that I haven't
> read.) Probably someone who is familiar with the problem will
> understand and reply. If not, what's the behaviour seen by David
> Wilson, what is the desired behaviour, what sort of failure, what
> spins for what?
The problem seen is that Subversion needs auth info to perform the
checkout, so by default, it prompts for that information. The problem
is that, while running from a cron job, there's no way to actually
respond to those prompts, so Subversion just hangs waiting for input
it will never get.
The --non-interactive options tells Subversion to never prompt for
auth information. In this case, if Subversion doesn't prompt, it
doesn't hang. But then, it doesn't get the auth info it needs either,
so it will simply return an error. But at least it doesn't hang!
Of course, if the repository requires only simple username/password
auth input, then the cron job can use --non-interactive, --username,
and --password to achieve success. More complex scenarios might
involve tweaking runtime config options (for the likes of cert path
and passphrase info, etc).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 15 15:50:02 2005