


How to Execute a Command in Go and Detach It from the Parent Process?
Run Command in Go and Detach It from Process
In Go, you can execute a command in a detached manner, allowing it to run independently of your program. Here's how you can achieve this:
Code:
<code class="go">package main import ( "fmt" "log" "os" "os/exec" "strconv" "syscall" ) func main() { // Define the command and its arguments cmd := exec.Command("sleep", "120") // Set up the pipes for stdout and stderr stdoutPipe, err := cmd.StdoutPipe() if err != nil { log.Fatal(err) } stderrPipe, err := cmd.StderrPipe() if err != nil { log.Fatal(err) } // Start the command if err := cmd.Start(); err != nil { log.Fatal(err) } // Get the process ID (PID) of the child process pid := cmd.Process.Pid // Print the PID fmt.Printf("PID: %d\n", pid) // Read from the stdout and stderr pipes and log the output go func() { for { buf := make([]byte, 1024) n, err := stdoutPipe.Read(buf) if err != nil { log.Fatal(err) } fmt.Printf("stdout: %s", string(buf[:n])) } }() go func() { for { buf := make([]byte, 1024) n, err := stderrPipe.Read(buf) if err != nil { log.Fatal(err) } fmt.Printf("stderr: %s", string(buf[:n])) } }() // Wait for the command to finish if err := cmd.Wait(); err != nil { if exitErr := cmd.ProcessState.Sys().(syscall.WaitStatus).ExitStatus(); exitErr != 0 { log.Fatal(fmt.Sprintf("Error #48692663: Command exited with code %d", exitErr)) } else { log.Printf("Command exited with exit code 0") } } // Optionally, keep the child process alive even after the parent process exits // This can be achieved by setting `cmd.SysProcAttr = &syscall.SysProcAttr{Setpgid: true}` before starting the command. // Example of sending a signal to the detached process if err := syscall.Kill(pid, os.Interrupt); err != nil { log.Fatalf("Error sending signal to process: %d: %s", pid, err) } else { fmt.Printf("Received ^C and forwarded to process %d\n", pid) } // Optionally, use `syscall.Reap()` to clean up any child processes that are terminated but not yet waited for. }</code>
This code demonstrates how to execute a command in a detached manner, allowing it to continue running independently of the parent process. It provides features such as capturing stdout and stderr, obtaining the process ID, and optionally sending signals to the child process.
Key Considerations:
- Note that detaching a process does not prevent it from becoming orphaned upon the exit of its parent, as the kernel still holds a reference to it.
- Using SysProcAttr.Setpgid can keep the child process alive independently, but it may require additional handling in certain cases.
- Be sure to use Wait() to ensure that the process returns an exit code and you can handle any potential errors.
- Use syscall.Reap() to clean up zombie processes to avoid resource leaks.
The above is the detailed content of How to Execute a Command in Go and Detach It from the Parent Process?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

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

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

Undress AI Tool
Undress images for free

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

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...
