The file handle of the parent process will be leaked to the child process

[today2014]

use github.com/go-cmd/cmd I wrote a daemon process
Start my own program run linux, the code is as follows:
cmdx.SetConfig(cmdx.Config{CommandDir: “/app/mysvr/bin”)
if err := cmdx.RunCommandPrintOutput("./mysvr", "-d"); err != nil {
log.Fatalf("Command failed: %v", err)
}

My daemon process uses file locks to prevent multiple instances from running,the my daemon has exited. After the mysvr daemon runs in the background, the file handle of the daemon's file lock leaks into mysvr.
Could you please advise on any good solutions?

[daniel-nichter]

You sure this is the correct package? This package doesn't have SetConfig or RunCommandPrintOutput.

[today2014]

You sure this is the correct package? This package doesn't have SetConfig or RunCommandPrintOutput.

sorry I tested several libraries at the same time and sent the wrong code
cmd.NewCmd("./mysvr", "-d")
}

[daniel-nichter]

Without seeing nearly all the code (i.e. your code, not go-cmd), it's nearly impossible to debug. File handles don't leak across processes; a file handle is a per-process resource. It might be related to the process group, but go-cmd terminates the whole process group by default. But that won't stop a child process from forking into a new process group. So there's a lot that could be going on under the hood. You'll probably need to step through things with a debugger and watch how the parent and child processes behave (i.e. with ps, /proc, and such). Or, if you can create a reproducible test case, that'd be best.