similar to: hang on exit

My apologies Nico, I overlooked the fact that your post was not to the list since most I receive are cc'd to me. You have my sincere apology for the public re-posting of your private comments. > > I expect private e-mail to stay private. Particularly if I'm > helping someone who I'm not required to help. It seems that you > think that I'm obligated to you. > I have

> > Yes, you can "police" these things as a sysadmin. How? Use > /usr/proc/bin/ptree, ps, lsof and what not to find all sshd > processes and their associated ptys - the sshds that have no > children processes but whose master pty's slave pty still has > processes associated with said pty, those are the sshds that must be > killed in order to clean up (or you

so, should this go into 3.5? Index: serverloop.c =================================================================== RCS file: /home/markus/cvs/ssh/serverloop.c,v retrieving revision 1.103 diff -u -r1.103 serverloop.c --- serverloop.c 24 Jun 2002 14:33:27 -0000 1.103 +++ serverloop.c 12 Jul 2002 16:34:20 -0000 @@ -388,6 +388,11 @@ buffer_append(&stderr_buffer, buf, len); } } + /*

>From what I understand, the problem is due to people's disagreement about what the "correct" behavior should be. I'm pretty sure that the following is the correct behavior from running rsh and ssh often (both fsecure and openssh). Lets say you have a stupid script that does while 1 do sleep 1 done Called foreverSleep on your remote host: rsh remotehost

Ok, so I think I have a complete explanation for the difference between the *BSD behaviour and the Linux/Solaris behaviour. Well, almost complete :) Pull out your trusty copies of "The Design and Implementation of the 4.4BSD Operating System" as well as "Unix Internals: The New Frontiers". Specifically, pages 111-112 and 344 of the former and page 108 of the latter. It comes

Here is a simpler patch (based on Markus Friedl's suggestion posted to this list) to OpenSSH-3.0.2p1 to fix the hang-on-exit bug (Protocol 2 only). To date, no data loss has been reported with this patch: it does not break ssh or scp. This patch should make OpenSSH work on all operating systems exactly as it does under FreeBSD. This patch and others are maintained on the

Attached is a very small patch that allows the ssh clients to use the socks5 library. It should work with socks4 but is untested. Tested on linux only configure --with-socks configure --with-socks5 Also included is a configure option to disable scp statistics --disable-scp-stats modified files openssh-2.9.9p2/acconfig.h openssh-2.9.9p2/channels.c openssh-2.9.9p2/configure.in

Sir/Madam, I am a graduate student in Petroleum Engineering. I have a problem in using R and hope that you could help in solving that. I have a code in C, which displays orthogonal arrays when I give number of rows and number of columns to it. I have another code in R that calls this C code. I am very new to R. I downloaded the R and loaded packages base and mva. I also kept my C code .exe

The hang-on-exit bug still hasn't been fixed in OpenSSH-3.0p1... :-( Here again is the patch to fix this bug under Linux, updated for OpenSSH-3.0p1. This has been exhaustively tested for six months now. It also add an exit delay option that can be useful. The patch does not lead to data loss under Linux. Please see the Secure NFS page (SNFS) for further details:

I have two identical installations of samba v2.25 on linux boxes. On one system everything works fine but on the other, copies of smbd start but never terminate. The result is that the winduhs boxes that are trying to access the samba share get locked out and never find the samba server. The configurations of the two systems are identical and I am unable to determine why one works and the other

http://bugzilla.mindrot.org/show_bug.cgi?id=52 imaging at math.ualberta.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #801 is|0 |1 obsolete| | ------- Comment #18 from imaging at math.ualberta.ca 2006-02-22 16:24

Hi, I use openssh-2.9p2 on LynxOS i386 system. sshd runs on LynxOS and ssh client on Redhat 7.0 Linux system (openssh-2.9p2 ssh client). The ssh client hangs on exit 90% of times. I don't think this is the usual hang-on-exit bug, because, there are no background processes running, I suppose. I attach the server debug messages. $ssh -V hari at lynx (From Linux) ... Password: ... lynx>

http://bugzilla.mindrot.org/show_bug.cgi?id=36 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|openssh-unix-dev at mindrot.org|markus at openbsd.org ------- Additional Comments From markus at openbsd.org 2001-12-29 00:35 ------- i'll look into this

The hang on exit has become quite an issue in my organization(Sun and HP hosts). I see this note in the changelog which indicates that there will not be a fix for this problem: 20001129 - (djm) Back out all the serverloop.c hacks. sshd will now hang again if there are background children with open fds. Also, I am aware of the workaround as noted in the FAQ. However this workaround is not

On Mon, 8 Oct 2001, Markus Friedl wrote: > Date: Mon, 8 Oct 2001 23:12:41 +0200 > From: Markus Friedl <markus at openbsd.org> > To: Ed Phillips <ed at UDel.Edu> > Subject: Re: ssh hangs instead of exiting > > On Mon, Oct 08, 2001 at 05:07:12PM -0400, Ed Phillips wrote: > > On Mon, 8 Oct 2001, Markus Friedl wrote: > > > > > Date: Mon, 8 Oct 2001

When should sshd disconnect an SSHv2 connection? Markus Friedl says "for protocol v2 the client decides when to close the connection." In principle, I agree, because SSHv2 supports multiple sessions over the same connection, with the client able to launch new sessions anytime then it should be upto the client. But this would be a major cultural change for most users, and would break

I have just uploaded a new snapshot to http://www.mindrot.org/misc/openssh/ Snapshot production is now automated - new snapshots will be made at about 4:30 am (Australian Eastern time) and will be available from the URL above. This snapshot consists of mainly minor fixes over the previous. The race when sshd exits which was causing data loss (as evidenced by "ssh localhost dd

http://bugzilla.mindrot.org/show_bug.cgi?id=52 ------- Additional Comments From djm at mindrot.org 2002-01-23 17:37 ------- This is a known issue and has been discussed extensively on the mailings list. There is difference of opinion as to whether this is a bug or whether it is correct behaviour. A good description of the issue comes from a text file in Redhat's source RPM:

Hello, my name is Gregor and I''m new to this list and to wxRuby/wxDialogs. That''s why I wanted to introduce myself shortly. I''m a Ruby fan for 2 years now and I''m doing a lot of web development with Rails and a little Camping and I''m currently writing my Master''s Thesis around Ruby. You may follow my thoughts on my blog www.nach-vorne.de if

When I run this command: ssh -1 -v -n -l root njdb1b /usr/bin/X11/xterm -sb -sl 1000 -T njdb1b -e find /etc An xterm appears on my screen, the contents of /etc scroll by and then ssh exits. When I invoke the same command with the -2 option, the xterm appears (and disappears) but ssh never exits. netstat says the (ssh) connection is still established but the xterm is no longer