Damian Wiest <[EMAIL PROTECTED]> wrote: > Suppose your cron jobs don't emit output, which any good job shouldn't do.
Huh? If you want a task to run on a schedule, and then mail you the results, then cron is exactly what you want. Any "good job" does what its author wants it to. If they want it to emit output, then having it be silent for no reason does not make it a "good job". Adam
