Date: Mon, 8 Jun 2009 20:54:07 -0700 From: Steven Schlansker <scs@eecs.berkeley.edu> To: Lord Of Hyphens <lordofhyphens@gmail.com> Cc: Daniel Underwood <djuatdelta@gmail.com>, freebsd-questions@freebsd.org Subject: Re: Reproduce previous stdout output without running previous command Message-ID: <9FACF948-286D-40BC-9471-74CC1D5580E9@eecs.berkeley.edu> In-Reply-To: <b0442c260906082048u6deeb5a8v44077bf92afc58dc@mail.gmail.com> References: <b6c05a470906082044l69616b2h531adaa1fdf9f0e@mail.gmail.com> <b0442c260906082048u6deeb5a8v44077bf92afc58dc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 8, 2009, at 8:48 PM, Lord Of Hyphens wrote: > On Mon, Jun 8, 2009 at 10:44 PM, Daniel Underwood <djuatdelta@gmail.com > >wrote: >> >> $ fdupes -r ~/directorywithlotsoflargefiles >> >> (.....lots of output, woops, should have sent to a text file!....) >> >> $ output[1] >> ~/textfile.txt >> >> Hopefully this has made (some) sense. >> <freebsd-questions@freebsd.org> > > > Check the manpage for tee. That should give you a solution you're > looking > for. I think the intention of the original question was for the case where you have forgotten to set up a pipe/redirection properly before starting the long- running command. Tee would work fine if you have the foresight to use it... Steven
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9FACF948-286D-40BC-9471-74CC1D5580E9>