Stas Bekman wrote:
> But you don't need to call setsid() when you fork. Why looking for
> complicated workaround when you can do it properly without any workaround.
> Have you ever seen an example of fork that uses setsid?
>
But your Guide says:
----
A much better approach would be to spawn a sub-process, hand it the
information it needs to do the task, and have it detach (close STDIN, STDOUT
and STDERR + execute setsid()).
----


Reply via email to