Re: openssh refuses to close if open stderr/stdout/stdin
From: Bill Unruh (unruh@string.physics.ubc.ca)Date: 04/25/02
- Next message: Richard E. Silverman: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Previous message: Neil W Rickert: "Re: ssh working as designed?"
- In reply to: Nico Kadel-Garcia: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Next in thread: Richard E. Silverman: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Reply: Richard E. Silverman: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: unruh@string.physics.ubc.ca (Bill Unruh) Date: 24 Apr 2002 22:37:54 GMT
"Nico Kadel-Garcia" <nkadel@bellatlantic.net> writes:
]"Bill Unruh" <unruh@string.physics.ubc.ca> wrote in message
]news:aa1iln$inh$1@nntp.itservices.ubc.ca...
]> Open ssh has changed the default in that it will refuse to close if
]> there are any programs which still have open ports (eg stderr, stdout,
]> stdin) through the link. This is a change in the procedures, and is a
]> real real pain in the but, since a lot of programs are badly written and
]> leave one of those ports dangling even if put into the background. This
]> hangs the closing of ssh.
]>
]> Is there some variable I can set or some configuration I can do to get
]> the old behaviour back again. It would be OK if it warned me about open
]> ports, but it should then tell me which programs, and I should be able
]> to shut the ssh link anyway if I want to.
]>
]> The current behaviour is terrible.
]But it was important. If you closed the programs immediately, they might
]leave interesting dangling jobs running that would be a problem later, or
]have problems with wanting to send something important to stdout and stderr
]that was unsafe not to cope with.
Maybe, but the current situation is intolerable. The session closes, so
you cannot do anything on it anymore, like killing the bad program. But
it is not closed, so the connection is kept up. It makes no report as to
why it is being kept open (like which program it is waiting for).
For example, mount will hold open a connection. It has detached itself
from teh controlling terminal, but somehow it has not let go properly as
far as ssh is concerned. A bug where you have to fix thousands of other
programs is just very bad program design. Once you type exit, it could
at least give you the option of nastily closing the dangling
connections. Instead you are stuck, except for going to another screeen
and killing the ssh connection.
]You've got a couple of user level options.
] 1: Redirect stdin/stdout/stderr to /dev/null when needed.
] 2: Run "screen" for interactive sessions, which will allow you to type
]"exit" and leave the session alive until the shell terminates, but detach
]from the screen process.
Sure I can also write messages on a piece of paper and put them into a
bottle in the ocean. Computers are supposed to make things easier, not
put roadblocks in your way.
You usually have no idea as to "when needed". some program happens to
keep stdin open just because the programmer forgot. and there you are
with some unkown programming hanging up the session.
I am sorry but the current implimentation leaves much to be desired.
- Next message: Richard E. Silverman: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Previous message: Neil W Rickert: "Re: ssh working as designed?"
- In reply to: Nico Kadel-Garcia: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Next in thread: Richard E. Silverman: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Reply: Richard E. Silverman: "Re: openssh refuses to close if open stderr/stdout/stdin"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
