http://www.mynitor.com/2010/02/28/daemonize-any-process-in-linux/ When the real business don't work out, make it a blog. Thu, 19 Jan 2012 15:03:35 +0000 hourly 1 http://wordpress.org/?v=3.3 http://www.mynitor.com/2010/02/28/daemonize-any-process-in-linux/comment-page-1/#comment-252 criptych Sat, 12 Jun 2010 16:06:20 +0000 http://www.mynitor.com/?p=691#comment-252 There's also "daemon," which does the same thing (pretty much) and with less typing. :) There’s also “daemon,” which does the same thing (pretty much) and with less typing.

]]> http://www.mynitor.com/2010/02/28/daemonize-any-process-in-linux/comment-page-1/#comment-230 sigquit Thu, 25 Mar 2010 02:55:34 +0000 http://www.mynitor.com/?p=691#comment-230 [...] on Mon [...] Leave a Reply. Name (required) Mail (will not be published) (required) Website ...Daemonize any process in LinuxProcesses run by nohup are immnue to SIGHUP and SIGQUIT signals. By using nohup, it releases the [...] [...] on Mon [...] Leave a Reply. Name (required) Mail (will not be published) (required) Website …Daemonize any process in LinuxProcesses run by nohup are immnue to SIGHUP and SIGQUIT signals. By using nohup, it releases the [...]

]]> http://www.mynitor.com/2010/02/28/daemonize-any-process-in-linux/comment-page-1/#comment-212 Links 1/3/2010: New Linux Benchmarks ARM Development Studio for Linux | Boycott Novell Tue, 02 Mar 2010 01:17:18 +0000 http://www.mynitor.com/?p=691#comment-212 [...] Daemonize any process in Linux [...] [...] Daemonize any process in Linux [...]

]]> http://www.mynitor.com/2010/02/28/daemonize-any-process-in-linux/comment-page-1/#comment-210 GoblinX Project » GoblinX Newsletter, Issue 239 (03/01/2010) Mon, 01 Mar 2010 12:12:52 +0000 http://www.mynitor.com/?p=691#comment-210 [...] Daemonize any process in Linux [...] [...] Daemonize any process in Linux [...]

]]> http://www.mynitor.com/2010/02/28/daemonize-any-process-in-linux/comment-page-1/#comment-209 orkan Mon, 01 Mar 2010 07:07:29 +0000 http://www.mynitor.com/?p=691#comment-209 isn't it better to use "screen" for such purposes? you can have multiple screens with environments for each of the tasks and you can control the output of all of them isn’t it better to use “screen” for such purposes? you can have multiple screens with environments for each of the tasks and you can control the output of all of them

]]>