This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.21: rxvt fails to shutdown due to ssh -f still running

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

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: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]