Use Output() to execute simple commands and obtain stdout output, suitable for scenarios without interaction; 2. Use CombinedOutput() to capture stdout and stderr at the same time, suitable for debugging or error troubleshooting; 3. Customize working directories and environment variables by setting Dir and Env fields to achieve a more flexible execution environment; 4. Use StdinPipe and stdout to read to implement interactive input and output with commands, suitable for scenarios where data needs to be input dynamically; 5. Use CommandContext to combine context.WithTimeout to implement timeout control to prevent unlimited command blocking; in summary, the os/exec package provides a complete external command execution solution from simple execution to complex interaction, and you can choose the appropriate method according to your needs.
In Go language, "command execution" usually refers to executing external commands (such as shell commands, system tools, etc.) through a program. Go's os/exec
package provides a powerful interface to achieve this. The following are several common examples to illustrate how to execute external commands in Go.

1. Execute simple commands and get output
Use exec.Command
to create a command and use Output()
method to get the standard output.
package main import ( "fmt" "log" "os/exec" ) func main() { cmd := exec.Command("ls", "-l") // on Linux/macOS // cmd := exec.Command("dir") // on Windows output, err := cmd.Output() if err != nil { log.Fatal(err) } fmt.Printf("Output:\n%s", output) }
? For: You want to run a command quickly and get its output without interaction.

2. Execute commands and handle errors (including stderr)
Output()
returns only stdout, and if the command errors (non-zero exit code), it returns an error. But the stderr content will not be included in the error unless you capture it explicitly.
A more flexible way is to use CombinedOutput()
:

package main import ( "fmt" "os/exec" ) func main() { cmd := exec.Command("go", "run", "noneexistent.go") output, err := cmd.CombinedOutput() if err != nil { fmt.Printf("Command execution failed: %v\n", err) } fmt.Printf("Output (including stderr):\n%s", output) }
? Suitable for: debugging or requiring both stdout and stderr to be captured.
3. Command execution with environment variables and working directory
You can customize the environment variables and run directories of the command.
package main import ( "fmt" "log" "os/exec" "os" ) func main() { cmd := exec.Command("pwd") // Set the working directory cmd.Dir = "/tmp" // Optional: Set environment variables (complete replacement) // cmd.Env = []string{"PATH=/usr/bin"} // Inherit the current environment and add the custom variable cmd.Env = append(os.Environ(), "MY_VAR=hello") output, err := cmd.Output() if err != nil { log.Fatal(err) } fmt.Printf("Execute pwd: %s under /tmp", output) }
4. Interactively execute commands (input/output stream)
When you need to enter data into a command (such as stdin
), you can use a pipeline.
package main import ( "fmt" "io" "log" "os/exec" ) func main() { cmd := exec.Command("grep", "hello") // Get stdin pipeline stdin, err := cmd.StdinPipe() if err != nil { log.Fatal(err) } // Start command if err := cmd.Start(); err != nil { log.Fatal(err) } // Write input io.WriteString(stdin, "hello world\n") io.WriteString(stdin, "goodbye world\n") stdin.Close() // Get the output output, _ := io.ReadAll(cmd.Stdout) cmd.Wait() // Wait for completion fmt.Printf("Match result:\n%s", output) }
? Suitable for: scenarios that need to interact with commands, such as grep
, bc
, custom CLI tools, etc.
5. Timeout control (avoid command stuck)
Use context
to control execution time to prevent unlimited waiting of commands.
package main import ( "context" "fmt" "log" "time" "os/exec" ) func main() { ctx, cancel := context.WithTimeout(context.Background(), 2*time.Second) defer cancel() cmd := exec.CommandContext(ctx, "sleep", "5") // Timeout will be interrupted err := cmd.Run() if err != nil { if ctx.Err() == context.DeadlineExceeded { fmt.Println("Command Timeout") } else { log.Printf("Command Error: %v", err) } } else { fmt.Println("Command completed successfully") } }
? Suitable for: Execute commands that are untrusted or may run for a long time.
Summary: Comparison of common methods
method | use |
---|---|
cmd.Output()
|
Get stdout, automatically handle startup and waiting |
cmd.CombinedOutput()
|
Get stdout stderr |
cmd.Start() manual management |
More finer control (input, concurrency, etc.) |
exec.CommandContext()
|
Support timeout or cancellation |
Basically these common uses. Go's os/exec
design is simple but complete, and is suitable for most automated scripts, CLI tools or system integration scenarios. The key is to choose the appropriate method based on whether you need input, timeout, environmental control, etc.
The above is the detailed content of go by example command execution. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

TointegrateGolangserviceswithexistingPythoninfrastructure,useRESTAPIsorgRPCforinter-servicecommunication,allowingGoandPythonappstointeractseamlesslythroughstandardizedprotocols.1.UseRESTAPIs(viaframeworkslikeGininGoandFlaskinPython)orgRPC(withProtoco

Golangofferssuperiorperformance,nativeconcurrencyviagoroutines,andefficientresourceusage,makingitidealforhigh-traffic,low-latencyAPIs;2.Python,whileslowerduetointerpretationandtheGIL,provideseasierdevelopment,arichecosystem,andisbettersuitedforI/O-bo

Golang is mainly used for back-end development, but it can also play an indirect role in the front-end field. Its design goals focus on high-performance, concurrent processing and system-level programming, and are suitable for building back-end applications such as API servers, microservices, distributed systems, database operations and CLI tools. Although Golang is not the mainstream language for web front-end, it can be compiled into JavaScript through GopherJS, run on WebAssembly through TinyGo, or generate HTML pages with a template engine to participate in front-end development. However, modern front-end development still needs to rely on JavaScript/TypeScript and its ecosystem. Therefore, Golang is more suitable for the technology stack selection with high-performance backend as the core.

The key to installing Go is to select the correct version, configure environment variables, and verify the installation. 1. Go to the official website to download the installation package of the corresponding system. Windows uses .msi files, macOS uses .pkg files, Linux uses .tar.gz files and unzip them to /usr/local directory; 2. Configure environment variables, edit ~/.bashrc or ~/.zshrc in Linux/macOS to add PATH and GOPATH, and Windows set PATH to Go in the system properties; 3. Use the government command to verify the installation, and run the test program hello.go to confirm that the compilation and execution are normal. PATH settings and loops throughout the process

Golang usually consumes less CPU and memory than Python when building web services. 1. Golang's goroutine model is efficient in scheduling, has strong concurrent request processing capabilities, and has lower CPU usage; 2. Go is compiled into native code, does not rely on virtual machines during runtime, and has smaller memory usage; 3. Python has greater CPU and memory overhead in concurrent scenarios due to GIL and interpretation execution mechanism; 4. Although Python has high development efficiency and rich ecosystem, it consumes a high resource, which is suitable for scenarios with low concurrency requirements.

To build a GraphQLAPI in Go, it is recommended to use the gqlgen library to improve development efficiency. 1. First select the appropriate library, such as gqlgen, which supports automatic code generation based on schema; 2. Then define GraphQLschema, describe the API structure and query portal, such as defining Post types and query methods; 3. Then initialize the project and generate basic code to implement business logic in resolver; 4. Finally, connect GraphQLhandler to HTTPserver and test the API through the built-in Playground. Notes include field naming specifications, error handling, performance optimization and security settings to ensure project maintenance

The choice of microservice framework should be determined based on project requirements, team technology stack and performance expectations. 1. Given the high performance requirements, KitEx or GoMicro of Go is given priority, especially KitEx is suitable for complex service governance and large-scale systems; 2. FastAPI or Flask of Python is more flexible in rapid development and iteration scenarios, suitable for small teams and MVP projects; 3. The team's skill stack directly affects the selection cost, and if there is already Go accumulation, it will continue to be more efficient. The Python team's rash conversion to Go may affect efficiency; 4. The Go framework is more mature in the service governance ecosystem, suitable for medium and large systems that need to connect with advanced functions in the future; 5. A hybrid architecture can be adopted according to the module, without having to stick to a single language or framework.

sync.WaitGroup is used to wait for a group of goroutines to complete the task. Its core is to work together through three methods: Add, Done, and Wait. 1.Add(n) Set the number of goroutines to wait; 2.Done() is called at the end of each goroutine, and the count is reduced by one; 3.Wait() blocks the main coroutine until all tasks are completed. When using it, please note: Add should be called outside the goroutine, avoid duplicate Wait, and be sure to ensure that Don is called. It is recommended to use it with defer. It is common in concurrent crawling of web pages, batch data processing and other scenarios, and can effectively control the concurrency process.
