Barney Wolff <[EMAIL PROTECTED]> writes:
> Er, could it possibly be that telnet has been hiding the error
> all along? It's really, really hard to see how ssh could
> *create* this sort of error.
Try the following patch (which I dug up off the Web after the previous
go-round on this problem). It seems to work.
(The indentation is wrong, I know. I had to apply the patch -l because
the HTMLization of the original mail message hosed the whitespace.)
--- /usr/src/crypto/openssh/session.c Sun Feb 4 10:01:29 2001
+++ /usr/src/crypto/openssh/session.c.PIPE_PATCH Sun Feb 4 10:01:58 2001
@@ -448,8 +448,6 @@
if (s == NULL)
fatal("do_exec_no_pty: no session");
- signal(SIGPIPE, SIG_DFL);
-
session_proctitle(s);
#ifdef USE_PAM
@@ -461,6 +459,8 @@
/* Child. Reinitialize the log since the pid has changed. */
log_init(__progname, options.log_level, options.log_facility,
log_stderr);
+ signal(SIGPIPE, SIG_DFL);
+
/*
* Create a new session and process group since the 4.4BSD
* setlogin() affects the entire process group.
@@ -569,6 +569,8 @@
if ((pid = fork()) == 0) {
/* Child. Reinitialize the log because the pid has changed. */
log_init(__progname, options.log_level, options.log_facility,
log_stderr);
+
+ signal(SIGPIPE, SIG_DFL);
/* Close the master side of the pseudo tty. */
close(ptyfd);
--
Christopher Davis * <[EMAIL PROTECTED]> * <URL:http://www.ckdhr.com/ckd/>
Put location information in your DNS! <URL:http://www.ckdhr.com/dns-loc/>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
