Date: Thu, 24 Dec 2009 10:38:41 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Rolf G Nielsen <lazlar@lazlarlyricon.com> Cc: Noel Jones <noeldude@gmail.com>, freebsd-questions@freebsd.org Subject: Re: Supressing dd output Message-ID: <20091224163841.GG98917@dan.emsphone.com> In-Reply-To: <4B32F1CA.8000500@lazlarlyricon.com> References: <4B32EBDB.1090808@lazlarlyricon.com> <cce506b0912232032v568ec1bdo2c1928e60430f3e3@mail.gmail.com> <4B32F1CA.8000500@lazlarlyricon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Dec 24), Rolf G Nielsen said: > Noel Jones wrote: > > On Wed, Dec 23, 2009 at 10:19 PM, Rolf Nielsen wrote: > >> I'm wondering if there's a way to supress the summary output from dd. > >> I'm working on a backup script, that encrypts the backups, and after > >> encrypting overwrites the unencrypted file several times using dd. > >> I've tried to redirect the output with 2>&1 > /dev/null but it doesn't > >> work. Since I run the script from the daily_local variable in > >> periodic.conf, and the script backs up 11 filsystems (ZFS) to separate > >> files, the mail from periodic daily gets ridiculously long, and most of > >> it being dd summaries. > > > > Order matters. > > > > dd ... >/dev/null 2>&1 > > Thanks Noel. I've never considered using that order before. Probably > because first time I saw that construct and had it explained to me, it was > ordered the way I had it, and I very rarely have any use for it, so I > haven't really noticed that my way was wrong; I usually only redirect > stdout if anything at all. Anyway, now it works like a charm. Thanks. > :) 2>/dev/null is really all you need, since dd only prints those info lines to stderr (stdout usually being used as its stream output unless of= is used) -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091224163841.GG98917>