On Wed, Oct 19, 2005 at 07:33:18AM -0600, Bdale Garbee wrote:
> On Wed, 2005-10-19 at 10:12 +0200, A Mennucc wrote:
>
> > Each day I receive a long email with all details of what dump did;
> > I would appreciate if there was a wait to quiet dump
>
> The approach taken by most backup systems (like amanda, bacula, etc)
> that wrap invocations of dump, tar, etc., is to redirect stdout/stderr
> to a log file, and then post-process the log file.
yes, I thought of it, I will probably change my code to
dump -f - 2> dumplog | ssh backuphost 'dd of=backup'
egrep -v 'blah|blah' dumplog
Still a -quiet option would be much nicer...
indeed, in the above approach, if I run my script interactively,
I will not see error messages until dump is done
unfortunately shell code does not admit "double pipes", that is ,
some magic code looking like
dump -f - \
1>| { ssh backuphost 'dd of=backup' ; }
2>| { egrep -v 'blah|blah' ; }
where two pipes are opened at the same time, for fd 1 and fd 2
(that would be cool... I will open a wishlist on bash :-)
a.
ps: I use my backup system on 6 different PCs, that is why I am annoyed
by the emails... I am now annoyed by the dump blah blah, and
I do not read the emails, so I may skip some other important cron messages
ps2: you may wonder why I do not use amanda/bakula/etc :
I started writing my backup scripts some years ago, then they improved
in the years, and they do the job very well for me
--
Andrea Mennucc
"Ukn ow,Ifina llyfixe dmysp acebar.ohwh atthef"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
