Stas Bekman wrote: > > 1. Start the long running process (runs indefinitly for the > > purpose of this test), which closes STDOUT, STDIN and > > STDERR and then calls setsid(). > > Why do you call setsid()? He's probably thinking of traditional the traditional way in which you background a daemon by forking, setsid'ing, then forking again to prevent the process from ever reacquiring a controlling terminal (your point, that this isn't needed here, is well taken). -- Richard Goerwitz [EMAIL PROTECTED]
- Re: fork inherits socket co... Stas Bekman
- Re: fork inherits socket co... Kees Vonk 7249 24549
- Re: fork inherits socket co... Stas Bekman
- Re: fork inherits socket co... Kees Vonk 7249 24549
- Re: fork inherits socket co... Stas Bekman
- Re: fork inherits socket connec... Rafael Caceres
- Re: fork inherits socket co... Stas Bekman
- Re: fork inherits socket co... Bill Moseley
- Re: fork inherits socket co... Bill Moseley
- Re: fork inherits socket connection Vivek Khera
- Re: fork inherits socket connection Richard L. Goerwitz
- Re: fork inherits socket connection G.W. Haywood
- Re: fork inherits socket connection Vivek Khera