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.
--
[email protected] <><, Pseudo Engineer, itinerant idiot
_______________________________________________
LibreOffice mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice
