- Forum
- Windows Programming
- How to start a process and make it 'inde
How to start a process and make it 'independent'
Assuming I've got these two facts right :-
CreateProcess() starts a process and lets your program continue while it runs, but when your program finishes, the child process goes down with it. Furthermore, your program has to take note of when the child process exits so that it can properly release the process handle.
system() starts a process, waits for it to complete then continues with your program.
- what I need to know is how to start a process and let it run independently of my program, and persist after my program exits. I don't need to capture its output or have any further control over it, I just want to let the user interact with it - like say I wanted to write an alternative to the Start Menu Run command.
So is it, please, actually possible to do that?
CreateProcess() starts a process and lets your program continue while it runs, but when your program finishes, the child process goes down with it. Furthermore, your program has to take note of when the child process exits so that it can properly release the process handle.
system() starts a process, waits for it to complete then continues with your program.
- what I need to know is how to start a process and let it run independently of my program, and persist after my program exits. I don't need to capture its output or have any further control over it, I just want to let the user interact with it - like say I wanted to write an alternative to the Start Menu Run command.
So is it, please, actually possible to do that?
CreateProcess() does not wait for child process to finish by default, it returns immediately. Use WaitForSingleObject if you want to wait.
No, the child process is not killed automatically when parent exists, and the handle is anyway freed automatically by the operating system, not need to do it yourself (if you use a modern version of windows).
No, the child process is not killed automatically when parent exists, and the handle is anyway freed automatically by the operating system, not need to do it yourself (if you use a modern version of windows).
Just like any OS resource(gdi objects, user objects, kernel objects), if you don't destroy/release/close the resource yourself then you will have resource leaks while your application runs. You should close both handles returned from CreateProcess soon after CreateProcess returns.
Ok thanks. Looks like I need to experiment more with CreateProcess as I haven't understood it totally.
Topic archived. No new replies allowed.