Cron Daemon backup message too big
- From: Haines Brown <brownh@xxxxxxxxxxxxxxxx>
- Date: Sun, 30 Mar 2008 11:28:35 -0400
For a long time I've done back ups by having cron run a script
regularly. At a certain point (can't recall the circumstances) that
ceased to work, and I've had to initiate the backups by hand.
What happens is that Cron Daemon sends me a message that reports backup
progress, That is, I suppose there is one line in the message for every
file backed up. However, at a certain point, the message gets too big
and the backup terminates. I get a message from cron to the effect,
"mail failure - message too big".
My guess is that I am exceeding the message size limit in exim (default
is 50Mb). I suppose I could simply configure exim to accept larger
messages by having:
message_size_limit = 500 MB
(not sure of syntax here), but I'd prefer that cron simply not send me
messages for this job. Is there any way I can modify my backup script to
tell cron to be silent or to send its report instead to a temporary log
file?
--
Haines Brown, KB1GRM
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: Cron Daemon backup message too big
- From: Andrei Popescu
- Re: Cron Daemon backup message too big
- Prev by Date: Can we run a qemu instance as a dedicated home network firewall?
- Next by Date: Samba 3.0 - (smbpasswd) list added users
- Previous by thread: Can we run a qemu instance as a dedicated home network firewall?
- Next by thread: Re: Cron Daemon backup message too big
- Index(es):
Relevant Pages
- Re: Silent Cron Jobs
... afaik cron mails all output from a script. ... cronjob I usually dump
all stdout ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
(Debian-User) - Re: mksysb script
... > I should schedule mksysb on AIX 4.3.3 machine every day at the same time. ...
> Also should have record in a log file about backup and status of backup. ... >
This last line in Cron should report error if occurs. ... Try running the backup script
on the command line with the log redirected as ... (comp.unix.admin) - Re: mksysb script
... > I should schedule mksysb on AIX 4.3.3 machine every day at the same time. ...
> Also should have record in a log file about backup and status of backup. ... >
This last line in Cron should report error if occurs. ... Try running the backup script
on the command line with the log redirected as ... (comp.unix.questions) - Re: mksysb script
... > I should schedule mksysb on AIX 4.3.3 machine every day at the same time. ...
> Also should have record in a log file about backup and status of backup. ... >
This last line in Cron should report error if occurs. ... Try running the backup script
on the command line with the log redirected as ... (comp.unix.misc) - Re: mksysb script
... > I should schedule mksysb on AIX 4.3.3 machine every day at the same time. ...
> Also should have record in a log file about backup and status of backup. ... >
This last line in Cron should report error if occurs. ... Try running the backup script
on the command line with the log redirected as ... (comp.unix.aix)