Need help setting up cron

[Robert Dailey]

On Sun, Jul 20, 2008 at 11:37 AM, Mumia W.
<paduille.4062.mumia.w+nospam at earthlink.net> wrote:
> Can you find out what signal, if any, was used to interrupt the program?
>
> The output, including any error message, is critical. You might be able
> to use the "script" program to capture both normal and error output from
> your script and the spawned programs.
>
> 30 12 * * * root script -c "/my/script/file" -f /tmp/debug.log
>
> Svnadmin might also want to interact with a TTY--especially to
> authenticate--and that could lead to failure. If you need to
> programmatically enter a password for svnadmin, you could either use a
> command-line paramter or use the "expect" program.

I don't know if a signal was used to interrupt the program. I'm also
not seeing any error messages using the logging method I was using
previously. I tried doing your 'script' command to log instead,
however it's not showing me anything useful. It's showing the output
from the "svnadmin dump" process going normally, but then it just
stops. No errors, no warnings. It just magically stops.

Below is the new logging information I get when using the 'script'
program to run my backup script. As you can see, it gets to revision
26 in the dump process and then it just decides not to continue...

Script started on Sun Jul 20 12:17:01 2008
Starting dump process...
* Dumped revision 0.
* Dumped revision 1.
* Dumped revision 2.
* Dumped revision 3.
* Dumped revision 4.
* Dumped revision 5.
* Dumped revision 6.
* Dumped revision 7.
* Dumped revision 8.
* Dumped revision 9.
* Dumped revision 10.
* Dumped revision 11.
* Dumped revision 12.
* Dumped revision 13.
* Dumped revision 14.
* Dumped revision 15.
* Dumped revision 16.
* Dumped revision 17.
* Dumped revision 18.
* Dumped revision 19.
* Dumped revision 20.
* Dumped revision 21.
* Dumped revision 22.
* Dumped revision 23.
* Dumped revision 24.
* Dumped revision 25.
* Dumped revision 26.