Mail Archives: cygwin/2006/10/11/09:47:38
Igor Peshansky wrote:
> On Wed, 11 Oct 2006, Michael Hoffman wrote:
>
>> When I log out of or shutdown my Windows login session, if I had a
>> background process that I started within a Win32 rxvt session, I get an
>> error that rxvt00000<some other hex numbers> has not shut down. For
>> example if I use ssh -f or run ssh in the background using &, this
>> symptom manifests.
>>
>> I can also see a related symptom if I am running using a Windows
>> console. When I log out of bash, the console window will stick around
>> until the ssh process is killed.
>>
>> I would like for these console windows and hidden rxvt windows to shut
>> down without further confirmation. Is there a way to do this? Or a good
>> workaround?
>>
>> I have Googled for this problem, and while I have found other related
>> problems (such as ssh-agent continuing to run) I have not found any
>> solutions for this case.
>
> "man nohup", "man setsid", in bash: "help disown".
Thanks, setsid works fine if I do not need to enter a password but
unfortunately will not work if I am using ssh -f to get an interactive
password before forking.
Looking in the openssh source, I can see that ssh -f calls daemon(),
which should call setsid(). Is that correct? If so, why is it still
hanging onto the terminal?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -