Linux: No output when running a (working) command in a .sh script

Question

I want to get the output from a program in Linux, and I put this into a .sh file:

wine Blockland.exe ptlaaxobimwroe -dedicated -port 30100 > consoleLog.txt

It executed the program, but created a blank file. This command always works when directly executed in a Terminal window. So why isn't it printing the output to the file when in a .sh script?

You are running a DOS console application, which does not necessarily write to stdout or stderr, but it writes to the "console". It's nearly impossible to capture the "console" output reliably. The only tool that I have ever seen that is able to capture console output is expect by Don Libes, and that does all sorts of hacks. — Mark Lakata
– Mark Lakata, Commented Jul 25, 2013 at 19:52

nullptr · Accepted Answer · 2013-07-25 19:49:41Z

1

Possibly because it prints its output to the stderr stream, not to stdout. Try appending 2>&1 to the end of command (after consoleLog.txt), or just use &> instead of >.

answered Jul 25, 2013 at 19:49

nullptr

11.1k1 gold badge27 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Ryhnn · Accepted Answer · 2013-07-25 20:00:13Z

0

redirect stdout with exec:

#!/bin/sh
#Example script
exec > consoleLog.txt
wine Blockland.exe ptlaaxobimwroe -dedicated -port 30100

answered Jul 25, 2013 at 20:00

Ryhnn

4561 gold badge5 silver badges16 bronze badges

Collectives™ on Stack Overflow

Linux: No output when running a (working) command in a .sh script

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related