search for: chan_init_iost

...t;sock, c->istate, c->ostate, strerror(errno)); } Although the self and sock fields vary, ostate is 128 and istate is 1 in the warning messages. ======================================== Where does ostate get set? ---------------------------------------- grep ostate *.c *.h channels.c: chan_init_iostates(c); channels.c: if (ch->ostate == CHAN_OUTPUT_OPEN || channels.c: ch->ostate == CHAN_OUTPUT_WAIT_DRAIN) { channels.c: } else if (ch->ostate == CHAN_OUTPUT_WAIT_DRAIN) { channels.c: debug...

The command "ssh ls -l /doesnotexist" gives various responses: Running from a 200 MHz PentiumPro with dsa key added to ssh-agent: Mistakes worst to fast machine: To a faster 600 MHz dual processor i686 600 MHz machine: ls: /doesnotexist: No such file or directory -- correct nothing at all -- wrong ls: select: Bad file descriptor -- wrong

I am running OpenSSH 2.9p1 on SunOS 5.7 w/4-24-2001 patch cluster. Like many other users I am seeing the hanging session on logout with background processes. This is a huge problem for me as I centrally manage 50+ machines with rdist across ssh. Instead of just complaining about the problem I thought I would put my CS degree to use and try to track down the problem myself. For starters,

.../* * we have to remove the fd's from the select mask diff -u openssh-2.9.9p2/channels.h openssh-2.9.9p2J/channels.h --- openssh-2.9.9p2/channels.h Mon Sep 17 23:51:14 2001 +++ openssh-2.9.9p2J/channels.h Thu Sep 27 22:16:44 2001 @@ -219,6 +219,7 @@ void chan_mark_dead(Channel *); void chan_init_iostates(Channel *); void chan_init(void); +void chan_shutdown_read(Channel *); typedef void chan_event_fn(Channel *); diff -u openssh-2.9.9p2/clientloop.c openssh-2.9.9p2J/clientloop.c --- openssh-2.9.9p2/clientloop.c Mon Sep 17 23:51:14 2001 +++ openssh-2.9.9p2J/clientloop.c Fri Sep 28 12:4...

In the changelog, there is an entry: 20001129 - (djm) Back out all the serverloop.c hacks. sshd will now hang again if there are background children with open fds. Does this mean that this is regarded as expected (and correct) behavior, that should not change in the future, or does it mean that this behavior is a known problem that someone will eventually fix? --Adam -- Adam McKenna

...])(c, readset, writeset); + } channel_garbage_collect(c); } } diff -ur openssh-3.0p1/channels.h openssh-3.0p1J/channels.h --- openssh-3.0p1/channels.h Thu Oct 11 19:35:06 2001 +++ openssh-3.0p1J/channels.h Tue Nov 13 15:55:52 2001 @@ -218,6 +218,7 @@ void chan_mark_dead(Channel *); void chan_init_iostates(Channel *); void chan_init(void); +void chan_shutdown_read(Channel *); typedef void chan_event_fn(Channel *); diff -ur openssh-3.0p1/clientloop.c openssh-3.0p1J/clientloop.c --- openssh-3.0p1/clientloop.c Thu Oct 11 19:36:09 2001 +++ openssh-3.0p1J/clientloop.c Tue Nov 13 16:06:36 20...

Hi OpenSSH developers, I am using openSSH (now 2.9.9p2, but prob occurs in 2.9p2 also) to execute commands on a remote machine which outputs data to stdout then pipes it to another invocation of ssh which connects back to the first machine in the same way, where it starts a program to read and store the output from the command on the second machine. I am using the "command" option in