search for: channel_stop_listening

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the

...0, max_fd, status; pid_t pid; + int fd; debug("Entering interactive session for SSH2."); *************** *** 736,742 **** xfree(writeset); signal(SIGCHLD, SIG_DFL); ! while ((pid = waitpid(-1, &status, WNOHANG)) > 0) session_close_by_pid(pid, status); channel_stop_listening(); } --- 737,745 ---- xfree(writeset); signal(SIGCHLD, SIG_DFL); ! while ((fd = channel_find_open()) >= 0) ! channel_free(fd); ! while ((pid = waitpid(-1, &status, 0)) > 0) session_close_by_pid(pid, status); channel_stop_listening(); }

...() function below does that, I think, but it would be nice to have confirmation. Comments? Nico static void forkoff(int stop_listening, int detach) { pid_t pid; int fd; Channel *c; /* Restore tty modes. */ leave_raw_mode(); /* Stop listening for new connections. */ if (stop_listening) channel_stop_listening(); fprintf(stderr, "Forking off into the background - %s", stop_listening ? "no longer listening" : "still listening"); /* Fork into background. */ pid = fork(); if (pid < 0) { error("fork: %.100s", strerror(errno)); return; } if (pid != 0) {...

Hi, protocolkeepalives sends ssh_msg_ignore, which the ssh2 server handles incorrectly (i.e. it produces some output to syslog, instead of ignoring the packet): Jul 9 11:58:07 ren sshd[16580]: error: Hm, dispatch protocol error: type 32 plen 4 This patch implements a highly advanced function to ignore these packets ;) Matthew -------------- next part -------------- An embedded and

...e to serve connections, + * but put in background and no more new connections). + */ +static +void +forkoff(int stop_listening, int detach) +{ + pid_t pid; + int fd; + Channel *c; + + /* Restore tty modes. */ + leave_raw_mode(); + + /* Stop listening for new connections. */ + if (stop_listening) + channel_stop_listening(); + + fprintf(stderr, "Forking off into the background - %s", + stop_listening ? "no longer listening" : "still listening"); + + /* Fork into background. */ + pid = fork(); + if (pid < 0) { + error("fork: %.100s", strerror(errno)); + return; + } + if (...

...e to serve connections, + * but put in background and no more new connections). + */ +static +void +forkoff(int stop_listening, int detach) +{ + pid_t pid; + int fd; + Channel *c; + + /* Restore tty modes. */ + leave_raw_mode(); + + /* Stop listening for new connections. */ + if (stop_listening) + channel_stop_listening(); + + fprintf(stderr, "Forking off into the background - %s, %s", + stop_listening ? "no longer listening" : "still listening", + detach ? "detaching" : "not detaching"); + + /* Fork into background. */ + pid = fork(); + if (pid < 0) { + erro...

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