142

I'm looking to execute a shell command in Go and get the resulting output as a string in my program. I saw the Rosetta Code version:

package main
import "fmt"
import "exec"

func main() {
  cmd, err := exec.Run("/bin/ls", []string{"/bin/ls"}, []string{}, "", exec.DevNull, exec.PassThrough, exec.PassThrough)
  if (err != nil) {
    fmt.Println(err)
    return
  }
  cmd.Close()

But this doesn't capture the actual standard out or err in a way that I can programatically access - those still print out to the regular stdout / stderr. I saw that using Pipe as the out or err could help elsewhere, but no example of how to do so. Any ideas?

1

11 Answers 11

271

The package "exec" was changed a little bit. The following code worked for me.

package main

import (
    "fmt"
    "os/exec"
)

func main() {
    app := "echo"

    arg0 := "-e"
    arg1 := "Hello world"
    arg2 := "\n\tfrom"
    arg3 := "golang"

    cmd := exec.Command(app, arg0, arg1, arg2, arg3)
    stdout, err := cmd.Output()

    if err != nil {
        fmt.Println(err.Error())
        return
    }

    // Print the output
    fmt.Println(string(stdout))
}
Sign up to request clarification or add additional context in comments.

6 Comments

Now the import has to be like "os/exec" and I got an error with the err.String() but apart from that, it works. Thanks.
@AlvaroSantisteban, thank you. I just upgrade the post as well as point links to the package and an example of use of exec.Command.
Is there a simple way to separate stderr from stdout. I see CombinedOutput(), and I see more complicated ways, but what I want is simply out, errout, errcode = cmd.Output3().
@cdunn2001, (1) #easy you can set the exec.Cmd.Stderr before call cmd.Output() by yourself or (2) #hard you add your function to golang ($GOROOT/src/pkg/os/exec/exec.go), recompile (cd $GOROOT/src && ./make.bash), test it.
This doesn't work for wildcards i.e. *. See the answer here to see how to handle wildcards.
|
97

None of the provided answers allow to separate stdout and stderr so I try another answer.

First you get all the info you need, if you look at the documentation of the exec.Cmd type in the os/exec package. Look here: https://golang.org/pkg/os/exec/#Cmd

Especially the members Stdin and Stdout,Stderr where any io.Reader can be used to feed stdin of your newly created process and any io.Writer can be used to consume stdout and stderr of your command.

The function Shellout in the following programm will run your command and hand you its output and error output separatly as strings.

As the parameter value is executed as a shell command, sanitize all external inputs used in the construction of the parameter value.

Probably don't use it in this form in production.

package main

import (
    "bytes"
    "fmt"
    "log"
    "os/exec"
)

const ShellToUse = "bash"

func Shellout(command string) (string, string, error) {
    var stdout bytes.Buffer
    var stderr bytes.Buffer
    cmd := exec.Command(ShellToUse, "-c", command)
    cmd.Stdout = &stdout
    cmd.Stderr = &stderr
    err := cmd.Run()
    return stdout.String(), stderr.String(), err
}

func main() {
    out, errout, err := Shellout("ls -ltr")
    if err != nil {
        log.Printf("error: %v\n", err)
    }
    fmt.Println("--- stdout ---")
    fmt.Println(out)
    fmt.Println("--- stderr ---")
    fmt.Println(errout)
}

10 Comments

Fantastic answer, this should be at the top. Having the ability to have a Golang error, stdout, and stderr clearly separated is the best combination available in this post.
Fantastic answer 2
I like this helper function for when you have a string and just want to use it as a command. Maybe not the safest thing to run in prod (maybe that's why the std lib approach uses varargs, not string), but useful for quick stuff. The only change I would suggest would be to re-arrange the return types so that error is last, which would be the Go convention for returning errors. VS Code complained about this to me when I copy and pasted this in.
I always thought code snippets here on stackoverflow are just examples, you should alter as you see fit. But you are right in all regards.
The most important point in my opinion: If the value for the command parameter is constructed from untrusted data, you really must sanitize it. Otherwise you are building a remote code execution flaw/bug/error.
|
13

This answer does not represent the current state of the Go standard library. Please take a look at @Lourenco's answer for an up-to-date method!


Your example does not actually read the data from stdout. This works for me.

package main

import (
   "fmt"
   "exec"
   "os"
   "bytes"
   "io"
)

func main() {
    app := "/bin/ls"
    cmd, err := exec.Run(app, []string{app, "-l"}, nil, "", exec.DevNull, exec.Pipe, exec.Pipe)

    if (err != nil) {
       fmt.Fprintln(os.Stderr, err.String())
       return
    }

    var b bytes.Buffer
    io.Copy(&b, cmd.Stdout)
    fmt.Println(b.String())

    cmd.Close()
}

2 Comments

@ChrisBunch might consider switching the checkmark as a service to the community.
What is a package named "exec"? Why don't you use "os/exec" from the standard library? And keep using variables like os.DevNull instead of your exec.DevNull
9
// Wrap exec, with option to use bash shell

func Cmd(cmd string, shell bool) []byte {

    if shell {
        out, err := exec.Command("bash", "-c", cmd).Output()
        if err != nil {
            panic("some error found")
        }
        return out
    } else {
        out, err := exec.Command(cmd).Output()
        if err != nil {
            panic("some error found")
        }
        return out
    }
}

you may try this .

3 Comments

Thanks qing this is a useful function for running miscellaneous commands via the shell, without having to split up all the args like in @Lourenco 's answer
Obviously this is no longer a cross-platform solution, but the question is specific to shell commands.
Note that if shell is false, arguments can't be passed to the command.
4
package main

import (
    "fmt"
    "os/exec"
)

func main() {
    cmd := exec.Command("cmd", "/C", "dir")
    output, err := cmd.Output()

    if err != nil {
        fmt.Println("Error executing command:", err)
        return
    }

    fmt.Println(string(output))
}

Use the exec.Command function to create a new cmd process with the /C flag and the dir command as its argument Capture output with output() method and print it.

Comments

3

Here is a simple function that will run your command and capture the error, stdout, and stderr for you to inspect. You can easily see anything that might go wrong or be reported back to you.

// RunCMD is a simple wrapper around terminal commands
func RunCMD(path string, args []string, debug bool) (out string, err error) {

    cmd := exec.Command(path, args...)

    var b []byte
    b, err = cmd.CombinedOutput()
    out = string(b)

    if debug {
        fmt.Println(strings.Join(cmd.Args[:], " "))

        if err != nil {
            fmt.Println("RunCMD ERROR")
            fmt.Println(out)
        }
    }

    return
}

You can use it like this (Converting a media file):

args := []string{"-y", "-i", "movie.mp4", "movie_audio.mp3", "INVALID-ARG!"}
output, err := RunCMD("ffmpeg", args, true)

if err != nil {
    fmt.Println("Error:", output)
} else {
    fmt.Println("Result:", output)
}

I've used this with Go 1.2-1.7

Comments

3

If you want run long-running script asynchronously with execution progress, you may capture command output using io.MultiWriter and forward it to stdout/stderr:

import (
    "fmt"
    "io"
    "os"
    "os/exec"
)

var stdoutBuf, stderrBuf bytes.Buffer

cmd := exec.Command("/some-command")

cmd.Stdout = io.MultiWriter(os.Stdout, &stdoutBuf)
cmd.Stderr = io.MultiWriter(os.Stderr, &stderrBuf)

err := cmd.Start()  // Starts command asynchronously

if err != nil {
    fmt.Printf(err.Error())
}

Comments

1

import (
    "github.com/go-cmd/cmd"
)

const DefaultTimeoutTime = "1m"

func RunCMD(name string, args ...string) (err error, stdout, stderr []string) {
    c := cmd.NewCmd(name, args...)
    s := <-c.Start()
    stdout = s.Stdout
    stderr = s.Stderr
    return
}

go test

import (
    "fmt"
    "gotest.tools/assert"
    "testing"
)

func TestRunCMD(t *testing.T) {
    err, stdout, stderr := RunCMD("kubectl", "get", "pod", "--context", "cluster")
    assert.Equal(t, nil, err)
    for _, out := range stdout {
        fmt.Println(out)
    }
    for _, err := range stderr {
        fmt.Println(err)
    }
}

Comments

0

I did not get the Rosetta example to work in my Windows Go. Finally I managed to go past the old format of the Subprocess with this command to start outfile in notepad in windows. The wait constant parameter mentioned in one manual did not exist so I just left out Wait as the user will close the program by themself or leave it open to reuse.

p, err := os.StartProcess(`c:\windows\system32\notepad.EXE`,
    []string{`c:\windows\system32\notepad.EXE`, outfile},
    &os.ProcAttr{Env: nil, Dir: "", Files:  []*os.File{os.Stdin, os.Stdout, os.Stderr}})

You would change the os.Stdout.. to os.Pipe as previous answer

EDIT: I got it finally from godoc os Wait, that Wait has changed to method of and I succeeded to do:

   defer p.Wait(0)

Then I decided finally to put

   defer p.Release()

instead.

Comments

0

I ended up doing this to get exit error code, command output and error:

parts := strings.Split("netstat -tupln", " ")
cmd := exec.Command(parts[0], parts[1:]...)
out, err := cmd.Output()
exitCode := cmd.ProcessState.ExitCode()

with the help from answers above (and other questions on stackoverflow), hope this helps someone.

Comments

0

Here's a great alternative using the cmdx library that makes executing commands and capturing output simpler and more intuitive:

package main

import (
    "github.com/kgs19/cmdx"
    "log"
)

func main() {
    command := "date"
    args := []string{"+%H:%M"}
    out, err := cmdx.RunCommandReturnOutput(command, args...)
    if err != nil {
        log.Fatalf("Error executing 'date' command: %v", err)
    }
    println("cmd output: " + out)
}

Explanation

  • cmdx.RunCommandReturnOutput(command, args...): This function runs the specified command with the given arguments and returns the output as a string.

For more information, check out the GitHub repository.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.