similar to: OpenSSH (1.2.3) sshd hanging when using rsync over ssh (retry)

comments? alternatives: sigsetjmp(ugly) and pselect(not portable, available) drawback: additional filedescriptors. Index: serverloop.c =================================================================== RCS file: /home/markus/cvs/ssh/serverloop.c,v retrieving revision 1.82 diff -u -r1.82 serverloop.c --- serverloop.c 10 Oct 2001 22:18:47 -0000 1.82 +++ serverloop.c 11 Oct 2001 18:06:33 -0000 @@

On Thu, 2006-03-16 at 01:01 +0000, Guy Helmer <ghelmer@palisadesys.com> wrote: > David Wolfskill wrote: > > I'm running: > > > > localhost(6.1-P)[21] uname -a > > FreeBSD localhost 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #19: > Wed Mar 15 07:15:25 PST 2006 >

Still chasing a hang that has dogged me for quite some time. This time I noticed the console logging output showed that processing stopped right on the five-minute interval when cron would have kicked off bsdsar, which in turn ran vmstat. The system is a Supermicro P4PDE motherboard with dual Xeons and hyperthreading enabled. Kernel debugging results are available at

Please review the function below, forkoff(), meant to be used in clientloop.c instead of daemon() and the code in process_escapes(). The intention is to make ~D ( like ~& but also detach) possible and to make it possible for ssh -f (or ssh -f -f - see other thread on this) to detach, not just forkoff(). I also intend to use the same detach technique in a feature patch for the hang-on-exit

Hello, it's me again ! I tried to compile / install OpenSSH on our Reliant UNIX system, OS version 5.45 (and 5.44). The following problems did appear: 1. OpenSSL-0.9.5a will not compile out of the box. The problem on RU 5.45 is, that the compiler does support "long long" but NOT "unsigned long long". The latter just provokes the error message "superfluous

Hi, stevesk at sweden.hp.com wrote: > Has any progress been made on this issue? I've included an older > message that has a stack trace, which if I recall was still the same in > 2.1.1p1. I can provide a newer trace or additional information if > needed. not really... On a non-trusted system with HP AnsiC it seems to work if changing shutdown(fdin, SHUT_WR) to shutdown(fdin,

Background ========== "ssh -f ..." causes ssh to fork into the background when userauth successfully completes. WHAT === With this patch "ssh -f -f ..." causes ssh to fork into the background when the first forwarded port/x11 display/agent is successfully opened. WHY === This feature makes launching remote X11 apps more reliable: when ssh exits it must have exited because

We have just installed Samba 1.9.18p10 on an Ultra Sparc, Solaris 2.5.1 . So far we have been very impressed with the resilience and performance of Samba in contrast to Hummingbird and Solstice NFS products while doing large product builds on our NT4.0 sp4 machines. However we have come across one little problem, which may be down to configuration, that has left us "worried" about

http://bugzilla.mindrot.org/show_bug.cgi?id=241 Summary: When I kill scp, the underlying ssh child process remains alive Product: Portable OpenSSH Version: 3.1p1 Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P3 Component: scp AssignedTo: openssh-unix-dev

I have a strange problem with sshd (from openssh-2.9p2) on Solaris 7. My shell is bash. When I open an ssh session , and type a Control-C to bash's prompt, the shell hangs. (But, if I for instance run "sleep 10" (during which time the pty is in cooked mode) and press Control-C, the sleep command is interrupted quite normally, and the bash prompt returns.) Adding some debugging

Markus, How's this patch? - a chan_wont_read()/chan_wont_write() API is added that is very much like chan_read_failed()/chan_write_failed(), but for the debug messages and chan_wont_*() don't ever call error() The 3.0.2p1 channel_pre_x11_open() uses chan_*_failed() but looks like it ought to use chan_wont_*() instead :) - forkoff() no longer fakes EOF for SSHv2 (still

I'm curious how to go about submitting a suggestion that affects both the original BSD version and the portable release. A few days ago I sent off a BSD-relative patch to openssh at openssh.com. Is this the right thing to do? I didn't hear anything back, but it's only been 3 days, so I'm probably just being too antsy. In the meantime, maybe someone else out there would like to

I think my first send was eaten by elm.. Yuck I hate this programm.. Anyawys, first the disclaimer: This is barely tests, I submit this to the general population, but I will not submit this for review of rest of the OpenSSH team. Mainly because it is horrible at best. dealing with alarm() in a sane way is not fun. It does not compile clean, but works. IF anyone cares to clean it up..

Again, this has been lightly tested. I think there still are a few glitchs. 1. stole progressmeter() from scp.c - clean up and simplified a little to remove the 'flag' status. It now understands how to initialize itself and how to terminate itself. Along with a malloced status bar instead of the original fix width bar. 2. removed all initialization code from scp.c for progressmeter()

Hello, I figured it out, in short, winbind rocks. For some reason, I did not see the point of specifying nss_winbind in /etc/nsswitch.conf. Now that I did that I can use the UIDs/GIDs mapped for my system by winbindd for perms. Using winbind this way eliminates the need to create local Unix accounts :) Awesome. I'm not sure why I didn't realize this before ( maybe because the other

I'd like a feature whereby ssh puts itself in the background after the first successful X11 (or other port) forwarding. The reason for this is simple: error handling. If the application fails to open the X display and exits, then the client can still exit with the application's exit code. But if the application opens the X display successfully, then it can just display any errors by

This is the LAST version I plan on doing.. If I hear no feed back good or bad. Then I'll assume I've wasted my time on a feature that people whine about but don't care to try. This is against 3.0.2pX so it should be VERY easy for anyone to test. - Ben diff -ur openssh-3.0.2p1/misc.c openssh/misc.c --- openssh-3.0.2p1/misc.c Tue Jul 3 23:46:58 2001 +++ openssh/misc.c Wed Feb 6

Hi, I'm a newbie to openssh and was trying to read the source code recently. Could anyone tell me why in sshd the connection_in and connection_out are the same(seems to be integer 3 in my machine). connection_in is used in process_input(readset), and connection_out is used in process_output(writeset); But how does it work if it tries to read and write from the same file descriptor? /Bob

Dear R people, I wonder how to hide tick lines behind other figures in a plot, e.g. in a boxplot. # Sample code: x<- c(rep(4,50),rep(5,20),rep(6,50),rnorm(20,5,1)) boxplot(x) axis(2,tck=1,col.ticks='grey',lty=5 ) # end of sample code The tick lines is put on top of the box-plot, but I would like to put these lines behind the box and whiskers.. Regards Helmer

this (uncomplete) patch makes various features compile time options and saves up to 24K in the resulting ssh/sshd binaries. i don't know whether this should be added to the CVS since it makes the code less readable. perhaps WITH_COMPRESSION should be added, since it removes the dependency on libz -m Index: Makefile.inc =================================================================== RCS