On Oct 26, 2007, at 22:05, Chris Ross wrote:
>  On Oct 26, 2007, at 21:50, John Nemeth wrote:
>>       This is setting a bunch of timeouts to "0".  I assume the
>> idea is
>>  to not have cron hang indefinitely if there are mail problems.
>>  However, it probably takes a bit of time to do crypto processing.
>> Try
>>  changing the "-or0s" to "-or1m".  This should allow a considerable
>>  ammount of time for processing without having cron hang forever.
>
>     Yup.  As you expected, this causes it to work.  Even trying the
>  command-line test I was using with -or10s works alright for me,
>  on my 450Mhz sparc64.

   It occurs to me that cron runs things once-a-minute, so using
a minute as a timeout may be a bad idea.  I would recommend
something in the 10-30 second range.  Anyway.  Thanks for your
assistance.

                 - Chris