Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index



On Fri, 2011-10-07 at 23:59 -0400, Kevin Hunter wrote:
I'm about to get schooled in Bash, I'm sure, but if you're looking to 
get both stdout and stderr into the log file, would that be '&>' (ensure 
no space between ampersand and carrot), as opposed to >& ?

        I guess I learn these things by some random walk, but >& works for me
here:

ls /notthere >& /tmp/baa.log
cat /tmp/baa.log
ls: cannot access /notthere: No such file or directory

        ;-)

        ATB,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.