On Sun, Oct 07, 2007 at 08:00:17PM +1000, Tim Bates wrote:
>
> Quite possibly it's generating too much output for cron to be happy, and
> cron is killing the job. Incremental backups should in theory have much
> fewer files, so much less output.
> Try running with " > /dev/null" at the end of the
Quite possibly it's generating too much output for cron to be happy, and
cron is killing the job. Incremental backups should in theory have much
fewer files, so much less output.
Try running with " > /dev/null" at the end of the command line to stop
it printing non-errors out.
TB
On 7/10/2007, "
One of my backup sets is designed to back up the whole of four systems -
the four that are always at home and always on, running a system that
flexbackup can handle.
A full backup of this set runs OK manually, but when run from cron,
stopped working during one of the larger filesystems.
An increm
