nim-daemon
nim-daemon copied to clipboard
advantage over using poDemon with startProcess?
would be nice to make that clear in readme.md
First of all poDemon inside of osproc.nim is different.
So if you will use nim-daemon on Windows, it will start clone of your process which will be running on background, detached from console, so it will be almost equal to Unix daemonization, while Nim's osproc is just creates new process without console window, and it will be terminated when parent exits.
ok thanks; how about on posix (osx, linux)?
On Posix systems it uses old algorithm of daemonization, so your process will be detached from parent, which execute it and will continue running in the background, while poDemon is starts new process group, and then execv this new process (so nim-daemon achieves same result, but with less number of syscalls - only one fork()).
So main use-case of poDemon inside of osproc.nim is to start new custom process detached from parent. While nim-daemon is library which allow to detach your own process from parent.
thanks! these answers would be great in the repo's readme.md